Home/Catalog/JUNIPER-RSVP-MIB

JUNIPER-RSVP-MIB

Updated Feb 3, 2004
The MIB modules for Resource ReSerVation Protocol.
Main OID:
jnxRsvpMIB.1.3.6.1.4.1.2636.3.30
16
Objects
Active
Status
3
Dependencies

Imported Objects

Objects

16 total
Object Name
jnxRsvpMIBThe MIB modules for Resource ReSerVation Protocol.
MODULE-IDENTITY
.1.3.6.1.4.1.2636.3.30
jnxRsvpOperation
OBJECT IDENTIFIER
.1.3.6.1.4.1.2636.3.30.1
jnxRsvpSessionTableDefines the jnxRsvpSession Table for RSVP Sessions.
SEQUENCE OF JnxRsvpSessionEntry
.1.3.6.1.4.1.2636.3.30.1.1
jnxRsvpSessionEntryDefines an entry in the jnxRsvpSessionTable. The first index element jnxRsvpSessionName is similar to the LSP name in the MPLS MIB and can be used to co-relate the mplsLspEntry to an RSVP session entry. There could be multiple entries with the same jnxRsvpSessionName and hence the need for a secondary index which is just an Unsigned32 to identify each of them uniquely. A management application may walk through all entries with the same jnxRsvpSessionName and based on the other RSVP session information in each entry, such as jnxRsvpSessionFrom and/or jnxRsvpSessionTo may decide to query a particular RSVP session.
JnxRsvpSessionEntry
.1.3.6.1.4.1.2636.3.30.1.1.1
jnxRsvpSessionNameName of the RSVP Session. This is the same as LSP name.
DisplayString
.1.3.6.1.4.1.2636.3.30.1.1.1.1
jnxRsvpSessionIndexRSVP Session index.
Unsigned32
.1.3.6.1.4.1.2636.3.30.1.1.1.2
jnxRsvpSessionStateThe operational state of the RSVP Session.ro
Enumeration
.1.3.6.1.4.1.2636.3.30.1.1.1.3
jnxRsvpSessionFromSource IP address of this RSVP session.ro
IpAddress
.1.3.6.1.4.1.2636.3.30.1.1.1.4
jnxRsvpSessionToDestination IP address of this RSVP session.ro
IpAddress
.1.3.6.1.4.1.2636.3.30.1.1.1.5
jnxRsvpSessionLspIdLSP ID of the sender for this RSVP session.ro
Unsigned32
.1.3.6.1.4.1.2636.3.30.1.1.1.6
jnxRsvpSessionTunnelIdTunnel ID for the RSVP session.ro
Unsigned32
.1.3.6.1.4.1.2636.3.30.1.1.1.7
jnxRsvpSessionPathTypeIf 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).ro
Enumeration
.1.3.6.1.4.1.2636.3.30.1.1.1.8
jnxRsvpSessionRoleThis 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.ro
Enumeration
.1.3.6.1.4.1.2636.3.30.1.1.1.9
jnxRsvpSessionDiscontinuityTimeThe 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.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.2636.3.30.1.1.1.10
jnxRsvpSessionMplsOctetsThe 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.ro
Counter64
.1.3.6.1.4.1.2636.3.30.1.1.1.11
jnxRsvpSessionMplsPacketsThe 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.ro
Counter64
.1.3.6.1.4.1.2636.3.30.1.1.1.12

More MIBs from Juniper Networks

Browse all Juniper NetworksMIBs →
JUNIPER-CHASSIS-DEFINES-MIB

The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.

5187 objects→
JUNIPER-MOBILE-GATEWAY-GTP-MIB

The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.

1616 objects→
GGSN-MIB

SNMP MIB module

789 objects→
JUNIPER-IFOPTICS-MIB

SNMP MIB module

754 objects→
JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB

The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.

683 objects→
JUNIPER-IPSEC-FLOW-MON-MIB

The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.

453 objects→