[c-nsp] IPv6 in IPv4 BGP?
Hank Nussbacher
hank at efes.iucc.ac.il
Mon Mar 6 14:53:10 EST 2006
On a 12.2(18)SXE4:
petach-tikva-gp#sho bgp ipv4 unic sum
BGP table version is 18169678, main routing table version 18169678
181641 network entries using 20707074 bytes of memory
181718 path entries using 8722464 bytes of memory
33235/32720 BGP path/bestpath attribute entries using 3323500 bytes of
memory
30194 BGP AS-PATH entries using 807876 bytes of memory
430 BGP community entries using 21846 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 33582760 total bytes of memory
Dampening enabled. 0 history paths, 0 dampened paths
2 received paths for inbound soft reconfiguration
BGP activity 1723355/1541139 prefixes, 2770529/2588221 paths, scan
interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
2001:798:1D:10AA::1
4 20965 19 20 0 0 0 03:10:44 Active
...
Huh? An IPv6?
petach-tikva-gp#sho bgp ipv6 unicas sum
BGP table version is 4, main routing table version 4
534 network entries using 77430 bytes of memory
534 path entries using 38448 bytes of memory
33230/1 BGP path/bestpath attribute entries using 3323000 bytes of memory
30191 BGP AS-PATH entries using 807688 bytes of memory
430 BGP community entries using 21846 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 4268412 total bytes of memory
Dampening enabled. 0 history paths, 0 dampened paths
BGP activity 1723363/1541147 prefixes, 2770571/2588260 paths, scan
interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
2001:798:1D:10AA::1
4 20965 19 20 0 0 0 03:14:21 Active
2001:BF8::1 4 378 499 7 0 0 0 08:59:09 Active
2001:BF8::4 4 378 0 0 0 0 0 never Active
2001:BF8:0:3:230:B6FF:FE56:601B
4 378 449 449 4 0 0 07:25:37
0
2001:BF8:0:B::2 4 378 1197 542 4 0 0 08:58:40
534
Is this normal or a bug? Peer 2001:798:1D:10AA::1 pops up in IPv4 and
IPv6 output.
Thanks,
Hank
More information about the cisco-nsp
mailing list