Narbik_OSPFv3-Lab-2

CCIE R&S by Narbik Kocharians Advanced CCIE R&S Work Book 4.0 Page 1 of 23 © 2015 Narbik Kocharians. All rights reserved

Advanced CCIE Routing & Switching

v5.0

www.MicronicsTraining.com

Narbik Kocharians

CCSI, CCIE #12410

R&S, Security, SP

VOL-III


R1

:1

R7

:7

R2R8

:8

17::/64 G0/0F0/0

27::/64

G0/1

F0/1

Area 0

Area 1

28::/64 F0/0G0/0

:2

Area 2

Lo0 - 2000:111:111:1110::111/64

Lo1 - 2000:111:111:1111::111/64

Lo2 - 2000:111:111:1112::111/64

Lo3 - 2000:111:111:1113::111/64

Lo0 - 2000:777:111:1110::111/64

Lo1 - 2000:777:111:1117::111/64

Lo2 - 2000:777:111:111A::111/64

Lo3 - 2000:777:111:111E::111/64

Lo0 - 2000:888:111:111B::111/64

Lo1 - 2000:888:111:111C::111/64

Lo2 - 2000:888:111:111D::111/64

Lo3 - 2000:888:111:111F::111/64

Task 1

Configure the above topology. DO NOT configure any routing protocol/s. The Link-local IPv6 addresses of these routers should be based on the following: R1 – FE80::1 R2 – FE80::2 R7 – FE80::7 R8 – FE80::8

On SW1:

SW1(config)#int range f0/1 , f0/7

Lab 2 – Summarization of Internal and

External Networks


SW1(config-if-range)#Swi mode acc

SW1(config-if-range)#swi acc v 17

SW1(config-if-range)#Spanning portf

SW1(config-if-range)#No shut



SW1(config-if-range)#Swi acc v 28

SW1(config-if-range)#Spannin portf


On SW2:



SW2(config-if-range)#Swi acc v 27

SW2(config-if-range)#Spannin portf


On R1:

R1(config)#int f0/0

R1(config-if)#IPv6 address 17::1/64

R1(config-if)#IPv6 address FE80::1 Link-Local

R1(config-if)#No shut

R1(config)#Int Lo0

R1(config-if)#Ipv6 addr 2000:111:111:1110::111/64

R1(config)#Int lo1

R1(config-if)#Ipv addr 2000:111:111:1111::111/64

R1(config)#Int Lo2


R1(config)#Int Lo3


On R7:

R7(config)#int g0/0


R7(config-if)#IPv6 address FE80::7 Link-local



R7(config)#int g0/1




R7(config)#Int Lo0


R7(config)#Int Lo1


R7(config)#Int Lo2

R7(config-if)#Ipv addr 2000:777:111:111A::111/64

R7(config)#Int Lo3

R7(config-if)#Ipv addr 2000:777:111:111E::111/64

To verify the configuration:

On R7:

R7#Ping 17::1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 17::1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms

R7#Show ipv6 neighbors

IPv6 Address Age Link-layer Addr State Interface

17::1 2 000a.b86b.dfd0 STALE Gi0/0

FE80::1 2 000a.b86b.dfd0 STALE Gi0/0

27::2 1 0013.c455.f569 STALE Gi0/1

FE80::2 0 0013.c455.f569 STALE Gi0/1

On R2:

R2(config)#int F0/1




R2(config)#Int f0/0






On R2:

R2#Ping 27::7



!!!!!


R2#Sh ipv6 neighbors


27::7 0 24e9.b3ab.4921 REACH Fa0/1

FE80::7 0 24e9.b3ab.4921 DELAY Fa0/1

On R8:

R8(config)#int g0/0




R8(config)#Int Lo0

R8(config-if)#Ipv addr 2000:888:111:111B::111/64

R8(config)#Int Lo1

R8(config-if)#Ipv addr 2000:888:111:111C::111/64

R8(config)#Int Lo2

R8(config-if)#Ipv addr 2000:888:111:111D::111/64

R8(config)#Int Lo3

R8(config-if)#Ipv addr 2000:888:111:111F::111/64


On R8:


R8#Ping 28::2



!!!!!


R8#Show ipv6 neighbors


28::2 0 0013.c455.f568 REACH Gi0/0

FE80::2 0 0013.c455.f568 DELAY Gi0/0

Task 2

Configure OSPFv3 based on the following requirements:

Configure OSPFv3 on R1 and run all its directly connected interfaces in area 1. DON’T use Address-family to configure this router. Configure the loopback interfaces with their correct mask. The RID of this router should be set to “0.0.0.1”

Configure OSPFv3 on R7 using an Address-family. This router should run OSPFv3 area 1 on its G0/0 and OSPFv3 area 0 on its G0/1. The loopoback interfaces of this router should be configured in area 0. Configure the loopback interfaces with their correct mask. The RID of this router should be set to “0.0.0.7”

Configure OSPFv3 on R2 and run its F0/1 interface in area 0, and its F0/0 interface in area 2. DON’T use Address-family to configure this router. The RID of this router should be set to “0.0.0.2”

Configure OSPFv3 on R8 using an Address-family. This router should run OSPFv3 area 2 on its G0/1 interface. The loopoback interfaces of this router should be configured in OSPFv3 routing domain. The RID of this router should be set to “0.0.0.8”.

On R1:

R1(config)#ipv6 unicast-routing

R1(config)#IPv6 router ospf 1

R1(config-rtr)#router-id 0.0.0.1


R1(config)#int f0/0

R1(config-if)#ipv6 ospf 1 area 1

R1(config)#int range Lo0 - 3

R1(config-if-range)#ipv6 ospf 1 area 1

R1(config-if-range)#ipv6 ospf network point-to-point

On R7:


R7(config)#router OSPFv3 1

R7(config-router)#address-family ipv6 unicast

R7(config-router-af)#router-id 0.0.0.7

R7(config)#int g0/1

R7(config-if)#OSPFv3 1 ipv6 area 0

R7(config)#int g0/0

R7(config-if)#OSPFv3 1 ipv6 area 1

You should see the following console message:

%OSPFv3-5-ADJCHG: Process 1, IPv6, Nbr 0.0.0.1 on GigabitEthernet0/0 from

LOADING to FULL, Loading Done

R7(config)#int range lo0 - 3

R7(config-if-range)#OSPFv3 1 ipv6 area 0

R7(config-if-range)#OSPFv3 network Point-to-point


On R7:

R7#Show ipv6 route ospf

IPv6 Routing Table - default - 17 entries

Codes: C - Connected, L - Local, S - Static, U - Per-user Static route

B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP

H - NHRP, I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea

IS - ISIS summary, D - EIGRP, EX - EIGRP external, NM - NEMO

ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect

O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2

ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, ls - LISP site

ld - LISP dyn-EID, a – Application


O 2000:111:111:1110::/64 [110/2]

via FE80::1, GigabitEthernet0/0

O 2000:111:111:1111::/64 [110/2]


O 2000:111:111:1112::/64 [110/2]


O 2000:111:111:1113::/64 [110/2]


R7#Show ospfv3 neighbor

OSPFv3 1 address-family ipv6 (router-id 0.0.0.7)

Neighbor ID Pri State Dead Time Interface ID Interface

0.0.0.1 1 FULL/DR 00:00:37 3 GigabitEthernet0/0

R7#Show ospfv3 inter br

Interface PID Area AF Cost State Nbrs F/C

Lo0 1 0 ipv6 1 P2P 0/0

Lo1 1 0 ipv6 1 P2P 0/0

Lo2 1 0 ipv6 1 P2P 0/0

Lo3 1 0 ipv6 1 P2P 0/0

Gi0/1 1 0 ipv6 1 DR 0/0

Gi0/0 1 1 ipv6 1 BDR 1/1

On R2:



R2(config-rtr)#router-id 0.0.0.2

R2(config)#int f0/1


R2(config)#int f0/0



%OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.7 on FastEthernet0/1 from LOADING

to FULL, Loading Done



On R2:





I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary

D - EIGRP, EX - EIGRP external, NM - NEMO, ND - Neighbor Discovery

l - LISP


ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2

OI 17::/64 [110/2]

via FE80::7, FastEthernet0/1

OI 2000:111:111:1110::/64 [110/3]


OI 2000:111:111:1111::/64 [110/3]


OI 2000:111:111:1112::/64 [110/3]


OI 2000:111:111:1113::/64 [110/3]


O 2000:777:111:1110::/64 [110/2]


O 2000:777:111:1117::/64 [110/2]


O 2000:777:111:111A::/64 [110/2]


O 2000:777:111:111E::/64 [110/2]


On R8:

Since the task does not specify the area in which the loopback interfaces should be configured, the only other way to run them in OSPF si redistribution. Let’s configure R8 based on the requirements of this task:


R8(config-router)#route-map tst

R8(config-route-map)#match interface lo0 lo1 lo2 lo3

R8(config)#router ospfv3 1


R8(config-router-af)#router-id 0.0.0.8

R8(config-router-af)#redistribute connected route-map tst


R8(config-if)#int g0/1

R8(config-if)#ospfv3 1 ipv6 area 2


%OSPFv3-5-ADJCHG: Process 1, IPv6, Nbr 0.0.0.2 on GigabitEthernet0/0 from

LOADING to FULL, Loading Done


On R8:










ld - LISP dyn-EID, a - Application

OI 17::/64 [110/3]


OI 27::/64 [110/2]


OI 2000:111:111:1110::/64 [110/4]


OI 2000:111:111:1111::/64 [110/4]


OI 2000:111:111:1112::/64 [110/4]


OI 2000:111:111:1113::/64 [110/4]


OI 2000:777:111:1110::/64 [110/3]


OI 2000:777:111:1117::/64 [110/3]


OI 2000:777:111:111A::/64 [110/3]


OI 2000:777:111:111E::/64 [110/3]


On R2:


R2#Show ipv route ospf






l - LISP



OI 17::/64 [110/2]


OI 2000:111:111:1110::/64 [110/3]


OI 2000:111:111:1111::/64 [110/3]


OI 2000:111:111:1112::/64 [110/3]


OI 2000:111:111:1113::/64 [110/3]


O 2000:777:111:1110::/64 [110/2]


O 2000:777:111:1117::/64 [110/2]


O 2000:777:111:111A::/64 [110/2]


O 2000:777:111:111E::/64 [110/2]


OE2 2000:888:111:111B::/64 [110/20]


OE2 2000:888:111:111C::/64 [110/20]


OE2 2000:888:111:111D::/64 [110/20]


OE2 2000:888:111:111F::/64 [110/20]


Task 3

Summarize the loopback interfaces configured on R1 and R7. There should be a single summary route for the loopback interfaces of R1 and R7. DON’T configure more than two summary routes to accomplish this task.


In OSPFv2 or v3 summarization can be configured on two router types: ABR and/or an ASBR. In this case, since R7 is the ABR, we should configure R7 to summarize all 8 network. The process of summarization in IPv6 is identical to IPv4, let’s look at the IPv6 addresses on R1: Lo0 - 2000:111:111:1110::111/64

Lo1 - 2000:111:111:1111::111/64

Lo2 - 2000:111:111:1112::111/64

Lo3 - 2000:111:111:1113::111/64

We can see that they all start with 2000:111:111:111 and the last Hex character in the forth hextet is where they differ. Let’s convert the last Hex character of the forth Hextet to binary: 0 = 0 0 0 0

1 = 0 0 0 1

2 = 0 0 1 0

3 = 0 0 1 1

Let’s count the common identical contiguous bits, we should see the following: 0 = 0 0 0 0

1 = 0 0 0 1

2 = 0 0 1 0

3 = 0 0 1 1

We can see that the last two binary digits is where they differ, therefore, all the bits up to the third binary digit of the forth Hextet are identical, therefore, the network that summarizes the above four networks should be:

2000:111:111:1110::/62

Basically, we zeroed the last two bits in the forth Hextet, that gave us the “2000:111:111:1110::” and the prefix length specifies the number of identical contiguous bits, in this case we have: 16 bits : 16 bits : 16 bits : 14 bits or /62. Let’s configure OSPFv3 to summarize these networks, but before we summarize, let’s verify the routing table of R2 and look for these networks:

On R2:

R2#Show ipv6 route ospf | Inc 2000:111:111

OI 2000:111:111:1110::/64 [110/3]


OI 2000:111:111:1111::/64 [110/3]

OI 2000:111:111:1112::/64 [110/3]

OI 2000:111:111:1113::/64 [110/3]

To summarize:

On R7: R2(config)#router ospfv3 1


R2(config-rtr)#area 1 range 2000:111:111:1110::/62


On R2: R2#Show ipv6 route ospf | Inc 2000:111:111

OI 2000:111:111:1110::/62 [110/3]

On R7: R7#Show ipv6 route ospf | Inc /62|Null

O 2000:111:111:1110::/62 [110/2]

via Null0, directly connected

We can see that the discard route is injected to avoid forwarding loops just like OSPFv2. Let’s summarize the loopback interfaces configured on R7. Let’s look at the IPv6 addresses on R7:

Lo0 - 2000:777:111:1110::111/64

Lo1 - 2000:777:111:1117::111/64

Lo2 - 2000:777:111:111A::111/64

Lo3 - 2000:777:111:111E::111/64

Once again the last Hex character of the forth Hextet is where they differ, let’s go through the same process:

0 – 0 0 0 0

7 – 0 1 1 1

A – 1 0 1 0

E – 1 1 1 0


In this case the contiguous identical bits stop at the third Hex character of the forth Hextet, therefore, the summary route should be:

2000:777:111:1110::

And the prefix length should be: 16 bits : 16 bits : 16 bits : 12 bits or /60



R7(config-router-af)#area 0 range 2000:777:111:1110::/60


On R1:

R1#Show ipv6 route ospf | Inc /60

OI 2000:777:111:1110::/60 [110/2]

R1#Ping 2000:777:111:1117::111


Sending 5, 100-byte ICMP Echos to 2000:777:111:1117::111, timeout is 2

seconds:

!!!!!


We need to repeat the same configuration on R2, but before we configure the summary route for R7’s Loopback IPv6 addresses let’s verify the routing table of R8:

On R8:










ld - LISP dyn-EID, a – Application


OI 17::/64 [110/3]


OI 27::/64 [110/2]


OI 2000:111:111:1110::/62 [110/4]


OI 2000:777:111:1110::/64 [110/3]


OI 2000:777:111:1117::/64 [110/3]


OI 2000:777:111:111A::/64 [110/3]


OI 2000:777:111:111E::/64 [110/3]


On R2:

R2(config)#ipv6 router ospf 1

R2(config-rtr)#Area 0 range 2000:777:111:1110::/60


On R8:











OI 17::/64 [110/3]


OI 27::/64 [110/2]


OI 2000:111:111:1110::/62 [110/4]


OI 2000:777:111:1110::/60 [110/3]


R8#Ping 2000:777:111:1117::111



Sending 5, 100-byte ICMP Echos to 2000:777:111:1117::111, timeout is 2

seconds:

!!!!!


Task 4

Summarize the external routes redistributed on R8. If this is done based on the policy, the rest of the routers should see a single summary route for the four networks redistributed into OSPF routing domain.

Let’s look at the IPv6 addresses that are to be summarized:

Lo0 - 2000:888:111:111B::111/64

Lo1 - 2000:888:111:111C::111/64

Lo2 - 2000:888:111:111D::111/64

Lo3 - 2000:888:111:111F::111/64

Let’s configure the last character of the forth Hextet to binary:

B – 1 0 1 1

C – 1 1 0 0

D – 1 1 0 1

F – 1 1 1 1

Therefore, the summary route should be 2000:888:111:1118::/61. Let’s configure and verify:

On R8:

In OSPFv3 we use “Area range” command for internal routes and “Summary-address” for summarizing external routes. In OSPFv3, we still use the “Area range” command but for external routes instead of “Summary-address” the “Summary-prefix” command is used. R8(config)#router ospfv3 1


R8(config-router-af)#Summary-prefix 2000:888:111:1118::/61



On R1:

R1#Show ipv6 route ospf | Inc /61

OE2 2000:888:111:1118::/61 [110/20]

R1#Ping 2000:888:111:111f::111


Sending 5, 100-byte ICMP Echos to 2000:888:111:111F::111, timeout is 2

seconds:

!!!!!


Task 5

The policy for summarizing external routes has changed, the routers in area 2 should see all specific external routes whereas, the routers in the other areas should see a single summary route for the four external routes.

Let’s remove the “Summary-prefix” configured in the previous step:

On R8:



R8(config-router-af)#No summary-prefix 2000:888:111:1118::/61


On R1: R1#Show ipv6 route ospf | Inc /61

R1#

R1#Show ipv6 route ospf | Inc OE2


OE2 2000:888:111:111B::/64 [110/20]

OE2 2000:888:111:111C::/64 [110/20]


OE2 2000:888:111:111D::/64 [110/20]

OE2 2000:888:111:111F::/64 [110/20]

Note: Summarization in OSPFv3 is identical to OSPFv2; there are two routers where the summarization can be configured:

If the routes are internal OSPF routes, the summarization can only be configured on the ABRs using the “Area range” command.

If the routes are external: There are two types of external routes, the “E” routes, these can be “E1” or “E2”, or “N” routes, and they can be “N1” or “N2”. When it comes to “N” routes, they can ONLY be summarized on the ASBR/s, but if the routes are “E” routes, they can be summarized on the router that originates them using the “summary-prefix” command. Therefore, if Area 2 is converted into an NSSA area, R2 will receive the “N” routes, in this case “N2” and it will originate “E” routes or in this case “E2” routes. Since R2 is the one that originates the external “E2” routes, it can summarize the routes redistributed by R8.

On R8:



R8(config-router-af)#Area 2 NSSA

You should see the following console message stating that the adjacency to R2 is down. This is because the area stub flag no longer matches, once R2 is configured with “Area 2 NSSA”, the area stub flag will match (They will both be in NSSA area) and the adjacency will be reestablished.

%OSPFv3-5-ADJCHG: Process 1, IPv6, Nbr 0.0.0.2 on GigabitEthernet0/0

from FULL to DOWN, Neighbor Down: Adjacency forced to reset

On R2:


R2(config-rtr)#Area 2 NSSA

R2(config-rtr)#Summary-prefix 2000:888:111:1118::/61

You should see the following console message stating that the adjacency with 0.0.0.8 or R8 is in FULL state:

%OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.8 on FastEthernet0/0 from LOADING

to FULL, Loading Done



On R1: R1#Show ipv6 route ospf | Inc /61

OE2 2000:888:111:1118::/61 [110/20]

R1#Ping 2000:888:111:111f::111


Sending 5, 100-byte ICMP Echos to 2000:888:111:111F::111, timeout is 2

seconds:

!!!!!


Task 6

None of the routers should have a discard route in their routing table.

In OSPF, the “discard routes” are auto-injected on the router that configured summarization. Let’s verify the existence of the discard routes on R7 and R2:

On R2:







l - LISP



OI 17::/64 [110/2]


OI 2000:111:111:1110::/62 [110/3]


O 2000:777:111:1110::/60 [110/0]


O 2000:777:111:1110::/64 [110/2]



O 2000:777:111:1117::/64 [110/2]


O 2000:777:111:111A::/64 [110/2]


O 2000:777:111:111E::/64 [110/2]


O 2000:888:111:1118::/61 [110/0]


ON2 2000:888:111:111B::/64 [110/20]

via 28::8, FastEthernet0/0

ON2 2000:888:111:111C::/64 [110/20]


ON2 2000:888:111:111D::/64 [110/20]


ON2 2000:888:111:111F::/64 [110/20]


The output of the above show command reveals that R2 has two discard routes, the 2000:777:111:1110::/60, which was injected as a result of summarizing internal routes within Area 0, and the second one is network 2000:888:111:1118::/61 which was injected as a result of summarizing external routes. Let’s remove the discard route for the internal routes:


R2(config-rtr)#No discard-route internal

To verify this configuration:

On R2:







l - LISP



OI 17::/64 [110/2]


OI 2000:111:111:1110::/62 [110/3]


O 2000:777:111:1110::/64 [110/2]



O 2000:777:111:1117::/64 [110/2]


O 2000:777:111:111A::/64 [110/2]


O 2000:777:111:111E::/64 [110/2]


O 2000:888:111:1118::/61 [110/0]


ON2 2000:888:111:111B::/64 [110/20]


ON2 2000:888:111:111C::/64 [110/20]


ON2 2000:888:111:111D::/64 [110/20]


ON2 2000:888:111:111F::/64 [110/20]


We can see that the discard-route for internal networks is removed, let’s remove the discard-route for the external routes:


R2(config-rtr)#No Discard-route external

To verify this configuration:

On R2:







l - LISP



OI 17::/64 [110/2]


OI 2000:111:111:1110::/62 [110/3]


O 2000:777:111:1110::/64 [110/2]


O 2000:777:111:1117::/64 [110/2]



O 2000:777:111:111A::/64 [110/2]


O 2000:777:111:111E::/64 [110/2]


ON2 2000:888:111:111B::/64 [110/20]


ON2 2000:888:111:111C::/64 [110/20]


ON2 2000:888:111:111D::/64 [110/20]


ON2 2000:888:111:111F::/64 [110/20]


Now, let’s remove the discard-route on R7:

On R7:











OI 28::/64 [110/2]


O 2000:111:111:1110::/62 [110/2]


O 2000:111:111:1110::/64 [110/2]


O 2000:111:111:1111::/64 [110/2]


O 2000:111:111:1112::/64 [110/2]


O 2000:111:111:1113::/64 [110/2]


O 2000:777:111:1110::/60 [110/1]


OE2 2000:888:111:1118::/61 [110/20]


Since both discard routes are for internal networks, they can be removed using a single command:




R7(config-router-af)#No discard-route internal


On R7:











OI 28::/64 [110/2]


O 2000:111:111:1110::/64 [110/2]


O 2000:111:111:1111::/64 [110/2]


O 2000:111:111:1112::/64 [110/2]


O 2000:111:111:1113::/64 [110/2]


OE2 2000:888:111:1118::/61 [110/20]


Task 7

Erase the startup configuration of the routers, config.text and the VLAN.dat of the switches and reload them before proceeding to the next lab.

Documents

Narbik_OSPFv3-Lab-2