Chapter 13
| Basic Administration Protocols
Simple Network Management Protocol
– 408 –
â—† 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 page 73.
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 page 403, a default notify filter will be created.
Parameters
These parameters are displayed:
◆ IP Address – The IPv4 or IPv6 address of a remote device. The specified target
host must already have been configured using the Administration > SNMP
(Configure Trap – Add) page.
The notification log is stored locally. It is not sent to a remote device. This
remote host parameter is only required to complete mandatory fields in the
SNMP Notification MIB.
◆ Filter Profile Name – Notification log profile name. (Range: 1-32 characters)
Web Interface
To create an SNMP notification log:
1. Click Administration, SNMP.
2. Select Configure Notify Filter from the Step list.
3. Select Add from the Action list.
4. Fill in the IP address of a configured trap manager and the filter profile name.
5. Click Apply