VRF support for SNMP
VRF support for SNMP, the related configuration and commands.
The vRouter supports the implementation of SNMP on a routing instance, which allows the following associations and configurations:
- An SNMP client to be associated with a specific routing instance and handle context-based access to MIBs.
- An SNMP trap target to be associated with a routing instance for sending SNMP notifications that are specific to the routing instance.
- An SNMP agent to be configured to listen for incoming requests from a specific routing instance.
The SNMP V2 clients are associated with a routing instance by mapping the SNMP community strings with a routing instance, as shown in the following command:
set service snmp community <comm-string> [context <routing-instance>]
When a V2 request with a community string that is mapped to a routing instance is received, an SNMP agent retrieves MIB information that is specific to the routing instance.
The SNMP V3 clients are associated with a routing instance by specifying the routing instance as context in their requests. An SNMP agent returns context-based MIB information for these requests.
The SNMP V2 and V3 trap targets can be configured to receive routing instance-specific SNMP notifications. Traps to these targets are sent out on the configured routing instance, as shown in the following sample:
set service snmp trap-target <ip-addr> [routing-instance <name>]
set service snmp v3 trap-target <ip-addr> [routing-instance <name>]
When no routing instance is configured for a trap target, traps are sent over a default routing instance.
An SNMP agent can be configured to accept client requests from a specific routing instance:
set service snmp [routing-instance <name>]
When no routing instance is configured, an SNMP agent listens for client requests on a default routing instance.