Question

A network engineer configures SNMPv3 for both polling and traps on a Catalyst switch. Polling from the NMS works correctly using user 'netops' with authPriv, but the NMS never receives any SNMPv3 traps from the switch. The relevant configuration includes: 'snmp-server user netops NETGRP v3 auth sha Cisco123! priv aes 128 Cisco456!', 'snmp-server group NETGRP v3 priv read READVIEW', and 'snmp-server host 10.1.1.50 version 3 priv netops'. What is the most likely reason traps are not being received?

Accepted Answer

The 'snmp-server host' command references the correct user, but no 'snmp-server enable traps' command has been configured to generate notifications

Answer

The 'snmp-server group NETGRP v3 priv' line is missing the 'notify' view, so no notifications are authorized to be sent

Answer

SNMPv3 does not support traps; only informs can be sent with version 3, so the host command must use the 'informs' keyword

Answer

The engine ID of the switch must be manually configured on the host line for outbound traps to be authenticated by the NMS