You are connected to R1, a branch router that must synchronize time with the NTP server at 198.51.100.1 (reachable via G0/0) and send critical syslog messages (severity 0-4) to the logging server at 203.0.113.10. The current configuration has NTP pointing to a wrong server and syslog set to debug level, flooding the server. Correct the NTP server, set the NTP source interface to Loopback0 (10.10.10.1/32), and adjust the syslog trap level so that only emergencies through warnings are logged.
Hints
- •Remove the incorrect NTP server before adding the correct one.
- •Use the 'ntp source' command to specify the Loopback interface.
- •The logging trap level 'warnings' corresponds to severity 4.
! R1 configure terminal no ntp server 192.0.2.1 ntp server 198.51.100.1 ntp source Loopback0 logging trap warnings end
Why this answer
The router points to the wrong NTP server (192.0.2.1: reach 0, stratum 16, unsynchronized). Remove it and configure the correct server 198.51.100.1, with Loopback0 as the NTP source interface (ntp source Loopback0, or the source keyword on the ntp server command). The syslog trap level is debugging (7), which sends every message; 'logging trap warnings' (level 4) sends only emergencies through warnings (severity 0-4).
Verify with show ntp associations, show ntp status and show running-config | include logging trap.
Exam trap
Watch out for two separate configuration items: NTP and syslog. Ensure you update both the NTP server IP and source interface, and set the correct syslog trap level. Common traps include forgetting to change the NTP server IP, using the wrong source interface, or setting the wrong syslog severity level.
Why the other options are wrong
The source interface must be Loopback0 for consistency, and the trap level should be warnings (4) to include warnings.
The NTP server address must be updated to 198.51.100.1; 192.0.2.1 is the misconfigured server.
The trap level should be warnings (4), not debugging (7). Debugging sends all messages, flooding the server.