Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    SNMP and the JunosV App Engine MIB

    As of Junos OS Release 13.2R2, SNMP-based management and monitoring of the JunosV App Engine infrastructure is introduced using a new Juniper Networks proprietary MIB. This MIB is a collection of tables that gives users access to information such as an inventory of compute nodes and application instances, resource usage, and hardware.

    System and network administrators are the intended users of this feature.

    The new MIB is split into two parts: jnx-jvae-infra-mib and jnx-jvae-node-mib. jnx-jvae-infra-mib is implemented on the router and contains information about various nodes and virtual machines (VMs). jnx-jvae-node-mib is implemented on the compute nodes as a subagent of the Junos SNMP daemon (smnpd) on the router.

    The subagent is added to vehostd on the compute node and registers with snmpd on the router to service SNMP queries for the MIB and generate traps for monitored events. The router responds to the queries with information on compute nodes and VMs that are passed on to the configured trap receiver. To receive and act on this information, at least one SNMP trap receiver must be configured.

    CLI configuration statements are provided to specify thresholds for low storage (disk) space, high processing load, and low free memory conditions on the compute node. SNMP traps are raised when the values exceed or fall below these thresholds. These threshold statements are at the following CLI hierarchy levels:

    • [edit services app-engine]
    • [edit services app-engine compute-cluster compute-cluster-name]
    • [edit services app-engine compute-cluster compute-cluster-name compute-node compute-node-name]

    Threshold configuration statements at the [edit services app-engine compute-cluster compute-cluster-name compute-node compute-node-name] hierarchy level override those at the [edit services app-engine compute-cluster compute-cluster-name] and [edit services app-engine] hierarchy levels, and statements at the [edit services app-engine compute-cluster compute-cluster-name] hierarchy level override those at the [edit services app-engine] hierarchy level.

    Published: 2014-04-04