
Customizing SNMP
308644-15.1 Rev 00
3-25
•
delete
disassociates a view from a community or deletes the community,
depending on whether you specify
view_name
.
For example, to disassociate the view named “block” from the community
“pubnet,” enter:
snmpserver community pubnet view block delete
To delete the community named “pubnet,” and thereby the view association with
“pubnet,” enter:
snmpserver community pubnet delete
Configuring Traps on the Router
A trap is an event that the router sends to some external network device, such as a
network management station. You can specify which log events the SNMP agent
sends to the network management station as traps, based on the following:
• Slot number: the number of the slot on which the trap will be received
• Entity number: the code assigned to the entity issuing the event that uniquely
identifies a router event
• Severity level: indicates whether the trap is a fault, warning, information,
trace, or debug message
A router never broadcasts traps on the network. Rather, it sends traps to specific IP
addresses, which you configure on the router as managers of a community. Traps
are always sent to specific managers. For more information about traps, see
“
Events and Traps” on page 2-5.
Using the BCC
To specify a trap entity based on slot and protocol entity, enter the following
command at the SNMP prompt:
trap-entity entity <entity_name> slot <slot_number>
entity_name
is the name of the entity issuing the event. For a list of all entities,
enter
help trap-entity entity
at the SNMP prompt.
slot_number
is the number of the slot on which the trap will be received.
Commentaires sur ces manuels