200-101 · Question #99
Refer to the exhibit. What is the cause of the Syslog output messages?
The correct answer is C. A shut command was executed on interface Fa0/1, causing the EIGRP adjacency to go down. The Syslog output shows an EIGRP adjacency going down on interface Fa0/1. When a 'shutdown' command is issued on an interface, it brings the interface administratively down, which immediately tears down any routing protocol adjacencies (including EIGRP) that rely on that…
Question
Options
- AThe EIGRP neighbor on Fa0/1 went down due to a failed link.
- BThe EIGRP neighbor connected to Fa0/1 is participating in a different EIGRP process, causing the adjacency to go down.
- CA shut command was executed on interface Fa0/1, causing the EIGRP adjacency to go down.
- DInterface Fa0/1 has become error disabled, causing the EIGRP adjacency to go down.
How the community answered
(30 responses)- A10% (3)
- B7% (2)
- C80% (24)
- D3% (1)
Explanation
The Syslog output shows an EIGRP adjacency going down on interface Fa0/1. When a 'shutdown' command is issued on an interface, it brings the interface administratively down, which immediately tears down any routing protocol adjacencies (including EIGRP) that rely on that interface. The Syslog messages would show the interface state change followed by the EIGRP neighbor adjacency going down - a sequence consistent with a manual shutdown. A failed link (A) would show a physical line-protocol down message without an admin-down state. A mismatched EIGRP process (B) would show a different error. An err-disabled interface (D) results from a security violation (e.g., port security), not a simple EIGRP adjacency drop.
Topics
Community Discussion
No community discussion yet for this question.