29.6.7 Checking the generation of BGP4 + advertised routes

<Structure of this section>

(1) List of operation commands

The following tables list the operation commands for creating BGP4 + advertised routes.

Table 29-25: List of operation commands
Command name	Description
show ipv6 bgp	Shows information about the BGP4+ protocol.
show ipv6 route	Displays routing information stored in the routing table.

(2) Checking BGP4 + advertised routes

(a) Displaying generated advertised routes

To display generated BGP4+ advertised routes, use the show ipv6 bgp operation command. In the following example, 3ffe:173:16::/48 and 3ffe:192:169:10::/64 are generated BGP4+ advertised routes.

Figure 29-31: Result of executing show ipv6 bgp command
> show ipv6 bgp Date 20XX/10/20 22:43:26 UTC Local AS: 65531, Local Router ID: 192.168.1.100 Status Codes: d dampened, * valid, > active, S Stale, r RIB failure Origin Codes: i - IGP, e - EGP, ? - incomplete Network Next Hop MED LocalPref Weight Path * 3ffe:173:16::/48 ---- - 100 0 i * 3ffe:192:169:10::/64 ---- - 100 0 i

Figure 29-31: Result of executing show ipv6 bgp command

> show ipv6 bgp
Date 20XX/10/20 22:43:26 UTC
Local AS: 65531, Local Router ID: 192.168.1.100
Status Codes: d dampened, * valid, > active, S Stale, r RIB failure
Origin Codes: i - IGP, e - EGP, ? - incomplete
   Network                  Next Hop        MED    LocalPref Weight Path
*  3ffe:173:16::/48         ----            -      100       0      i
*  3ffe:192:169:10::/64     ----            -      100       0      i

(b) Displaying advertised routes

To check whether a generated BGP4+ advertised route has been advertised, use the show ipv6 bgp operation command with the advertised-routes parameter specified.

Figure 29-32: Result of executing show ipv6 bgp command (specifying advertised-routes parameter)
> show ipv6 bgp advertised-routes 3ffe:173:16::/48 Date 20XX/10/29 18:08:54 UTC BGP4+ Peer: 3ffe:172:16:2::2, Remote AS: 65532 Local AS: 65531, Local Router ID: 192.168.1.100 Status Codes: * valid, > active Route 3ffe:173:16::/48 * Next Hop ---- MED: -, LocalPref: -, Type: Internal route Origin: IGP Path:65531 Next Hop Attribute: 3ffe:172:16:2::1 > show ipv6 bgp advertised-routes 3ffe:192:169:10::/64 Date 20XX/10/29 18:08:54 UTC BGP4+ Peer: 3ffe:172:16:2::2, Remote AS: 65532 Local AS: 65531, Local Router ID: 192.168.1.100 Status Codes: * valid, > active Route 3ffe: 3ffe:192:169:10::/64 * Next Hop ---- MED: -, LocalPref: -, Type: Internal route Origin: IGP Path:65531 Next Hop Attribute: 3ffe:172:16:2::1

Figure 29-32: Result of executing show ipv6 bgp command (specifying advertised-routes parameter)

> show ipv6 bgp advertised-routes 3ffe:173:16::/48
Date 20XX/10/29 18:08:54 UTC
BGP4+ Peer: 3ffe:172:16:2::2, Remote AS: 65532
Local AS: 65531, Local Router ID: 192.168.1.100
Status Codes: * valid, > active
Route 3ffe:173:16::/48
*  Next Hop ----
     MED: -, LocalPref: -,   Type: Internal route
     Origin: IGP
     Path:65531
     Next Hop Attribute: 3ffe:172:16:2::1
 
> show ipv6 bgp advertised-routes 3ffe:192:169:10::/64
Date 20XX/10/29 18:08:54 UTC
BGP4+ Peer: 3ffe:172:16:2::2, Remote AS: 65532
Local AS: 65531, Local Router ID: 192.168.1.100
Status Codes: * valid, > active
Route 3ffe: 3ffe:192:169:10::/64
*  Next Hop ----
     MED: -, LocalPref: -, Type: Internal route
     Origin: IGP
     Path:65531
     Next Hop Attribute: 3ffe:172:16:2::1