The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp flow peer verbose
BGP Peer is 1.1.1.1, remote AS 100
Type: EBGP link
BGP version 4, Remote router ID 1.1.1.1
Update-group ID: 1
BGP current state: Established, Up for 00h20m44s
BGP current event: RecvKeepalive
BGP last state: Established
BGP Peer Up count: 1
Received total routes: 1
Received active routes total: 1
Advertised total routes: 1
Port: Local - 51783 Remote - 179
Configured: Active Hold Time: 180 sec Keepalive Time:60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time:60 sec
Peer optional capabilities:
Peer supports bgp multi-protocol extension
Peer supports bgp route refresh capability
Peer supports bgp route-policy-distribute capability
FLOWv4 address-family: send
Negotiated bgp route-policy-distribute capability
FLOWv4 address-family: receive
Peer supports bgp 4-byte-as capability
Address family IPv4 Unicast: advertised and received
Address family FLOWv4: advertised and received
Received: Total 25 messages
Update messages 3
Open messages 1
KeepAlive messages 21
Notification messages 0
Refresh messages 0
Sent: Total 25 messages
Update messages 3
Open messages 1
KeepAlive messages 21
Notification messages 0
Refresh messages 0
Authentication type configured: None
Last keepalive received:2011-10-14 05:42:05
Minimum route advertisement interval is 30 seconds
Optional capabilities:
Route refresh capability has been enabled
Route-policy-distribute capability has been enabled
FLOWv4 address-family: receive
4-byte-as capability has been enabled
Peer Preferred Value: 0
Memory Priority: high
Routing policy configured:
No routing policy is configured
| Item | Description |
|---|---|
| BGP version | BGP version. |
| BGP current state | Current BGP status:
|
| BGP current event | Current BGP event. |
| BGP last state | State of last BGP stage, which may be Idle, Connect, Active, OpenSent, OpenConfirm, Established or No neg. |
| BGP Peer Up count | Number of times the BGP FlowSpec peer alternates between Up and Down. |
| Peer optional capabilities | Optional capabilities supported by the BGP FlowSpec peer. |
| Peer supports bgp multi-protocol extension | The BGP FlowSpec peer supports MP-BGP. |
| Peer supports bgp route refresh capability | The BGP FlowSpec peer supports route-refresh. |
| Peer supports bgp route-policy-distribute capability | Routing Policy Distribution (RPD) capability of the BGP FlowSpec peer:
|
| Peer supports bgp 4-byte-as capability | The BGP FlowSpec peer supports 4-byte AS numbers. |
| Peer Preferred Value | Preferred value of the BGP FlowSpec peer. |
| Update-group ID | Update group ID of the BGP FlowSpec peer. |
| Received total routes | Number of route prefixes received. |
| Received active routes total | Number of active route prefixes received. |
| Received : Active Hold Time | Hold time of the BGP FlowSpec peer. |
| Received | Number of messages received from the BGP FlowSpec peer:
|
| Advertised total routes | Number of route prefixes sent. |
| Keepalive Time | Indicates the interval at which Keepalive messages are sent to the peer. |
| Negotiated: Active Hold Time | Hold time negotiated with the BGP FlowSpec peer. |
| Negotiated bgp route-policy-distribute capability | RPD capability of the local end after negotiation:
|
| 4-byte-as capability has been enabled | The 4-byte AS numbers are supported. |
| Address family IPv4 Unicast | IPv4 unicast address family. |
| Address family FLOWv4 | BGP-Flow VPN instance IPv4 address family. |
| Authentication type configured | Authentication type. |
| Last keepalive received | Last time when Keepalive messages were received. |
| Minimum route advertisement interval is 30 seconds | Minimum route advertisement interval:
|
| Optional capabilities | Optional capabilities supported by the BGP FlowSpec peer. |
| Route refresh capability has been enabled | Route-refresh is enabled. |
| Route-policy-distribute capability has been enabled | RPD capability of the local end:
|
| 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 FlowSpec peer:
|