Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring SNMP on JDM

There are several SNMP-enabled components in NFX (JDM, hypervisor, and so on). This topic discusses the SNMP implementation of JDM and hypervisor. For JCP, see the Junos documentation. On the NFX250 platform, JDM plays the role of the SNMP agent and at the same time it acts as an SNMP proxy for the hypervisor (host OS). When SNMP is configured in JDM, hypervisor also takes the same SNMP configuration. By default, SNMP is disabled on disaggregated Junos OS platforms. To enable SNMP , you must include the SNMP configuration statements at the [edit snmp] hierarchy level. This section describes:

Configuring SNMP Community

To configure SNMP community:

Specify a name for the SNMP community:

Configuring SNMP System Parameters

To configure SNMP system parameters:

  1. Set the system name:
  2. Enter a description for the system being managed:
  3. Specify the location of the system:
  4. Specify the name of the contact person:

Configuring SNMP v3

In contrast to SNMP version 1 (SNMPv1) and SNMP version 2 (SNMPv2), SNMP version 3 (SNMPv3) supports authentication and encryption. SNMPv3 uses the user-based security model (USM) for message security and the view-based access control model (VACM) for access control. USM specifies authentication and encryption. VACM specifies access-control rules. To configure local engine information for the user-based security model (USM) with Secure Hash Algorithm (SHA) as the authentication type for the SNMPv3 user, enter the command:

To configure local engine information for the USM with MD5 as the authentication type for the SNMPv3 user, enter the command:

Configuring SNMP Traps

To configure SNMP traps, create a named group of hosts to receive the specified trap notifications. At least one trap group must be configured for SNMP traps to be sent:

Querying SNMP MIBs

The NFX 250 platform supports querying SNMP MIBs on both, the JDM and the hypervisor. NFX MIBS are read-only, which means that the values can be read from the MIB but cannot be configured using SNMP.

The commands below are the queries on SNMP v1, SNMP v2 and SNMP v3. :

To query the hypervisor, you need to provide an additional context name, which is the user name appended by -host:

You can query libvirt MIBs only as a host:

Managing Traps

The agent sends traps to notify the manager of significant events that occur on the device. To configure traps:

JDM traps are assigned the context jdm, and hypervisor traps are assigned the context host.