JUNIPER-JVAE-INFRA-MIB

All MIBs › JUNIPER-JVAE-INFRA-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2012-08-01

Category: Vendor: Juniper

Description: Defines managed objects for Juniper Virtual Application Engine (JVAE) infrastructure monitoring, supporting virtual machine resource tracking.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is JUNIPER-JVAE-INFRA-MIB?

JUNIPER-JVAE-INFRA-MIB defines managed objects for Juniper Networks' JunosV App Engine (JVAE) infrastructure, a virtualized application-engine environment hosted on Juniper routing platforms. It exposes a compute-node table (jnxJVAECNTable) describing each virtual compute node/container, including its name, associated compute cluster (jnxJVAECCName), current operational state, last state-change time, management and router IPv4/IPv6 addresses, and software version (jnxJVAECNSWVersion). Its monitoring focus is on software/virtualization status: tracking whether a compute node is up, down, or transitioning (jnxJVAECNState/jnxJVAECNLastStateChange), verifying reachability via its management and router IP addresses, and confirming the running software version for consistency across the virtualized fleet. It is a Juniper enterprise MIB that depends on Junos platform conventions and complements standard Juniper chassis/virtual-machine MIBs for physical host correlation. It is deployed on Juniper MX-series and similar routers running JunosV App Engine to host virtualized network functions or applications, where JUNIPER-JVAE-INFRA-MIB SNMP monitoring tracks compute-node state and software version across the fleet.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-JVAE-INFRA-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Juniper MX-series routers running JunosV App Engine
Juniper virtualized application-engine platforms

Monitoring Examples

An operator would poll jnxJVAECNState across jnxJVAECNTable (keyed by jnxJVAECNId) to spot a compute node that has dropped out of its expected running state, then check jnxJVAECNLastStateChange to see how recently it flapped. jnxJVAECNMgmtIPv4/jnxJVAECNRouterIPv4 let the NMS verify network reachability to a specific virtual engine, and jnxJVAECNSWVersion is polled fleet-wide to catch nodes still running an outdated image after a rollout.

What Can Be Monitored

compute node operational state
last state-change time
management/router IP reachability
software version per compute node
compute cluster association

Imported Objects

From INET-ADDRESS-MIB

InetAddressIPv4
InetAddressIPv6

From JUNIPER-SMI

jnxJVAEMibRoot

OBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using jnxJVAECNState OID:

Select a Juniper MX-series router running JunosV App Engine as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxJVAECNState into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the state of Compute Node as seen by the VE platform Manager. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'online', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxJVAEInfraMIB	1.3.6.1.4.1.2636.3.69.1			The MIB module for JunosV App Engine Infrastructure.
jnxJVAEInfraNotifications	1.3.6.1.4.1.2636.3.69.1.0
NTF jnxJVAECNStateChange	1.3.6.1.4.1.2636.3.69.1.0.1			This notification is generated whenever compute node state changes.
NTF jnxJVAEVMStateChange	1.3.6.1.4.1.2636.3.69.1.0.2			This notification whenever the virutal machine status changes.
jnxJVAEInfraObjects	1.3.6.1.4.1.2636.3.69.1.1
jnxJVAEInfraTables	1.3.6.1.4.1.2636.3.69.1.1.1
jnxJVAECNTable	1.3.6.1.4.1.2636.3.69.1.1.1.1		not-accessible	A table of Compute Nodes.
jnxJVAECNEntry	1.3.6.1.4.1.2636.3.69.1.1.1.1.1		not-accessible	A Compute Node.
STR jnxJVAECNId	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.1	DisplayString	not-accessible	Id of the Compute Node.
STR jnxJVAECNName	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.2	DisplayString	read-only	Name of the Compute Node.
STR jnxJVAECCName	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.3	DisplayString	read-only	Name of the Compute Cluster, to which this Compute Node belongs.
INT jnxJVAECNStateEx	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.4	INTEGER	read-only	State of Compute Node as seen by the VE platform Manager.
STR jnxJVAECNLastStateChange	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.5	DisplayString	read-only	The date and time when last state change was observed for this Compute Node.
ADR jnxJVAECNRouterIPv4	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.6	InetAddressIPv4	read-only	Network address on the router side, which used for all management between the router and Compute Node.
ADR jnxJVAECNRouterIPv6	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.7	InetAddressIPv6	read-only	Network address on the router side, which used for all management between the router and Compute Node.
ADR jnxJVAECNMgmtIPv4	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.8	InetAddressIPv4	read-only	Network address on the compute node side, which used for all management between the router and Compute Node.
ADR jnxJVAECNMgmtIPv6	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.9	InetAddressIPv6	read-only	Network address on the compute node side, which used for all management between the router and Compute Node.
STR jnxJVAECNSWVersion	1.3.6.1.4.1.2636.3.69.1.1.1.1.1.10	DisplayString	read-only	Compute Node software version.
jnxJVAEVMTable	1.3.6.1.4.1.2636.3.69.1.1.1.2		not-accessible	A table of virutal machine instances.
jnxJVAEVMEntry	1.3.6.1.4.1.2636.3.69.1.1.1.2.1		not-accessible	A virutal machine instance.
OCT jnxJVAEVMId	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.1	OCTET STRING	not-accessible	An unique identifier for this virtual machine instance. This identifier is not retained across restart of the subsytem.
STR jnxJVAEVMName	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.2	DisplayString	read-only	Name of the virtual machine instance.
STR jnxJVAEVMCCName	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.3	DisplayString	read-only	Name of the compute cluster which the compute node belongs.
STR jnxJVAEVMCNName	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.4	DisplayString	read-only	Name of the compute node on which the virtual machine runs.
STR jnxJVAEVMCNId	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.5	DisplayString	read-only	Id of the compute node on which the virtual machine runs.
OCT jnxJVAEVMUuid	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.6	OCTET STRING	read-only	UUID of the virtual machine.
STR jnxJVAEVMPkg	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.7	DisplayString	read-only	Name of package installed on the router holding the imgage for this virtual machine.
INT jnxJVAEVMStatus	1.3.6.1.4.1.2636.3.69.1.1.1.2.1.8	INTEGER	read-only	Status of the virtual machine instance.

RFC description

Juniper JunosV App Engine infrastructure including compute nodes and virtual resource management.

Start monitoring Juniper MX-series router running JunosV App Engine with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download JUNIPER-JVAE-INFRA-MIB