3. Troubleshooting Functional Failures in Operation1103.14 SNMP Communication Failure3.14.1 MIBs Cannot Be Obtained from SNMP ManagerConfirm that the configuration has been set correctly.When using SNMPv1 or SNMPv2CExecute the show access-list command to confirm that the IP address of the SNMP manager has beenregistered on the access list in the configuration. Execute the show snmp-server command to confirm that thecommunity name and access list have been registered correctly.If they are not registered, execute configuration command snmp-server community to set up the informationon the SNMP manager.(config)# show access-listaccess-list enableaccess-list 1 permit ip 20.1.1.1 0.0.0.255!(config)# show snmp-serversnmp-server community "event-monitor" ro 1!(config)#When using SNMPv3Execute the show snmp-server command to confirm that the information on the SNMP manager has beenregistered in the configuration for this system. If it is not correctly registered, execute the configuration commandbelow to set up the information on the SNMP manager.• snmp-server engineID local• snmp-server view• snmp-server user• snmp-server group(config)# show snmp-serversnmp-server engineID local "engine-ID"snmp-server group "v3group" v3 priv read "view1" write "view1"snmp-server user "v3user" "v3group" v3 auth md5 "abc*_1234" priv des "xyz/+6789"snmp-server view "view1" 1.3.6.1.2.1.1 included!(config)#3.14.2 Traps Cannot Be Received by SNMP ManagerConfirm that the configuration has been set correctly.When using SNMPv1 or SNMPv2CExecute configuration command show snmp-server to confirm that the information on the SNMP managerand trap has been registered in the configuration for this system.If it is not registered, execute configuration command snmp-server host to set up the information on theSNMP manager and trap.(config)# show snmp-serversnmp-server host 20.1.1.1 traps "event-monitor" snmp!(config)#
