CCNPv7 TSHOOT
Chapter 4 Lab 4-1, Layer 2 Issues Physical Topology
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 1 of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Logical Topology
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 2 of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Objectives •
Load the de"ice confi!uration files for each trouble tic&et.
•
'ia!nose and resol"e Layer 2 connecti"ity proble$s.
•
'ia!nose and resol"e spannin!-tree proble$s.
•
'ocu$ent the troubleshootin! pro!ress, confi!uration chan!es, and proble$ resolution.
Background (ser co$puters, ser"ers, and printers all connect to the access layer of the hierarchical $odel. )ith hundreds or thousands of hosts attached, access de"ices such as Layer 2 s*itches are a co$$on source of net*or&in! issues. %hysical and data-lin& proble$s at the a ccess layer can include hard*are, cablin!, +L assi!n$ent, spannin! tree, trun&in! protocol, or port security issues. In this lab, you *ill troubleshoot "arious Layer 2 proble$s. or each tas& or trouble tic&et, the scenario and sy$pto$s are described. )hile troubleshootin!, you *ill disco"er the cause of the proble$, correct it, and then docu$ent the process and results.
Physical and Logical Topology iagra!s #he physical and lo!ical topolo!ies are pro"ided at the be!innin! of the lab, includin! interface desi!nations and I%"4/I%" addresses, to assist the troubleshootin! effort.
Note" #his lab uses Cisco I 2 routers runnin! Cisco I 15.43 i$a!es *ith I% 6ase and ecurity pac&a!es enabled, and Cisco Catalyst 50 and 270 s*itches runnin! Cisco I 15.032 I% er"ices and L 6ase i$a!es, respecti"ely. #he 50 and 270 s*itches are confi!ured *ith the '8 te$plates dual# ipv$#and#ipv% routing and lanbase#routing , respecti"ely. Depending on the router or switch model and Cisco IOS Software version, the commands available and output produced might vary from what is shown in this lab. ny chan!es $ade to the baseline confi!urations or topolo!y 3other than errors introduced are noted in the trouble tic&et so that you are a*are of the$ prior to be!innin! the troubleshootin! process.
&e'uired &esources •
•
•
routers 3Cisco I elease 15.4 or co$parable 2 $ultilayer s*itches and 1 access layer s*itch 3Cisco I elease 15.032 or co$parable *ith ast 9thernet interfaces, runnin! '8 te$plates that support I%"4/I%" addressin!/routin!/CLs +1 3%C *ith static I% address: )indo*s ; *ith 'I(, ##%, and syslo! ser"ers, plus an < client and )irehar& soft*are
•
%C-6 3'
•
%C-C 3'
•
erial and 9thernet cables
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Task (" Trouble Ticket Lab $#( TT#) Step (" &evie* trouble ticket Lab $#( TT#)+ Late yesterday afternoon, access s*itch L1 failed, and you disco"ered that the po*er supply *as not *or&in!. =unior collea!ue *as tas&ed *ith replacin! L1 *ith a co$parable s*itch. )hen you arri"ed this $ornin!, you as&ed hi $ ho* thin!s *ent. our tas& is to dia!nose the issues and restore s*itch L1 as a fully functional access s*itch on the net*or&.
Step ," Load the device trouble ticket con-iguration -iles -or TT#)+ (sin! the procedure described in the 69 Lab, "erify that the lab confi!uration files are present in flash. Load the confi!uration files indicated in the 'e"ice Confi!uration ile #able.
Note" #he follo*in! de"ice access $ethods are in effect after loadin! the confi!uration files: •
Console access re?uires no userna$e or pass*ord.
•
< re?uires userna$e cisco and pass*ord cisco.
•
#he enable pass*ord is cisco.
evice Con-iguration .ile Table evice Na!e
.ile to Load
Notes
)LS(
Lab41-L1-##--Cf!.t@t
LS(
Lab41-'L1-##--Cf!.t@t
LS,
Lab41-'L2-##--Cf!.t@t
&(
Lab41-1-##--Cf!.t@t
&,
Lab41-2-##--Cf!.t@t
&/
Lab41--##--Cf!.t@t
S&0(
/
tatic I%: 10.1.100.1 and 2001:'6A:C9:100::1 'efault !ate*ay: 10.1.100.254/24 and 2001:'6A:C9:100::'1/4
PC#B
/
'
PC#C
/
'
Step /" Con-igure S&0( and start the syslog and T.TP servers+ 9nsure that +1 has static I% addresses as indicated in the 'e"ice Confi!uration ile #able. tart the syslo! ser"er on +1, *hich is the syslo! ser"er for the entire net*or&. )hen the net*or& is properly confi!ured, all de"ices send syslo! $essa!es to +1. tart the ##% ser"er on +1, *hich is the archi"e ser"er for the entire net*or&. )hen the net*or& is properly confi!ured, all de"ices send archi"es of their runnin! confi!urations to this ser"er *hene"er the runnin!-confi! is copied to the startup confi!. 9nsure that the default ##% directory on +1 is set to the directory *here you *ant to store the archi"es.
Step $" &elease and rene* the HCP leases on PC#B and PC#C+ 9nsure that %C-6 and %C-C are confi!ured as '
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 4 of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Note" %roble$s introduced into the net*or& by the trouble tic&et $i!ht pre"ent one or both of these %Cs fro$ ac?uirin! an I% address. 'o not assi!n ei ther %C a static address.
Step 2" Outline the troubleshooting approach and validation steps+ (se this space to identify your troubleshootin! approach and the &ey steps to "erify that the proble$ is resol"ed. #roubleshootin! approaches to select fro$ include the follo*-the-path, perfor$-co$parison, botto$-up, top-do*n, di"ide-and-con?uer, shoot-fro$-the-hip, and s*ap-co$ponents 3$o"e-the-proble$ $ethods.
Note" In addition to a specific approach, you can use the !eneric troubleshootin! process: definin! a proble$, !atherin! infor$ation, analyBin! the infor$ation, eli$inatin! possible proble$ causes, for$ulatin! a hypothesis about the li&ely cause of the proble$, testin! that hypothesis, and sol"in! the proble$.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ Step %" &ecord the troubleshooting process and con-iguration changes+ (se this lo! to docu$ent your actions and results durin! the troubleshootin! process. List the co$$ands you used to !ather infor$ation and, as you pro!ress, record your thou!hts as to *ha t you thin& the proble$ $i!ht be and *hat actions you *ill ta&e to correct the proble$s. evice
)ctions and &esults
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 5 of 10
CCNPv7 TSHOOT
evice
Lab 4-1, Layer 2 Issues
)ctions and &esults
Step 7" ocu!ent trouble ticket debrie- notes+ (se this space to $a&e notes of the &ey learnin! points that you pic&ed up durin! the discussion of this trouble tic&et *ith your instructor. #he notes can include proble$s encountered, solutions applied, useful co$$ands e$ployed, alternate solutions, $ethods, and processes, and procedure and co$$unication i$pro"e$ents.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Task ," Trouble Ticket Lab $#( TT#B Step (" &evie* trouble ticket Lab $#( TT#B+ fter an e?uip$ent failure, a net*or& technician *as as&ed to confi!ure bundled 9thernet lin&s bet*een the L1 access s*itch and the t*o distribution layer s*itches in the net*or& 3'L1 and 'L2. hortly after the chan!es *ere $ade, users on L1 *ere unable to access the Internet 3si$ulated by Lo1 on 2. >ou ha"e been as&ed to loo& into the proble$ and ha"e deter$ined that you are able to pin! the Internet fro$ +1. >our tas& is to dia!nose the issues, allo* hosts on L1 to connect to the Internet "ia 'L1 or 'L2, and "erify that the s*itchin! en"iron$ent redundant paths are functional.
Note" #o si$ulate an Internet connection, you can pin! the 2 Lo1 address at 2.2.2.2. lternately, you can use the %C bro*ser to connect to 2.2.2.2. >ou *ill then be pro$pted for a lo!in to the router $ana!e$ent (I by 2. 9nter the userna$e cisco and enable pass*ord cisco .
Step ," Load the device trouble ticket con-iguration -iles -or TT#B+ (sin! the procedure described in the 69 Lab, "erify that the lab confi!uration files are present in flash. Load the confi!uration files indicated in the 'e"ice Confi!uration ile #able.
evice Con-iguration .ile Table evice Na!e
.ile to Load
Notes
)LS(
Lab41-L1-##-6-Cf!.t@t
LS(
Lab41-'L1-##-6-Cf!.t@t
LS,
Lab41-'L2-##-6-Cf!.t@t
&(
Lab41-1-##-6-Cf!.t@t
&,
Lab41-2-##-6-Cf!.t@t
&/
Lab41--##-6-Cf!.t@t
S&0(
/
tatic I%: 10.1.100.1 and 2001:'6A:C9:100::1 'efault !ate*ay: 10.1.100.254/24 and 2001:'6A:C9:100::'1/4
PC#B
/
'
PC#C
/
'
Step /" Con-igure S&0( and start the syslog and T.TP servers as described in Task (+ Step $" &elease and rene* the HCP lease -or PC#B and PC#C as described in Task (+ Step 2" Outline the troubleshooting approach and validation steps+ (se this space to identify your troubleshootin! approach and the &ey steps to "erify that the proble$ is resol"ed. . #roubleshootin! approaches to select fro$ include follo*-the-path, perfor$-co$parison, botto$-up, top-do*n, di"ide-and-con?uer, shoot-fro$-the-hip, and s*ap-co$ponents 3$o"e-the-proble$ $ethods.
Note" In addition to a specific approach, you can use the !eneric troubleshootin! process.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ © 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e ; of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Step %" &ecord the troubleshooting process and con-iguration changes+ (se this lo! to docu$ent your actions and results durin! the troubleshootin! process. List the co$$ands you used to !ather infor$ation. s you pro!ress, record *hat you thin& the proble$ $i!ht be and *hat actions you *ill ta&e to correct the proble$. evice
)ctions and &esults
Step 7" ocu!ent trouble ticket debrie- notes+ (se this space to $a&e notes of the &ey learnin! points that you pic&ed up durin! the discussion of this trouble tic&et *ith your instructor. #he notes can include proble$s encountered, solutions applied, useful co$$ands e$ployed, alternate solutions, $ethods and processes, and procedure and co$$unication i$pro"e$ents.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e A of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Task /" Trouble Ticket Lab $#( TT#C Step (" &evie* trouble ticket Lab $#( TT#C+ #his $ornin!, the help des& recei"ed a call fro$ an e@ternal consultant that needed access to the +1 !uest account 3si$ulated by pin!. our tas& is to dia!nose and sol"e this proble$, $a&in! sure that the consultant !ets access to +1.
Step ," Load the device trouble ticket con-iguration -iles -or TT#C+ (sin! the procedure described in the 69 Lab, "erify that the lab confi!uration files are present in flash. Load the confi!uration files indicated in the 'e"ice Confi!uration ile #able.
evice Con-iguration .ile Table evice Na!e
.ile to Load
Notes
)LS(
Lab41-L1-##-C-Cf!.t@t
LS(
Lab41-'L1-##-C-Cf!.t@t
LS,
Lab41-'L2-##-C-Cf!.t@t
&(
Lab41-1-##-C-Cf!.t@t
&,
Lab41-2-##-C-Cf!.t@t
&/
Lab41--##-C-Cf!.t@t
S&0(
/
tatic I%: 10.1.100.1 and 2001:'6A:C9:100::1 'efault !ate*ay: 10.1.100.254/24 and 2001:'6A:C9:100::'1/4
PC#B
/
'
PC#C
/
'
Step /" Con-igure S&0( and start the syslog and T.TP servers3 as described in Task (+ Step $" &elease and rene* the HCP lease -or PC#B and PC#C as described in Task (+ Step 2" Outline the troubleshooting approach and validation steps+ (se this space to identify your troubleshootin! approach and the &ey steps to "erify that the proble$ is resol"ed. . #roubleshootin! approaches to select fro$ include follo*-the-path, perfor$-co$parison, botto$-up, top-do*n, di"ide-and-con?uer, shoot-fro$-the-hip, and s*ap-co$ponents 3$o"e-the-proble$ $ethods.
Note" In addition to a specific approach, you can use the !eneric troubleshootin! process.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 7 of 10
CCNPv7 TSHOOT
Lab 4-1, Layer 2 Issues
Step %" &ecord the troubleshooting process and con-iguration changes+ (se this lo! to docu$ent your actions and results durin! the troubleshootin! process. List the co$$ands you used to !ather infor$ation. s you pro!ress, record your thou!hts as to *hat you thin& the proble$ $i!ht be and *hich actions you ta&e to correct the proble$. evice
)ctions and &esults
Step 7" ocu!ent trouble ticket debrie- notes+ (se this space to $a&e notes of the &ey learnin! points that you pic&ed up durin! the discussion of this trouble tic&et *ith your instructor. #he notes can include proble$s encountered, solutions applied, useful co$$ands e$ployed, alternate solutions and $ethods, and procedure and co$$unication i$pro"e$ents.
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________
© 2015 Cisco and/or its affiliates. ll ri!hts reser"ed. #his docu$ent is Cisco %ublic.
%a!e 10 of 10
