PRVT-LMGR-MIB: View SNMP OID List / Download MIB

The MIB module for management of the PRVT-LMGR product.

This object allows LSR Id value to be set. It is needed for unique identification of LSR instance, from which the packets are sent through created LDP session. Although every 32 bit value is valid, it is recommended the device's loopback ip address to be used. A value of zero indicates that no LSR ID has been configured. In this case, the signaling protocol stack should construct a unique LSR ID from the other information that is available to it (such as IP addresses). For example, PRVT-CR-LDP and PRVT-RSVP derive the LSR ID by taking the 32 low bits of the following _transport_address_ field, left padding with zeros if necessary.

Each entry represents an instance of the Label Manager. Each instance is identified by LSR index.

Each entry represents a Label Manager entity.

LSR index for this prvtLmgrLsrEntityEntry. This is the entity index passed in the Label Manager create parameters.

Administrative status for Label Manager. When prvtLmgrLsrEntityRowStatus is 'active' and prvtLmgrLsrEntityAdminStatus is 'up' Label Manager is active and only these two fields and prvtLmgrLsrEntityMinLsiBuffers can be modified.

The current operational status of the Label Manager entity.

Row status for the Label Manager table entry, used to create and destroy table entries. When prvtLmgrLsrEntityRowStatus is 'active' and prvtLmgrLsrEntityAdminStatus is 'up' Label Manager is active and only these two fields and prvtLmgrLsrEntityMinLsiBuffers can be modified.

Minimum number of buffers to allocate for Label Switch Interface requests. This number includes any buffers sent to the Label Switch Controller and awaiting a response.

Maximum number of buffers to allocate for Label Switch Interface requests. A value of 0 means no maximum, otherwise this value must equal or exceed the minimum buffer count.

Diagnostic field providing information about the status of the Label Switch Controller as seen by Label Manager.

Diagnostic field providing information about the number of active interfaces between Label Manager and the its Label Database Interface users (PRVT-TEMIB and PRVT-RSVP).

An ID that uniquely identifies this LSR within the network. The LSR ID is typically derived from one of the LSR's IP addresses. It may be used for path vector based loop detection if the signaling protocol in use implements that. A value of zero indicates that no LSR ID has been configured. In this case, the signaling protocol stack should construct a unique LSR ID from the other information that is available to it (such as IP addresses). For example, PRVT-CR-LDP and PRVT-RSVP derive the LSR ID by taking the 32 low bits of the following _transport_address_ field, left padding with zeros if necessary. The LSR ID is only used to identify this LSR on IPv4 networks. See dcLmgrLsrEntityIpv6TranAddr for equivalent function for use in IPv6 networks.

The type of the internetwork layer address used as the transport address. Currently this must be IPv4. See dcLmgrLsrEntityIpv6TranAddr, below, for the equivalent field for use in IPv6 networks. The transport address is used by LDP as the source transport address for LDP Hello messages for the global (per-platform) label space. The transport address is used by RSVP as the source address for messages originating on unnumbered interfaces. This object indicates how the value of mplsLdpEntityTransAddr is to be interpreted.

The length of the internetwork layer address used as the transport address for LDP Hello messages in the global label space and for messages originating on unnumbered interfaces in RSVP. Currently this must be an IPv4 address. This object indicates how many elements of the mplsLdpEntityTransAddr array are valid. This value must not exceed _LMGR_LSR_ADDR_LEN_.

The value of the internetwork layer address used as the transport address for LDP Hello messages in the global label space and for messages originating on unnumbered interfaces in RSVP. This must be an IPv4 address. See dcLmgrLsrEntityIpv6TranAddr, below, for the equivalent field for use in IPv6 networks. If the transport address is not set, then _lsr_id_ must be set to zero. In this case, the transport address and LSR ID are taken from an address on the Interface Information Interface.

The LSP control mode that this LSR should adopt. This field is only used by Label Manager in systems where it supports LDP and/or CR-LDP.

Whether this LSR should aim to merge LSPs, where permitted by the underlying hardware. This field is only used by Label Manager in systems where it supports LDP and/or CR-LDP.

Whether this LSR should perform loop detection. This field is only used by Label Manager in systems where it supports LDP and/or CR-LDP.

Whether Label Manager should perform LSP grouping on behalf of the LDBI user. This field is currently only used for systems supporting RSVP.

Whether Label Manager should automatically activate or deactivate static LSPs when the interfaces on which they depend become active or inactive.

Whether Label Manager should display the virtual cross connects its sets up at the Egress node of Implicit Null and Explicit Null LSPs in the mplsXcTable. These cross connects do not represent real switch programming, but do show the prescence of such LSPs, and correspond to the entries in the mplsTunnelTable for theses types of LSP.

The value of the internetwork address used for messages originating on unnumbered interfaces in RSVP in an IPv6 network. This value also uniquely identifies this LSR within an IPv6 network. If this address is not set, the IPv6 transport address is taken from an address on the Interface Information Interface. A length value of zero indicates that no IPv6 transport address has been configured. In this case, if IPv6 support is configured, the signaling protocol stack should use an IPv6 address configured to the signaling stack over the Interface Information Interface that is flagged as suitable for use as a stable address.

Each entry represents an instance of an LSP cross-conect between a single in-segment and a single out-segment.

Each entry represents an LSP cross connect.

XC index for this prvtLmgrLsrLspXc. This is the XC index assigned by Label Manager for the LSP.

Index for the in segment. This is the index assigned by Label Manager for the in segment.

If index for the in segment. This is the If index specified on setting up the in segment.

Top label for the in segment. This is the Label assigned by Label Manager Label Library for the in segment.

Index for the out segment. This is the index assigned by Label Manager for the out segment.

Interface Index for the out segment. This is the interface index specified when setting up the out segment.

Top label for the out segment. This is the label specified by the remote LSR for the out segment.

Next hop address for the out segment. This is the address specified by the remote LSR for the out segment.

The compliance statement for the PRVT-LMGR product.

Label Manager Entity Objects.

Miscellaneous Non-Mandatory Objects.