Using any standard SNMP network management application, you can retrieve and display information from the P2MP MPLS-TE MIB
(CISCO-IETF-MPLS-TE-P2MP-MIB) by using GET operations; similarly, you can traverse information in the MIB database for display
by using GETNEXT operations.
Note |
The
show mpls traffic-eng tunnels command can be used to see the value of various objects discussed in this section through the CLI.
|
The point-to-multipoint MIB tables and objects supported in Cisco IOS releases follow. Important MIB tables (those highlighted
in bold type) are described briefly in accompanying text.
Following is a list and description of each entry for the supported P2MP MPLS-TE MIB Scalar objects:
-
mplsTeP2mpTunnelConfigured—Total number of P2MP MPLS-TE tunnels configured on this device. A tunnel is considered configured
if the mplsTunnelRowStatus in MPLS-TE-STD-MIB is active.
-
mplsTeP2mpTunnelActive—Total number of P2MP MPLS-TE tunnels active on this device.
mplsTeP2mpTunnelTable
The mplsTeP2mpTunnelTable allows new P2MP MPLS-TE tunnels to be created between an LSR and one or more remote endpoints, and
existing P2MP MPLS-TE tunnels to be reconfigured or removed. This table augments the mplsTunnelTable in the MPLS-TE-STD-MIB
so that the entries in that table can be flagged as point-to-multipoint, and can be configured and monitored appropriately.
The mplsTeP2mpTunnelTable is indexed by four indices similar to the mplsTunnelTable:
-
mplsTunnelIndex
-
mplsTunnelInstance
-
mplsTunnelIngressLSRId
-
mplsTunnelEgressLSRId
The mplsTunnelEgressLSRId maps to the P2MP MPLS-TE subgroup-id of the sub-lsp. The subgroup-id is zero for the P2MP MPLS-TE
LSP virtual interface (VIF). Therefore, the mplsTunnelEgressLSRId has a zero value for the P2MP MPLS-TE LSP VIF. The mapping
of the remainder of the indices is similar to those found in the MPLS-TE MIB.
The following is a list and description of each supported mplsTeP2mpTunnelTable object:
-
mplsTeP2mpTunnelBranchRole—Supplements the value in the object mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role
of this LSR in the tunnel represented by this entry in mplsTeP2mpTunnelTable. This object supports the head, transit, and
tail in order to describe the role of LSR for the tunnel. The following objects describe the mplsTunnelRole:
- RRR_MGMT_TUN_ROLE_HEAD–Contains the value D_cmplsTeP2mpTunnelBranchRole_notBranch.
- RRR_MGMT_TUN_ROLE_MID–Contains the value D_cmplsTeP2mpTunnelBranchRole_branch.
- RRR_MGMT_TUN_ROLE_TAIL–Contains the value D_cmplsTeP2mpTunnelBranchRole_notBranch.
-
mplsTeP2mpTunnelP2mpXcIndex– Contains the value of mplsXCIndex, the primary index of the mplsXCTable for all cross-connect
entries for this P2MP MPLS-TE LSP.
-
mplsTeP2mpTunnelRowStatus– Contains the variable used to create, modify, and delete a row in this table. The row in this
table is in the active state only and no objects in that row can be modified by the agent except for the mplsTeP2mpTunnelRowStatus
and mplsTeP2mpTunnelStorageType.
-
mplsTeP2mpTunnelStorageType– Contains the storage type for this tunnel entry that may or may not be marked “volitile” because
this value may or may not be persisted.
mplsTeP2mpTunnelDestTable
An entry in this table represents a destination of a P2MP MPLS-TE tunnel. 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). This
table shows information about sub-LSPs (one entry per destination of the tunnel). An entry to a destination is considered
as sub-lsp.
The first three mplsTeP2mpTunnelDestTable indices are the same as the MPLS-TE MIB:
-
mplsTunnelIndex
-
mplsTunnelInstance
-
mplsTunnelIngressLSRId
The fourth index entry, mplsTunnelEgressLSRId maps to the P2MP MPLS-TE ID. The remainder of the indices are as follows:
-
mplsTeP2mpTunnelDestSrcSubGroupOriginType
-
mplsTeP2mpTunnelDestSrcSubGroupOrigin
-
mplsTeP2mpTunnelDestSrcSubGroupID
-
mplsTeP2mpTunnelDestSubGroupOriginType
-
mplsTeP2mpTunnelDestSubGroupOrigin
-
mplsTeP2mpTunnelDestSubGroupID
-
mplsTeP2mpTunnelDestDestinationType
-
mplsTeP2mpTunnelDestDestination
The following is a list and description of each supported mplsTeP2mpTunnelDestTable object:
-
mplsTeP2mpTunnelDestSrcSubGroupOriginType—Identifies the IPv4 address carried in mplsTeP2mpTunnelDestSrcSubGroupOrigin object
at a transit or egress LSR and has a value unknown (0) for an ingress LSR.
-
mplsTeP2mpTunnelDestSrcSubGroupOrigin—Contains the TE Router ID (reachable and stable IP address) of the originator of the
P2MP MPLS-TE subgroup as received on a Path message by a transit or egress LSR. This object maps to the ingress LSR ID for
a egress and transit LSR and unknown (0) for ingress LSR.
-
mplsTeP2mpTunnelDestSrcSubGroupID—Contains the unique identifier assigned by the subgroup originator for this subgroup of
this P2MP MPLS-TE tunnel as received on a Path message by a transit or egress LSR. This object maps to the subgroup ID for
the sub-LSP to this destination for an egress and transit LSR ID and 0 for Ingress. The rrr_get_lsp_id_p2mp_subgroup_id (lsp_id)
is used to fetch the value at egress or transit.
-
mplsTeP2mpTunnelDestSubGroupOriginType—Identifies the IPv4 address carried in the mplsTeP2mpTunnelDestSubGroupOrigin object.
-
mplsTeP2mpTunnelDestSubGroupOrigin—Contains the TE Router ID (reachable and stable IP address) of the originator of the P2MP
MPLS-TE subgroup. In many cases, this is the ingress LSR of the P2MP MPLS-TE tunnel and is the received signaled value as
available in mplsTeP2mpTunnelDestSrcSubGroupOrigin object. This object maps to Ingress LSR ID.
Note |
The
show mpls traffic-eng tunnels command can be used to list the source address for tunnel that maps to this object's value.
|
-
mplsTeP2mpTunnelDestSubGroupOrigin—Contains the unique identifier assigned by the subgroup originator for this subgroup of
this P2MP MPLS-TE tunnel. This object has the value of subgroup ID of the sub-LSP. At egress, this contains the value of mplsTeP2mpTunnelDestSrcSubGroupID.
-
mplsTeP2mpTunnelDestDestinationType—Identifies the IPv4 address carried in the mplsTeP2mpTunnelDestDestination object.
-
mplsTeP2mpTunnelDestDestination—Identifies the single destination of this P2MP MPLS-TE tunnel that is the TE address of a
leaf that can be routed. This is often the TE Router ID of the leaf, but can be any interface address. When a signaling protocol
is used, this object corresponds to the S2L sub-LSP destination address field in the S2L_SUB_LSP object. This object maps
to the destination address of the sub-LSP.
-
mplsTeP2mpTunnelDestBranchOutSegment—Identifies the outgoing branch from this LSR towards the destination represented by
this table entry. It must be a unique identifier within the scope of this tunnel. This object contains an index into mplsOutSegmentTable
object. This value maps to mplsOutSegmentIndex of the MPLS-LSR-STD-MIB. The LSR MIB shows the outgoing branches at a bud node.
This outsegmentindex value (for each outsegment) is mapped to each sub-LSP.
-
mplsTeP2mpTunnelDestHopTableIndex—Provides the index into the mplsTunnelHopListIndex of mplsTunnelHopTable of RFC TE MIB
entry that specifies the explicit route hops for this destination of the P2MP MPLS-TE tunnel. This index is only valid for
head entries. For nonhead entries the value is zero.
-
mplsTeP2mpTunnelDestPathInUse—Contains the value that denotes the configured path that was chosen as the explicit path to
this destination of this P2MP MPLS-TE tunnel. This value reflects the secondary index into mplsTunnelHopTable where the primary
index comes from mplsTeP2mpTunnelDestHopTableIndex. This object maps to mplsTunnelPathOptionIndex of RFC TE MIB. TE only supports
one path-option to be configured per sub-LSP, so the mplsTeP2mpTunnelDestPathInUse object is always 1.
-
mplsTeP2mpTunnelDestCHopTableIndex—Provides the index into the mplsTunnelCHopTable that identifies the explicit path for
this destination of the P2MP MPLS-TE tunnel. This object maps to mplsTunnelCHopListIndex of RFC TE MIB.
-
mplsTeP2mpTunnelDestARHopTableIndex—Provides the index into the mplsTunnelARHopTable that identifies the actual hops traversed
to this destination of the P2MP MPLS-TE tunnel. This is automatically updated by the agent when the actual hops become available.
This object maps to mplsTunnelARHopTableIndex of RFC TE MIB.
-
mplsTeP2mpTunnelDestAdminStatus—Indicates the desired operational status of this destination of this P2MP MPLS-TE tunnel.
Status can be up or down.
-
mplsTeP2mpTunnelDestOperStatus—Indicates the actual operational status of this destination of this P2MP MPLS-TE tunnel.
-
mplsTeP2mpTunnelDestRowStatus—Creates, modifies, and/or deletes a row in this table. When a row in this table is in the active
(1) state, no objects in that row can be modified by SET operations except mplsTeP2mpTunnelDestAdminStatus and mplsTeP2mpTunnelDestStorageType.
-
mplsTeP2mpTunnelDestStorageType—Indicates the storage type for this table entry which is permanent. Conceptual rows having
the value “permanent” do not allow write-access to any columnar objects in the row.
mplsTeP2mpTunnelBranchPerfBranch
An entry in this table provides information about P2MP MPLS-TE Tunnel. The mapping of the first four indices is similar to
mplsTeP2mpTunnelTable. The table shows the outsegment information for head and transit entries. For tail entries, the entries
are shown to display that tails are configured but values for objects are not provided.
This table has five indices:
The following is a list and description of each supported mplsTeP2mpTunnelBranchPerfBranch object:
-
mplsTeP2mpTunnelBranchPerfBranch—Identifies an outgoing branch from this LSR for this tunnel. Its value is unique within
the context of the tunnel. 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 destinations
reached on this branch. This value maps to mplsOutSegmentIndex of MPLS-LSR-STD-MIB.
-
mplsTeP2mpTunnelBranchPerfPackets—Displays the number of packets forwarded by the tunnel onto this branch. This object should
represents the 32-bit value of the least significant part of the 64-bit value if both mplsTeP2mpTunnelBranchPerfHCPackets
is returned. This object should be read in conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime object.
Note |
The
show interface tunnel
command can be used to see the value of packets.
|
-
mplsTeP2mpTunnelBranchPerfHCPackets—Displays the High Capacity counter for number of packets forwarded by the tunnel onto
this branch.
-
mplsTeP2mpTunnelBranchPerfErrors—Displays the number of packets dropped because of errors or for other reasons, that were
supposed to be forwarded onto this branch for this tunnel. This object should be read in conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime
object.
-
mplsTeP2mpTunnelBranchPerfBytes—Displays the number of bytes forwarded by the tunnel onto this branch. This object should
represent the 32-bit value of the least significant part of the 64-bit value if both mplsTeP2mpTunnelBranchPerfHCBytes is
returned. This object should be read in conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime object.
Note |
The
show mpls forwarding-table command can be used to verify the values.
|
-
cmplsTeP2mpTunnelBranchLocalLabel—Displays the local MPLS label for this branch.
Note |
Use the
show mpls traffic-eng forwarding path-set and
show cef path set detail commands can also be used to view label information.
|
-
cmplsTeP2mpTunnelBranchOutIfIndex—Displays the index of outgoing TE link physical interface for the P2MP MPLS-TE egress tunnel
branch. It is nonzero when the P2MP MPLS-TE tunnel’s outgoing branch has been signaled.
-
cmplsTeP2mpTunnelBranchOutLabel—Displays the outgoing MPLS label for this branch.
Note |
Use the
show mpls traffic-eng forwarding path-set and
show cef path set detail commands can also be used to view label information.
|
-
cmplsTeP2mpTunnelBranchInIfIndex—Displays the index of incoming TE link physical interface for the P2MP MPLS-TE ingress tunnel
branch. It is nonzero when the P2MP MPLS-TE tunnel's incoming branch has been signaled and it is applicable only on midpoint
routers for tunnels having out-segment up and running.
Feedback