303
a.
Configure IP addresses for interfaces (details not shown).
b.
Configure the eBGP connection.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp] router-id 2.2.2.2
[SwitchB-bgp] peer 200.1.1.2 as-number 65008
c.
Configure the iBGP connection.
[SwitchB-bgp] peer 9.1.1.2 as-number 65009
d.
Configure BGP to redistribute direct routes.
[SwitchB-bgp] import-route direct
e.
Enable GR capability for BGP.
[SwitchB-bgp] graceful-restart
3.
Configure Switch C.
a.
Configure IP addresses for interfaces (details not shown).
b.
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
c.
Configure BGP to redistribute direct routes.
[SwitchC-bgp] import-route direct
d.
Enable GR for BGP.
[SwitchC-bgp] graceful-restart
Verification
After completing the previous configuration, perform an active or standby main board switchover
on Switch B. Switch A and Switch C can ping each other.
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 must establish a TCP session using port 179 and
exchange open messages successfully.