Technical Tip: BGP Neighbors Created via CLI Without Remote-AS may Remain in Admin-Down State on FortiGate
| Description | This article describes how to create a BGP neighbor via CLI without a remote-AS (unlike the GUI) can leave the neighbor in an admin-down state despite the remote-AS being configured later. |
| Scope | FortiGate v7.2.10, v7.4.X. |
| Solution | Unlike the GUI, the FortiGate CLI allows BGP neighbor creation without specifying a remote-as.
FGT # config router bgp Neighbors created this way remain in the Admin-down state when the remote-as is added later, even if shutdown is disabled:
FGT # config router bgp FGT # get router info bgp summ VRF 0 BGP router identifier 3.3.3.3, local AS number 65002 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd Starting with v7.6.3, configuring a BGP neighbor via CLI requires specifying the remote-as:
Workaround:
FGT # config router bgp FGT # config router bgp FGT # get router info bgp summary Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd |
