JN0-281 · Question #41
You are troubleshooting a downed BGP session. Referring to the exhibit, what is the cause of the problem?
The correct answer is C. The TCP session between the peers has not been established. The BGP session in the exhibit shows the state as Connect, which indicates that the TCP session between the BGP peers has not been fully established. BGP State "Connect": The Connect state is the second stage in the BGP finite state machine (FSM). At this stage, BGP is trying…
Question
You are troubleshooting a downed BGP session. Referring to the exhibit, what is the cause of the problem?
Exhibit
Options
- AThe UDP session between the peers has not been established.
- BThe local peer has sent an Open message but not received one from the remote peer.
- CThe TCP session between the peers has not been established.
- DThe local peer has sent an Update message but not received one from the remote peer.
How the community answered
(19 responses)- A16% (3)
- B5% (1)
- C74% (14)
- D5% (1)
Explanation
The BGP session in the exhibit shows the state as Connect, which indicates that the TCP session between the BGP peers has not been fully established. BGP State "Connect": The Connect state is the second stage in the BGP finite state machine (FSM). At this stage, BGP is trying to establish a TCP session with the peer, but the session has not yet been successfully A successful TCP three-way handshake (SYN, SYN-ACK, ACK) is required before BGP can progress to the OpenSent state, where the peers exchange BGP Open messages. Possible Causes: A firewall blocking TCP port 179. Incorrect IP addresses or network connectivity issues between the BGP peers.
Topics
Community Discussion
No community discussion yet for this question.
