draft-ietf-mpls-ldp-mib-11.txt   draft-ietf-mpls-ldp-mib-12.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft Artel Internet-Draft Artel
Expires December 2003 H. Sjostrand Expires December 2003 H. Sjostrand
IP Unplugged IP Unplugged
J. Luciani J. Luciani
Consultant Consultant
June 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-11.txt> <draft-ietf-mpls-ldp-mib-12.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 9 skipping to change at page 2, line 9
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for the Multiprotocol In particular, it describes managed objects for the Multiprotocol
Label Switching, Label Distribution Protocol (LDP). Label Switching, Label Distribution Protocol (LDP).
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 Modules ................................. 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-STD-MIB Module ................................ 5 3.5 The MPLS-LDP-STD-MIB Module ................................ 6
3.5.1 The LDP Entity Table ..................................... 6 3.5.1 LDP Scalar Objects ....................................... 6
3.5.1.1 Changing Values After Session Establishment ............ 6 3.5.2 The LDP Entity Table ..................................... 6
3.5.2 The LDP Entity Statistics Table .......................... 7 3.5.2.1 Changing Values After Session Establishment ............ 7
3.5.3 The LDP Peer Table ....................................... 7 3.5.3 The LDP Entity Statistics Table .......................... 8
3.5.4 The LDP Session Table .................................... 8 3.5.4 The LDP Peer Table ....................................... 8
3.5.5 The LDP Session Statistics Table ......................... 8 3.5.5 The LDP Session Table .................................... 9
3.5.6 The LDP Hello Adjacencies Table .......................... 8 3.5.6 The LDP Session Statistics Table ......................... 9
3.5.7 The LDP LSP Table ........................................ 8 3.5.7 The LDP Hello Adjacency Table ............................ 9
3.5.8 The FEC Table ............................................ 9 3.5.8 The LDP LSP Table ........................................ 9
3.5.9 The LDP Session Peer Address Table ....................... 9 3.5.9 The FEC Table ............................................ 10
3.5.10 The LDP Session Peer Address Table ...................... 10
3.6 LDP Notifications .......................................... 10 3.6 LDP Notifications .......................................... 10
3.7 LDP Notification Frequency ................................. 10 3.7 LDP Notification Frequency ................................. 11
4 MPLS Label Distribution Protocol MIB Definitions ............. 10 4 MPLS Label Distribution Protocol MIB Definitions ............. 11
4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 64 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 65
4.1.1 The LDP ATM Session Table ................................ 64 4.1.1 The LDP Entity ATM Table ................................. 65
4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 81 4.1.2 The LDP Entity ATM Label Range Table ..................... 65
4.2.1 The LDP Frame Relay Session Table ........................ 82 4.1.3 The LDP ATM Session Table ................................ 65
4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 96 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 82
5 Revision History ............................................. 104 4.2.1 The LDP Entity Frame Relay Table ........................ 82
5.1 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 104 4.2.2 The LDP Entity Frame Relay Label Range Table ............. 83
5.2 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 104 4.2.3 The LDP Frame Relay Session Table ........................ 83
5.2.1 Changes based on MIB Doctor Review Comments .............. 104 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 97
5.3 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 109 5 Revision History ............................................. 105
5.4 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 111 5.1 Changes from <draft-ietf-mpls-ldp-mib-11.txt> .............. 105
5.5 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 112 5.2 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 105
5.6 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 113 5.3 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 105
5.7 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 115 5.3.1 Changes based on MIB Doctor Review Comments .............. 106
5.8 Changes from <draft-ietf-mpls-ldp-mib-03.txt> .............. 117 5.4 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 110
5.9 Changes from <draft-ietf-mpls-ldp-mib-02.txt> .............. 119 5.5 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 113
5.10 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 119 5.6 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 114
5.11 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 120 5.7 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 114
6 Acknowledgments .............................................. 121 5.8 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 116
7 Normative References ......................................... 122 5.9 Changes from <draft-ietf-mpls-ldp-mib-03.txt> .............. 118
8 Informative References ....................................... 124 5.10 Changes from <draft-ietf-mpls-ldp-mib-02.txt> ............. 120
9 Security Considerations ...................................... 124 5.11 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 121
9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 124 5.12 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 122
9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 125 6 Acknowledgments .............................................. 124
........................................................... 126 7 Normative References ......................................... 125
9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 127 8 Informative References ....................................... 127
9.5 Additional Security Considerations ......................... 128 9 Security Considerations ...................................... 127
10 IANA Considerations ......................................... 128 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 127
10.1 IANA Considerations for the MPLS-LDP-STD-MIB Module ....... 128 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 128
........................................................... 129 9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 129
...................................................... 129 9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 130
Module .................................................... 129 9.5 Additional Security Considerations ......................... 130
11 Intellectual Property Notice ................................ 129 10 IANA Considerations ......................................... 131
12 Authors' Addresses .......................................... 129 10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 131
13 Full Copyright Statement .................................... 130 10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 131
10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 131
10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 132
11 Intellectual Property Notice ................................ 132
12 Authors' Addresses .......................................... 132
13 Full Copyright Statement .................................... 133
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.
The Layer 2 media supported by the MIB Modules are Ethernet, ATM and The Layer 2 media supported by the MIB Modules are Ethernet, ATM and
skipping to change at page 5, line 5 skipping to change at page 5, line 5
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
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 Modules
This section describes the structure of the LDP MIB. This section describes the structure of the LDP MIB Modules.
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-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD- MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD-
MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB
defines objects which are common to all LDP implementations. The defines objects which are common to all LDP implementations. The
MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space
objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB
defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with
the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer
2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB. 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB.
The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of
the Layer 2 MIB Modules MUST be implemented. As an example, if an the Layer 2 MIB Modules MUST be implemented by an Agent developer on
Label Switching Router (LSR) or Label Edge Router (LER) an Label Switching Router (LSR) or Label Edge Router (LER). As an
implementation intends to support LDP utilizing a Layer 2 of example, if an Label Switching Router (LSR) or Label Edge Router
(LER) implementation intends to support LDP utilizing a Layer 2 of
Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB
Modules MUST implemented. If an LSR/LER implementation intends to Modules MUST implemented. If an LSR/LER implementation intends to
support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB
Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an
LSR/LER implementation intends to support LDP utilizing a Layer 2 of LSR/LER implementation intends to support LDP utilizing a Layer 2 of
FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME- FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME-
RELAY-STD-MIB Module MUST be implemented. An LDP implementation that RELAY-STD-MIB Module MUST be implemented. An LDP implementation that
utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST
support all 4 MIB Modules. Each of the Modules will be discussed in support all 4 MIB Modules. Each of the Modules will be discussed in
detail in the following sections. 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
for full compliance which includes configuration and monitoring via compliance statement is for full compliance which allows both
SNMP. The other is a read-only compliance which allows SNMP to configuration and monitoring via SNMP. The other compliance
monitor. statement is for read-only compliance which allows only monitoring
via SNMP.
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. been included.
[RFC2684] does not describe VP merge capability and so this feature [RFC2684] does not describe VP merge capability and so this feature
has not been included. has not been included.
skipping to change at page 6, line 18 skipping to change at page 6, line 21
3.3. Interface Indexing 3.3. Interface Indexing
Interface Indexes as specified in [RFC2863] are used in these MIB Interface Indexes as specified in [RFC2863] are used in these MIB
Modules. The descriptions of the ifIndexes denote which ifIndex is Modules. The descriptions of the ifIndexes denote which ifIndex is
being used. 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 document is almost LDP Specification. As described in the Introduction, this document
entirely based on the LDP specification. The differences are is almost entirely based on the LDP specification. The differences
documented here. are documented here.
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
thus, have been adopted within this MPLS-LDP-STD-MIB. Please note, and thus, have been adopted within this MPLS-LDP-STD-MIB module.
they can certainly be changed during row creation or a subsequent set Please note, they can certainly be changed during row creation or a
request. subsequent SET request.
A second difference is the mplsLdpEntityConfGenericLRTable in the A second difference is the mplsLdpEntityConfGenericLRTable in the
MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a
way to reserve a range of generic labels, does not exist in the LDP way to reserve a range of generic labels, does not exist in the LDP
Specification. It was added to the MIB due to a request from the Specification. It was added to the MIB due to a request from the
working group and because this table was considered useful for working group and because this table was considered useful for
reserving a range of generic labels. 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-STD-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.
This table allows the Label Edge Router (LER) or the Label Switching This table allows the Label Edge Router (LER) or the Label Switching
router (LSR) to initiate and/or receive requests to establish LDP Router (LSR) to initiate and/or receive requests to establish LDP
sessions. As the LDP protocol distributes labels and establishes sessions. As the LDP protocol distributes labels and establishes
sessions with Peers most of the tables in this MIB are populated by sessions with Peers most of the tables in this module are populated
the agent as instructed by the LDP protocol. The exception is the by the agent as instructed by the LDP protocol. The exception is the
mplsFecTable and the mplsLdpLspFecTable which can be configured by mplsFecTable and the mplsLdpLspFecTable which can be configured by
the operator to specify Forwarding Equivalence Class information for the operator to specify Forwarding Equivalence Class information for
an LSP. an LSP.
Each table in the MPLS-LDP-STD-MIB Module is described in the Some scalars and each table in the MPLS-LDP-STD-MIB Module is
following subsections. described in the following subsections.
3.5.1. The LDP Entity Table 3.5.1. LDP Scalar Objects
The MPLS-LDP-STD-MIB provides objects to configure or allow potential There are several scalar objects in the LDP MIB module. The
mplsLdpLsrId is a read-only scalar object which reports Lable
Switching Router's (LSR's) Identifier. This MUST be a globally
unique value, such as the 32-bit router ID assigned to the LSR.
The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the
LSR is capable of supporting loop detection and if so, which form of
loop detection.
There are two LastChange scalar objects, mplsLdpEntityLastChange and
mplsLdpPeerLastChange. These objects give an indication of there was
a change in the number of entries in the table, or if any of the
values in the respective tables changed. Please see the object's
description for more details.
The mplsLdpEntityIndexNext scalar object is described in the next
section.
3.5.2. The LDP Entity Table
The MPLS-LDP-STD-MIB provides objects to configure/set-up potential
LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used
to configure potential LDP Sessions, where each row in the table to configure information which is used by the LDP protocol to setup
represents a potential LDP Session. potential LDP Sessions.
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
not able to create another LDP Entity at that time. LSR/LER is not able to create another LDP Entity at that time.
3.5.1.1. Changing Values After Session Establishment 3.5.2.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 Assuming that the configuration was done correctly, then a new
skipping to change at page 8, line 8 skipping to change at page 8, line 34
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 and Session statistics (i.e. relevant row in the
mplsLdpSessionTable). Also, if the LSR MIB is implemented and the mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [LSRMIB]
optional Mapping Table objects are implemented, then all information is implemented and the optional Mapping Table objects are
related to the LSPs in this session should be removed from these implemented, then all information related to the LSPs in this session
MIBs. [For more information please see the section on "The Mapping should be removed from these MIB modules. [For more information
Tables".] At this point, the operator could modify the Label Range. please see the section on "The Mapping Tables".] At this point, the
Lastly, the operator should set the mplsLdpEntityAdminStatus to operator could modify the Label Range. Lastly, the operator should
"enable(1)". At this point session initialization should occur. The set the mplsLdpEntityAdminStatus to "enable(1)". At this point
LDP Entity goes through the Session Initialization in order to session initialization should occur. The LDP Entity goes through the
communicate the new Label Ranges to the Peer and establish new LSPs. Session Initialization in order to communicate the new Label Ranges
to the Peer and establish new LSPs.
3.5.2. The LDP Entity Statistics Table 3.5.3. 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 AUGMENTS an mplsLdpEntityEntry.
and this table AUGMENTS an mplsLdpEntityEntry. This table could be This table could be used to give insight into how to reconfigure
used to give insight into how to reconfigure values so that a session values so that a session could be successfully established. For
could be successfully established. For example, if the example, if the mplsLdpEntityStatsSessionRejectedLRErrors Counter
mplsLdpSesRejectedLRErrors Counter object was increasing, then this object was increasing, then this would indicate that the Label Range
would indicate that the Label Range (LR) may need to be adjusted. (LR) may need to be adjusted.
3.5.3. The LDP Peer Table 3.5.4. The LDP Peer Table
The LDP Peer Table is a read-only table which contains information The mplsLdpPeerTable is a read-only table which contains information
about LDP Peers known to LDP Entities. In other words, the Peer about LDP Peers known to LDP Entities. In other words, the Peer
information is learned by LDP through initialization or discovery. information is learned by LDP through initialization or discovery.
This table should be populated by the agent as directed by the LDP This table should be populated by the agent as directed by the LDP
protocol. protocol.
A row in this table is related to one or more rows in the Hello A row in this table is related to one or more rows in the Hello
Adjacency Table and related to a single row in the Session Table. Adjacency Table and related to a single row in the Session Table.
The values in the Peer table are specific to a Peer and may or may The values in the Peer table are specific to a Peer and may or may
not be the same values used in the session. The reason is that the not be the same values used in the session. The reason is that the
Peer and Entity negotiate certain values. The Entity's values are Peer and Entity negotiate certain values. The Entity's values are
skipping to change at page 9, line 18 skipping to change at page 10, line 5
The actual value for the Path Vector Limit is the Peer's value and The actual value for the Path Vector Limit is the Peer's value and
may not be the same value that appears in the session. There could may not be the same value that appears in the session. There could
be a mismatch in this value between the Entity and the Peer. In the be a mismatch in this value between the Entity and the Peer. In the
event of a mismatch, then the session will use the Path Limit set by event of a mismatch, then the session will use the Path Limit set by
the Entity (and not the Peer). the Entity (and not the Peer).
The Peer Table information was placed in a separate table from the The Peer Table information was placed in a separate table from the
Session information to allow for a more comprehensive and coherent Session information to allow for a more comprehensive and coherent
MIB model. MIB model.
3.5.4. The LDP Session Table 3.5.5. The LDP Session Table
The LDP Session Table is a read-only table. Each entry in this table The LDP Session Table is a read-only table. Each entry in this table
represents a single session between an LDP Entity and a Peer. The represents a single session between an LDP Entity and a Peer. The
mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry.
The information in this table is learned during session The information in this table is learned during session
establishment. NOTE: rows in this table will appear during session establishment. NOTE: rows in this table will appear during session
intialization. intialization.
3.5.5. The LDP Session Statistics Table 3.5.6. The LDP Session Statistics Table
The MPLS LDP Session Stats Table is a read-only table which contains The mplsLdpSessionStatsTable is a read-only table which contains
statistical information on sessions. statistical information on sessions. This table AUGMENTS the
mplsLdpPeerTable.
3.5.6. The LDP Hello Adjacencies Table 3.5.7. The LDP Hello Adjacency Table
This is a table of all adjacencies between all LDP Entities and all This is a table of all adjacencies between all LDP Entities and all
LDP Peers. A Session may have one or more adjacencies. A session LDP Peers. A Session may have one or more adjacencies. A session
should not have zero adjacencies, because this indicates that the should not have zero adjacencies, because this indicates that the
session has lost contact with the Peer. A session which has zero session has lost contact with the Peer. A session which has zero
Hello Adjacencies should be eventually removed. Hello Adjacencies should be removed.
3.5.7. The LDP LSP Table 3.5.8. The LDP LSP Table
The Label Information Base (LIB) contains information about labels The Label Information Base (LIB) contains information about labels
learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all
currently defined MPLS protocols) is represented in the LSR MIB currently defined MPLS protocols) is represented in the LSR MIB
[LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls
Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and
the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable
models the cross-connection of the ingress label with a specific models the cross-connection of the incoming label with a specific
egress label. The mplsInSegmentTable stores the ingress label's outgoing label. The mplsInSegmentTable stores the incoming label's
information, and the mplsOutSegmentTable stores the egress label's information, and the mplsOutSegmentTable stores the outgoing label's
information. information.
The LDP Session that created the LSP and the LSP's (ingress label, The LDP Session that created the LSP and the LSP's (incoming label,
egress label) pair along with other information is contained in the outgoing label) pair along with other information is contained in the
LSR MIB's mplsXCTable, the mplsInSegmentTable and the MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the
mplsOutSegmentTable. mplsOutSegmentTable.
In order to utilize the LSR MIB's mplsXCTable, mplsInSegmentTable and In order to utilize the MPLS-LSR-STD-MIB module's mplsXCTable,
mplsOutSegmentTable for LDP LSPs, there needs to be a mechanism to mplsInSegmentTable and mplsOutSegmentTable for LDP LSPs, there needs
associate LDP sessions with LDP LSPs created as a result of those LDP to be a mechanism to associate LDP sessions with LDP LSPs created as
sessions. The mplsInSegmentLdpLspTable and mplsOutSegmentLdpLspTable a result of those LDP sessions. The mplsInSegmentLdpLspTable and
in this MIB contain information to find the LDP LSP entries in the mplsOutSegmentLdpLspTable in this MIB contain information to find the
mplsInSegmentTable, mplsOutSegmentTable and the mplsXCTable. LDP LSP entries in the mplsInSegmentTable, mplsOutSegmentTable and
the mplsXCTable.
These two tables, the mplsInSegmentLdpLspTable and These two tables, the mplsInSegmentLdpLspTable and
mplsOutSegmentLdpLspTable, have been made optional in the conformance mplsOutSegmentLdpLspTable, have been made optional in the conformance
section of the MIB. They only need to be supported if the LSR MIBs section of the MIB. They only need to be supported if the LSR MIBs
mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are
implemented. implemented.
As discussed in the section, "Changing Values after Session As discussed in the section, "Changing Values after Session
Establishment", if a session is torn down, then all the information Establishment", if a session is torn down, then all the information
related to this session, must be removed from the both LDP MIB and, related to this session, must be removed from the both LDP MIB and,
if implemented, from the LSR MIB. if implemented, from the LSR MIB.
3.5.8. The FEC Table 3.5.9. The FEC Table
The FEC Table is a table which contains FEC (Forwarding Equivalence The FEC Table is a table which contains FEC (Forwarding Equivalence
Class) information. Each entry/row represents a single FEC Element. Class) information. Each entry/row represents a single FEC Element.
There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which
associates FECs with the LSPs. associates FECs with the LSPs.
3.5.9. The LDP Session Peer Address Table 3.5.10. The LDP Session Peer Address Table
The MPLS LDP Session Peer Address Table is a table which extends the The MPLS LDP Session Peer Address Table is a table which extends the
mplsLdpSessionTable. This table is a read-only table which stores mplsLdpSessionTable. This table is a read-only table which stores
Addresses learned after session initialization via Address Message Addresses learned after session initialization via Address Message
advertisement. advertisement.
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. There are no objects
which enable or disable notifications from being generated. RFC 2573
[RFC2573] contains MIB modules which can be implemented that will
enable or disable these notifications from being generated.
The mplsLdpInitSesThresholdExceeded notification indicates to the The mplsLdpInitSessionThresholdExceeded 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 reaching the operational state as indicated by the
mplsLdpSessionState object. If the value of mplsLdpSessionState object. If the value of
mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to
specifying the value of infinity for the threshold, and the specifying the value of infinity for the threshold, and the
mplsLdpInitSessionThresholdExceeded notification will never be sent. mplsLdpInitSessionThresholdExceeded notification will never be sent.
skipping to change at page 11, line 32 skipping to change at page 12, line 23
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 generated when there is an appropriate change in the
mplsLdpSessionState object, e.g. when sessions change state (Up to mplsLdpSessionState object, e.g. when sessions change state (Up to
Down for the mplsLdpSessionDown trap, or Down to Up for the Down for the mplsLdpSessionDown notification, or Down to Up for the
mplsLdpSessionUp trap). mplsLdpSessionUp notification). There was discussion about combining
these two notifications into a single notification, however, some NMS
applications can utilize two different notifications, rather than
having to parse the varbind list of a single notification. For
example, the SessionDown is matched to a SessionUp notification more
easily by some NMS applications, than having to parse a Varbind list
in a SessionChange type of notification.
3.7. LDP Notification Frequency 3.7. LDP Notification Frequency
LDP Notifications are expected to be few in number when LDP is LDP Notifications are expected to be few in number when LDP is
ubiquitously deployed in a relatively stable network. An NMS that is ubiquitously deployed in a relatively stable network. A notification
receiving these notifications should not be overwhelmed by the receiver, e.g. an NMS, that receives these notifications should not
frequency of LDP notifications. If this assertion proves to be be overwhelmed by the frequency of LDP notifications. If this
inaccurate, then a throttling object to throttle these notifications assertion proves to be inaccurate, then a throttling object to
may be added to future versions of the MPLS-LDP-STD-MIB. 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-STD-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
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero
FROM IF-MIB
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
mplsStdMIB, mplsStdMIB,
MplsLabel,
MplsLabelDistributionMethod, MplsLabelDistributionMethod,
MplsLdpIdentifier, MplsLdpIdentifier,
MplsLdpLabelType, MplsLdpLabelType,
MplsLspType, MplsLspType,
MplsLsrIdentifier, MplsLsrIdentifier,
MplsRetentionMode MplsRetentionMode
FROM MPLS-TC-STD-MIB; FROM MPLS-TC-STD-MIB
MplsIndexType
FROM MPLS-LSR-STD-MIB;
mplsLdpStdMIB MODULE-IDENTITY mplsLdpStdMIB MODULE-IDENTITY
LAST-UPDATED "200306091200Z" -- 9 June 2003 LAST-UPDATED "200306281200Z" -- 28 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)
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
skipping to change at page 13, line 22 skipping to change at page 14, line 21
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 "200306091200Z" -- 9 June 2003 REVISION "200306281200Z" -- 28 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 mplsStdMIB subId is 4, e.g. -- The requested mplsStdMIB subId is 4, e.g.
-- ::= { mplsStdMIB 4 } -- ::= { mplsStdMIB 4 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
skipping to change at page 14, line 9 skipping to change at page 15, line 9
-- --
-- The MPLS Label Distribution Protocol's -- The MPLS Label Distribution Protocol's
-- Label Switching Router Objects -- Label Switching Router Objects
-- --
mplsLdpLsrId OBJECT-TYPE mplsLdpLsrId OBJECT-TYPE
SYNTAX MplsLsrIdentifier SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LSR's Identifier." "The Label Switching Router's Identifier."
::= { mplsLdpLsrObjects 1 } ::= { mplsLdpLsrObjects 1 }
mplsLdpLsrLoopDetectionCapable OBJECT-TYPE mplsLdpLsrLoopDetectionCapable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
other(2), other(2),
hopCount(3), hopCount(3),
pathVector(4), pathVector(4),
hopCountAndPathVector(5) hopCountAndPathVector(5)
} }
skipping to change at page 17, line 17 skipping to change at page 18, line 17
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.
That value should be used for the value of this index That value should be used for the value of this index
when creating a row in this table. (NOTE: if a value when creating a row in this table. NOTE: if a value
of zero (0) is retrieved, that indicates that no rows of zero (0) is retrieved, that indicates that no rows
can be created in this table at this time. can be created in this table at this time.
A secondary index (this object) is meaningful to some A secondary index (this object) is meaningful to some
but not all, LDP implementations. For example but not all, LDP implementations. For example
in an LDP implementation which uses PPP would an LDP implementation which uses PPP would
use this index to differentiate PPP sub-links. use this index to differentiate PPP sub-links.
Another way to use this index is to give this the Another way to use this index is to give this the
value of ifIndex. However, this is dependant value of ifIndex. However, this is dependant
on the implementation." on the implementation."
::= { mplsLdpEntityEntry 2 } ::= { mplsLdpEntityEntry 2 }
mplsLdpEntityProtocolVersion OBJECT-TYPE mplsLdpEntityProtocolVersion OBJECT-TYPE
SYNTAX Unsigned32(1..65535) SYNTAX Unsigned32(1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 18, line 42 skipping to change at page 19, line 42
mplsLdpEntityOperStatus OBJECT-TYPE mplsLdpEntityOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
enabled(2), enabled(2),
disabled(3) disabled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational status of this LDP Entity." "The operational status of this LDP Entity.
The value of unknown(1) indicates that the
operational status cannot be determined at
this time. The value of unknown should be
a transient condition before changing
to enabled(2) or disabled(3)."
::= { mplsLdpEntityEntry 5 } ::= { mplsLdpEntityEntry 5 }
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."
skipping to change at page 21, line 24 skipping to change at page 22, line 30
"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 }
mplsLdpEntityInitSessionThreshold 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
given Peer, the given LDP Entity should a given Peer, the given LDP Entity should
send out the SNMP notification, send out the SNMP notification,
'mplsLdpInitSesThresholdExceeded', when 'mplsLdpInitSessionThresholdExceeded', when
the number of Session Initialization messages sent the number of Session Initialization messages
exceeds this threshold. The notification is sent exceeds this threshold.
used to notify an operator when this Entity and
its Peer are possibily engaged in an endless The notification is used to notify an
sequence of messages as each NAKs the other's operator when this Entity and its Peer are
possibily engaged in an endless 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
notify the operator. operator. The notification should be generated
each time this threshold is exceeded and
for every subsequent Initialization message
which is NAK'd with an Error Notification
message after this threshold is exceeded.
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 }
skipping to change at page 24, line 30 skipping to change at page 25, line 43
the Extended Discovery. This object indicates how the Extended Discovery. This object indicates how
the value of mplsLdpEntityTargetPeerAddr is to the value of mplsLdpEntityTargetPeerAddr is to
be interpreted." be interpreted."
::= { mplsLdpEntityEntry 18 } ::= { mplsLdpEntityEntry 18 }
mplsLdpEntityTargetPeerAddr OBJECT-TYPE mplsLdpEntityTargetPeerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the internetwork layer address used for "The value of the internetwork layer address
the Extended Discovery." used for the Extended Discovery. The value of
mplsLdpEntityTargetPeerAddrType specifies how
this address is to be intepreted."
::= { mplsLdpEntityEntry 19 } ::= { mplsLdpEntityEntry 19 }
mplsLdpEntityLabelType OBJECT-TYPE mplsLdpEntityLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType SYNTAX MplsLdpLabelType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the optional parameters for the LDP "Specifies the optional parameters for the LDP
Initialization Message. If the value is generic(1) Initialization Message.
then no optional parameters will be sent in
the LDP Initialization message associated with If the value is generic(1) then no
this Entity. optional parameters will be sent in
the LDP Initialization message associated
with 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
Table, which corresponds to this entry. mplsLdpEntityAtmTable, 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
Table, which corresponds to this entry." mplsLdpEntityFrameRelayTable, 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
specific instances associated with this entity of are the specific instances associated with this
any Counter32, or Counter64 object contained entity of any Counter32 object contained
in the 'mplsLdpEntityStatsTable'. If no such in the 'mplsLdpEntityStatsTable'. If no such
discontinuities have occurred since the last discontinuities have occurred since the last
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
skipping to change at page 26, line 42 skipping to change at page 28, line 16
mplsLdpEntityStatsEntry OBJECT-TYPE mplsLdpEntityStatsEntry OBJECT-TYPE
SYNTAX MplsLdpEntityStatsEntry SYNTAX MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table contains statistical information "A row in this table contains statistical information
about an LDP Entity. Some counters contained in a about an LDP Entity. Some counters contained in a
row are for fatal errors received during a former row are for fatal errors received during a former
LDP Session associated with this entry. For example, LDP Session associated with this entry. For example,
an Ldp Pdu received on a TCP connection during an an LDP PDU received on a TCP connection during an
LDP Session contains a fatal error. That LDP Session contains a fatal error. That
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. the Session
remains), then the error is counted in the remains), then the error is counted in the
mplsLdpSesStatsEntry." mplsLdpSessionStatsEntry."
AUGMENTS { mplsLdpEntityEntry } AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 } ::= { mplsLdpEntityStatsTable 1 }
MplsLdpEntityStatsEntry ::= SEQUENCE { MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEntityStatsSessionAttempts Counter32, mplsLdpEntityStatsSessionAttempts Counter32,
mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32, mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32,
mplsLdpEntityStatsSessionRejectedAdErrors Counter32, mplsLdpEntityStatsSessionRejectedAdErrors Counter32,
mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32, mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32,
mplsLdpEntityStatsSessionRejectedLRErrors Counter32, mplsLdpEntityStatsSessionRejectedLRErrors Counter32,
mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, mplsLdpEntityStatsBadLdpIdentifierErrors Counter32,
skipping to change at page 27, line 29 skipping to change at page 28, line 48
mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32,
mplsLdpEntityStatsShutdownReceivedNotifications Counter32, mplsLdpEntityStatsShutdownReceivedNotifications Counter32,
mplsLdpEntityStatsShutdownSentNotifications Counter32 mplsLdpEntityStatsShutdownSentNotifications Counter32
} }
mplsLdpEntityStatsSessionAttempts 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 Session Initialization messages
this LDP Entity. which were sent or received by this LDP Entity and
were NAK'd. In other words, this counter counts
the number of session initializations that failed.
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 }
mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 29, line 29 skipping to change at page 31, line 5
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 }
skipping to change at page 34, line 5 skipping to change at page 35, line 26
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 type of the Internet address for the "The type of the Internet address for the
mplsLdpPeerTransportAddr object. The LDP mplsLdpPeerTransportAddr object. The LDP
specification describes this as being either specification describes this as being either
an IPv4 Transport Address or IPv6 Transport an IPv4 Transport Address or IPv6 Transport
Address which is ued in opening the LDP session's Address which is used in opening the LDP session's
TCP connection, or if the optional TLV is not TCP connection, or if the optional TLV is not
present, then this is the IPv4/IPv6 source present, then this is the IPv4/IPv6 source
address for the UPD packet carrying the Hellos." address for the UPD packet carrying the Hellos.
This object specifies how the value of the
mplsLdpPeerTransportAddr object should be
interpreted."
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 Internet address advertised 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 The type of this address is specified by the
value of the mplsLdpPeerTransportAddrType value of the mplsLdpPeerTransportAddrType
object." 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
-- --
mplsLdpSessionTable OBJECT-TYPE mplsLdpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionEntry 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
LDP Peers. Each row represents a single session." and LDP Peers. This table AUGMENTS the
mplsLdpPeerTable. Each row in this table
represents a single session."
::= { mplsLdpSessionObjects 3 } ::= { mplsLdpSessionObjects 3 }
mplsLdpSessionEntry OBJECT-TYPE mplsLdpSessionEntry OBJECT-TYPE
SYNTAX MplsLdpSessionEntry 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.
skipping to change at page 35, line 45 skipping to change at page 37, line 26
mplsLdpSessionKeepAliveTime Unsigned32, mplsLdpSessionKeepAliveTime Unsigned32,
mplsLdpSessionMaxPduLength Unsigned32, mplsLdpSessionMaxPduLength Unsigned32,
mplsLdpSessionDiscontinuityTime TimeStamp mplsLdpSessionDiscontinuityTime TimeStamp
} }
mplsLdpSessionStateLastChange 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
its current state as denoted by the mplsLdpSessionState object." Session entered its current state as
denoted by the mplsLdpSessionState
object."
::= { mplsLdpSessionEntry 1 } ::= { mplsLdpSessionEntry 1 }
mplsLdpSessionState 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
session negotiation behavior." for 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."
::= { mplsLdpSessionEntry 2 } ::= { mplsLdpSessionEntry 2 }
mplsLdpSessionRole 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/LER takes either the "During session establishment the LSR/LER takes either
active role or the passive role based on address the active role or the passive role based on address
comparisons. This object indicates whether this LSR/LER 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 session's 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"
::= { mplsLdpSessionEntry 3 } ::= { mplsLdpSessionEntry 3 }
mplsLdpSessionProtocolVersion 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
session initialization." during session initialization."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSessionEntry 4 } ::= { mplsLdpSessionEntry 4 }
mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 38, line 22 skipping to change at page 40, line 4
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."
::= { mplsLdpSessionEntry 7 } ::= { mplsLdpSessionEntry 7 }
mplsLdpSessionDiscontinuityTime 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
which any one or more of this session's counters at 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 object contained in the
mplsLdpSessionStatsTable. 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."
skipping to change at page 39, line 4 skipping to change at page 40, line 29
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."
::= { mplsLdpSessionEntry 8 } ::= { mplsLdpSessionEntry 8 }
-- --
-- The MPLS LDP Session Statistics Table -- The MPLS LDP Session Statistics Table
-- --
mplsLdpSessionStatsTable OBJECT-TYPE mplsLdpSessionStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry
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. This table AUGMENTS
the mplsLdpPeerTable."
::= { mplsLdpSessionObjects 4 } ::= { mplsLdpSessionObjects 4 }
mplsLdpSessionStatsEntry OBJECT-TYPE mplsLdpSessionStatsEntry OBJECT-TYPE
SYNTAX MplsLdpSessionStatsEntry 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."
skipping to change at page 39, line 35 skipping to change at page 41, line 18
mplsLdpSessionStatsUnknownMesTypeErrors Counter32, mplsLdpSessionStatsUnknownMesTypeErrors Counter32,
mplsLdpSessionStatsUnknownTlvErrors Counter32 mplsLdpSessionStatsUnknownTlvErrors Counter32
} }
mplsLdpSessionStatsUnknownMesTypeErrors 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 by this LSR/LER 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."
::= { mplsLdpSessionStatsEntry 1 } ::= { mplsLdpSessionStatsEntry 1 }
mplsLdpSessionStatsUnknownTlvErrors 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 by this LSR/LER 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."
::= { mplsLdpSessionStatsEntry 2 } ::= { mplsLdpSessionStatsEntry 2 }
-- --
-- The MPLS LDP Hello Adjacency Table -- The MPLS LDP Hello Adjacency Table
-- --
skipping to change at page 40, line 32 skipping to change at page 42, line 16
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
SYNTAX MplsLdpHelloAdjacencyEntry SYNTAX MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents a single LDP Hello Adjacency. "Each row represents a single LDP Hello Adjacency.
An LDP Session can have one or more Hello adjacencies." An LDP Session can have one or more Hello
Adjacencies."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpHelloAdjacencyIndex } mplsLdpHelloAdjacencyIndex }
::= { mplsLdpHelloAdjacencyTable 1 } ::= { mplsLdpHelloAdjacencyTable 1 }
MplsLdpHelloAdjacencyEntry ::= SEQUENCE { MplsLdpHelloAdjacencyEntry ::= SEQUENCE {
mplsLdpHelloAdjacencyIndex Unsigned32, mplsLdpHelloAdjacencyIndex Unsigned32,
mplsLdpHelloAdjacencyHoldTimeRem TimeInterval, mplsLdpHelloAdjacencyHoldTimeRem TimeInterval,
mplsLdpHelloAdjacencyHoldTime Unsigned32, mplsLdpHelloAdjacencyHoldTime Unsigned32,
skipping to change at page 41, line 20 skipping to change at page 43, line 5
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 65535, "If the value of this object is 65535,
this means that the hold time is infinite this means that the hold time is infinite
(i.e. wait forever). (i.e. wait forever).
Otherwise, the time remaining for Otherwise, the time remaining for
this Hello Adjacency to receive its this Hello Adjacency to receive its
next Hello message. 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 unless it Hello Adjacency is received unless it
is infinite." is infinite."
::= { mplsLdpHelloAdjacencyEntry 2 } ::= { mplsLdpHelloAdjacencyEntry 2 }
mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) 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
skipping to change at page 42, line 17 skipping to change at page 44, line 4
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).
Otherwise, it is a result of a 'targeted' Otherwise, it is a result of a 'targeted'
hello, targeted(2)." hello, targeted(2)."
::= { mplsLdpHelloAdjacencyEntry 4 } ::= { mplsLdpHelloAdjacencyEntry 4 }
-- --
-- Session Label (LSP) Mapping to LSR MIB's In Segment LIB Information. -- Session Label (LSP) Mapping to LSR MIB's
-- In Segment LIB Information.
-- --
-- --
-- NOTE: the next 2 tables map to the MPLS-LSR-MIB's MplsInSegmentTable -- NOTE: the next 2 tables map to the
-- and MplsOutSegmentTable. The cross-connect information is not -- MPLS-LSR-STD-MIB's MplsInSegmentTable
-- represented here as it can be gleaned from the MPLS-LSR-MIB. -- and MplsOutSegmentTable. The
-- cross-connect (XC) information is not
-- represented here as it can be gleaned
-- from the MPLS-LSR-STD-MIB.
-- --
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 mplsInSegmentTable in the
the LSR MIB's." the MPLS-LSR-STD-MIB module."
::= { mplsLdpSessionObjects 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
single LDP LSP which is represented by on a 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
index tuple (mplsInSegmentLdpLspIfIndex, index for the mplsInSegmentTable
mplsInSegmentLdpLspLabel). (mplsInSegmentLdpLspLabelIndex) from the
MPLS-LSR-STD-MIB.
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,
mplsInSegmentLdpLspIfIndex, mplsInSegmentLdpLspIndex
mplsInSegmentLdpLspLabel
} }
::= { mplsInSegmentLdpLspTable 1 } ::= { mplsInSegmentLdpLspTable 1 }
MplsInSegmentLdpLspEntry ::= SEQUENCE { MplsInSegmentLdpLspEntry ::= SEQUENCE {
mplsInSegmentLdpLspIfIndex InterfaceIndexOrZero, mplsInSegmentLdpLspIndex MplsIndexType,
mplsInSegmentLdpLspLabel MplsLabel,
mplsInSegmentLdpLspLabelType MplsLdpLabelType, mplsInSegmentLdpLspLabelType MplsLdpLabelType,
mplsInSegmentLdpLspType MplsLspType mplsInSegmentLdpLspType MplsLspType
} }
mplsInSegmentLdpLspIfIndex OBJECT-TYPE mplsInSegmentLdpLspIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value associated with this LSP which has the "This contains the same value as the
same value as the mplsInSegmentIfIndex in the MPLS-LSR-MIB's mplsInSegmentIndex in the
mplsInSegmentTable." MPLS-LSR-STD-MIB's mplsInSegmentTable."
::= { mplsInSegmentLdpLspEntry 1 } ::= { mplsInSegmentLdpLspEntry 1 }
mplsInSegmentLdpLspLabel OBJECT-TYPE
SYNTAX MplsLabel
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP label for this LSP. This is also the same value
as the mplsInSegmentLabel index in the MPLS-LSR-MIB's
mplsInSegmentTable."
::= { mplsInSegmentLdpLspEntry 2 }
mplsInSegmentLdpLspLabelType OBJECT-TYPE mplsInSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType SYNTAX MplsLdpLabelType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Layer 2 Label Type." "The Layer 2 Label Type."
::= { mplsInSegmentLdpLspEntry 3 } ::= { mplsInSegmentLdpLspEntry 2 }
mplsInSegmentLdpLspType OBJECT-TYPE mplsInSegmentLdpLspType OBJECT-TYPE
SYNTAX MplsLspType SYNTAX MplsLspType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of LSP connection." "The type of LSP connection."
::= { mplsInSegmentLdpLspEntry 4 } ::= { mplsInSegmentLdpLspEntry 3 }
-- --
-- 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 mplsOutSegmentTable in the map to the mplsOutSegmentTable in the
the LSR MIB." the MPLS-LSR-STD-MIB."
::= { mplsLdpSessionObjects 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
single LDP LSP which is represented by on a 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
index tuple (mplsOutSegmentLdpLspIfIndex, index (mplsOutSegmentLdpLspIndex)
mplsOutSegmentLdpLspLabel). for the mplsOutSegmentTable.
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,
mplsOutSegmentLdpLspIfIndex, mplsOutSegmentLdpLspIndex
mplsOutSegmentLdpLspLabel
} }
::= { mplsOutSegmentLdpLspTable 1 } ::= { mplsOutSegmentLdpLspTable 1 }
MplsOutSegmentLdpLspEntry ::= SEQUENCE { MplsOutSegmentLdpLspEntry ::= SEQUENCE {
mplsOutSegmentLdpLspIfIndex InterfaceIndexOrZero, mplsOutSegmentLdpLspIndex MplsIndexType,
mplsOutSegmentLdpLspLabel MplsLabel,
mplsOutSegmentLdpLspLabelType MplsLdpLabelType, mplsOutSegmentLdpLspLabelType MplsLdpLabelType,
mplsOutSegmentLdpLspType MplsLspType mplsOutSegmentLdpLspType MplsLspType
} }
mplsOutSegmentLdpLspIfIndex OBJECT-TYPE mplsOutSegmentLdpLspIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value associated with this LSP which has the "This contains the same value as the
same value as the mplsOutSegmentIfIndex in the MPLS-LSR-MIB's mplsOutSegmentIndex in the
mplsOutSegmentTable. NOTE: the value of zero represents MPLS-LSR-STD-MIB's mplsOutSegmentTable."
the perPlatform label space."
::= { mplsOutSegmentLdpLspEntry 1 } ::= { mplsOutSegmentLdpLspEntry 1 }
mplsOutSegmentLdpLspLabel OBJECT-TYPE
SYNTAX MplsLabel
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP label for this LSP. This is also the same value
as the mplsOutSegmentTopLabel in the MPLS-LSR-MIB's
mplsOutSegmentTable."
::= { mplsOutSegmentLdpLspEntry 2 }
mplsOutSegmentLdpLspLabelType OBJECT-TYPE mplsOutSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType SYNTAX MplsLdpLabelType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Layer 2 Label Type." "The Layer 2 Label Type."
::= { mplsOutSegmentLdpLspEntry 3 } ::= { mplsOutSegmentLdpLspEntry 2 }
mplsOutSegmentLdpLspType OBJECT-TYPE mplsOutSegmentLdpLspType OBJECT-TYPE
SYNTAX MplsLspType SYNTAX MplsLspType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of LSP connection." "The type of LSP connection."
::= { mplsOutSegmentLdpLspEntry 4 } ::= { mplsOutSegmentLdpLspEntry 3 }
-- --
-- Mpls FEC Table -- Mpls FEC Table
-- --
mplsFecObjects OBJECT IDENTIFIER ::= mplsFecObjects OBJECT IDENTIFIER ::=
{ mplsLdpSessionObjects 8 } { mplsLdpSessionObjects 8 }
mplsFecLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most
recent addition/deletion of an entry
to/from the mplsLdpFectTable or
the most recent change in values to any objects
in the mplsLdpFecTable.
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsFecObjects 1 }
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
available." available."
::= { mplsFecObjects 1 } ::= { mplsFecObjects 2 }
mplsFecTable OBJECT-TYPE mplsFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsFecEntry SYNTAX SEQUENCE OF MplsFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the FEC "This table represents the FEC
(Forwarding Equivalence Class) (Forwarding Equivalence Class)
Information associated with an LSP." Information associated with an LSP."
::= { mplsFecObjects 2 } ::= { mplsFecObjects 3 }
mplsFecEntry OBJECT-TYPE mplsFecEntry OBJECT-TYPE
SYNTAX MplsFecEntry SYNTAX MplsFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents a single FEC Element." "Each row represents a single FEC Element."
INDEX { mplsFecIndex } INDEX { mplsFecIndex }
::= { mplsFecTable 1 } ::= { mplsFecTable 1 }
MplsFecEntry ::= SEQUENCE { MplsFecEntry ::= SEQUENCE {
mplsFecIndex IndexInteger, mplsFecIndex IndexInteger,
mplsFecType INTEGER, mplsFecType INTEGER,
mplsFecAddrPrefixLength InetAddressPrefixLength, mplsFecAddrType InetAddressType,
mplsFecAddrFamily InetAddressType,
mplsFecAddr InetAddress, mplsFecAddr InetAddress,
mplsFecAddrPrefixLength InetAddressPrefixLength,
mplsFecStorageType StorageType, mplsFecStorageType StorageType,
mplsFecRowStatus RowStatus mplsFecRowStatus RowStatus
} }
mplsFecIndex OBJECT-TYPE mplsFecIndex OBJECT-TYPE
SYNTAX IndexInteger SYNTAX IndexInteger
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index which uniquely identifies this entry." "The index which uniquely identifies this entry."
skipping to change at page 47, line 24 skipping to change at page 49, line 5
mplsFecType OBJECT-TYPE mplsFecType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
prefix(1), prefix(1),
hostAddress(2) hostAddress(2)
} }
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 an address prefix.
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 mplsFecAddrType OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the value of the 'mplsFecType' is 'hostAddress(2)'
then this object is undefined.
If the value of 'mplsFecType' is 'prefix(1)'
then the value of this object is the length in
bits of the address prefix represented by
'mplsFecAddr', or zero. If the value of this
object is zero, this indicates that the
prefix matches all addresses. In this case the
prefix MUST also be zero (i.e. 'mplsFecAddr' will
have the value of zero.)"
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
DEFVAL { 0 }
::= { mplsFecEntry 3 }
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
type of the address should then be looked up in the Internet address. The value of this object,
ADDRESS FAMILY NUMBERS [RFC1700] for the corresponding entry decides how the value of the mplsFecAddr object
there and this value should be encoded in the FEC TLV." is interpreted."
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 interpreted based
address type is specified by the 'mplsFecAddrFamily' object. on the value of the 'mplsFecAddrType' object.
This address is then used as either an address prefix, This address is then further interpretted as
or as the host address as indicated by the 'mplsFecType' an being used with the address prefix,
object. In other words, the FEC element is populated or as the host address. This further interpretation
is indicated by the 'mplsFecType' 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 }
mplsFecAddrPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the value of the 'mplsFecType' is 'hostAddress(2)'
then this object is undefined.
If the value of 'mplsFecType' is 'prefix(1)'
then the value of this object is the length in
bits of the address prefix represented by
'mplsFecAddr', or zero. If the value of this
object is zero, this indicates that the
prefix matches all addresses. In this case the
address prefix MUST also be zero (i.e. 'mplsFecAddr'
should have the value of zero.)"
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
DEFVAL { 0 }
::= { mplsFecEntry 3 }
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. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
skipping to change at page 49, line 22 skipping to change at page 51, line 7
NOTE: if this row is being referenced by any entry in the NOTE: if this row is being referenced by any entry in the
mplsLdpLspFecTable, then a request to destroy this row, will mplsLdpLspFecTable, then a request to destroy this row, will
result in an inconsistentValue error." result in an inconsistentValue error."
::= { mplsFecEntry 7 } ::= { mplsFecEntry 7 }
-- --
-- LDP LSP FEC Table -- LDP LSP FEC Table
-- --
mplsLdpLspFecLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most
recent addition/deletion of an entry
to/from the mplsLdpLspFecTable or
the most recent change in values to any objects in the
mplsLdpLspFecTable.
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsLdpSessionObjects 9 }
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 LSPs and FECs. Each row represents
a single LSP to FEC association." a single LDP LSP to FEC association."
::= { mplsLdpSessionObjects 9 } ::= { mplsLdpSessionObjects 10 }
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,
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpLspFecSegment, mplsLdpLspFecSegment,
mplsLdpLspFecIfIndex, mplsLdpLspFecSegmentIndex,
mplsLdpLspFecLabel,
mplsLdpLspFecIndex mplsLdpLspFecIndex
} }
::= { mplsLdpLspFecTable 1 } ::= { mplsLdpLspFecTable 1 }
MplsLdpLspFecEntry ::= SEQUENCE { MplsLdpLspFecEntry ::= SEQUENCE {
mplsLdpLspFecSegment INTEGER, mplsLdpLspFecSegment INTEGER,
mplsLdpLspFecIfIndex InterfaceIndexOrZero, mplsLdpLspFecSegmentIndex MplsIndexType,
mplsLdpLspFecLabel MplsLabel,
mplsLdpLspFecIndex IndexInteger, mplsLdpLspFecIndex IndexInteger,
mplsLdpLspFecOperStatus INTEGER,
mplsLdpLspFecLastChange TimeStamp,
mplsLdpLspFecStorageType StorageType, mplsLdpLspFecStorageType StorageType,
mplsLdpLspFecRowStatus RowStatus mplsLdpLspFecRowStatus RowStatus
} }
mplsLdpLspFecSegment OBJECT-TYPE mplsLdpLspFecSegment OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
inSegment(1), inSegment(1),
outSegment(2) outSegment(2)
} }
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value is inSegment(1), then this "If the value is inSegment(1), then this
indicates that the following indices, indicates that the following index,
mplsLdpLspFecIfIndex and mplsLdpLspFecLabel mplsLdpLspFecSegmentIndex, contains the same
contain the same values as the mplsInSegmentLdpLspIfIndex value as the mplsInSegmentLdpLspIndex.
and the mplsInSegmentLdpLspLabel.
Otherwise, if the value of this object is Otherwise, if the value of this object is
outSegment(2), then this outSegment(2), then this
indicates that the following indices, indicates that following index,
mplsLdpLspFecIfIndex and mplsLdpLspFecLabel mplsLdpLspFecSegmentIndex, contains the same
contain the same values as the mplsOutSegmentLdpLspIfIndex value as the mplsOutSegmentLdpLspIndex."
and the mplsOutSegmentLdpLspLabel."
::= { mplsLdpLspFecEntry 1 } ::= { mplsLdpLspFecEntry 1 }
mplsLdpLspFecIfIndex OBJECT-TYPE mplsLdpLspFecSegmentIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is either the mplsInSegmentLdpLspIfIndex "This index is interpretted by using the value
or the mplsOutSegmentLdpLspIfIndex as indicated by of the mplsLdpLspFecSegment.
the mplsLdpLspFecSegment."
::= { mplsLdpLspFecEntry 2 }
mplsLdpLspFecLabel OBJECT-TYPE If the mplsLdpLspFecSegment is inSegment(1),
SYNTAX MplsLabel then this index has the same value as
MAX-ACCESS not-accessible mplsInSegmentLdpLspIndex.
STATUS current
DESCRIPTION
"This index is either the mplsInSegmentLdpLspLabel
or the mplsOutSegmentLdpLspLabel as indicated by
the mplsLdpLspFecSegment."
::= { mplsLdpLspFecEntry 3 }
If the mplsLdpLspFecSegment is outSegment(2),
then this index has the same value as
mplsOutSegmentLdpLspIndex."
::= { mplsLdpLspFecEntry 2 }
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 3 }
mplsLdpLspFecOperStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
inUse(2),
notInUse(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the operational status of
the FEC associated with LDP LSP.
unknown(1) - this is a temporary state which
may indicate the LSP-FEC association
is in a state of transition.
inUse(2) - the FEC associated with the LSP is
currently being applied.
notInUse(3) - the FEC associated with the LSP is
not being applied. Eventually, this
entry may be aged out."
::= { mplsLdpLspFecEntry 5 }
mplsLdpLspFecLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value of sysUpTime at the time of the most recent
change to the mplsLdpLspFecOperStatus object."
::= { 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. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLdpLspFecEntry 7 } ::= { mplsLdpLspFecEntry 4 }
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 "The status of this conceptual row. If the
value of this object is 'active(1)', then value of this object is 'active(1)', then
none of the writable objects of this entry none of the writable objects of this entry
can be modified. can be modified.
skipping to change at page 53, line 9 skipping to change at page 54, line 12
mplsLdpEntityAdminStatus object) mplsLdpEntityAdminStatus object)
is to set the mplsLdpEntityAdminStatus to is to set the mplsLdpEntityAdminStatus to
down, thereby explicitly causing a session down, thereby explicitly causing a session
to be torn down. This will also 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 5 }
-- --
-- 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.
-- --
mplsLdpSessionPeerAddrTable OBJECT-TYPE mplsLdpSessionPeerAddrTable OBJECT-TYPE
skipping to change at page 53, line 32 skipping to change at page 54, line 35
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 'sparse augments',
rather than 'AUGMENTS' the mplsLdpSessionTable's the mplsLdpSessionTable's information."
information." ::= { mplsLdpSessionObjects 11 }
::= { mplsLdpSessionObjects 10 }
mplsLdpSessionPeerAddrEntry OBJECT-TYPE mplsLdpSessionPeerAddrEntry OBJECT-TYPE
SYNTAX MplsLdpSessionPeerAddrEntry 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."
skipping to change at page 54, line 40 skipping to change at page 55, line 43
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
mplsLdpSessionPeerNextHopAddr." mplsLdpSessionPeerNextHopAddr."
::= { mplsLdpSessionPeerAddrEntry 2 } ::= { mplsLdpSessionPeerAddrEntry 2 }
mplsLdpSessionPeerNextHopAddr 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 next hop address. The type of this address
is specified by the value of the
mplsLdpSessionPeerNextHopAddrType."
REFERENCE REFERENCE
"RFC3036, Section 2.7. LDP Identifiers "RFC3036, Section 2.7. LDP Identifiers
and Next Hop Addresses" and Next Hop Addresses"
::= { mplsLdpSessionPeerAddrEntry 3 } ::= { mplsLdpSessionPeerAddrEntry 3 }
--- ---
--- Notifications --- Notifications
--- ---
mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpEntityInitSessionThreshold mplsLdpEntityInitSessionThreshold
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the value of "This notification is generated when the value of
the 'mplsLdpEntityInitSessionThreshold' 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
skipping to change at page 55, line 41 skipping to change at page 56, line 45
mplsLdpSessionUp NOTIFICATION-TYPE mplsLdpSessionUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpSessionState, mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors mplsLdpSessionStatsUnknownTlvErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this notification is enabled to generated, "If this notification is sent when the
then this notification is sent when the
value of 'mplsLdpSessionState' enters value of 'mplsLdpSessionState' enters
the 'operational(5)' state." the 'operational(5)' state."
::= { mplsLdpNotifications 3 } ::= { mplsLdpNotifications 3 }
mplsLdpSessionDown NOTIFICATION-TYPE mplsLdpSessionDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpSessionState, mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors mplsLdpSessionStatsUnknownTlvErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 57, line 25 skipping to change at page 58, line 28
"An implementation is only required to support IPv4 and "An implementation is only required to support IPv4 and
globally unique IPv6 addresses." globally unique IPv6 addresses."
OBJECT mplsLdpEntityRowStatus OBJECT mplsLdpEntityRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"Support for createAndWait and notInService is not "Support for createAndWait and notInService is not
required." required."
OBJECT mplsFecAddrFamily OBJECT mplsFecAddrType
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 mplsFecAddr OBJECT mplsFecAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"An implementation is only required to support IPv4 and "An implementation is only required to support IPv4 and
globally unique IPv6 addresses." globally unique IPv6 addresses."
skipping to change at page 61, line 29 skipping to change at page 62, line 31
OBJECT mplsFecType OBJECT mplsFecType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsFecAddrPrefixLength OBJECT mplsFecAddrPrefixLength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsFecAddrFamily OBJECT mplsFecAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. "Write access is not required.
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 mplsFecAddr OBJECT mplsFecAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 64, line 10 skipping to change at page 65, line 13
mplsLdpSessionRole, mplsLdpSessionRole,
mplsLdpSessionProtocolVersion, mplsLdpSessionProtocolVersion,
mplsLdpSessionKeepAliveHoldTimeRem, mplsLdpSessionKeepAliveHoldTimeRem,
mplsLdpSessionKeepAliveTime, mplsLdpSessionKeepAliveTime,
mplsLdpSessionMaxPduLength, mplsLdpSessionMaxPduLength,
mplsLdpSessionDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors, mplsLdpSessionStatsUnknownTlvErrors,
mplsLdpSessionPeerNextHopAddrType, mplsLdpSessionPeerNextHopAddrType,
mplsLdpSessionPeerNextHopAddr, mplsLdpSessionPeerNextHopAddr,
mplsFecLastChange,
mplsFecIndexNext, mplsFecIndexNext,
mplsFecType, mplsFecType,
mplsFecAddrPrefixLength, mplsFecAddrType,
mplsFecAddrFamily,
mplsFecAddr, mplsFecAddr,
mplsFecAddrPrefixLength,
mplsFecStorageType, mplsFecStorageType,
mplsFecRowStatus mplsFecRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations." "Objects that apply to all MPLS LDP implementations."
::= { mplsLdpGroups 1 } ::= { mplsLdpGroups 1 }
mplsLdpLspGroup OBJECT-GROUP mplsLdpLspGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsInSegmentLdpLspLabelType, mplsInSegmentLdpLspLabelType,
mplsInSegmentLdpLspType, mplsInSegmentLdpLspType,
mplsOutSegmentLdpLspLabelType, mplsOutSegmentLdpLspLabelType,
mplsOutSegmentLdpLspType, mplsOutSegmentLdpLspType,
mplsLdpLspFecOperStatus,
mplsLdpLspFecLastChange, mplsLdpLspFecLastChange,
mplsLdpLspFecStorageType, mplsLdpLspFecStorageType,
mplsLdpLspFecRowStatus mplsLdpLspFecRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are for LDP implementations "These objects are for LDP implementations
which interface to the Label Information Base (LIB) which interface to the Label Information Base (LIB)
in the MPLS-LSR-STD-MIB. The LIB is in the MPLS-LSR-STD-MIB. The LIB is
represented in the mplsInSegmentTable, represented in the mplsInSegmentTable,
skipping to change at page 65, line 15 skipping to change at page 66, line 18
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification for an MPLS LDP implemention." "The notification for an MPLS LDP implemention."
::= { mplsLdpGroups 3 } ::= { mplsLdpGroups 3 }
END END
4.1. The MPLS-LDP-ATM-STD-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 medium. 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
mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third
table is the mplsLdpAtmSessionTable which is a read-only table.
4.1.1. The LDP Entity ATM Table
The mplsLdpEntityAtmTable provides a way to configure information The mplsLdpEntityAtmTable provides a way to configure information
which would be contained in the "Optional Parameter" portion of an which would be contained in the "Optional Parameter" portion of an
LDP PDU Initialization Message. LDP PDU Initialization Message.
4.1.2. The LDP Entity ATM Label Range Table
The mplsLdpEntityAtmLRTable provides a way to configure information The mplsLdpEntityAtmLRTable provides a way to configure information
which would be contained in the "ATM Label Range Components" portion which would be contained in the "ATM Label Range Components" portion
of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036]. of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036].
4.1.1. The LDP ATM Session Table 4.1.3. 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-STD-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
skipping to change at page 66, line 24 skipping to change at page 67, line 33
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpAtmStdMIB MODULE-IDENTITY mplsLdpAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200306091200Z" -- 9 June 2003 LAST-UPDATED "200306281200Z" -- 28 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 67, line 8 skipping to change at page 68, line 16
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 "200306091200Z" -- 9 June 2003 REVISION "200306281200Z" -- 28 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 mplsStdMIB subId is 5, e.g. -- the suggested mplsStdMIB subId is 5, e.g.
-- ::= { mplsStdMIB 5 } -- ::= { mplsStdMIB 5 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
skipping to change at page 67, line 41 skipping to change at page 69, line 4
-- --
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 ATM specific information
ATM specific information which could be used which could be used in the
in the 'Optional Parameters' and other ATM 'Optional Parameters' and other ATM specific
specific information. information.
This table 'sparse augments' the mplsLdpEntityTable This table 'sparse augments' the mplsLdpEntityTable
when ATM as the Layer 2 media." when ATM is the Layer 2 medium."
::= { 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 35 skipping to change at page 69, line 44
mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier, mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier,
mplsLdpEntityAtmStorageType StorageType, mplsLdpEntityAtmStorageType StorageType,
mplsLdpEntityAtmRowStatus RowStatus mplsLdpEntityAtmRowStatus RowStatus
} }
mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE mplsLdpEntityAtmIfIndexOrZero 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
the 'ifLayer' where the ATM Labels 'owned' by this or 0 (zero). The value of zero means that the
entry were created, or 0 (zero). The value of zero InterfaceIndex is not known.
means that the InterfaceIndex is not known. For example,
if the InterfaceIndex is created subsequent to the
ATM Label's creation, then it would not be known.
However, if the InterfaceIndex is known, then it must However, if the InterfaceIndex is known, then it must
be represented by this value. be represented by this value.
If an InterfaceIndex becomes known, then the If an InterfaceIndex becomes known, then the
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. If an ATM Label is value of the InterfaceIndex. If an ATM Label is
being used in forwarding data, then the value of this being used in forwarding data, then the value of this
object MUST be the InterfaceIndex." object MUST be the InterfaceIndex."
::= { mplsLdpEntityAtmEntry 1 } ::= { mplsLdpEntityAtmEntry 1 }
skipping to change at page 70, line 8 skipping to change at page 71, line 16
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-only
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
to this entry. to this entry.
This is the EXACT value for the ATM Session Parameter, This is the EXACT value for the ATM Session Parameter,
field N (for Number of label range components). The ATM field N (for Number of label range components). The ATM
Session Parameter is an optional parameter in the Initialization Session Parameter is an optional parameter in the Initialization
skipping to change at page 74, line 40 skipping to change at page 75, line 47
be one entry having LowerBound vpi/vci == 0/32, and be one entry having LowerBound vpi/vci == 0/32, and
UpperBound vpi/vci == 0/100, and a second entry UpperBound vpi/vci == 0/100, and a second entry
for this same interface with LowerBound for this same interface with LowerBound
vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. vpi/vci == 0/101 and UpperBound vpi/vci == 0/200.
However, there could not be a third entry with However, there could not be a third entry with
LowerBound vpi/vci == 0/200 and LowerBound vpi/vci == 0/200 and
UpperBound vpi/vci == 0/300 because this label UpperBound vpi/vci == 0/300 because this label
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 become active unless a unique and
non-overlapping range is specified. Thus, row non-overlapping range is specified.
creation implies a one-shot row creation of
LDP EntityID and LowerBound vpi/vci and At least one label range entry for a
UpperBound vpi/vci. At least one label 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 A request to create a row with an overlapping
range should result in an inconsistentValue range should result in an inconsistentValue
error." error."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpEntityAtmLRMinVpi, mplsLdpEntityAtmLRMinVpi,
mplsLdpEntityAtmLRMinVci mplsLdpEntityAtmLRMinVci
skipping to change at page 80, line 14 skipping to change at page 81, line 19
OBJECT mplsLdpEntityAtmIfIndexOrZero OBJECT mplsLdpEntityAtmIfIndexOrZero
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityAtmMergeCap OBJECT mplsLdpEntityAtmMergeCap
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityAtmLRComponents
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsLdpEntityAtmVcDirectionality OBJECT mplsLdpEntityAtmVcDirectionality
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityAtmLsrConnectivity OBJECT mplsLdpEntityAtmLsrConnectivity
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 82, line 30 skipping to change at page 83, line 30
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-STD-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 medium. 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 mplsLdpEntityFrameRelayTable and the the mplsLdpEntityFrameRelayTable and the
mplsLdpEntityFrameRelayLRTable. mplsLdpEntityFrameRelayLRTable. The third table,
mplsLdpFrameRelaySessionTable, is a read-only table.
4.2.1. The LDP Entity Frame Relay Table
The mplsLdpEntityFrameRelayTable 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.
4.2.2. The LDP Entity Frame Relay Label Range Table
The mplsLdpEntityFrameRelayLRTable provides a way to configure The mplsLdpEntityFrameRelayLRTable provides a way to configure
information which would be contained in the "Frame Relay Label Range information which would be contained in the "Frame Relay Label Range
Components" portion of an LDP PDU Intialization Message, see Components" portion of an LDP PDU Intialization Message, see
[RFC3034] and [RFC3036]. [RFC3034] and [RFC3036].
4.2.1. The LDP Frame Relay Session Table 4.2.3. 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-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
skipping to change at page 83, line 38 skipping to change at page 85, line 4
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpFrameRelayStdMIB MODULE-IDENTITY mplsLdpFrameRelayStdMIB MODULE-IDENTITY
LAST-UPDATED "200306091200Z" -- 9 June 2003 LAST-UPDATED "200306281200Z" -- 28 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 84, line 28 skipping to change at page 85, line 35
" "
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 "200306091200Z" -- 9 June 2003 REVISION "200306281200Z" -- 28 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 mplsStdMIB subId is 6, e.g. -- The requested mplsStdMIB subId is 6, e.g.
-- ::= { mplsStdMIB 6 } -- ::= { mplsStdMIB 6 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
skipping to change at page 85, line 18 skipping to change at page 86, line 25
-- --
mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 1 } { mplsLdpFrameRelayObjects 1 }
mplsLdpEntityFrameRelayTable OBJECT-TYPE mplsLdpEntityFrameRelayTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the "This table contains Frame Relay specific
Optional Parameters to specify what this Entity is information which could be used in the
going to specify for Frame Relay specific 'Optional Parameters' and other Frame Relay
LDP Intialization Messages." Relay specific information.
This table 'sparse augments' the mplsLdpEntityTable
when Frame Relay is the Layer 2 medium."
::= { mplsLdpEntityFrameRelayObjects 1 } ::= { mplsLdpEntityFrameRelayObjects 1 }
mplsLdpEntityFrameRelayEntry OBJECT-TYPE mplsLdpEntityFrameRelayEntry OBJECT-TYPE
SYNTAX MplsLdpEntityFrameRelayEntry SYNTAX MplsLdpEntityFrameRelayEntry
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
optional parameters associated with the LDP entity." optional parameters associated with the LDP entity."
INDEX { mplsLdpEntityLdpId, INDEX { mplsLdpEntityLdpId,
skipping to change at page 87, line 10 skipping to change at page 88, line 21
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-only
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 Session Parameter is an optional parameter in
skipping to change at page 95, line 31 skipping to change at page 96, line 42
OBJECT mplsLdpEntityFrameRelayIfIndexOrZero OBJECT mplsLdpEntityFrameRelayIfIndexOrZero
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityFrameRelayMergeCap OBJECT mplsLdpEntityFrameRelayMergeCap
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityFrameRelayLRComponents
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsLdpEntityFrameRelayVcDirectionality OBJECT mplsLdpEntityFrameRelayVcDirectionality
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityFrameRelayStorageType OBJECT mplsLdpEntityFrameRelayStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 97, line 15 skipping to change at page 98, line 21
"Objects that apply to all MPLS LDP implementations "Objects that apply to all MPLS LDP implementations
using Frame Relay as the Layer 2." using Frame Relay as the Layer 2."
::= { mplsLdpFrameRelayGroups 1 } ::= { mplsLdpFrameRelayGroups 1 }
END END
4.3. The MPLS-LDP-GENERIC-STD-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
mplsLdpEntityGenericLRTable. Although the LDP Specification does not mplsLdpEntityGenericLRTable. Although the LDP Specification does not
provide a way for configuring Label Ranges for Generic Labels, the provide a way for configuring Label Ranges for Generic Labels, the
MIB does provide a way to reserve a range of generic labels because MIB does provide a way to reserve a range of generic 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-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
skipping to change at page 97, line 37 skipping to change at page 99, line 4
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
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex mplsLdpEntityIndex
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpGenericStdMIB MODULE-IDENTITY mplsLdpGenericStdMIB MODULE-IDENTITY
LAST-UPDATED "200306091200Z" -- 9 June 2003 LAST-UPDATED "200306281200Z" -- 28 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 98, line 38 skipping to change at page 99, line 44
" "
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 "200306091200Z" -- 9 June 2003 REVISION "200306281200Z" -- 28 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 mplsStdMIB subId is 7, e.g. -- The requested mplsStdMIB subId is 7, e.g.
-- ::= { mplsStdMIB 7 } -- ::= { mplsStdMIB 7 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpGenericObjects mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance mplsLdpGenericConformance
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP GENERIC Objects -- MPLS LDP GENERIC Objects
--**************************************************************** --****************************************************************
-- --
skipping to change at page 101, line 32 skipping to change at page 102, line 40
::= { 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
the 'ifLayer' where these Generic Label would be created, the 'ifLayer' where these Generic Label would be created,
or 0 (zero). The value of zero means that the or 0 (zero). The value of zero means that the
InterfaceIndex is not known. For example, if InterfaceIndex is not known.
the InterfaceIndex is created subsequent to
the Generic Label's creation, then it would not be However, if the InterfaceIndex is known,
known. However, if the InterfaceIndex then it must be represented by this value.
is known, then it must be represented by this value.
If an InterfaceIndex becomes known, then the If an InterfaceIndex becomes known, then the
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
skipping to change at page 105, line 8 skipping to change at page 106, line 8
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations "Objects that apply to all MPLS LDP implementations
using Generic Labels as the Layer 2." 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.
5.1. Changes from <draft-ietf-mpls-ldp-mib-10.txt> 5.1. Changes from <draft-ietf-mpls-ldp-mib-11.txt>
Updated with comments from the 3rd Last Call for this MIB which took
place, Thursday, June 12 to June 24, 2003.
Updated with last call comments from Adrian Farell posted to the MPLS
Working Group email list on June 12, 2003.
Updated the 2 outstanding issues from Bert's email May 9th which was
posted to the MPLS Working Group. These issues were not updated for
version 10, so were addressed in version 11: 1) updated #3 from that
email and 2) reviewed all the InetAddressType and InetAddress objects
to make sure that descriptions were per rfc3291.
5.2. Changes from <draft-ietf-mpls-ldp-mib-10.txt>
Renamed the MIB module to include Std and also updated the IANA Renamed the MIB module to include Std and also updated the IANA
Considerations Section to use mplsStdMIB. Considerations Section to use mplsStdMIB.
Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet 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 update #3 from that email and 2) did not yet review all the
InetAddressType and InetAddress objects to make sure that InetAddressType and InetAddress objects to make sure that
descriptions were per rfc3291. descriptions were per rfc3291.
Changed Ses to Session for clarity. Changed Ses to Session for clarity.
5.2. Changes from <draft-ietf-mpls-ldp-mib-09.txt> 5.3. 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.2.1. Changes based on MIB Doctor Review Comments 5.3.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 110, line 18 skipping to change at page 111, line 33
"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.3. Changes from <draft-ietf-mpls-ldp-mib-08.txt> 5.4. 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 112, line 32 skipping to change at page 114, line 5
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.4. Changes from <draft-ietf-mpls-ldp-mib-07.txt> 5.5. 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 113, line 42 skipping to change at page 115, line 13
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.5. Changes from <draft-ietf-mpls-ldp-mib-06.txt> 5.6. 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.6. Changes from <draft-ietf-mpls-ldp-mib-05.txt> 5.7. 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 116, line 4 skipping to change at page 117, line 21
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.7. Changes from <draft-ietf-mpls-ldp-mib-04.txt> 5.8. 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 118, line 28 skipping to change at page 119, line 44
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.8. Changes from <draft-ietf-mpls-ldp-mib-03.txt> 5.9. 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 120, line 5 skipping to change at page 121, line 19
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.9. Changes from <draft-ietf-mpls-ldp-mib-02.txt> 5.10. 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.
skipping to change at page 120, line 33 skipping to change at page 122, line 5
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.10. Changes from <draft-ietf-mpls-ldp-mib-01.txt> 5.11. 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 121, line 44 skipping to change at page 123, line 15
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.11. Changes from <draft-ietf-mpls-ldp-mib-00.txt> 5.12. 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 38 skipping to change at page 124, line 7
The following objects were added to the mplsLdpPeerEntityTable: The following objects were added to the mplsLdpPeerEntityTable:
mplsLdpPeerLabelDistributionMethod. mplsLdpPeerLabelDistributionMethod.
The following object was removed from the mplsLdpEntityStatsTable: The following object was removed from the mplsLdpEntityStatsTable:
mplsLdpEntityEstablishedSessions. mplsLdpEntityEstablishedSessions.
References were added and revised. References were added and revised.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank the following people: Leigh This document is a product of the MPLS Working Group. The authors
McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel would like to thank Mike MacFadden and Adrian Farrel for their
Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, helpful comments on several reviews. Also, the authors would like to
some members of the working group were very helpful with comments and give a special acknowledgement to Bert Wijnen for his many detailed
corrections to the MIB; the authors would like to thank Adrian Farrel reviews. Bert's assistance and guidance is greatly appreciated.
of Movaz Networks, and Alan Kullberg from NetPlane Systems.
We would also like to thank Cheenu Srinivasan, Arun Viswanathan and
Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [LSRMIB], for
their assistance.
Additionally, there have been other members of the working group that
have been very helpful: Alan Kullberg from NetPlane Systems gave
input on earlier versions of this document, and more recently, Riza
Cetin of Alcatel and Neil Jerram of Data Connection who both provided
MIB objects.
Early versions of this document were also reviewed by colleagues at
Nortel Networks and Ericsson. The authors would like to thank the
following people: Leigh McLellan, Geetha Brown, Geping Chen and
Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo
Augustsson from Ericsson.
7. Normative References 7. Normative References
[RFC1700] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC [RFC2115] Brown, C., and F. Baker, "Management Information Base for
1700, October 1994. Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[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 [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.
[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.,
skipping to change at page 124, line 24 skipping to change at page 126, line 21
[RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information [RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information
Base for the Differentiated Services Architecture", RFC Base for the Differentiated Services Architecture", RFC
3289, May 2002. 3289, May 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.
Schoenwaelder, "Textual Coventions for Internet Network Schoenwaelder, "Textual Coventions for Internet Network
Addresses", RFC 3291, May 2002. 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-09.txt, October 2003. draft-ietf-mpls-lsr-mib-11.txt, June 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-08.txt, June 2003.
8. Informative References 8. Informative References
[RFC2115] Brown, C., and F. Baker, "Management Information Base for [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3",
Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. RFC 2026, October 1996.
[RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of
Textual Conventions and OBJECT-IDENTITIES for ATM
Management", RFC 2514, February 1999.
[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.
[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-04.txt, May 2003. mpls-mgmt-overview-06.txt, June 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-STD-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
skipping to change at page 126, line 9 skipping to change at page 128, line 5
associate an LSP with a FEC. Unauthorized access to objects in associate an LSP with a FEC. Unauthorized access to objects in
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if an LDP session has been network. This is especially true if an LDP session has been
established. The use of stronger mechanisms such as SNMPv3 established. The use of stronger mechanisms such as SNMPv3
security should be considered where possible. Specifically, security should be considered where possible. Specifically,
SNMPv3 VACM and USM MUST be used with any v3 agent which SNMPv3 VACM and USM MUST be used with any v3 agent which
implements this MIB. Administrators should consider whether implements this MIB. Administrators should consider whether
read access to these objects should be allowed, since read read access to these objects should be allowed, since read
access may be undesirable under certain circumstances. access may be undesirable under certain circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module i.e., "objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible", may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
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 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
skipping to change at page 126, line 47 skipping to change at page 128, line 43
LDP-MIB. Unauthorized access to objects in these tables, could LDP-MIB. Unauthorized access to objects in these tables, could
result in disruption of traffic on the network. This is result in disruption of traffic on the network. This is
especially true if an LDP session has been established. The use especially true if an LDP session has been established. The use
of stronger mechanisms such as SNMPv3 security should be of stronger mechanisms such as SNMPv3 security should be
considered where possible. Specifically, SNMPv3 VACM and USM considered where possible. Specifically, SNMPv3 VACM and USM
MUST be used with any v3 agent which implements this MIB. MUST be used with any v3 agent which implements this MIB.
Administrators should consider whether read access to these Administrators should consider whether read access to these
objects should be allowed, since read access may be undesirable objects should be allowed, since read access may be undesirable
under certain circumstances. under certain circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module i.e., "objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible", may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
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.
skipping to change at page 127, line 40 skipping to change at page 129, line 35
Unauthorized access to objects in these tables, could result in Unauthorized access to objects in these tables, could result in
disruption of traffic on the network. This is especially true disruption of traffic on the network. This is especially true
if an LDP session has been established. The use of stronger if an LDP session has been established. The use of stronger
mechanisms such as SNMPv3 security should be considered where mechanisms such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used with possible. Specifically, SNMPv3 VACM and USM MUST be used with
any v3 agent which implements this MIB. Administrators should any v3 agent which implements this MIB. Administrators should
consider whether read access to these objects should be allowed, consider whether read access to these objects should be allowed,
since read access may be undesirable under certain since read access may be undesirable under certain
circumstances. circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module i.e., "objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible", may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
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 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
skipping to change at page 128, line 35 skipping to change at page 130, line 29
Unauthorized access to objects in these tables, could result in Unauthorized access to objects in these tables, could result in
disruption of traffic on the network. This is especially true disruption of traffic on the network. This is especially true
if an LDP session has been established. The use of stronger if an LDP session has been established. The use of stronger
mechanisms such as SNMPv3 security should be considered where mechanisms such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used with possible. Specifically, SNMPv3 VACM and USM MUST be used with
any v3 agent which implements this MIB. Administrators should any v3 agent which implements this MIB. Administrators should
consider whether read access to these objects should be allowed, consider whether read access to these objects should be allowed,
since read access may be undesirable under certain since read access may be undesirable under certain
circumstances. circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module i.e., "objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible", may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
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.
skipping to change at page 129, line 39 skipping to change at page 131, line 30
10. IANA Considerations 10. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-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 mplsStdMIB 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 mplsStdMIB 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-STD-MIB Module 10.1. IANA Considerations for MPLS-LDP-STD-MIB
The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD- The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD-
MIB module specified in this document. MIB module specified in this document.
10.2. IANA Considerations for the MPLS-LDP-ATM-STD-MIB Module 10.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM- The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM-
STD-MIB module specified in this document. STD-MIB module specified in this document.
10.3. IANA Considerations for the MPLS-LDP-FRAME-RELAY-STD-MIB Module 10.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB
The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP- The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP-
FRAME-RELAY-STD-MIB module specified in this document. FRAME-RELAY-STD-MIB module specified in this document.
10.4. IANA Considerations for the MPLS-LDP-GENERIC-STD-MIB Module 10.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB
The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP- The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP-
GENERIC-STD-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
 End of changes. 

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