Configuration Guide Vol. 3


29.6.4 Verifying Support Feature Negotiation

<Structure of this section>

(1) List of operation commands

The following table lists the operation commands related to the negotiation of support functions.

Table 29-22: List of operation commands

Command name

Description

show ipv6 bgp

Shows information about the BGP4+ protocol.

(2) Verifying Negotiation

To display the result of capability negotiation, use the show ipv6 bgp operation command with the neighbors and detail parameters specified.

Figure 29-26: Result of executing show ipv6 bgp command (specifying neighbors detail parameter)
> show ipv6 bgp neighbors detail
Date 20XX/10/17 15:52:14 UTC
BGP4+ Peer: 3ffe:10:1:2::2     , Remote AS: 65531 
Remote Router ID: 10.1.2.102
    BGP4+ Status: Established       HoldTime: 180  , Keepalive: 60
    Established Transitions: 1      Established Date: 20XX/10/17 15:51:00
    BGP4+ Version: 4                Type: Internal
    Local Address: 3ffe:10:1:2::1
    Local AS: 65531                 Local Router ID: 192.168.1.100
    Next Connect Retry: -           Connect Retry Timer: - 
    Last Keep Alive Sent: 15:52:00  Last Keep Alive Received: 15:52:00
    BGP4+ Message  UpdateIn   UpdateOut  TotalIn    TotalOut
                   0          0          2          4
    BGP4+ Capability Negotiation: <IPv6-Uni Refresh Refresh(v)>            ..1
      Send   : <IPv6-Uni Refresh Refresh(v)> 
      Receive: <IPv6-Uni Refresh Refresh(v)>
    Password: UnConfigured
BGP4+ Peer: 3ffe:192:168:2::2   , Remote AS: 65531
Remote Router ID: 192.168.1.102
    BGP4+ Status: Established       HoldTime: 180  , Keepalive: 60
    Established Transitions: 1      Established Date: 20XX/10/17 15:50:43
    BGP4+ Version: 4                Type: Internal
    Local Address:3ffe:192:168:2::1
    Local AS: 65531                 Local Router ID: 192.168.1.100
    Next Connect Retry: -           Connect Retry Timer: -
    Last Keep Alive Sent: 15:51:43  Last Keep Alive Received: 15:51:43
    BGP4+ Message  UpdateIn   UpdateOut  TotalIn    TotalOut
                   0          0          2          4
    BGP4+ Capability Negotiation: <IPv6-Uni Refresh>                       ..2
      Send   : <IPv6-Uni Refresh Refresh(v)>
      Receive: <IPv6-Uni Refresh >
    Password: UnConfigured
BGP4+ Peer: 3ffe:10:2:2::2       , Remote AS: 65533
Remote Router ID: 10.2.2.102
    BGP4+ Status: Established       HoldTime: 180  , Keepalive: 60
    Established Transitions: 1      Established Date: 20XX/10/17 15:50:30
    BGP4+ Version: 4                Type: External
    Local Address: 10.1.2.1
    Local AS: 65531                 Local Router ID: 192.168.1.100
    Next Connect Retry: -           Connect Retry Timer: -
    Last Keep Alive Sent: 15:51:30  Last Keep Alive Received: 15:51:30
    BGP4+ Message  UpdateIn   UpdateOut  TotalIn    TotalOut
                   0          0          2          4
    BGP4+ Capability Negotiation: <IPv6-Uni>                               ..3
      Send   : <IPv6-Uni Refresh Refresh(v)>
      Receive: <IPv6-Uni>
    Password: UnConfigured
BGP4+ Peer: 3ffe:172:16:2::2   , Remote AS: 65532
Remote Router ID: 172.16.1.102
    BGP4+ Status: Established       HoldTime: 180  , Keepalive: 60
    Established Transitions: 1      Established Date: 20XX/10/17 15:49:35
    BGP4+ Version: 4                Type: External
    Local Address:3ffe:172:16:2::1
    Local AS: 65531                 Local Router ID: 192.168.1.100
    Next Connect Retry: -           Connect Retry Timer: -
    Last Keep Alive Sent: 15:51:35  Last Keep Alive Received: 15:51:35
    BGP4+ Message  UpdateIn   UpdateOut  TotalIn    TotalOut
                   0          0          3          5
    BGP4+ Capability Negotiation: <>                                       ..4
      Send   : <IPv6-Uni Refresh Refresh(v)>
      Receive: <>
    Password: UnConfigured
>
  1. The following capabilities were successfully negotiated: IPv6-Uni: IPv6 unicast routing; Refresh: Route refresh capability (RFC 2918-compliant); and Refresh(v): Route refresh capability (Capability Code: 128).

  2. The following capabilities were successfully negotiated: IPv6-Uni: IPv6 unicast routing; and Refresh: Route refresh capability (RFC 2918-compliant).

  3. The following capability was successfully negotiated: IPv6-Uni: IPv6 unicast routing.

  4. Capabilities were not successfully negotiated.