Thanks Jay... i missed that while reading show run :)
You were a lifesaver (y). thanks amer On Thu, Dec 16, 2010 at 2:14 AM, Jay Taylor <[email protected]> wrote: > I see the frame map for R5's link local addy but not R2's: > > > frame-relay map ipv6 FE80::5 512 broadcast > > > On Wed, Dec 15, 2010 at 6:04 PM, Amer Mustafa <[email protected]>wrote: > >> >> Also i am adding the ipv6 packet debug : >> >> ype escape sequence to abort. >> Sending 5, 100-byte ICMP Echos to 2000:1:1:2B2B::2, timeout is 2 seconds: >> Dec 15 22:59:50.119: IPv6: Looking up 2000:1:1:2B2B::2 [Source ::] in FIB >> Dec 15 22:59:50.119: IPv6: FIB lookup for 2000:1:1:2B2B::2 succeeded. >> if=Serial0/1/0.1, nexthop FE80::2 >> Dec 15 22:59:50.119: IPv6-Sas: SAS picked source FD00:0:0:6419::5 for >> 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:50.119: IPv6-Fwd: nexthop FE80::2, >> Dec 15 22:59:50.119: IPV6: source FD00:0:0:6419::5 (local) >> Dec 15 22:59:50.119: dest 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:50.119: traffic class 0, flow 0x0, len 100+0, prot 58, >> hops 64, originating >> *Dec 15 22:59:50.119: IPv6-Fwd: Encapsulation failed, could not queue for >> resolution.* >> Dec 15 22:59:52.119: IPv6: Looking up 2000:1:1:2B2B::2 [Source ::] in FIB >> Dec 15 22:59:52.119: IPv6: FIB lookup for 2000:1:1:2B2B::2 succeeded. >> if=Serial0/1/0.1, nexthop FE80::2 >> Dec 15 22:59:52.119: IPv6-Sas: SAS picked source FD00:0:0:6419::5 for >> 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:52.119: IPv6-Fwd: nexthop FE80::2, >> Dec 15 22:59:52.119: IPV6: source FD00:0:0:6419::5 (local) >> Dec 15 22:59:52.119: dest 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:52.119: traffic class 0, flow 0x0, len 100+0, prot 58, >> hops 64, originating >> Dec 15 22:59:52.119: IPv6-Fwd: Encapsulation failed, could not queue for >> resolution. >> Dec 15 22:59:54.119: IPv6: Looking up 2000:1:1:2B2B::2 [Source ::] in FIB >> Dec 15 22:59:54.119: IPv6: FIB lookup for 2000:1:1:2B2B::2 succeeded. >> if=Serial0/1/0.1, nexthop FE80::2 >> Dec 15 22:59:54.119: IPv6-Sas: SAS picked source FD00:0:0:6419::5 for >> 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:54.119: IPv6-Fwd: nexthop FE80::2, >> Dec 15 22:59:54.119: IPV6: source FD00:0:0:6419::5 (local) >> Dec 15 22:59:54.119: dest 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:54.119: traffic class 0, flow 0x0, len 100+0, prot 58, >> hops 64, originating >> Dec 15 22:59:54.119: IPv6-Fwd: Encapsulation failed, could not queue for >> resolution. >> Dec 15 22:59:56.119: IPv6: Looking up 2000:1:1:2B2B::2 [Source ::] in FIB >> Dec 15 22:59:56.119: IPv6: FIB lookup for 2000:1:1:2B2B::2 succeeded. >> if=Serial0/1/0.1, nexthop FE80::2 >> Dec 15 22:59:56.119: IPv6-Sas: SAS picked source FD00:0:0:6419::5 for >> 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:56.119: IPv6-Fwd: nexthop FE80::2, >> Dec 15 22:59:56.119: IPV6: source FD00:0:0:6419::5 (local) >> Dec 15 22:59:56.119: dest 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:56.119: traffic class 0, flow 0x0, len 100+0, prot 58, >> hops 64, originating >> Dec 15 22:59:56.119: IPv6-Fwd: Encapsulation failed, could not queue for >> resolution. >> Dec 15 22:59:58.119: IPv6: Looking up 2000:1:1:2B2B::2 [Source ::] in FIB >> Dec 15 22:59:58.119: IPv6: FIB lookup for 2000:1:1:2B2B::2 succeeded. >> if=Serial0/1/0.1, nexthop FE80::2 >> Dec 15 22:59:58.119: IPv6-Sas: SAS picked source FD00:0:0:6419::5 for >> 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:58.119: IPv6-Fwd: nexthop FE80::2, >> Dec 15 22:59:58.119: IPV6: source FD00:0:0:6419::5 (local) >> Dec 15 22:59:58.119: dest 2000:1:1:2B2B::2 (Serial0/1/0.1) >> Dec 15 22:59:58.119: traffic class 0, flow 0x0, len 100+0, prot 58, >> hops 64, originating >> Dec 15 22:59:58.119: IPv6-Fwd: Encapsulation failed, could not queue for >> resolution. >> >> Success rate is 0 percent (0/5) >> R5(config)# >> ---------- Forwarded message ---------- >> From: Amer Mustafa <[email protected]> >> Date: Thu, Dec 16, 2010 at 1:55 AM >> Subject: Workbook 1 ==> Task 32.7 (RIPng) >> To: [email protected] >> Cc: Jason Maynard <[email protected]> >> >> >> *Workbook 1 ==> Task 32.7 (RIPng)* >> ** >> the task requires to advertise a new loop back on R2 in cisco275 and it >> should be reachable from R5. >> >> *on R2 ======>* >> >> R2(config-if)#do show run int lo 1 >> Building configuration... >> Current configuration : 102 bytes >> ! >> interface Loopback1 >> no ip address >> ipv6 address 2000:1:1:2B2B::2/64 >> ipv6 rip cisco275 enable >> end >> >> *on R5 =======>* >> ** >> R5(config)#do show run int ser 0/1/0.1 >> Building configuration... >> Current configuration : 275 bytes >> ! >> interface Serial0/1/0.1 multipoint >> description Use DLCI 512 here when mapped >> ipv6 address FE80::5 link-local >> ipv6 address FD00:0:0:6419::5/64 >> ipv6 rip cisco275 enable >> frame-relay map ipv6 FE80::5 512 broadcast >> frame-relay map ipv6 FD00:0:0:6419::2 512 broadcast >> end >> >> ======================================== >> >> >> R5(config)#do show ipv6 route >> IPv6 Routing Table - Default - 4 entries >> Codes: C - Connected, L - Local, S - Static, U - Per-user Static route >> B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1 >> I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP >> EX - EIGRP external >> O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 >> ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 >> *R 2000:1:1:2B2B::/64 [120/2] >> * via FE80::2, Serial0/1/0.1 >> C FD00:0:0:6419::/64 [0/0] >> via Serial0/1/0.1, directly connected >> L FD00:0:0:6419::5/128 [0/0] >> via Serial0/1/0.1, receive >> L FF00::/8 [0/0] >> via Null0, receive >> R5(config)# >> >> >> BUT STILL NOT ABLE TO PING IT !??? >> >> R5(config)# do ping 2000:1:1:2b2b::2 >> Type escape sequence to abort. >> Sending 5, 100-byte ICMP Echos to 2000:1:1:2B2B::2, timeout is 2 seconds: >> ..... >> Success rate is 0 percent (0/5) >> R5(config)# >> >> >> *can anyone advice why ?* >> >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
