Troubleshooting Bgp; No Bgp Peer Relationship Established - H3C S5800 Series Configuration Manual

[SwitchB-bgp] peer 9.1.1.2 as-number 65009
# Inject networks 200.1.1.0/24 and 9.1.1.0/24 to the BGP routing table.
[SwitchB-bgp] network 200.1.1.0 24
[SwitchB-bgp] network 9.1.1.0 24
# Redistribute direct routes.
[SwitchB-bgp] import-route direct
# Enable GR capability for BGP.
[SwitchB-bgp] graceful-restart
3) Configure Switch C
# Configure IP addresses for interfaces (omitted).
# Configure the iBGP connection.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp] router-id 3.3.3.3
[SwitchC-bgp] peer 9.1.1.1 as-number 65009
# Redistribute direct routes.
[SwitchC-bgp] import-route direct
# Enable GR capability for BGP.
[SwitchC-bgp] graceful-restart
Verification
Ping Switch C on Switch A. Meanwhile, perform an active/standby main board switchover on Switch B.
You can ping Switch C from Switch A during the whole switchover process.
The S5800 series switches are centralized devices that support IRF. They can act as a GR Helper
before forming an IRF; they can form a distributed chassis switch in a logical sense and act as a GR
Restarter after forming an IRF. Active and standby switchover in this document refers to the switching
of the master for IRF devices.

Troubleshooting BGP

No BGP Peer Relationship Established

Symptom
Display BGP peer information using the display bgp peer command. The state of the connection to a
peer cannot become established.
Analysis
To become BGP peers, any two routers need to establish a TCP session using port 179 and exchange
Open messages successfully.
Solution
1) Use the display current-configuration command to verify the peer's AS number.
6-73