Meanings of BGP peer status


In addition to the common Idle and Established status, BGP peer also has the following status:

1. active: indicates that the TCP connection of the BGP session has not been established.
2. no neg: indicates that the negotiation is not performed. If IPv4 Unicast is configured at one end, and IPv4 Unicast and IPv4 Multicast are configured at the other end, after the peer is established, you can discover that IPv4 Unicast negotiation succeeds, and the BGP peer is in Established status. However, the IPv4 Multicast is in no neg status in that IPv4 Multicast is not configured at one end.
3. Idle (Admin): indicates the BGP peer is proactively disabled, and there is no attempt to establish it again. If the peer ignore command is executed, or this peer is set to be down through the MIB, this peer remains in this status.

Other related questions:
Monitoring OSPF and BGP status on the firewall
Perform as follows to monitor OSPF and BGP status on the firewall: 1. Choose Network > Route > Dynamic Route Monitoring Table. 2. On the OSPFv2 Route List page, view detailed OSPFv2 route information. 3. On the BGP Route List page, view detailed BGP route information.

Problem and solution when BGP peer cannot be established
The BGP peer establishment on the firewall needs to use port 179 to establish TCP sessions and requires that OPEN messages be properly exchanged. Perform as follows to rectify the issue: 1. Check whether the AS number and IP address among peers are correct by using the display bgp peer command. 2. Check whether the router IDs configured on both BGP peers are conflicting by using the display bgp peer command. 3. If the loopback interface is used, check whether the peer connect-interface command is configured to specify the loopback interface as the source interface for sending BGP packets. 4. If EBGP neighbors are not directly connected to the physical layer, check whether the peer ebgp-max-hop command is configured. 5. Check whether there are available routes to the peer in the routing table. 6. Check whether there are reachable routes to the specified connect-interface by using the ping -a source-ip-address host-address command. 7. Check whether the ACL that is used to disable TCP port 179 is configured.

What do the BGP peer states including Active, No Neg, and Idle(Admin) mean on S series switches
In addition to Idle and Established, BGP Peer can be in other states including: Active: indicates that the TCP connection is not set up for the BGP session. No Neg: indicates that the ability to establish a BGP connection is not negotiated. Assume that one device is configured with IPv4 unicast, and the other device is configured with IPv4 unicast and IPv4 multicast. After the peer relationship is set up between the two devices, the device configured with IPv4 unicast only enters in Established state, whereas the other device configured with IPv4 unicast and IPv4 multicast enters in No Neg state. This is because one device is not configured with IPv4 multicast. Idle (Admin): indicates that a peer is shut down and does not attempt to set up a connection. If the peer ignore command is executed on the peer or the status of the peer is set to Down through the related MIB, the peer is in Idle (Admin) state.

How to configure BGP for S series switches
For information about how to configure basic BGP functions on a S series switch, visit Example for Configuring Basic BGP Functions

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top