PRVT-CR-LDP-MIB: View SNMP OID List / Download MIB

The MIB module for management of the PRVT-CR-LDP

The table of active instances of PRVT-CR-LDP Signaling.

Each of these entries represents an instance of PRVT-CR-LDP Signaling running in the HAF. Some of these instances will be the primary, and others may be backups.

The index of this prvtcrldpSigEntry. This is the HAF entity index passed on the product create parameters.

The index of the Path Manager instance to which this instance of Signaling is to join. See prvtcrldpPmTable.

The index of the PRVT-LMGR product instance to which this PRVT-CR-LDP Signaling is to join as its LDB interface provider. See prvtlmgrLsrEntityTable.

Management assigned interface identifier for the IP Sockets component interface to PRVT-CR-LDP Signalling.

The number of pre-reserved buffers available for sending sockets and LDI messages for each LDP session. This is used to pace the sockets and LDI data flows for each LDP session.

The number of pre-reserved buffers available for sending sockets, LDBI, NHR and I3 messages within Entity Manager This is used to pace Entity Manager's sockets, LDBI, NHR and I3 data flows.

The number of pre-reserved buffers available for sending sockets messages within Adjacency Manager. This is used to pace Adjacency Manager's sockets data flows.

This object is used to activate the PRVT-CR-LDP Signaling instance.

The current operational status of this instance of PRVT-CR-LDP Signaling.

Used to create and delete a PRVT-CR-LDP Signaling Table entry. When this object is set to 'active', only the prvtcrldpSigAdminStatus object in the row may be modified.

Used to indicate whether this PRVT-CR-LDP Signaling instance should use the I3 interface or the IPR interface to determine information regarding local interface configuration. Use of the IPR interface is deprecated, but nevertheless this field defaults to its use for back-compatibility reasons.

Flags specifying how PRVT-LDP Session Controller should behave in situations either where the interpretation of strict conformance is debatable, or where strictly conformant behavior contradicts the general IETF principle of being liberal on receipt. maxPduLen If set, this flag means that PRVT-LDP should abort session initialization if the peer (in the passive role) proposes a max PDU length that is larger than PRVT-LDP's proposed value. The interpretation here is that the passive peer's value should be the already negotiated value, not its raw value. Bits: 'maxPduLen': 0.

Used to indicate whether the PRVT-CR-LDP signaling is to use IPv6 transport where possible. Note that if PRVT-LDP is configured with an IPv4 transport address, IPv4 transport will be used for multicast and IPv6 sockets using a IPv4 mapped IPv6 address will be used for unicast when this field is set to True.

If this object is true, then it enables the generation of mplsLdpSessionUp and mplsLdpSessionDown traps, otherwise these traps are not generated.

If this object is true, then it enables the generation of mplsLdpInitSessionThresholdExceeded traps, otherwise these traps are not generated.

If this object is true, then it enables the generation of mplsLdpPathVectorLimitMismatch traps, otherwise these traps are not generated.

The table of active instances of PRVT-CR-LDP Path Manager.

Each of these entries represents an instance of PRVT-CR-LDP Path Manager running in the HAF. Some of these instances will be the primary, and others may be backups.

The index of this prvtcrldpPmEntry. This is the HAF entity index passed on the product create parameters.

The index of the PRVT-LMGR product instance to which this PRVT-CR-LDP Path Manager is to join as its LDB interface provider. See prvtlmgrLsrEntityTable.

When set to 'true', the Entity Manager component of PRVT-CR-LDP creates Entities automatically based on interfaces known to Entity Manager. When set to 'false' Entities are not automatically created.

When set to 'true', the Entity Manager component of PRVT-CR-LDP automatically starts Entities. Both configured and automatically created Entities are automatically started. When set to 'false' Entities are not automatically started.

When set to 'true', the same Entity can be used for multiple interfaces. That is, the per-platform label space behaves as a per-interface label space. When set to 'false', the same entity cannot be used for multiple interfaces.

An indication of the LDP version supported. Enumeration: 'version1': 1.

When set to 'true', PRVT-CR-LDP implements fault tolerance procedures for LDP and CR-LDP. When set to 'false', fault tolerance procedures are not used.

The number identifying the autonomous system (AS) to which this node belongs.

The size of the buffer pool used for sending either (deprecated) IPRI messages or for sending NHR and I3 messages. This is used to pace IPR/NHR+I3 data flows from PM.

When set to 'true', PRVT-CR-LDP implements LDP functionality. When set to 'false' received LDP requests are rejected. Note that at least one of prvtcrldpPmLdpSupported and prvtcrldpPmCrLdpSupported must be set to 'true' before activating a prvtcrldpPmTable row. Both prvtcrldpPmLdpSupported and prvtcrldpPmCrLdpSupported may be set to 'true'.

When set to 'true', PRVT-CR-LDP implements CR-LDP functionality. When set to 'false' received CR-LDP requests are rejected. Note that at least one of prvtcrldpPmLdpSupported and prvtcrldpPmCrLdpSupported must be set to 'true' before activating a prvtcrldpPmTable row. Both prvtcrldpPmLdpSupported and prvtcrldpPmCrLdpSupported may be set to 'true'.

When set to 'true', PRVT-CR-LDP queries the routing stub when a label mapping for an unrecognized FEC is received to determine whether the FEC should be recognized and the corresponding switch programming performed or not. If set to 'false' PRVT-CR-LDP creates a dummy FEC for the mapping and retains or releases the mapping based on the label retention policy for the session.

This object is used to activate the PRVT-CR-LDP Path Manager instance.

The current operational status of this instance of PRVT-CR-LDP Path Manager.

Used to create and delete a PRVT-CR-LDP Path Manager Table entry. When this object is set to 'active', only the prvtcrldpPmAdminStatus object in the row may be modified.

A flag to indicate whether the local node should advertise itself as LDP restart capable if the Label Switch Controller or Label Data Forwarder is capable of supporting the required procedures.

The time in milliseconds that the local node takes to restart LDP and bring up the LDP sessions. This is advertised to neighbors in the FT Session TLV in Initialization messages. The value chosen should be large enough for LDP to be terminated and restarted. Only used if prvtcrldpPmRestartCapable is set to true.

The period of time in milliseconds that the local node is willing to retain its MPLS forwarding state, if any, that it preserved across the restart. The time is from the end of the restart time configured above. Only used if prvtcrldpPmRestartCapable is set to true.

The maximum period of time in milliseconds that LDP should wait for a restart capable neighbor to restore an LDP session. LDP waits for the minimum of this time and the Reconnect Timeout advertised in the FT Session TLV in the Initialization message from the neighbor. Only used if prvtcrldpPmRestartCapable is set to true.

The maximum period of time in milliseconds that LDP should wait for a restart capable neighbor to refresh Label Mappings previously received from that neighbor before deleting the stale bindings. LDP waits for the minimum of this time and the Recovery Time advertised in the FT Session TLV in the Initialization message from the neighbor. Only used if prvtcrldpPmRestartCapable is set to true.

The time in milliseconds to hold a failed LDP Hello adjacency to distinguish between LDP peer failure and interface failure. This field is used to ensure that LDP retains adjacency multi-link LSPs during peer restart recovery when the peer restarts and an LDP Hello adjacency goes down before the LDP session. When an LDP Hello adjacency fails, Path Manager waits until the adjacency holding timer expires before tearing down any LSP out segments associated with the adjacency. If the LDP session fails before the adjacency holding timer expires, Path Manager performs peer restart recovery instead of tearing down any LSP out segments. If the adjacency holding timer expires and the LDP session is still active then Path Manager assumes that the interface has failed but the peer is still active. In this case Path Manager tears down LSP out segments associated with the adjacency. The value chosen should be large enough for the LDP session to fail if the LDP peer has failed. Only used if _restart_capable_ is set to AMB_TRUE, and cannot be modified when the _row_status_ is ACTIVE.

This determines the order in which LDP connects and releases out segments. default: This will release all out-segments on a session before programming new out-segments on the same session. No ordering for out-segments across different sessions is enforced when ECMP is in use. connFirst: This mode forces all the out-segments for an LSP to be programmed before any out-segments are released. This ordering is only supported if the LSC stub supports implicit XCs. Enumeration: 'default': 0, 'connFirst': 1.

This field indicates whether LDP Path Manager supports IPv6 addresses, FECs and routes. If this field is set to false then no IPv6 addresses will be accepted over the NHR and I3 interfaces and all LDP protocol messages for IPv6 addresses or FECs will be returned to the peer as an LDP status code of 'Unsupported Address Family'.

This field contains bit flags which indicate whether PRVT-LDP supports LDP Policy and if per FEC policy optimization is to be used. The supported bit flags are defined below. - policySupported - perFecOptimizationSupported - suppressAddressPolicy. The policySupported flag indicates that PRVT-LDP will enforce policy decisions made by the user through a number of user exits. If this flag is not set PRVT-LDP will not call policy user exits. The perFecOptimizationSupported flag indicates that PRVT-LDP provides policy on a per FEC basis as opposed to a per FEC per session basis. This results in policy user exits only being called once per FEC. This field is only significant if the policySupported flag is set. This feature is used to reduce the number of calls to the Policy User Exits particularly when a change in Policy is being implemented. If the perFecOptimizationSupported flag is not set then PRVT-LDP Path Manager enforces policy on a per FEC per peer basis. If this flag is set policy is enforced on a per FEC basis and the same policy decision is assumed to apply for all peers. The suppressAddressPolicy flag if set prevents PRVT-LDP from performing any Policy processing on receipt of a Address or Address Withdraw message from a peer. If this field is not set then its default value is determined by the RCP_USER_DO_POLICY compile time flag. Changes to the value of policy_support_flags are not permitted whilst the MIB row is active. Bits: 'perFecOptimizationSupported': 1, 'suppressAddressPolicy': 2, 'policySupported': 0.

This field indicates whether LDP Path Manager makes the programming of each out segment conditional on the status of the interface where the out segment is programmed. When set to false, LDP Path Manager assumes that the availability of interfaces for programming is reflected in the adjacency and session information that it receives from LDP Session Controller, and in the routing information that it receives from the NHR stub. When set to true, LDP Path Manager tracks interface status itself and uses this in addition to input from LDP Session Controller and the NHR stub to decide whether an out segment should be programmed on a particular interface. If the other inputs indicate 'yes', but the relevant interface is (or goes) down, LDP Path Manager will not program that out segment (or will remove the existing out segment on that interface). This field cannot be changed when the row is active.