No routing policy is configured
Peer: 3::2
Type: EBGP link
BGP version 4, remote router ID 3.3.3.3
BGP current state: Established, Up for 00h05m00s
BGP current event: KATimerExpired
BGP last state: OpenConfirm
Port:
Configured: Active Hold Time: 180 sec
Received
Negotiated: Active Hold Time: 180 sec
Peer optional capabilities:
Peer support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support BGP route AS4 capability
Address family IPv6 Unicast: advertised and received
Received: Total 8 messages, Update messages 1
Sent: Total 8 messages, Update messages 1
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Peer preferred value: 0
IPsec profile name: policy002
Routing policy configured:
No routing policy is configured
The output shows that IBGP and EBGP peers are established and both sent and received IPv6 BGP
packets are encapsulated by IPsec.
Troubleshooting BGP
Symptom
Display BGP peer information by using the display bgp peer ipv4 unicast or display bgp peer ipv6
unicast command. The state of the connection to a peer cannot become established.
Analysis
To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange
Open messages successfully.
Local: 2.2.2.2
Local - 24897
Remote - 179
: Active Hold Time: 180 sec
Keepalive Time: 60 sec
Keepalive Time: 60 sec
312