NSE7-FSN-AR-7-6Demo

By Fortinet · Question Mode

QuestionQ14

Rules and routing

Refer to the exhibit. The output from a BGP debug command is displayed.

Question Image

What is the most likely reason the local FortiGate is not receiving any prefixes from its neighbors?

  • A None of the three neighbors has successfully established the TCP three-way handshake with the local router.
  • B The local router is waiting for the keepalive message from the router 10.125.0.60.
  • C The router 100.64.3.1 is waiting for the OPEN message from the local router.
  • D The RIB-OUT configuration for router 10.127.0.75 prevents any route advertisement to the local router.
Explanation

A BGP neighbor shown with a numeric State/PfxRcd value has an established session; a value of 0 means that no prefixes were received. The session with 10.127.0.75 is established but supplies zero prefixes, which is consistent with that neighbor's RIB-Out policy filtering all route advertisements destined for the local FortiGate. The other neighbors are not established: OpenSent is awaiting the peer's OPEN message, while Active indicates an unsuccessful TCP connection attempt. Fortinet documents get router info bgp summary as the command for checking BGP peering status and uses the final field to show received-prefix counts.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!