Question

An NMS successfully polls the global routing table of a router using SNMPv3 (authPriv), but every attempt to poll interface counters and routing data that reside inside VRF 'CUSTOMER-A' times out. The SNMPv3 user credentials, engine ID, and authentication/privacy passphrases are confirmed correct because global OIDs return data. The router runs the VRF-aware SNMP feature. Which configuration omission most likely explains why the VRF data cannot be retrieved?

Accepted Answer

The SNMPv3 group is not mapped to a context, and no 'snmp-server context' / 'snmp mib community-map' or 'snmp-server group ... context' association exists to bind the VRF context to the user's group

Answer

The SNMPv3 user is configured with the wrong privacy protocol (AES vs DES) for the VRF

Answer

The 'snmp-server host' command is missing the 'vrf CUSTOMER-A' keyword for the NMS destination

Answer

The NMS is using UDP port 161 instead of port 162 to reach the VRF instance