Group-Based Snmp Access; Snmp And Embedded Event Manager; Multiple Instance Support; High Availability For Snmp - Cisco Nexus 7000 Series Configuration Manual

SNMP and Embedded Event Manager

Group-Based SNMP Access

Note Because group is a standard SNMP term used industry-wide, we refer to roles as groups in this SNMP
section.
SNMP access rights are organized by groups. Each group in SNMP is similar to a role through the CLI. Each
group is defined with read access or read-write access.
You can begin communicating with the agent once your username is created, your roles are set up by your
administrator, and you are added to the roles.
SNMP and Embedded Event Manager
The Embedded Event Manager (EEM) feature monitors events, including SNMP MIB objects, and triggers
an action based on these events. One of the actions could be to send an SNMP notification. EEM sends the
cEventMgrPolicyEvent of CISCO-EMBEDDED-EVENT-MGR-MIB as the SNMP notification.

Multiple Instance Support

A device can support multiple instances of a logical network entity, such as protocol instances or virtual
routing and forwarding (VRF) instances. Most existing MIBs cannot distinguish between these multiple logical
network entities. For example, the original OSPF-MIB assumes a single protocol instance on a device, but
you can now configure multiple OSPF instances on a device.
SNMPv3 uses contexts to distinguish between these multiple instances. An SNMP context is a collection of
management information that you can access through the SNMP agent. A device can support multiple contexts
for different logical network entities. An SNMP context allows the SNMP manager to access one of the
multiple instances of a MIB module supported on the device for the different logical network entities.
Cisco NX-OS supports the CISCO-CONTEXT-MAPPING-MIB to map between SNMP contexts and logical
network entities. You can associate an SNMP context to a VRF, protocol instance, or topology.
SNMPv3 supports contexts with the contextName field of the SNMPv3 PDU. You can map this contextName
field to a particular protocol instance or VRF.
For SNMPv2c, you can map the SNMP community to a context using the snmpCommunityContextName
MIB object in the SNMP-COMMUNITY-MIB (RFC 3584). You can then map this
snmpCommunityContextName to a particular protocol instance or VRF using the
CISCO-CONTEXT-MAPPING-MIB or the CLI.

High Availability for SNMP

Cisco NX-OS supports stateless restarts for SNMP. After a reboot or supervisor switchover, Cisco NX-OS
applies the running configuration.
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
180
Configuring SNMP