Question 280
At Pinebrook Health Systems, while commissioning a routed spine uplink, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. Which recurring validation best prevents this failure mode?
Explanation
Correct Answer
At Pinebrook Health Systems, while commissioning a routed spine uplink, for Pinebrook Health Systems, include the safeguard: Include peer transport checks before tuning route policies. It reduces repeat risk from the original mechanism and complements a validation of: The BGP TCP session establishes and the peer reaches the expected state.
Incorrect Answers
At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Monitor unresolved next hops separately from BGP state. The alternative focuses on The received route's next hop cannot be resolved in the relevant routing instance, not on the stated defect. For this scenario the expected acceptance result would be: The BGP TCP session establishes and the peer reaches the expected state.
At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Maintain explicit management-prefix exclusion tests. This option assumes the other problem (A leaf exports its connected management subnet into tenant-visible fabric routing) 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 Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Use positive and negative prefix fixtures when revising route policy. The option describes a different failure mode: A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes. It would address A prefix match was broader than the approved route-exchange scope, 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.