Defines the jnxRsvpSession Table for RSVP Sessions.
jnxRsvpSessionName
1.3.6.1.4.1.2636.3.30.1.1.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 (0..64) · OCTET STRING · hint 255a
Name of the RSVP Session. This is the same as LSP name.
If the head-end router signals the type of path corresponding to an RSVP session; viz. primary or secondary path, then this information can be used on other routers as well to associate RSVP session information to an MPLS path of an LSP (tunnel).
This value signifies the role of an RSVP session with respect to the start and end points of the session. This value MUST be set to ingress(1) at the head-end (source) of this session. This value MUST be set to egress(3) at the tail-end (destination) of the RSVP session. This value MUST be set to transit(2) on any other intermediate nodes that this RSVP session exists on.
jnxRsvpSessionDiscontinuityTime
1.3.6.1.4.1.2636.3.30.1.1.1.10
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 value of sysUpTime on the most recent occasion at which any one or more of this RSVP Session's counters suffered a discontinuity. The relevant counters are jnxRsvpSessionMplsOctets and jnxRsvpSessionMplsPackets. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then then this object contains a zero value.
jnxRsvpSessionMplsOctets
1.3.6.1.4.1.2636.3.30.1.1.1.11
Counter64 (0..18446744073709551615)
The number of MPLS octets that have been forwarded over this RSVP Session. 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. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of jnxRsvpSessionDiscontinuityTime.
jnxRsvpSessionMplsPackets
1.3.6.1.4.1.2636.3.30.1.1.1.12
Counter64 (0..18446744073709551615)
The number of MPLS packets that have been forwarded over this RSVP Session. 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. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of jnxRsvpSessionDiscontinuityTime.