Need help on an IPv6 Lab -> OSPFv3.

billscott92787billscott92787 Member Posts: 933
in CCNP
Hey guys,


I have been trying to figure out how to do this IPV6 OSPv3 lab here today. I know that I am missing something. I have included a diagram for your review as to what the network looks like. I have defined router ID's on all the routers.

R1 -> 1.1.1.1
R2 -> 2.2.2.2
R3 -> 3.3.3.3
R4 -> 4.4.4.4

Each router has ipv6 unicast-routing enabled, and each interface has an IPv6 address assigned to it (a link local address FE80..). In addition, I have enabled OSPFv3 on the interfaces between R1 to R2, R2 to R3, and R3 to R4. I know where the issue lies, R4 is connected to R3, which is not connected to area 0. This is where it comes into play needing a virtual link to be created. Here is what I tried to do.


On R4.

ipv6 router ospf 1
area 12 virtual-link 2.2.2.2

On R2
ipv6 router ospf 1
area 12 virtual-link 4.4.4.4


I used the router id's which are still expressed in a 32-bit format. Each router has an adjacency to the other routers.


R1#show ipv6 ospf neighbor

Neighbor ID Pri State Dead Time Interface ID Interface
2.2.2.2 1 FULL/ - 00:00:32 4 Serial0/0


R2#show ipv6 ospf neighbor

Neighbor ID Pri State Dead Time Interface ID Interface
1.1.1.1 1 FULL/ - 00:00:30 4 Serial0/0
3.3.3.3 1 FULL/ - 00:00:34 4 Serial0/1


R3#show ipv6 ospf neighbor

Neighbor ID Pri State Dead Time Interface ID Interface
2.2.2.2 1 FULL/ - 00:00:32 5 Serial0/0
4.4.4.4 1 FULL/ - 00:00:34 4 Serial0/1

R4#show ipv6 ospf ne

Neighbor ID Pri State Dead Time Interface ID Interface
3.3.3.3 1 FULL/ - 00:00:37 5 Serial0/0




What I can't figure out is the fact that my virtual-link never comes up.



R4#show ipv6 ospf virtual-links
Virtual Link OSPFv3_VL0 to router 2.2.2.2 is down
Interface ID 13, IPv6 address ::
Run as demand circuit
DoNotAge LSA allowed.
Transit area 12, Cost of using 65535
Transmit Delay is 1 sec, State DOWN,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

R2#show ipv6 ospf virtual-links
Virtual Link OSPFv3_VL0 to router 4.4.4.4 is down
Interface ID 12, IPv6 address ::
Run as demand circuit
DoNotAge LSA allowed.
Transit area 12, Cost of using 65535
Transmit Delay is 1 sec, State DOWN,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5




My question is, what am I forgetting. Can they not reach each other because R4 doesn't know how to get to 2.2.2.2 and R2 doesn't know how to get to 4.4.4.4?
· Share on FacebookShare on Twitter

Comments

  • jason_lundejason_lunde Member Posts: 567
    I may be wrong..but I think your virtual link needs to be from r2-->r3..connecting that last area to the backbone; making area12 a transit area. Cisco doc time...
    OSPF Virtual Link [IP Routing] - Cisco Systems
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    I believe it would be between R2 and R4. R3 is connected to R2, which R2 has an interface that is in area 0. R4 connects to R3 which doesn't have an interface within area 0. So I would believe that area 12 would be the transit area to area 0. I have been beating my brain in trying to figure this lab out. LOL. I really think somehow it has something to do with R2 not knowing how to reach 4.4.4.4 and R4 not knowing how to reach 2.2.2.2.
    · Share on FacebookShare on Twitter
  • jason_lundejason_lunde Member Posts: 567
    billscott92787 wrote: »
    I believe it would be between R2 and R4. R3 is connected to R2, which R2 has an interface that is in area 0. R4 connects to R3 which doesn't have an interface within area 0. So I would believe that area 12 would be the transit area to area 0. I have been beating my brain in trying to figure this lab out. LOL. I really think somehow it has something to do with R2 not knowing how to reach 4.4.4.4 and R4 not knowing how to reach 2.2.2.2.

    R3 doesnt have to have an interface in area 0, the area has to have some physical connectivity to it. From the cisco doc:
    "All areas in an Open Shortest Path First (OSPF) autonomous system must be physically connected to the backbone area (Area 0)"

    So if area 12 is the transit area, R3 virtually has an interface to area 0, thus giving that final area physical connection to area 0 through the R3 and the virtual link.
    · Share on FacebookShare on Twitter
  • acidsatyracidsatyr Member Posts: 111
    billscott92787 wrote: »
    I believe it would be between R2 and R4. R3 is connected to R2, which R2 has an interface that is in area 0. R4 connects to R3 which doesn't have an interface within area 0. So I would believe that area 12 would be the transit area to area 0. I have been beating my brain in trying to figure this lab out. LOL. I really think somehow it has something to do with R2 not knowing how to reach 4.4.4.4 and R4 not knowing how to reach 2.2.2.2.

    No. its R2 and R3.
    Because R3 is potential Abr.
    Try it out.
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    Ah ok. I see what you guys are saying now. I understand what you mean. I tried configuring it though but I still get the virtual link as down.


    R3#show ipv6 ospf virtual-links
    Virtual Link OSPFv3_VL2 to router 2.2.2.2 is down
    Interface ID 14, IPv6 address ::
    Run as demand circuit
    DoNotAge LSA allowed.
    Transit area 12, Cost of using 65535
    Transmit Delay is 1 sec, State DOWN,
    Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5


    R2#show ipv6 ospf virtual-links
    Virtual Link OSPFv3_VL3 to router 3.3.3.3 is down
    Interface ID 15, IPv6 address ::
    Run as demand circuit
    DoNotAge LSA allowed.
    Transit area 12, Cost of using 65535
    Transmit Delay is 1 sec, State DOWN,
    Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    · Share on FacebookShare on Twitter
  • acidsatyracidsatyr Member Posts: 111
    well its obvious, see that "ipv6 add :: " ? that means you don't have ipv6 address configured on r2's interface to r3 and vice versa.
    add something like fc00::2/64 and fc00::3/64 then get back.

    p.s. link local doesn't count - its only used as next-hop. you need the real address.
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    acidsatyr wrote: »
    well its obvious, see that "ipv6 add :: " ? that means you don't have ipv6 address configured on r2's interface to r3 and vice versa.
    add something like fc00::2/64 and fc00::3/64 then get back.



    There is no IPV6 address configured on the loopback interface that I defined as router-ID (EX: 2.2.2.2 is a loopback on R2, same with 1.1.1.1 -> R1, 3.3.3.3 -> R3, 4.4.4.4 -> R4)


    R2 to R3:

    R2#show ipv6 int s0/1
    Serial0/1 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::1
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:1
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.


    R3#show ipv6 int s0/0
    Serial0/0 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::2
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:2
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.


    There is IP connectivity between them. These pings are being sent between R2 to R3 and from R3 to R2.


    R3#ping FE80:2::1
    Output Interface: serial0/0
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80:2::1, timeout is 2 seconds:
    Packet sent with a source address of FE80:2::2
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 8/16/36 ms


    R2#ping FE80:2::2
    Output Interface: serial0/1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80:2::2, timeout is 2 seconds:
    Packet sent with a source address of FE80:2::1
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 8/12/24 ms



    As well as between all the other routers:


    R1 to R2:

    R1#ping FE80:1::2
    Output Interface: serial0/0
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80:1::2, timeout is 2 seconds:
    Packet sent with a source address of FE80:1::1
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 8/11/20 ms




    R3 to R4:

    R3#ping FE80:3::3
    Output Interface: serial0/1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80:3::3, timeout is 2 seconds:
    Packet sent with a source address of FE80:3::1
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 4/14/28 ms




    All interfaces are up and up. Verified with the show ipv6 interface serialx/x command.
    · Share on FacebookShare on Twitter
  • acidsatyracidsatyr Member Posts: 111
    i said, r2's interface to r3 needs ipv6 add, and vice versa. Not loopback.
    r2's s0/1 need routable address, and r3's s0/0 need routable address.
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    acidsatyr wrote: »
    i said, r2's interface to r3 needs ipv6 add, and vice versa. Not loopback.
    r2's s0/1 need routable address, and r3's s0/0 need routable address.



    I understand what you are saying. But, If you look at my text, you can see that they have IPv6 addresses assigned to them. To the "serial" interfaces that connect R1 to R2, R2 to R3, and R3 to R4. Pings work between them all as you can see in the above text. Is there an additional address I need to assign since these are link-local addresses?
    · Share on FacebookShare on Twitter
  • acidsatyracidsatyr Member Posts: 111
    billscott92787 wrote: »
    I know what you said. If you look at my text, you can see that they have IPv6 addresses assigned to them. To the "serial" interfaces that connect R1 to R2, R2 to R3, and R3 to R4.


    No you don't get it.

    R2#show ipv6 int s0/1
    Serial0/1 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::1
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:1
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.


    R3#show ipv6 int s0/0
    Serial0/0 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::2
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:2
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.

    YOU NEED ROUTABLE IPV6 ADD! FE80 is link local.
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    acidsatyr wrote: »
    No you don't get it.

    R2#show ipv6 int s0/1
    Serial0/1 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::1
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:1
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.


    R3#show ipv6 int s0/0
    Serial0/0 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80:2::2
    No global unicast address is configured
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::5
    FF02::1:FF00:2
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    Hosts use stateless autoconfig for addresses.

    YOU NEED ROUTABLE IPV6 ADD! FE80 is link local.



    I see what you mean now. The link local's only work between the two links, not between any of the other routers. I will add that and report back. Thank you :)
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    Well, you definitely were correct. I apologize that I didn't understand that you meant global IPv6 addresses. As soon as I added them, immediately it worked. I could see the route to R4's loop back interface within R1's IPv6 routing table. I really appreciate your time that you spent getting it through my thick skull. LOL
    · Share on FacebookShare on Twitter
  • burbankmarcburbankmarc Member Posts: 460
    You might wanna hit the IPv6 chapter again icon_thumright.gif
    · Share on FacebookShare on Twitter
  • billscott92787billscott92787 Member Posts: 933
    burbankmarc wrote: »
    You might wanna hit the IPv6 chapter again icon_thumright.gif

    I am definitely going to do that before my next attempt in two weeks. I remember seeing it now but didn't retain that part, so I'm going to hit it again. Thanks for all your help guys :)
    · Share on FacebookShare on Twitter
Sign In or Register to comment.