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

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

The table of RSVP entities.

Each entry represents an RSVP entity.

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

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

The TTL set on messages originating at this node. A value of 0 indicates this number is determined by other means.

The minimum granularity to allow an internal timer to be set in the PRVT-RSVP product code.

Management assigned interface identifier for the (internal) LRAPI interface between RSVP and TE-MIB components. This must be unique in the interface index namespace of the node - it MUST not match any real interface index. It is recommended that this is set to zero or 0x7FFFFFFF.

Management assigned IP address used to identify the (internal) LRAPI interface between RSVP and TE-MIB components. The configured API address MUST not be a real address in the network. It is recommended that this is set to a non-zero reserved address value, such as 224.0.0.0. If multi-stack support is set to PHOP, this address must be unique for each RSVP stack in the node. The same address(es) can be used on all nodes in the network.

This field is now deprecated.

This object is used to set the delay between detection of a path error and instigation of local repair procedures. This allows local routing updates to converge. A value of -1 indicates that local repair procedures should not take place, but that the error should be propagated upstream. Where FRR capabilities are supported at this node local_repair_delay must be set to -1.

This RSVP value, R, which is used to set the average interval between refresh path and resv messages. Note : If values for the if_refresh_interval and if_refresh_multiple are configured such that the following inequality is not obeyed : 6 * refresh_interval * (refresh_multiple + 0.5) < 0x7FFFFFFF. Then the time-to-die for the path value will be set to its maximum value and it is probable that the lsp will time out before a refresh arrives.

The RSVP value, K, which is the number of unresponded Path or Resv refresh attempts which must be made, spaced by the refresh interval before the state is deemed to have timed out. Note : See note in prvtRsvpProductRefreshInterval above.

The denominator of the fraction, SlewMax, which is the maximum allowable increase in the refresh interval, R, to prevent state timeout while changing R. R is increased by this fraction until it reaches the new desired value.

The numerator of the fraction, SlewMax, which is the maximum allowable increase in the refresh interval, R, to prevent state timeout while changing R. R is increased by this fraction until it reaches the new desired value.

The RSVP value, Kb, which is the number of refresh timeout periods after which blockade state is deleted.

The number of pre-reserved buffers available for sending sockets data. This is used to pace the sockets data flows.

The number of pre-reserved buffers available for programming the switch. This is used to ensure programming operations do not fail in buffer shortage conditions.

The number of pre-reserved buffers available for signalling TE-MIB. This is used to ensure signals are not lost in buffer shortage conditions.

The number of pre-reserved buffers available for route queries. This is used to ensure re-routing of many LSPs does not fail in buffer shortage conditions.

The setup priority to apply to LSPs which are not signalling this parameter. 0 represents the highest priority, 7 the lowest. The value of this object must be numerically more or equal (so lower or equal priority) than the value of the holding priority object.

The holding priority to apply to LSPs which are not signalling this parameter. 0 represents the highest priority, 7 the lowest. The value of this object must be numerically less or equal (so higher or equal priority) than the value of the holding priority object.

The desired administrative state of the RSVP entity.

The current operational state of this instance of PRVT-RSVP.

Used to create and delete a PRVT-RSVP Product Table entry. When this object is set to 'active', only the prvtRsvpProductAdminStatus object in the row may be modified.

The index of the PRVT-LMGR product instance which this PRVT-RSVP is to join to as its LDB interface provider. If this value is not specified, or the value of this object is 0, PRVT-RSVP will use the prvtRsvpProductIndex value as the Lsr index when joining on the LDB interface.

The index of the TE-MIB product instance which this PRVT-RSVP is to join to as its LRA interface provider. If this value is not specified, or the value of this object is 0, PRVT-RSVP will use the prvtRsvpProductIndex value as the TeMib Index when joining on the LRA interface.

A flag to indicate if multiple RSVP stacks are present in the same system as the current one and, if so, how they are supported. If set to PHOP, Path messages are forwarded to PRVT-RSVP with the Previous Hop value set as the hop prior to the incoming interface, not as the next hop interface as normal. If set to LIH, the hardware location of the current RSVP stack is used as the LIH in the HOP object.

A flag to indicate that PRVT-RSVP should use the hop by hop addressing scheme for PATH and PATH-TEAR messages it sends. If set then the IP addresses used in the IP header of PATH messages forwarded by PRVT-RSVP set source as the local outgoing interface IP address, and destination as the next hop router IP address.

A flag to indicate that PRVT-RSVP should attempt to insert a Notify Request object in all Path requests that is sends as ingress and all Resv requests that it sends as egress. The precise behavior is modified by a user exit called by the RSVP code. This field is not used unless the mplsTunnelUpNotRecip or mplsTunnelDownNotRecip fields in TE-MIB are set to 0.0.0.0.

The percentage increase in the rapid retransmission interval for each consecutive unacknowledged RSVP Notify message. A value of 0 indicates a constant retransmission rate.

The interval in milliseconds before a Notify message is first resent if no acknowledgement is received.

The maximum number of times a Notify message is resent if no acknowledgement is received.

A flag to indicate that PRVT-RSVP should support the use of IP encapsulation of RSVP packets, which are required for out-of-band signaling. If set, then PRVT-RSVP will accept incoming RSVP packets that are IP encapsulated, and will IP encapsulate outgoing packets whenever the IP routing stub indicates that it is required for a particular route.

Specifies which extensions to the standard RSVP-TE protocol are enabled. For fully standards-compliant behavior, set this parameter to zero (no bits set). To enable specific non-standard protocol extensions, set this parameter to the bitwise OR of whichever of the following behaviors you wish to enable. - bypassFastReroute: Enable support for facility fast reroute protection of LSPs (bypass LSP protection). This flag is deprecated in favour of the prvtRsvpProductFrrFacAdminStatus field which can be modified while RSVP is admin up, however either field can be used. When this flag is set RSVP automatically sets the prvtRsvpProductFrrFacAdminStatus. - detourFastReroute: Enable support for one-to-one fast reroute protection of LSPs (detour LSP protection). - noResAffOnInIf: Disable resource affinity checking on incoming interfaces for LSPs. If this flag is set, RSVP will accept Path messages which use invalid resource affinities for the incoming interface used by the LSP. Bits: 'detourFastReroute': 1, 'bypassFastReroute': 0, 'noResAffOnInIf': 2.

This field is used by PRVT-RSVP to determine whether it should set the Path State Removed flag on a PathErr (and therefore remove corresponding state and generate a PathTear). Each bit of this flags field corresponds to a situation where PRVT-RSVP may generate a PathErr. Setting a particular bit will result in PRVT-RSVP removing state, setting the Path State Removed flag and generating a PathTear in that corresponding situation. The possible bit values are - pathErrPSRSet: PRVT-RSVP has received a PathErr message with the Path State Removed flag set. - pathErrPSRNotSet: PRVT-RSVP has received a PathErr message with the Path State Removed flag unset. - ldbCommonRcvd: PRVT-RSVP has received a negative response to an ATG_LDB_RESERVE_LSP_XC or ATG_LDB_CONNECT_LSP_XC message. - ldbPreempted: PRVT-RSVP has received a Preemption message from Label Manager. - routingError: PRVT-RSVP has received a Negative response to an ATG_IPR_QUERY_ROUTE message. - invalidPathMsg: PRVT-RSVP has received an invalid Path message. - sessionExpired: A session in PRVT-RSVP has expired. - unableToRepairRoute: A route has been removed and PRVT-RSVP is unable to start local repair. - unableToRepairIf: An interface has been removed and PRVT-RSVP is unable start local repair. - reachedRetryLimit: An initial Path Message has reached its retry limit. - unableToRefresh: PRVT-RSVP has been unable to refresh an LSP. - resvErrTurnaround: PRVT-RSVP has received a ResvErr at the Egress node containing a REROUTING object and this is to be turned round into a PathErr. - incomingIfDown: The incoming MPLS data interface for an LSP has been deactivated. - outgoingIfDown: The outgoing MPLS data interface for an LSP has been deactivated. Bits: 'ldbPreempted': 3, 'invalidPathMsg': 5, 'incomingIfDown': 12, 'unableToRepairIf': 8, 'outgoingIfDown': 13, 'resvErrTurnaround': 11, 'pathErrPSRNotSet': 1, 'sessionExpired': 6, 'unableToRefresh': 10, 'unableToRepairRoute': 7, 'reachedRetryLimit': 9, 'pathErrPSRSet': 0, 'routingError': 4, 'ldbCommonRcvd': 2.

The percentage increase in the rapid retransmission interval for each consecutive unacknowledged RSVP Initial Path message. A value of 0 indicates a constant retransmission rate. A Path message is treated as an initial Path if it is the Path message which creates the LSP or a Path refresh message which requires re-routing.

The rapid retransmission interval in milliseconds before an Initial Path message is first resent if no acknowledgement is received. A Path message is treated as an initial Path if it is the Path message which creates the LSP or a Path refresh message which requires re-routing.

The maximum number of times an Initial Path message is resent if no acknowledgement is received. A Path message is treated as an initial Path if it is the Path message which creates the LSP or a Path refresh message which requires re-routing.

A flag to indicate whether the local node supports UNI signaling messages.

A flag to indicate whether the local node should advertise itself as restart capable. This should be set to true if fault-tolerance is enabled in PRVT-MPLS or if the node supports recovery procedures.

The time in milliseconds that the local node takes to restart RSVP-TE and the communication channel used for RSVP communication. This is advertised to neighbors in the Restart_Cap object in Hello messages. The value chosen should be large enough for RSVP to be terminated and restarted. If fault-tolerance is enabled in PRVT-MPLS, then sufficient time should be allowed for RSVP to fail over, which should include the time taken for the audit phase to complete. A value of 0xFFFFFFFF may be configured to imply an infinite restart time. Only used if prvtRsvpProductRestartCapable is set to true. Note that the maximum real time value that can be set is 0x7FFFFFFF. If a value is requested greater than 0x7FFFFFFF and less than 0xFFFFFFFF the request will be rejected.

The period of time in milliseconds that the local node would like neighbors to take to resyncronize RSVP and MPLS forwarding information after the re-establishment of Hello connectivity. This is advertised to neighbors in the Restart_Cap object in Hello messages. A value of zero indicates that the node does not support resynchronization following failure of the local node. A value of 0xFFFFFFFF indicates an infinite recovery time. Note that if fault-tolerance is not enabled in PRVT-MPLS and the node is acting as an ingress for tunnels, then any ingress tunnels that need to be recovered should be configured during this recovery period. These tunnels should be configured in TE-MIB with the admin_status set to UP, otherwise they will be lost from the switch controller. Only used if prvtRsvpProductRestartCapable is set to true. Note that the maximum real time value that can be set is 0x7FFFFFFF. If a value is requested greater than 0x7FFFFFFF and less than 0xFFFFFFFF the request will be rejected.

The mininum period of time in milliseconds that RSVP should wait for a restart capable neighbor to regain Hello connectivity before invoking procedures related to communication loss. RSVP will wait for the maximum of this time and the restart_time advertised in the RESTART_CAP object in Hello messages from the neighbor.

The time in milliseconds that PRVT-MPLS will wait for graceful deletion to complete before the forced deletion procedure is used instead.

Specifies the action that an egress node should take in the graceful deletion procedure on receipt of a Path message containing an Admin Status object with the D and R bits set. The possible values are:- - delWithPathErr: Send a PathErr message with the Path_State_removed flag set. - delWithResvD: Send a Resv message containing an Admin Status object with the D bit set. Enumeration: 'delWithPathErr': 1, 'delWithResvD': 2.

A flag to indicate whether UNI-N nodes should allow the splicing of UNI connections with proprietary ON connections.

Specifies what fast reroute capabilities are enabled on this node. This field is only valid if the fast reroute extension is enabled in the prvtRsvpProductProtocolExtensions field above. - PLR: Node provides fast reroute point of local repair capability. - MP: Node provides fast reroute merge point capability. - DetourRestart: Node implements some protocol extensions to recover detour fast reroute LSPs after a node restart or an adjacent node restart. This flag is only valid if detourFastReroute flag is set in the prvtRsvpProductProtocolExtensions field above. Note that a node can still perform some FRR processing even if the PLR and MP flags are clear (at a detour transit for instance). Bits: 'fastReroutePLR': 0, 'fastRerouteDetourRestart': 2, 'fastRerouteMP': 1.

When this node is a PLR, this field specifies the period that the node should wait before retrying the setup of a backup LSP which failed last time because no route was available. In the case that a backup LSP is set up but an error is received from upstream, setup will be attempted again immediately. This field is only valid if this node is defined as PLR capable in the _prvtRsvpProductFastRerouteCapabilities_ field above.

This field is used by PRVT-RSVP to determine whether it should take any special action following certain types of local errors. Each bit of this flags field corresponds to an error and a corresponding action. When one of these errors occurs, the relevant bit flag is checked - if set, the specified action is taken; if not set, the normal action is taken according the RSVP protocol. The possible bit values are the following. - eafTearStateOnLSIErr: When PRVT-RSVP receives a negative response to an ATG_LDB_CONNECT_LSP_XC message on a UNI node, the Path state is torn down. Bits: 'eafTearStateOnLSIErr': 0.

A flag to indicate whether the local node supports NNI signaling messages. Enumeration: 'disabled': 1, 'enabled': 2, 'disabling': 3.

Specifies some detailed aspects of the behavior of PRVT-RSVP. This field may be changed while _admin_status_ is up. - enableTTLMatch: Whether to discard received RSVP packets sent with the Router Alert option if the IP and RSVP TTL values do not match. In certain circumstances TTL comparison can identify RSVP service breaks, and allow the discarding of packets that would otherwise disrupt installed LSPs. This option has no effect for Out Of Band operation. This option should be left disabled for LSP hierarchy operation (LSPs set up over existing LSPs) and for Facility Fast Reroute (which sets up backup LSPs over existing bypass LSPs). Bits: 'enableTTLMatch': 0.

Specifies the style of LABEL_SET object that should be used. RFCs 3741 and 3743 are unclear whether the LABEL_SET object should include LABEL headers. The correct interpretation is that the header should not be present, but there are implementations that include the LABEL header, so this option is included for compatibility with these implementations. - excludeLabelHeader: The LABEL_SET object contains concatenated LABEL values without the object headers. - includeLabelHeader: The LABEL_SET object contains concatenated LABEL objects with the object headers. Enumeration: 'includeLabelHeader': 2, 'excludeLabelHeader': 1.

The current operational state of Label Set style. - excludeLabelHeader: The LABEL_SET object contains concatenated LABEL values without the object headers. - includeLabelHeader: The LABEL_SET object contains concatenated LABEL objects with the object headers. - goingToExclude: The Label Set Style is being changed from includeLabelHeader to excludeLabelHeader. - goingToInclude: The Label Set Style is being changed from excludeLabelHeader to includeLabelHeader. Enumeration: 'goingToInclude': 4, 'includeLabelHeader': 2, 'excludeLabelHeader': 1, 'goingToExclude': 3.

This object is used to enable traps for the Label Set style oper_status object.

Specifies the action to take when the value of prvtRsvpProductLabelSetStyle is changed. - leaveLSPs: All nodes should suppress refreshes and switch to the new format while refreshes are suppressed. - tearLSPs: Any LSPs using label sets will be deleted before switching all nodes to the new format, and any new LSPs using label sets will be dropped/rejected until the switch is complete.

The desired operational state of support for the extended PROTECTION object defined in draft-lang-ccamp-gmpls-recovery-e2e-signaling.

Specifies whether Sonet Profile is included on messages to or from a UNI-C node.

Specifies whether backup LSPs can be put in place for LSPs requesting FRR using the facility method. Setting this to UP means that LSPs that request FRR using the facility method can have protection at this node. Existing LSPs that request FRR facility protection will have protection put in place when the next Path refresh is received. Setting this to DOWN means that LSPs that request FRR using the facility method will not be protected at this node. Existing LSPs that have FRR facility protection will lose that protection, and if the LSP had been rerouted to use the backup LSP then the protected LSP will be lost. This field replaces the bypassFastReroute flag on the protocol extensions field in this MIB (although the bypassFastReroute flag is still supported for backwards compatibility). It can be modified while RSVP is oper_status UP or DOWN. When this field is changed the bypassFastReroute flag is automatically modified to mirror the change.

The current operational status for FRR Facility support. When this is UP backup LSPs will be put in place, when this is down backup LSPs will not be put in place and there will be no LSPs that have backup LSPs.

Specifies whether the local node supports IPv6 LSPs. Setting this to UP means that this node supports IPv6 LSPs being set up to, from and through this node. Setting this to DOWN means that IPv6 LSPs are NOT supported by this node. Existing IPv6 LSPs for which this node is the ingress, egress or transit are torn down. This field can be modified while RSVP is oper_status UP or DOWN. The value of this field MUST match the value of the dcMplsTeMibRsvpIpv6AdminStatus field in the prvtMplsTeMibEntityTable.

The current operational status for IPv6 support. When this is UP IPv6 LSPs can be set up to from or through this node. When this is down there will be no active IPv6 LSPs.

Management assigned IPv6 address used to identify the (internal) LRAPI interface between RSVP and TE-MIB components. The configured API IPv6 address MUST not be a real address in the network. It is recommended that this is set to a non-zero reserved address value. This MUST be an address with global scope. If multi-stack support is set to PHOP, this address must be unique for each RSVP stack in the node. The same address(es) can be used on all nodes in the network.

The table of sessions that are being diagnosed.

Each entry represents a session that is being diagnosed.

The index of the PRVT-RSVP product that is handling this query.

The index of this prvtRsvpDiagnosticEntry. This corresponds to a particular session being diagnosed and is an arbitrary value, defined on row creation.

The number of outstanding diagnostic requests relating to this session.

The IP address of the tunnel end point, from the LSP_TUNNEL_IPv4 session object.

The tunnel ID, from the LSP_TUNNEL_IPv4 session object.

The extended tunnel ID, from the LSP_TUNNEL_IPv4 session object.

The IP address of the last hop to be queried. This is the address to which the DREQ message is first sent.

The IP address of the sender for the specified session.

The maximum number of hops to diagnose.

A flag to indicate that DREPs should be returned hop-by- hop using the reverse of the path taken by the DREQ.

The table of nodes within a session that is being diagnosed. External management can extract information from this table, but cannot modify information in it.

Each entry represents a node within a session that is being diagnosed.

The index of the PRVT-RSVP product that is handling this query.

The index of the corresponding request in prvtRsvpDiagnosticTable.

The index of this prvtRsvpDiagNodeEntry. This is equivalent to the hop number, with 1 being the ingress.

The type of the node: ingress, transit, egress or missing. Missing indicates that no diagnostic response has been received for this node, and this entry may in fact represent more than one node.

The arrival time of the DREQ at the node, specified as a 32-bit NTP timestamp.

The IP address of the interface on which message from the sender are expected to arrive at this node, or 0 if unknown.

The IP address of the interface through which the DREQ arrived and to which messages flow from the given sender for the specified session address, or 0 if unknown.

The IP address from which this node receives RSVP PATH messages for this source, or 0 if unknown. This is also the address to which the DREQ was forwarded.

The number of IP hops traversed by the DREQ between the downstream RSVP node and this node.

A flag that indicates whether the reservation described by the response objects is merged with reservations from other downstream interfaces before being forwarded upstream.

The error conditions at this node. Bit 3 indicates ROUTE object too big; Bit 2 indicates packet too big; Bit 1 indicates no PATH state. Bit 1 is the least significant bit.

The refresh timer multiple.

The local refresh timer value in seconds.

The hop address from the session's RSVP_HOP object.

The LIH from the session's RSVP_HOP object.

The address from the session's SENDER_TEMPLATE object.

The LSP ID from the session's SENDER_TEMPLATE object.

Int-serv controlled load token bucket rate in bytes per second, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv controlled load token bucket depth in bytes, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv controlled load peak data rate in bytes per second, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv controlled load minimum policed unit from the session's FLOWSPEC object.

Int-serv controlled load maximum packet size from the session's FLOWSPEC object.

Int-serv guaranteed QoS token bucket rate in bytes per second, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv guaranteed QoS token bucket depth in bytes, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv guaranteed QoS peak data rate in bytes per second, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv guaranteed QoS minimum policed unit from the session's FLOWSPEC object.

Int-serv guaranteed QoS maximum packet size from the session's FLOWSPEC object.

Int-serv guaranteed QoS rate in bytes per second, from the session's FLOWSPEC object. This value is rounded to the nearest integer.

Int-serv guaranteed QoS slack in microseconds, from the session's FLOWSPEC object.

CoS class of service from the session's FLOWSPEC object.

CoS maximum packet size from the session's FLOWSPEC object.

The address from the session's FILTER_SPEC object.

The LSP ID from the session's FILTER_SPEC object.

The address from the session's CONFIRM object.

The style word from the session's STYLE object.

The compliance statement for the PRVT-RSVP product MIB.

Product Table Objects.

Diagnostic Table Objects.

Diag Node Table Objects.