FortiGate BGP commands for neighbors and route verification

Inspect one neighbor #

get router info bgp summary

get router info bgp neighbors 198.51.100.10

Use the summary to find the affected peer and then read that peer's detailed state, uptime and negotiated capabilities. In the summary's state/prefix column, a prefix count indicates an established exchange; state names such as Idle or Active require a different investigation. Active is not a synonym for a healthy session.

If the peer is not established, establish whether packets to and from TCP port 179 are visible and whether the peer address has the expected route. Compare the two endpoints' AS numbers, source addresses and intended topology. Do not start by clearing every BGP peer: that changes the situation you are trying to explain.

An empty neighbor list also needs context. With dynamic neighbor groups and ranges, a peer may not appear until the remote endpoint initiates the connection. Do not equate an empty summary with absent BGP configuration.

Separate route views #

get router info bgp neighbors 198.51.100.10 routes

get router info bgp neighbors 198.51.100.10 advertised-routes

get router info routing-table bgp

get router info routing-table detail 192.0.2.80

The neighbor route view shows routes accepted after inbound filtering. The advertised view shows what this FortiGate offers to that peer. The routing-table view answers a different question: which BGP-derived routes participate in forwarding? When a prefix appears in one view but not another, that boundary is the useful lead.

Optionally inspect pre-policy received routes #

get router info bgp neighbors 198.51.100.10 received-routes

This view depends on inbound soft reconfiguration being available for the neighbor. If the command reports that it is not enabled, do not interpret the error as proof that the peer advertised nothing. Enabling additional route retention is a configuration and resource decision, outside this read-only reference.

Follow a single prefix #

Choose one failing destination and document the exact prefix, next hop, peer and route view where it disappears. For example, an accepted prefix that is not the selected forwarding route calls for route-selection analysis; a prefix absent from advertised-routes calls for export/origination checks. Confirm the corresponding view on the peer before assigning responsibility.

IPv6 uses the separate get router info6 ... command family. Do not substitute an IPv6 address into every IPv4 example and assume identical output. Save both address-family context and VDOM with the result.