Troubleshooting Bgp; Bgp Peer Relationship Not Established - HPE 5800 Series Configuration Manual

Preference: 150
IpPrecedence:
BkNextHop: 0.0.0.0
RelyNextHop: 0.0.0.0
Tunnel ID: 0x0
BKTunnel ID: 0x0
The output shows that Switch A and Switch C communicate through Switch B, and Switch C
has two routes to reach network 1.1.1.0/24: Switch C<—>Switch B<—>Switch A, which is the
active route; Switch C<—>Switch D<—>Switch A, which is the backup route.
When the link Switch C<—>Switch B<—>Switch A fails, Switch C can quickly detect the link
failure.
# Display route 1.1.1.0/24 on Switch C.
<SwitchC> display ip routing-table 1.1.1.0 24 verbose
Routing Table : Public
Summary Count : 1
Destination: 1.1.1.0/24
Protocol: BGP
Preference: 0
BkNextHop: 0.0.0.0
RelyNextHop: 2.0.2.1
Tunnel ID: 0x0
The output shows that Switch A and Switch C communicate through Switch D, and Switch C
has one route Switch C<—>Switch D<—>Switch A to reach network 1.1.1.0/24.

Troubleshooting BGP

BGP peer relationship not established

Symptom
Display BGP peer information by 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.
Solution
Use the display current-configuration command to verify that the peer's AS number is
1.
correct.
Use the display bgp peer command to verify that the peer's IP address is correct.
2.
If a loopback interface is used, verify that the loopback interface is specified with the peer
3.
connect-interface command.
NextHop: 2.0.2.1
State: Inactive Adv
Tag: 1
NextHop: 2.0.1.1
State: Active Adv
Tag: 0
Cost: 1
QosLcId:
Interface: Vlan-interface201
BkInterface:
Neighbor : 0.0.0.0
Label: NULL
BKLabel: NULL
Age: 00h14m10s
Process ID: 0
Cost: 100
Interface: Vlan-interface201
BkInterface:
Neighbor : 2.0.1.1
Label: NULL
Age: 00h09m54s
245