Scribd Logo
Upload

Welcome to Scribd!

  • 67 views

    IPv6 OSPF

    Uploaded by

    David Cerqueira
    A small export company has an existing enterprise network that is running OSPFv3. R4's loopback address (FEC0:4:4) cannot be seen in R1's IPv6 routing table. You are tasked with identifying the cause of this fault and implementing corrective actions.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    IPv6 OSPF

    Uploaded by

    David Cerqueira
    67 views3 pages
    A small export company has an existing enterprise network that is running OSPFv3. R4's loopback address (FEC0:4:4) cannot be seen in R1's IPv6 routing table. You are tasked with identifying the cause of this fault and implementing corrective actions.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    A small export company has an existing enterprise network that is running OSPFv3. R4's loopback address (FEC0:4:4) cannot be seen in R1's IPv6 routing table. You are tasked with identifying the cause of this fault and implementing corrective actions.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    67 views3 pages

    IPv6 OSPF

    Uploaded by

    David Cerqueira
    A small export company has an existing enterprise network that is running OSPFv3. R4's loopback address (FEC0:4:4) cannot be seen in R1's IPv6 routing table. You are tasked with identifying the cause of this fault and implementing corrective actions.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 3

    OSPF VIRTUAL LINK Question Acme is a small export company that has an existing enterprise network that is running

    IPv6 OSPFv3. Currently OSPF is configured on all routers. However, R4s loopback address (FEC0:4:4) cannot be seen in R1s IPv6 routing table. You are tasked with identifying the cause of this fault and implementing the needed corrective actions that uses OSPF features and does no change the current area assignments. You will know that you have corrected the fault when R4s loopback address (FEC0:4:4) can be seen in the routing table of R1.

    Special Note: To gain the maximum number of points you must remove all incorrect or unneeded configuration statements related to this issue. Answer and Explanation: To troubleshoot the problem, first issue the show running-config on all of 4 routers. Pay more attention to the outputs of routers R2 and R3 The output of the show running-config command of R2:

    The output of the show running-config command of R3:

    + Configure virtual link on R2 (from the first output above, we learned that the OSPF process ID of R2 is 1):

    R2>enable R2#configure terminal R2(config)#ipv6 router ospf 1 R2(config-rtr)#area 11 virtual-link 3.3.3.3


    (Notice that we have to use R3 neighbour router-id 3.3.3.3, not R2s router-id 2.2.2.2) + Configure virtual link on R3 (from the second output above, we learned that the OSPF process ID of R3 is 1 and we have to disable the wrong configuration of area 54 virtual-link 4.4.4.4):

    R3>enable R3#configure terminal R3(config)#ipv6 router ospf 1 R3(config-rtr)#no area 54 virtual-link 4.4.4.4 R3(config-rtr)#area 11 virtual-link 2.2.2.2
    We should check the configuration on R4:

    R4>enable R4#show running-config


    You will see a wrongly configured virtual-link command. To get full mark we have to disable this command:

    R4#configure terminal R4(config)#ipv6 router ospf 1 R4(config-rtr)#no area 54 virtual-link 3.3.3.3


    After finishing the configurations dont forget to ping between R1 and R4 to make sure they work well! Now all the configuration was done. It is weird that we cant ping the IPv6 loopback interface of R4 (with the ping or ping ipv6 command) but we can check by using the command show ipv6 route on R1

    The copying running-config startup-config command will not work but dont worry, just skip it. Notice: If you issue the command show running-config on R1, you will see these two lines: passive-interface default no passive-interface fa0/0 (fa0/0 is the interface connecting with R2) These two lines make all the interfaces of R1 become passive interfaces except interface fa0/0. They are correctly configured so dont try to disable them. Conclude with sh ipv6 route in R1 At the end of the output you will find

    FEC0:4:4/128 (the loopback address of R4).

    1.Policy Based (Same as on digitaltut) 2. Eigrp summarization (Digitaltut config + should use distance eigrp 90 109(ext should be <110) ping n trace route works to check/confirm the change, R1-R2(FE) R2-R3(FE), R2-R4(Serial) 3. Ospf Stub (its true that after giving stub no-summary on ABR, neighbour goes to down.. what ever we try it will be in down after configuring stub still got 100% in OSPF, so its right to leave it there and right of Lynaic is Area 1, that doesn't make any difference) 4. Ipv6 OSPFv3 virtual link (same as digitaltut lab) R1 will show the loop back IP of R4 after successful change n config (PING doesn't work) DND.steps to implement OSPF.answer is (options 3, 4, 5, 6) 3. Summarization boundaries 4. Ospf process ID that will be used 5. Authentication type that will be used 6. Ospf Area and associated prefix IPV4 equivalent IP for IPV6 ::ffff:AC11:AC11, I select 172.17.172.17

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy