draft-ietf-mpls-p2mp-te-mib-03.txt   draft-ietf-mpls-p2mp-te-mib-04.txt 
Network Working Group A. Farrel (Editor) Network Working Group A. Farrel (Editor)
Updates: RFC3812 Old Dog Consulting INTERNET-DRAFT Old Dog Consulting
Intended Status: Standards Track Updates: RFC3812
Expires: August 2007 S. Yasukawa Intended Status: Standards Track S. Yasukawa
NTT Expires: January 2008 NTT
T. Nadeau T. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
February 2007
Point-to-Multipoint Multiprotocol Label Switching (MPLS) Point-to-Multipoint Multiprotocol Label Switching (MPLS)
Traffic Engineering (TE) Management Information Base (MIB) module Traffic Engineering (TE) Management Information Base (MIB) module
draft-ietf-mpls-p2mp-te-mib-03.txt draft-ietf-mpls-p2mp-te-mib-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 45 skipping to change at page 1, line 43
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html. accessed at http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
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 point-to-multipoint In particular, it describes managed objects for point-to-multipoint
Multiprotocol Label Switching-based traffic engineering. (P2MP) Multiprotocol Label Switching (MPLS) based traffic engineering
(TE).
Table of Contents Table of Contents
1. Introduction .................................................. 2 1. Introduction .................................................. 2
2. The Internet-Standard Management Framework .................... 3 2. The Internet-Standard Management Framework .................... 3
3. Feature List .................................................. 3 3. Feature List .................................................. 3
4. Outline ....................................................... 4 4. Outline ....................................................... 4
4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module .. 5 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module .. 5
4.2. Use of MPLS-TE-STD-MIB ................................... 5 4.2. Use of MPLS-TE-STD-MIB ................................... 5
4.3. Scalars .................................................. 7 4.3. Scalars .................................................. 7
4.3. mplsTeP2mpTunnelTable .................................... 8 4.3. mplsTeP2mpTunnelTable .................................... 8
4.5. mplsTeP2mpTunnelDestTable ................................ 8 4.5. mplsTeP2mpTunnelDestTable ................................ 8
4.6. mplsTeP2mpTunnelBranchPerfTable .......................... 8 4.6. mplsTeP2mpTunnelBranchPerfTable .......................... 8
4.7. Relationships Between MIB Tables ......................... 8 4.7. Relationships Between MIB Tables ......................... 9
5. Using the P2MP MPLS-TE MIB Module ............................. 9 5. Using the P2MP MPLS-TE MIB Module ............................. 9
5.1. Example Use of the P2MP MPLS-TE MIB Module .............. 10 5.1. Example Use of the P2MP MPLS-TE MIB Module .............. 10
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ........ 15 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ........ 15
6.1. Example Use of the LSR MIB Module ....................... 16 6.1. Example Use of the LSR MIB Module ....................... 16
7. MPLS Traffic Engineering P2MP MIB Definitions ................ 19 7. MPLS Traffic Engineering P2MP MIB Definitions ................ 19
8. Security Considerations ...................................... 43 8. Security Considerations ...................................... 43
9. Acknowledgments .............................................. 45 9. Acknowledgments .............................................. 44
10. IANA Considerations .......................................... 45 10. IANA Considerations .......................................... 45
10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 45 10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 45
11. References ................................................... 45 11. References ................................................... 45
11.1. Normative References .................................... 45 11.1. Normative References .................................... 45
11.2. Informative References ..................................... 46 11.2. Informative References ..................................... 46
12. Authors' Addresses ........................................... 47 12. Authors' Addresses ........................................... 47
13. Intellectual Property ........................................ 47 13. Intellectual Property ........................................ 47
14. Full Copyright Statement ..................................... 48 14. Full Copyright Statement ..................................... 48
0. Changes Since Previous Revision 0. Changes Since Previous Revision
[This section to be removed before publication as an RFC.] [This section to be removed before publication as an RFC.]
- Typos.
- Move the Informational RFC 4461 to be an Informative Reference. Updates after early MIB Doctor review.
- Updates to sections 4.2, 4.3, and 4.7 for clarity. - Fix compiler warnings
- Minor clarifications in Abstract and Overview sections
- Add conformance statements for objects of syntax InetAddressType
- Clarifications to various Description clauses
- Delete mplsTeP2mpTunnelIsP2MP
- Allow mplsTeP2mpTunnelSubGroupOrigin to have zero length when
mplsTeP2mpTunnelSubGroupOrigin is set to unknown(0)
- Change syntax of mplsTeP2mpTunnelSubGroupID to IndexInteger
1. Introduction 1. Introduction
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 modeling In particular, it describes managed objects for modeling
point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS)
traffic engineering (TE). traffic engineering (TE).
MPLS is defined in [RFC3031] and a signaling protocol for MPLS is defined in [RFC3031] and a signaling protocol for
point-to-point (P2P) MPLS-TE (TE extensions to the Resource point-to-point (P2P) MPLS-TE (TE extensions to the Resource
Reservation Protocol - RSVP-TE) is defined in [RFC3209]. RSVP-TE is Reservation Protocol - RSVP-TE) is defined in [RFC3209]. RSVP-TE is
extended for use in a P2MP environment by [P2MP-TE] following the extended for use in a P2MP environment by [RFC4875] following the
requirements set out in [RFC4461]. requirements set out in [RFC4461].
[RFC3812] provides a MIB module for modeling and controlling P2P [RFC3812] provides a MIB module for modeling and controlling P2P
MPLS-TE in conjunction with Textual Conventions defined in [RFC3811]. MPLS-TE in conjunction with Textual Conventions defined in [RFC3811].
In addition, [RFC3813] defines a MIB module for modeling and In addition, [RFC3813] defines a MIB module for modeling and
controlling an MPLS Label Switching Router (LSR) that may support controlling an MPLS Label Switching Router (LSR) that may support
MPLS-TE. An overview of MPLS MIB modules can be found in [RFC4221]. MPLS-TE. An overview of MPLS MIB modules can be found in [RFC4221].
This document defines a MIB module for managing and controlling P2MP This document defines a MIB module for managing and controlling P2MP
MPLS-TE. It builds on the objects and tables defined in [RFC3812] so MPLS-TE. It builds on the objects and tables defined in [RFC3812] so
skipping to change at page 4, line 33 skipping to change at page 4, line 39
are invariant across the branches of a P2MP LSP toward different are invariant across the branches of a P2MP LSP toward different
leaves. leaves.
One of the configuration parameters associated with an MPLS tunnel is One of the configuration parameters associated with an MPLS tunnel is
the path (or route) that supporting LSPs are required to follow. This the path (or route) that supporting LSPs are required to follow. This
can be specified as a series of loose or strict hops. In P2MP TE, can be specified as a series of loose or strict hops. In P2MP TE,
this specification of the LSP route includes implicit or explicit this specification of the LSP route includes implicit or explicit
identification of the branch points in the P2MP LSPs. identification of the branch points in the P2MP LSPs.
The setup of P2MP tunnels can be achieved as: The setup of P2MP tunnels can be achieved as:
- management actions only, by using [RFC3813]
- control plane actions under the direction of a management process - Management actions only, by using [RFC3813] to configure cross-
by using [RFC3812] and the MIB module defined in this document connections or forwarding state at the LSRs along the path of the
- control plane actions under the direction of some other management tunnel. See Section 6 for more details.
process, monitored using [RFC3812] and the MIB module defined in
this document. - Control plane actions (i.e., signaling using [RFC4875]) under the
direction of a management process, by using [RFC3812] and the MIB
module defined in this document.
- Control plane actions ([RFC4875]) under the direction of some other
management process, and monitored using [RFC3812] and the MIB
module defined in this document.
Note that [RFC4802] defines a MIB module that can be used to manage Note that [RFC4802] defines a MIB module that can be used to manage
and model Generalized MPLS (GMPLS) LSPs - it is a series of MIB and model Generalized MPLS (GMPLS) LSPs - it is a series of MIB
objects and tables some of which extend tables in MPLS-TE-STD-MIB objects and tables some of which extend tables in MPLS-TE-STD-MIB
[RFC3812]. [RFC4461] and [P2MP-TE] are clear that they apply to [RFC3812]. [RFC4461] and [RFC4875] are clear that they apply to
MPLS-TE [RFC3031] and GMPLS [RFC3945]. This document describes a MIB MPLS-TE [RFC3031] and GMPLS [RFC3945]. This document describes a MIB
module that can be used for both MPLS-TE and GMPLS P2MP LSPs. module that can be used for both MPLS-TE and GMPLS P2MP LSPs, and all
objects apply to both MPLS and GMPLS.
The following sections describe the components of the P2MP MPLS-TE The following sections describe the components of the P2MP MPLS-TE
MIB module. The subsequent section provides an explanation and MIB module. The subsequent section provides an explanation and
example of how the P2MP MPLS-TE MIB module can be used for the example of how the P2MP MPLS-TE MIB module can be used to configure
processes listed above in combination with the MPLS-TE MIB module and manage a P2MP tunnel when used in combination with the MPLS-TE
defined in [RFC3812]. A further section describes how P2MP tunnels MIB module defined in [RFC3812]. A further section describes how
can be managed solely through the LSR MIB module defined in P2MP tunnels can be managed solely through the LSR MIB module defined
[RFC3813], and gives an example. in [RFC3813], and gives an example.
4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module
The MIB module consists of the following objects and tables: The MIB module consists of the following objects and tables:
- The P2MP Tunnel table (mplsTeP2mpTunnelTable) sparse augments the - The P2MP Tunnel table (mplsTeP2mpTunnelTable) sparse augments the
MPLS-TE Tunnel table (mplsTunnelTable) and is used to set up and MPLS-TE Tunnel table (mplsTunnelTable) and is used to set up and
monitor P2MP MPLS-TE tunnels. monitor P2MP MPLS-TE tunnels.
- The P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) lists - The P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) lists
skipping to change at page 5, line 40 skipping to change at page 5, line 52
The MIB module defined in this document builds on the objects and The MIB module defined in this document builds on the objects and
tables of MPLS-TE-STD-MIB defined in [RFC3812]. That is, most of the tables of MPLS-TE-STD-MIB defined in [RFC3812]. That is, most of the
basic properties of the MPLS tunnel are modeled and managed by basic properties of the MPLS tunnel are modeled and managed by
objects in MPLS-TE-STD-MIB, and new objects are only defined within objects in MPLS-TE-STD-MIB, and new objects are only defined within
this document where additional features or different behavior is this document where additional features or different behavior is
required. required.
When an MPLS-TE tunnel is a P2MP tunnel, certain objects in the When an MPLS-TE tunnel is a P2MP tunnel, certain objects in the
mplsTunnelTable have new meanings just as the signaling objects in mplsTunnelTable have new meanings just as the signaling objects in
RSVP-TE [RFC3209] have different meanings when the signaling messages RSVP-TE [RFC3209] have different meanings when the signaling messages
are used to establish P2MP LSPs [P2MP-TE]. are used to establish P2MP LSPs [RFC4875].
As indicated in the next section, the presence of a conceptual row in As indicated in the next section, the presence of a conceptual row in
the mplsTeP2mpTunnelTable of the MIB module defined in this document the mplsTeP2mpTunnelTable of the MIB module defined in this document
with the object mplsTeP2mpTunnel containing the value true(1) shows shows that a tunnel defined in the corresponding conceptual row of
that a tunnel defined in the corresponding conceptual row of the the mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP tunnel. Under those
mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP tunnel. Under those
circumstances the following scalars and objects from the appropriate circumstances the following scalars and objects from the appropriate
conceptual rows in MPLS-TE-STD-MIB MUST be interpreted as follows. conceptual rows in MPLS-TE-STD-MIB MUST be interpreted as follows.
The text below is supplementary for the Description clauses in The text below is supplementary for the Description clauses in
[RFC3812]. [RFC3812].
mplsTunnelMaxHops mplsTunnelMaxHops
This object continues to refer to the maximum number of hops that This object continues to refer to the maximum number of hops that
can be configured to a single destination for a tunnel on this can be configured to a single destination for a tunnel on this
device. Thus, for a P2MP tunnel, this refers to the maximum number device. Thus, for a P2MP tunnel, this refers to the maximum number
of hops that can be configured on this device to any individual of hops that can be configured on this device to any individual
destination of the tunnel. destination of the tunnel.
A new object, mplsTeP2mpTunnelTotalMaxHops, is defined in this MIB A new object, mplsTeP2mpTunnelTotalMaxHops, is defined in this MIB
module to supply the total number of hops across all destinations module to supply the total number of hops across all destinations
of a P2MP tunnel. of a P2MP tunnel. mplsTeP2mpTunnelTotalMaxHops would normally be
set larger than or equal to mplsTunnelMaxHops.
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
This object continues to map to the field in the RSVP-TE Session This object continues to map to the field in the RSVP-TE Session
Object that occupies the space used by the IPv4 Tunnel Endpoint Object that occupies the space used by the IPv4 Tunnel Endpoint
Address [RFC3209], but for a P2MP tunnel, this object does not Address [RFC3209], but for a P2MP tunnel, this object does not
identify an address of the egress of the tunnel. Instead it identify an address of the egress of the tunnel. Instead it
contains the P2MP ID value that identifies the identifier of the contains the P2MP ID value that identifies the identifier of the
set of destinations for the P2MP tunnel and is carried in the P2MP set of destinations for the P2MP tunnel and is carried in the P2MP
Session Object [P2MP-TE]. The Description clause for this object Session Object [RFC4875]. The Description clause for this object
can be read as follows. can be read as follows.
"Identity of the egress LSR associated with this tunnel "Identity of the egress LSR associated with this tunnel
instance. instance.
When an entry in the mplsTeP2mpTunnelTable is present When an entry in the mplsTeP2mpTunnelTable is present
corresponding to this entry in the mplsTunnelTable and when corresponding to this entry in the mplsTunnelTable, this
the mplsTeP2mpTunnel object in that table entry is present object contains the P2MP ID that identifies the set of
with the value true(1), this object contains the P2MP ID that destinations of this tunnel and that is signaled in the
identifies the set of destinations of this tunnel and that is P2MP ID field of the P2MP Session Object if the MPLS
signaled in the P2MP ID field of the P2MP Session Object if signaling protocol for this tunnel indicated by
the MPLS signaling protocol for this tunnel indicated by
mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp(2)." mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp(2)."
The destinations of the P2MP tunnel are found in the new The destinations of the P2MP tunnel are found in the new
mplsTeP2mpTunnelDestTable. mplsTeP2mpTunnelDestTable.
mplsTunnelHopTableIndex mplsTunnelHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel,
and when the mplsTeP2mpTunnel object in that table entry is this object is not used. This is because the destinations and
present with the value true(1), this object is not used. This is paths to those destinations are found in the
because the destinations and paths to those destinations are found mplsTeP2mpTunnelDestTable.
in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it SHOULD contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelPathInUse mplsTunnelPathInUse
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel,
and when the mplsTeP2mpTunnel object in that table entry is this object is not used. This is because the destinations and
present with the value true(1), this object is not used. This is paths to those destinations are found in the
because the destinations and paths to those destinations are found mplsTeP2mpTunnelDestTable.
in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it SHOULD contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelARHopTableIndex mplsTunnelARHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel,
and when the mplsTeP2mpTunnel object in that table entry is this object is not used. This is because the destinations and
present with the value true(1), this object is not used. This is paths to those destinations are found in the
because the destinations and paths to those destinations are found mplsTeP2mpTunnelDestTable.
in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it SHOULD contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelCHopTableIndex mplsTunnelCHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel,
and when the mplsTeP2mpTunnel object in that table entry is this object is not used. This is because the destinations and
present with the value true(1), this object is not used. This is paths to those destinations are found in the
because the destinations and paths to those destinations are found mplsTeP2mpTunnelDestTable.
in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it SHOULD contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
4.3. Scalars 4.3. Scalars
There are three scalars defined for this MIB module. There are three scalars defined for this MIB module.
mplsTeP2mpTunnelConfigured provides a read-only counter of the number mplsTeP2mpTunnelConfigured provides a read-only counter of the number
of P2MP MPLS-TE tunnels that are configured on this LSR through this of P2MP MPLS-TE tunnels that are configured on this LSR through this
MIB module. MIB module.
mplsTeP2mpTunnelActive provides a read-only counter of the number of mplsTeP2mpTunnelActive provides a read-only counter of the number of
P2MP MPLS-TE tunnels configured on this LSR through this MIB module P2MP MPLS-TE tunnels configured on this LSR through this MIB module
that are currently active. that are currently active.
As described in Section 4.2, mplsTeP2mpTunnelTotalMaxHops is a read- As described in Section 4.2, mplsTeP2mpTunnelTotalMaxHops is a read-
only scalar that reports the maximum number of explicit route hops only scalar that reports the maximum number of explicit route hops
supported by this LSR for any single P2MP LSP configured or monitored supported by this LSR for any single P2MP LSP configured or monitored
through this MIB module. through this MIB module. mplsTeP2mpTunnelTotalMaxHops would normally
be set larger than or equal to mplsTunnelMaxHops.
4.4. mplsTeP2mpTunnelTable 4.4. mplsTeP2mpTunnelTable
The mplsTeP2mpTunnelTable extends (through a sparse augmentation) the The mplsTeP2mpTunnelTable extends (through a sparse augmentation) the
MPLS Tunnel table (mplsTunnelTable) from MPLS-TE-STD-MIB [RFC3812] to MPLS Tunnel table (mplsTunnelTable) from MPLS-TE-STD-MIB [RFC3812] to
allow P2MP MPLS-TE tunnels to be created, controlled, and monitored allow P2MP MPLS-TE tunnels to be created, controlled, and monitored
at any LSR in the network. at any LSR in the network.
A P2MP MPLS-TE tunnel may be represented in the MIB, by defining it A P2MP MPLS-TE tunnel may be represented in the MIB, by defining it
in the mplsTunnelTable and providing objects in this table to in the mplsTunnelTable and providing objects in this table to
skipping to change at page 9, line 9 skipping to change at page 9, line 21
between the various pre-existing MPLS-TE and LSR MIB tables can be between the various pre-existing MPLS-TE and LSR MIB tables can be
seen in [RFC4221]. seen in [RFC4221].
An arrow in the figure shows that the MIB table pointed from contains An arrow in the figure shows that the MIB table pointed from contains
a reference to the MIB table pointed to. a reference to the MIB table pointed to.
mplsTunnelPerfTable mplsTunnelPerfTable
^ ^
| |
v v
mplsTunnelTable----------->mplsP2mpTunnelTable mplsTunnelTable----------->mplsTeP2mpTunnelTable
^ | | ^ | |
| | | | | |
| +--->mplsXCTable--+ v | +--->mplsXCTable--+ v
v | mplsP2mpTunnelDestTable v | mplsTeP2mpTunnelDestTable
mplsTunnelResourceTable | | | | mplsTunnelResourceTable | | | |
^ | | | +--->mplsTunnelHopTable ^ | | | +--->mplsTunnelHopTable
| | | | +--->mplsTunnelCHopTable | | | | +--->mplsTunnelCHopTable
mplsInSegmentTable<-----+ | | +--->mplsTunnelARHopTable mplsInSegmentTable<-----+ | | +--->mplsTunnelARHopTable
| | | | | |
v | | v | |
mplsOutSegmentTable<---+ | mplsOutSegmentTable<---+ |
v v
mplsP2mpTunnelBranchPerfTable mplsTeP2mpTunnelBranchPerfTable
Figure 1 : Dependencies Between MIB Tables Figure 1 : Dependencies Between MIB Tables
5. Using the P2MP MPLS-TE MIB Module 5. Using the P2MP MPLS-TE MIB Module
This section describes how to use the P2MP MPLS-TE MIB module defined This section describes how to use the P2MP MPLS-TE MIB module defined
in this document to manage and model P2MP MPLS-TE LSPs. A subsection in this document to manage and model P2MP MPLS-TE LSPs. A subsection
gives an example of usage. gives an example of usage.
A P2MP MPLS-TE LSP is modeled as a single LSP tunnel. That is, there A P2MP MPLS-TE LSP is modeled as a single LSP tunnel. That is, there
skipping to change at page 10, line 35 skipping to change at page 10, line 41
/ /
R---A---B R---A---B
\ \
\ \
C2---D2 C2---D2
Figure 2 : Topology of a simple P2MP MPLS-TE LSP Figure 2 : Topology of a simple P2MP MPLS-TE LSP
Let us assign IP addresses to the LSRs as follows: Let us assign IP addresses to the LSRs as follows:
R 192.168.100.1 R 192.0.2.1
A 192.168.101.1 A 192.0.2.9
B 192.168.102.1 B 192.0.2.17
C1 192.168.103.1 C1 192.0.2.33
C2 192.168.103.10 C2 192.0.2.34
D1 192.168.104.1 D1 192.0.2.65
D2 192.168.104.10 D2 192.0.2.66
Step 1 - Define the resource requirements for the LSP Step 1 - Define the resource requirements for the LSP
Let us assume that we require a best effort LSP. Let us assume that we require a best effort LSP.
In mplsTunnelResourceTable define as follows: In mplsTunnelResourceTable define as follows:
{ {
mplsTunnelResourceIndex = 9, mplsTunnelResourceIndex = 9,
mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMaxRate = 0,
skipping to change at page 11, line 17 skipping to change at page 11, line 26
mplsTunnelResourceRowStatus = createAndGo(4) mplsTunnelResourceRowStatus = createAndGo(4)
} }
Step 2 - Define the core parameters for the LSP tunnel. Step 2 - Define the core parameters for the LSP tunnel.
In mplsTunnelTable define as follows: In mplsTunnelTable define as follows:
{ {
mplsTunnelIndex = 4, mplsTunnelIndex = 4,
mplsTunnelInstance = 0, mplsTunnelInstance = 0,
mplsTunnelIngressLSRId = 192.168.100.1, mplsTunnelIngressLSRId = 192.0.2.1,
-- The tunnel egress LSR ID is used to -- The tunnel egress LSR ID is used to
-- hold the P2MP ID for the P2MP LSP tunnel -- hold the P2MP ID for the P2MP LSP tunnel
mplsTunnelEgressLSRId = 328, mplsTunnelEgressLSRId = 328,
mplsTunnelName = "My first P2MP tunnel", mplsTunnelName = "My first P2MP tunnel",
mplsTunnelDescr = "Here to there and there", mplsTunnelDescr = "Here to there and there",
mplsTunnelIsIf = true(1), mplsTunnelIsIf = true(1),
-- There is no cross-connect present yet -- There is no cross-connect present yet
mplsTunnelXCPointer = 0.0, mplsTunnelXCPointer = 0.0,
-- This table entry is created by configuration no signaling -- This table entry is created by configuration no signaling
mplsTunnelSignallingProto = rsvp(2), mplsTunnelSignallingProto = rsvp(2),
skipping to change at page 12, line 10 skipping to change at page 12, line 14
Note that any active or signaled instances of the above tunnel Note that any active or signaled instances of the above tunnel
would appear with the same primary mplsTunnelIndex, but would have would appear with the same primary mplsTunnelIndex, but would have
values greater than 0 for mplsTunnelInstance. They would also have values greater than 0 for mplsTunnelInstance. They would also have
other objects such as the mplsTunnelXCPointer set accordingly. other objects such as the mplsTunnelXCPointer set accordingly.
Step 3 - Create the P2MP Tunnel Step 3 - Create the P2MP Tunnel
In mplsTeP2mpTunnelTable define as follows: In mplsTeP2mpTunnelTable define as follows:
{ {
mplsTeP2mpTunnelIsP2MP = true(1),
mplsTeP2mpTunnelP2mpIntegrity = true(1), mplsTeP2mpTunnelP2mpIntegrity = true(1),
-- This is the head end of the LSP and not a branch -- This is the head end of the LSP and not a branch
mplsTeP2mpTunnelBranchRole = notBranch(1), mplsTeP2mpTunnelBranchRole = notBranch(1),
mplsTeP2mpTunnelSubGroupOriginType = ipv4(1), mplsTeP2mpTunnelSubGroupOriginType = ipv4(1),
mplsTeP2mpTunnelSubGroupOrigin = 192.168.100.1, mplsTeP2mpTunnelSubGroupOrigin = 192.0.2.1,
mplsTeP2mpTunnelSubGroupID = 132, mplsTeP2mpTunnelSubGroupID = 132,
mplsTeP2mpTunnelRowStatus = createAndGo(4) mplsTeP2mpTunnelRowStatus = createAndGo(4)
} }
Step 4 - Create the configured explicit routes for the LSP Step 4 - Create the configured explicit routes for the LSP
Two pieces of explicit path are required. The first runs from R to Two pieces of explicit path are required. The first runs from R to
D1, and the second from B to D2. See [P2MP-TE] for a discussion of D1, and the second from B to D2. See [RFC4875] for a discussion of
the construction of explicit routes for P2MP MPLS-TE LSPs. the construction of explicit routes for P2MP MPLS-TE LSPs.
In mplsTunnelHopTable define as follows: In mplsTunnelHopTable define as follows:
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1, mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.101.1", mplsTunnelHopIpAddr = "192.0.2.9",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2, mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.102.1", mplsTunnelHopIpAddr = "192.0.2.17",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3, mplsTunnelHopIndex = 3,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.103.1", mplsTunnelHopIpAddr = "192.0.2.33",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 4, mplsTunnelHopIndex = 4,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.104.1", mplsTunnelHopIpAddr = "192.0.2.65",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 2, mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1, mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.102.1", mplsTunnelHopIpAddr = "192.0.2.17",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 2, mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2, mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.103.10", mplsTunnelHopIpAddr = "192.0.2.34",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
{ {
mplsTunnelHopListIndex = 2, mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3, mplsTunnelHopIndex = 3,
mplsTunnelHopAddrType = ipv4(1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpAddr = "192.168.104.10", mplsTunnelHopIpAddr = "192.0.2.66",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict(2), mplsTunnelHopType = strict(2),
mplsTunnelHopInclude = true(1), mplsTunnelHopInclude = true(1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit(2), mplsTunnelHopEntryPathComp = explicit(2),
mplsTunnelHopRowStatus = createAndGo(4) mplsTunnelHopRowStatus = createAndGo(4)
} }
Step 5 - Create the destinations for the P2MP LSP tunnel Step 5 - Create the destinations for the P2MP LSP tunnel
In mplsTeP2mpTunnelDestTable define as follows: In mplsTeP2mpTunnelDestTable define as follows:
{ {
mplsTeP2mpTunnelDestSubGroupOriginType = ipv4(1), mplsTeP2mpTunnelDestSubGroupOriginType = ipv4(1),
mplsTeP2mpTunnelDestSubGroupOrigin = 192.168.100.1, mplsTeP2mpTunnelDestSubGroupOrigin = 192.0.2.1,
mplsTeP2mpTunnelDestSubGroupID = 132, mplsTeP2mpTunnelDestSubGroupID = 132,
mplsTeP2mpTunnelDestDestinationType = ipv4(1), mplsTeP2mpTunnelDestDestinationType = ipv4(1),
mplsTeP2mpTunnelDestDestination = 192.168.104.1, mplsTeP2mpTunnelDestDestination = 192.0.2.65,
mplsTeP2mpTunnelDestHopTableIndex = 1, mplsTeP2mpTunnelDestHopTableIndex = 1,
mplsTeP2mpTunnelDestPathInUse = 1, mplsTeP2mpTunnelDestPathInUse = 1,
mplsTeP2mpTunnelDestAdminStatus = up(1), mplsTeP2mpTunnelDestAdminStatus = up(1),
mplsTeP2mpTunnelDestRowStatus = createAndGo(4) mplsTeP2mpTunnelDestRowStatus = createAndGo(4)
} }
{ {
mplsTeP2mpTunnelDestSubGroupOriginType = ipv4(1), mplsTeP2mpTunnelDestSubGroupOriginType = ipv4(1),
mplsTeP2mpTunnelDestSubGroupOrigin = 192.168.100.1, mplsTeP2mpTunnelDestSubGroupOrigin = 192.0.2.1,
mplsTeP2mpTunnelDestSubGroupID = 132, mplsTeP2mpTunnelDestSubGroupID = 132,
mplsTeP2mpTunnelDestDestinationType = ipv4(1), mplsTeP2mpTunnelDestDestinationType = ipv4(1),
mplsTeP2mpTunnelDestDestination = 192.168.104.10, mplsTeP2mpTunnelDestDestination = 192.0.2.66,
mplsTeP2mpTunnelDestHopTableIndex = 2, mplsTeP2mpTunnelDestHopTableIndex = 2,
mplsTeP2mpTunnelDestPathInUse = 1, mplsTeP2mpTunnelDestPathInUse = 1,
mplsTeP2mpTunnelDestAdminStatus = up(1), mplsTeP2mpTunnelDestAdminStatus = up(1),
mplsTeP2mpTunnelDestRowStatus = createAndGo(4) mplsTeP2mpTunnelDestRowStatus = createAndGo(4)
} }
Step 6 - Activate the tunnel Step 6 - Activate the tunnel
In mplsTunnelTable define as follows: In mplsTunnelTable define as follows:
{ {
mplsTunnelIndex = 4, mplsTunnelIndex = 4,
mplsTunnelInstance = 0, mplsTunnelInstance = 0,
mplsTunnelIngressLSRId = 192.168.100.1, mplsTunnelIngressLSRId = 192.0.2.1,
mplsTunnelEgressLSRId = 328, mplsTunnelEgressLSRId = 328,
-- Activate the tunnel -- Activate the tunnel
mplsAdminStatus = up(1) mplsAdminStatus = up(1)
} }
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module
The nature of P2MP tunnels is such that an LSR that is crossed by a The nature of P2MP tunnels is such that an LSR that is crossed by a
tunnel may either be the ingress of that tunnel or have precisely one tunnel may either be the ingress of that tunnel or have precisely one
upstream LSP segment (also known as an in-segment [RFC3812]) for that upstream LSP segment (also known as an in-segment [RFC3812]) for that
skipping to change at page 19, line 8 skipping to change at page 19, line 8
mplsXCIndex = 0x37, -- common index mplsXCIndex = 0x37, -- common index
mplsXCInSegmentIndex = 0x00000015,-- the in-segment mplsXCInSegmentIndex = 0x00000015,-- the in-segment
mplsXCOutSegmentIndex = 0x00, -- no out-segment mplsXCOutSegmentIndex = 0x00, -- no out-segment
mplsXCLspId = 0x0102 -- unique LSP ID mplsXCLspId = 0x0102 -- unique LSP ID
mplsXCLabelStackIndex = 0x00, -- no other outgoing label mplsXCLabelStackIndex = 0x00, -- no other outgoing label
} }
7. MPLS Traffic Engineering P2MP MIB Definitions 7. MPLS Traffic Engineering P2MP MIB Definitions
This MIB module uses imports from [RFC2578], [RFC2580], [RFC2579], This MIB module uses imports from [RFC2578], [RFC2580], [RFC2579],
[RFC3811], [RFC3812], [RFC3813], [RFC3289], and [RFC3291]. [RFC3811], [RFC3812], [RFC3813], [RFC3289], and [RFC4001].
MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Counter64, TimeTicks Unsigned32, Counter32, Counter64, TimeTicks
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
TruthValue, RowStatus, StorageType, TimeStamp TruthValue, RowStatus, StorageType, TimeStamp
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
mplsStdMIB, MplsPathIndexOrZero mplsStdMIB, MplsPathIndexOrZero
FROM MPLS-TC-STD-MIB -- RFC 3811 FROM MPLS-TC-STD-MIB -- RFC 3811
MplsIndexType MplsIndexType
FROM MPLS-LSR-STD-MIB -- RFC 3813 FROM MPLS-LSR-STD-MIB -- RFC 3813
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- RFC 3812 FROM MPLS-TE-STD-MIB -- RFC 3812
IndexIntegerNextFree IndexInteger, IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC 3289 FROM DIFFSERV-MIB -- RFC 3289
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- RFC 3291 FROM INET-ADDRESS-MIB -- RFC 4001
; ;
mplsTeP2mpStdMIB MODULE-IDENTITY mplsTeP2mpStdMIB MODULE-IDENTITY
LAST-UPDATED "200702240000Z" -- February 24, 2007 LAST-UPDATED "200702240000Z" -- February 24, 2007
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Adrian Farrel " Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
skipping to change at page 21, line 39 skipping to change at page 21, line 39
"RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB), Engineering (TE) Management Information Base (MIB),
Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
::= { mplsTeP2mpScalars 2 } ::= { mplsTeP2mpScalars 2 }
mplsTeP2mpTunnelTotalMaxHops OBJECT-TYPE mplsTeP2mpTunnelTotalMaxHops OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of hops that can be specified for "The maximum number of hops that can be specified for an
an entire P2MP tunnel on this device. entire P2MP tunnel on this device. This object should be
This object should be used in conjunction with used in conjunction with mplsTunnelMaxHops in
mplsTunnelMaxHops in MPLS-TE-STD-MIB that is used in the MPLS-TE-STD-MIB that is used in the context of P2MP tunnels
context of P2MP tunnels to express the maximum number of to express the maximum number of hops to any individual
hops to any individual destination of a P2MP tunnel that destination of a P2MP tunnel that can be configured on this
can be configured on this device." device. mplsTeP2mpTunnelTotalMaxHops would normally be set
larger than or equal to mplsTunnelMaxHops."
REFERENCE REFERENCE
"RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB), Engineering (TE) Management Information Base (MIB),
Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
::= { mplsTeP2mpScalars 3 } ::= { mplsTeP2mpScalars 3 }
-- End of MPLS Tunnel scalars. -- End of MPLS Tunnel scalars.
-- MPLS P2MP tunnel table. -- MPLS P2MP tunnel table.
skipping to change at page 23, line 12 skipping to change at page 23, line 12
Engineering (TE) Management Information Base (MIB), Engineering (TE) Management Information Base (MIB),
Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
INDEX { mplsTunnelIndex, INDEX { mplsTunnelIndex,
mplsTunnelInstance, mplsTunnelInstance,
mplsTunnelIngressLSRId, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
} }
::= { mplsTeP2mpTunnelTable 1 } ::= { mplsTeP2mpTunnelTable 1 }
MplsTeP2mpTunnelEntry ::= SEQUENCE { MplsTeP2mpTunnelEntry ::= SEQUENCE {
mplsTeP2mpTunnelIsP2MP TruthValue,
mplsTeP2mpTunnelP2mpIntegrity TruthValue, mplsTeP2mpTunnelP2mpIntegrity TruthValue,
mplsTeP2mpTunnelBranchRole INTEGER, mplsTeP2mpTunnelBranchRole INTEGER,
mplsTeP2mpTunnelSubGroupOriginType InetAddressType, mplsTeP2mpTunnelSubGroupOriginType InetAddressType,
mplsTeP2mpTunnelSubGroupOrigin InetAddress, mplsTeP2mpTunnelSubGroupOrigin InetAddress,
mplsTeP2mpTunnelSubGroupID Unsigned32, mplsTeP2mpTunnelSubGroupID Unsigned32,
mplsTeP2mpTunnelRowStatus RowStatus, mplsTeP2mpTunnelRowStatus RowStatus,
mplsTeP2mpTunnelStorageType StorageType mplsTeP2mpTunnelStorageType StorageType
} }
mplsTeP2mpTunnelIsP2MP OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes whether or not this tunnel is a point-to-multipoint
tunnel.
If this object is not present or is present and set to
false(2), this tunnel is not a point-to-multipoint tunnel
and all other objects in this table entry are not valid."
DEFVAL { true }
::= { mplsTeP2mpTunnelEntry 1 }
mplsTeP2mpTunnelP2mpIntegrity OBJECT-TYPE mplsTeP2mpTunnelP2mpIntegrity OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not P2MP Integrity is required for this "Denotes whether or not P2MP Integrity is required for this
tunnel. tunnel.
If P2MP integrity is operational on a P2MP tunnel then the If P2MP integrity is operational on a P2MP tunnel then the
failure of the path to any of the tunnel destinations should failure of the path to any of the tunnel destinations should
cause the teardown of the entire P2MP tunnel." cause the teardown of the entire P2MP tunnel."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
DEFVAL { false } DEFVAL { false }
::= { mplsTeP2mpTunnelEntry 2 } ::= { mplsTeP2mpTunnelEntry 2 }
mplsTeP2mpTunnelBranchRole OBJECT-TYPE mplsTeP2mpTunnelBranchRole OBJECT-TYPE
SYNTAX INTEGER { notBranch(1), SYNTAX INTEGER { notBranch(1),
branch(2), branch(2),
bud(3) } bud(3) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value supplements the value in the object "This value supplements the value in the object
mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role
of this LSR in the tunnel represented by this entry in of this LSR in the tunnel represented by this entry in
skipping to change at page 25, line 33 skipping to change at page 25, line 22
Since the object mplsTeP2mpTunnelSubGroupOrigin must conform Since the object mplsTeP2mpTunnelSubGroupOrigin must conform
to the protocol specification, this object must return to the protocol specification, this object must return
either ipv4(1) or ipv6(2) at a transit or egress LSR. either ipv4(1) or ipv6(2) at a transit or egress LSR.
At an ingress LSR, mplsTeP2mpTunnelSubGroupOrigin should not At an ingress LSR, mplsTeP2mpTunnelSubGroupOrigin should not
be used, and this object should return the value be used, and this object should return the value
unknown(0)." unknown(0)."
::= { mplsTeP2mpTunnelEntry 4 } ::= { mplsTeP2mpTunnelEntry 4 }
mplsTeP2mpTunnelSubGroupOrigin OBJECT-TYPE mplsTeP2mpTunnelSubGroupOrigin OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..16)) SYNTAX InetAddress (SIZE (0..16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TE Router ID (reachable and stable IP address) of the "The TE Router ID (reachable and stable IP address) of the
originator of the P2MP sub-group as received on a Path originator of the P2MP sub-group as received on a Path
message by a transit or egress LSR. message by a transit or egress LSR.
This object is interpreted in the context of This object is interpreted in the context of
mplsTeP2mpTunnelSubGroupOriginType. mplsTeP2mpTunnelSubGroupOriginType.
The value of the sub-group originator used on outgoing Path The value of the sub-group originator used on outgoing Path
messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and
is copied from this object unless this LSR is responsible is copied from this object unless this LSR is responsible
for changing the sub-group ID. for changing the sub-group ID.
At an ingress LSR this object is not used because there is At an ingress LSR this object is not used because there is
no received Path message. mplsTeP2mpTunnelSubGroupOriginType no received Path message. mplsTeP2mpTunnelSubGroupOriginType
should return unknown(0), and this object should return the should return unknown(0), and this object should return a
value 0x00, or should be absent." zero-length string, or should be absent."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelEntry 5 } ::= { mplsTeP2mpTunnelEntry 5 }
mplsTeP2mpTunnelSubGroupID OBJECT-TYPE mplsTeP2mpTunnelSubGroupID OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unique identifier assigned by the sub-group originator "The unique identifier assigned by the sub-group originator
for this sub-group of this P2MP tunnel as received on a Path for this sub-group of this P2MP tunnel as received on a Path
message by a transit or egress LSR. message by a transit or egress LSR.
The value of the sub-group identifier used on outgoing Path The value of the sub-group identifier used on outgoing Path
messages is found in mplsTeP2mpTunnelDestSubGroupID and is messages is found in mplsTeP2mpTunnelDestSubGroupID and is
copied from this object unless this LSR is responsible for copied from this object unless this LSR is responsible for
changing the sub-group ID. changing the sub-group ID.
At an ingress LSR this object is not used because there is At an ingress LSR this object is not used because there is
no received Path message, and the object should be absent or no received Path message, and the object should be absent or
should return zero." should return zero."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelEntry 6 } ::= { mplsTeP2mpTunnelEntry 6 }
mplsTeP2mpTunnelRowStatus OBJECT-TYPE mplsTeP2mpTunnelRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table. When a row in this table is in active(1) in this table. When a row in this table is in active(1)
state, no objects in that row can be modified by the agent state, no objects in that row can be modified by the agent
skipping to change at page 27, line 32 skipping to change at page 27, line 20
Conceptual rows having the value 'permanent' need not allow Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row." write-access to any columnar objects in the row."
DEFVAL { volatile } DEFVAL { volatile }
::= { mplsTeP2mpTunnelEntry 8 } ::= { mplsTeP2mpTunnelEntry 8 }
-- End of mplsTeP2mpTunnelTable -- End of mplsTeP2mpTunnelTable
-- MPLS P2MP tunnel destination table. -- MPLS P2MP tunnel destination table.
mplsTeP2mpTunnelSubGroupIDNext OBJECT-TYPE mplsTeP2mpTunnelSubGroupIDNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295) SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for "This object contains an unused value for
mplsTeP2mpTunnelDestSubGroupID, or a zero to indicate that mplsTeP2mpTunnelDestSubGroupID, or a zero to indicate that
none exists. Negative values are not allowed, as they do not none exists. Negative values are not allowed, as they do not
correspond to valid values of correspond to valid values of
mplsTeP2mpTunnelDestSubGroupID. mplsTeP2mpTunnelDestSubGroupID.
Note that this object offers an unused value for an Note that this object offers an unused value for an
skipping to change at page 28, line 4 skipping to change at page 27, line 37
correspond to valid values of correspond to valid values of
mplsTeP2mpTunnelDestSubGroupID. mplsTeP2mpTunnelDestSubGroupID.
Note that this object offers an unused value for an Note that this object offers an unused value for an
mplsTeP2mpTunnelDestSubGroupID value at the local LSR when mplsTeP2mpTunnelDestSubGroupID value at the local LSR when
it is a sub-group originator. In other cases, the value of it is a sub-group originator. In other cases, the value of
mplsTeP2mpTunnelDestSubGroupID SHOULD be taken from the mplsTeP2mpTunnelDestSubGroupID SHOULD be taken from the
received value signaled by the signaling protocol and received value signaled by the signaling protocol and
corresponds to the value in mplsTeP2mpTunnelSubGroupID." corresponds to the value in mplsTeP2mpTunnelSubGroupID."
::= { mplsTeP2mpObjects 2 } ::= { mplsTeP2mpObjects 2 }
mplsTeP2mpTunnelDestTable OBJECT-TYPE mplsTeP2mpTunnelDestTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTeP2mpTunnelDestEntry SYNTAX SEQUENCE OF MplsTeP2mpTunnelDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTeP2mpTunnelDestTable allows new destinations of "The mplsTeP2mpTunnelDestTable allows new destinations of
P2MP MPLS tunnels to be added to and removed from P2MP P2MP MPLS tunnels to be added to and removed from P2MP
tunnels. tunnels."
Entries in this table share some index fields with the
mplsTeP2mpTunnelTable and the mplsTunnelTable in
MPLS-TE-STD-MIB. Entries in this table have no meaning
unless there is a corresponding entry in
mplsTeP2mpTunnelTable (which, itself, depends on a
corresponding entry in mplsTunnelTable) and that entry has
mpl2P2mpTunnelIsP2mp set to true(1)."
REFERENCE REFERENCE
"RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB), Engineering (TE) Management Information Base (MIB),
Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
::= { mplsTeP2mpObjects 3 } ::= { mplsTeP2mpObjects 3 }
mplsTeP2mpTunnelDestEntry OBJECT-TYPE mplsTeP2mpTunnelDestEntry OBJECT-TYPE
SYNTAX MplsTeP2mpTunnelDestEntry SYNTAX MplsTeP2mpTunnelDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a destination of a P2MP "An entry in this table represents a destination of a P2MP
MPLS tunnel. An entry can be created by a network MPLS tunnel. An entry can be created by a network
administrator or by an SNMP agent as instructed by an MPLS administrator or by an SNMP agent as instructed by an MPLS
signaling protocol. signaling protocol.
skipping to change at page 28, line 41 skipping to change at page 28, line 19
"An entry in this table represents a destination of a P2MP "An entry in this table represents a destination of a P2MP
MPLS tunnel. An entry can be created by a network MPLS tunnel. An entry can be created by a network
administrator or by an SNMP agent as instructed by an MPLS administrator or by an SNMP agent as instructed by an MPLS
signaling protocol. signaling protocol.
Entries in this table share some index fields with the Entries in this table share some index fields with the
mplsTeP2mpTunnelTable and the mplsTunnelTable in mplsTeP2mpTunnelTable and the mplsTunnelTable in
MPLS-TE-STD-MIB. Entries in this table have no meaning MPLS-TE-STD-MIB. Entries in this table have no meaning
unless there is a corresponding entry in unless there is a corresponding entry in
mplsTeP2mpTunnelTable (which, itself, depends on a mplsTeP2mpTunnelTable (which, itself, depends on a
corresponding entry in mplsTunnelTable) and that entry has corresponding entry in mplsTunnelTable).
mpl2P2mpTunnelIsP2mp set to true(1).
Note that the same destination may be present more than once Note that the same destination may be present more than once
if it is in more than one sub-group as reflected by the if it is in more than one sub-group as reflected by the
mplsTeP2mpTunnelDestSubGroupOriginType, mplsTeP2mpTunnelDestSubGroupOriginType,
mplsTeP2mpTunnelDestSubGroupOrigin, and mplsTeP2mpTunnelDestSubGroupOrigin, and
mplsTeP2mpTunnelDestSubGroupID, index objects. mplsTeP2mpTunnelDestSubGroupID, index objects.
Entries in this table may be created at any time. If created Entries in this table may be created at any time. If created
before an entry in the mplsTeP2mpTunnelTable the entries before an entry in the mplsTeP2mpTunnelTable the entries
have no meaning, but may be kept ready for the creation of have no meaning, but may be kept ready for the creation of
skipping to change at page 29, line 23 skipping to change at page 29, line 4
mplsTunnelInstance, mplsTunnelInstance,
mplsTunnelIngressLSRId, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId, mplsTunnelEgressLSRId,
mplsTeP2mpTunnelDestSubGroupOriginType, mplsTeP2mpTunnelDestSubGroupOriginType,
mplsTeP2mpTunnelDestSubGroupOrigin, mplsTeP2mpTunnelDestSubGroupOrigin,
mplsTeP2mpTunnelDestSubGroupID, mplsTeP2mpTunnelDestSubGroupID,
mplsTeP2mpTunnelDestDestinationType, mplsTeP2mpTunnelDestDestinationType,
mplsTeP2mpTunnelDestDestination mplsTeP2mpTunnelDestDestination
} }
::= { mplsTeP2mpTunnelDestTable 1 } ::= { mplsTeP2mpTunnelDestTable 1 }
MplsTeP2mpTunnelDestEntry ::= SEQUENCE { MplsTeP2mpTunnelDestEntry ::= SEQUENCE {
mplsTeP2mpTunnelDestSubGroupOriginType InetAddressType, mplsTeP2mpTunnelDestSubGroupOriginType InetAddressType,
mplsTeP2mpTunnelDestSubGroupOrigin InetAddress, mplsTeP2mpTunnelDestSubGroupOrigin InetAddress,
mplsTeP2mpTunnelDestSubGroupID Unsigned32, mplsTeP2mpTunnelDestSubGroupID IndexInteger,
mplsTeP2mpTunnelDestDestinationType InetAddressType, mplsTeP2mpTunnelDestDestinationType InetAddressType,
mplsTeP2mpTunnelDestDestination InetAddress, mplsTeP2mpTunnelDestDestination InetAddress,
mplsTeP2mpTunnelDestBranchOutSegment MplsIndexType, mplsTeP2mpTunnelDestBranchOutSegment MplsIndexType,
mplsTeP2mpTunnelDestHopTableIndex MplsPathIndexOrZero, mplsTeP2mpTunnelDestHopTableIndex MplsPathIndexOrZero,
mplsTeP2mpTunnelDestPathInUse MplsPathIndexOrZero, mplsTeP2mpTunnelDestPathInUse MplsPathIndexOrZero,
mplsTeP2mpTunnelDestCHopTableIndex MplsPathIndexOrZero, mplsTeP2mpTunnelDestCHopTableIndex MplsPathIndexOrZero,
mplsTeP2mpTunnelDestARHopTableIndex MplsPathIndexOrZero, mplsTeP2mpTunnelDestARHopTableIndex MplsPathIndexOrZero,
mplsTeP2mpTunnelDestTotalUpTime TimeTicks, mplsTeP2mpTunnelDestTotalUpTime TimeTicks,
mplsTeP2mpTunnelDestInstanceUpTime TimeTicks, mplsTeP2mpTunnelDestInstanceUpTime TimeTicks,
mplsTeP2mpTunnelDestPathChanges Counter32, mplsTeP2mpTunnelDestPathChanges Counter32,
skipping to change at page 30, line 37 skipping to change at page 30, line 12
received signaled value as available in received signaled value as available in
mplsTeP2mpTunnelSubGroupOrigin. mplsTeP2mpTunnelSubGroupOrigin.
When a signaling protocol is used, this object corresponds When a signaling protocol is used, this object corresponds
to the Sub-Group Originator field in the SENDER_TEMPLATE to the Sub-Group Originator field in the SENDER_TEMPLATE
object. object.
This object is interpreted in the context of This object is interpreted in the context of
mplsTeP2mpTunnelDestSubGroupOriginType." mplsTeP2mpTunnelDestSubGroupOriginType."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelDestEntry 2 } ::= { mplsTeP2mpTunnelDestEntry 2 }
mplsTeP2mpTunnelDestSubGroupID OBJECT-TYPE mplsTeP2mpTunnelDestSubGroupID OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX IndexInteger
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unique identifier assigned by the sub-group originator "The unique identifier assigned by the sub-group originator
for this sub-group of this P2MP tunnel. for this sub-group of this P2MP tunnel.
An appropriate value for this object during row creation An appropriate value for this object during row creation
when the sub-group origin in when the sub-group origin in
mplsTeP2mpTunnelDestSubGroupOrigin is the local LSR can mplsTeP2mpTunnelDestSubGroupOrigin is the local LSR can
be obtained by reading mplsTeP2mpTunnelSubGroupIDNext." be obtained by reading mplsTeP2mpTunnelSubGroupIDNext."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelDestEntry 3 } ::= { mplsTeP2mpTunnelDestEntry 3 }
mplsTeP2mpTunnelDestDestinationType OBJECT-TYPE mplsTeP2mpTunnelDestDestinationType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the type of address carried in "This object identifies the type of address carried in
mplsTeP2mpTunnelDestDestination. mplsTeP2mpTunnelDestDestination.
skipping to change at page 31, line 41 skipping to change at page 31, line 20
routable TE address of a leaf. This will often be the TE routable TE address of a leaf. This will often be the TE
Router ID of the leaf, but can be any interface address. Router ID of the leaf, but can be any interface address.
When a signaling protocol is used, this object corresponds When a signaling protocol is used, this object corresponds
to the S2L Sub-LSP destination address field in the to the S2L Sub-LSP destination address field in the
S2L_SUB_LSP object. S2L_SUB_LSP object.
This object is interpreted in the context of This object is interpreted in the context of
mplsTeP2mpTunnelDestDestinationType." mplsTeP2mpTunnelDestDestinationType."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelDestEntry 5 } ::= { mplsTeP2mpTunnelDestEntry 5 }
mplsTeP2mpTunnelDestBranchOutSegment OBJECT-TYPE mplsTeP2mpTunnelDestBranchOutSegment OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the outgoing branch from this LSR "This object identifies the outgoing branch from this LSR
towards the destination represented by this table entry. It towards the destination represented by this table entry. It
must be a unique identifier within the scope of this tunnel. must be a unique identifier within the scope of this tunnel.
If MPLS-LSR-STD-MIB is implemented, this object should If MPLS-LSR-STD-MIB is implemented, this object should
skipping to change at page 33, line 36 skipping to change at page 33, line 8
mplsTeP2mpTunnelDestPathInUse, but may have been modified mplsTeP2mpTunnelDestPathInUse, but may have been modified
and automatically updated by the agent when computed hops and automatically updated by the agent when computed hops
become available or when computed hops get modified. become available or when computed hops get modified.
If this destination is the destination of the 'first S2L If this destination is the destination of the 'first S2L
sub-LSP' then this path will be signaled in the Explicit sub-LSP' then this path will be signaled in the Explicit
Route Object. If this destination is the destination of a Route Object. If this destination is the destination of a
'subsequent S2L sub-LSP' then this path will be signaled in 'subsequent S2L sub-LSP' then this path will be signaled in
a Secondary Explicit Route Object." a Secondary Explicit Route Object."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelDestEntry 9 } ::= { mplsTeP2mpTunnelDestEntry 9 }
mplsTeP2mpTunnelDestARHopTableIndex OBJECT-TYPE mplsTeP2mpTunnelDestARHopTableIndex OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into the mplsTunnelARHopTable that identifies the "Index into the mplsTunnelARHopTable that identifies the
actual hops traversed to this destination of the P2MP actual hops traversed to this destination of the P2MP
tunnel. This is automatically updated by the agent when the tunnel. This is automatically updated by the agent when the
actual hops becomes available. actual hops becomes available.
If this destination is the destination of the 'first S2L If this destination is the destination of the 'first S2L
sub-LSP' then this path will be signaled in the Recorded sub-LSP' then this path will be signaled in the Recorded
Route Object. If this destination is the destination of a Route Object. If this destination is the destination of a
'subsequent S2L sub-LSP' then this path will be signaled in 'subsequent S2L sub-LSP' then this path will be signaled in
a Secondary Recorded Route Object." a Secondary Recorded Route Object."
REFERENCE REFERENCE
"Extensions to RSVP-TE for Point to Multipoint TE LSPs, "RFC 4875 - Extensions to Resource Reservation Protocol -
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
progress." Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
and S. Yasukawa, May 2007."
::= { mplsTeP2mpTunnelDestEntry 10 } ::= { mplsTeP2mpTunnelDestEntry 10 }
mplsTeP2mpTunnelDestTotalUpTime OBJECT-TYPE mplsTeP2mpTunnelDestTotalUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the aggregate up time for all "This value represents the aggregate up time for all
instances of this tunnel to this destination, if this instances of this tunnel to this destination, if this
information is available. information is available.
skipping to change at page 36, line 31 skipping to change at page 35, line 48
down(2), -- out of service down(2), -- out of service
testing(3), -- in some test mode testing(3), -- in some test mode
unknown(4), -- status cannot be determined unknown(4), -- status cannot be determined
lowerLayerDown(7) -- down due to the state of lowerLayerDown(7) -- down due to the state of
-- lower layer interfaces -- lower layer interfaces
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the actual operational status of this destination "Indicates the actual operational status of this destination
of this P2MP tunnel. of this P2MP tunnel. This object may be compared to
This object may be compared to mplsTunnelOperStatus that mplsTunnelOperStatus that includes two other values:
includes two other values:
dormant(5) -- some component is missing dormant(5) -- some component is missing
notPresent(6) -- down due to the state of notPresent(6) -- down due to the state of
-- lower layer interfaces. -- lower layer interfaces.
These states do not aply to an individual destinaton of a These states do not aply to an individual destinaton of a
P2MP MPLS-TE LSP and so are not included in this object." P2MP MPLS-TE LSP and so are not included in this object."
REFERENCE REFERENCE
"RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB), Engineering (TE) Management Information Base (MIB),
Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
::= { mplsTeP2mpTunnelDestEntry 19 } ::= { mplsTeP2mpTunnelDestEntry 19 }
skipping to change at page 38, line 20 skipping to change at page 37, line 30
of the P2MP tunnel, and the out-segment that identifies the of the P2MP tunnel, and the out-segment that identifies the
outgoing branch." outgoing branch."
INDEX { mplsTunnelIndex, INDEX { mplsTunnelIndex,
mplsTunnelInstance, mplsTunnelInstance,
mplsTunnelIngressLSRId, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId, mplsTunnelEgressLSRId,
mplsTeP2mpTunnelBranchPerfBranch mplsTeP2mpTunnelBranchPerfBranch
} }
::= { mplsTeP2mpTunnelBranchPerfTable 1 } ::= { mplsTeP2mpTunnelBranchPerfTable 1 }
mplsTeP2mpTunnelBranchPerfEntry ::= SEQUENCE { MplsTeP2mpTunnelBranchPerfEntry ::= SEQUENCE {
mplsTeP2mpTunnelBranchPerfBranch MplsIndexType, mplsTeP2mpTunnelBranchPerfBranch MplsIndexType,
mplsTeP2mpTunnelBranchPerfPackets Counter32, mplsTeP2mpTunnelBranchPerfPackets Counter32,
mplsTeP2mpTunnelBranchPerfHCPackets Counter64, mplsTeP2mpTunnelBranchPerfHCPackets Counter64,
mplsTeP2mpTunnelBranchPerfErrors Counter32, mplsTeP2mpTunnelBranchPerfErrors Counter32,
mplsTeP2mpTunnelBranchPerfBytes Counter32, mplsTeP2mpTunnelBranchPerfBytes Counter32,
mplsTeP2mpTunnelBranchPerfHCBytes Counter64, mplsTeP2mpTunnelBranchPerfHCBytes Counter64,
mplsTeP2mpTunnelBranchDiscontinuityTime TimeStamp mplsTeP2mpTunnelBranchDiscontinuityTime TimeStamp
} }
mplsTeP2mpTunnelBranchPerfBranch OBJECT-TYPE mplsTeP2mpTunnelBranchPerfBranch OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType fish
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the outgoing branch from this LSR "This object identifies an outgoing branch from this LSR
for this tunnel. Its value is unique within the context of for this tunnel. Its value is unique within the context of
the tunnel. If MPLS-LSR-STD-MIB is implemented, this object the tunnel.
should contain a row pointer to the out-segment for this
branch. Under all circumstances, this object should contain If MPLS-LSR-STD-MIB is implemented, this object should
contain an index into mplsOutSegmentTable.
Under all circumstances, this object should contain
the same value as mplsTeP2mpTunnelDestBranchOutSegment for the same value as mplsTeP2mpTunnelDestBranchOutSegment for
destinations reached on this branch." destinations reached on this branch."
::= { mplsTeP2mpTunnelBranchPerfEntry 1 } ::= { mplsTeP2mpTunnelBranchPerfEntry 1 }
mplsTeP2mpTunnelBranchPerfPackets OBJECT-TYPE mplsTeP2mpTunnelBranchPerfPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets forwarded by the tunnel onto this branch. "Number of packets forwarded by the tunnel onto this branch.
This object should represents the 32-bit value of the least This object should represents the 32-bit value of the least
significant part of the 64-bit value if both significant part of the 64-bit value if both
mplsTeP2mpTunnelBranchPerfHCPackets is returned. mplsTeP2mpTunnelBranchPerfHCPackets is returned.
This object should be read in conjunction with This object should be read in conjunction with
skipping to change at page 39, line 35 skipping to change at page 38, line 38
mplsTeP2mpTunnelBranchDiscontinuityTime." mplsTeP2mpTunnelBranchDiscontinuityTime."
::= { mplsTeP2mpTunnelBranchPerfEntry 3 } ::= { mplsTeP2mpTunnelBranchPerfEntry 3 }
mplsTeP2mpTunnelBranchPerfErrors OBJECT-TYPE mplsTeP2mpTunnelBranchPerfErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets dropped because of errors or for other "Number of packets dropped because of errors or for other
reasons, that were supposed to be forwarded onto this reasons, that were supposed to be forwarded onto this
branch for this tunnel. branch for this tunnel. This object should be read in
This object should be read in conjunction with conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime."
mplsTeP2mpTunnelBranchDiscontinuityTime."
::= { mplsTeP2mpTunnelBranchPerfEntry 4 } ::= { mplsTeP2mpTunnelBranchPerfEntry 4 }
mplsTeP2mpTunnelBranchPerfBytes OBJECT-TYPE mplsTeP2mpTunnelBranchPerfBytes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of bytes forwarded by the tunnel onto this branch. "Number of bytes forwarded by the tunnel onto this branch.
This object should represents the 32-bit value of the least This object should represents the 32-bit value of the least
significant part of the 64-bit value if both significant part of the 64-bit value if both
skipping to change at page 40, line 40 skipping to change at page 39, line 40
-- Notifications. -- Notifications.
mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the generation of "If this object is true(1), then it enables the generation of
mplsTeP2mpTunnelDestUp and mplsTeP2mpTunnelDestDown mplsTeP2mpTunnelDestUp and mplsTeP2mpTunnelDestDown
notifications. Otherwise these notifications are not notifications. Otherwise these notifications are not
emitted." emitted.
Note that whn tunnels have large numbers of destinations,
setting this object to true(1) may result in the generation
of large numbers of notifications."
DEFVAL { false } DEFVAL { false }
::= { mplsTeP2mpObjects 5 } ::= { mplsTeP2mpObjects 5 }
mplsTeP2mpTunnelDestUp NOTIFICATION-TYPE mplsTeP2mpTunnelDestUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsTeP2mpTunnelDestAdminStatus, mplsTeP2mpTunnelDestAdminStatus,
mplsTeP2mpTunnelDestOperStatus mplsTeP2mpTunnelDestOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 41, line 45 skipping to change at page 41, line 4
-- End of notifications. -- End of notifications.
-- Module compliance. -- Module compliance.
mplsTeP2mpGroups mplsTeP2mpGroups
OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 1 } OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 1 }
mplsTeP2mpCompliances mplsTeP2mpCompliances
OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 2 } OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
mplsTeP2mpModuleFullCompliance MODULE-COMPLIANCE mplsTeP2mpModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support "Compliance statement for agents that provide full support
for MPLS-TE-P2MP-STD-MIB. Such devices can be monitored and for MPLS-TE-P2MP-STD-MIB. Such devices can be monitored and
also be configured using this MIB module." also be configured using this MIB module."
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTeP2mpGroup, mplsTeP2mpGroup,
mplsTeP2mpNotifGroup mplsTeP2mpNotifGroup
} }
-- mplsTeP2mpTunnelTable
OBJECT mplsTeP2mpTunnelSubGroupOriginType
SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)}
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
-- mplsTeP2mpTunnelDestTable
OBJECT mplsTeP2mpTunnelDestSubGroupOriginType
SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)}
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTeP2mpTunnelDestDestinationType
SYNTAX InetAddressType {ipv4(1), ipv6(2)}
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
::= { mplsTeP2mpCompliances 1 } ::= { mplsTeP2mpCompliances 1 }
-- Units of conformance. -- Units of conformance.
mplsTeP2mpGroup OBJECT-GROUP mplsTeP2mpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsTeP2mpTunnelConfigured, mplsTeP2mpTunnelConfigured,
mplsTeP2mpTunnelActive, mplsTeP2mpTunnelActive,
mplsTeP2mpTunnelTotalMaxHops, mplsTeP2mpTunnelTotalMaxHops,
mplsTeP2mpTunnelIsP2MP,
mplsTeP2mpTunnelP2mpIntegrity, mplsTeP2mpTunnelP2mpIntegrity,
mplsTeP2mpTunnelBranchRole, mplsTeP2mpTunnelBranchRole,
mplsTeP2mpTunnelSubGroupOriginType,
mplsTeP2mpTunnelSubGroupOrigin,
mplsTeP2mpTunnelSubGroupID,
mplsTeP2mpTunnelRowStatus, mplsTeP2mpTunnelRowStatus,
mplsTeP2mpTunnelStorageType, mplsTeP2mpTunnelStorageType,
mplsTeP2mpTunnelSubGroupIDNext, mplsTeP2mpTunnelSubGroupIDNext,
mplsTeP2mpTunnelDestBranchOutSegment, mplsTeP2mpTunnelDestBranchOutSegment,
mplsTeP2mpTunnelDestHopTableIndex, mplsTeP2mpTunnelDestHopTableIndex,
mplsTeP2mpTunnelDestPathInUse, mplsTeP2mpTunnelDestPathInUse,
mplsTeP2mpTunnelDestCHopTableIndex, mplsTeP2mpTunnelDestCHopTableIndex,
mplsTeP2mpTunnelDestARHopTableIndex, mplsTeP2mpTunnelDestARHopTableIndex,
mplsTeP2mpTunnelDestTotalUpTime, mplsTeP2mpTunnelDestTotalUpTime,
mplsTeP2mpTunnelDestInstanceUpTime, mplsTeP2mpTunnelDestInstanceUpTime,
skipping to change at page 45, line 12 skipping to change at page 44, line 50
RECOMMENDED. Instead, it is RECOMMENDED that SNMPv3 be deployed and RECOMMENDED. Instead, it is RECOMMENDED that SNMPv3 be deployed and
cryptographic security enabled. It is then a customer/operator cryptographic security enabled. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
only those principals (users) that have legitimate rights to those only those principals (users) that have legitimate rights to those
objects. objects.
9. Acknowledgments 9. Acknowledgments
The authors wish to thank Tom Petch and Ben Niven-Jenkins for their The authors wish to thank Tom Petch and Ben Niven-Jenkins for their
input to this work. input to this work. Thanks to Zafar Ali for discussions.
Joan Cucchiara provided a very thorough and helpful early MIB Doctor
review which caught a lot of issues.
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@lists.ietf.org mpls@lists.ietf.org
10. IANA Considerations 10. IANA Considerations
As requested in MPLS-TC-STD-MIB [RFC3811], MPLS-related standards As requested in MPLS-TC-STD-MIB [RFC3811], MPLS-related standards
track MIB modules should be rooted under the mplsStdMIB subtree. track MIB modules should be rooted under the mplsStdMIB subtree.
There is one new MPLS MIB module contained in this document, and the There is one new MPLS MIB module contained in this document, and the
skipping to change at page 46, line 20 skipping to change at page 46, line 9
Label Switching Architecture", RFC 3031, January 2001. Label Switching Architecture", RFC 3031, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[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.
Schoenwaelder, "TextualConventions for Internet Network
Addresses", RFC 3291, May 2002.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions and for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)", Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004. RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC 3813, (LSR) Router Management Information Base (MIB)", RFC 3813,
June 2004. June 2004.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[P2MP-TE] Aggarwal, R., Papadimitriou, D., and Yasukawa, S., [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
"Extensions to RSVP-TE for Point to Multipoint TE Schoenwaelder, "TextualConventions for Internet Network
LSPs", draft-ietf-mpls-rsvp-te-p2mp, work in progress. Addresses", RFC 3291, May 2002.
[RFC4875] Aggarwal, R., Papadimitriou, D., and Yasukawa, S.,
"Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs)", RFC 4875, May 2007.
11.2. Informative References 11.2. Informative References
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statement for Internet "Introduction and Applicability Statement for Internet
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
 End of changes. 86 change blocks. 
176 lines changed or deleted 205 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/