Description

How to poll SNMP over routing instance

Symptoms

This article provides the needed steps to do SNMP polling inside a routing instance on EX system.

If it is not configured correctly, SNMP polling will fail with similar error messages as below:


Jun 11 23:25:54 snmpd[817]: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 192.168.100.2 not allowed
Jun 11 23:25:54 snmpd[817]: SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP community from 192.168.100.2 to unknown community name (public)
Jun 11 23:25:56 snmpd[817]: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 192.168.100.2 not allowed
Jun 11 23:25:56 snmpd[817]: SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP community from 192.168.100.2 to unknown community name (public)

Solution

To be able to perform SNMP polling inside a routing instance on the EX platform, refer to the minimal example configuration below :

{master:0}[edit]
root# show routing-instances
VRF1 {
instance-type virtual-router;
interface vlan.100;
}

{master:0}[edit]
root# show snmp
community public {
routing-instance VRF1;
}
routing-instance-access;
In the SNMP configuration, the routing-instance name under the community stanza and routing-instance-access are required.

In order to access MIB objects and perform SNMP operations for the routing-instances, SNMP v1 and v2c clients need to encode the routing-instance name in the community string in their SNMP requests.
The format is:
routing-instance name@community string
As per the above example, the community string for SNMP v1 an v2c requests should use the following:
VRF1@public

Related Information