Alaxala AX2500S, Руководство по устранению неисправностей

Страница: 101 / 136

3 Troubleshooting Functional Failures During Operation
75
3.10.2 Traps cannot be received by the SNMP manager
Make sure the configuration has been registered correctly.
When using SNMPv1 or SNMPv2C
Execute the show running-config operation command, and check whether the
information about the SNMP manager and traps has been registered in the
configuration for the Switch.
If the information has not been registered, execute the snmp-server host
configuration command to set the information about the SNMP manager and traps.
# show running-config
...
...
snmp-server host 20.1.1.1 traps "event-monitor" snmp
#
When using SNMPv3
Execute the show running-config configuration command, and check whether the
information about SNMP and traps has been set correctly in the configuration of the
Switch. If the information has not been set correctly, execute the following
configuration commands to set the information about SNMP and traps:

snmp-server engineID local

snmp-server view

snmp-server user

snmp-server group

snmp-server host
# show running-config
...
...
snmp-server engineID local "engine-ID"
snmp-server group "v3group" v3 priv notify "view1"
snmp-server host 20.1.1.1 traps "v3user" version 3 priv snmp
snmp-server user "v3user" "v3group" v3 auth md5 "abc*_1234" priv des "xyz/+6789"
snmp-server view "view1" 1.3.6.1 included
!
...
...
#
3.10.3 When SNMPv3 cannot be used
When an unexpected reboot (due to power outage, etc.) occurs when the Switch starts or
immediately after the input of the
snmp-server engineID local configuration command,
the Engine ID and the restart count after changing the Engine ID that are recorded in the
internal flash memory might become corrupted.
When SNMPv3 cannot be used, see Procedure for recovering the SNMP engine ID under
Using SNMP to Manage Networks in the Configuration Guide Vol. 2 to recover the engine
ID.