MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 10 (transmission). 166 (mplsStdMIB). 2 (mplsLsrStdMIB). 1 (mplsLsrObjects). 7 (mplsOutSegmentTable). 1 (mplsOutSegmentEntry)
OID : 1.3.6.1.2.1.10.166.2.1.7.1
TXT : iso. org. dod. internet. mgmt. mib-2. transmission. mplsStdMIB. mplsLsrStdMIB. mplsLsrObjects. mplsOutSegmentTable. mplsOutSegmentEntry
Enfants
D├ętails
OID1.3.6.1.2.1.10.166.2.1.7.1
Module MPLS-LSR-STD-MIB (CISCO)
NommplsOutSegmentEntry
Statuscurrent
DescriptionAn entry in this table represents one outgoing segment. An entry can be created by a network administrator, an SNMP agent, or an MPLS signaling protocol. The object mplsOutSegmentOwner indicates the creator of this entry. The value of mplsOutSegmentRowStatus cannot be active(1) unless the ifTable entry corresponding to mplsOutSegmentInterface exists. Note that the indexing of this table uses a single, arbitrary index (mplsOutSegmentIndex) to indicate which out-segment (i.e.: label) is being switched to from which in-segment (i.e: label) or in-segments. This is necessary because it is possible to have an equal-cost multi-path situation where two identical out-going labels are assigned to the same cross-connect (i.e.: they go to two different neighboring LSRs); thus, requiring two out-segments. In order to preserve the uniqueness of the references by the mplsXCEntry, an arbitrary integer must be used as the index for this table.
Module MPLS-LSR-STD-MIB (ietf)
NommplsOutSegmentEntry
Statuscurrent
DescriptionAn entry in this table represents one outgoing segment. An entry can be created by a network administrator, an SNMP agent, or an MPLS signaling protocol. The object mplsOutSegmentOwner indicates the creator of this entry. The value of mplsOutSegmentRowStatus cannot be active(1) unless the ifTable entry corresponding to mplsOutSegmentInterface exists. Note that the indexing of this table uses a single, arbitrary index (mplsOutSegmentIndex) to indicate which out-segment (i.e.: label) is being switched to from which in-segment (i.e: label) or in-segments. This is necessary because it is possible to have an equal-cost multi-path situation where two identical out-going labels are assigned to the same cross-connect (i.e.: they go to two different neighboring LSRs); thus, requiring two out-segments. In order to preserve the uniqueness of the references by the mplsXCEntry, an arbitrary integer must be used as the index for this table.