From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Wed Nov 30 2005 - 12:19:10 GMT-3
Gustavo -
Here is the routes at R4....
R4#sh ipv rou
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext
2
L FE80::/10 [0/0]
via ::, Null0
C FEC0::34:0/125 [0/0]
via ::, Serial0
L FEC0::34:4/128 [0/0]
via ::, Serial0
R FEC0::103:0/125 [120/2]
via FE80::3, Serial0
C FEC0::104:0/126 [0/0]
via ::, Loopback604
L FEC0::104:1/128 [0/0]
via ::, Loopback604
L FF00::/8 [0/0]
via ::, Null0
The ping running, while debug was on at the R4 did not produce any
output or errors. However, you gave me an idea to try a traceroute on R1
to the loop. Here is the output. It appears that it gets to R3, but
then gets lost.
R1#traceroute ipv6 fec0::104:1
Type escape sequence to abort.
Tracing the route to FEC0::104:1
1 FEC0::123:3 48 msec 44 msec 44 msec
2 * * *
3 * * *
4 * * *
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: Gustavo Novais [mailto:gustavo.novais@novabase.pt]
Sent: Wednesday, November 30, 2005 10:01 AM
To: Schulz, Dave
Subject: RE: IPv6 redistribution with RIP
Can you show the ipv6 routing table of R4? And do a deb ipv6 packet
while you are pinging from R1. If R4 does not have a route to R1 serial,
it would not know how to reply to it.
I think that your redistribution is being done one way only FRAME-34 to
FRAME-123, although I think you have it well configured.
Can you also post sh ipv6 protocols?
Gustavo Novais
-----Original Message-----
From: Schulz, Dave [mailto:DSchulz@dpsciences.com]
Sent: quarta-feira, 30 de Novembro de 2005 14:53
To: Gustavo Novais
Subject: RE: IPv6 redistribution with RIP
Thanks for the response. You are seeing the problem that I am
seeing....I see the route to it, but cannot ping it from R1. I CAN get
a good ping response to that 604 loopback at R3. I turned on the debug
routing and repeated the process and it does not give me any
encapsulation failures. R4 only has the single serial interface.
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: Gustavo Novais [mailto:gustavo.novais@novabase.pt]
Sent: Wednesday, November 30, 2005 9:42 AM
To: Schulz, Dave
Subject: RE: IPv6 redistribution with RIP
Hi Dave, not sure I understand your problem, as you posted R1 ipv6 RIB
with
R FEC0::104:0/126 [120/3]
via FE80::3, Serial0/0.123
You are not able to ping the R4 Loopback? Does it show encapsulation
failed when deb ipv6 packet?
Is R1 serial interface on R4's ipv6 RIB?
Do you have any other interface on IPV6 on R1?
Gustavo Novais
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Schulz, Dave
Sent: quarta-feira, 30 de Novembro de 2005 14:16
To: ccielab@groupstudy.com
Subject: IPv6 redistribution with RIP
Here is an issue that I am having with IPv6 redistribution.....I have 4
routers set up on two frame networks......
R1------------------R3(loop603------------------------R4 (loop604)
\------------R2(loop602)
I can see all the routes at R1, except the loop604 at R4 (however, I see
the route to it both in the RIB and rip database. I am redistributing
the route into rip at R4, and redistributing at R3 (understanding that
the loopback must still be redistributed if it is connected directly to
the router (under IPv6). I also tried to add the R4 directly into the
rip process as an internal route, but it still cannot be reached by R1.
At first, I thought this to be a split horizon issue (in rip), but when
it was turned off at R1, the issue continues to exist. Here are the
configs.....any direction would be appreciated......
---------------------------------------------
R1#
!
ipv6 unicast-routing
!
!
interface Serial0/0.123 multipoint
ip address 172.16.123.1 255.255.255.128
no ip split-horizon
ipv6 address FEC0::123:1/125
ipv6 address FE80::1 link-local
ipv6 rip FRAME-123 enable
frame-relay map ipv6 FE80::2 102 broadcast
frame-relay map ipv6 FE80::3 103 broadcast
frame-relay map ipv6 FEC0::123:2 102 broadcast
frame-relay map ipv6 FEC0::123:3 103 broadcast
frame-relay map ip 172.16.123.1 102
frame-relay map ip 172.16.123.2 102 broadcast
frame-relay map ip 172.16.123.3 103 broadcast
no frame-relay inverse-arp
!
router rip
version 2
redistribute eigrp 200
passive-interface default
no passive-interface Serial0/0.123
network 172.16.0.0
neighbor 172.16.123.3
neighbor 172.16.123.2
default-metric 2
no auto-summary
!
ipv6 router rip FRAME-123
!
-----------------------------------------------------
R3#
!
ipv6 unicast-routing
!
interface Loopback603
no ip address
ipv6 address FEC0::103:1/125
ipv6 rip FRAME-34 enable
!
interface Serial0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
frame-relay lmi-type ansi
!
interface Serial0.2 multipoint
ip address 172.16.123.3 255.255.255.128
ipv6 address FEC0::123:3/125
ipv6 address FE80::3 link-local
ipv6 rip FRAME-123 enable
frame-relay map ipv6 FE80::2 301
frame-relay map ipv6 FEC0::123:1 301 broadcast
frame-relay map ipv6 FEC0::123:2 301
frame-relay map ip 172.16.123.1 301 broadcast
frame-relay map ip 172.16.123.2 301
frame-relay map ip 172.16.123.3 301
frame-relay map ipv6 FE80::1 301 broadcast
no frame-relay inverse-arp
!
interface Serial0.4 point-to-point
ip address 172.16.34.3 255.255.255.128
ipv6 address FEC0::34:3/125
ipv6 address FE80::3 link-local
ipv6 rip FRAME-34 enable
frame-relay interface-dlci 304
!
!
ipv6 router rip FRAME-34
redistribute connected metric 3 route-map Lv6
redistribute rip FRAME-123 metric 2
!
ipv6 router rip FRAME-123
redistribute connected metric 3 route-map Lv6
redistribute rip FRAME-34 metric 2
!
!
route-map Lv6 permit 10
match interface Loopback603
!
----------------------------------------------------------------
R4#
!
ipv6 unicast-routing
!
interface Loopback604
no ip address
ipv6 address FEC0::104:1/126
!
interface Serial0
ip address 172.16.34.4 255.255.255.128
encapsulation frame-relay
ipv6 address FEC0::34:4/125
ipv6 address FE80::4 link-local
ipv6 rip FRAME-34 enable
frame-relay map ipv6 FE80::3 403 broadcast
frame-relay map ip 172.16.34.3 403 broadcast
frame-relay map ipv6 FEC0::34:3 403 broadcast
no frame-relay inverse-arp
frame-relay lmi-type ansi
!
ipv6 router rip FRAME-34
redistribute connected metric 3 route-map Lv6
!
route-map Lv6 permit 10
match interface Loopback604
!
R1 (sh ipv6 route).......
R1#sh ipv rou
IPv6 Routing Table - 11 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS
summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext
2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
L FE80::/10 [0/0]
via ::, Null0
C FEC0::101:0/125 [0/0]
via ::, Loopback601
L FEC0::101:1/128 [0/0]
via ::, Loopback601
R FEC0::102:0/125 [120/4]
via FE80::2, Serial0/0.123
R FEC0::103:0/125 [120/4]
via FE80::3, Serial0/0.123
R FEC0::104:0/126 [120/3]
via FE80::3, Serial0/0.123
C FEC0::122:0/125 [0/0]
via ::, FastEthernet0/0.30
L FEC0::122:1/128 [0/0]
via ::, FastEthernet0/0.30
C FEC0::123:0/125 [0/0]
via ::, Serial0/0.123
L FEC0::123:1/128 [0/0]
via ::, Serial0/0.123
L FF00::/8 [0/0]
via ::, Null0
Dave Schulz,
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com >
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:08 GMT-3