Cisco AP775A - Nexus Converged Network Switch 5010 Manuale di riferimento rapido - Pagina 3
Sfoglia online o scarica il pdf Manuale di riferimento rapido per Interruttore Cisco AP775A - Nexus Converged Network Switch 5010. Cisco AP775A - Nexus Converged Network Switch 5010 14. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Anche per Cisco AP775A - Nexus Converged Network Switch 5010: Nota di rilascio (48 pagine), Nota di rilascio (44 pagine), Nota di rilascio (26 pagine), Nota di rilascio (26 pagine)
Stampa la pagina
S e n d d o c u m e n t a t i o n c o m m e n t s t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
Table 1
Operation
trap
inform
1. With this operation, an SNMP manager does not need to know the exact variable name. A sequential search finds the next
2. The get-bulk and inform commands are not a part of SNMPv1.
3. The get-bulk and inform commands are not a part of SNMPv1.
SNMPv1 was the initial version of the protocol. SNMPv2 added support for 64-bit counters, and
SNMPv3 added increased security for access, authentication, and encryption of managed data.
SNMP Traps and Informs
You can configure Cisco Nexus 5000 Series switches to send notifications to SNMP managers when
particular events occur. You can send these notifications as traps or inform requests. Traps are unreliable
because the receiver does not send any acknowledgment when it receives a trap. The sender cannot
determine if the trap was received. However, an SNMP manager that receives an inform request
acknowledges the message with an SNMP response. If the sender never receives a response, the inform
request can be sent again. Informs are more likely to reach their intended destinations than traps.
Notifications may contain a list of MIB variables (varbinds) that clarify the status that is relayed by the
notification. The list of varbinds associated with a notification is included in the notification definition
in the MIB. In the case of standard MIBs, Cisco has enhanced some notifications with additional
varbinds that further clarify the cause of the notification. See the
page 9
Use the SNMP-TARGET-MIB to obtain more information on trap destinations and inform requests. See
the Cisco Nexus 5000 CLI Configuration Guide for more information on configuring traps and informs.
You must enable most notifications through the CLI. For more information, see the Cisco Nexus 5000
Note
Series CLI Configuration Guide, Release 4.0.
Interpreting the MIB Structure
A MIB presents the managed data in a logical tree hierarchy, using an IETF standard syntax called the
Structure of Management Information (SMI). Branches of this MIB tree are organized into individual
tables, which contain the managed data as leaf objects.
This section includes the following topics:
•
•
•
•
OL-16784-01
SNMP Operations (continued)
Description
Sends an unsolicited message by an SNMP agent to an SNMP manager indicating
that some event has occurred.
2
Sends an unsolicited message by an SNMP agent to an SNMP manager indicating
that some event has occurred. An inform differs from a trap in that an
acknowledgement is required from the manager.
variable from within the MIB.
for an example of these extensions in the IF-MIB.
Object Identifiers, page 4
Tables, page 4
SYNTAX Clause, page 5
MAX-ACCESS Clause, page 5
MIBs and Network Management
"Extending the IF-MIB" section on
Cisco Nexus 5000 Series MIB Quick Reference
3