300-410 Question 263
Single answerA network administrator is troubleshooting SNMP communication between a monitoring server and a router. The monitoring server is using SNMPv3, but no SNMP data is being received. Upon investigation, the administrator identifies that the following configuration is present on the router:
snmp-server group MONITOR v3 priv snmp-server user MONITOR_USER MONITOR v3 auth sha MYAUTHPASS priv aes 128 MYPRIVPASS snmp-server host 192.168.1.100 version 3 priv MONITOR_USER
What could be the cause of the issue?
- A
The SNMP group is incorrectly configured to use the 'auth' level instead of 'priv'.
- B
The SNMP user MONITOR_USER is not associated with the correct group.
- C
The monitoring server is not using the correct authentication or privacy credentials.
- D
The SNMP host configuration does not match the IP address of the monitoring server.
Show answer and explanation
Correct answer: C
Explanation
In SNMPv3, both authentication and privacy credentials must match between the SNMP server (router) and the monitoring client. In this scenario, the router is configured correctly with the 'MONITOR_USER' user, 'sha' for authentication, and 'aes 128' for privacy. However, if the monitoring server is not using the same credentials, communication will fail. None of the other options indicate a misconfiguration in the router that would cause the issue.
- A. Incorrect.
This is incorrect because the configuration explicitly specifies 'priv' for the SNMP group, which is the appropriate privacy level for SNMPv3.
- B. Incorrect.
This is incorrect because the user MONITOR_USER is correctly associated with the MONITOR group, as seen in the configuration.
- C. Correct.
This is correct because if the monitoring server does not use the same authentication password (MYAUTHPASS) or privacy password (MYPRIVPASS) configured on the router, SNMP communication will fail.
- D. Incorrect.
This is incorrect because the host IP address (192.168.1.100) in the configuration matches the monitoring server's IP address.