FCSS_NST_SE-7.6 · Question #100
Refer to the exhibit, which shows the output of a BGP debug command. What is the reason that the local FortiGate is not receiving any prefixes from its neighbors?
The correct answer is D. None of the three neighbors have successfully established the TCP three-way handshake with. Since none of the peers are in the Established state (two remain in Active/OpenSent and the one "0" in the PfxRcd column actually indicates no adjacency), there is no session over which to receive any routes.
Question
Refer to the exhibit, which shows the output of a BGP debug command. What is the reason that the local FortiGate is not receiving any prefixes from its neighbors?
Exhibit
Options
- AThe RIB-OUT configuration for router 10.127.0.75 prevents any route advertisement to the
- BThe router 100.64.3.1 needs to update the local AS number to 65060 to become adjacent with
- CThe local router is waiting for the keepalive message from the router 10.125.0.60.
- DNone of the three neighbors have successfully established the TCP three-way handshake with
How the community answered
(34 responses)- A12% (4)
- B6% (2)
- C21% (7)
- D62% (21)
Explanation
Since none of the peers are in the Established state (two remain in Active/OpenSent and the one "0" in the PfxRcd column actually indicates no adjacency), there is no session over which to receive any routes.
Topics
Community Discussion
No community discussion yet for this question.