IPv6 design, deployment, standards, and best practices.
timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

silly ipv6 problem !

Sat Aug 06, 2011 9:48 am

i worked with IPv6 in GNS many times and have not had any problem with it. but today i want to do it in real gears. i connect the devices like this:
cat3550 ---R1---R2.

i assigned the ipv4 and ipv6 addresses to respective interfaces on shown devices. i entered the "ipv6 unicast-routing" on every devices. i have ipv4 reachibility between "connected devices" but not ipv6 reachibility. i means, for example, i assigned the 1001::1/64 to cat 3550, then 1001::2/64 to R1. but the ping is unsuccessful. even i did it between R1 and R2 and again ping is unsuccessful. is there any difference between GNS and real devices in the case of ipv6? ... what is this silly problem? i am confused. tnx
timaz mohsenzadeh

User avatar
mellowd
CCIE #38070
Posts:
13814
Joined:
Wed Jun 18, 2008 7:49 am
Certs:
CCIE (RS,SP), JNCIE-SP, BC-/SPNE/NP

Re: silly ipv6 problem !

Sat Aug 06, 2011 10:02 am

do a show ipv6 route on all devices and paste the output here in code tags

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Sat Aug 06, 2011 10:15 am

there is no problem with that. actually the output of this command does show the "L" and "C" routes in the table. but the problem is that the routers don't ping the connected networks.
timaz mohsenzadeh

User avatar
mellowd
CCIE #38070
Posts:
13814
Joined:
Wed Jun 18, 2008 7:49 am
Certs:
CCIE (RS,SP), JNCIE-SP, BC-/SPNE/NP

Re: silly ipv6 problem !

Sat Aug 06, 2011 10:25 am

I asked because I want to see it

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Sun Aug 07, 2011 12:17 pm

sw1(config)#do sh ipv6 route
IPv6 Routing Table - Default - 3 entries

C 1001::/64 [0/0]
via FastEthernet0/1, directly connected
L 1001::1/128 [0/0]
via FastEthernet0/1, receive
L FF00::/8 [0/0]
via Null0, receive

-----------------------------------------------

r2(config)#do sh ipv6 route
IPv6 Routing Table - Default - 3 entries

C 1002::/64 [0/0]
via Serial0/0/0.201, directly connected
L 1002::2/128 [0/0]
via Serial0/0/0.201, receive
L FF00::/8 [0/0]
via Null0, receive

---------------------------------------------------

r1(config)#do sh ipv6 route
IPv6 Routing Table - 5 entries

C 1001::/64 [0/0]
via ::, FastEthernet0/0
L 1001::2/128 [0/0]
via ::, FastEthernet0/0
C 1002::/64 [0/0]
via ::, Serial0/0
L 1002::1/128 [0/0]
via ::, Serial0/0
L FF00::/8 [0/0]
via ::, Null0

besides, i use this IOS on routers:

c3550-ipservicesk9-mz.122-44.SE.bin

C2600-ADVENTERPRISEK9-M), Version 12.4(15)T7

c1800-adventerprisek9-124-24t.bin
also, i have issued "ipv6 unicast-routing" on all of routers.
timaz mohsenzadeh

User avatar
routerdork
Post Whore
Posts:
1497
Joined:
Tue Feb 22, 2011 9:40 am
Certs:
CCNA, MCDST, MCP, A+

Re: silly ipv6 problem !

Sun Aug 07, 2011 12:30 pm

Can you ping the IPv6 addresses on the local routers?

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Sun Aug 07, 2011 12:31 pm

yes. i do. besides, the command "sh ipv6 neighbors" does not reveal any output on any routers.
timaz mohsenzadeh

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Mon Aug 08, 2011 12:12 pm

i have issued the "debug ipv6 packet" and i'm going to paste the out put here. i tested IPv6 in this simple topology:

sw1 (1000::1/64)-----------(1000::2/64)r1

------------------------------------------------------

r1#debug ipv6 packet
IPv6 unicast packet debugging is on
r1#
r1#ping 1000::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1000::1, timeout is 2 seconds:

*Mar 1 00:41:44.273: IPv6: SAS picked source 1000::2 for 1000::1 (FastEthernet0/0)
*Mar 1 00:41:44.273: IPV6: source 1000::2 (local)
*Mar 1 00:41:44.273: dest 1000::1 (FastEthernet0/0)
*Mar 1 00:41:44.273: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:41:44.277: IPV6: source 1000::2 (local)
*Mar 1 00:41:44.277: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:44.277: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:44.277: IPv6: Sending on FastEthernet0/0
*Mar 1 00:41:44.277: IPv6: Encapsulation failed
*Mar 1 00:41:44.277: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0
*Mar 1 00:41:44.281: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0
*Mar 1 00:41:45.279: IPV6: source 1000::2 (local)
*Mar 1 00:41:45.279: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:45.279: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:45.279: IPv6: Sending on FastEthernet0/0.
*Mar 1 00:41:46.280: IPV6: source 1000::2 (local)
*Mar 1 00:41:46.280: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:46.280: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:46.280: IPv6: Sending on FastEthernet0/0
*Mar 1 00:41:46.284: IPv6: SAS picked source 1000::2 for 1000::1 (FastEthernet0/0)
*Mar 1 00:41:46.284: IPV6: source 1000::2 (local)
*Mar 1 00:41:46.284: dest 1000::1 (FastEthernet0/0)
*Mar 1 00:41:46.284: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:41:46.284: IPv6: Encapsulation failed
*Mar 1 00:41:46.284: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0
*Mar 1 00:41:46.288: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0.
*Mar 1 00:41:48.288: IPv6: SAS picked source 1000::2 for 1000::1 (FastEthernet0/0)
*Mar 1 00:41:48.288: IPV6: source 1000::2 (local)
*Mar 1 00:41:48.288: dest 1000::1 (FastEthernet0/0)
*Mar 1 00:41:48.288: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:41:48.292: IPV6: source 1000::2 (local)
*Mar 1 00:41:48.292: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:48.292: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:48.292: IPv6: Sending on FastEthernet0/0
*Mar 1 00:41:48.292: IPv6: Encapsulation failed
*Mar 1 00:41:48.292: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0
*Mar 1 00:41:48.292: IPv6: Resolving next hop 1000::1 on interface FastEthernet0/0
*Mar 1 00:41:49.289: IPV6: source 1000::2 (local)
*Mar 1 00:41:49.289: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:49.289: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:49.289: IPv6: Sending on FastEthernet0/0.
*Mar 1 00:41:50.291: IPV6: source 1000::2 (local)
*Mar 1 00:41:50.291: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:50.291: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:50.291: IPv6: Sending on FastEthernet0/0
*Mar 1 00:41:50.299: IPv6: SAS picked source 1000::2 for 1000::1 (FastEthernet0/0)
*Mar 1 00:41:50.299: IPV6: source 1000::2 (local)
*Mar 1 00:41:50.299: dest 1000::1 (FastEthernet0/0)
*Mar 1 00:41:50.299: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
Success rate is 0 percent (0/5)
r1#
*Mar 1 00:41:54.309: IPV6: source 1000::2 (local)
*Mar 1 00:41:54.309: dest FF02::1:FF00:1 (FastEthernet0/0)
*Mar 1 00:41:54.309: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:41:54.309: IPv6: Sending on FastEthernet0/0
r1#

--------------------------------------------

sw1#ping 1000::2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1000::2, timeout is 2 seconds:

*Mar 1 00:11:41.315: IPv6: SAS picked source 1000::1 for 1000::2 (FastEthernet0/1)
*Mar 1 00:11:41.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:41.315: dest 1000::2 (FastEthernet0/1)
*Mar 1 00:11:41.315: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:11:41.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:41.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:41.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:41.315: IPv6: Sending on FastEthernet0/1
*Mar 1 00:11:41.315: IPv6: Resolving next hop 1000::2 on interface FastEthernet0/1
*Mar 1 00:11:41.315: IPv6: Encapsulation postponed, performing resolution
*Mar 1 00:11:42.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:42.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:42.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:42.315: IPv6: Sending on FastEthernet0/1.
*Mar 1 00:11:43.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:43.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:43.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:43.315: IPv6: Sending on FastEthernet0/1
*Mar 1 00:11:43.315: IPv6: SAS picked source 1000::1 for 1000::2 (FastEthernet0/1)
*Mar 1 00:11:43.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:43.315: dest 1000::2 (FastEthernet0/1)
*Mar 1 00:11:43.315: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:11:43.315: IPv6: Resolving next hop 1000::2 on interface FastEthernet0/1
*Mar 1 00:11:43.315: IPv6: Encapsulation postponed, performing resolution.
*Mar 1 00:11:45.315: IPv6: SAS picked source 1000::1 for 1000::2 (FastEthernet0/1)
*Mar 1 00:11:45.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:45.315: dest 1000::2 (FastEthernet0/1)
*Mar 1 00:11:45.315: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:11:45.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:45.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:45.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:45.315: IPv6: Sending on FastEthernet0/1
*Mar 1 00:11:45.315: IPv6: Resolving next hop 1000::2 on interface FastEthernet0/1
*Mar 1 00:11:45.315: IPv6: Encapsulation postponed, performing resolution
*Mar 1 00:11:46.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:46.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:46.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:46.315: IPv6: Sending on FastEthernet0/1.
*Mar 1 00:11:47.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:47.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:47.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:47.315: IPv6: Sending on FastEthernet0/1
*Mar 1 00:11:47.315: IPv6: SAS picked source 1000::1 for 1000::2 (FastEthernet0/1)
*Mar 1 00:11:47.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:47.315: dest 1000::2 (FastEthernet0/1)
*Mar 1 00:11:47.315: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
*Mar 1 00:11:47.315: IPv6: Resolving next hop 1000::2 on interface FastEthernet0/1
*Mar 1 00:11:47.315: IPv6: Encapsulation postponed, performing resolution.
*Mar 1 00:11:49.315: IPv6: SAS picked source 1000::1 for 1000::2 (FastEthernet0/1)
Success rate is 0 percent (0/5)
sw1#
*Mar 1 00:11:51.315: IPV6: source 1000::1 (local)
*Mar 1 00:11:51.315: dest FF02::1:FF00:2 (FastEthernet0/1)
*Mar 1 00:11:51.315: traffic class 224, flow 0x0, len 72+8, prot 58, hops 255, originating
*Mar 1 00:11:51.315: IPv6: Sending on FastEthernet0/1
sw1#

-------------------------------------------------------------

r1(config-if)#ipv6 add 2000::2/64
r1(config-if)#
*Mar 1 00:44:44.769: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:44.769: dest FF02::16 (Serial0/0)
*Mar 1 00:44:44.773: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originating
*Mar 1 00:44:44.773: IPv6: Encapsulation failed
*Mar 1 00:44:44.773: IPv6: Resolving next hop FF02::16 on interface Serial0/0
*Mar 1 00:44:44.773: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:44.773: dest FF02::16 (Serial0/0)
*Mar 1 00:44:44.777: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originating
*Mar 1 00:44:44.777: IPv6: Encapsulation failed
r1(config-if)#
r1(config-if)#
r1(config-if)#
r1(config-if)#
*Mar 1 00:44:44.777: IPv6: Resolving next hop FF02::16 on interface Serial0/0
*Mar 1 00:44:44.781: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:44.781: dest FF02::16 (Serial0/0)
*Mar 1 00:44:44.781: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originating
*Mar 1 00:44:44.781: IPv6: Encapsulation failed
*Mar 1 00:44:44.781: IPv6: Resolving next hop FF02::16 on interface Serial0/0
*Mar 1 00:44:45.101: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:45.101: dest FF02::16 (Serial0/0)
*Mar 1 00:44:45.101: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originating
*Mar 1 00:44:45.101: IPv6: Encapsulation failed
*Mar 1 00:44:45.101: IPv6: Resolving next hop FF02::16 on interface Serial0/0
*Mar 1 00:44:45.105: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:45.105: dest FF02::16 (Serial0/0)
*Mar 1 00:44:45.105: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originatin
r1(config-if)#g
*Mar 1 00:44:45.105: IPv6: Encapsulation failed
*Mar 1 00:44:45.105: IPv6: Resolving next hop FF02::16 on interface Serial0/0
*Mar 1 00:44:45.598: IPV6: source FE80::211:BBFF:FE34:45A0 (local)
*Mar 1 00:44:45.598: dest FF02::16 (Serial0/0)
*Mar 1 00:44:45.598: traffic class 224, flow 0x0, len 76+0, prot 0, hops 1, originating
*Mar 1 00:44:45.598: IPv6: Encapsulation failed
*Mar 1 00:44:45.598: IPv6: Resolving next hop FF02::16 on interface Serial0/0
r1(config-if)#

-----------------------------------------------------------
timaz mohsenzadeh

willroute4food
Member
Posts:
200
Joined:
Fri Nov 13, 2009 4:42 pm
Certs:
CCIE R&S

Re: silly ipv6 problem !

Mon Aug 08, 2011 12:43 pm

AFAIK 3550's wont work with IPv6. From my experience you can enter all the information in them, but they wont ever pass traffic (I have tested this). 3550's just dont support it. I read once about a guy who got them to work using GRE tunnels, but I never looked much more into it to be honest.

willroute4food
Member
Posts:
200
Joined:
Fri Nov 13, 2009 4:42 pm
Certs:
CCIE R&S

Re: silly ipv6 problem !

Mon Aug 08, 2011 12:47 pm

Here I found it for you if you want to try it out:
http://www.gossamer-threads.com/lists/c ... ded#127795

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Mon Aug 08, 2011 12:50 pm

so what is the problem with R1 (2600xm)? .. as we see from the out put, when i want to assigne ipv6 address just on se0/0 on 2600xm, it said "encapsulation failed". even i have tested the ipv6 ping on 2 router, (2600xm and 1841). but again it was unsuccessful.
timaz mohsenzadeh

willroute4food
Member
Posts:
200
Joined:
Fri Nov 13, 2009 4:42 pm
Certs:
CCIE R&S

Re: silly ipv6 problem !

Mon Aug 08, 2011 1:01 pm

paste in the config of those interfaces (the serial ones connecting the two routers), or just a 'show ipv6 int bri'.

User avatar
mellowd
CCIE #38070
Posts:
13814
Joined:
Wed Jun 18, 2008 7:49 am
Certs:
CCIE (RS,SP), JNCIE-SP, BC-/SPNE/NP

silly ipv6 problem !

Mon Aug 08, 2011 1:08 pm

Encapsulation failed means there is no layer 3 to layer 2 mapping.


---
- Sent on the move...

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Mon Aug 08, 2011 1:13 pm

I know. and I think, this is the reason that I cannot see any output from the "sh ipv6 neighbors" command. I think the routers cannot handle the IPv6 Neighbor Discovery process. am i right?
timaz mohsenzadeh

comptech
Junior Member
Posts:
54
Joined:
Sat Jun 13, 2009 8:39 pm
Certs:
CCNA, 642-902

Re: silly ipv6 problem !

Mon Aug 08, 2011 7:28 pm

The IP addresses you're trying to ping aren't correct if I'm reading the routing table correctly.
Try to ping 1001::1 or 1001::2 between R1 and SW1 and see what happens.

Edit: After reading willroute4food's link, it appears that a 3550 doesn't support IPv6 very well. This probably still won't work.

timaz
Member
Posts:
225
Joined:
Sat May 31, 2008 2:25 pm

Re: silly ipv6 problem !

Sun Aug 21, 2011 5:20 pm

I have tried this test on 2 1841 connected routers and it was succesful. i think there is a problem with 2600xm router that has "Adventerprise 12.4(15)t7" ios. I must change the IOS to test if it work.
timaz mohsenzadeh

milton
New Member
Posts:
3
Joined:
Wed Feb 08, 2012 5:05 am
Certs:
none

Re: silly ipv6 problem !

Wed Feb 08, 2012 5:08 am

nice discussion...

User avatar
writeerase
Ultimate Member
Posts:
509
Joined:
Sat Apr 09, 2011 3:55 pm
Certs:
CCIE CCNP-S CCDA MCSE RHCT Sec+ A+

Re: silly ipv6 problem !

Wed Feb 08, 2012 10:07 am

3550s are worthless for IPv6, you need 3560s...

User avatar
Agent Zed
Senior Member
Posts:
362
Joined:
Fri Sep 02, 2011 6:59 am
Certs:
CCNA, CCNP

Re: silly ipv6 problem !

Mon Feb 13, 2012 9:19 am

timaz wrote:I have tried this test on 2 1841 connected routers and it was succesful. i think there is a problem with 2600xm router that has "Adventerprise 12.4(15)t7" ios. I must change the IOS to test if it work.
I rune those and they work mint! How about that interface config paste? How's the L2 setup on them (since the encapsulation failed)?

'

Return to IPv6

Who is online

Users browsing this forum: No registered users and 5 guests