Home/Catalog/JUNIPER-JVAE-INFRA-MIB

JUNIPER-JVAE-INFRA-MIB

Updated Aug 1, 2012
AI MIB Summary

The JUNIPER-JVAE-INFRA-MIB provides SNMP access to monitor the operational status, resource utilization, and health metrics of the JunosV App Engine virtual infrastructure components. This module enables the tracking of virtual appliance states, container performance counters, and underlying hypervisor resource allocation within Juniper's virtualized network environment.

The MIB module for JunosV App Engine Infrastructure.
Main OID:
jnxJVAEInfraMIB.1.3.6.1.4.1.2636.3.69.1
28
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

28 total
Object Name
jnxJVAEInfraMIBThe MIB module for JunosV App Engine Infrastructure.
MODULE-IDENTITY
.1.3.6.1.4.1.2636.3.69.1
jnxJVAEInfraNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.2636.3.69.1.0
jnxJVAECNStateChangeThis notification is generated whenever compute node state changes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2636.3.69.1.0.1
jnxJVAEVMStateChangeThis notification whenever the virutal machine status changes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2636.3.69.1.0.2
jnxJVAEInfraObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.2636.3.69.1.1
jnxJVAEInfraTables
OBJECT IDENTIFIER
.1.3.6.1.4.1.2636.3.69.1.1.1
jnxJVAECNTableA table of Compute Nodes.
SEQUENCE OF JnxJVAECNEntry
.1.3.6.1.4.1.2636.3.69.1.1.1.1
jnxJVAECNEntryA Compute Node.
JnxJVAECNEntry
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1
jnxJVAECNIdId of the Compute Node.
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.1
jnxJVAECNNameName of the Compute Node.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.2
jnxJVAECCNameName of the Compute Cluster, to which this Compute Node belongs.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.3
jnxJVAECNStateState of Compute Node as seen by the VE platform Manager.ro
Enumeration
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.4
jnxJVAECNLastStateChangeThe date and time when last state change was observed for this Compute Node.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.5
jnxJVAECNRouterIPv4Network address on the router side, which used for all management between the router and Compute Node.ro
InetAddressIPv4 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.6
jnxJVAECNRouterIPv6Network address on the router side, which used for all management between the router and Compute Node.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.7
jnxJVAECNMgmtIPv4Network address on the compute node side, which used for all management between the router and Compute Node.ro
InetAddressIPv4 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.8
jnxJVAECNMgmtIPv6Network address on the compute node side, which used for all management between the router and Compute Node.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.9
jnxJVAECNSWVersionCompute Node software version.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.1.1.10
jnxJVAEVMTableA table of virutal machine instances.
SEQUENCE OF JnxJVAEVMEntry
.1.3.6.1.4.1.2636.3.69.1.1.1.2
jnxJVAEVMEntryA virutal machine instance.
JnxJVAEVMEntry
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1
jnxJVAEVMIdAn unique identifier for this virtual machine instance. This identifier is not retained across restart of the subsytem.
OCTET STRING
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.1
jnxJVAEVMNameName of the virtual machine instance.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.2
jnxJVAEVMCCNameName of the compute cluster which the compute node belongs.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.3
jnxJVAEVMCNNameName of the compute node on which the virtual machine runs.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.4
jnxJVAEVMCNIdId of the compute node on which the virtual machine runs.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.5
jnxJVAEVMUuidUUID of the virtual machine.ro
OCTET STRING
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.6
jnxJVAEVMPkgName of package installed on the router holding the imgage for this virtual machine.ro
DisplayString
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.7
jnxJVAEVMStatusStatus of the virtual machine instance.ro
Enumeration
.1.3.6.1.4.1.2636.3.69.1.1.1.2.1.8

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→