show ipv6 bgp neighbors

Displays configuration information and statistics for BGP4+ neighbors of the device.
Syntax
show ipv6 bgp neighbors
show ipv6 bgp neighbors ipv6-addr
show ipv6 bgp neighbors last-packet-with-error
show ipv6 bgp neighbors routes-summary
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
last-packet-with-error
Displays information about the last packet from a neighbor that contained an error.
routes-summary
Displays information about all route information received in UPDATE messages from BGP neighbors.
Modes

User EXEC mode

Usage Guidelines

Use this command to view configuration information and statistics for BGP neighbors of the device. Output shows all configured parameters for the neighbors. Only the parameters whose values differ from defaults are shown.

The show ipv6 bgp neighbors command displays the following information:

Output field Description

IP Address

The IPv6 address of the neighbor.

AS

The AS in which the neighbor resides.

EBGP or IBGP

Whether the neighbor session is an IBGP session, an EBGP session, or a confederation EBGP session:

  • EBGP - The neighbor is in another AS.
  • EBGP_Confed - The neighbor is a member of another sub-AS in the same confederation.
  • IBGP - The neighbor is in the same AS.

RouterID

The neighbor’s router ID.

State

The state of the device’s session with the neighbor. The states are from the perspective of the session, not the neighbor’s perspective. The state values can be one of the following:

  • IDLE - The BGP4+ process is waiting to be started. Usually, enabling BGP4 or establishing a neighbor session starts the BGP4+ process.
    • A minus sign (-) indicates that the session has gone down and the software is clearing or removing routes.
  • ADMND - The neighbor has been administratively shut down.
    • A minus sign (-) indicates that the session has gone down and the software is clearing or removing routes.
  • CONNECT - BGP4+ is waiting for the connection process for the TCP neighbor session to be completed.
  • ACTIVE - BGP4+ is waiting for a TCP connection from the neighbor.
Note: If the state frequently changes between CONNECT and ACTIVE, there may be a problem with the TCP connection.
  • OPEN SENT - BGP4+ is waiting for an Open message from the neighbor.
  • OPEN CONFIRM - BGP4+4 has received an OPEN message from the neighbor and is now waiting for either a KEEPALIVE or NOTIFICATION message. If the device receives a KEEPALIVE message from the neighbor, the state changes to Established. If the message is a NOTIFICATION, the state changes to Idle.
  • ESTABLISHED - BGP4+ is ready to exchange UPDATE messages with the neighbor.
    • If there is more BGP data in the TCP receiver queue, a plus sign (+) is also displayed.
Note: If you display information for the neighbor using the show ipv6 bgp neighbor<ipv6-address> command, the TCP receiver queue value will be greater than 0.

Time

The amount of time this session has been in its current state.

KeepAliveTime

The keep alive time, which specifies how often this device sends keep alive messages to the neighbor.

HoldTime

The hold time, which specifies how many seconds the device will wait for a KEEPALIVE or UPDATE message from a BGP4+ neighbor before deciding that the neighbor is dead.

RefreshCapability

Whether the device has received confirmation from the neighbor that the neighbor supports the dynamic refresh capability.

Messages Sent and Received

The number of messages this device has sent to and received from the neighbor. The display shows statistics for the following message types:

  • Open
  • Update
  • KeepAlive
  • Notification
  • Refresh-Req

Last Update Time

Lists the last time updates were sent and received for the following:

  • NLRIs
  • Withdraws

Last Connection Reset Reason

The reason the previous session with this neighbor ended. The reason can be one of the following:

  • No abnormal error has occurred.
  • Reasons described in the BGP specifications:
    • Message Header Error
    • Connection Not Synchronized
    • Bad Message Length
    • Bad Message Type
    • OPEN Message Error
    • Unsupported Version Number
    • Bad Peer AS Number
    • Bad BGP Identifier
    • Unsupported Optional Parameter
    • Authentication Failure
    • Unacceptable Hold Time
    • Unsupported Capability
    • UPDATE Message Error
    • Malformed Attribute List
    • Unrecognized Well-known Attribute
    • Missing Well-known Attribute
    • Attribute Flags Error
    • Attribute Length Error
    • Invalid ORIGIN Attribute
    • Invalid NEXT_HOP Attribute
    • Optional Attribute Error
    • Invalid Network Field
    • Malformed AS_PATH
    • Hold Timer Expired
    • Finite State Machine Error
    • Rcv Notification

Last Connection Reset Reason (cont.)

  • Reasons specific to the implementation:
    • Reset All Peer Sessions
    • User Reset Peer Session
    • Port State Down
    • Peer Removed
    • Peer Shutdown
    • Peer AS Number Change
    • Peer AS Confederation Change
    • TCP Connection KeepAlive Timeout
    • TCP Connection Closed by Remote
    • TCP Data Stream Error Detected

Notification Sent

If the device receives a NOTIFICATION message from the neighbor, the message contains an error code corresponding to one of the following errors. Some errors have subcodes that clarify the reason for the error. Where applicable, the subcode messages are listed underneath the error code messages.

  • Message Header Error
    • Connection Not Synchronized
    • Bad Message Length
    • Bad Message Type
    • Unspecified
  • Open Message Error
    • Unsupported Version
    • Bad Peer As
    • Bad BGP Identifier
    • Unsupported Optional Parameter
    • Authentication Failure
    • Unacceptable Hold Time
    • Unspecified
  • Update Message Error
    • Malformed Attribute List
    • Unrecognized Attribute
    • Missing Attribute
    • Attribute Flag Error
    • Attribute Length Error
    • Invalid Origin Attribute
    • Invalid NextHop Attribute
    • Optional Attribute Error
    • Invalid Network Field
    • Malformed AS Path
    • Unspecified
  • Hold Timer Expired
  • Finite State Machine Error
  • Cease
  • Unspecified

Notification Received

Refer to the description for Notification Sent.

Neighbor NLRI Negotiation

The state of the device’s NLRI negotiation with the neighbor. The states can include the following:

  • Peer negotiated IPv6 unicast capability.
  • Peer configured for IPv6 unicast routes.
  • Peer negotiated IPv4 unicast capability.
  • Peer negotiated IPv4 multicast capability.

TCP Connection state

The state of the connection with the neighbor. The connection can have one of the following states:

  • LISTEN - Waiting for a connection request.
  • SYN-SENT - Waiting for a matching connection request after having sent a connection request.
  • SYN-RECEIVED - Waiting for a confirming connection request acknowledgment after having both received and sent a connection request.
  • ESTABLISHED - Data can be sent and received over the connection. This is the normal operational state of the connection.
  • FIN-WAIT-1 - Waiting for a connection termination request from the remote TCP, or an acknowledgment of the connection termination request previously sent.
  • FIN-WAIT-2 - Waiting for a connection termination request from the remote TCP.
  • CLOSE-WAIT - Waiting for a connection termination request from the local user.
  • CLOSING - Waiting for a connection termination request acknowledgment from the remote TCP.
  • LAST-ACK - Waiting for an acknowledgment of the connection termination request previously sent to the remote TCP (which includes an acknowledgment of its connection termination request).
  • TIME-WAIT - Waiting for enough time to pass to be sure the remote TCP received the acknowledgment of its connection termination request.
  • CLOSED - There is no connection state.

Byte Sent

The number of bytes sent.

Byte Received

The number of bytes received.

Local host

The IPv6 address of the device.

Local port

The TCP port the RUCKUS device is using for the BGP4+ TCP session with the neighbor.

Remote host

The IPv6 address of the neighbor.

Remote port

The TCP port the neighbor is using for the BGP4+ TCP session with the device.

ISentSeq

The initial send sequence number for the session.

SendNext

The next sequence number to be sent.

TotUnAck

The number of sequence numbers sent by the device that have not been acknowledged by the neighbor.

TotSent

The number of sequence numbers sent to the neighbor.

ReTrans

The number of sequence numbers that the device retransmitted because they were not acknowledged.

UnAckSeq

The current acknowledged sequence number.

IRcvSeq

The initial receive sequence number for the session.

RcvNext

The next sequence number expected from the neighbor.

SendWnd

The size of the send window.

TotalRcv

The number of sequence numbers received from the neighbor.

DupliRcv

The number of duplicate sequence numbers received from the neighbor.

RcvWnd

The size of the receive window.

SendQue

The number of sequence numbers in the send queue.

RcvQue

The number of sequence numbers in the receive queue.

CngstWnd

The number of times the window has changed.

Examples

The following is sample output from the show ipv6 bgp neighbors command when no arguments or keywords are used.

device> show ipv6 bgp neighbors

    Total number of BGP Neighbors: 2
1   IP Address: 2001:1001::1, AS: 63753 (IBGP), RouterID: 1.0.0.1, VRF: default-vrf
       Description: SWD-2
    State: ESTABLISHED, Time: 0h47m50s, KeepAliveTime: 60, HoldTime: 180
       KeepAliveTimer Expire in 26 seconds, HoldTimer Expire in 168 seconds
    Minimal Route Advertisement Interval: 0 seconds
       MD5 Password: $Qj0tZHMlXC1vbjYt
       UpdateSource: Loopback 1
       NextHopSelf: yes
       RefreshCapability: Received
       GracefulRestartCapability: Received
           Restart Time 120 sec, Restart bit 0
           afi/safi 2/1, Forwarding bit 0
       GracefulRestartCapability: Sent
           Restart Time 120 sec, Restart bit 0
           afi/safi 2/1, Forwarding bit 0
    Messages:    Open    Update  KeepAlive Notification Refresh-Req
.....

The following is sample output from the show ipv6 bgp neighbors command when an IPv6 address is specified.

device> show ipv6 bgp neighbors 2001:db8:113:113::2

Total number of BGP Neighbors: 2
1   IP Address: 2001:db8:113:113::2, AS: 65001 (EBGP), RouterID: 0.0.0.0, VRF:
efault-vrf
    State: CONNECT, Time: 1d14h21m38s, KeepAliveTime: 60, HoldTime: 180
    Minimal Route Advertisement Interval: 0 seconds
    Messages:    Open    Update  KeepAlive Notification Refresh-Req
       Sent    : 1       0       0         1            0
       Received: 1       0       0         0            0
    Last Connection Reset Reason:Unknown
    Notification Sent:     Unspecified
    Notification Received: Unspecified
    Neighbor NLRI Negotiation:
      Peer configured for IPV6 unicast  Routes
    Neighbor AS4 Capability Negotiation:
    Outbound Policy Group:
       ID: 2, Use Count: 3
       Last update time was 123948 sec ago
    TCP Connection state: SYN-SENT
     Maximum segment size: 1440
    TTL check: value: 0
       Byte Sent:   0, Received: 0
       Local host: 2001:db8:113:113::1, Local  Port: 8014
       Remote host: 2001:db8:113:113::2, Remote Port: 179
       ISentSeq:   76022806  SendNext:   76022807  TotUnAck:          1
       TotSent:           1  ReTrans:           2  UnAckSeq:   76022806
       IRcvSeq:           0  RcvNext:           0  SendWnd:           1
       TotalRcv:          0  DupliRcv:          0  RcvWnd:        16384
       SendQue:           1  RcvQue:            0  CngstWnd:       1440
…
History