EZ5 MIB Catalog

MPLS-MIB

2009-02-23

The MIB module for Multi-Protocol Label Switched Paths.

Download MPLS-MIB.txt Open MPLS-MIB.txt in a new tab

SCALARS (5) · TABLES (3) · TRAPS (10)

Scalars (5)

NameOID
mplsVersion1.3.6.1.4.1.2636.3.2.1.1
mplsSignalingProto1.3.6.1.4.1.2636.3.2.1.2
mplsConfiguredLsps1.3.6.1.4.1.2636.3.2.1.3
mplsActiveLsps1.3.6.1.4.1.2636.3.2.1.4
mplsTEDistProtocol1.3.6.1.4.1.2636.3.2.2.1

Tables (3)

NameOID
mplsAdminGroupList1.3.6.1.4.1.2636.3.2.2.2
mplsLspList1.3.6.1.4.1.2636.3.2.3
mplsLspInfoList1.3.6.1.4.1.2636.3.2.5

Traps (10)

NameOID
mplsLspInfoUp1.3.6.1.4.1.2636.3.2.0.1
mplsLspInfoDown1.3.6.1.4.1.2636.3.2.0.2
mplsLspInfoChange1.3.6.1.4.1.2636.3.2.0.3
mplsLspInfoPathDown1.3.6.1.4.1.2636.3.2.0.4
mplsLspInfoPathUp1.3.6.1.4.1.2636.3.2.0.5
mplsLspUp(deprecated)1.3.6.1.4.1.2636.3.2.4.1
mplsLspDown(deprecated)1.3.6.1.4.1.2636.3.2.4.2
mplsLspChange(deprecated)1.3.6.1.4.1.2636.3.2.4.3
mplsLspPathDown(deprecated)1.3.6.1.4.1.2636.3.2.4.4
mplsLspPathUp(deprecated)1.3.6.1.4.1.2636.3.2.4.5

END OF TOC

Scalar details

mplsVersion

1.3.6.1.4.1.2636.3.2.1.1

Integer32

MPLS version number.

mplsSignalingProto

1.3.6.1.4.1.2636.3.2.1.2

INTEGER1 = none2 = other3 = rsvp4 = ldp · Integer32

MPLS signaling protocol.

mplsConfiguredLsps

1.3.6.1.4.1.2636.3.2.1.3

Integer32

Number of configured LSPs.

mplsActiveLsps

1.3.6.1.4.1.2636.3.2.1.4

Integer32

Number of active LSPs.

mplsTEDistProtocol

1.3.6.1.4.1.2636.3.2.2.1

INTEGER1 = none2 = isis3 = ospf4 = isis-ospf · Integer32

IGP used to distribute Traffic Engineering information and topology to each LSR for the purpose of automatic path computation.

Table details

mplsAdminGroupList

1.3.6.1.4.1.2636.3.2.2.2

Index: mplsAdminGroupNumber

List of configured administrative groups. Administrative groups are used to label links in the Traffic Engineering topology in order to place constraints (include and exclude) on LSP paths.

mplsAdminGroupNumber

1.3.6.1.4.1.2636.3.2.2.2.1.1

INTEGER (0..31) · Integer32

Index of the administrative group.

mplsAdminGroupName

1.3.6.1.4.1.2636.3.2.2.2.1.2

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

Name of the administrative group.

mplsLspList

1.3.6.1.4.1.2636.3.2.3

Index: mplsLspName

******* Deprecated Object ****** List of Configured Label Switched Paths. This object has been deprecated and replaced by mplsLspInfoList

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsLspState

1.3.6.1.4.1.2636.3.2.3.1.2

INTEGER1 = unknown2 = up3 = down4 = notInService5 = backupActive · Integer32

The operational state of the LSP.

mplsLspOctets

1.3.6.1.4.1.2636.3.2.3.1.3

Counter64 (0..18446744073709551615)

The number of octets that have been forwarded over current LSP active path. The number reported is not realtime, may subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsLspPackets

1.3.6.1.4.1.2636.3.2.3.1.4

Counter64 (0..18446744073709551615)

The number of packets that have been forwarded over current LSP active path. The number reported is not realtime, may subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsLspAge

1.3.6.1.4.1.2636.3.2.3.1.5

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The age (i.e., time from creation till now) of this LSP in 10-millisecond periods.

mplsLspTimeUp

1.3.6.1.4.1.2636.3.2.3.1.6

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The total time in 10-millisecond units that this LSP has been operational. For example, the percentage up time can be determined by computing (mplsLspTimeUp/mplsLspAge * 100 %).

mplsLspPrimaryTimeUp

1.3.6.1.4.1.2636.3.2.3.1.7

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The total time in 10-millisecond units that this LSP's primary path has been operational. For example, the percentage contribution of the primary path to the operational time is given by (mplsLspPrimaryTimeUp/mplsLspTimeUp * 100) %.

mplsLspTransitions

1.3.6.1.4.1.2636.3.2.3.1.8

Counter32

The number of state transitions (up -> down and down -> up) this LSP has undergone.

mplsLspLastTransition

1.3.6.1.4.1.2636.3.2.3.1.9

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time in 10-millisecond units since the last transition occurred on this LSP.

mplsLspPathChanges

1.3.6.1.4.1.2636.3.2.3.1.10

Counter32

The number of path changes this LSP has had. For every path change (path down, path up, path change), a corresponding syslog/trap (if enabled) is generated for it.

mplsLspLastPathChange

1.3.6.1.4.1.2636.3.2.3.1.11

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time in 10-millisecond units since the last change occurred on this LSP.

mplsLspConfiguredPaths

1.3.6.1.4.1.2636.3.2.3.1.12

Integer32

The number of paths configured for this LSP.

mplsLspStandbyPaths

1.3.6.1.4.1.2636.3.2.3.1.13

Integer32

The number of standby paths configured for this LSP.

mplsLspOperationalPaths

1.3.6.1.4.1.2636.3.2.3.1.14

Integer32

The number of operational paths for this LSP. This includes the path currently active, as well as operational standby paths.

mplsLspFrom

1.3.6.1.4.1.2636.3.2.3.1.15

IpAddress SIZE (4)

Source IP address of this LSP.

mplsLspTo

1.3.6.1.4.1.2636.3.2.3.1.16

IpAddress SIZE (4)

Destination IP address of this LSP.

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

mplsPathType

1.3.6.1.4.1.2636.3.2.3.1.18

INTEGER1 = other2 = primary3 = standby4 = secondary5 = bypass · Integer32

The type of path that is active, i.e., a primary path, a standby path, a generic secondary path, or a bypass path. The value other, primary, standby and secondary apply to data LSPs, and are meaningful only if mplsPathName is not empty. The value bypass applies to bypass tunnels. A bypass tunnel may have an empty mplsPathName.

mplsPathExplicitRoute

1.3.6.1.4.1.2636.3.2.3.1.19

OCTET STRING SIZE (0..1024)

The explicit route used to set up this LSP. This may either be the route configured by the user, or a route automatically computed to satisfy constraints set by the user. This field is a displayable string in the format of XXX.XXX.XXX.XXX <space> S/L <newline> repeated for each explicit address. The S/L character stands for Strict/Loose route. This field is meaningless unless mplsPathName is not empty

mplsPathRecordRoute

1.3.6.1.4.1.2636.3.2.3.1.20

OCTET STRING SIZE (0..1024)

The route actually used for this path, as recorded by the signaling protocol. This field is a displayable string in the format of XXX.XXX.XXX.XXX <space> repeated for each address. This field is meaningless unless mplsPathName is not empty

mplsPathBandwidth

1.3.6.1.4.1.2636.3.2.3.1.21

Integer32

The configured bandwidth for this LSP, in units of thousands of bits per second (Kbps). This field is meaningless unless mplsPathName is not empty

mplsPathCOS

1.3.6.1.4.1.2636.3.2.3.1.22

INTEGER (0..7 | 255) · Integer32

The configured Class Of Service on this path. If the value is between 0 and 7 inclusive, this value will be inserted in the 3 bit COS field in the label. If the value is 255, the value in the COS field of the label will depend on other factors. This field is meaningless unless mplsPathName is not empty

mplsPathInclude

1.3.6.1.4.1.2636.3.2.3.1.23

Integer32

This is a configured set of colors (administrative groups) specified as a bit vector (i.e., bit n is 1 if color n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link MUST have colors associated with it, and the intersection of the link's colors and the 'include' set MUST be non-null. This field is meaningless unless mplsPathName is not empty

mplsPathExclude

1.3.6.1.4.1.2636.3.2.3.1.24

Integer32

This is a configured set of colors (administrative groups) specified as a bit vector (i.e., bit n is 1 if color n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link MUST have colors associated with it, and the intersection of the link's colors and the 'exclude' set MUST be null. This field is meaningless unless mplsPathName is not empty

mplsPathSetupPriority

1.3.6.1.4.1.2636.3.2.3.1.25

INTEGER (0..7) · Integer32

The setup priority configured for this path. This field is meaningless unless mplsPathName is not empty

mplsPathHoldPriority

1.3.6.1.4.1.2636.3.2.3.1.26

INTEGER (0..7) · Integer32

The hold priority configured for this path. This field is meaningless unless mplsPathName is not empty

mplsPathProperties

1.3.6.1.4.1.2636.3.2.3.1.27

INTEGER1 = record-route2 = adaptive4 = cspf8 = mergeable16 = preemptable32 = preemptive64 = fast-reroute · Integer32

The set of configured properties for this path, expressed as a bit map. For example, if the path is an adaptive path, the bit corresponding to bit value xxx is set. This field is meaningless unless mplsPathName is not empty

mplsLspInfoList

1.3.6.1.4.1.2636.3.2.5

Index: IMPLIED mplsLspInfoName

List of Configured Label Switched Paths.

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsLspInfoState

1.3.6.1.4.1.2636.3.2.5.1.2

INTEGER1 = unknown2 = up3 = down4 = notInService5 = backupActive · Integer32

The operational state of the LSP.

mplsLspInfoOctets

1.3.6.1.4.1.2636.3.2.5.1.3

Counter64 (0..18446744073709551615)

The number of octets that have been forwarded over current LSP active path. The number reported is not realtime, may subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsLspInfoPackets

1.3.6.1.4.1.2636.3.2.5.1.4

Counter64 (0..18446744073709551615)

The number of packets that have been forwarded over current LSP active path. The number reported is not realtime, may subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsLspInfoAge

1.3.6.1.4.1.2636.3.2.5.1.5

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The age (i.e., time from creation till now) of this LSP in 10-millisecond periods.

mplsLspInfoTimeUp

1.3.6.1.4.1.2636.3.2.5.1.6

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The total time in 10-millisecond units that this LSP has been operational. For example, the percentage up time can be determined by computing (mplsLspInfoTimeUp/mplsLspInfoAge * 100 %).

mplsLspInfoPrimaryTimeUp

1.3.6.1.4.1.2636.3.2.5.1.7

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The total time in 10-millisecond units that this LSP's primary path has been operational. For example, the percentage contribution of the primary path to the operational time is given by (mplsLspInfoPrimaryTimeUp/mplsLspInfoTimeUp * 100) %.

mplsLspInfoTransitions

1.3.6.1.4.1.2636.3.2.5.1.8

Counter32

The number of state transitions (up -> down and down -> up) this LSP has undergone.

mplsLspInfoLastTransition

1.3.6.1.4.1.2636.3.2.5.1.9

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time in 10-millisecond units since the last transition occurred on this LSP.

mplsLspInfoPathChanges

1.3.6.1.4.1.2636.3.2.5.1.10

Counter32

The number of path changes this LSP has had. For every path change (path down, path up, path change), a corresponding syslog/trap (if enabled) is generated for it.

mplsLspInfoLastPathChange

1.3.6.1.4.1.2636.3.2.5.1.11

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time in 10-millisecond units since the last change occurred on this LSP.

mplsLspInfoConfiguredPaths

1.3.6.1.4.1.2636.3.2.5.1.12

Integer32

The number of paths configured for this LSP.

mplsLspInfoStandbyPaths

1.3.6.1.4.1.2636.3.2.5.1.13

Integer32

The number of standby paths configured for this LSP.

mplsLspInfoOperationalPaths

1.3.6.1.4.1.2636.3.2.5.1.14

Integer32

The number of operational paths for this LSP. This includes the path currently active, as well as operational standby paths.

mplsLspInfoFrom

1.3.6.1.4.1.2636.3.2.5.1.15

IpAddress SIZE (4)

Source IP address of this LSP.

mplsLspInfoTo

1.3.6.1.4.1.2636.3.2.5.1.16

IpAddress SIZE (4)

Destination IP address of this LSP.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsPathInfoType

1.3.6.1.4.1.2636.3.2.5.1.18

INTEGER1 = other2 = primary3 = standby4 = secondary5 = bypass · Integer32

The type of path that is active, i.e., a primary path, a standby path, a generic secondary path, or a bypass path. The value other, primary, standby and secondary apply to data LSPs, and are meaningful only if mplsPathInfoName is not empty. The value bypass applies to bypass tunnels. A bypass tunnel may have an empty mplsPathInfoName.

mplsPathInfoExplicitRoute

1.3.6.1.4.1.2636.3.2.5.1.19

OCTET STRING SIZE (0..1024)

The explicit route used to set up this LSP. This may either be the route configured by the user, or a route automatically computed to satisfy constraints set by the user. This field is a displayable string in the format of XXX.XXX.XXX.XXX <space> S/L <newline> repeated for each explicit address. The S/L character stands for Strict/Loose route. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoRecordRoute

1.3.6.1.4.1.2636.3.2.5.1.20

OCTET STRING SIZE (0..1024)

The route actually used for this path, as recorded by the signaling protocol. This field is a displayable string in the format of XXX.XXX.XXX.XXX <space> repeated for each address. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoBandwidth

1.3.6.1.4.1.2636.3.2.5.1.21

Integer32

The configured bandwidth for this LSP, in units of thousands of bits per second (Kbps). This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoCOS

1.3.6.1.4.1.2636.3.2.5.1.22

INTEGER (0..7 | 255) · Integer32

The configured Class Of Service on this path. If the value is between 0 and 7 inclusive, this value will be inserted in the 3 bit COS field in the label. If the value is 255, the value in the COS field of the label will depend on other factors. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoInclude

1.3.6.1.4.1.2636.3.2.5.1.23

Integer32

This is a configured set of colors (administrative groups) specified as a bit vector (i.e., bit n is 1 if color n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link MUST have colors associated with it, and the intersection of the link's colors and the 'include' set MUST be non-null. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoExclude

1.3.6.1.4.1.2636.3.2.5.1.24

Integer32

This is a configured set of colors (administrative groups) specified as a bit vector (i.e., bit n is 1 if color n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link MUST have colors associated with it, and the intersection of the link's colors and the 'exclude' set MUST be null. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoSetupPriority

1.3.6.1.4.1.2636.3.2.5.1.25

INTEGER (0..7) · Integer32

The setup priority configured for this path. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoHoldPriority

1.3.6.1.4.1.2636.3.2.5.1.26

INTEGER (0..7) · Integer32

The hold priority configured for this path. This field is meaningless unless mplsPathInfoName is not empty

mplsPathInfoProperties

1.3.6.1.4.1.2636.3.2.5.1.27

INTEGER1 = record-route2 = adaptive4 = cspf8 = mergeable16 = preemptable32 = preemptive64 = fast-reroute · Integer32

The set of configured properties for this path, expressed as a bit map. For example, if the path is an adaptive path, the bit corresponding to bit value xxx is set. This field is meaningless unless mplsPathInfoName is not empty

mplsLspInfoAggrOctets

1.3.6.1.4.1.2636.3.2.5.1.28

Counter64 (0..18446744073709551615)

The number of octets that have beeen forwarded over current LSP. This is an aggregate count of octets forwarded over all LSP instances from the time LSP was up. The number reported is not realtime, may be subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsLspInfoAggrPackets

1.3.6.1.4.1.2636.3.2.5.1.29

Counter64 (0..18446744073709551615)

The number of packets that have been forwarded over current LSP. This is an aggregate count of packets forwarded over all LSP instances from the time LSP was up. The number reported is not realtime, may be subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment.

mplsPathInfoRecordRouteWithLabels

1.3.6.1.4.1.2636.3.2.5.1.30

OCTET STRING SIZE (0..1024)

The route actually used for this path, as recorded by the signaling protocol. This field is a displayable string in the format of XXX.XXX.XXX.XXX <flag/label> <space> repeated for each address. This field is meaningless unless mplsPathInfoName is not empty

Trap details

mplsLspInfoUp

1.3.6.1.4.1.2636.3.2.0.1

An mplsLspInfoUp trap signifies that the specified LSP is up. The current active path for the LSP is mplsPathInfoName.

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsLspInfoDown

1.3.6.1.4.1.2636.3.2.0.2

An mplsLspInfoDown trap signifies that the specified LSP is down, because the current active path mplsPathInfoName went down.

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsLspInfoChange

1.3.6.1.4.1.2636.3.2.0.3

An mplsLspInfoChange trap signifies that the the specified LSP has switched traffic to the new active path 'toLspPath'. The LSP maintains up state before and after the switch over

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsLspInfoPathDown

1.3.6.1.4.1.2636.3.2.0.4

An mplsLspInfoPathDown trap signifies that the specified path mplsPathName for the specified LSP mplsLspInfoName went down

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsLspInfoPathUp

1.3.6.1.4.1.2636.3.2.0.5

An mplsLspInfoPathUp trap signifies that the specified path mplsPathName for the specified LSP mplsLspInfoName came up

mplsLspInfoName

1.3.6.1.4.1.2636.3.2.5.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a

Name of the Label Switched Path.

mplsPathInfoName

1.3.6.1.4.1.2636.3.2.5.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspInfoEntry are meaningless.

mplsLspUp

1.3.6.1.4.1.2636.3.2.4.1

An mplsLspUp trap signifies that the specified LSP is up. The current active path for the LSP is mplsPathName.

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

mplsLspDown

1.3.6.1.4.1.2636.3.2.4.2

An mplsLspDown trap signifies that the specified LSP is down, because the current active path mplsPathName went down.

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

mplsLspChange

1.3.6.1.4.1.2636.3.2.4.3

An mplsLspChange trap signifies that the the specified LSP has switched traffic to the new active path 'toLspPath'. The LSP maintains up state before and after the switch over

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

mplsLspPathDown

1.3.6.1.4.1.2636.3.2.4.4

An mplsLspPathDown trap signifies that the specified path mplsPathName for the specified LSP mplsLspName went down

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

mplsLspPathUp

1.3.6.1.4.1.2636.3.2.4.5

An mplsLspPathUp trap signifies that the specified path mplsPathName for the specified LSP mplsLspName came up

mplsLspName

1.3.6.1.4.1.2636.3.2.3.1.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (32) · OCTET STRING · hint 255a

******* Deprecated Object ****** Name of the Label Switched Path. This object has been deprecated and replaced by mplsLspInfoName

mplsPathName

1.3.6.1.4.1.2636.3.2.3.1.17

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..16) · OCTET STRING · hint 255a

The name of the active path for this LSP, if any. If there is none, the name should be empty; in that case, the rest of the fields in mplsLspEntry are meaningless.

↑ To TOC