display bgp peer

Function

The display bgp peer command displays BGP peers.

Format

display bgp [ vpnv4 vpn-instance vpn-instance-name ] peer [ { group-name | ipv4-address } log-info | [ ipv4-address ] verbose ]

display bgp vpnv4 all peer [ [ ipv4-address ] verbose ]

display bgp vpn-target peer [ [ ipv4-address ] verbose ]

display bgp ipv6 peer [ verbose ]

display bgp ipv6 peer ipv6-address verbose

display bgp ipv6 peer ipv6-address { log-info | verbose }

display bgp vpnv6 all peer [ [ ipv6-address ] verbose ]

display bgp vpnv6 vpn-instance vpn-instance-name peer [ { group-name | ipv6-address } log-info | [ ipv6-address ] verbose ]

display bgp multicast peer [ [ ipv4-address ] verbose ]

Parameters

Parameter	Description	Value
vpnv4	Displays the peer of Virtual Private Network version 4 (VPNv4).	-
vpn-instance vpn-instance-name	Displays the peers of VPN instance.	The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
group-name	Specifies the name of a peer group.	The name is a string of 1 to 47 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
ipv4-address	Specifies the address of an IPv4 peer. To display IPv6 Provider Edge (6PE) peers, run the display bgp ipv6 peer ipv4-address verbose command.	The value is in dotted decimal notation.
log-info	Displays log information of the peer.	-
verbose	Displays the detailed information of the peer.	-
all	Displays all peers.	-
vpn-target	Displays information about peers in the VPN-Target address family.	-
ipv6	Displays IPv6 peers.	-
ipv6-address	Specifies the address of an IPv6 peer.	The prefix is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.
vpnv6	Displays information about BGP Virtual Private Network version 6 (VPNv6) peers.	-
multicast	Displays Multicast BGP (MBGP) peers.	-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display bgp peer command displays BGP peer information. You can implement the following operations based on the command output:

Check the status of BGP connections.
Check information about a BGP peer.
Check whether a BGP peer is configured using the peer as-number command.
Check whether a BGP peer is deleted using the undo peer as-number command.

Precautions

BGP has multiple address and sub-address families. By default, the display bgp peer command displays information about BGP peers in IPv4 unicast address family only. If you want to view information about BGP peers in another address family, specify its address family parameter.

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.

If log-info is specified in the command, log information about a BGP peer is displayed, including information about BGP peer flapping.

Example

# Display information about BGP peers.

<sysname> display bgp peer

 BGP Local router ID : 10.2.3.4
 local AS number : 10
 Total number of peers : 2                 Peers in established state : 1

  Peer             V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.1.1.1          4   100        0        0     0 00:00:07        Idle       0
  10.2.5.6          4   200       32       35     0 00:17:49 Established       0

**Table 1** Description of the **display bgp peer** command output
Item	Description
BGP Local router ID	BGP local router ID. NOTE: If two ends have the same BGP local router ID, no BGP peer relationship can be established between them. In this situation, run the router id command in the BGP view on either end to change the BGP local router ID. Changing it to the IP address of a loopback interface is recommended.
local AS number	Local AS number.
Total number of peers	Total number of BGP peers.
Peers in established state	Total number of BGP peers in Established state.
Peer	IP address of the peer.
V	BGP version used by the peer. Currently, BGP4 is used.
AS	Autonomous System number.
MsgRcvd	Number of received messages.
MsgSent	Number of sent messages.
OutQ	Message to be sent to the specified peer.
Up/Down	Period during which a BGP session keeps the current state.
State	Status of the peer: Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP. Upon receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection initiated by the remote BGP peer, and changes its state to Connect. Idle(Admin): indicates that the peer relationship is shut down on purpose and no attempt is made to establish the peer relationship. If the peer ignore command is configured or the peer is set to the Down state through the MIB, the peer is in the Idle (Admin) state. Idle(Ovlmt): indicates that the peer relationship is interrupted because the number of routes exceeds the upper threshold. After a BGP peer relationship is interrupted due to the running of the peer route-limit command, the status of the BGP peer relationship is displayed as Idle(Ovlmt). If the reset bgp command is not run, the BGP peer relationship will not be reestablished. Connect: indicates that BGP waits for the TCP connection to be set up before it determines whether to perform other operations. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection to the remote BGP peer, and stays in the Connect state. Active: indicates that BGP tries to set up a TCP connection. This is the intermediate status of BGP. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect. If BGP initiates a TCP connection with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state. OpenSent: indicates that BGP has sent one Open message to its peer and waits for the other Open message from the peer. If there are no errors in the Open message received, BGP changes its state to OpenConfirm. If there are errors in the Open message received, BGP sends a Notification message to the remote peer and changes its state to Idle. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active. OpenConfirm: indicates that BGP waits for a Notification message or a Keepalive message. If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle. If BGP receives a Keepalive message, BGP changes its state to Established. Established: indicates that BGP peers can exchange Update, Notification and Keepalive packets. If BGP receives an Update or a Keepalive message, its state stays in Established. If BGP receives a Notification message, BGP changes its state to Idle.
PrefRcv	Number of prefixes received by the local peer from the remote peer

# Display detailed information of a BGP peer.

<sysname> display bgp peer 10.2.2.9 verbose

         BGP Peer is 10.2.2.9,  remote AS 200
         Type: EBGP link 
         BGP version 4, Remote router ID 0.0.0.0
         Update-group ID: 0
         BGP current state: Established, Up for 20h21m17s
         BGP current event: KATimerExpired
         BGP last state: OpenConfirm
         BGP Peer Up count: 3
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 0
         Port:  Local - 179      Remote - 54446
         Configured: Min Hold Time: 15 sec
         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 4-byte-as capability
         Graceful Restart Capability: advertised
         Address family IPv4 Unicast: advertised and received
 Received: Total 76 messages
                  Update messages                1
                  Open messages                  5
                  KeepAlive messages             71
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 91 messages
                  Update messages                1
                  Open messages                  10
                  KeepAlive messages             77
                  Notification messages          4
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2012-03-06 19:17:37 UTC-8:00
 Last keepalive sent    : 2012-03-06 19:17:37 UTC-8:00
 Last update    received: 2012-03-06 19:17:43 UTC-8:00
 Last update    sent    : 2012-03-06 19:17:37 UTC-8:00
 Minimum route advertisement interval is 30 seconds 
 Optional capabilities: 
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Listen-only has been configured
 Peer's BFD has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Out-delay has been configured, delay value: 50 second(s)

**Table 2** Description of the **display bgp peer verbose** command output
Item	Description
BGP Peer is 10.2.2.9	IP address of the peer.
remote AS 200	AS number of the remote peer.
Type	Type of a BGP link: IBGP or EBGP.
BGP version	BGP version used by the peer. Currently, BGP4 is used.
remote router ID	Router ID of the peer.
Update-group ID	ID of the update-group.
BGP current state	Current state of BGP: Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP. Upon receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection initiated by the remote BGP peer, and changes its state to Connect. Idle(Admin): indicates that the peer relationship is shut down on purpose and no attempt is made to establish the peer relationship. If the peer ignore command is configured or the peer is set to the Down state through the MIB, the peer is in the Idle (Admin) state. Idle(Ovlmt): indicates that the peer relationship is interrupted because the number of routes exceeds the upper threshold. After a BGP peer relationship is interrupted due to the running of the peer route-limit command, the status of the BGP peer relationship is displayed as Idle(Ovlmt). If the reset bgp command is not run, the BGP peer relationship will not be reestablished. Connect: indicates that BGP waits for the TCP connection to be set up before it determines whether to perform other operations. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection to the remote BGP peer, and stays in the Connect state. Active: indicates that BGP tries to set up a TCP connection. This is the intermediate status of BGP. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect. If BGP initiates a TCP connection with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state. OpenSent: indicates that BGP has sent one Open message to its peer and waits for the other Open message from the peer. If there are no errors in the Open message received, BGP changes its state to OpenConfirm. If there are errors in the Open message received, BGP sends a Notification message to the remote peer and changes its state to Idle. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active. OpenConfirm: indicates that BGP waits for a Notification message or a Keepalive message. If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle. If BGP receives a Keepalive message, BGP changes its state to Established. Established: indicates that BGP peers can exchange Update, Notification and Keepalive packets. If BGP receives an Update or a Keepalive message, its state stays in Established. If BGP receives a Notification message, BGP changes its state to Idle.
BGP current event	BGP current event.
BGP last state	Last status of BGP: OpenConfirm, Idle, Idle(Admin), Idle(Ovlmt), Connect, Active, OpenSent, or Established
BGP Peer Up count	Flapping count of a BGP peer during a specific period.
Received total routes	Number of received prefixes.
Received active routes total	Number of active prefixes.
Advertised total routes	Number of advertised prefixes.
Port	Port number: Local: local port number. BGP uses TCP as the transport layer protocol, with port number 179. Remote: port number of the peer
Configured	Locally configured timers: Connect-retry Time: indicates the ConnectRetry interval for a BGP peer or peer group, in seconds. When BGP initiates a TCP connection, the ConnectRetry timer is stopped if the TCP connection is established successfully. If the first attempt to establish a TCP connection fails, BGP tries again to establish the TCP connection after the ConnectRetry timer expires. Min Hold Time: indicates the minimum Holdtime configured on the local device, in seconds. Active Hold Time: indicates the Holdtime period, in seconds. If BGP does not receive any Keepalive message from a peer within the Holdtime period, BGP considers that the connection with the peer is disconnected, and then BGP notifies other peers to remove the routes received from the disconnected peer. Keepalive Time: indicates the interval for sending Keepalive messages to the peer. BGP peers send Keepalive messages to each other periodically to advertise their working state.
Received : Active Hold Time	Holdtime period of the peer
Negotiated	Negotiated timers with the BGP peer: Active Hold Time: Holdtime period negotiated by BGP peers. Keepalive Time: Keepalive period negotiated by BGP peers.
Address family IPv4 Unicast	IPv4 unicast address family.
Received	Number of messages received from peers: Total: total messages received from peers Update messages: number of Update messages received from peers Open messages: number of Open messages received from peers KeepAlive messages: number of Keepalive messages received from peers Notification messages: number of Notification messages received from peers Refresh messages: number of Route-refresh messages received from peers
Sent	Number of messages sent to peers: Total: total messages sent to peers Update messages: number of Update messages sent to peers Open messages: number of Open messages sent to peers KeepAlive messages: number of Keepalive messages sent to peers Notification messages: number of Notification messages sent to peers Refresh messages: number of Route-refresh messages sent to peers
Authentication type configured	Configured BGP authentication type: Message Digest 5 (MD5) Keychain (kk), in which kk indicates the name of the configured keychain authentication None, which indicates no BGP authentication is configured
Last keepalive received	Time when the Keepalive packet was received last time, in any of the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last keepalive sent	Indicates the time when the Keepalive packet is sent last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last update received	Time when the Update packet was received last time, in any of the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last update sent	Indicates the time when the update packet is sent last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Minimum route advertisement interval is 30 seconds	Minimum interval for advertising routes by default: For EBGP, this value is 30 seconds For IBGP, this value is 15 seconds
Peer optional capabilities	Capability supported by peers (optional). Peer supports bgp multi-protocol extension: Indicates the BGP peer supports BGP multi-protocol extension. Peer supports bgp route refresh capability: Indicates the BGP peer supports BGP route refresh. Peer supports bgp 4-byte-as capability: Indicates the BGP peer supports BGP 4-byte AS numbers.
Graceful Restart Capability	Graceful Restart (GR) capability: advertised: Indicates the GR capability has been advertised to the peer. received: Indicates BGP has received the GR capability from the peer.
Optional capabilities	Capabilities supported by the peer (optional).
Route refresh capability has been enabled	Route-refresh is enabled.
4-byte-as capability has been enabled	4-byte-AS capability is enabled.
Listen-only has been configured	The peers only listens to connection requests.
Peer Preferred Value	PrefVal of the peer
Routing policy configured	Configured routing policy.
Peer's BFD has been enabled	BFD is enabled on the peer.
Out-delay has been configured, delay value: 50 second(s)	Update packets are sent with a delay of 50s.

# Display the BGP peer of the VPN instance named vrf1.

<sysname> display bgp vpnv4 vpn-instance vrf1 peer

 BGP local router ID : 10.1.1.9
 Local AS number : 100

 VPN-Instance vrf1, Router ID 10.1.1.9:
 Total number of peers : 2                 Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.2.6.5         4       65410        0        0     0 19:37:40        Idle   0
  10.1.2.2        4       65410        5        8     0 00:02:25 Established   0

# Display detailed information about the BGP peer of the VPN instance named vpna.

<sysname> display bgp vpnv4 vpn-instance vpna peer verbose

         BGP Peer is 10.1.2.2,  remote AS 65410
         Type: EBGP link
         BGP version 4, Remote router ID 10.10.10.10
         Update-group ID: 1
         BGP current state: Established, Up for 00h06m07s
         BGP current event: KATimerExpired
         BGP last state: OpenConfirm
         BGP Peer Up count: 1
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 3
         Port:  Local - 179      Remote - 49459

         Configured: Connect-retry Time: 32 sec

         Configured: Min Hold Time: 15 sec

         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 4-byte-as capability
         Address family IPv4 Unicast: advertised and received
 Received: Total 9 messages
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             8
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 13 messages
                  Update messages                3
                  Open messages                  2
                  KeepAlive messages             8
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2012-03-06 19:17:37 UTC-8:00
 Last keepalive sent    : 2012-03-06 19:17:37 UTC-8:00
 Last update    received: 2012-03-06 19:17:43 UTC-8:00
 Last update    sent    : 2012-03-06 19:17:37 UTC-8:00
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Multi-hop ebgp has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Out-delay has been configured, delay value: 50 second(s)

# Display information about IPv6 peers.

<sysname> display bgp ipv6 peer

 BGP Local router ID : 10.0.0.1

 local AS number : 100
  Total number of peers : 1                 Peers in established state : 1

  Peer            V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  20::21          4   200       17       19     0 00:09:59 Established       3

# Display detailed information about IPv6 peers.

<sysname> display bgp ipv6 peer 2001::1 verbose

         BGP Peer is 2001::1,  remote AS 1
         Type: EBGP link
         BGP version 4, Remote router ID 1.1.1.1
         Update-group ID: 1
         BGP current state: Established, Up for 00h00m59s
         BGP current event: RecvKeepalive
         BGP last state: OpenConfirm
         BGP Peer Up count: 2
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 0
         Port:  Local - 179      Remote - 49153

         Configured: Connect-retry Time: 32 sec

         Configured: Min Hold Time: 15 sec

         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 4-byte-as capability
         Address family IPv6 Unicast: advertised and received
 Received: Total 76 messages
                  Update messages                1
                  Open messages                  5
                  KeepAlive messages             71
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 91 messages
                  Update messages                1
                  Open messages                  10
                  KeepAlive messages             77
                  Notification messages          4
                  Refresh messages               0
 Authentication type configured: None

 Last keepalive received: 2012-03-06 19:17:37 UTC-8:00
 Last keepalive sent    : 2012-03-06 19:17:37 UTC-8:00
 Last update    received: 2012-03-06 19:17:43 UTC-8:00
 Last update    sent    : 2012-03-06 19:17:37 UTC-8:00
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 listen-only has been configured
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Out-delay has been configured, delay value: 50 second(s)

# Display brief information about VPNv6 peers.

<sysname> display bgp vpnv6 all peer

 BGP local router ID : 10.1.1.9
 Local AS number : 100
 Total number of peers : 2                 Peers in established state : 2

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.3.3.9         4         100     1535     1359     0 19:32:16 Established   1

  Peer of IPv6-family for vpn instance :

 VPN-Instance vpn1, Router ID 10.4.4.4 :
  2001::1         4       65410     1249     1458     0 19:44:17 Established   1

# Display detailed information about the VPNv6 peer with the IPv4 address as 10.3.3.9.

<sysname> display bgp vpnv6 all peer 10.3.3.9 verbose

         BGP Peer is 10.3.3.9,  remote AS 100
         Type: IBGP link
         BGP version 4, Remote router ID 10.3.3.9
         Update-group ID: 1
         BGP current state: Established, Up for 20h08m44s
         BGP current event: KATimerExpired
         BGP last state: OpenConfirm
         BGP Peer Up count: 2
         Received total routes: 1
         Received active routes total: 1
         Advertised total routes: 1
         Port:  Local - 179      Remote - 51921

         Configured: Connect-retry Time: 32 sec

         Configured: Min Hold Time: 15 sec

         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 4-byte-as capability
         Address family IPv4 Unicast: advertised and received
         Address family VPNv4: advertised and received
         Address family VPNv6: advertised and received
 Received: Total 1582 messages
                  Update messages                4
                  Open messages                  1
                  KeepAlive messages             1576
                  Notification messages          0
                  Refresh messages               1
 Sent: Total 1402 messages
                  Update messages                3
                  Open messages                  2
                  KeepAlive messages             1395
                  Notification messages          0
                  Refresh messages               2
 Authentication type configured: None
 Last keepalive received: 2012-03-06 19:17:37 UTC-8:00
 Last keepalive sent    : 2012-03-06 19:17:37 UTC-8:00
 Last update    received: 2012-03-06 19:17:43 UTC-8:00
 Last update    sent    : 2012-03-06 19:17:37 UTC-8:00
 Minimum route advertisement interval is 0 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Connect-interface has been configured
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Out-delay has been configured, delay value: 50 second(s)

# Display log information about BGP4+ peer groups of the VPN instance.

<sysname> display bgp vpnv6 vpn-instance vpn1 peer g1 log-info

 Peer : 2000::2

 Date\Time     : 2010/12/27 11:16:13 UTC UTC-8:00

 State         : Up

 Date\Time     : 2010/12/27 11:16:05 UTC-08:00

 State         : Down

 Error Code    : 6(CEASE)

 Error Subcode : 3(Peer De-configured)

 Notification  : Receive Notification

 Date\Time     : 2010/12/27 11:16:11 UTC-08:00

 State         : Up

 Date\Time     : 2010/12/27 11:16:06 UTC-08:00

 State         : Down

 Error Code    : 6(CEASE)

 Error Subcode : 4(Administrative Reset)

 Notification  : Send Notification

 Date\Time     : 2010/12/27 11:12:52 UTC-08:00

 State         : Up

# Display detailed information about BGP4+ peers of the VPN instance with the IPv6 address as 2001::1 on the local router.

<sysname> display bgp vpnv6 vpn-instance vpn1 peer 2001::1 verbose

         BGP Peer is 2001::1,  remote AS 65410
         Type: EBGP link
         BGP version 4, Remote router ID 10.10.10.10
         Update-group ID: 1
         BGP current state: Established, Up for 20h34m36s
         BGP current event: KATimerExpired
         BGP last state: OpenConfirm
         BGP Peer Up count: 1
         Received total routes: 1
         Received active routes total: 0
         Advertised total routes: 1
         Port:  Local - 49152    Remote - 179

         Configured: Connect-retry Time: 32 sec

         Configured: Min Hold Time: 15 sec

         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 4-byte-as capability
         Address family IPv6 Unicast: advertised and received
 Received: Total 1302 messages
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             1300
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 1520 messages
                  Update messages                7
                  Open messages                  1
                  KeepAlive messages             1512
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2012-03-06 19:17:37-08:00
 Last keepalive sent    : 2012-03-06 19:17:37-08:00
 Last update    received: 2012-03-06 19:17:43-08:00
 Last update    sent    : 2012-03-06 19:17:37-08:00
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Out-delay has been configured, delay value: 50 second(s)