- play_arrow Overview
- play_arrow Installation and Configuration
- Performing Initial Software Configuration on an NFX250 Device
- Installing Software on NFX250 Devices
- Configuring JDM User Accounts and Authentication
- YANG files on NFX250 Devices
- Synchronizing Time Using NTP
- Configuring Management Interfaces for JDM
- Configuring Remote Access to JDM
- Configuring Enhanced Orchestration and Hugepages
- Managing Virtual Network Functions Using JDM
- Configuring Service Chaining Using JDM
- ADSL2 and ADSL2+ Interfaces on NFX250 Devices
- VDSL2 Interfaces on NFX250 Devices
- play_arrow Configuring High Availability
- play_arrow Configuration Statements and Operational Commands
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:
user@jdm# set snmp community community
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:
user@jdm# set snmp v3 usm local-engine user username authentication-sha authentication-password authentication-password
To configure local engine information for the USM with MD5 as the authentication type for the SNMPv3 user, enter the command:
user@jdm# set snmp v3 usm local-engine user username authentication-md5 authentication-password authentication-password
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:
user@jdm# set snmp trap-group group-name targets address
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. :
user@SNMP_server# snmpwalk -v 1 -c community-name jdm_ip-address oid
user@jdm# snmpwalk -v 2 -c community-name ip-address oid
user@jdm# snmpwalk -v3 -u username -l authNoPriv -a SHA -A password ip-address oid
To query the hypervisor, you need to provide an additional context
name, which is the user name appended by -host:
user@jdm# snmpwalk -v 1 -c community-name-host ip-address oid
user@jdm# snmpwalk -v 2 -c community-name-host ip-address oid
user@jdm# snmpwalk -v3 -u username-host -l authNoPriv -a SHA -A password ip-address oid
You can query libvirt MIBs only as a host:
user@jdm# snmpwalk -v 2c -c community-name-host ip-address oid
Managing Traps
The agent sends traps to notify the manager of significant events that occur on the device. To configure traps:
user@jdm# set snmp trap-group group-name targets ip-address
JDM traps are assigned the context jdm, and hypervisor traps are assigned the context host.
