Packet Tracer - Determining the DR and BDR Topology
Addressing Table Device RA
RB
RC
Interface
IP Address
Subnet Mask
G0/0
192.168.1.1
255.255.255.0
Lo0
192.168.31.11
255.255.255.255
G0/0
192.168.1.2
255.255.255.0
Lo0
192.168.31.22
255.255.255.255
G0/0
192.168.1.3
255.255.255.0
Lo0
192.168.31.33
255.255.255.255
Objectives Part 1: Examine DR and BDR Changing Roles Part 2: Modify OSPF Priority and Force Elections
Scenario In this activity, you will examine DR and BDR roles and watch the roles change when there is a change in the network. You will then modify the priority to control the roles and force a new election. Finally, you will verify routers are filling the desired roles.
Part 1: Examine DR and BDR Changing Roles Step 1: Wait until the amber link lights turn green. When you first open the file in Packet Tracer, you may notice that the link lights for the switch are amber. These link lights will stay amber for 50 seconds while the switch makes sure that one of the routers is not another switch. Alternatively, you can click Fast Forward Time to bypass this process.
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 3
Packet Tracer - Determining the DR and BDR
Step 2: Verify the current OSPF neighbor states. a. Use the appropriate command on each router to examine the current DR and BDR. b. Which router is the DR? ______________ c.
Which router is the BDR? ______________
Step 3: Turn on IP OSPF adjacency debugging. a. You can monitor the DR and BDR election process with a debug command. On RA and RB, enter the following command. RA# debug ip ospf adj RB# debug ip ospf adj
Step 4: Disable the Gigabit Ethernet 0/0 interface on RC. a. Disable the link between RC and the switch to cause roles to change. b. Wait about 30 seconds for the dead timers to expire on RA and RB. According to the debug output, which router was elected DR and which router was elected BDR? ____________________________________________________________________________________
Step 5: Restore the Gigabit Ethernet 0/0 interface on RC. a. Re-enable the link between RC and the switch. b. Wait for the new DR/BDR elections to occur. Did DR and BDR roles change? Why or why not? ____________________________________________________________________________________ ____________________________________________________________________________________
Step 6: Disable the Gigabit Ethernet 0/0 interface on RB. a. Disable the link between RB and the switch to cause roles to change. b. Wait about 30 seconds for the holddown timers to expire on RA and RC. According to the debug output on RA, which router was elected DR and which router was elected BDR? ____________________________________________________________________________________
Step 7: Restore the Gigabit Ethernet 0/0 interface on RB. a. Re-enable the link between RB and the switch. b. Wait for the new DR/BDR elections to occur. Did DR and BDR roles change? Why or why not? ____________________________________________________________________________________ ____________________________________________________________________________________
Step 8: Turn off Debugging. Enter the command undebug all on RA and RB to disable debugging.
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 3
Packet Tracer - Determining the DR and BDR
Part 2: Modify OSPF Priority and Force Elections Step 1: Configure OSPF priorities on each router. To change the DR and BDR, configure the Gigabit Ethernet 0/0 port of each router with the following OSPF interface priorities: RA: 200 RB: 100 RC: 1 (This is the default priority)
Step 2: Force an election by reloading the switch. Note: The command clear ip ospf process can also be used on the routers to reset the OSPF process.
Step 3: Verify DR and BDR elections were successful. a. Wait long enough for OSPF to converge and for the DR/BDR election to occur. This should take a few minutes. You can click Fast Forward Time to speed up the process. b. According to output from an appropriate command, which router is now DR and which router is now BDR? ____________________________________________________________________________________
Suggested Scoring Rubric Question Location
Possible Points
Step 2b
10
Step 2c
10
Step 4b
10
Step 5b
10
Step 6b
10
Step 7b
10
Part 1 Total
60
Step 3b
10
Part 2 Total
10
Packet Tracer Score
30
Total Score
100
Activity Section Part 1: Examine DR and BDR Changing Roles
Part 2: Modify OSPF Priority and Force Elections
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Earned Points
Page 3 of 3
Packet Tracer - Propagating a Default Route in OSPFv2 Topology
Addressing Table Device
Interface
IPv4 Address
Subnet Mask
Default Gateway
G0/0
172.16.1.1
255.255.255.0
N/A
S0/0/0
172.16.3.1
255.255.255.252
N/A
S0/0/1
192.168.10.5
255.255.255.252
N/A
G0/0
172.16.2.1
255.255.255.0
N/A
S0/0/0
172.16.3.2
255.255.255.252
N/A
S0/0/1
192.168.10.9
255.255.255.252
N/A
S0/1/0
209.165.200.225
255.255.255.224
N/A
G0/0
192.168.1.1
255.255.255.0
N/A
S0/0/0
192.168.10.6
255.255.255.252
N/A
S0/0/1
192.168.10.10
255.255.255.252
N/A
PC1
NIC
172.16.1.2
255.255.255.0
172.16.1.1
PC2
NIC
172.16.2.2
255.255.255.0
172.16.2.1
PC3
NIC
192.168.1.2
255.255.255.0
192.168.1.1
R1
R2
R3
Objectives Part 1: Propagate a Default Route Part 2: Verify Connectivity
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 2
Packet Tracer - Propagating a Default Route in OSPFv2
Background In this activity, you will configure an IPv4 default route to the Internet and propagate that default route to other OSPF routers. You will then verify the default route is in downstream routing tables and that hosts can now access a web server on the Internet.
Part 1: Propagate a Default Route Step 1: Configure a default route on R2. Configure R2 with a directly attached default route to the Internet. R2(config)# ip route 0.0.0.0 0.0.0.0 Serial0/1/0
Step 2: Propagate the route in OSPF. Configure OSPF to propagate the default route in OSPF routing updates. R2(config-router)# default-information originate
Step 3: Examine the routing tables on R1 and R3. Examine the routing tables of R1 and R3 to verify that the route has been propagated. R1> show ip route <output omitted> O*E2 0.0.0.0/0 [110/1] via 172.16.3.2, 00:00:08, Serial0/0/0 !-------------------
R3> show ip route <output omitted> O*E2 0.0.0.0/0 [110/1] via 192.168.10.9, 00:08:15, Serial0/0/1
Part 2: Verify Connectivity Verify that PC1, PC2, and PC3 can ping the web server.
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 2
Packet Tracer - Configuring OSPF Advanced Features Topology
Addressing Table Device
Interface
IPv4 Address
Subnet Mask
Default Gateway
G0/0
172.16.1.1
255.255.255.0
N/A
S0/0/0
172.16.3.1
255.255.255.252
N/A
S0/0/1
192.168.10.5
255.255.255.252
N/A
G0/0
172.16.2.1
255.255.255.0
N/A
S0/0/0
172.16.3.2
255.255.255.252
N/A
S0/0/1
192.168.10.9
255.255.255.252
N/A
S0/1/0
209.165.200.225
255.255.255.224
N/A
G0/0
192.168.1.1
255.255.255.0
N/A
S0/0/0
192.168.10.6
255.255.255.252
N/A
S0/0/1
192.168.10.10
255.255.255.252
N/A
PC1
NIC
172.16.1.2
255.255.255.0
172.16.1.1
PC2
NIC
172.16.2.2
255.255.255.0
172.16.2.1
PC3
NIC
192.168.1.2
255.255.255.0
192.168.1.1
R1
R2
R3
Objectives Part 1: Modify OSPF Default Settings Part 2: Verify Connectivity
Scenario In this activity, OSPF is already configured and all end devices currently have full connectivity. You will modify the default OSPF routing configuration by changing the hello and dead timers, adjusting the bandwidth of a
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 2
Packet Tracer - Configuring OSPF Advanced Features link, and enabling OSPF authentication. Then you will verify that full connectivity is restored for all end devices.
Part 1: Modify OSPF Default Settings Step 1: Test connectivity between all end devices. Before modifying the OSPF settings, verify that all PCs can ping the web server and each other.
Step 2: Adjust the hello and dead timers between R1 and R2. a. Enter the following commands on R1. R1(config)# interface s0/0/0 R1(config-if)# ip ospf hello-interval 15 R1(config-if)# ip ospf dead-interval 60 b. After a short period of time, the OSPF connection with R2 will fail. Both sides of the connection need to have the same timers in order for the adjacency to be maintained. Adjust the timers on R2.
Step 3: Adjust the bandwidth setting on R1. a. Trace the path between PC1 and the web server located at 64.100.1.2. Notice that the path from PC1 to 64.100.1.2 is routed through R2. OSPF prefers the lower cost path. b. On the R1 Serial 0/0/0 interface, set the bandwidth to 64 Kb/s. This does not change the actual port speed, only the metric that the OSPF process on R1 will use to calculate best routes. R1(config-if)# bandwidth 64 c.
Trace the path between PC1 and the web server located at 64.100.1.2. Notice that the path from PC1 to 64.100.1.2 is redirected through R3. OSPF prefers the lower cost path.
Step 4: Enable OSPF authentication on all serial interfaces. a. Use the following commands to configure authentication between R1 and R2. Note: The key text R1-R2 is case-sensitive. R1(config-router)# area 0 authentication message-digest R1(config)# interface serial 0/0/0 R1(config-if)# ip ospf message-digest-key 1 md5 R1-R2 b. After the dead interval expires, neighbor adjacency between R1 and R2 will be lost. Repeat the authentication commands on R2. c.
Use the following command to configure authentication on R1 for the link it shares with R3. R1(config-if)# ip ospf message-digest-key 1 md5 R1-R3
d. Finish the authentication configurations necessary to restore full connectivity. The password for the link between R2 and R3 is R2-R3. e. Verify that authentication is working between each router. R1# show ip ospf interface Message digest authentication enabled
Part 2: Verify Connectivity Verify all PCs can ping the web server and each other.
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 2
Packet Tracer â&#x20AC;&#x201C; Troubleshooting Single-Area OSPFv2 Topology
Addressing Table Device
Interface
IP Address
Subnet Mask
Default Gateway
G0/0
172.16.1.1
255.255.255.0
N/A
S0/0/0
172.16.3.1
255.255.255.252
N/A
S0/0/1
192.168.10.5
255.255.255.252
N/A
G0/0
172.16.2.1
255.255.255.0
N/A
S0/0/0
172.16.3.2
255.255.255.252
N/A
S0/0/1
192.168.10.9
255.255.255.252
N/A
S0/1/0
209.165.200.225
255.255.255.224
N/A
G0/0
192.168.1.1
255.255.255.0
N/A
S0/0/0
192.168.10.6
255.255.255.252
N/A
S0/0/1
192.168.10.10
255.255.255.252
N/A
PC1
NIC
172.16.1.2
255.255.255.0
172.16.1.1
PC2
NIC
172.16.2.2
255.255.255.0
172.16.2.1
PC3
NIC
192.168.1.2
255.255.255.0
192.168.1.1
R1
R2
R3
Scenario In this activity, you will troubleshoot OSPF routing issues using ping and show commands to identify errors in the network configuration. Then, you will document the errors you discover and implement an appropriate solution. Finally, you will verify end-to-end connectivity is restored.
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 2
Packet Tracer â&#x20AC;&#x201C; Troubleshooting Single-Area OSPFv2
Troubleshooting Process 1. Use testing commands to discover connectivity problems in the network and document the problem in the Documentation Table. 2. Use verification commands to discover the source of the problem and devise an appropriate solution to implement. Document the proposed solution in the Documentation Table. 3. Implement each solution one at a time and verify if the problem is resolved. Indicate the resolution status in the Documentation Table. 4.
If the problem is not resolved, it may be necessary to first remove the implemented solution before returning to Step 2.
5. Once all identified problems are resolved, test for end-to-end connectivity.
Documentation Table Device
Identified Problem
Proposed Solution
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Resolved?
Page 2 of 2
Packet Tracer – Skills Integration Challenge Topology
Addressing Table Device
Interface
IP Address
Subnet Mask
RA
G0/0
192.168.1.1
255.255.255.0
RB
G0/0
192.168.1.2
255.255.255.0
G0/0
192.168.1.3
255.255.255.0
S0/0/0
209.165.200.225
255.255.255.252
RC
Scenario In this Skills Integration Challenge, your focus is OSPFv2 advanced configurations. IP addressing has been configured for all devices. You will configure OSPFv2 routing with passive interfaces and default route propagation. You will modify the OSPFv2 configuration by adjusting timers and establishing MD5 authentication. Finally, you will verify your configurations and test connectivity between end devices.
Requirements Use the following requirements to configure OSPFv2 routing on RA and RB: -
OSPFv2 routing requirements: Process ID 1 Network address for each interface Enable authentication for area 0
-
OSPF priority set to 150 on the LAN interface of RA
-
OSPF priority set to 100 on the LAN interface of RB
-
OSPF MD5 authentication key ID of 1 and MD5 key “cisco” on the LAN interfaces of RA and RB
-
Set the hello interval to 5
-
Set the dead interval to 20
Use the following requirements to configure RC OSPFv2 routing: -
OSPFv2 routing requirements: Process ID 1
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 2
Packet Tracer – Skills Integration Challenge Network address for the LAN interface Enable authentication for area 0 Set all interfaces to passive by default, allow OSPF updates on the active LAN Set the router to distribute default routes -
Configure a directly attached default route to the Internet
-
OSPF priority set to 50 on the LAN interface
-
OSPF MD5 authentication key ID of 1 and MD5 key “cisco” on the LAN interface of RC
-
Set the hello interval to 5
-
Set the dead interval to 20
Note: Issue the clear ip ospf process command on RC if the default route does not propagate. Verify your configurations and test connectivity -
OSPF neighbors should be established and routing tables should be complete.
-
RA should be the DR, RB should be the BDR.
-
All three routers should be able to ping the web server.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 2
Packet Tracer – Configuring Multiarea OSPFv2 Topology
Addressing Table Device
R1
R2
R3
Interface
IP Address
Subnet Mask
OSPFv2 Area
G0/0
10.1.1.1
255.255.255.0
1
G0/1
10.1.2.1
255.255.255.0
1
S0/0/0
192.168.10.2
255.255.255.252
0
G0/0
10.2.1.1
255.255.255.0
0
S0/0/0
192.168.10.1
255.255.255.252
0
S0/0/1
192.168.10.5
255.255.255.252
0
G0/0
192.168.2.1
255.255.255.0
2
G0/1
192.168.1.1
255.255.255.0
2
S0/0/1
192.168.10.6
255.255.255.252
0
Objectives Part 1: Configure Multiarea OSPFv2 Part 2: Verify and Examine Multiarea OSPFv2
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 3
Packet Tracer â&#x20AC;&#x201C; Configuring Multiarea OSPFv2
Background In this activity, you will configure multiarea OSPFv2. The network is already connected and interfaces are configured with IPv4 addressing. Your job is to enable multiarea OSPFv2, verify connectivity, and examine the operation of multiarea OSPFv2.
Part 1: Configure OSPFv2 Step 1: Configure OSPFv2 on R1. Configure OSPFv2 on R1 with a process ID of 1 and a router ID of 1.1.1.1.
Step 2: Advertise each directly connected network in OSPFv2 on R1. Configure each network in OSPFv2 assigning areas according to the Addressing Table. R1(config-router)# network 10.1.1.0 0.0.0.255 area 1 R1(config-router)# network 10.1.2.0 0.0.0.255 area 1 R1(config-router)# network 192.168.10.0 0.0.0.3 area 0
Step 3: Configure OSPFv2 on R2 and R3. Repeat the steps above for R2 and R3 using a router ID of 2.2.2.2 and 3.3.3.3, respectively.
Part 2: Verify and Examine Multiarea OSPFv2 Step 1: Verify connectivity to each of the OSPFv2 areas. From R1, ping each of the following remote devices in area 0 and area 2: 192.168.1.2, 192.168.2.2, and 10.2.1.2.
Step 2: Use show commands to examine the current OSPFv2 operations. Use the following commands to gather information about your OSPFv2 multiarea implementation. show show show show show
ip ip ip ip ip
protocols route ospf database ospf interface ospf neighbor
Reflection Questions 1. Which router(s) are internal routers? _____________________________________________ 2. Which router(s) are backbone routers? _____________________________________________ 3. Which router(s) are area border routers? _____________________________________________ 4. Which router(s) are autonomous system routers? _____________________________________________ 5. Which routers are generating Type 1 LSAs? _____________________________________________ 6. Which routers are generating Type 2 LSAs? _____________________________________________ 7. Which routers are generating Type 3 LSAs? _____________________________________________ 8. Which routers are generating Type 4 and 5 LSAs? _____________________________________________ 9. How many inter area routes does each router have? _____________________________________________
Š 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 3
Packet Tracer – Configuring Multiarea OSPFv2 10. Why would there usually be an ASBR in this type of network? ______________________________________
Suggested Scoring Rubric Packet Tracer scores 80 points. Each of the Reflection Questions is worth 2 points.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 3
Packet Tracer – Configuring Multiarea OSPFv3 Topology
Addressing Table Device
RA
RB
RC
Interface
IPv6 Address
OSPF Area
G0/0
2001:DB8:1:A1::1/64
1
G0/1
2001:DB8:1:A2::1/64
1
S0/0/0
2001:DB8:1:AB::2/64
0
Link-Local
FE80::A
G0/0
2001:DB8:1:B1::1/64
0
S0/0/0
2001:DB8:1:AB::1/64
0
S0/0/1
2001:DB8:1:BC::1/64
0
Link-Local
FE80::B
G0/0
2001:DB8:1:C1::1/64
2
G0/1
2001:DB8:1:C2::1/64
2
S0/0/1
2001:DB8:1:BC::2/64
0
Link-Local
FE80::C
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
N/A
N/A
N/A
Page 1 of 2
Packet Tracer – Configuring Multiarea OSPFv3
Objectives Part 1: Configure OSPFv3 Part 2: Verify Multiarea OSPFv3 Operations
Background In this activity, you will configure multiarea OSPFv3. The network is already connected and interfaces are configured with IPv6 addressing. Your job is to enable multiarea OSPFv3, verify connectivity and examine the operation of multiarea OSPFv3.
Part 1: Configure OSPFv3 Step 1: Enable IPv6 routing and configure OSPFv3 on RA. a. Enable IPv6 routing. b. Configure OSPFv3 on RA with a process ID of 1 and a router ID of 1.1.1.1.
Step 2: Advertise each directly connected network in OSPFv3 on RA. Configure each active IPv6 interface with OSPFv3 assigning each to the area listed in the Addressing Table.
Step 3: Configure OSPFv3 on RB and RC Repeat the Steps 1 and 2 for RB and RC, changing the router ID to 2.2.2.2 and 3.3.3.3 respectively.
Part 2: Verify Multiarea OSPFv3 Operations Step 1: Verify connectivity to each of the OSPFv3 areas. From RA, ping each of the following remote devices in area 0 and area 2: 2001:DB8:1:B1::2, 2001:DB8:1:A1::2, 2001:DB8:1:A2::2, 2001:DB8:1:C1::2, and 2001:DB8:1:C2::2.
Step 2: Use show commands to examine the current OSPFv3 operations. Use the following commands to gather information about your OSPFv3 multiarea implementation. show show show show show
ipv6 ipv6 ipv6 ipv6 ipv6
ospf route ospf database ospf interface ospf neighbor
Note: Packet Tracer output for show ipv6 protocols is currently not aligned with IOS 15 output. Refer to the real equipment labs for correct show command output.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 2