From: Darrin K. Pierce (darrin@dkpierce.com)
Date: Fri Feb 23 2007 - 00:07:32 ART
I don't believe that a BVI supports IPv6. I'd try to put it through a GRE
tunnel!
Darrin
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of John
Aitken
Sent: Thursday, February 22, 2007 5:18 PM
To: Cisco certification
Subject: I.E. Lab 16 IPv6 (7.4)
Guys,
Can anyone explain to me why this isn't working?
R2 FE0/0 is connected to BB2 E0, speaking IPv6 rip and sending IPv6 RIP
routes to BB2, which is seeing and installing them in it's route tables.
R2 FE0/0 is part of a bridge group (Not in use for this section). If I put
the config on the BVI interface I don't recieve any IPv6 RIP routes from BB2
. If I put the IPv6 config on the fastethernet I get exactly exactly the
same results (In the answer key the config is on the fastethernet, not the
BVI).
If I remove the interface from the bridge group it all springs into life, if
I re add it then same again. Rebooted also to see if that fixed anything.
Have the following config on R2:
interface BVI1
ip address 192.10.1.2 255.255.255.0
ipv6 address 2001:192:10:1::/64 eui-64
ipv6 rip RIPng enable
end
or alternately (Removing from FA0/0):
interface FastEthernet0/0
no ip address
ipv6 address 2001:192:10:1::/64 eui-64
ipv6 rip RIPng enable
bridge-group 1
end
On BB2 it's:
interface Ethernet0
ip address 192.10.1.254 255.255.255.0
ipv6 address 2001:192:10:1::254/64
ipv6 rip RIPng enable
end
!
ipv6 router rip RIPng
distribute-list prefix-list RIPng out
!
ipv6 prefix-list RIPng seq 5 permit 2001:205:90:31::/64
ipv6 prefix-list RIPng seq 10 permit 2001:220:20:3::/64
ipv6 prefix-list RIPng seq 15 permit 2001:222:22:2::/64
(These are the routes I'm expecting to see)
Some debugs:
R2 (BVI)
*May 11 14:37:57.167: RIPng: Sending multicast update on BVI1 for RIPng
*May 11 14:37:57.167: src=FE80::20D:BDFF:FE27:5C20
*May 11 14:37:57.167: dst=FF02::9 (BVI1)
*May 11 14:37:57.167: sport=521, dport=521, length=112
*May 11 14:37:57.167: command=2, version=1, mbz=0, #rte=5
*May 11 14:37:57.167: tag=0, metric=1, prefix=2001:CC1E:1::2/128
*May 11 14:37:57.167: tag=0, metric=1, prefix=2001:CC1E:1:25::/64
*May 11 14:37:57.167: tag=0, metric=1, prefix=2001:192:10:1::/64
*May 11 14:37:57.167: tag=0, metric=2, prefix=2001:CC1E:1::5/128
*May 11 14:37:57.171: tag=0, metric=2, prefix=2001:CC1E:1:5::/64
R2 (fa0/0)
*May 11 14:31:31.979: RIPng: Sending multicast update on FastEthernet0/0 for
RIPng
*May 11 14:31:31.979: src=FE80::20D:BDFF:FE27:5C20
*May 11 14:31:31.979: dst=FF02::9 (FastEthernet0/0)
*May 11 14:31:31.979: sport=521, dport=521, length=112
*May 11 14:31:31.979: command=2, version=1, mbz=0, #rte=5
*May 11 14:31:31.979: tag=0, metric=1, prefix=2001:CC1E:1::2/128
*May 11 14:31:31.979: tag=0, metric=1, prefix=2001:192:10:1::/64
*May 11 14:31:31.979: tag=0, metric=1, prefix=2001:CC1E:1:25::/64
*May 11 14:31:31.979: tag=0, metric=2, prefix=2001:CC1E:1::5/128
*May 11 14:31:31.983: tag=0, metric=2, prefix=2001:CC1E:1:5::/64
(Never recieve any from BB2)
BB2
Mar 1 00:31:40.559: RIPng: Output filter suppresses 2001:192:10:1::/64
Mar 1 00:31:40.563: RIPng: Sending multicast update on Ethernet0 for RIPng
Mar 1 00:31:40.567: src=FE80::2E0:1EFF:FE67:F6EB
Mar 1 00:31:40.571: dst=FF02::9 (Ethernet0)
Mar 1 00:31:40.571: sport=521, dport=521, length=72
Mar 1 00:31:40.575: command=2, version=1, mbz=0, #rte=3
Mar 1 00:31:40.575: tag=0, metric=1, prefix=2001:205:90:31::/64
Mar 1 00:31:40.579: tag=0, metric=1, prefix=2001:220:20:3::/64
Mar 1 00:31:40.583: tag=0, metric=1, prefix=2001:222:22:2::/64
Mar 1 00:31:40.587: RIPng: Output filter suppresses 2001:192:10:1::/64
Mar 1 00:31:40.591: RIPng: Output filter suppresses 2001:CC1E:1::2/128
Mar 1 00:31:40.595: RIPng: Output filter suppresses 2001:CC1E:1::5/128
Mar 1 00:31:40.595: RIPng: Output filter suppresses 2001:CC1E:1:5::/64
Mar 1 00:31:40.599: RIPng: Output filter suppresses 2001:CC1E:1:25::/64
Mar 1 00:31:40.603: RIPng:
Mar 1 00:31:45.723: RIPng: response received from FE80::20D:BDFF:FE27:5C20
on Ethernet0 for RIPng
Mar 1 00:31:45.727: src=FE80::20D:BDFF:FE27:5C20 (Ethernet0)
Mar 1 00:31:45.731: dst=FF02::9
Mar 1 00:31:45.731: sport=521, dport=521, length=112
Mar 1 00:31:45.735: command=2, version=1, mbz=0, #rte=5
Mar 1 00:31:45.735: tag=0, metric=1, prefix=2001:CC1E:1::2/128
Mar 1 00:31:45.739: tag=0, metric=1, prefix=2001:CC1E:1:25::/64
Mar 1 00:31:45.743: tag=0, metric=1, prefix=2001:192:10:1::/64
Mar 1 00:31:45.747: tag=0, metric=2, prefix=2001:CC1E:1:5::/64u
FRS-BB2#u all
Mar 1 00:31:45.747: tag=0, metric=2, prefix=2001:CC1E:1::5/128
Am I just banging my head against a bug or am I missing something blindingly
obvious?
This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:47 ART