draft-ietf-mpls-ldp-mib-10.txt   draft-ietf-mpls-ldp-mib-11.txt 
Network Working Group J. Cucchiara Network Working Group J. Cucchiara
Internet-Draft Artel Internet-Draft Artel
Expires October 2003 H. Sjostrand Expires December 2003 H. Sjostrand
IP Unplugged IP Unplugged
J. Luciani J. Luciani
Consultant Consultant
April 2003 June 2003
Definitions of Managed Objects for Definitions of Managed Objects for
the Multiprotocol Label Switching, Label Distribution Protocol (LDP) the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
<draft-ietf-mpls-ldp-mib-10.txt> <draft-ietf-mpls-ldp-mib-11.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1 Introduction ................................................. 3 1 Introduction ................................................. 3
2 The Internet-Standard Management Framework ................... 3 2 The Internet-Standard Management Framework ................... 3
3 Structure of the MIB ......................................... 4 3 Structure of the MIB ......................................... 4
3.1 Overview ................................................... 4 3.1 Overview ................................................... 4
3.2 Future Considerations ...................................... 4 3.2 Future Considerations ...................................... 4
3.3 Interface Indexing ......................................... 5 3.3 Interface Indexing ......................................... 5
3.4 Differences from the LDP Specification ..................... 5 3.4 Differences from the LDP Specification ..................... 5
3.5 The MPLS-LDP-MIB Module .................................... 5 3.5 The MPLS-LDP-STD-MIB Module ................................ 5
3.5.1 The LDP Entity Table ..................................... 6 3.5.1 The LDP Entity Table ..................................... 6
3.5.1.1 Changing Values After Session Establishment ............ 6 3.5.1.1 Changing Values After Session Establishment ............ 6
3.5.2 The LDP Entity Statistics Table .......................... 7 3.5.2 The LDP Entity Statistics Table .......................... 7
3.5.3 The LDP Peer Table ....................................... 7 3.5.3 The LDP Peer Table ....................................... 7
3.5.4 The LDP Session Table .................................... 8 3.5.4 The LDP Session Table .................................... 8
3.5.5 The LDP Session Statistics Table ......................... 8 3.5.5 The LDP Session Statistics Table ......................... 8
3.5.6 The LDP Hello Adjacencies Table .......................... 8 3.5.6 The LDP Hello Adjacencies Table .......................... 8
3.5.7 The LDP LSP Table ........................................ 8 3.5.7 The LDP LSP Table ........................................ 8
3.5.8 The FEC Table ............................................ 9 3.5.8 The FEC Table ............................................ 9
3.5.9 The LDP Session Peer Address Table ....................... 9 3.5.9 The LDP Session Peer Address Table ....................... 9
3.6 LDP Notifications .......................................... 10 3.6 LDP Notifications .......................................... 10
3.7 LDP Notification Frequency ................................. 10
4 MPLS Label Distribution Protocol MIB Definitions ............. 10 4 MPLS Label Distribution Protocol MIB Definitions ............. 10
4.1 The MPLS-LDP-ATM-MIB Module ................................ 62 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 64
4.1.1 The LDP ATM Session Table ................................ 63 4.1.1 The LDP ATM Session Table ................................ 64
4.2 The MPLS-LDP-FRAME-RELAY-MIB Module ........................ 80 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 81
4.2.1 The LDP Frame Relay Session Table ........................ 80 4.2.1 The LDP Frame Relay Session Table ........................ 82
4.3 The MPLS-LDP-GENERIC-MIB Module ............................ 94 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 96
5 Revision History ............................................. 103 5 Revision History ............................................. 104
5.1 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 103 5.1 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 104
5.1.1 Changes based on MIB Doctor Review Comments .............. 103 5.2 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 104
5.2 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 108 5.2.1 Changes based on MIB Doctor Review Comments .............. 104
5.3 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 110 5.3 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 109
5.4 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 111 5.4 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 111
5.5 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 112 5.5 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 112
5.6 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 114 5.6 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 113
5.7 Changes from <draft-ietf-mpls-ldp-mib-03.txt> .............. 116 5.7 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 115
5.8 Changes from <draft-ietf-mpls-ldp-mib-02.txt> .............. 117 5.8 Changes from <draft-ietf-mpls-ldp-mib-03.txt> .............. 117
5.9 Changes from <draft-ietf-mpls-ldp-mib-01.txt> .............. 118 5.9 Changes from <draft-ietf-mpls-ldp-mib-02.txt> .............. 119
5.10 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 119 5.10 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 119
6 Acknowledgments .............................................. 120 5.11 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 120
7 Normative References ......................................... 121 6 Acknowledgments .............................................. 121
8 Informative References ....................................... 123 7 Normative References ......................................... 122
9 Security Considerations ...................................... 123 8 Informative References ....................................... 124
9.1 Security Considerations for MPLS-LDP-MIB ................... 123 9 Security Considerations ...................................... 124
9.2 Security Considerations for MPLS-LDP-ATM-MIB ............... 125 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 124
9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-MIB ....... 126 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 125
9.4 Security Considerations for MPLS-LDP-GENERIC-MIB ........... 127 ........................................................... 126
9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 127
9.5 Additional Security Considerations ......................... 128
10 IANA Considerations ......................................... 128 10 IANA Considerations ......................................... 128
10.1 IANA Considerations for the MPLS-LDP-MIB Module ........... 129 10.1 IANA Considerations for the MPLS-LDP-STD-MIB Module ....... 128
10.2 IANA Considerations for the MPLS-LDP-ATM-MIB Module ....... 129
Module .................................................... 129
........................................................... 129 ........................................................... 129
...................................................... 129
Module .................................................... 129
11 Intellectual Property Notice ................................ 129 11 Intellectual Property Notice ................................ 129
12 Authors' Addresses .......................................... 130 12 Authors' Addresses .......................................... 129
13 Full Copyright Statement .................................... 130 13 Full Copyright Statement .................................... 130
1. Introduction 1. Introduction
This document defines 4 MIB Modules which together support the This document defines 4 MIB Modules which together support the
configuration and monitoring of the Label Distribution Protocol configuration and monitoring of the Label Distribution Protocol
(LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type
of Multiprotocol Label Switching (MPLS) protocols described in of Multiprotocol Label Switching (MPLS) protocols described in
[RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an
operator to configure LDP sessions using 3 different Layer 2 media. operator to configure LDP sessions using 3 different Layer 2 media.
skipping to change at page 5, line 12 skipping to change at page 5, line 12
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Structure of the MIB 3. Structure of the MIB
This section describes the structure of the LDP MIB. This section describes the structure of the LDP MIB.
3.1. Overview 3.1. Overview
There are 4 MIB Modules in this document. These MIB Modules are the There are 4 MIB Modules in this document. These MIB Modules are the
MPLS-LDP-MIB, the MPLS-LDP-GENERIC-MIB, the MPLS-LDP-ATM-MIB and the MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD-
MPLS-LDP-FRAME-RELAY-MIB. The MPLS-LDP-MIB defines objects which are MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB
common to all LDP implementations. The MPLS-LDP-GENERIC-MIB defines defines objects which are common to all LDP implementations. The
Layer 2 Per Platform Label Space objects for use with the MPLS-LDP- MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space
MIB. The MPLS-LDP-ATM-MIB defines Layer 2 Asynchronous Transfer Mode objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB
(ATM) objects for use with the MPLS-LDP-MIB. The MPLS-LDP-FRAME- defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with
RELAY-MIB defines Layer 2 FRAME-RELAY objects for use with the MPLS- the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer
LDP-MIB. 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB.
The MPLS-LDP-MIB Module MUST be implemented and at least one of the The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of
Layer 2 MIB Modules MUST be implemented. As an example, if an LSR the Layer 2 MIB Modules MUST be implemented. As an example, if an
implementation wants to support LDP utilizing a Layer 2 of Ethernet, Label Switching Router (LSR) or Label Edge Router (LER)
then the MPLS-LDP-MIB and the MPLS-LDP-GENERIC-MIB Modules would be implementation intends to support LDP utilizing a Layer 2 of
implemented. If an LSR implementation wants to support LDP utilizing Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB
a Layer 2 of ATM, then the MPLS-LDP-MIB Module MUST be implemented Modules MUST implemented. If an LSR/LER implementation intends to
and the MPLS-LDP-ATM-MIB Module would be implemented. If an LSR support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB
implementation wants to support LDP utilizing a Layer 2 of FRAME- Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an
RELAY, then the MPLS-LDP-MIB Module would be implemented and the LSR/LER implementation intends to support LDP utilizing a Layer 2 of
MPLS-LDP-FRAME-RELAY-MIB Module would be implemented. An LDP FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME-
implementation that utilizes all 3 Layer 2 media (Ethernet, Frame- RELAY-STD-MIB Module MUST be implemented. An LDP implementation that
Relay, ATM) would support all 4 MIB Modules. Each of the Modules utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST
will be discussed in detail in the following sections. support all 4 MIB Modules. Each of the Modules will be discussed in
detail in the following sections.
There are 2 Compliance statements for each MIB Module. One which is There are 2 Compliance statements for each MIB Module. One which is
for FULL Compliance which includes configuration and monitoring via for full compliance which includes configuration and monitoring via
SNMP. The other is a READ-ONLY Compliance which is only monitoring SNMP. The other is a read-only compliance which allows SNMP to
via SNMP. monitor.
3.2. Future Considerations 3.2. Future Considerations
The LDP Specification [RFC3036] does not specify the use of VPNs or The LDP Specification [RFC3036] does not specify the use of VPNs or
multicast for LDP, and thus, objects related to these areas have not multicast for LDP, and thus, objects related to these areas have not
been included in the MIB. been included.
This MIB does not include VP merge configuration either. [RFC2684] [RFC2684] does not describe VP merge capability and so this feature
does not yet describe this capability and so it has been excluded has not been included.
from the MIB.
These areas need to be specified in the LDP Specification or other These areas need to be specified in the LDP Specification or other
specifications prior to being added in this or any other MIB. specifications prior to being added in this or any other MIB
document.
3.3. Interface Indexing 3.3. Interface Indexing
Interface Indexes as specified in [RFC2863] are used in the MIB. The Interface Indexes as specified in [RFC2863] are used in these MIB
descriptions of the ifIndexes denote which ifIndex is being used. Modules. The descriptions of the ifIndexes denote which ifIndex is
NOTE: the use of ifIndex is for actual existing connections. being used. The use of ifIndex is for actual existing connections.
3.4. Differences from the LDP Specification 3.4. Differences from the LDP Specification
Currently, there are 3 differences between this specification and the Currently, there are 3 differences between this specification and the
LDP Specification. As previously mentioned, this MIB is almost LDP Specification. As previously mentioned, this document is almost
entirely based on the LDP specification. The differences are entirely based on the LDP specification. The differences are
documented here in the hope to avoid any confusion between the two documented here.
documents.
The first difference is that the LDP Entity Table contains some The first difference is that the LDP Entity Table contains some
DEFVAL clauses which are not specified explicitly in the LDP DEFVAL clauses which are not specified explicitly in the LDP
Specification. These values, although not documented in the LDP Specification. These values, although not documented in the LDP
Specification are widely used by existing LDP MIB implementations and Specification are widely used by existing LDP MIB implementations and
thus, have been adopted within this MIB. Please note, they can thus, have been adopted within this MPLS-LDP-STD-MIB. Please note,
certainly be changed during row creation or a subsequent set request. they can certainly be changed during row creation or a subsequent set
request.
A second difference is the mplsLdpEntityConfGenericLabelRangeTable. A second difference is the mplsLdpEntityConfGenericLRTable in the
This table, although provided as a way to reserve a range of generic MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a
labels, does not exist in the LDP Specification. It was added to the way to reserve a range of generic labels, does not exist in the LDP
MIB due to a request from the working group and because this table Specification. It was added to the MIB due to a request from the
was considered useful for reserving a range of generic labels. working group and because this table was considered useful for
reserving a range of generic labels.
The third difference is documented by the TEXTUAL-CONVENTION, The third difference is documented by the TEXTUAL-CONVENTION,
MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC
was added to restrict vci values to be greater than 31 as described was added to restrict vci values to be greater than 31 as described
in RFC 3035 [RFC3035]. in RFC 3035 [RFC3035].
3.5. The MPLS-LDP-MIB Module 3.5. The MPLS-LDP-STD-MIB Module
This MIB Module contains objects which are common to all LDP This MIB Module contains objects which are common to all LDP
implementations. This MIB Module MUST always be implemented along implementations. This MIB Module MUST always be implemented along
with one or more of the Layer 2 MIB Modules. with one or more of the Layer 2 MIB Modules.
NOTE, this table allows the Label Edge Router (LER) or the Label This table allows the Label Edge Router (LER) or the Label Switching
Switching router (LSR) to initiate and/or receive requests to router (LSR) to initiate and/or receive requests to establish LDP
establish LDP sessions. As the LDP protocol distributes labels and sessions. As the LDP protocol distributes labels and establishes
establishes sessions with Peers most of the tables in this MIB are sessions with Peers most of the tables in this MIB are populated by
populated by the agent as instructed by the LDP protocol. The the agent as instructed by the LDP protocol. The exception is the
exception is the mplsFecTable and the mplsLdpLspFecTable which can be mplsFecTable and the mplsLdpLspFecTable which can be configured by
configured by the operator to specify Forwarding Equivalence Class the operator to specify Forwarding Equivalence Class information for
information for an LSP. an LSP.
Each table in this MIB Module is described in the following Each table in the MPLS-LDP-STD-MIB Module is described in the
subsections. following subsections.
3.5.1. The LDP Entity Table 3.5.1. The LDP Entity Table
The MPLS-LDP-MIB provides objects to configure/set-up potential LDP The MPLS-LDP-STD-MIB provides objects to configure or allow potential
sessions on a specific LSR. The mplsLdpEntityTable is used to LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used
configure potential LDP Sessions, where each row in the table to configure potential LDP Sessions, where each row in the table
represents a potential LDP Session. represents a potential LDP Session.
Each entry/row in this table represents a single LDP Entity. There Each entry/row in this table represents a single LDP Entity. There
is no maximum number of LDP Entities specified. However, there is an is no maximum number of LDP Entities specified. However, there is an
mplsLdpEntityIndexNext object which should be retrieved by the mplsLdpEntityIndexNext object which should be retrieved by the
command generator prior to creating an LDP Entity. If the command generator prior to creating an LDP Entity. If the
mplsLdpEntityIndexNext object is zero, this indicates that the LSR is mplsLdpEntityIndexNext object is zero, this indicates that the LSR is
not able to create another LDP Entity at that time. not able to create another LDP Entity at that time.
3.5.1.1. Changing Values After Session Establishment 3.5.1.1. Changing Values After Session Establishment
One way to manually modify a session's parameters is by using SNMP to One way to manually modify a session's parameters is by using SNMP to
change the MIB objects related to that session. Please note special change the MIB objects related to that session. Please note, special
care should be taken if MIB objects which are used in the MPLS LDP care should be taken if MIB objects which are used in the MPLS LDP
Session Initialization need to be modified. If the modification of Session Initialization need to be modified. If the modification of
any of these MIB variables takes place anytime after the start of any of these MIB variables takes place anytime after the start of
session intialization, then the entire session must be halted. Any session intialization, then the entire session must be halted. Any
information learned by that session must be discarded. The objects information learned by that session must be discarded. The objects
should then be modified, and session initialization started. should then be modified, and session initialization started.
Assuming that the configuration was done correctly, then a new
session will be created.
For example, assume that an operator wishes to change the For example, assume that an operator wishes to change the
configuration of a Label Range which is used by a Session that has configuration of a Label Range which is used by a Session that has
already been established. The operator should change the already been established. The operator should change the
mplsLdpEntityAdminStatus to "disable(2)". Setting the mplsLdpEntityAdminStatus to "disable(2)". Setting the
mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be
torn down (i.e. this will signal to LDP that it should send out tear torn down (i.e. this will signal to LDP that it should send out tear
down messages for that session). Also, all information related to down messages for that session). Also, all information related to
that session should be removed from this MIB by the Agent. This that session should be removed from this MIB by the Agent. This
includes Peer information (i.e. relevant row in the mplsPeerTable) includes Peer information (i.e. relevant row in the mplsPeerTable)
and Session statistics (i.e. releveant row in the mplsLdpSesTable). and Session statistics (i.e. releveant row in the
Also, if the LSR MIB is implemented and the optional Mapping Table mplsLdpSessionTable). Also, if the LSR MIB is implemented and the
objects are implemented, then all information related to the LSPs in optional Mapping Table objects are implemented, then all information
this session should be removed from these MIBs. [For more information related to the LSPs in this session should be removed from these
please see the section on "The Mapping Tables".] At this point, the MIBs. [For more information please see the section on "The Mapping
operator could modify the Label Range. Lastly, the operator should Tables".] At this point, the operator could modify the Label Range.
set the mplsLdpEntityAdminStatus to "enable(1)". At this point Lastly, the operator should set the mplsLdpEntityAdminStatus to
session initialization should occur. The LDP Entity goes through the "enable(1)". At this point session initialization should occur. The
Session Initialization in order to communicate the new Label Ranges LDP Entity goes through the Session Initialization in order to
to the Peer and establish new LSPs. communicate the new Label Ranges to the Peer and establish new LSPs.
3.5.2. The LDP Entity Statistics Table 3.5.2. The LDP Entity Statistics Table
The mplsLpdEntityStatsTable is a read-only table which contains The mplsLpdEntityStatsTable is a read-only table which contains
statistical information related to failed attempts to establish statistical information related to failed attempts to establish
sessions. Each row in this table is related to a single LDP entity sessions. Each row in this table is related to a single LDP entity
and this table AUGMENTS an mplsLdpEntityEntry. This table could be and this table AUGMENTS an mplsLdpEntityEntry. This table could be
used to give insight into how to reconfigure values so that a session used to give insight into how to reconfigure values so that a session
could be successfully established. For example, if the could be successfully established. For example, if the
mplsLdpSesRejectedLRErrors Counter object was increasing, then this mplsLdpSesRejectedLRErrors Counter object was increasing, then this
skipping to change at page 11, line 15 skipping to change at page 11, line 15
3.6. LDP Notifications 3.6. LDP Notifications
Currently, there are several notifications which are specific for Currently, there are several notifications which are specific for
LDP. These are described in this section. LDP. These are described in this section.
The mplsLdpInitSesThresholdExceeded notification indicates to the The mplsLdpInitSesThresholdExceeded notification indicates to the
operator that there may be a misconfigured mplsLdpEntityEntry because operator that there may be a misconfigured mplsLdpEntityEntry because
the session associated with this Entity is not being established, and the session associated with this Entity is not being established, and
the Entity keeps trying to establish the session. A side effect of the Entity keeps trying to establish the session. A side effect of
this situation is that a row in the mplsLdpSessionTable may not be this situation is that a row in the mplsLdpSessionTable may not be
reaching the operational state as indicated by the mplsLdpSesState reaching the operational state as indicated by the
object. If the value of mplsLdpEntityInitSesThreshold is 0 (zero) mplsLdpSessionState object. If the value of
then this is equal to specifying the value of infinity for the mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to
threshold, and the mplsLdpInitSesThresholdExceeded notification will specifying the value of infinity for the threshold, and the
never be sent. mplsLdpInitSessionThresholdExceeded notification will never be sent.
The mplsLdpPathVectorLimitMismatch notification is generated when The mplsLdpPathVectorLimitMismatch notification is generated when
there is a mismatch in the Path Vector Limits between the Entity and there is a mismatch in the Path Vector Limits between the Entity and
Peer during session initialization. The session uses the value which Peer during session initialization. The session uses the value which
is configured as the Entity's Path Vector Limit. However, a is configured as the Entity's Path Vector Limit. However, a
notification should be generated to indicate that a mismatch notification should be generated to indicate that a mismatch
occurred. For further details, please see Section 3.5.3 of the LDP occurred. For further details, please see Section 3.5.3 of the LDP
Specification [RFC3036]. Specification [RFC3036].
The mplsLdpSessionUp and mplsLdpSessionDown notifications are The mplsLdpSessionUp and mplsLdpSessionDown notifications are
generated when there is an appropriate change in the mplsLdpSesState generated when there is an appropriate change in the
object, e.g. when sessions change state (Up to Down for the mplsLdpSessionState object, e.g. when sessions change state (Up to
mplsLdpSessionDown trap, or Down to Up for the mplsLdpSessionUp Down for the mplsLdpSessionDown trap, or Down to Up for the
trap). mplsLdpSessionUp trap).
3.7. LDP Notification Frequency
LDP Notifications are expected to be few in number when LDP is
ubiquitously deployed in a relatively stable network. An NMS that is
receiving these notifications should not be overwhelmed by the
frequency of LDP notifications. If this assertion proves to be
inaccurate, then a throttling object to throttle these notifications
may be added to future versions of the MPLS-LDP-STD-MIB.
4. MPLS Label Distribution Protocol MIB Definitions 4. MPLS Label Distribution Protocol MIB Definitions
MPLS-LDP-MIB DEFINITIONS ::= BEGIN MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
Integer32, Counter32, Unsigned32 Integer32, Counter32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, TimeInterval, TruthValue, RowStatus, TimeInterval, TruthValue,
TimeStamp, StorageType TimeStamp, StorageType
skipping to change at page 12, line 17 skipping to change at page 12, line 27
InetAddressPrefixLength, InetAddressPrefixLength,
InetAddressType, InetAddressType,
InetAddress, InetAddress,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
IndexInteger, IndexInteger,
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB FROM DIFFSERV-MIB
mplsMIB, mplsStdMIB,
MplsLabel, MplsLabel,
MplsLabelDistributionMethod, MplsLabelDistributionMethod,
MplsLdpIdentifier, MplsLdpIdentifier,
MplsLdpLabelType, MplsLdpLabelType,
MplsLspType, MplsLspType,
MplsLsrIdentifier, MplsLsrIdentifier,
MplsRetentionMode MplsRetentionMode
FROM MPLS-TC-STD-MIB;
FROM MPLS-TC-MIB; mplsLdpStdMIB MODULE-IDENTITY
LAST-UPDATED "200306091200Z" -- 9 June 2003
mplsLdpMIB MODULE-IDENTITY
LAST-UPDATED "200304221200Z" -- 22 April 2003
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@artel.com)
Artel Artel
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Consultant Consultant
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net" MPLS Working Group, email: mpls@uu.net"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
This MIB contains managed object definitions for the This MIB contains managed object definitions for the
'Multiprotocol Label Switching, Label Distribution 'Multiprotocol Label Switching, Label Distribution
Protocol, LDP' document." Protocol, LDP' document."
REVISION "200304221200Z" -- 22 April 2003 REVISION "200306091200Z" -- 9 June 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsMIB subId is 4, e.g. -- The requested mplsStdMIB subId is 4, e.g.
-- ::= { mplsMIB 4 } -- ::= { mplsStdMIB 4 }
::= { mplsMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 0 } mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 }
mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 }
mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP Objects -- MPLS LDP Objects
--**************************************************************** --****************************************************************
mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 }
mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 }
-- --
skipping to change at page 16, line 21 skipping to change at page 16, line 28
mplsLdpEntityLdpId MplsLdpIdentifier, mplsLdpEntityLdpId MplsLdpIdentifier,
mplsLdpEntityIndex IndexInteger, mplsLdpEntityIndex IndexInteger,
mplsLdpEntityProtocolVersion Unsigned32, mplsLdpEntityProtocolVersion Unsigned32,
mplsLdpEntityAdminStatus INTEGER, mplsLdpEntityAdminStatus INTEGER,
mplsLdpEntityOperStatus INTEGER, mplsLdpEntityOperStatus INTEGER,
mplsLdpEntityTcpDscPort InetPortNumber, mplsLdpEntityTcpDscPort InetPortNumber,
mplsLdpEntityUdpDscPort InetPortNumber, mplsLdpEntityUdpDscPort InetPortNumber,
mplsLdpEntityMaxPduLength Unsigned32, mplsLdpEntityMaxPduLength Unsigned32,
mplsLdpEntityKeepAliveHoldTimer Unsigned32, mplsLdpEntityKeepAliveHoldTimer Unsigned32,
mplsLdpEntityHelloHoldTimer Unsigned32, mplsLdpEntityHelloHoldTimer Unsigned32,
mplsLdpEntityInitSesThreshold Integer32, mplsLdpEntityInitSessionThreshold Integer32,
mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod,
mplsLdpEntityLabelRetentionMode MplsRetentionMode, mplsLdpEntityLabelRetentionMode MplsRetentionMode,
mplsLdpEntityPathVectorLimit Integer32, mplsLdpEntityPathVectorLimit Integer32,
mplsLdpEntityHopCountLimit Integer32, mplsLdpEntityHopCountLimit Integer32,
mplsLdpEntityTransportAddrKind INTEGER, mplsLdpEntityTransportAddrKind INTEGER,
mplsLdpEntityTargetPeer TruthValue, mplsLdpEntityTargetPeer TruthValue,
mplsLdpEntityTargetPeerAddrType InetAddressType, mplsLdpEntityTargetPeerAddrType InetAddressType,
mplsLdpEntityTargetPeerAddr InetAddress, mplsLdpEntityTargetPeerAddr InetAddress,
mplsLdpEntityLabelType MplsLdpLabelType, mplsLdpEntityLabelType MplsLdpLabelType,
mplsLdpEntityDiscontinuityTime TimeStamp, mplsLdpEntityDiscontinuityTime TimeStamp,
skipping to change at page 16, line 43 skipping to change at page 17, line 5
mplsLdpEntityRowStatus RowStatus mplsLdpEntityRowStatus RowStatus
} }
mplsLdpEntityLdpId OBJECT-TYPE mplsLdpEntityLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP identifier." "The LDP identifier."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section on LDP Identifiers." "RFC3036, LDP Specification, Section on LDP Identifiers."
::= { mplsLdpEntityEntry 1 } ::= { mplsLdpEntityEntry 1 }
mplsLdpEntityIndex OBJECT-TYPE mplsLdpEntityIndex OBJECT-TYPE
SYNTAX IndexInteger SYNTAX IndexInteger
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is used as a secondary index to uniquely "This index is used as a secondary index to uniquely
identify this row. Before creating a row in this table, identify this row. Before creating a row in this table,
the 'mplsLdpEntityIndexNext' object should be retrieved. the 'mplsLdpEntityIndexNext' object should be retrieved.
skipping to change at page 17, line 37 skipping to change at page 17, line 45
DESCRIPTION DESCRIPTION
"The version number of the LDP protocol which will be "The version number of the LDP protocol which will be
used in the session initialization message. used in the session initialization message.
Section 3.5.3 in the LDP Specification specifies Section 3.5.3 in the LDP Specification specifies
that the version of the LDP protocol is negotiated during that the version of the LDP protocol is negotiated during
session establishment. The value of this object session establishment. The value of this object
represents the value that is sent in the initialization represents the value that is sent in the initialization
message." message."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3 Initialization "RFC3036, LDP Specification, Section 3.5.3 Initialization
Message." Message."
DEFVAL { 1 } DEFVAL { 1 }
::= { mplsLdpEntityEntry 3 } ::= { mplsLdpEntityEntry 3 }
mplsLdpEntityAdminStatus OBJECT-TYPE mplsLdpEntityAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enable(1), enable(1),
disable(2) disable(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status of this LDP Entity. "The administrative status of this LDP Entity.
If this object is changed from 'enable' to 'disable' If this object is changed from 'enable' to 'disable'
skipping to change at page 18, line 20 skipping to change at page 18, line 28
that the network management subsystem should clean that the network management subsystem should clean
up any related entry in the mplsLdpPeerTable. This up any related entry in the mplsLdpPeerTable. This
further implies that a 'tear-down' for that session further implies that a 'tear-down' for that session
is issued and the session and all information related is issued and the session and all information related
to that session cease to exist). to that session cease to exist).
At this point the operator is able to change values At this point the operator is able to change values
which are related to this entity. which are related to this entity.
When the admin status is set back to 'enable', then When the admin status is set back to 'enable', then
this Entity will attempt to establish a NEW session this Entity will attempt to establish a new session
with the Peer." with the Peer."
DEFVAL { enable } DEFVAL { enable }
::= { mplsLdpEntityEntry 4 } ::= { mplsLdpEntityEntry 4 }
mplsLdpEntityOperStatus OBJECT-TYPE mplsLdpEntityOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
enabled(2), enabled(2),
disabled(3) disabled(3)
} }
skipping to change at page 18, line 46 skipping to change at page 19, line 9
mplsLdpEntityTcpDscPort OBJECT-TYPE mplsLdpEntityTcpDscPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP Discovery Port for "The TCP Discovery Port for
LDP. The default value is the well-known LDP. The default value is the well-known
value of this port." value of this port."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.4.1, "RFC3036, LDP Specification, Section 2.4.1,
Basic Discovery Mechanism, Section 2.4.2, Basic Discovery Mechanism, Section 2.4.2,
Extended Discovery Mechanism, Section Extended Discovery Mechanism, Section
3.10, Well-known Numbers, and Section 3.10.1. 3.10, Well-known Numbers, and Section 3.10.1.
UDP and TCP Ports." UDP and TCP Ports."
DEFVAL { 646 } DEFVAL { 646 }
::= { mplsLdpEntityEntry 6 } ::= { mplsLdpEntityEntry 6 }
mplsLdpEntityUdpDscPort OBJECT-TYPE mplsLdpEntityUdpDscPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP Discovery Port for "The UDP Discovery Port for
LDP. The default value is the LDP. The default value is the
well-known value for this port." well-known value for this port."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.4.1, "RFC3036, LDP Specification, Section 2.4.1,
Basic Discovery Mechanism, Section 2.4.2, Basic Discovery Mechanism, Section 2.4.2,
Extended Discovery Mechanism, Section Extended Discovery Mechanism, Section
3.10, Well-known Numbers, and Section 3.10.1. 3.10, Well-known Numbers, and Section 3.10.1.
UDP and TCP Ports." UDP and TCP Ports."
DEFVAL { 646 } DEFVAL { 646 }
::= { mplsLdpEntityEntry 7 } ::= { mplsLdpEntityEntry 7 }
mplsLdpEntityMaxPduLength OBJECT-TYPE mplsLdpEntityMaxPduLength OBJECT-TYPE
SYNTAX Unsigned32 (256..65535) SYNTAX Unsigned32 (256..65535)
UNITS "octets" UNITS "octets"
skipping to change at page 19, line 45 skipping to change at page 20, line 7
a value of 255 or less specifies the a value of 255 or less specifies the
default maximum length of 4096 octets, this is why default maximum length of 4096 octets, this is why
the value of this object starts at 256. The operator the value of this object starts at 256. The operator
should explicitly choose the default value (i.e. 4096), should explicitly choose the default value (i.e. 4096),
or some other value. or some other value.
The receiving LSR MUST calculate the maximum PDU The receiving LSR MUST calculate the maximum PDU
length for the session by using the smaller of its and length for the session by using the smaller of its and
its peer's proposals for Max PDU Length." its peer's proposals for Max PDU Length."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3. "RFC3036, LDP Specification, Section 3.5.3.
Initialization Message." Initialization Message."
DEFVAL { 4096 } DEFVAL { 4096 }
::= { mplsLdpEntityEntry 8 } ::= { mplsLdpEntityEntry 8 }
mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 16-bit integer value which is the proposed keep "The 16-bit integer value which is the proposed keep
alive hold timer for this LDP Entity." alive hold timer for this LDP Entity."
DEFVAL { 40 } DEFVAL { 40 }
::= { mplsLdpEntityEntry 9 } ::= { mplsLdpEntityEntry 9 }
skipping to change at page 21, line 4 skipping to change at page 21, line 12
specifies that the Hold Time's actual default value is specifies that the Hold Time's actual default value is
45 seconds (i.e. the default Hold time for Targeted 45 seconds (i.e. the default Hold time for Targeted
Hellos is 45 seconds). Hellos is 45 seconds).
A value of 65535 means infinite (i.e. wait forever). A value of 65535 means infinite (i.e. wait forever).
All other values represent the amount of time in All other values represent the amount of time in
seconds to wait for a Hello Message. Setting the seconds to wait for a Hello Message. Setting the
hold time to a value smaller than 15 is not hold time to a value smaller than 15 is not
recommended, although not forbidden according recommended, although not forbidden according
to [RFC3036]." to RFC3036."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.2., "RFC3036, LDP Specification, Section 3.5.2.,
Hello Message." Hello Message."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLdpEntityEntry 10 } ::= { mplsLdpEntityEntry 10 }
mplsLdpEntityInitSesThreshold OBJECT-TYPE mplsLdpEntityInitSessionThreshold OBJECT-TYPE
SYNTAX Integer32(0..100) SYNTAX Integer32(0..100)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When attempting to establish a session with a "When attempting to establish a session with a
given Peer, the given LDP Entity should given Peer, the given LDP Entity should
send out the SNMP notification, send out the SNMP notification,
'mplsLdpInitSesThresholdExceeded', when 'mplsLdpInitSesThresholdExceeded', when
the number of Session Initialization messages sent the number of Session Initialization messages sent
exceeds this threshold. The notification is exceeds this threshold. The notification is
skipping to change at page 21, line 34 skipping to change at page 21, line 42
sequence of messages as each NAKs the other's sequence of messages as each NAKs the other's
Initialization messages with Error Notification Initialization messages with Error Notification
messages. Setting this threshold which triggers messages. Setting this threshold which triggers
the notification is one way to the notification is one way to
notify the operator. notify the operator.
A value of 0 (zero) for this object A value of 0 (zero) for this object
indicates that the threshold is infinity, thus indicates that the threshold is infinity, thus
the SNMP notification will never be generated." the SNMP notification will never be generated."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, "RFC3036, LDP Specification,
Section 2.5.3 Session Initialization." Section 2.5.3 Session Initialization."
DEFVAL { 8 } DEFVAL { 8 }
::= { mplsLdpEntityEntry 11 } ::= { mplsLdpEntityEntry 11 }
mplsLdpEntityLabelDistMethod OBJECT-TYPE mplsLdpEntityLabelDistMethod OBJECT-TYPE
SYNTAX MplsLabelDistributionMethod SYNTAX MplsLabelDistributionMethod
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For any given LDP session, the method of "For any given LDP session, the method of
skipping to change at page 22, line 38 skipping to change at page 22, line 46
Otherwise, if this object has a value greater than Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors is enabled, zero, then Loop Dection for Path Vectors is enabled,
and the Path Vector Limit is this value. and the Path Vector Limit is this value.
Also, the value of the object, Also, the value of the object,
'mplsLdpLsrLoopDetectionCapable', must be set to 'mplsLdpLsrLoopDetectionCapable', must be set to
either 'pathVector(4)' or 'hopCountAndPathVector(5)', either 'pathVector(4)' or 'hopCountAndPathVector(5)',
if this object has a value greater than 0 (zero), if this object has a value greater than 0 (zero),
otherwise it is ignored." otherwise it is ignored."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.8 Loop Dection, "RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV." Section 3.4.5 Path Vector TLV."
::= { mplsLdpEntityEntry 14 } ::= { mplsLdpEntityEntry 14 }
mplsLdpEntityHopCountLimit OBJECT-TYPE mplsLdpEntityHopCountLimit OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 0 (zero), "If the value of this object is 0 (zero),
then Loop Detection using Hop Counters is then Loop Detection using Hop Counters is
disabled. disabled.
If the value of this object is greater than If the value of this object is greater than
skipping to change at page 24, line 45 skipping to change at page 25, line 7
this Entity. this Entity.
If the value is atmParameters(2) then If the value is atmParameters(2) then
a row must be created in the mplsLdpEntityAtmParms a row must be created in the mplsLdpEntityAtmParms
Table, which corresponds to this entry. Table, which corresponds to this entry.
If the value is frameRelayParameters(3) then If the value is frameRelayParameters(3) then
a row must be created in the mplsLdpEntityFrameRelayParms a row must be created in the mplsLdpEntityFrameRelayParms
Table, which corresponds to this entry." Table, which corresponds to this entry."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3., "RFC3036, LDP Specification, Section 3.5.3.,
Initialization Message." Initialization Message."
::= { mplsLdpEntityEntry 20 } ::= { mplsLdpEntityEntry 20 }
mplsLdpEntityDiscontinuityTime OBJECT-TYPE mplsLdpEntityDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this entity's counters at which any one or more of this entity's counters
suffered a discontinuity. The relevant counters are the suffered a discontinuity. The relevant counters are the
specific instances associated with this entity of specific instances associated with this entity of
any Counter32, or Counter64 object contained any Counter32, or Counter64 object contained
skipping to change at page 25, line 26 skipping to change at page 25, line 33
re-initialization of the local management re-initialization of the local management
subsystem, then this object contains a zero subsystem, then this object contains a zero
value." value."
::= { mplsLdpEntityEntry 21 } ::= { mplsLdpEntityEntry 21 }
mplsLdpEntityStorageType OBJECT-TYPE mplsLdpEntityStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row, except for setting the need not allow write-access to any columnar
mplsLdpEntityRowStatus to 'destroy(6)'." objects in the row."
DEFVAL{ nonVolatile } DEFVAL{ nonVolatile }
::= { mplsLdpEntityEntry 22 } ::= { mplsLdpEntityEntry 22 }
mplsLdpEntityRowStatus OBJECT-TYPE mplsLdpEntityRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any
detail in the section entitled, 'Changing Values After Session time, however, as described in detail in
Establishment', and again described in the the section entitled, 'Changing Values After
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a Session Establishment', and again described
session has been initiated with a Peer, changing objects in the DESCRIPTION clause of the
in this table will wreak havoc with the session and interrupt mplsLdpEntityAdminStatus object, if a session
traffic. To repeat again: the recommended procedure is to has been initiated with a Peer, changing objects
in this table will wreak havoc with the session
and interrupt traffic. To repeat again:
the recommended procedure is to
set the mplsLdpEntityAdminStatus to down, thereby set the mplsLdpEntityAdminStatus to down, thereby
explicitly causing a session to be torn down. Then, explicitly causing a session to be torn down. Then,
change objects in this entry, then set the mplsLdpEntityAdminStatus change objects in this entry, then set
to enable which enables a NEW session to be initiated." the mplsLdpEntityAdminStatus to enable,
which enables a new session to be initiated."
::= { mplsLdpEntityEntry 23 } ::= { mplsLdpEntityEntry 23 }
-- --
-- The MPLS LDP Entity Statistics Table -- The MPLS LDP Entity Statistics Table
-- --
mplsLdpEntityStatsTable OBJECT-TYPE mplsLdpEntityStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 26, line 42 skipping to change at page 27, line 9
error is counted here, because the error is counted here, because the
session is terminated. session is terminated.
If the error is NOT fatal (i.e. and the Session If the error is NOT fatal (i.e. and the Session
remains), then the error is counted in the remains), then the error is counted in the
mplsLdpSesStatsEntry." mplsLdpSesStatsEntry."
AUGMENTS { mplsLdpEntityEntry } AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 } ::= { mplsLdpEntityStatsTable 1 }
MplsLdpEntityStatsEntry ::= SEQUENCE { MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEntityStatsSesAttempts Counter32, mplsLdpEntityStatsSessionAttempts Counter32,
mplsLdpEntityStatsSesRejectedNoHelloErrors Counter32, mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32,
mplsLdpEntityStatsSesRejectedAdErrors Counter32, mplsLdpEntityStatsSessionRejectedAdErrors Counter32,
mplsLdpEntityStatsSesRejectedMaxPduErrors Counter32, mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32,
mplsLdpEntityStatsSesRejectedLRErrors Counter32, mplsLdpEntityStatsSessionRejectedLRErrors Counter32,
mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, mplsLdpEntityStatsBadLdpIdentifierErrors Counter32,
mplsLdpEntityStatsBadPduLengthErrors Counter32, mplsLdpEntityStatsBadPduLengthErrors Counter32,
mplsLdpEntityStatsBadMessageLengthErrors Counter32, mplsLdpEntityStatsBadMessageLengthErrors Counter32,
mplsLdpEntityStatsBadTlvLengthErrors Counter32, mplsLdpEntityStatsBadTlvLengthErrors Counter32,
mplsLdpEntityStatsMalformedTlvValueErrors Counter32, mplsLdpEntityStatsMalformedTlvValueErrors Counter32,
mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32,
mplsLdpEntityStatsShutdownReceivedNotifications Counter32, mplsLdpEntityStatsShutdownReceivedNotifications Counter32,
mplsLdpEntityStatsShutdownSentNotifications Counter32 mplsLdpEntityStatsShutdownSentNotifications Counter32
} }
mplsLdpEntityStatsSesAttempts OBJECT-TYPE mplsLdpEntityStatsSessionAttempts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total attempted sessions for "A count of the total attempted sessions for
this LDP Entity. this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 1 } ::= { mplsLdpEntityStatsEntry 1 }
mplsLdpEntityStatsSesRejectedNoHelloErrors OBJECT-TYPE mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the Session Rejected/No Hello Error "A count of the Session Rejected/No Hello Error
Notification Messages sent or received by Notification Messages sent or received by
this LDP Entity. this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 2 } ::= { mplsLdpEntityStatsEntry 2 }
mplsLdpEntityStatsSesRejectedAdErrors OBJECT-TYPE mplsLdpEntityStatsSessionRejectedAdErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the Session Rejected/Parameters "A count of the Session Rejected/Parameters
Advertisement Mode Error Notification Messages sent Advertisement Mode Error Notification Messages sent
or received by this LDP Entity. or received by this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 3 } ::= { mplsLdpEntityStatsEntry 3 }
mplsLdpEntityStatsSesRejectedMaxPduErrors OBJECT-TYPE mplsLdpEntityStatsSessionRejectedMaxPduErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the Session Rejected/Parameters "A count of the Session Rejected/Parameters
Max Pdu Length Error Notification Messages sent Max Pdu Length Error Notification Messages sent
or received by this LDP Entity. or received by this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 4 } ::= { mplsLdpEntityStatsEntry 4 }
mplsLdpEntityStatsSesRejectedLRErrors OBJECT-TYPE mplsLdpEntityStatsSessionRejectedLRErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the Session Rejected/Parameters "A count of the Session Rejected/Parameters
Label Range Notification Messages sent Label Range Notification Messages sent
or received by this LDP Entity. or received by this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
skipping to change at page 29, line 10 skipping to change at page 29, line 21
DESCRIPTION DESCRIPTION
"This object counts the number of Bad LDP Identifier "This object counts the number of Bad LDP Identifier
Fatal Errors detected by the session(s) Fatal Errors detected by the session(s)
(past and present) associated with this LDP Entity. (past and present) associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 6 } ::= { mplsLdpEntityStatsEntry 6 }
mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Bad Pdu Length "This object counts the number of Bad Pdu Length
Fatal Errors detected by the session(s) Fatal Errors detected by the session(s)
(past and present) associated with this LDP Entity. (past and present) associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 7 } ::= { mplsLdpEntityStatsEntry 7 }
mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Bad Message "This object counts the number of Bad Message
Length Fatal Errors detected by the session(s) Length Fatal Errors detected by the session(s)
(past and present) associated with this LDP Entity. (past and present) associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 8 } ::= { mplsLdpEntityStatsEntry 8 }
mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Bad TLV "This object counts the number of Bad TLV
Length Fatal Errors detected by the session(s) Length Fatal Errors detected by the session(s)
(past and present) associated with this LDP Entity. (past and present) associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 9 } ::= { mplsLdpEntityStatsEntry 9 }
mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Malformed TLV "This object counts the number of Malformed TLV
Value Fatal Errors detected by the session(s) Value Fatal Errors detected by the session(s)
(past and present) associated with this (past and present) associated with this
LDP Entity. LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 10 } ::= { mplsLdpEntityStatsEntry 10 }
mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Session Keep Alive "This object counts the number of Session Keep Alive
Timer Expired Errors detected by the session(s) Timer Expired Errors detected by the session(s)
(past and present) associated with this LDP Entity. (past and present) associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 11 } ::= { mplsLdpEntityStatsEntry 11 }
mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Shutdown Notfications "This object counts the number of Shutdown Notfications
received related to session(s) (past and present) received related to session(s) (past and present)
associated with this LDP Entity. associated with this LDP Entity.
skipping to change at page 31, line 40 skipping to change at page 32, line 7
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 13 } ::= { mplsLdpEntityStatsEntry 13 }
-- --
-- The MPLS LDP Peer Table -- The MPLS LDP Peer Table
-- --
mplsLdpSesObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 }
mplsLdpPeerLastChange OBJECT-TYPE mplsLdpPeerLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time of the most "The value of sysUpTime at the time of the most
recent addition or deletion to/from the recent addition or deletion to/from the
mplsLdpPeerTable/mplsLdpSesTable." mplsLdpPeerTable/mplsLdpSessionTable."
::= { mplsLdpSesObjects 1 } ::= { mplsLdpSessionObjects 1 }
mplsLdpPeerTable OBJECT-TYPE mplsLdpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpPeerEntry SYNTAX SEQUENCE OF MplsLdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about LDP peers known by Entities in "Information about LDP peers known by Entities in
the mplsLdpEntityTable. The information in this table the mplsLdpEntityTable. The information in this table
is based on information from the Entity-Peer interaction is based on information from the Entity-Peer interaction
during session initialization but is not appropriate during session initialization but is not appropriate
for the mplsLdpSesTable, because objects in this for the mplsLdpSessionTable, because objects in this
table may or may not be used in session establishment." table may or may not be used in session establishment."
::= { mplsLdpSesObjects 2 } ::= { mplsLdpSessionObjects 2 }
mplsLdpPeerEntry OBJECT-TYPE mplsLdpPeerEntry OBJECT-TYPE
SYNTAX MplsLdpPeerEntry SYNTAX MplsLdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single Peer which is related "Information about a single Peer which is related
to a Session. NOTE: this table is augmented by to a Session. This table is augmented by
the mplsLdpSessionTable." the mplsLdpSessionTable."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId } mplsLdpPeerLdpId }
::= { mplsLdpPeerTable 1 } ::= { mplsLdpPeerTable 1 }
MplsLdpPeerEntry ::= SEQUENCE { MplsLdpPeerEntry ::= SEQUENCE {
mplsLdpPeerLdpId MplsLdpIdentifier, mplsLdpPeerLdpId MplsLdpIdentifier,
mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod,
mplsLdpPeerPathVectorLimit Integer32, mplsLdpPeerPathVectorLimit Integer32,
skipping to change at page 33, line 26 skipping to change at page 33, line 38
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 0 (zero) then "If the value of this object is 0 (zero) then
Loop Dection for Path Vectors for this Peer Loop Dection for Path Vectors for this Peer
is disabled. is disabled.
Otherwise, if this object has a value greater than Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors for this zero, then Loop Dection for Path Vectors for this
Peer is enabled and the Path Vector Limit is this value." Peer is enabled and the Path Vector Limit is this value."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.8 Loop Dection, "RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV." Section 3.4.5 Path Vector TLV."
::= { mplsLdpPeerEntry 3 } ::= { mplsLdpPeerEntry 3 }
mplsLdpPeerTransportAddrType OBJECT-TYPE mplsLdpPeerTransportAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object specifies how to interpret the address "The type of the Internet address for the
for the mplsLdpPeerTransportAddr object." mplsLdpPeerTransportAddr object. The LDP
specification describes this as being either
an IPv4 Transport Address or IPv6 Transport
Address which is ued in opening the LDP session's
TCP connection, or if the optional TLV is not
present, then this is the IPv4/IPv6 source
address for the UPD packet carrying the Hellos."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.5.2 "RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures." Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 4 } ::= { mplsLdpPeerEntry 4 }
mplsLdpPeerTransportAddr OBJECT-TYPE mplsLdpPeerTransportAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport address advertized by the peer "The Internet address advertised by the peer
in the hello message or the Hello source address." in the hello message or the Hello source address.
The type of this address is determined by the
value of the mplsLdpPeerTransportAddrType
object."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.5.2 "RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures." Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 5 } ::= { mplsLdpPeerEntry 5 }
-- --
-- The MPLS LDP Sessions Table -- The MPLS LDP Sessions Table
-- --
mplsLdpSesTable OBJECT-TYPE mplsLdpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSesEntry SYNTAX SEQUENCE OF MplsLdpSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Sessions between the LDP Entities and "A table of Sessions between the LDP Entities and
LDP Peers. Each row represents a single session." LDP Peers. Each row represents a single session."
::= { mplsLdpSesObjects 3 } ::= { mplsLdpSessionObjects 3 }
mplsLdpSesEntry OBJECT-TYPE mplsLdpSessionEntry OBJECT-TYPE
SYNTAX MplsLdpSesEntry SYNTAX MplsLdpSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single session between an LDP Entity and LDP Peer. single session between an LDP Entity and LDP Peer.
The information contained in a row is read-only. The information contained in a row is read-only.
Please note: the Path Vector Limit for the Please note: the Path Vector Limit for the
Session is the value which is configured in Session is the value which is configured in
the corresponding mplsLdpEntityEntry. The the corresponding mplsLdpEntityEntry. The
Peer's Path Vector Limit is in noted in the Peer's Path Vector Limit is in the
mplsLdpPeerPathVectorLimit object in the
mplsLdpPeerTable. mplsLdpPeerTable.
Values which may differ from those configured are Values which may differ from those configured are
noted in the objects of this table, the noted in the objects of this table, the
mplsLdpAtmSesTable and the mplsLdpAtmSessionTable and the
mplsLdpFrameRelaySesTable. A value will mplsLdpFrameRelaySessionTable. A value will
differ if it was negotiated between the differ if it was negotiated between the
Entity and the Peer. Values may or may not Entity and the Peer. Values may or may not
be negotiated. For example, if the values be negotiated. For example, if the values
are the same then no negotiation takes place. are the same then no negotiation takes place.
If they are negotiated, then they may differ." If they are negotiated, then they may differ."
AUGMENTS { mplsLdpPeerEntry } AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSesTable 1 } ::= { mplsLdpSessionTable 1 }
MplsLdpSesEntry ::= SEQUENCE { MplsLdpSessionEntry ::= SEQUENCE {
mplsLdpSesStateLastChange TimeStamp, mplsLdpSessionStateLastChange TimeStamp,
mplsLdpSesState INTEGER, mplsLdpSessionState INTEGER,
mplsLdpSesRole INTEGER, mplsLdpSessionRole INTEGER,
mplsLdpSesProtocolVersion Unsigned32, mplsLdpSessionProtocolVersion Unsigned32,
mplsLdpSesKeepAliveHoldTimeRem TimeInterval, mplsLdpSessionKeepAliveHoldTimeRem TimeInterval,
mplsLdpSesKeepAliveTime Unsigned32, mplsLdpSessionKeepAliveTime Unsigned32,
mplsLdpSesMaxPduLength Unsigned32, mplsLdpSessionMaxPduLength Unsigned32,
mplsLdpSesDiscontinuityTime TimeStamp mplsLdpSessionDiscontinuityTime TimeStamp
} }
mplsLdpSesStateLastChange OBJECT-TYPE mplsLdpSessionStateLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this Session entered "The value of sysUpTime at the time this Session entered
its current state as denoted by the mplsLdpSesState object." its current state as denoted by the mplsLdpSessionState object."
::= { mplsLdpSesEntry 1 } ::= { mplsLdpSessionEntry 1 }
mplsLdpSesState OBJECT-TYPE mplsLdpSessionState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
nonexistent(1), nonexistent(1),
initialized(2), initialized(2),
openrec(3), openrec(3),
opensent(4), opensent(4),
operational(5) operational(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the session, all of the "The current state of the session, all of the
states 1 to 5 are based on the state machine for states 1 to 5 are based on the state machine for
session negotiation behavior." session negotiation behavior."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.5.4, "RFC3036, LDP Specification, Section 2.5.4,
Initialization State Machine." Initialization State Machine."
::= { mplsLdpSesEntry 2 } ::= { mplsLdpSessionEntry 2 }
mplsLdpSesRole OBJECT-TYPE mplsLdpSessionRole OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
active(2), active(2),
passive(3) passive(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"During session establishment the LSR takes either the "During session establishment the LSR/LER takes either the
active role or the passive role based on address active role or the passive role based on address
comparisons. This object indicates whether this LSR comparisons. This object indicates whether this LSR/LER
was behaving in an active role or passive role during was behaving in an active role or passive role during
this sessions establishment. this session's establishment.
The value of unknown(1), indicates that the role is not The value of unknown(1), indicates that the role is not
able to be determined at the present time." able to be determined at the present time."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.5.3., "RFC3036, LDP Specification, Section 2.5.3.,
Session Initialization" Session Initialization"
::= { mplsLdpSesEntry 3 } ::= { mplsLdpSessionEntry 3 }
mplsLdpSesProtocolVersion OBJECT-TYPE mplsLdpSessionProtocolVersion OBJECT-TYPE
SYNTAX Unsigned32(1..65535) SYNTAX Unsigned32(1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version of the LDP Protocol which "The version of the LDP Protocol which
this session is using. This is the version of this session is using. This is the version of
the LDP protocol which has been negotiated during the LDP protocol which has been negotiated during
session initialization." session initialization."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSesEntry 4 } ::= { mplsLdpSessionEntry 4 }
mplsLdpSesKeepAliveHoldTimeRem OBJECT-TYPE mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The keep alive hold time remaining for this session." "The keep alive hold time remaining for
::= { mplsLdpSesEntry 5 } this session."
::= { mplsLdpSessionEntry 5 }
mplsLdpSesKeepAliveTime OBJECT-TYPE mplsLdpSessionKeepAliveTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated KeepAlive Time. This value is "The negotiated KeepAlive Time which
negotiated during session initialization." represents the amount of seconds between
keep alive messages. The
mplsLdpEntityKeepAliveHoldTimer
related to this Session is the
value that was proposed as the
KeepAlive Time for this session.
This value is negotiated during
session initialization between
the entity's proposed value
(i.e. the value configured in
mplsLdpEntityKeepAliveHoldTimer)
and the peer's proposed
KeepAlive Hold Timer value.
This value is the smaller
of the two proposed values."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSesEntry 6 } ::= { mplsLdpSessionEntry 6 }
mplsLdpSessionMaxPduLength OBJECT-TYPE
mplsLdpSesMaxPduLength OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of maximum allowable length for LDP PDUs for "The value of maximum allowable length for LDP PDUs for
this session. This value may have been negotiated during this session. This value may have been negotiated during
the Session Initialization. This object is related to the Session Initialization. This object is related to
the mplsLdpEntityMaxPduLength object. The the mplsLdpEntityMaxPduLength object. The
mplsLdpEntityMaxPduLength object specifies the requested mplsLdpEntityMaxPduLength object specifies the requested
LDP PDU length, and this object reflects the negotiated LDP PDU length, and this object reflects the negotiated
LDP PDU length between the Entity and LDP PDU length between the Entity and
the Peer." the Peer."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSesEntry 7 } ::= { mplsLdpSessionEntry 7 }
mplsLdpSesDiscontinuityTime OBJECT-TYPE mplsLdpSessionDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which any one or more of this session's counters which any one or more of this session's counters
suffered a discontinuity. The relevant counters are suffered a discontinuity. The relevant counters are
the specific instances associated with this session the specific instances associated with this session
of any Counter32 or Counter64 object contained in the of any Counter32 or Counter64 object contained in the
mplsLdpSesStatsTable. mplsLdpSessionStatsTable.
The initial value of this object is the value of The initial value of this object is the value of
sysUpTime when the entry was created in this table. sysUpTime when the entry was created in this table.
Also, a command generator can distinguish when a session Also, a command generator can distinguish when a session
between a given Entity and Peer goes away and a new between a given Entity and Peer goes away and a new
session is established. This value would change and session is established. This value would change and
thus indicate to the command generator that this is a thus indicate to the command generator that this is a
different session." different session."
::= { mplsLdpSesEntry 8 } ::= { mplsLdpSessionEntry 8 }
-- --
-- The MPLS LDP Session Statistics Table -- The MPLS LDP Session Statistics Table
-- --
mplsLdpSessionStatsTable OBJECT-TYPE
mplsLdpSesStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry
SYNTAX SEQUENCE OF MplsLdpSesStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of statistics for Sessions between "A table of statistics for Sessions between
LDP Entities and LDP Peers." LDP Entities and LDP Peers."
::= { mplsLdpSesObjects 4 } ::= { mplsLdpSessionObjects 4 }
mplsLdpSesStatsEntry OBJECT-TYPE mplsLdpSessionStatsEntry OBJECT-TYPE
SYNTAX MplsLdpSesStatsEntry SYNTAX MplsLdpSessionStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents statistical "An entry in this table represents statistical
information on a single session between an LDP information on a single session between an LDP
Entity and LDP Peer." Entity and LDP Peer."
AUGMENTS { mplsLdpPeerEntry } AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSesStatsTable 1 } ::= { mplsLdpSessionStatsTable 1 }
MplsLdpSesStatsEntry ::= SEQUENCE { MplsLdpSessionStatsEntry ::= SEQUENCE {
mplsLdpSesStatsUnkMesTypeErrors Counter32, mplsLdpSessionStatsUnknownMesTypeErrors Counter32,
mplsLdpSesStatsUnkTlvErrors Counter32 mplsLdpSessionStatsUnknownTlvErrors Counter32
} }
mplsLdpSesStatsUnkMesTypeErrors OBJECT-TYPE mplsLdpSessionStatsUnknownMesTypeErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Unknown Message Type "This object counts the number of Unknown Message Type
Errors detected during this session. Errors detected during this session.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpSesDiscontinuityTime." mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSesStatsEntry 1 } ::= { mplsLdpSessionStatsEntry 1 }
mplsLdpSesStatsUnkTlvErrors OBJECT-TYPE
mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Unknown TLV Errors "This object counts the number of Unknown TLV Errors
detected during this session. detected during this session.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpSessionDiscontinuityTime." mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSesStatsEntry 2 } ::= { mplsLdpSessionStatsEntry 2 }
-- --
-- The MPLS LDP Hello Adjacency Table -- The MPLS LDP Hello Adjacency Table
-- --
mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::=
{ mplsLdpSesObjects 5 } { mplsLdpSessionObjects 5 }
mplsLdpHelloAdjacencyTable OBJECT-TYPE mplsLdpHelloAdjacencyTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Hello Adjacencies for Sessions." "A table of Hello Adjacencies for Sessions."
::= { mplsLdpHelloAdjacencyObjects 1 } ::= { mplsLdpHelloAdjacencyObjects 1 }
mplsLdpHelloAdjacencyEntry OBJECT-TYPE mplsLdpHelloAdjacencyEntry OBJECT-TYPE
skipping to change at page 40, line 18 skipping to change at page 41, line 10
mplsLdpHelloAdjacencyIndex OBJECT-TYPE mplsLdpHelloAdjacencyIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier for this specific adjacency." "An identifier for this specific adjacency."
::= { mplsLdpHelloAdjacencyEntry 1 } ::= { mplsLdpHelloAdjacencyEntry 1 }
mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time remaining for this Hello Adjacency. "If the value of this object is 65535,
this means that the hold time is infinite
(i.e. wait forever).
Otherwise, the time remaining for
this Hello Adjacency to receive its
next Hello message.
This interval will change when the 'next' This interval will change when the 'next'
Hello message which corresponds to this Hello message which corresponds to this
Hello Adjacency is received." Hello Adjacency is received unless it
is infinite."
::= { mplsLdpHelloAdjacencyEntry 2 } ::= { mplsLdpHelloAdjacencyEntry 2 }
mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Hello hold time which is negotiated between "The Hello hold time which is negotiated between
the Entity and the Peer. the Entity and the Peer. The entity associated
with this Hello Adjacency issues a proposed
Hello Hold Time value in the
mplsLdpEntityHelloHoldTimer object. The peer
also proposes a value and this object represents
the negotiated value.
A value of 0 means the default, A value of 0 means the default,
which is 15 seconds for Link Hellos and 45 seconds which is 15 seconds for Link Hellos
for Targeted Hellos. A value of 0xffff indicates an and 45 seconds for Targeted Hellos.
A value of 65535 indicates an
infinite hold time." infinite hold time."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.2 Hello Message" "RFC3036, LDP Specification, Section 3.5.2 Hello Message"
::= { mplsLdpHelloAdjacencyEntry 3 } ::= { mplsLdpHelloAdjacencyEntry 3 }
mplsLdpHelloAdjacencyType OBJECT-TYPE mplsLdpHelloAdjacencyType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
link(1), link(1),
targeted(2) targeted(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This adjacency is the result of a 'link' "This adjacency is the result of a 'link'
hello if the value of this object is link(1). hello if the value of this object is link(1).
skipping to change at page 41, line 29 skipping to change at page 42, line 36
-- --
mplsInSegmentLdpLspTable OBJECT-TYPE mplsInSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of LDP LSP's which "A table of LDP LSP's which
map to the InSegment Table in the map to the InSegment Table in the
the LSR MIB's." the LSR MIB's."
::= { mplsLdpSesObjects 6 } ::= { mplsLdpSessionObjects 6 }
mplsInSegmentLdpLspEntry OBJECT-TYPE mplsInSegmentLdpLspEntry OBJECT-TYPE
SYNTAX MplsInSegmentLdpLspEntry SYNTAX MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single LDP LSP which is represented by single LDP LSP which is represented by
a session's index triple (mplsLdpEntityLdpId, a session's index triple (mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the
skipping to change at page 43, line 14 skipping to change at page 44, line 22
-- --
-- Session Label (LSP) Mapping to LSR MIB's Out Segment LIB Information. -- Session Label (LSP) Mapping to LSR MIB's Out Segment LIB Information.
-- --
mplsOutSegmentLdpLspTable OBJECT-TYPE mplsOutSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of LDP LSP's which "A table of LDP LSP's which
map to the InSegment Table in the map to the mplsOutSegmentTable in the
the LSR MIB's." the LSR MIB."
::= { mplsLdpSesObjects 7 } ::= { mplsLdpSessionObjects 7 }
mplsOutSegmentLdpLspEntry OBJECT-TYPE mplsOutSegmentLdpLspEntry OBJECT-TYPE
SYNTAX MplsOutSegmentLdpLspEntry SYNTAX MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single LDP LSP which is represented by single LDP LSP which is represented by
a session's index triple (mplsLdpEntityLdpId, a session's index triple (mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the
skipping to change at page 44, line 44 skipping to change at page 46, line 8
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of LSP connection." "The type of LSP connection."
::= { mplsOutSegmentLdpLspEntry 4 } ::= { mplsOutSegmentLdpLspEntry 4 }
-- --
-- Mpls FEC Table -- Mpls FEC Table
-- --
mplsFecObjects OBJECT IDENTIFIER ::= mplsFecObjects OBJECT IDENTIFIER ::=
{ mplsLdpSesObjects 8 } { mplsLdpSessionObjects 8 }
mplsFecIndexNext OBJECT-TYPE mplsFecIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to "This object contains an appropriate value to
be used for mplsFecIndex when creating be used for mplsFecIndex when creating
entries in the mplsFecTable. The value entries in the mplsFecTable. The value
0 indicates that no unassigned entries are 0 indicates that no unassigned entries are
skipping to change at page 46, line 19 skipping to change at page 47, line 29
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the FEC. If the value of this object "The type of the FEC. If the value of this object
is 'prefix(1)' then the FEC type described by this is 'prefix(1)' then the FEC type described by this
row is for address prefixes. row is for address prefixes.
If the value of this object is 'hostAddress(2)' then If the value of this object is 'hostAddress(2)' then
the FEC type described by this row is a host address." the FEC type described by this row is a host address."
REFERENCE REFERENCE
"[RFC3036], Section 3.4.1. FEC TLV." "RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 2 } ::= { mplsFecEntry 2 }
mplsFecAddrPrefixLength OBJECT-TYPE mplsFecAddrPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of the 'mplsFecType' is 'hostAddress(2)' "If the value of the 'mplsFecType' is 'hostAddress(2)'
then this object is undefined. then this object is undefined.
If the value of 'mplsFecType' is 'prefix(1)' If the value of 'mplsFecType' is 'prefix(1)'
then the value of this object is the length in then the value of this object is the length in
bits of the address prefix represented by bits of the address prefix represented by
'mplsFecAddr', or zero. If the value of this 'mplsFecAddr', or zero. If the value of this
object is zero, this indicates that the object is zero, this indicates that the
prefix matches all addresses. In this case the prefix matches all addresses. In this case the
prefix MUST also be zero (i.e. 'mplsFecAddr' will prefix MUST also be zero (i.e. 'mplsFecAddr' will
have the value of zero.)" have the value of zero.)"
REFERENCE REFERENCE
"[RFC3036], Section 3.4.1. FEC TLV." "RFC3036, Section 3.4.1. FEC TLV."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsFecEntry 3 } ::= { mplsFecEntry 3 }
mplsFecAddrFamily OBJECT-TYPE mplsFecAddrFamily OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is the type of the address. The "The value of this object is the type of the address. The
type of the address should then be looked up in the type of the address should then be looked up in the
ADDRESS FAMILY NUMBERS [RFC1700] for the corresponding entry ADDRESS FAMILY NUMBERS [RFC1700] for the corresponding entry
there and this value should be encoded in the FEC TLV." there and this value should be encoded in the FEC TLV."
REFERENCE REFERENCE
"[RFC3036], Section 3.4.1. FEC TLV." "RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 4 } ::= { mplsFecEntry 4 }
mplsFecAddr OBJECT-TYPE mplsFecAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is the an address where the "The value of this object is the an address where the
address type is specified by the 'mplsFecAddrFamily' object. address type is specified by the 'mplsFecAddrFamily' object.
This address is then used as either an address prefix, This address is then used as either an address prefix,
or as the host address as indicated by the 'mplsFecType' or as the host address as indicated by the 'mplsFecType'
object. In other words, the FEC element is populated object. In other words, the FEC element is populated
according to the Prefix FEC Element value encoding, or according to the Prefix FEC Element value encoding, or
the Host Address FEC Element encoding." the Host Address FEC Element encoding."
REFERENCE REFERENCE
"[RFC3036], Section 3.4.1 FEC TLV." "RFC3036, Section 3.4.1 FEC TLV."
::= { mplsFecEntry 5 } ::= { mplsFecEntry 5 }
mplsFecStorageType OBJECT-TYPE mplsFecStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to Conceptual rows having the value 'permanent(4)'
any columnar objects in the row, except for setting the need not allow write-access to any columnar
'mplsFecRowStatus' to 'destroy(6)'." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsFecEntry 6 } ::= { mplsFecEntry 6 }
mplsFecRowStatus OBJECT-TYPE mplsFecRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. If the value of this "The status of this conceptual row. If the value of this
object is 'active(1)', then none of the writable objects of object is 'active(1)', then none of the writable objects of
skipping to change at page 48, line 20 skipping to change at page 49, line 30
-- --
mplsLdpLspFecTable OBJECT-TYPE mplsLdpLspFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpLspFecEntry SYNTAX SEQUENCE OF MplsLdpLspFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table which shows the relationship between "A table which shows the relationship between
LDP LSP's and FECs. Each row represents LDP LSP's and FECs. Each row represents
a single LSP to FEC association." a single LSP to FEC association."
::= { mplsLdpSesObjects 9 } ::= { mplsLdpSessionObjects 9 }
mplsLdpLspFecEntry OBJECT-TYPE mplsLdpLspFecEntry OBJECT-TYPE
SYNTAX MplsLdpLspFecEntry SYNTAX MplsLdpLspFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry represents a LDP LSP "An entry represents a LDP LSP
to FEC association." to FEC association."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
skipping to change at page 50, line 8 skipping to change at page 51, line 19
or the mplsOutSegmentLdpLspLabel as indicated by or the mplsOutSegmentLdpLspLabel as indicated by
the mplsLdpLspFecSegment." the mplsLdpLspFecSegment."
::= { mplsLdpLspFecEntry 3 } ::= { mplsLdpLspFecEntry 3 }
mplsLdpLspFecIndex OBJECT-TYPE mplsLdpLspFecIndex OBJECT-TYPE
SYNTAX IndexInteger SYNTAX IndexInteger
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index identifies the FEC entry in the "This index identifies the FEC entry in the
mplsFecTable associated with this Session. mplsFecTable associated with this session.
In other words, the value of this index In other words, the value of this index
is the same as the value of the mplsFecIndex is the same as the value of the mplsFecIndex
that denotes the FEC associated with this that denotes the FEC associated with this
Session." Session."
::= { mplsLdpLspFecEntry 4 } ::= { mplsLdpLspFecEntry 4 }
mplsLdpLspFecOperStatus OBJECT-TYPE mplsLdpLspFecOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
inUse(2), inUse(2),
skipping to change at page 51, line 8 skipping to change at page 52, line 20
DESCRIPTION DESCRIPTION
"This value of sysUpTime at the time of the most recent "This value of sysUpTime at the time of the most recent
change to the mplsLdpLspFecOperStatus object." change to the mplsLdpLspFecOperStatus object."
::= { mplsLdpLspFecEntry 6 } ::= { mplsLdpLspFecEntry 6 }
mplsLdpLspFecStorageType OBJECT-TYPE mplsLdpLspFecStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to Conceptual rows having the value 'permanent(4)'
any columnar objects in the row, except for setting the need not allow write-access to any columnar
mplsLdpLspFecRowStatus' to 'destroy(6)'." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpLspFecEntry 7 } ::= { mplsLdpLspFecEntry 7 }
mplsLdpLspFecRowStatus OBJECT-TYPE mplsLdpLspFecRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. If the value of this "The status of this conceptual row. If the
object is 'active(1)', then none of the writable objects of value of this object is 'active(1)', then
this entry can be modified. none of the writable objects of this entry
can be modified.
The Agent should delete this row when the Session ceases to The Agent should delete this row when
exist. If an operator wants to associate the session with the session ceases to exist. If an
operator wants to associate the session with
a different FEC, the recommended a different FEC, the recommended
procedure is (as described in detail in the section procedure is (as described in detail in the section
entitled, 'Changing Values After Session entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object) DESCRIPTION clause of the
is to set the mplsLdpEntityAdminStatus to down, thereby mplsLdpEntityAdminStatus object)
explicitly causing a session to be torn down. This will also is to set the mplsLdpEntityAdminStatus to
down, thereby explicitly causing a session
to be torn down. This will also
cause this entry to be deleted. cause this entry to be deleted.
Then, set the mplsLdpEntityAdminStatus Then, set the mplsLdpEntityAdminStatus
to enable which enables a NEW session to be initiated. to enable which enables a new session to be initiated.
Once the session is initiated, an entry may be added to this Once the session is initiated, an entry may be added to this
table to associate the new session with a FEC." table to associate the new session with a FEC."
::= { mplsLdpLspFecEntry 8 } ::= { mplsLdpLspFecEntry 8 }
-- --
-- Address Message/Address Withdraw Message Information -- Address Message/Address Withdraw Message Information
-- --
-- This information is associated with a specific Session -- This information is associated with a specific Session
-- because Label Address Messages are sent after session -- because Label Address Messages are sent after session
-- initialization has taken place. -- initialization has taken place.
-- --
mplsLdpSesPeerAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSesPeerAddrEntry mplsLdpSessionPeerAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table 'extends' the mplsLdpSessionTable. "This table 'extends' the mplsLdpSessionTable.
This table is used to store Label Address Information This table is used to store Label Address Information
from Label Address Messages received by this LSR from from Label Address Messages received by this LSR from
Peers. This table is read-only and should be updated Peers. This table is read-only and should be updated
when Label Withdraw Address Messages are received, i.e. when Label Withdraw Address Messages are received, i.e.
Rows should be deleted as apropriate. Rows should be deleted as apropriate.
NOTE: since more than one address may be contained NOTE: since more than one address may be contained
in a Label Address Message, this table 'extends', in a Label Address Message, this table 'extends',
rather than 'AUGMENTS' the mplsLdpSessionTable's rather than 'AUGMENTS' the mplsLdpSessionTable's
information." information."
::= { mplsLdpSesObjects 10 } ::= { mplsLdpSessionObjects 10 }
mplsLdpSesPeerAddrEntry OBJECT-TYPE mplsLdpSessionPeerAddrEntry OBJECT-TYPE
SYNTAX MplsLdpSesPeerAddrEntry SYNTAX MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on "An entry in this table represents information on
a session's single next hop address which was a session's single next hop address which was
advertised in an Address Message from the LDP peer. advertised in an Address Message from the LDP peer.
The information contained in a row is read-only." The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpSesPeerAddrIndex mplsLdpSessionPeerAddrIndex
} }
::= { mplsLdpSesPeerAddrTable 1 } ::= { mplsLdpSessionPeerAddrTable 1 }
MplsLdpSesPeerAddrEntry ::= SEQUENCE { MplsLdpSessionPeerAddrEntry ::= SEQUENCE {
mplsLdpSesPeerAddrIndex Unsigned32, mplsLdpSessionPeerAddrIndex Unsigned32,
mplsLdpSesPeerNextHopAddrType InetAddressType, mplsLdpSessionPeerNextHopAddrType InetAddressType,
mplsLdpSesPeerNextHopAddr InetAddress mplsLdpSessionPeerNextHopAddr InetAddress
} }
mplsLdpSesPeerAddrIndex OBJECT-TYPE mplsLdpSessionPeerAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index which uniquely identifies this entry within "An index which uniquely identifies this entry within
a given session." a given session."
::= { mplsLdpSesPeerAddrEntry 1 } ::= { mplsLdpSessionPeerAddrEntry 1 }
mplsLdpSesPeerNextHopAddrType OBJECT-TYPE mplsLdpSessionPeerNextHopAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The internetwork layer address type of this Next Hop "The internetwork layer address type of this Next Hop
Address as specified in the Label Address Message Address as specified in the Label Address Message
associated with this Session. The value of this associated with this Session. The value of this
object indicates how to interpret the value of object indicates how to interpret the value of
mplsLdpSesPeerNextHopAddress." mplsLdpSessionPeerNextHopAddr."
::= { mplsLdpSesPeerAddrEntry 2 } ::= { mplsLdpSessionPeerAddrEntry 2 }
mplsLdpSesPeerNextHopAddr OBJECT-TYPE mplsLdpSessionPeerNextHopAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the next hop address." "The value of the next hop address."
REFERENCE REFERENCE
"[RFC3036], Section 2.7. LDP Identifiers and Next Hop Addresses" "RFC3036, Section 2.7. LDP Identifiers
::= { mplsLdpSesPeerAddrEntry 3 } and Next Hop Addresses"
::= { mplsLdpSessionPeerAddrEntry 3 }
--- ---
--- Notifications --- Notifications
--- ---
mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE
mplsLdpInitSesThresholdExceeded NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpEntityInitSesThreshold mplsLdpEntityInitSessionThreshold
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the value of "This notification is generated when the value of
the 'mplsLdpEntityInitSesThreshold' object the 'mplsLdpEntityInitSessionThreshold' object
is not zero, and the number of Session is not zero, and the number of Session
Initialization messages exceeds the value Initialization messages exceeds the value
of the 'mplsLdpEntityInitSesThreshold' object." of the 'mplsLdpEntityInitSessionThreshold' object."
::= { mplsLdpNotifications 1 } ::= { mplsLdpNotifications 1 }
mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpEntityPathVectorLimit, mplsLdpEntityPathVectorLimit,
mplsLdpPeerPathVectorLimit mplsLdpPeerPathVectorLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this notification is enabled to generated, "This notification is sent when the
then this notification is sent when the
'mplsLdpEntityPathVectorLimit' does NOT match 'mplsLdpEntityPathVectorLimit' does NOT match
the value of the 'mplsLdpPeerPathVectorLimit' for the value of the 'mplsLdpPeerPathVectorLimit' for
a specific Entity." a specific Entity."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 3.5.3." "RFC3036, LDP Specification, Section 3.5.3."
::= { mplsLdpNotifications 2 } ::= { mplsLdpNotifications 2 }
mplsLdpSesUp NOTIFICATION-TYPE mplsLdpSessionUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpSesState, mplsLdpSessionState,
mplsLdpSesDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSesStatsUnkMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSesStatsUnkTlvErrors mplsLdpSessionStatsUnknownTlvErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this notification is enabled to generated, "If this notification is enabled to generated,
then this notification is sent when the then this notification is sent when the
value of 'mplsLdpSesState' enters value of 'mplsLdpSessionState' enters
the 'operational(5)' state." the 'operational(5)' state."
::= { mplsLdpNotifications 3 } ::= { mplsLdpNotifications 3 }
mplsLdpSesDown NOTIFICATION-TYPE mplsLdpSessionDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpSesState, mplsLdpSessionState,
mplsLdpSesDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSesStatsUnkMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSesStatsUnkTlvErrors mplsLdpSessionStatsUnknownTlvErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this notification is enabled to generated, "This notification is sent when the
then this notification is sent when the the value of 'mplsLdpSessionState' leaves
the value of 'mplsLdpSesState' leaves
the 'operational(5)' state." the 'operational(5)' state."
::= { mplsLdpNotifications 4 } ::= { mplsLdpNotifications 4 }
--**************************************************************** --****************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--**************************************************************** --****************************************************************
mplsLdpGroups mplsLdpGroups
OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } OBJECT IDENTIFIER ::= { mplsLdpConformance 1 }
skipping to change at page 56, line 45 skipping to change at page 58, line 14
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Support for createAndWait and notInService is not "Support for createAndWait and notInService is not
required. Also, the entries in this table may be required. Also, the entries in this table may be
created by the agent, so strictly speaking created by the agent, so strictly speaking
read-create functionality is not necessary, but read-create functionality is not necessary, but
may be nice to have." may be nice to have."
OBJECT mplsLdpSesPeerNextHopAddrType OBJECT mplsLdpSessionPeerNextHopAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"An implementation is only required to support "An implementation is only required to support
'unknown(0)', IPv4 and globally unique IPv6 addresses." 'unknown(0)', IPv4 and globally unique IPv6 addresses."
OBJECT mplsLdpSesPeerNextHopAddr
OBJECT mplsLdpSessionPeerNextHopAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"An implementation is only required to support IPv4 "An implementation is only required to support IPv4
and globally unique IPv6 addresses." and globally unique IPv6 addresses."
::= { mplsLdpCompliances 1 } ::= { mplsLdpCompliances 1 }
-- --
-- Read-Only Compliance -- Read-Only Compliance
-- --
skipping to change at page 58, line 26 skipping to change at page 59, line 42
OBJECT mplsLdpEntityKeepAliveHoldTimer OBJECT mplsLdpEntityKeepAliveHoldTimer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityHelloHoldTimer OBJECT mplsLdpEntityHelloHoldTimer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityInitSesThreshold OBJECT mplsLdpEntityInitSessionThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityLabelDistMethod OBJECT mplsLdpEntityLabelDistMethod
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityLabelRetentionMode OBJECT mplsLdpEntityLabelRetentionMode
skipping to change at page 61, line 8 skipping to change at page 62, line 23
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpLspFecRowStatus OBJECT mplsLdpLspFecRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and active is the "Write access is not required, and active is the
only status that needs to be supported." only status that needs to be supported."
OBJECT mplsLdpSesPeerNextHopAddrType OBJECT mplsLdpSessionPeerNextHopAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"An implementation is only required to support "An implementation is only required to support
'unknown(0)', IPv4 and globally unique IPv6 addresses." 'unknown(0)', IPv4 and globally unique IPv6 addresses."
OBJECT mplsLdpSesPeerNextHopAddr OBJECT mplsLdpSessionPeerNextHopAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"An implementation is only required to support IPv4 "An implementation is only required to support IPv4
and globally unique IPv6 addresses." and globally unique IPv6 addresses."
::= { mplsLdpCompliances 2 } ::= { mplsLdpCompliances 2 }
-- units of conformance -- units of conformance
mplsLdpGeneralGroup OBJECT-GROUP mplsLdpGeneralGroup OBJECT-GROUP
skipping to change at page 61, line 38 skipping to change at page 63, line 10
mplsLdpEntityLastChange, mplsLdpEntityLastChange,
mplsLdpEntityIndexNext, mplsLdpEntityIndexNext,
mplsLdpEntityProtocolVersion, mplsLdpEntityProtocolVersion,
mplsLdpEntityAdminStatus, mplsLdpEntityAdminStatus,
mplsLdpEntityOperStatus, mplsLdpEntityOperStatus,
mplsLdpEntityTcpDscPort, mplsLdpEntityTcpDscPort,
mplsLdpEntityUdpDscPort, mplsLdpEntityUdpDscPort,
mplsLdpEntityMaxPduLength, mplsLdpEntityMaxPduLength,
mplsLdpEntityKeepAliveHoldTimer, mplsLdpEntityKeepAliveHoldTimer,
mplsLdpEntityHelloHoldTimer, mplsLdpEntityHelloHoldTimer,
mplsLdpEntityInitSesThreshold, mplsLdpEntityInitSessionThreshold,
mplsLdpEntityLabelDistMethod, mplsLdpEntityLabelDistMethod,
mplsLdpEntityLabelRetentionMode, mplsLdpEntityLabelRetentionMode,
mplsLdpEntityPathVectorLimit, mplsLdpEntityPathVectorLimit,
mplsLdpEntityHopCountLimit, mplsLdpEntityHopCountLimit,
mplsLdpEntityTransportAddrKind, mplsLdpEntityTransportAddrKind,
mplsLdpEntityTargetPeer, mplsLdpEntityTargetPeer,
mplsLdpEntityTargetPeerAddrType, mplsLdpEntityTargetPeerAddrType,
mplsLdpEntityTargetPeerAddr, mplsLdpEntityTargetPeerAddr,
mplsLdpEntityLabelType, mplsLdpEntityLabelType,
mplsLdpEntityDiscontinuityTime, mplsLdpEntityDiscontinuityTime,
mplsLdpEntityStorageType, mplsLdpEntityStorageType,
mplsLdpEntityRowStatus, mplsLdpEntityRowStatus,
mplsLdpEntityStatsSesAttempts, mplsLdpEntityStatsSessionAttempts,
mplsLdpEntityStatsSesRejectedNoHelloErrors, mplsLdpEntityStatsSessionRejectedNoHelloErrors,
mplsLdpEntityStatsSesRejectedAdErrors, mplsLdpEntityStatsSessionRejectedAdErrors,
mplsLdpEntityStatsSesRejectedMaxPduErrors, mplsLdpEntityStatsSessionRejectedMaxPduErrors,
mplsLdpEntityStatsSesRejectedLRErrors, mplsLdpEntityStatsSessionRejectedLRErrors,
mplsLdpEntityStatsBadLdpIdentifierErrors, mplsLdpEntityStatsBadLdpIdentifierErrors,
mplsLdpEntityStatsBadPduLengthErrors, mplsLdpEntityStatsBadPduLengthErrors,
mplsLdpEntityStatsBadMessageLengthErrors, mplsLdpEntityStatsBadMessageLengthErrors,
mplsLdpEntityStatsBadTlvLengthErrors, mplsLdpEntityStatsBadTlvLengthErrors,
mplsLdpEntityStatsMalformedTlvValueErrors, mplsLdpEntityStatsMalformedTlvValueErrors,
mplsLdpEntityStatsKeepAliveTimerExpErrors, mplsLdpEntityStatsKeepAliveTimerExpErrors,
mplsLdpEntityStatsShutdownReceivedNotifications, mplsLdpEntityStatsShutdownReceivedNotifications,
mplsLdpEntityStatsShutdownSentNotifications, mplsLdpEntityStatsShutdownSentNotifications,
mplsLdpPeerLastChange, mplsLdpPeerLastChange,
mplsLdpPeerLabelDistMethod, mplsLdpPeerLabelDistMethod,
mplsLdpPeerPathVectorLimit, mplsLdpPeerPathVectorLimit,
mplsLdpPeerTransportAddrType, mplsLdpPeerTransportAddrType,
mplsLdpPeerTransportAddr, mplsLdpPeerTransportAddr,
mplsLdpHelloAdjacencyHoldTimeRem, mplsLdpHelloAdjacencyHoldTimeRem,
mplsLdpHelloAdjacencyHoldTime, mplsLdpHelloAdjacencyHoldTime,
mplsLdpHelloAdjacencyType, mplsLdpHelloAdjacencyType,
mplsLdpSesStateLastChange, mplsLdpSessionStateLastChange,
mplsLdpSesState, mplsLdpSessionState,
mplsLdpSesRole, mplsLdpSessionRole,
mplsLdpSesProtocolVersion, mplsLdpSessionProtocolVersion,
mplsLdpSesKeepAliveHoldTimeRem, mplsLdpSessionKeepAliveHoldTimeRem,
mplsLdpSesKeepAliveTime, mplsLdpSessionKeepAliveTime,
mplsLdpSesMaxPduLength, mplsLdpSessionMaxPduLength,
mplsLdpSesDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSesStatsUnkMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSesStatsUnkTlvErrors, mplsLdpSessionStatsUnknownTlvErrors,
mplsLdpSesPeerNextHopAddrType, mplsLdpSessionPeerNextHopAddrType,
mplsLdpSesPeerNextHopAddr, mplsLdpSessionPeerNextHopAddr,
mplsFecIndexNext, mplsFecIndexNext,
mplsFecType, mplsFecType,
mplsFecAddrPrefixLength, mplsFecAddrPrefixLength,
mplsFecAddrFamily, mplsFecAddrFamily,
mplsFecAddr, mplsFecAddr,
mplsFecStorageType, mplsFecStorageType,
mplsFecRowStatus mplsFecRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 63, line 20 skipping to change at page 64, line 36
mplsInSegmentLdpLspType, mplsInSegmentLdpLspType,
mplsOutSegmentLdpLspLabelType, mplsOutSegmentLdpLspLabelType,
mplsOutSegmentLdpLspType, mplsOutSegmentLdpLspType,
mplsLdpLspFecOperStatus, mplsLdpLspFecOperStatus,
mplsLdpLspFecLastChange, mplsLdpLspFecLastChange,
mplsLdpLspFecStorageType, mplsLdpLspFecStorageType,
mplsLdpLspFecRowStatus mplsLdpLspFecRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are optional and only need to be supported "These objects are for LDP implementations
for LDP implementations which support the following which interface to the Label Information Base (LIB)
tables in the LSR MIB: mplsInSegmentTable, in the MPLS-LSR-STD-MIB. The LIB is
represented in the mplsInSegmentTable,
mplsOutSegmentTable and mplsXCTable." mplsOutSegmentTable and mplsXCTable."
::= { mplsLdpGroups 2 } ::= { mplsLdpGroups 2 }
mplsLdpNotificationsGroup NOTIFICATION-GROUP mplsLdpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsLdpInitSesThresholdExceeded, NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded,
mplsLdpPathVectorLimitMismatch, mplsLdpPathVectorLimitMismatch,
mplsLdpSesUp, mplsLdpSessionUp,
mplsLdpSesDown mplsLdpSessionDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification(s) which an MPLS LDP implemention "The notification for an MPLS LDP implemention."
is required to implement."
::= { mplsLdpGroups 3 } ::= { mplsLdpGroups 3 }
END END
4.1. The MPLS-LDP-ATM-MIB Module 4.1. The MPLS-LDP-ATM-STD-MIB Module
This MIB Module MUST be supported if LDP uses ATM as the Layer 2 This MIB Module MUST be supported if LDP uses ATM as the Layer 2
media. There are three tables in this MIB Module. Two tables are media. There are three tables in this MIB Module. Two tables are
for configuring LDP to use ATM. These tables are the for configuring LDP to use ATM. These tables are the
mplsLdpEntityAtmParmsTable and the mplsLdpEntityAtmLabelRangeTable. mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable.
The mplsLdpEntityAtmParmsTable provides a way to configure The mplsLdpEntityAtmTable provides a way to configure information
information which would be contained in the "Optional Parameter" which would be contained in the "Optional Parameter" portion of an
portion of an LDP PDU Initialization Message. LDP PDU Initialization Message.
The mplsLdpEntityAtmLabelRangeTable provides a way to configure The mplsLdpEntityAtmLRTable provides a way to configure information
information which would be contained in the "ATM Label Range which would be contained in the "ATM Label Range Components" portion
Components" portion of an LDP PDU Intialization Message, see of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036].
[RFC3035] and [RFC3036].
4.1.1. The LDP ATM Session Table 4.1.1. The LDP ATM Session Table
The MPLS LDP ATM Session Table is a read-only table which contains The MPLS LDP ATM Session Table is a read-only table which contains
session information specific to ATM. session information specific to ATM.
MPLS-LDP-ATM-MIB DEFINITIONS ::= BEGIN MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB FROM ATM-TC-MIB
mplsMIB, mplsStdMIB,
MplsAtmVcIdentifier MplsAtmVcIdentifier
FROM MPLS-TC-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpAtmMIB MODULE-IDENTITY mplsLdpAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200304221200Z" -- 22 April 2003 LAST-UPDATED "200306091200Z" -- 9 June 2003
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@artel.com)
Artel Artel
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
skipping to change at page 65, line 38 skipping to change at page 67, line 8
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2
media." media."
REVISION "200304221200Z" -- 22 April 2003 REVISION "200306091200Z" -- 9 June 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section -- Please see the IANA Considerations Section
-- the suggested mplsMIB subId is 5, e.g. -- the suggested mplsStdMIB subId is 5, e.g.
-- ::= { mplsMIB 5 } -- ::= { mplsStdMIB 5 }
::= { mplsMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpAtmObjects OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 1 }
mplsLdpAtmConformance OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 2 } mplsLdpAtmObjects OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 1 }
mplsLdpAtmConformance OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP ATM Objects -- MPLS LDP ATM Objects
--**************************************************************** --****************************************************************
-- --
-- Ldp Entity Objects for ATM -- Ldp Entity Objects for ATM
-- --
mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 1 } { mplsLdpAtmObjects 1 }
mplsLdpEntityAtmTable OBJECT-TYPE mplsLdpEntityAtmTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the "This table contains information about the
ATM specific information which could be used ATM specific information which could be used
in the 'Optional Parameters' and other ATM specific in the 'Optional Parameters' and other ATM
information. specific information.
This table 'extends' the mplsLdpEntityTable when This table 'sparse augments' the mplsLdpEntityTable
ATM as the Layer 2 media." when ATM as the Layer 2 media."
::= { mplsLdpEntityAtmObjects 1 } ::= { mplsLdpEntityAtmObjects 1 }
mplsLdpEntityAtmEntry OBJECT-TYPE mplsLdpEntityAtmEntry OBJECT-TYPE
SYNTAX MplsLdpEntityAtmEntry SYNTAX MplsLdpEntityAtmEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents the ATM parameters "An entry in this table represents the ATM parameters
and ATM information for this LDP entity." and ATM information for this LDP entity."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex mplsLdpEntityIndex
} }
skipping to change at page 68, line 31 skipping to change at page 69, line 48
- Non-merge and VC-merge LSRs may freely interoperate. - Non-merge and VC-merge LSRs may freely interoperate.
- The interoperability of VP-merge-capable switches with non- - The interoperability of VP-merge-capable switches with non-
VP-merge-capable switches is a subject for future study. VP-merge-capable switches is a subject for future study.
When the LSRs differ on the use of VP-merge, the session is When the LSRs differ on the use of VP-merge, the session is
established, but VP merge is not used.' established, but VP merge is not used.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityAtmEntry 2 } ::= { mplsLdpEntityAtmEntry 2 }
mplsLdpEntityAtmLRComponents OBJECT-TYPE mplsLdpEntityAtmLRComponents OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of Label Range Components in the Initialization "Number of Label Range Components in the Initialization
message. This also represents the number of entries message. This also represents the number of entries
in the mplsLdpEntityAtmLRTable which correspond in the mplsLdpEntityAtmLRTable which correspond
skipping to change at page 69, line 12 skipping to change at page 70, line 30
The description from rfc3036.txt is: The description from rfc3036.txt is:
'N, Number of label range components 'N, Number of label range components
Specifies the number of ATM Label Range Components Specifies the number of ATM Label Range Components
included in the TLV.' included in the TLV.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityAtmEntry 3 } ::= { mplsLdpEntityAtmEntry 3 }
mplsLdpEntityAtmVcDirectionality OBJECT-TYPE mplsLdpEntityAtmVcDirectionality OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bidirectional(0), bidirectional(0),
unidirectional(1) unidirectional(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 70, line 4 skipping to change at page 71, line 22
specifies unidirectional VC capability, meaning (within a given specifies unidirectional VC capability, meaning (within a given
VPI) a given VCI may appear in a label mapping for one VPI) a given VCI may appear in a label mapping for one
direction on the link only. When either or both of the peers direction on the link only. When either or both of the peers
specifies unidirectional VC capability, both LSRs use specifies unidirectional VC capability, both LSRs use
unidirectional VC label assignment for the link as follows. unidirectional VC label assignment for the link as follows.
The LSRs compare their LDP Identifiers as unsigned integers. The LSRs compare their LDP Identifiers as unsigned integers.
The LSR with the larger LDP Identifier may assign only odd- The LSR with the larger LDP Identifier may assign only odd-
numbered VCIs in the VPI/VCI range as labels. The system with numbered VCIs in the VPI/VCI range as labels. The system with
the smaller LDP Identifier may assign only even-numbered VCIs the smaller LDP Identifier may assign only even-numbered VCIs
in the VPI/VCI range as labels.' in the VPI/VCI range as labels.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityAtmEntry 4 } ::= { mplsLdpEntityAtmEntry 4 }
mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
direct(1), direct(1),
indirect(2) indirect(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 71, line 34 skipping to change at page 73, line 8
value of the 'mplsLdpEntityAtmDefaultControlVci', however value of the 'mplsLdpEntityAtmDefaultControlVci', however
another value may be configured." another value may be configured."
DEFVAL { 32 } DEFVAL { 32 }
::= { mplsLdpEntityAtmEntry 9 } ::= { mplsLdpEntityAtmEntry 9 }
mplsLdpEntityAtmStorageType OBJECT-TYPE mplsLdpEntityAtmStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row, except for setting the need not allow write-access to any columnar
mplsLdpEntityAtmRowStatus to 'destroy(6)'." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmEntry 10 } ::= { mplsLdpEntityAtmEntry 10 }
mplsLdpEntityAtmRowStatus OBJECT-TYPE mplsLdpEntityAtmRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any time,
detail in the section entitled, 'Changing Values After Session however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, DESCRIPTION clause of the mplsLdpEntityAdminStatus
if a session has been initiated with a Peer, object, if a session has been initiated with a Peer,
changing objects in this table will changing objects in this table will wreak havoc
wreak havoc with the session and interrupt traffic. To repeat again: with the session and interrupt traffic. To repeat again:
the recommended procedure is to set the mplsLdpEntityAdminStatus to the recommended procedure is to set the
down, thereby explicitely causing a session to be torn down. Then, mplsLdpEntityAdminStatus to down, thereby explicitly
change objects in this entry, then set the mplsLdpEntityAdminStatus causing a session to be torn down. Then,
to enable which enables a NEW session to be initiated. change objects in this entry, then set the
mplsLdpEntityAdminStatus to enable
NOTE: This RowStatus object should which enables a new session to be initiated."
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry."
::= { mplsLdpEntityAtmEntry 11 } ::= { mplsLdpEntityAtmEntry 11 }
-- --
-- The MPLS LDP Entity ATM Label Range Table -- The MPLS LDP Entity ATM Label Range Table
-- --
mplsLdpEntityAtmLRTable OBJECT-TYPE mplsLdpEntityAtmLRTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MPLS LDP Entity ATM Label Range (LR) Table. "The MPLS LDP Entity ATM Label Range (LR) Table.
The purpose of this table is to provide a mechanism The purpose of this table is to provide a mechanism
for configuring a contiguous range of vpi's for configuring a contiguous range of vpi's
with a contiguous range of vci's, or a 'label range' with a contiguous range of vci's, or a 'label range'
for LDP Entities. for LDP Entities.
LDP Entities which use ATM must have at least one LDP Entities which use ATM must have at least one
entry in this table." entry in this table.
There must exist at least one entry in this
table for every LDP Entity that has
'mplsLdpEntityOptionalParameters' object with
a value of 'atmSessionParameters'."
::= { mplsLdpEntityAtmObjects 2 } ::= { mplsLdpEntityAtmObjects 2 }
mplsLdpEntityAtmLREntry OBJECT-TYPE mplsLdpEntityAtmLREntry OBJECT-TYPE
SYNTAX MplsLdpEntityAtmLREntry SYNTAX MplsLdpEntityAtmLREntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in the LDP Entity ATM Label "A row in the LDP Entity ATM Label
Range Table. One entry in this table contains Range Table. One entry in this table contains
information on a single range of labels information on a single range of labels
skipping to change at page 73, line 23 skipping to change at page 74, line 47
range overlaps with the second entry (i.e. both range overlaps with the second entry (i.e. both
entries now have 0/200). entries now have 0/200).
A row will not be created unless a unique and A row will not be created unless a unique and
non-overlapping range is specified. Thus, row non-overlapping range is specified. Thus, row
creation implies a one-shot row creation of creation implies a one-shot row creation of
LDP EntityID and LowerBound vpi/vci and LDP EntityID and LowerBound vpi/vci and
UpperBound vpi/vci. At least one label UpperBound vpi/vci. At least one label
range entry for a specific LDP Entity MUST range entry for a specific LDP Entity MUST
include the default VPI/VCI values denoted include the default VPI/VCI values denoted
in the LDP Entity Table." in the LDP Entity Table.
A request to create a row with an overlapping
range should result in an inconsistentValue
error."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpEntityAtmLRMinVpi, mplsLdpEntityAtmLRMinVpi,
mplsLdpEntityAtmLRMinVci mplsLdpEntityAtmLRMinVci
} }
::= { mplsLdpEntityAtmLRTable 1 } ::= { mplsLdpEntityAtmLRTable 1 }
MplsLdpEntityAtmLREntry ::= SEQUENCE { MplsLdpEntityAtmLREntry ::= SEQUENCE {
mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, mplsLdpEntityAtmLRMinVpi AtmVpIdentifier,
mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier,
skipping to change at page 74, line 33 skipping to change at page 76, line 15
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum VCI number configured for this range." "The maximum VCI number configured for this range."
::= { mplsLdpEntityAtmLREntry 4 } ::= { mplsLdpEntityAtmLREntry 4 }
mplsLdpEntityAtmLRStorageType OBJECT-TYPE mplsLdpEntityAtmLRStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' need not allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row." need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmLREntry 5 } ::= { mplsLdpEntityAtmLREntry 5 }
mplsLdpEntityAtmLRRowStatus OBJECT-TYPE mplsLdpEntityAtmLRRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any time,
detail in the section entitled, 'Changing Values After Session however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer, if a session has been initiated with a Peer,
changing objects in this table will changing objects in this table will
wreak havoc with the session and interrupt traffic. To repeat again: wreak havoc with the session and interrupt traffic.
the recommended procedure is to set the mplsLdpEntityAdminStatus to To repeat again: the recommended procedure
down, thereby explicitely causing a session to be torn down. Then, is to set the mplsLdpEntityAdminStatus to
change objects in this entry, then set the mplsLdpEntityAdminStatus down, thereby explicitly causing a session
to enable which enables a NEW session to be initiated. to be torn down. Then, change objects in this
entry, then set the mplsLdpEntityAdminStatus
There must exist at least one entry in this to enable which enables a new session
table for every LDP Entity that has to be initiated."
'mplsLdpEntityOptionalParameters' object with
a value of 'atmSessionParameters'.
NOTE: This RowStatus object should
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry."
::= { mplsLdpEntityAtmLREntry 6 } ::= { mplsLdpEntityAtmLREntry 6 }
-- --
-- MPLS LDP ATM Session Information -- MPLS LDP ATM Session Information
-- --
mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::=
mplsLdpAtmSesObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 2 } { mplsLdpAtmObjects 2 }
mplsLdpAtmSesTable OBJECT-TYPE mplsLdpAtmSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpAtmSesEntry SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table which relates Sessions in the "A table which relates sessions in the
'mplsLdpSessionTable' and their label 'mplsLdpSessionTable' and their label
range intersections. There could be one range intersections. There could be one
or more label range intersections between an or more label range intersections between an
LDP Entity and LDP Peer using ATM as the underlying LDP Entity and LDP Peer using ATM as the
media. Each row represents a single label range underlying media. Each row represents
intersection. a single label range intersection.
NOTE: this table cannot use the 'AUGMENTS' This table cannot use the 'AUGMENTS'
clause because there is not necessarily a one-to-one clause because there is not necessarily
mapping between this table and the mplsLdpSessionTable." a one-to-one mapping between this table
::= { mplsLdpAtmSesObjects 1 } and the mplsLdpSessionTable."
::= { mplsLdpAtmSessionObjects 1 }
mplsLdpAtmSesEntry OBJECT-TYPE mplsLdpAtmSessionEntry OBJECT-TYPE
SYNTAX MplsLdpAtmSesEntry SYNTAX MplsLdpAtmSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single label range intersection between an LDP Entity single label range intersection between an LDP Entity
and LDP Peer. and LDP Peer.
The information contained in a row is read-only." The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpSesAtmLRLowerBoundVpi, mplsLdpSessionAtmLRLowerBoundVpi,
mplsLdpSesAtmLRLowerBoundVci mplsLdpSessionAtmLRLowerBoundVci
} }
::= { mplsLdpAtmSesTable 1 } ::= { mplsLdpAtmSessionTable 1 }
MplsLdpAtmSesEntry ::= SEQUENCE { MplsLdpAtmSessionEntry ::= SEQUENCE {
mplsLdpSesAtmLRLowerBoundVpi AtmVpIdentifier, mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier,
mplsLdpSesAtmLRLowerBoundVci MplsAtmVcIdentifier, mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier,
mplsLdpSesAtmLRUpperBoundVpi AtmVpIdentifier, mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier,
mplsLdpSesAtmLRUpperBoundVci MplsAtmVcIdentifier mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier
} }
mplsLdpSesAtmLRLowerBoundVpi OBJECT-TYPE mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum VPI number for this range." "The minimum VPI number for this range."
::= { mplsLdpAtmSesEntry 1 } ::= { mplsLdpAtmSessionEntry 1 }
mplsLdpSesAtmLRLowerBoundVci OBJECT-TYPE mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum VCI number for this range." "The minimum VCI number for this range."
::= { mplsLdpAtmSesEntry 2 } ::= { mplsLdpAtmSessionEntry 2 }
mplsLdpSesAtmLRUpperBoundVpi OBJECT-TYPE mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum VPI number for this range." "The maximum VPI number for this range."
::= { mplsLdpAtmSesEntry 3 } ::= { mplsLdpAtmSessionEntry 3 }
mplsLdpSesAtmLRUpperBoundVci OBJECT-TYPE
mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum VCI number for this range." "The maximum VCI number for this range."
::= { mplsLdpAtmSesEntry 4 } ::= { mplsLdpAtmSessionEntry 4 }
--************************************************************** --**************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--************************************************************** --**************************************************************
mplsLdpAtmGroups mplsLdpAtmGroups
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 }
mplsLdpAtmCompliances mplsLdpAtmCompliances
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 }
skipping to change at page 80, line 33 skipping to change at page 82, line 15
mplsLdpEntityAtmDefaultControlVpi, mplsLdpEntityAtmDefaultControlVpi,
mplsLdpEntityAtmDefaultControlVci, mplsLdpEntityAtmDefaultControlVci,
mplsLdpEntityAtmUnlabTrafVpi, mplsLdpEntityAtmUnlabTrafVpi,
mplsLdpEntityAtmUnlabTrafVci, mplsLdpEntityAtmUnlabTrafVci,
mplsLdpEntityAtmStorageType, mplsLdpEntityAtmStorageType,
mplsLdpEntityAtmRowStatus, mplsLdpEntityAtmRowStatus,
mplsLdpEntityAtmLRMaxVpi, mplsLdpEntityAtmLRMaxVpi,
mplsLdpEntityAtmLRMaxVci, mplsLdpEntityAtmLRMaxVci,
mplsLdpEntityAtmLRStorageType, mplsLdpEntityAtmLRStorageType,
mplsLdpEntityAtmLRRowStatus, mplsLdpEntityAtmLRRowStatus,
mplsLdpSesAtmLRUpperBoundVpi, mplsLdpSessionAtmLRUpperBoundVpi,
mplsLdpSesAtmLRUpperBoundVci mplsLdpSessionAtmLRUpperBoundVci
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations "Objects that apply to all MPLS LDP implementations
using ATM as the Layer 2." using ATM as the Layer 2."
::= { mplsLdpAtmGroups 1 } ::= { mplsLdpAtmGroups 1 }
END END
4.2. The MPLS-LDP-FRAME-RELAY-MIB Module 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module
This MIB Module MUST be supported if LDP uses FRAME RELAY as the This MIB Module MUST be supported if LDP uses FRAME RELAY as the
Layer 2 media. There are three tables in this MIB Module. Two Layer 2 media. There are three tables in this MIB Module. Two
tables are to configure LDP for using Frame Relay. These tables are tables are to configure LDP for using Frame Relay. These tables are
the mplsLdpEntityFrameRelayParmsTable and the the mplsLdpEntityFrameRelayTable and the
mplsLdpEntityFrameRelayLabelRangeTable. mplsLdpEntityFrameRelayLRTable.
The mplsLdpEntityFrameRelayParmsTable provides a way to configure The mplsLdpEntityFrameRelayTable provides a way to configure
information which would be contained in the "Optional Parameter" information which would be contained in the "Optional Parameter"
portion of an LDP PDU Initialization Message. portion of an LDP PDU Initialization Message.
The mplsLdpEntityFrameRelayLabelRangeTable provides a way to The mplsLdpEntityFrameRelayLRTable provides a way to configure
configure information which would be contained in the "Frame Relay information which would be contained in the "Frame Relay Label Range
Label Range Components" portion of an LDP PDU Intialization Message, Components" portion of an LDP PDU Intialization Message, see
see [RFC3034] and [RFC3036]. [RFC3034] and [RFC3036].
4.2.1. The LDP Frame Relay Session Table 4.2.1. The LDP Frame Relay Session Table
The MPLS LDP Frame Relay Session Table is a read-only table which The MPLS LDP Frame Relay Session Table is a read-only table which
contains session information specific to Frame Relay. contains session information specific to Frame Relay.
MPLS-LDP-FRAME-RELAY-MIB DEFINITIONS ::= BEGIN MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
mplsMIB mplsStdMIB
FROM MPLS-TC-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpFrameRelayMIB MODULE-IDENTITY mplsLdpFrameRelayStdMIB MODULE-IDENTITY
LAST-UPDATED "200304221200Z" -- 22 April 2003 LAST-UPDATED "200306091200Z" -- 9 June 2003
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@artel.com)
Artel Artel
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
skipping to change at page 82, line 45 skipping to change at page 84, line 28
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing Frame Relay as the Layer 2 media." utilizing Frame Relay as the Layer 2 media."
REVISION "200304221200Z" -- 22 April 2003 REVISION "200306091200Z" -- 9 June 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsMIB subId is 6, e.g. -- The requested mplsStdMIB subId is 6, e.g.
-- ::= { mplsMIB 6 } -- ::= { mplsStdMIB 6 }
::= { mplsMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpFrameRelayObjects mplsLdpFrameRelayObjects OBJECT IDENTIFIER
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 1 } ::= { mplsLdpFrameRelayStdMIB 1 }
mplsLdpFrameRelayConformance
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 2 } mplsLdpFrameRelayConformance OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP Frame Relay Objects -- MPLS LDP Frame Relay Objects
--**************************************************************** --****************************************************************
-- --
-- Ldp Entity Objects for Frame Relay -- Ldp Entity Objects for Frame Relay
-- --
mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
skipping to change at page 85, line 21 skipping to change at page 87, line 5
Value Meaning Value Meaning
0 Merge not supported 0 Merge not supported
1 Merge supported 1 Merge supported
Non-merge and merge Frame Relay LSRs may freely interoperate.' Non-merge and merge Frame Relay LSRs may freely interoperate.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 2 } ::= { mplsLdpEntityFrameRelayEntry 2 }
mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of Label Range Components in the Initialization "Number of Label Range Components in the Initialization
message. This also represents the number of entries message. This also represents the number of entries
in the mplsLdpEntityFrameRelayLRTable which correspond in the mplsLdpEntityFrameRelayLRTable which correspond
to this entry. to this entry.
This is the EXACT value for the Frame Relay Session Parameter, This is the EXACT value for the Frame Relay Session Parameter,
field N (for Number of label range components). The Frame Relay field N (for Number of label range components). The Frame Relay
Session Parameter is an optional parameter in the Initialization Message. Session Parameter is an optional parameter in
the Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'N, Number of label range components 'N, Number of label range components
Specifies the number of Frame Relay Label Range Components Specifies the number of Frame Relay Label Range Components
included in the TLV.' included in the TLV.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 3 } ::= { mplsLdpEntityFrameRelayEntry 3 }
mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bidirectional(0), bidirectional(0),
unidirection(1) unidirection(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 'bidirectional(0)', then "If the value of this object is 'bidirectional(0)', then
the LSR supports the use of a given DLCI as a label for the LSR supports the use of a given DLCI as a label for
skipping to change at page 86, line 41 skipping to change at page 88, line 28
capability, both LSRs use unidirectional VC label assignment capability, both LSRs use unidirectional VC label assignment
for the link as follows. The LSRs compare their LDP for the link as follows. The LSRs compare their LDP
Identifiers as unsigned integers. The LSR with the larger LDP Identifiers as unsigned integers. The LSR with the larger LDP
Identifier may assign only odd-numbered DLCIs in the range as Identifier may assign only odd-numbered DLCIs in the range as
labels. The system with the smaller LDP Identifier may assign labels. The system with the smaller LDP Identifier may assign
only even-numbered DLCIs in the range as labels.' only even-numbered DLCIs in the range as labels.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 4 } ::= { mplsLdpEntityFrameRelayEntry 4 }
mplsLdpEntityFrameRelayStorageType OBJECT-TYPE mplsLdpEntityFrameRelayStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row, except for setting the need not allow write-access to any columnar
mplsLdpEntityFrameRelayRowStatus to 'destroy(6)'." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayEntry 5 } ::= { mplsLdpEntityFrameRelayEntry 5 }
mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any time,
detail in the section entitled, 'Changing Values After Session however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer, if a session has been initiated with a Peer,
changing objects in this table will changing objects in this table will
wreak havoc with the session and interrupt traffic. To repeat again: wreak havoc with the session and interrupt
the recommended procedure is to set the mplsLdpEntityAdminStatus to traffic. To repeat again:
down, thereby explicitely causing a session to be torn down. Then, the recommended procedure is to set the
change objects in this entry, then set the mplsLdpEntityAdminStatus mplsLdpEntityAdminStatus to
to enable which enables a NEW session to be initiated. down, thereby explicitly causing a
session to be torn down. Then,
NOTE: This RowStatus object should change objects in this entry, then set
have the same value of the 'mplsLdpEntityRowStatus' the mplsLdpEntityAdminStatus
related to this entry." to enable which enables a new session
to be initiated."
::= { mplsLdpEntityFrameRelayEntry 6 } ::= { mplsLdpEntityFrameRelayEntry 6 }
-- --
-- Frame Relay Label Range Components -- Frame Relay Label Range Components
-- --
mplsLdpEntityFrameRelayLRTable OBJECT-TYPE mplsLdpEntityFrameRelayLRTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the "This table contains information about the
Optional Parameters for the Frame Relay Session Optional Parameters for the Frame Relay Session
in the LDP Initialization Message, specifically in the LDP Initialization Message, specifically
it contains information about the Frame Relay it contains information about the Frame Relay
Label Range Components." Label Range Components.
If the value of the object
'mplsLdpEntityOptionalParameters' contains the
value of 'frameRelaySessionParameters(3)' then
there must be at least one corresponding entry
in this table."
::= { mplsLdpEntityFrameRelayObjects 2 } ::= { mplsLdpEntityFrameRelayObjects 2 }
mplsLdpEntityFrameRelayLREntry OBJECT-TYPE mplsLdpEntityFrameRelayLREntry OBJECT-TYPE
SYNTAX MplsLdpEntityFrameRelayLREntry SYNTAX MplsLdpEntityFrameRelayLREntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents the Frame Relay "An entry in this table represents the Frame Relay
Label Range Component associated with the LDP entity." Label Range Component associated with the LDP entity."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
skipping to change at page 88, line 37 skipping to change at page 90, line 32
mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower bound which is supported. This value should "The lower bound which is supported. This value should
be the same as that in the Frame Relay Label Range be the same as that in the Frame Relay Label Range
Component's Minimum DLCI field. The value of zero Component's Minimum DLCI field. The value of zero
is valid for the minimum DLCI field of the label." is valid for the minimum DLCI field of the label."
REFERENCE REFERENCE
"[RFC 3034] Use of Label Switching on Frame Relay Networks "RFC3034, Use of Label Switching on Frame Relay Networks
Specification." Specification."
::= { mplsLdpEntityFrameRelayLREntry 1 } ::= { mplsLdpEntityFrameRelayLREntry 1 }
mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper bound which is supported. This value should "The upper bound which is supported. This value should
be the same as that in the Frame Relay Label Range be the same as that in the Frame Relay Label Range
skipping to change at page 89, line 33 skipping to change at page 91, line 29
Len DLCI bits Len DLCI bits
0 10 0 10
2 23 2 23
Len values 1 and 3 are reserved.' Len values 1 and 3 are reserved.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
::= { mplsLdpEntityFrameRelayLREntry 3 } ::= { mplsLdpEntityFrameRelayLREntry 3 }
mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' MAY allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row, except for setting the need not allow write-access to any columnar
mplsLdpEntityFrameRelayLRRowStatus to 'destroy(6)'." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayLREntry 4 } ::= { mplsLdpEntityFrameRelayLREntry 4 }
mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any time,
detail in the section entitled, 'Changing Values After Session however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer, if a session has been initiated with a Peer,
changing objects in this table will changing objects in this table will
wreak havoc with the session and interrupt traffic. To repeat again: wreak havoc with the session and interrupt
the recommended procedure is to set the mplsLdpEntityAdminStatus to traffic. To repeat again:
down, thereby explicitely causing a session to be torn down. Then, the recommended procedure is to set the
change objects in this entry, then set the mplsLdpEntityAdminStatus mplsLdpEntityAdminStatus to down, thereby
to enable which enables a NEW session to be initiated. explicitly causing a session to be torn down. Then,
change objects in this entry, then set the
If the value of the object mplsLdpEntityAdminStatus to enable which enables
'mplsLdpEntityOptionalParameters' contains the a new session to be initiated."
value of 'frameRelaySessionParameters(3)' then
there must be at least one corresponding entry
in this table.
NOTE: This RowStatus object should
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry."
::= { mplsLdpEntityFrameRelayLREntry 5 } ::= { mplsLdpEntityFrameRelayLREntry 5 }
-- --
-- MPLS LDP Frame Relay Session Information -- MPLS LDP Frame Relay Session Information
-- --
mplsLdpFrameRelaySesObjects OBJECT IDENTIFIER ::= mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 2 } { mplsLdpFrameRelayObjects 2 }
mplsLdpFrameRelaySesTable OBJECT-TYPE mplsLdpFrameRelaySessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpFrameRelaySesEntry SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Frame Relay label range intersections "A table of Frame Relay label range intersections
between the LDP Entities and LDP Peers. between the LDP Entities and LDP Peers.
Each row represents a single label range intersection. Each row represents a single label range intersection.
NOTE: this table cannot use the 'AUGMENTS' NOTE: this table cannot use the 'AUGMENTS'
clause because there is not necessarily a one-to-one clause because there is not necessarily a one-to-one
mapping between this table and the mplsLdpSessionTable." mapping between this table and the mplsLdpSessionTable."
::= { mplsLdpFrameRelaySesObjects 1 } ::= { mplsLdpFrameRelaySessionObjects 1 }
mplsLdpFrameRelaySesEntry OBJECT-TYPE mplsLdpFrameRelaySessionEntry OBJECT-TYPE
SYNTAX MplsLdpFrameRelaySesEntry SYNTAX MplsLdpFrameRelaySessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single label range intersection between an single label range intersection between an
LDP Entity and LDP Peer. LDP Entity and LDP Peer.
The information contained in a row is read-only." The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpFrameRelaySesMinDlci mplsLdpFrameRelaySessionMinDlci
} }
::= { mplsLdpFrameRelaySesTable 1 } ::= { mplsLdpFrameRelaySessionTable 1 }
MplsLdpFrameRelaySesEntry ::= SEQUENCE { MplsLdpFrameRelaySessionEntry ::= SEQUENCE {
mplsLdpFrameRelaySesMinDlci DLCI, mplsLdpFrameRelaySessionMinDlci DLCI,
mplsLdpFrameRelaySesMaxDlci DLCI, mplsLdpFrameRelaySessionMaxDlci DLCI,
mplsLdpFrameRelaySesLen INTEGER mplsLdpFrameRelaySessionLen INTEGER
} }
mplsLdpFrameRelaySesMinDlci OBJECT-TYPE mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower bound of DLCIs which are supported. "The lower bound of DLCIs which are supported.
The value of zero is a valid value for the The value of zero is a valid value for the
minimum DLCI field of the label." minimum DLCI field of the label."
REFERENCE REFERENCE
"[RFC 3034] Use of Label Switching on Frame Relay Networks "RFC3034, Use of Label Switching on Frame Relay Networks
Specification." Specification."
::= { mplsLdpFrameRelaySesEntry 1 } ::= { mplsLdpFrameRelaySessionEntry 1 }
mplsLdpFrameRelaySesMaxDlci OBJECT-TYPE mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper bound of DLCIs which are supported." "The upper bound of DLCIs which are supported."
::= { mplsLdpFrameRelaySesEntry 2 } ::= { mplsLdpFrameRelaySessionEntry 2 }
mplsLdpFrameRelaySesLen OBJECT-TYPE mplsLdpFrameRelaySessionLen OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tenDlciBits(0), tenDlciBits(0),
twentyThreeDlciBits(2) twentyThreeDlciBits(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the DLCI bits." "This object specifies the DLCI bits."
::= { mplsLdpFrameRelaySesEntry 3 } ::= { mplsLdpFrameRelaySessionEntry 3 }
--**************************************************************** --****************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--**************************************************************** --****************************************************************
mplsLdpFrameRelayGroups mplsLdpFrameRelayGroups
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 }
mplsLdpFrameRelayCompliances mplsLdpFrameRelayCompliances
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 }
skipping to change at page 95, line 9 skipping to change at page 96, line 46
mplsLdpEntityFrameRelayIfIndexOrZero, mplsLdpEntityFrameRelayIfIndexOrZero,
mplsLdpEntityFrameRelayMergeCap, mplsLdpEntityFrameRelayMergeCap,
mplsLdpEntityFrameRelayLRComponents, mplsLdpEntityFrameRelayLRComponents,
mplsLdpEntityFrameRelayVcDirectionality, mplsLdpEntityFrameRelayVcDirectionality,
mplsLdpEntityFrameRelayStorageType, mplsLdpEntityFrameRelayStorageType,
mplsLdpEntityFrameRelayRowStatus, mplsLdpEntityFrameRelayRowStatus,
mplsLdpEntityFrameRelayLRMaxDlci, mplsLdpEntityFrameRelayLRMaxDlci,
mplsLdpEntityFrameRelayLRLen, mplsLdpEntityFrameRelayLRLen,
mplsLdpEntityFrameRelayLRStorageType, mplsLdpEntityFrameRelayLRStorageType,
mplsLdpEntityFrameRelayLRRowStatus, mplsLdpEntityFrameRelayLRRowStatus,
mplsLdpFrameRelaySesMaxDlci, mplsLdpFrameRelaySessionMaxDlci,
mplsLdpFrameRelaySesLen mplsLdpFrameRelaySessionLen
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations over "Objects that apply to all MPLS LDP implementations
Frame Relay." using Frame Relay as the Layer 2."
::= { mplsLdpFrameRelayGroups 1 } ::= { mplsLdpFrameRelayGroups 1 }
END END
4.3. The MPLS-LDP-GENERIC-MIB Module 4.3. The MPLS-LDP-GENERIC-STD-MIB Module
This MIB Module MUST be supported if LDP uses a Per Platform Label This MIB Module MUST be supported if LDP uses a Per Platform Label
Space. This MIB Module contains a Label Range (LR) table for Space. This MIB Module contains a Label Range (LR) table for
configuring Mpls Generic Label Ranges. This table is configuring Mpls Generic Label Ranges. This table is
mplsLdpEntityGenericLabelRangeTable. Although the LDP Specification mplsLdpEntityGenericLRTable. Although the LDP Specification does not
does not provide a way for configuring Label Ranges for Generic provide a way for configuring Label Ranges for Generic Labels, the
Labels, the MIB does provide a way to reserve a range of generic MIB does provide a way to reserve a range of generic labels because
labels because this was thought to be useful by the working group. this was thought to be useful by the working group.
MPLS-LDP-GENERIC-MIB DEFINITIONS ::= BEGIN MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
skipping to change at page 96, line 4 skipping to change at page 97, line 33
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
mplsMIB mplsStdMIB
FROM MPLS-TC-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex mplsLdpEntityIndex
FROM MPLS-LDP-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpGenericMIB MODULE-IDENTITY mplsLdpGenericStdMIB MODULE-IDENTITY
LAST-UPDATED "200204221200Z" -- 22 April 2003 LAST-UPDATED "200306091200Z" -- 9 June 2003
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@artel.com)
Artel Artel
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
skipping to change at page 96, line 48 skipping to change at page 98, line 38
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing ethernet as the Layer 2 media." utilizing ethernet as the Layer 2 media."
REVISION "200304221200Z" -- 22 April 2003 REVISION "200306091200Z" -- 9 June 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsMIB subId is 7, e.g. -- The requested mplsStdMIB subId is 7, e.g.
-- ::= { mplsMIB 7 } -- ::= { mplsStdMIB 7 }
::= { mplsMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpGenericObjects mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 1 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance mplsLdpGenericConformance
OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 2 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP GENERIC Objects -- MPLS LDP GENERIC Objects
--**************************************************************** --****************************************************************
-- --
-- Ldp Entity Objects for Generic Labels -- Ldp Entity Objects for Generic Labels
-- --
mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::=
skipping to change at page 99, line 30 skipping to change at page 101, line 19
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value of this object is perPlatform(1), then "This value of this object is perPlatform(1), then
this means that the label space type is this means that the label space type is
per platform. per platform.
If this object is perInterface(2), then this If this object is perInterface(2), then this
means that the label space type is per Interface." means that the label space type is per Interface."
REFERENCE REFERENCE
"[RFC3036], LDP Specification, Section 2.2.1, "RFC3036, LDP Specification, Section 2.2.1,
Label Spaces." Label Spaces."
DEFVAL { perPlatform } DEFVAL { perPlatform }
::= { mplsLdpEntityGenericLREntry 3 } ::= { mplsLdpEntityGenericLREntry 3 }
mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents either the InterfaceIndex of "This value represents either the InterfaceIndex of
skipping to change at page 100, line 16 skipping to change at page 102, line 4
network management entity (e.g. SNMP agent) responsible network management entity (e.g. SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex." value of the InterfaceIndex."
::= { mplsLdpEntityGenericLREntry 4 } ::= { mplsLdpEntityGenericLREntry 4 }
mplsLdpEntityGenericLRStorageType OBJECT-TYPE mplsLdpEntityGenericLRStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual rows "The storage type for this conceptual row.
having the value 'permanent(4)' need not allow write-access to any Conceptual rows having the value 'permanent(4)'
columnar objects in the row." need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpEntityGenericLREntry 5 } ::= { mplsLdpEntityGenericLREntry 5 }
mplsLdpEntityGenericLRRowStatus OBJECT-TYPE mplsLdpEntityGenericLRRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable objects in this "The status of this conceptual row. All writable
row may be modified at any time, however, as described in objects in this row may be modified at any time,
detail in the section entitled, 'Changing Values After Session however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus object, DESCRIPTION clause of the mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer, if a session has been initiated with a Peer,
changing objects in this table will changing objects in this table will
wreak havoc with the session and interrupt traffic. To repeat again: wreak havoc with the session and interrupt traffic.
the recommended procedure is to set the mplsLdpEntityAdminStatus to To repeat again: the recommended procedure is
down, thereby explicitely causing a session to be torn down. Then, to set the mplsLdpEntityAdminStatus to
change objects in this entry, then set the mplsLdpEntityAdminStatus down, thereby explicitly causing a
to enable which enables a NEW session to be initiated. session to be torn down. Then, change objects
in this entry, then set the mplsLdpEntityAdminStatus
to enable which enables a new session to be initiated.
There must exist at least one entry in this There must exist at least one entry in this
table for every LDP Entity that has a table for every LDP Entity that has a
generic label configured. generic label configured."
NOTE: This RowStatus object should
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry."
::= { mplsLdpEntityGenericLREntry 6 } ::= { mplsLdpEntityGenericLREntry 6 }
--**************************************************************** --****************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--**************************************************************** --****************************************************************
mplsLdpGenericGroups mplsLdpGenericGroups
OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 }
mplsLdpGenericCompliances mplsLdpGenericCompliances
skipping to change at page 102, line 45 skipping to change at page 104, line 37
mplsLdpGenericGroup OBJECT-GROUP mplsLdpGenericGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLdpEntityGenericLabelSpace, mplsLdpEntityGenericLabelSpace,
mplsLdpEntityGenericIfIndexOrZero, mplsLdpEntityGenericIfIndexOrZero,
mplsLdpEntityGenericLRStorageType, mplsLdpEntityGenericLRStorageType,
mplsLdpEntityGenericLRRowStatus mplsLdpEntityGenericLRRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations "Objects that apply to all MPLS LDP implementations
using Generic Lables." using Generic Labels as the Layer 2."
::= { mplsLdpGenericGroups 1 } ::= { mplsLdpGenericGroups 1 }
END END
5. Revision History 5. Revision History
NOTE TO RFC-Editor: before publishing this document as an RFC, NOTE TO RFC-Editor: before publishing this document as an RFC,
please remove this Revision History (change log) section. sp please remove this Revision History (change log) section. sp
5.1. Changes from <draft-ietf-mpls-ldp-mib-09.txt> 5.1. Changes from <draft-ietf-mpls-ldp-mib-10.txt>
Renamed the MIB module to include Std and also updated the IANA
Considerations Section to use mplsStdMIB.
Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet
update #3 from that email and 2) did not yet review all the
InetAddressType and InetAddress objects to make sure that
descriptions were per rfc3291.
Changed Ses to Session for clarity.
5.2. Changes from <draft-ietf-mpls-ldp-mib-09.txt>
Added the new MIB boiler plate and associated MIB reference changes. Added the new MIB boiler plate and associated MIB reference changes.
Reworked the OID tree structure so that the Modules only have the Reworked the OID tree structure so that the Modules only have the
mplsMIB subid dependency. This was discussed in mpls wg email mplsMIB subid dependency. This was discussed in mpls wg email
(discussion was mostly between Bert, Tom and Joan). (discussion was mostly between Bert, Tom and Joan).
Added IANA Considerations section. This contains 4 subsections, one Added IANA Considerations section. This contains 4 subsections, one
per MIB module. per MIB module.
Updated and added new references as needed. Updated and added new references as needed.
Changed mplsMIB subid values to agree with the latest "Multiprotocol Changed mplsMIB subid values to agree with the latest "Multiprotocol
Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. Label Switching (MPLS) Management Overview" document, [MPLSMGMT].
Moved MIB modules around so that they would appear in subId order. Moved MIB modules around so that they would appear in subId order.
The Generic MIB module is shown last, since the subid is 7 (which is The Generic MIB module is shown last, since the subid is 7 (which is
the last (and largest) subid requested by IANA. the last (and largest) subid requested by IANA.
5.1.1. Changes based on MIB Doctor Review Comments 5.2.1. Changes based on MIB Doctor Review Comments
The following changes are based on comments from the MIB DR Review. The following changes are based on comments from the MIB DR Review.
The comments are from email to the mpls working group dated, Dec 6, The comments are from email to the mpls working group dated, Dec 6,
2002. These comments are quoted and prefaced by "REQ: comment goes 2002. These comments are quoted and prefaced by "REQ: comment goes
here", and then followed by our resolution. here", and then followed by our resolution.
"REQ: - missing IPR section". RSP: it has been added. "REQ: - missing IPR section". RSP: it has been added.
"REQ: - Security considerations probably needs more work "REQ: - Security considerations probably needs more work
Security ADs want you to explain what the vulnerabilities/risks Security ADs want you to explain what the vulnerabilities/risks
skipping to change at page 109, line 4 skipping to change at page 110, line 16
to this entry." to this entry."
Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed. Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed.
"REQ:- I see the xxxDlci index objects start at zero. "REQ:- I see the xxxDlci index objects start at zero.
Pls add to DESCRIPTION clauses why zero must be an index.". RSP: Pls add to DESCRIPTION clauses why zero must be an index.". RSP:
Since we are using DLCI and the value of zero is valid for a DLCI. A Since we are using DLCI and the value of zero is valid for a DLCI. A
statement was added about this. Also, used the DLCI TC from statement was added about this. Also, used the DLCI TC from
rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB
module uses an index of the VP which can also take on the value of module uses an index of the VP which can also take on the value of
zero. A statement was added to this Index also. "REQ:- zero. A statement was added to this Index also. "REQ:-
mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP:
done. done.
5.2. Changes from <draft-ietf-mpls-ldp-mib-08.txt> 5.3. Changes from <draft-ietf-mpls-ldp-mib-08.txt>
The following changes are from the IESG MIB review. The following changes are from the IESG MIB review.
Changed "Label Switch Router" to "Label Switching Router". Changed "Label Switch Router" to "Label Switching Router".
Spelling errors fixed (unlabelled, atttempt, subsytem). Spelling errors fixed (unlabelled, atttempt, subsytem).
Changed some of the enums to start at 1, instead of zero: Changed some of the enums to start at 1, instead of zero:
mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus.
skipping to change at page 111, line 22 skipping to change at page 112, line 32
Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus
objects. RowStatus now reflects the status of the row, and Admin objects. RowStatus now reflects the status of the row, and Admin
status controls enabling/disabling the entry. status controls enabling/disabling the entry.
Updated the DESCRIPTION clauses for the objects in the Updated the DESCRIPTION clauses for the objects in the
mplsLdpEntityStatsTable to refer to the mplsLdpEntityStatsTable to refer to the
mplsLdpEntityDiscontinuityTime object. mplsLdpEntityDiscontinuityTime object.
Changed StorType to StorageType. Changed StorType to StorageType.
5.3. Changes from <draft-ietf-mpls-ldp-mib-07.txt> 5.4. Changes from <draft-ietf-mpls-ldp-mib-07.txt>
There were three types of changes: the first change was that all the There were three types of changes: the first change was that all the
MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were
moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc-
mib-00.txt". The Textual Conventions are now IMPORTED from mib-00.txt". The Textual Conventions are now IMPORTED from
[MPLSTCMIB]. The second type of change was updates based on comments [MPLSTCMIB]. The second type of change was updates based on comments
from the IESG. These changes will be discussed below. The third from the IESG. These changes will be discussed below. The third
type of changes were based on minor editorial changes from the co- type of changes were based on minor editorial changes from the co-
authors. authors.
skipping to change at page 112, line 31 skipping to change at page 113, line 42
mplsLdpEntityInitSesTrapEnable object is useless and was removed mplsLdpEntityInitSesTrapEnable object is useless and was removed
since setting mplsLdpEntityInitSesThreshold=0 acheives the same since setting mplsLdpEntityInitSesThreshold=0 acheives the same
thing. Also removed it from the descriptive text in section 3. thing. Also removed it from the descriptive text in section 3.
Page 47, mplsLdpSessionDiscontinuityTime The initial value of this Page 47, mplsLdpSessionDiscontinuityTime The initial value of this
was changed to be sysUpTime instead of zero. sysUpTime for when the was changed to be sysUpTime instead of zero. sysUpTime for when the
session starts is more meaningful and was added to the Session session starts is more meaningful and was added to the Session
Up/Down Traps also. Also, added the Session specific stats to the Up/Down Traps also. Also, added the Session specific stats to the
up/down traps. up/down traps.
5.4. Changes from <draft-ietf-mpls-ldp-mib-06.txt> 5.5. Changes from <draft-ietf-mpls-ldp-mib-06.txt>
All changes were from the second last call which took place Thursday, All changes were from the second last call which took place Thursday,
July 20th, until Thursday, July 27th, 2000 and are described in the July 20th, until Thursday, July 27th, 2000 and are described in the
remainder of this section. remainder of this section.
Remove the reference to the MPLS framework document. Remove the reference to the MPLS framework document.
Add an mplsFecIndexNext type of object. Add an mplsFecIndexNext type of object.
Change the conformance of the FEC table objects to be part of the Change the conformance of the FEC table objects to be part of the
mplsLdpGeneralGroup. mplsLdpGeneralGroup.
The mplsLdpEntityConfGenericTable is no longer needed because the The mplsLdpEntityConfGenericTable is no longer needed because the
functionality has been absorbed by the functionality has been absorbed by the
mplsLdpEntityConfGenericLabelRangeTable. The mplsLdpEntityConfGenericLabelRangeTable. The
mplsLdpEntityConfGenericTable has been removed and the front section mplsLdpEntityConfGenericTable has been removed and the front section
was updated accordingly. was updated accordingly.
Other editorial issues, updating references, typos and so forth. Other editorial issues, updating references, typos and so forth.
5.5. Changes from <draft-ietf-mpls-ldp-mib-05.txt> 5.6. Changes from <draft-ietf-mpls-ldp-mib-05.txt>
The majority of changes in this revision are based on Last Call The majority of changes in this revision are based on Last Call
comments which were received during the last call from Thursday, comments which were received during the last call from Thursday,
March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. March 9, 2000 to Friday, March 17, 2000, or slightly thereafter.
Also, changes were made to agree with the latest specifications. Also, changes were made to agree with the latest specifications.
These changes are described in this section. These changes are described in this section.
Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-
ldp-08.txt. Specifically, removing references to IPv4/IP and using ldp-08.txt. Specifically, removing references to IPv4/IP and using
router id, as appropriate. router id, as appropriate.
skipping to change at page 114, line 40 skipping to change at page 116, line 4
Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40
seconds. seconds.
Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The
default value is 8. default value is 8.
The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects,
one for TCP and one for UDP. The names are one for TCP and one for UDP. The names are
Typo in the description for the Typo in the description for the
The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The
mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to
show that these two tables are related. There has been wording added show that these two tables are related. There has been wording added
to the mplsLdpSessionEntry description and to the description for the to the mplsLdpSessionEntry description and to the description for the
mplsLdpPeerTable. mplsLdpPeerTable.
5.6. Changes from <draft-ietf-mpls-ldp-mib-04.txt> 5.7. Changes from <draft-ietf-mpls-ldp-mib-04.txt>
Editorial changes, fixing typo's, fixing wrapping lines, etc. Editorial changes, fixing typo's, fixing wrapping lines, etc.
Updated references for latest drafts, and added [RFC3032] and Updated references for latest drafts, and added [RFC3032] and
[RFC3034] to Reference Section. [RFC3034] to Reference Section.
Added to the Acknowledgements Section. Added to the Acknowledgements Section.
Changed the SYNTAX and DESCRIPTION of the Changed the SYNTAX and DESCRIPTION of the
'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support
skipping to change at page 117, line 21 skipping to change at page 118, line 28
object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to
fit in with the 'mplsLdpEntityFrameRelayParmsTable'. fit in with the 'mplsLdpEntityFrameRelayParmsTable'.
Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen
object. (The 17 bit length was dropped by the Frame Relay Forum and object. (The 17 bit length was dropped by the Frame Relay Forum and
thus, is no longer required.) thus, is no longer required.)
Corrected the range of the 'mplsLdpEntityIndexNext' object to include Corrected the range of the 'mplsLdpEntityIndexNext' object to include
0 (zero). 0 (zero).
5.7. Changes from <draft-ietf-mpls-ldp-mib-03.txt> 5.8. Changes from <draft-ietf-mpls-ldp-mib-03.txt>
Reworded the description of the mplsLdpAtmSessionTable to clarify Reworded the description of the mplsLdpAtmSessionTable to clarify
that one or MORE label range intersection(s) is/are represented in that one or MORE label range intersection(s) is/are represented in
this table. this table.
Reworded the description of the mplsLdpFrameRelaySessionTable to Reworded the description of the mplsLdpFrameRelaySessionTable to
clarify that one or MORE label range intersection(s) is/are clarify that one or MORE label range intersection(s) is/are
represented in this table. represented in this table.
Added a new index, mplsLdpSessionPeerIndex, to the Added a new index, mplsLdpSessionPeerIndex, to the
skipping to change at page 118, line 43 skipping to change at page 120, line 5
The mplsLdpSessionIndex was removed throughout the MIB. This was The mplsLdpSessionIndex was removed throughout the MIB. This was
replaced by the object mplsLdpSessionDiscontinuityTime. The replaced by the object mplsLdpSessionDiscontinuityTime. The
motivation was to reduce the number of indices. motivation was to reduce the number of indices.
The descriptions for the objects in the mplsLdpSessionStatsTable, The descriptions for the objects in the mplsLdpSessionStatsTable,
mplsLdpSessionStatsUnknownMessageTypeErrors and mplsLdpSessionStatsUnknownMessageTypeErrors and
mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a
reference to the mplsLdpSessionDiscontinuityTime object. reference to the mplsLdpSessionDiscontinuityTime object.
5.8. Changes from <draft-ietf-mpls-ldp-mib-02.txt> 5.9. Changes from <draft-ietf-mpls-ldp-mib-02.txt>
Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and
mplsLdpEntityIndexNext. mplsLdpEntityIndexNext.
Added the following objects to the mplsLdpEntityTable: Added the following objects to the mplsLdpEntityTable:
mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus,
mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer,
mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and
mplsLdpEntityHelloHoldTimer. mplsLdpEntityHelloHoldTimer.
Changed the description of the mplsLdpEntityAtmParmsTable and added Changed the description of the mplsLdpEntityAtmParmsTable and added
the following objects to this table: mplsLdpEntityAtmLsrConnectivity, the following objects to this table: mplsLdpEntityAtmLsrConnectivity,
mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci, mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci,
mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the
last four objects were in Version 01 of the MIB but were mistakenly last four objects were in Version 01 of the MIB but were mistakenly
skipping to change at page 119, line 27 skipping to change at page 120, line 33
Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to
include the minimum VPI/VCI. This is to ensure that indices in this include the minimum VPI/VCI. This is to ensure that indices in this
table are unique. table are unique.
Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to
include the minimum DLCI value. This is to ensure that indices in include the minimum DLCI value. This is to ensure that indices in
this table are unique. this table are unique.
Added [RFC3036] to Reference Section. Added [RFC3036] to Reference Section.
5.9. Changes from <draft-ietf-mpls-ldp-mib-01.txt> 5.10. Changes from <draft-ietf-mpls-ldp-mib-01.txt>
The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of
the LDP Specification [RFC3036]. the LDP Specification [RFC3036].
The front section was updated. The front section was updated.
The MIB was made to be less ATM-centric. Essentially, the ATM The MIB was made to be less ATM-centric. Essentially, the ATM
specific objects where removed from the tables and placed in ATM specific objects where removed from the tables and placed in ATM
specific Tables. A type was added to the base tables and a row is to specific Tables. A type was added to the base tables and a row is to
be created in the ATM/FR/etc. type table. Apropos compliance be created in the ATM/FR/etc. type table. Apropos compliance
skipping to change at page 120, line 38 skipping to change at page 121, line 44
The mplsLdpSessionStatsTable was added to count statics based on a The mplsLdpSessionStatsTable was added to count statics based on a
per Session basis. per Session basis.
The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no
need to configure information for a Peer. All information for a peer need to configure information for a Peer. All information for a peer
is learned, thus peer information is read-only. is learned, thus peer information is read-only.
(Editorial) References were updated to reflect the documents which (Editorial) References were updated to reflect the documents which
this version was based on. this version was based on.
5.10. Changes from <draft-ietf-mpls-ldp-mib-00.txt> 5.11. Changes from <draft-ietf-mpls-ldp-mib-00.txt>
Textual conventions were added for the LSR Identifier and the LDP Textual conventions were added for the LSR Identifier and the LDP
Identifier. Identifier.
Top-level mib structure was added. The LDP MIB falls under a proposed Top-level mib structure was added. The LDP MIB falls under a proposed
hierarchy of mpls.mplsProtocols. hierarchy of mpls.mplsProtocols.
The mib hierarchy within the LDP MIB was also changed. A new branch, The mib hierarchy within the LDP MIB was also changed. A new branch,
under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This
branch is mplsLdpLsrObjects. Currently, this contains several new branch is mplsLdpLsrObjects. Currently, this contains several new
skipping to change at page 122, line 14 skipping to change at page 123, line 14
7. Normative References 7. Normative References
[RFC1700] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC [RFC1700] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC
1700, October 1994. 1700, October 1994.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Harvard University, Requirement Levels", BCP 14, RFC 2119, Harvard University,
March 1997 March 1997
[RFC2115] Brown, C., and F. Baker, "Management Information Base for
Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of
Textual Conventions and OBJECT-IDENTITIES for ATM
Management", RFC 2514, February 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB
using SMIv2", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, January 2001. Label Switching Architecture", RFC 3031, January 2001.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci,
D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC
3032, January 2001. 3032, January 2001.
[RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching
on Frame Relay Networks Specification", RFC 3034, January on Frame Relay Networks Specification", RFC 3034, January
2001. 2001.
skipping to change at page 123, line 5 skipping to change at page 124, line 14
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B.
Thomas, "LDP Specification", RFC 3036, January 2001. Thomas, "LDP Specification", RFC 3036, January 2001.
[RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037,
January 2001. January 2001.
[RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State
Machine", RFC 3215, January 2002. Machine", RFC 3215, January 2002.
[RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information
Base for the Differentiated Services Architecture", RFC
3289, May 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.
Schoenwaelder, "Textual Coventions for Internet Network
Addresses", RFC 3291, May 2002.
[LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label
Switching Router Management Information Base Using SMIv2", Switching Router Management Information Base Using SMIv2",
draft-ietf-mpls-lsr-mib-08.txt, January 2002. draft-ietf-mpls-lsr-mib-09.txt, October 2003.
[MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual
Conventions for Multiprotocol Label Switching Management", Conventions for Multiprotocol Label Switching Management",
draft-ietf-mpls-tc-mib-06.txt, March 2003. draft-ietf-mpls-tc-mib-06.txt, March 2003.
8. Informative References 8. Informative References
[RFC2115] Brown, C., and F. Baker, "Management Information Base for [RFC2115] Brown, C., and F. Baker, "Management Information Base for
Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of
Textual Conventions and OBJECT-IDENTITIES for ATM Textual Conventions and OBJECT-IDENTITIES for ATM
Management", RFC 2514, February 1999. Management", RFC 2514, February 1999.
[RFC2515] Tesink, K. (ed.) "Definitions of Managed Objects for ATM
Management", RFC 2515, February 1999.
[RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB
using SMIv2", RFC 2863, June 2000.
[RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation
over ATM Adaptation Layer 5", RFC 2684, September 1999. over ATM Adaptation Layer 5", RFC 2684, September 1999.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.
Schoenwaelder, "Textual Coventions for Internet Network
Addresses", RFC 3291, May 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Label Switching (MPLS) Management Overview", draft-ietf- Label Switching (MPLS) Management Overview", draft-ietf-
mpls-mgmt-overview-03.txt, February 2003. mpls-mgmt-overview-04.txt, May 2003.
9. Security Considerations 9. Security Considerations
This Security Considerations section consists of 4 subsections, one This Security Considerations section consists of 4 subsections, one
for each of the MIB Modules in this document. for each of the MIB Modules in this document.
9.1. Security Considerations for MPLS-LDP-MIB 9.1. Security Considerations for MPLS-LDP-STD-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityTable contains objects to provision potential o the mplsLdpEntityTable contains objects to provision potential
skipping to change at page 125, line 33 skipping to change at page 126, line 23
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and
mplsLdpSesStatsTable collectively show the LDP LSP network mplsLdpSesStatsTable collectively show the LDP LSP network
topology. If an Administrator does not want to reveal the LDP topology. If an Administrator does not want to reveal the LDP
LSP topology of the network, then these tables should be LSP topology of the network, then these tables should be
considered sensitive/vulnerable. considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. 9.2. Security Considerations for MPLS-LDP-ATM-STD-MIB
Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them.
9.2. Security Considerations for MPLS-LDP-ATM-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain
skipping to change at page 126, line 43 skipping to change at page 127, line 15
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the
Label Ranges for ATM. If an Administrator does not want to Label Ranges for ATM. If an Administrator does not want to
reveal this information then these tables should be considered reveal this information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
SNMP versions prior to SNMPv3 did not include adequate security. 9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB
Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them.
9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityFrameRelayTable and o the mplsLdpEntityFrameRelayTable and
skipping to change at page 128, line 11 skipping to change at page 128, line 11
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityFrameRelayTable and o the mplsLdpEntityFrameRelayTable and
mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame
Relay. If an Administrator does not want to reveal this Relay. If an Administrator does not want to reveal this
information then these tables should be considered information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
SNMP versions prior to SNMPv3 did not include adequate security. 9.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB
Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them.
9.4. Security Considerations for MPLS-LDP-GENERIC-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityGenericLRTable contains objects to provision o the mplsLdpEntityGenericLRTable contains objects to provision
skipping to change at page 129, line 21 skipping to change at page 129, line 5
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityGenericLRTable shows the Label Ranges for o the mplsLdpEntityGenericLRTable shows the Label Ranges for
ethernet. If an Administrator does not want to reveal this ethernet. If an Administrator does not want to reveal this
information then these tables should be considered information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
9.5. Additional Security Considerations
The following paragraphs describe additional security considerations
which are applicable to all 4 of the MIB Modules in this document.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8", provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy". authentication and privacy".
skipping to change at page 129, line 42 skipping to change at page 129, line 31
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
10. IANA Considerations 10. IANA Considerations
As described in [MPLSMGMT] and as stated in the MPLS-TC-MIB As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
[MPLSTCMIB], MPLS related standards track MIB modules should be [MPLSTCMIB], MPLS related standards track MIB modules should be
rooted under the mplsMIB subtree. There are 4 MPLS MIB Modules rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections requests IANA for a new assignment under
the mplsMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
10.1. IANA Considerations for the MPLS-LDP-MIB Module 10.1. IANA Considerations for the MPLS-LDP-STD-MIB Module
The IANA is requested to assign { mplsMIB 4 } to the MPLS-LDP-MIB The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD-
module specified in this document. MIB module specified in this document.
10.2. IANA Considerations for the MPLS-LDP-ATM-MIB Module 10.2. IANA Considerations for the MPLS-LDP-ATM-STD-MIB Module
The IANA is requested to assign { mplsMIB 5 } to the MPLS-LDP-ATM-MIB The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM-
module specified in this document. STD-MIB module specified in this document.
10.3. IANA Considerations for the MPLS-LDP-FRAME-RELAY-MIB Module 10.3. IANA Considerations for the MPLS-LDP-FRAME-RELAY-STD-MIB Module
The IANA is requested to assign { mplsMIB 6 } to the MPLS-LDP-FRAME- The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP-
RELAY-MIB module specified in this document. FRAME-RELAY-STD-MIB module specified in this document.
10.4. IANA Considerations for the MPLS-LDP-GENERIC-MIB Module 10.4. IANA Considerations for the MPLS-LDP-GENERIC-STD-MIB Module
The IANA is requested to assign { mplsMIB 7 } to the MPLS-LDP- The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP-
GENERIC-MIB module specified in this document. GENERIC-STD-MIB module specified in this document.
11. Intellectual Property Notice 11. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/