5.2.3.3 Lab - Troubleshooting Basic Single-Area OSPFv2 and OSPFv3.docx
Short Description
Download 5.2.3.3 Lab - Troubleshooting Basic Single-Area OSPFv2 and OSPFv3.docx...
Description
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 Topology
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3
Addressing Table !evice
OSPF "outer #!
#nter$ace
#P Address
!e$ault %ate&ay
1!2.1"#.1.1/2$ R1
1.1.1.1
0/0
2001%&'#%ACA&%A%%1/"$
,/A
()#0%%1 lin*+local 1!2.1"#.12.1/30 -0/0/0
2001%&'#%ACA&%12%%1/"$
,/A
()#0%%1 lin*+local 1!2.1#.13.1/30 -0/0/1
2001%&'#%ACA&%13%%1/"$
,/A
()#0%%1 lin*+local 1!2.1"#.2.1/2$ R2
2.2.2.2
0/0
2001%&'#%ACA&%'%%2/"$
,/A
()#0%%2 lin*+local 1!2.1"#.12.2/30 -0/0/0
2001%&'#%ACA&%12%%2/"$
,/A
()#0%%2 lin*+local 1!2.1"#.23.1/30 -0/0/1
2001%&'#%ACA&%23%%2/"$
,/A
()#0%%2 lin*+local 1!2.1"#.3.1/2$ R3
3.3.3.3
0/0
2001%&'#%ACA&%C%%3/"$
,/A
()#0%%3 lin*+local 1!2.1"#.13.2/30 -0/0/0
2001%&'#%ACA&%13%%3/"$
,/A
()#0%%3 lin*+local 1!2.1"#.23.2/30 -0/0/1
2001%&'#%ACA&%23%%3/"$
,/A
()#0%%3 lin*+local PC+A
,C
PC+'
,C
PC+C
,C
1!2.1"#.1.3/2$
1!2.1"#.1.1
2001%&'#%ACA&%A%%A/"$
()#0%%1
1!2.1"#.2.3/2$
1!2.1"#.2.1
2001%&'#%ACA&%'%%'/"$
()#0%%2
1!2.1"#.3.3/2$
1!2.1"#.3.1
2001%&'#%ACA&%C%%C/"$
()#0%%3
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3
Ob'ectives Part ( Build the )et&or* and Load !evice +on$igurations Part 2( Troubleshoot Layer 3 +onnectivity Part 3( Troubleshoot OSPFv2 Part ,( Troubleshoot OSPFv3
Bac*ground Scenario en -hortest Path (irst -P( is a lin*+state routing rotocol for P netor*s. -P(v2 is defined for Pv$ netor*s4 and -P(v3 is defined for Pv" netor*s. -P(v2 and -P(v3 are comletel5 isolated routing rotocols4 changes in -P(v2 do not affect -P(v3 routing4 and vice versa. n this lab4 a single+area -P( netor* running -P(v2 and -P(v3 is e6eriencing roblems. 7ou have been assigned to find the roblems ith the netor* and correct them. )ote% The routers used ith CC,A hands+on labs are Cisco 1!$1 ntegrated -ervices Routers -Rs ith Cisco - Release 18.2$93 universal*! image. ther routers and Cisco - versions can be used. &eending on the model and Cisco - version4 the commands available and outut roduced might var5 from hat is shon in the labs. Refer to the Router nterface -ummar5 Table at the end of this lab for the correct interface identifiers. )ote% 9a*e sure that the routers have been erased and ha ve no startu configurations. f 5ou are unsure4 contact 5our instructor.
"e.uired "esources •
3 Routers Cisco 1!$1 ith Cisco - Release 18.2$93 universal image or comarable
•
3 PCs :indos ;4 oad the folloing configurations into the aroriate router. All routers have the same assords. The rivileged )=)C assord is cisco. The assord for console and vt5 access is class. "outer " +on$iguration( conf t service password-encryption no ip domain lookup hostname R1 enable secret class line con 0
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 logging synchronous password cisco login line vty 0 password cisco login banner motd @Unauthorized Access is rohibited!@ ipv" unicast-routing ipv" router ospf 1 router-id 1#1#1#1 passive-interface g0$0 interface g0$0 ip address 1%"'#1#1 &((#&((#&((#0 ipv" address &001)db')acad)a))1$"* ipv" address fe'0))1 link-local interface s0$0$0 clock rate 1&'000 ip address 1%"'#1 &((#&((#&((#0 ipv" address &001)db')acad)1&))1$"* ipv" address fe'0))1 link-local ipv" ospf 1 area 0 no shutdown interface s0$0$1 ip address 1%"'#1+#1 &((#&((#&((#0 ipv" address &001)db')acad)1+))1$"* ipv" address fe'0))1 link-local ipv" ospf 1 area 0 no shutdown router ospf 1 network 1%"'#1#0 0#0#0#&(( area 0 network 1&%#1"'#1� 0#0#0#+ area 0 network 1%"'#1+#0 0#0#0#+ area 0 passive-interface g0$0 end
"outer "2 +on$iguration( conf t service password-encryption no ip domain lookup hostname R& enable secret class line con 0 logging synchronous password cisco login
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page , of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 line vty 0 password cisco login banner motd @Unauthorized Access is rohibited!@ ipv" unicast-routing ipv" router ospf 1 router-id &#&#&#& interface g0$0 ip address 1%"'# &((#&((#&((#0 ipv" address &001)db')acad),))&$"* ipv" address fe'0))1 link-local no shutdown interface s0$0$0 ip address 1%"'#1&#& &((#&((#&((#&(& ipv" address &001)db')acad)1&))&$"* ipv" address fe'0))& link-local ipv" ospf 1 area 0 no shutdown interface s0$0$1 clock rate 1&'000 ipv" address &001)db')acad)&+))&$"* ipv" address fe'0))& link-local no shutdown router ospf 1 network 1%"'#� 0#0#0#&(( area 0 network 1%"'#1� 0#0#0#+ area 0 network 1%"'#&+#0 0#0#0#+ area 0 end
"outer "3 +on$iguration( conf t service password-encryption no ip domain lookup enable secret class hostname R+ line con 0 logging synchronous password cisco login line vty 0 password cisco login banner motd @Unauthorized Access is rohibited!@ interface g0$0 ipv" address &001)db')acad)c))+$"*
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 0 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 ipv" address fe'0))+ link-local interface s0$0$0 clock rate 1&'000 ip address 1%"'#1+#1 &((#&((#&((#&(& ipv" address &001)db')acad)1+))+$"* ipv" address fe'0))+ link-local no shutdown interface s0$0$1 ip address 1%"'#&+#& &((#&((#&((#&(& ipv" address &001)db')acad)&+))+$"* ipv" address fe'0))+ link-local router ospf 1 network 1%"'#+#0 0#0#0#&(( area 0 passive-interface g0$0 end
Part 2( Troubleshoot Layer 3 +onnectivity n Part 24 5ou ill verif5 that >a5er 3 connectivit5 is established on all interfaces. 7ou ill need to test both Pv$ and Pv" connectivit5 for all device interfaces.
Step ( 1eri$y that the inter$aces listed in the Addressing Table are active and con$igured &ith the correct #P address in$oration/ a.
ssue the sho& ip inter$ace brie$ command on all routers to verif5 that the interfaces are in an u/u state. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
b.
ssue the sho& run inter$ace command to verif5 P address assignments on all router interfaces. Comare the interface P addresses against the Addressing Table and verif5 the subnet mas* assignments. (or Pv"4 verif5 that the lin*+local address has been assigned. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
c.
Resolve all roblems that are found. Record the commands used to correct the issues. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? d.
@sing the ping command4 verif5 that each router has netor* connectivit5 ith the serial interfaces on the neighbor routers. a5er 3 issues.
Part 3( Troubleshoot OSPFv2 n Part 34 5ou ill troubleshoot -P(v2 roblems and ma*e the necessar5 changes needed to establish -P(v2 routes and end+to+end Pv$ connectivit5. )ote% >A, 0/0 interfaces should not advertise -P( routing information4 but routes to these netor*s should be in the routing tables.
Step ( Test #Pv, end-to-end connectivity/ (rom each PC host4 ing the other PC hosts in the toolog5 to verif5 end+to+end connectivit5. )ote( t ma5 be necessar5 to disable the PC fireall before testing4 to ing beteen PCs. a. Ping from PC+A to PC+'. :ere the ings successful ?????????????? b. Ping from PC+A to PC+C. :ere the ings successful ?????????????? c.
Ping from PC+' to PC+C. :ere the ings successful ??????????????
Step 2( 1eri$y that all inter$aces are assigned to OSPFv2 area 4 on "/ a.
ssue the sho& ip protocols command to verif5 that -P( is running and that all netor*s are advertised in area 0. ist an5 additional changes made to R1. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ????????????????????????????????????????????????????????????????????????????????????
Step 3( 1eri$y that all inter$aces are assigned to OSPFv2 area 4 on "2/ a.
ssue the sho& ip protocols command to verif5 that -P( is running and that all netor*s are being advertised in area 0. ist an5 additional changes made to R2. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
Step ,( 1eri$y that all inter$aces are assigned to OSPFv2 area 4 on "3/ a.
ssue the sho& ip protocols command to verif5 that -P( is running and that all netor*s are being advertised in area 0. ist an5 additional changes made to R3. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ????????????????????????????????????????????????????????????????????????????????????
Step 0( 1eri$y OSPF neighbor in$oration/ a.
ssue the sho& ip osp$ neighbor command on all routers to vie the -P( neighbor information.
Step ( 1eri$y OSPFv2 "outing #n$oration/ a.
ssue the sho& ip route osp$ command to verif5 that each router has -P(v2 routes to all non+adDoining netor*s. Are all -P(v2 routes available ?????????????? f an5 -P(v2 routes are missing4 hat is missing ????????????????????????????
b. f an5 routing information is missing4 resolve these issues.
Step 5( 1eri$y #Pv, end-to-end connectivity/ (rom each PC4 verif5 that Pv$ end+to+end connectivit5 e6ists. PCs should be able to ing the other PC hosts in the toolog5. f Pv$ end+to+end connectivit5 does not e6ist4 then continue troubleshooting to resolve a n5 remaining issues. )ote% t ma5 be necessar5 to disable the PC fireall to ing beteen PCs.
Part ,( Troubleshoot OSPFv3 n Part $4 5ou ill troubleshoot -P(v3 roblems and ma*e the necessar5 changes needed to establish -P(v3 routes and end+to+end Pv" connectivit5. )ote% >A, 0/0 interfaces should not advertise -P(v3 routing information4 but routes to these netor*s should be contained in the routing tables.
Step ( Test #Pv end-to-end connectivity/ (rom each PC host4 ing the Pv" addresses of the other PC hosts in the toolog5 to verif5 Pv" end+to+end connectivit5.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 7 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 )ote% t ma5 be necessar5 to disable the PC fireall to ing beteen PCs.
Step 2( 1eri$y that #Pv unicast routing has been enabled on all routers/ a. An eas5 a5 to verif5 that Pv" routing has been enabled on a router is to use the sho& run 8 section ipv unicast command. '5 adding this ie E section to the sho& run command4 the ipv unicastrouting command disla5s if Pv" routing has been enabled. )ote% The sho& run command can also be issued ithout an5 ie4 and then a manual search for the ipv unicast-routing command can be done. ssue the command on each router. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? b. f Pv" unicast routing is not enabled on one or more routers4 enable it no. Record the commands used to correct the issues. ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
Step 3( 1eri$y that all inter$aces are assigned to OSPFv3 area 4 on "/ a.
ssue the sho& ipv protocols command and verif5 that the router & is correct. Also verif5 that the e6ected interfaces are disla5ed under area 0. )ote% f no outut is generated from this command4 then the -P(v3 rocess has not been configured. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
b. 9a*e the necessar5 configuration changes to R1. Record the commands used to correct the issues. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? c.
ssue the clear ipv osp$ process command if necessar5.
d. Re+issue the sho& ipv protocols command to verif5 that 5our changes had the desired effect. e.
ssue the sho& ipv osp$ inter$ace brie$ command to verif5 that all interfaces are listed as -P( netor*s assigned to area 0.
f.
ssue the sho& ipv osp$ inter$ace g44 command to verif5 that this interface is set not to advertise -P(v3 routes.
g. Resolve an5 roblems discovered on R1. >ist an5 additional changes made to R1. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ????????????????????????????????????????????????????????????????????????????????????
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 4 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3
Step ,( 1eri$y that all inter$aces are assigned to OSPFv3 area 4 on "2/ a.
ssue the sho& ipv protocols command and verif5 the router & is correct. Also verif5 that the e6ected interfaces disla5 under area 0. )ote% f no outut is generated from this command4 then the -P(v3 rocess has not been configured. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
b. 9a*e the necessar5 configuration changes to R2. Record the commands used to correct the issues. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? c.
ssue the clear ipv osp$ process command if necessar5.
d. Re+issue the sho& ipv protocols command to verif5 that 5our changes had the desired effect. e.
ssue the sho& ipv osp$ inter$ace brie$ command to verif5 that all interfaces are listed as -P( netor*s assigned to area 0.
f.
ssue the sho& ipv osp$ inter$ace g44 command to verif5 that this interface is not set to advertise -P(v3 routes.
g. >ist an5 additional changes made to R2. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
Step 0( 1eri$y that all inter$aces are assigned to OSPFv3 area 4 on "3/ a.
ssue the sho& ipv protocols command and verif5 that the router & is correct. Also verif5 that the e6ected interfaces disla5 under area 0. )ote% f no outut is generated from this command4 then the -P(v3 rocess has not been configured. Record 5our findings. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
b. 9a*e the necessar5 configuration changes to R3. Record the commands used to correct the issues. ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3 ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????? c.
ssue the clear ipv osp$ process command if necessar5.
d. Re+issue the sho& ipv protocols command to verif5 that 5our changes had the desired effect. e.
ssue the sho& ipv osp$ inter$ace brie$ command to verif5 that all interfaces are listed as -P( netor*s assigned to area 0.
f.
ssue the sho& ipv osp$ inter$ace g44 command to verif5 that this interface is set not to advertise -P(v3 routes.
g. Resolve an5 roblems discovered on R3. >ist an5 additional changes made to R3. f no roblems ere found on the device4 then resond ith Bno roblems ere found. ????????????????????????????????????????????????????????????????????????????????????
Step ( 1eri$y that all routers have correct neighbor ad'acency in$oration/ a.
ssue the sho& ipv osp$ neighbor command to verif5 that adDacencies have formed beteen neighboring routers.
b. Resolve an5 -P(v3 adDacenc5 issues that still e6ist.
Step 5( 1eri$y OSPFv3 routing in$oration/ a.
ssue the sho& ipv route osp$ command4 and verif5 that -P(v3 routes e6ist to all non+adDoining netor*s. Are all -P(v3 routes available ?????????????? f an5 -P(v3 routes are missing4 hat is missing ????????????????????????????
b. Resolve an5 routing issues that still e6ist.
Step 6( 1eri$y #Pv end-to-end connectivity/ (rom each PC4 verif5 that Pv" end+to+end connectivit5 e6ists. PCs should be able to ing each interface on the netor*. f Pv" end+to+end connectivit5 does not e6ist4 then continue troubleshooting to resolve remaining issues. )ote% t ma5 be necessar5 to disable the PC fireall to ing beteen PCs.
"e$lection :h5 ould 5ou troubleshoot -P(v2 and -P(v3 searatel5 ??????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????????
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 3
Lab – Troubleshooting Basic Single-Area OSPFv2 and OSPFv3
"outer #nter$ace Suary Table "outer #nter$ace Suary "outer 9odel
:thernet #nter$ace ;
:thernet #nter$ace ;2
Serial #nter$ace ;
Serial #nter$ace ;2
1#00
(ast )thernet 0/0 (0/0
(ast )thernet 0/1 (0/1
-erial 0/0/0 -0/0/0
-erial 0/0/1 -0/0/1
1!00
igabit )thernet 0/0 0/0
igabit )thernet 0/1 0/1
-erial 0/0/0 -0/0/0
-erial 0/0/1 -0/0/1
2#01
(ast )thernet 0/0 (0/0
(ast )thernet 0/1 (0/1
-erial 0/1/0 -0/1/0
-erial 0/1/1 -0/1/1
2#11
(ast )thernet 0/0 (0/0
(ast )thernet 0/1 (0/1
-erial 0/0/0 -0/0/0
-erial 0/0/1 -0/0/1
2!00
igabit )thernet 0/0 0/0
igabit )thernet 0/1 0/1
-erial 0/0/0 -0/0/0
-erial 0/0/1 -0/0/1
)ote% To find out ho the router is configured4 loo* at the interfaces to identif5 the t5e of router and ho man5 interfaces the router has. There is no a5 to effectivel5 list all the combinations of configurations for each router class. This table includes identifiers for the ossible combinations of )thernet and -erial interfaces in the device. The table does not include an5 other t5e of interface4 even though a secific router ma5 contain one. An e6amle of this might be an -&, 'R interface. The string in arenthesis is the legal abbreviation that can be used in Cisco - commands to reresent the interface.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 3
View more...
Comments
