Home > Ticket 16 – IPv6 RIPng OSPFv3 Redistribution

Ticket 16 – IPv6 RIPng OSPFv3 Redistribution

April 21st, 2018 in TSHOOT v2 Go to comments

Problem: Loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).

Configuration of R4:
ipv6 router ospf 6
 log-adjacency-changes
!
ipv6 router rip RIP_ZONE
 redistribute ospf 6 metric 2 include-connected
!

Answer:
Ans1) R4
Ans2) Ipv6 OSPF Routing
Ans3) Under ipv6 ospf process add the ‘redistribute rip RIP_Zone include-connected’ command

Comments (30) Comments
Comment pages
1 2 3 4 5 6 9 698
  1. Lukaas
    December 18th, 2015

    We are running 5.1.1.1 on ceurtesld 8600 s for more than a month with no issues (yet). 5.0.2 was interesting. SLPP issue that would lock up the cpu’s and a lane lockup in the lane with the 10gig ports on the 8634XGRS. 5.1.1.1 seemed to fix both of these.We went to the 5.x code stream just about a year ago in order to bumb our sever farm backhauls up to 10GigE with 5600 TOR and multiple 8612XLRS cards. Supermezz cards caused us many critical failures.Our advice, if you are on 5.x code and you are seeing cpu lockups or IST issues, disable SLPP and the SuperMezz cards. To this day we have not re-enabled the supermezz cards.Mark

  2. shef
    December 22nd, 2015

    I have the same comment like ticket 15 . I can’t ping 2026::111:1 from R3 . There is something wrong between R2 and R3 . R4 is nothing to deal with that . Can somebody take a look ? Is this a bug ?

  3. ak
    December 23rd, 2015

    shef:
    What Netw Simulator are u using when observing the problem?

  4. R4–redistribute rip RIP_Zone — Failed 710 !!
    January 8th, 2016

    This was on the test : Show ipv6 ospf neighbor and Show ipv6 eigrp neighbor
    Ans1) R4
    Ans2) Ipv6 OSPF Routing
    Ans3) Under ipv6 ospf process add the ‘redistribute rip RIP_Zone include-connected’ command

  5. Curious
    January 22nd, 2016

    Spammer link from fresh……. This link kept popping up on the route site. he will go by multiple names, but always to same site. BEWARE

  6. Aditya
    January 27th, 2016

    @networktut
    1.is there no option “ipv6 route redistribution”??

    2.i noticed some prev comments that(as in the simulator here) the answer option is not clearly visible here??(comes on scrolling)??..can u pls confirm

  7. networktut
    January 28th, 2016

    @Aditya: There is no option for “IPv6 route redistribution”. The answer option is not clearly visible in the real exam only (for Ticket 6 – Vlan Filter). Here everything is clearly visible.

  8. Anonymous
    January 31st, 2016

    BUT I have a pbm with this redistribution between RIP(120) and OSPF (AD 110), we will have a pbm on the router where we reditribute mutually isn’it ?
    the route wil choose the ospf external route because AD of ospf are less than the rip internal route isn’it ?

    I am confused I don’t understand this question ?

    can you explain please ?

    thks

  9. Kazi Shabbir Ahmed
    February 14th, 2016

    Hi Can you guys help me with the latest dumps and tips to my email address kazi.shabbir.ahmedATgmail.com. it will be a great help for me because I sceduled my 300 135 exam next week. Thanks in advance.

    Shabbir

  10. ak
    February 17th, 2016

    @all – FYI:
    This newer TSHOOTv2 Ticket has now been uploaded to the Packet Tracer (6.1) TSHOOT Ticket (.zip) Archive here @ Net Tut!

  11. elle
    March 1st, 2016

    thanks to God and to networktut and to every one who contributed to my successs. i am now ccnp certified.
    i passed t.shoot today with 1***
    am so happy

  12. itpro
    March 5th, 2016

    Elle, Can you please tell us about your experience? I am planning to sit for the exam this month. Is networktut.com enough to help someone pass the exam?
    Thank you so much for your reply

  13. Ticket question
    March 8th, 2016

    Is ticket one, OSPF issue, always ticket one or the OSPF fault may be ticket 2 or ticket 5, etc?

  14. Omoolorun
    March 18th, 2016

    @itpro

    Yes networktut.com is all you need to pass; premium membership will give you access to all the materials you need to pass it the first time. All the best.

  15. Rockport
    April 3rd, 2016

    I agree with you Omoolorun. With the help of NETWORKTUT, TSHOOT exam was the easiest exam I’ve passed under Cisco.

  16. taino
    April 7th, 2016

    (On Ticket 16) why the ping fail from R3 to interface 2026:12:1 on R1

  17. ak
    April 8th, 2016

    @tanio:

    Easyyy now!!! – Ping test from R3 to interface 2026:12:1 on R1 within the TSHOOT Infrastructure do NOT fail in any way!!!

    Pls look here:

    R3#sh ipv6 route 2026::12:1

    Routing entry for 2026::12:0/122
    Known via “ospf 6”, distance 110, metric 128, candidate default path
    Route count is 1/1, share count 0
    Routing paths:
    FE80::2D0:97FF:FE34:4E28,Serial0/0/0.23
    Last update 00:01:15 ago

    R3#ping 2026::12:1

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::12:1, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 6/48/101 ms <—- !!!

    R3#

    Thus, pls notice:

    BEFORE DOING ANY IPv6 Ping Tests etc. within the TSHOOT.com Infrastructure, YOU NEED TO WAIT at LEAST 40 – 45 seconds FOR FULL IPv6 NETW CONVERGENCE AFTER LAUNCHING (also) (PT) TICKET # 16!!!

    FULL PT IPv4 Network Convergence – at the other hand – lasts for about 1 minute in total after Ticket Start!!! – Pls do remember these preconditions when running the TSHOOT Tickets!

    Hope this helps!?

  18. taino
    April 9th, 2016

    Thanks @ak…, I was my fault…, the question was for the the premium members… Anyway I simulated every thing on GNS3 and it is working Good, no problem at all…,But as you said about wait 40 to 45 seconds…for convergence on “TSHOOT.com”. I am using the frame relay switch from GNS3, plus the time for convergence for routing protocols (ipv4/ipv6) took close 2 minutes for convergence… Thanks again …

    on GNS3
    R3#ping 2026::12:1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::12:1, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 20/31/40 ms
    R3#

  19. ak
    April 9th, 2016

    Cool tanio!
    I’m glad everything now works fine within your GNS3 TSHOOT Labs!
    In the PT 6.1 Labs provided here, I observed the total IPv4 Convergence time to be approx 60 Seconds after Ticket Start, incl. loading the F/R Switch and the eBGP Protocol (the latter is a VERY Complex and thus “Slow” Netw Protocol to Simulate in PT!) – (GNS3 “emulates” theese things, but it’s still quite complex to manage at u’r Desktop!)
    Anyway, think it’s REAL COOL, you’ve developed your own GNS3 TSHOOT Ticket Labs to Practice on b4 exam! – You’ll learn a LOT from doing this! – Respect for that! :)
    Whish you Good Luck at Exam!!!

  20. NetAdmin
    June 9th, 2016

    Are these still the same tickets they have on the test? I got my CCNP 3 years ago this November and if these are the same questions should be pretty easy to recert.

  21. John
    June 14th, 2016

    @all:
    Please bware, that this (PT) IPv6 Ticket # 16 will only run correctly within the (former) Packet Tracer 6.1 release!!!
    Thx!

  22. skymax
    July 18th, 2016

    Hi,

    Recently, I personally passed CCNP Route 300-101,SWITCH 300-115,TSHOOT 300-135 exams with full marks.
    I have purchased latest Premium vce dumps file that are 100% valid and I’m giving at nominal sharing cost.wanninayakegcb@gmail_com
    Hurry UP. Exam quest.. not change yet..

  23. Adam
    July 24th, 2016

    Dear friends
    Just for information please can you tell me that ticket and configs, M.C.Q,s and simulations are different in premium and normal account? Or they are same,,,,, what is difference in premium and guests account? what is benefit of premium account?
    Please reply ASAP
    Regards,

  24. Brian
    July 26th, 2016

    Adam, You’re just a real SPAMMER, wasting so much Space here on Net Tut, by repeating ALL your equal worded Post’s at every single Forum Page here!!!
    1 Post at the RIGHT Place regarding your issue is ENOUGH!!! – Thx!
    SHAME ON YOU!!!

  25. sharjeel
    July 29th, 2016

    Dear All,
    In Packet tracer im facing issue,couldn’t ping DSW2 loopback ip 2026::102:1 from DSW1 and R4,also Point to point IPs not pingable DSW2(2026::3:2/122) –DSW1(2026::3:1/122);is anyone face same issue ?how u solve

  26. Bruce
    July 30th, 2016

    @sharjeel:

    Yep – You’re right!

    There’s an issue with IPv6 on Packet Tracer rel. 6.2 – 6.3 Catalyst 3560 Eth. Links! – (However IPv6 on indeed ROUTER Links works just fine in these PT releases!)

    But within the Packet Tracer rel. 6.1 – IPv6 works like a charm!!!

    As shown here:

    !
    R4>sh ipv6 prot
    !
    !*** Output omitted for brevity!***
    !
    IPv6 Routing Protocol is “ospf 6”
    Interfaces (Area 34)
    Loopback4
    Tunnel34
    Redistribution:
    None ———————————————-OBS!!!
    !
    R4>
    R4>ena
    R4#conf t
    Enter configuration commands, one per line. End with CNTL/Z.
    R4(config)#ipv6 router ospf 6
    R4(config-rtr)#redistribute rip RIP_ZONE
    R4(config-rtr)#redistribute connected
    R4(config-rtr)#end
    R4#!
    %SYS-5-CONFIG_I: Configured from console by console
    !
    R4#sh ipv6 prot
    !
    !*** Output omitted for brevity!***
    !
    IPv6 Routing Protocol is “ospf 6”
    Interfaces (Area 34)
    Loopback4
    Tunnel34
    Redistribution:
    Redistributing protocol rip ———————-OBS!!!
    Redistributing protocol connected ————-OBS!!!
    !
    R4#ping 2026::102:1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::102:1, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0/22/44 ms
    R4#
    !
    DSW2#ping
    Protocol [ip]: ipv6
    Target IPv6 address: 2026::3:1
    Repeat count [5]:
    Datagram size [100]:
    Timeout in seconds [2]:
    Extended commands [n]: y
    Source address or interface: 2026::3:2
    Type of service [0]:
    Set DF bit in IP header? [no]:
    Validate reply data? [no]:
    Data pattern [0xABCD]:
    Loose, Strict, Record, Timestamp, Verbose[none]:
    Sweep range of sizes [n]:
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::3:1, timeout is 2 seconds:
    Packet sent with a source address of 2026::3:2
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0/7/16 ms
    DSW2#
    !
    To be continued –

  27. Bruce
    July 30th, 2016

    Continued:

    If You like, You can Download the PT 6.1 release from here – (Pls choose a “Non Tutorial” Package):

    ***https://www.dropbox.com/sh/57vxusg67490or0/AACyShw1fmTE6Q4xSkvgbJvca?dl=0***

    IMPORTANT:

    Please carefully study included PT TSHOOT “Readme First File” before installing and using the PT TSHOOT Tickets!

    Also, while troubleshooting PT 6.1 TSHOOT Ticket please study content of the PT: “Ticket Answers:” Menu (Click at “v” symbol at PT Drop down Menu) – (Located at the mid/bottom PT Screen)!

    Good Luck!

  28. skymax
    August 9th, 2016

    Contact me if you need updated dumps & working vce player, wanninayakegcb @ gmail dot com

  29. PAL
    September 4th, 2016

    ANY HELP ON THIS ?

    R4#ping 2026::102:1

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::102:1, timeout is 2 seconds:
    …..
    Success rate is 0 percent (0/5)

    R4#sh ipv6 route 2026::102:1
    Routing entry for 2026::102:0/122
    Known via “rip RIP_ZONE”, distance 120, metric 3
    Route count is 1/1, share count 0
    Routing paths:
    FE80::2E0:F7FF:FE4C:6701,FastEthernet0/0
    Last update 00:00:12 ago
    R4#ping 2026::102:1

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2026::102:1, timeout is 2 seconds:
    …..
    Success rate is 0 percent (0/5)

    R4#

  30. MB
    September 5th, 2016

    PAL:

    Pls try run all TSHOOT IPv6 Tickets within the former Packet Tracer 6.1 release! – Then it should work just perfect!

    (Pls remember to wait for FULL PT OSPFv3 Convergence after fixing the Tickets, b4 Testing!!!)

    A PT 6.1 S/W Download Link can be found at some of the most recent PT Forum Pages here!

    Unfortunately the newer PT 6.2 – 6.3 releases are having some trouble when running indeed IPv6 traffic on (L3 based) Cat. 3560 Switches within these PT S/W releases!

    But, perhaps this IPv6 issue has been solved within the newest Packet Tracer 7.0 Release??? – Haven’t tried it out yet, so it would be REAL nice, if somebody here could test it out, and then post a status about the case here! – THX!

    Hope this helps!

Comment pages
1 2 3 4 5 6 9 698