Question 370
At Harborstone Health Systems, while investigating next-hop reachability, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Harborstone Health Systems, while investigating next-hop reachability, for Harborstone Health Systems, accept the repair only after this observation: The BGP TCP session establishes and the peer reaches the expected state. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Harborstone Health Systems, while investigating next-hop reachability, this option proposes: The forwarding state lists the intended next-hop set for the test destination. This option assumes the other problem (A network engineer assumes multiple BGP peers automatically imply load-balanced traffic) is present. The case instead describes Two fabric peers have BGP configured but the session stays Idle with no TCP connection, for which the causal issue is The peer address is unreachable or TCP 179 is blocked by the underlay policy.
At Harborstone Health Systems, while investigating next-hop reachability, this option proposes: The default route resolves to an active next hop and controlled traffic reaches the gateway. The option describes a different failure mode: A static default route appears in configuration but never forwards traffic. It would address The referenced next-hop group has no reachable selected member, but here the case reports Two fabric peers have BGP configured but the session stays Idle with no TCP connection. The current required evidence is: The BGP TCP session establishes and the peer reaches the expected state.
At Harborstone Health Systems, while investigating next-hop reachability, this option proposes: Representative addresses within the target subnet follow the expected route. That choice would be more relevant when this different symptom occurs: An engineer configures a static route destination as a host when an entire subnet is needed. The present scenario instead points to: The peer address is unreachable or TCP 179 is blocked by the underlay policy. The correct resolution has its own verification outcome: The BGP TCP session establishes and the peer reaches the expected state.