The display bgp vpn-target peer verbose command displays detailed information about BGP peers.
Usage Scenario
The display bgp vpn-target peer verbose command can be used for troubleshooting, with details as follows: If BGP peers are disconnected, specify log-info in the command to check the log information of the specified peer. In the command output, Date/Time indicates the time when the peers were disconnected, and Error Code and Error Subcode indicate the cause of the disconnection.
Precautions
To view detailed information about a BGP peer, such as information about BGP timers, the number of sent and received routes, capacities supported, the number of sent and received BGP messages, and enabled functions, specify verbose in the command.
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp vpn-target peer verbose
BGP Peer is 2.2.2.2, remote AS 200
Type: EBGP link
BGP version 4, Remote router ID 2.2.2.2
Update-group ID: 7
BGP current state: Established, Up for 00h12m10s
BGP current event: RecvKeepalive
BGP last state: OpenConfirm
BGP Peer Up count: 3
Received total routes: 0
Received active routes total: 0
Advertised total routes: 0
Port: Local - 53198 Remote - 179
Configured: Connect-retry Time: 32 sec
Configured: Min Hold Time: 0 sec
Configured: Active Hold Time: 30 sec Keepalive Time:10 sec
Received : Active Hold Time: 30 sec
Negotiated: Active Hold Time: 30 sec Keepalive Time:10 sec
Peer optional capabilities:
Peer supports bgp multi-protocol extension
Peer supports bgp route refresh capability
Peer supports bgp 4-byte-as capability
Address family IPv4 Unicast: advertised and received
Address family VPN-Target: advertised and received
Received: Total 93 messages
Update messages 2
Open messages 1
KeepAlive messages 90
Notification messages 0
Refresh messages 0
Sent: Total 93 messages
Update messages 3
Open messages 1
KeepAlive messages 89
Notification messages 0
Refresh messages 0
Authentication type configured: None
Last keepalive received: 2019-09-17 05:12:10+00:00
Last keepalive sent : 2019-09-17 05:12:08+00:00
Last update received: 2019-09-17 05:00:02+00:00
Last update sent : 2019-09-17 05:00:02+00:00
No refresh received since peer has been configured
No refresh sent since peer has been configured
Minimum route advertisement interval is 30 seconds
Optional capabilities:
Route refresh capability has been enabled
4-byte-as capability has been enabled
Connect-interface has been configured
Multi-hop ebgp has been enabled
Peer Preferred Value: 0
Memory Priority: high
Routing policy configured:
No routing policy is configured
Item | Description |
---|---|
BGP Peer | IP address of the BGP peer. |
BGP version | BGP version. |
BGP current state | Status the BGP peer:
|
BGP current event | Current BGP event. |
Peer supports bgp multi-protocol extension | The BGP peer supports MP-BGP. |
Peer supports bgp route refresh capability | The BGP peer supports route-refresh. |
Peer Preferred Value | Preferred value of the BGP peer. |
remote AS | The AS Number of the peer. |
Remote router ID | Router ID of the peer. |
Update-group ID | Update group ID of the BGP peer. |
Received : Active Hold Time | Hold time of the BGP peer. |
Received | Number of messages received from the BGP peer:
|
Negotiated: Active Hold Time | Hold time negotiated with the BGP peer. |
Minimum route advertisement interval is 30 seconds | Minimum route advertisement interval:
|
Optional capabilities | Optional capabilities supported by the BGP peer. |
Route refresh capability has been enabled | Route-refresh is enabled. |
Memory Priority | The priority for a BGP peer relationship to be disconnected if memory overload occurs. |
Routing policy configured | Routing policy configured. |
Type | BGP link type, which can be either IBGP Link or EBGP Link. |
Port | Port number:
|
Configured | Timers that are locally configured:
|
Sent | Number of messages sent to the BGP peer:
|