Creating snmp notification logs, Figure 265 s – Brocade Communications Systems Brocate Ethernet Access Switch 6910 User Manual
Page 998
948
Brocade 6910 Ethernet Access Switch Configuration Guide
53-1002581-01
Simple Network Management Protocol
42
FIGURE 265
Showing Trap Managers
Creating SNMP Notification Logs
Use the Administration > SNMP (Configure Notify Filter - Add) page to create an SNMP notification
log.
CLI References
•
•
•
•
Command Usage
•
Systems that support SNMP often need a mechanism for recording Notification information as
a hedge against lost notifications, whether there are Traps or Informs that may be exceeding
retransmission limits. The Notification Log MIB (NLM, RFC 3014) provides an infrastructure in
which information from other MIBs may be logged.
•
Given the service provided by the NLM, individual MIBs can now bear less responsibility to
record transient information associated with an event against the possibility that the
Notification message is lost, and applications can poll the log to verify that they have not
missed any important Notifications.
•
If notification logging is not configured, when the switch reboots, some SNMP traps (such as
warm start) cannot be logged.
•
To avoid this problem, notification logging should be configured as described in this section,
and these commands stored in the startup configuration file using the System > File (Copy –
Running-Config) page as described on
. Then when the switch reboots, SNMP traps
(such as warm start) can now be logged.
•
Based on the default settings used in RFC 3014, a notification log can contain up to 256
entries, and the entry aging time is 1440 minutes. Information recorded in a notification log,
and the entry aging time can only be configured using SNMP from a network management
station.
•
When a trap host is created using the Administration > SNMP (Configure Trap – Add) page
described on
, a default notify filter will be created.