Configuration Guide Vol. 3


29.6.12 Checking the limit on the number of BGP4 + learned routes

<Structure of this section>

(1) List of operation commands

The following tables list the operation commands for limiting the number of BGP4 + learned routes.

Table 29-30: List of operation commands

Command name

Description

show ipv6 route

Displays routing information stored in the routing table.

show ipv6 bgp

Shows information about the BGP4+ protocol.

clear ipv6 bgp

Reconnects a peer that was disconnected because it exceeded the maximum number of BGP4+ routes that can be learned from a particular device.

(2) Checking the limit on the number of BGP4 + learned routes and the number of routes learned from peers

To check the allowable maximum and the actual number of BGP4+ routes (sum of the active and inactive paths) learned from a particular peer, use the show ipv6 bgp operation command with the neighbors parameter and an <As>, a <Peer Address>, or a <Host name> argument or the detail parameter specified.

Figure 29-41: Result of executing show ipv6 bgp command (specifying neighbors,detail parameter)
>show ipv6 bgp neighbors detail
 Date 20XX/01/13 18:45:09
 BGP4+ Peer: 3ffe:172:16:2::2, Remote AS: 65532
 Remote Router ID: 172.16.2.200
     BGP4+ Status:Idle               HoldTime: 90  , Keepalive: 60
     Established Transitions: 1      Established Date: 20XX/01/13 18:42:26..1
     BGP4+ Version: 4                Type: External
     Local Address: 3ffe:172:16:23::214
     Local AS: 65531                 Local Router ID: 172.16.2.100
     Next Connect Retry: 00:32,      Connect Retry Timer: 00:32
     Last Keep Alive Sent: 18:42:20, Last Keep Alive Received: 18:42:20
     BGP4+ Message  UpdateIn UpdateOut TotalIn TotalOut
                    12       14        36      42
     BGP4+ Peer Last Error: Cease(Over Prefix Limit)                      ..2
     BGP4+ Routes  Accepted     MaximumPrefix RestartTime Threshold       ..3
                   0            1000          60m         80%
     BGP4+ Capability Negotiation: <IPv6-Uni>
       Send   : <IPv6-Uni>
       Receive: <IPv6-Uni>
     Password : Configured
 BGP4+ Peer: 3ffe:192:168:2::1, Remote AS: 65531
 Remote Router ID: 192.168.2.200
     BGP4+ Status:Active             HoldTime: 90  , Keepalive: 60
     Established Transitions: 1      Established Date: 20XX/01/13 18:42:31
     BGP4+ Version: 4                Type: Internal
     Local Address: 3ffe:192:168:23::214
     Local AS: 65531                 Local Router ID: 192.168.2.100
     Next Connect Retry: 00:32,      Connect Retry Timer: 00:32
     Last Keep Alive Sent: 18:44:31, Last Keep Alive Received: 18:44:31
     BGP4+ Message  UpdateIn UpdateOut TotalIn TotalOut
                    12       14        36      42
     BGP4+ Routes  Accepted     MaximumPrefix RestartTime Threshold       ..4
                   94           1000          none        75%
     BGP4+ Capability Negotiation: <IPv6-Uni>
       Send   : <IPv6-Uni>
       Receive: <IPv6-Uni>
     Password : Configured
  1. The peer is disconnecting from 20XX/01/13 18:42:26.

  2. The peer was disconnected because it exceeded the maximum number of learned routes.

  3. The disconnected peer was reconnected after 60 minutes.

  4. Of the allowable maximum of 1000 routes, the peer has learned 94 routes from the specified peer.

(3) Reconnecting BGP4+ sessions disconnected due to the limit on the number of learned routes

BGP4+ sessions that are disconnected because the number of learned routes exceeds the upper limit due to the limit on the number of learned routes are reconnected by specifying the * or <Peer Address>, <Host Name> parameter in the operation command clear ipv6 bgp.

Reconnection of a BGP4+ session by using the command

  1. # clear ipv6 bgp 3ffe:172:16:2::2

    Reconnects the BGP4+ session with remote peer address 3ffe:172:16:2::2, which was disconnected after exceeding the learned routes limit.