Question

A network engineer configures SNMPv3 on a router for a monitoring server using authPriv (SHA authentication, AES-128 privacy). The NMS can reach the router and CoPP is not dropping SNMP, but every snmpwalk times out. The engineer runs 'show snmp user' and confirms the user exists with the correct auth and priv protocols. Debugging with 'debug snmp packets' shows incoming requests arriving at the router but no responses being generated. The NMS was recently rebuilt and its SNMP configuration was restored from an old backup. What is the MOST likely cause?

Accepted Answer

The NMS is using a cached/stale authoritative engineID that no longer matches the router, so the router silently discards the requests during authentication

Answer

The router is missing the 'snmp-server host' command for the NMS, so it cannot send responses back

Answer

The SNMPv3 group is not mapped to a view, so all OIDs are excluded from read access

Answer

The privacy protocol should be configured as AES-256 to match the NMS default, causing decryption to fail