NETW412Lab4

(1)

Davenport University Davenport University

Pete Anderson Pete Anderson

(2)

CCNPv TSHOOT CCNPv TSHOOT

Cha%ter  Lab !1" La#er 2 $ssues

P!ysica" Topo"o#y

(3)

(4)

Ob$ectives

• Load the device configuration files for each trouble tic'et. • (iagnose and resolve La#er 2 connectivit# %roblems. • (iagnose and resolve s%anning!tree %roblems.

• (ocument the troubleshooting %rogress" configuration changes" and %roblem resolution.

%ack#ro&nd

)ser com%uters" servers" and %rinters all connect to the access la#er of the hierarchical model. *ith hundreds or thousands of hosts attached" access devices such as La#er 2 s+itches are a common source of

net+or'ing issues. Ph#sical and data!lin' %roblems at the access la#er can include hard+are" cabling" ,LA-assignment" s%anning tree" trun'ing %rotocol" or %ort securit# issues.

$n this lab" #ou +ill troubleshoot various La#er 2 %roblems. or each tas' or trouble tic'et" the scenario and s#m%toms are described. *hile troubleshooting" #ou +ill discover the cause of the %roblem" correct it" and then document the %rocess and results.

P!ysica" and Lo#ica" Topo"o#y Dia#ra's

The %h#sical and logical to%ologies are %rovided at the beginning of the lab" including interface designations and $Pv/$Pv addresses" to assist the troubleshooting effort.

Note( This lab uses Cisco $ 2 routers running Cisco $3 15.4& images +ith $P 6ase and ecurit# %ac'ages enabled" and Cisco Catal#st &50 and 270 s+itches running Cisco $3 15.042 $P ervices and LA- 6ase images" res%ectivel#. The &50 and 270 s+itches are configured +ith the (8 tem%lates d&a") ipv4)and)ipv* ro&tin# and "anbase)ro&tin# " res%ectivel#. 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. An# changes made to the baseline configurations or to%olog# 4other than errors introduced are noted in the trouble tic'et so that #ou are a+are of them %rior to beginning the troubleshooting %rocess.

+e&ired +eso&rces

• & routers 4Cisco $3 elease 15. or com%arable

• 2 multila#er s+itches and 1 access la#er s+itch 4Cisco $3 elease 15.042 or com%arable +ith ast

9thernet interfaces" running (8 tem%lates that su%%ort $Pv/$Pv addressing/routing/ACLs

• ,1 4PC +ith static $P address: *indo+s ; +ith A($)" TTP" and s#slog servers" %lus an <

client and * irehar' soft+are

• PC!6 4(<CP client: *indo+s ; +ith < client and *irehar' soft+are • PC!C 4(<CP client: *indo+s ; +ith < client and *irehar' soft+are • erial and 9thernet cables

(5)

Task -( Tro&b"e Ticket Lab 4)- TT)A

Step -( +evie. tro&b"e ticket Lab 4)- TT)A/

Late #esterda# afternoon" access s+itch AL1 failed" and #ou discovered that the %o+er su%%l# +as not +or'ing. A =unior colleague +as tas'ed +ith re%lacing AL1 +ith a com%arable s+itch.

*hen #ou arrived this morning" #ou as'ed him ho+ things +ent. <e told #ou that he had sta#ed late tr#ing to reconfigure AL1" but +as not entirel# successful. )sers on ,LA- 120 have started to com%lain that the# cannot get access to the net+or' server ,1" and #ou are unable to use < to connect to AL1 from ,1. $n

addition" s#slog messages from AL1 are not being received on ,1.

>our tas' is to diagnose the issues and restore s+itch AL1 as a full# functional access s+itch on the net+or'.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)A/

)sing the %rocedure described in the 6A9 Lab" verif# that the lab configuration files are %resent in flash. Load the configuration files indicated in the (evice Configuration ile Table.

Note( The follo+ing device access methods are in effect after loading the configuration files:

• Console access re?uires no username or %ass+ord. • < re?uires username cisco and %ass+ord cisco. • The enable %ass+ord is cisco.

Device Con1i#&ration 2i"e Tab"e

Device Na'e 2i"e to Load Notes

ALS- Lab1!AL1!TT!A!Cfg.t@t DLS- Lab1!(L1!TT!A!Cfg.t@t DLS0 Lab1!(L2!TT!A!Cfg.t@t +- Lab1!1!TT!A!Cfg.t@t +0 Lab1!2!TT!A!Cfg.t@t +3 Lab1!&!TT!A!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1

(efault gate+a#: 10.1.100.25/2 and 2001:(6:CA9:100::(1/

PC)% -/A (<CP 4release and rene+ for $Pv and $Pv after loading device configurations PC)C -/A (<CP 4release and rene+ for $Pv and $Pv after loading device configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers/

9nsure that ,1 has static $P addresses as indicated in the (evice Configuration ile Table.

tart the s#slog server on ,1" +hich is the s#slog server for the entire net+or'. *hen the net+or' is %ro%erl# configured" all devices send s#slog messages to ,1.

tart the TTP server on ,1" +hich is the archive server for the entire net+or'. *hen the net+or' is %ro%erl# configured" all devices send archives of their running configurations to this server +henever the running!config is co%ied to the startu% config. 9nsure that the default TTP director# on ,1 is set to the d irector# +here #ou +ant to store the archives.

Step 4( +e"ease and rene. t!e DHCP "eases on PC)% and PC)C/

(6)

After loading all TT!A device configuration files" issue the ipcon1i# 5re"ease and ipcon1i# 5rene. commands on PC!6 and PC!C.

Note( Problems introduced into the net+or' b# the trouble tic'et might %revent one or both of these PCs from ac?uiring an $P address. (o not assign either PC a static address.

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

)se this s%ace to identif# #our troubleshooting a%%roach and the 'e# ste%s to verif# that the %roblem is resolved. Troubleshooting a%%roaches to select from include the follo+!the!%ath" %erform!com%arison" bottom!u%" to%!do+n" divide!and!con?uer" shoot!from!the!hi%" and s+a%!com%onents 4move!the!%roblem methods.

Note( $n addition to a s%ecific a%%roach" #ou can use the generic troubleshooting %rocess: defining a %roblem" gathering information" anal#Bing the information" eliminating %ossible %roblem causes" formulating a h#%othesis about the li'el# cause of the %roblem" testing that h#%othesis" and solving the %roblem.

Follow-the-path and divide-and-conquer approach________________________________________ _________________________________________________________________________________ We will know the issue is resolved when we can get a DHCP address on PC-B and C_____________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

)se this log to document #our actions and results during the troubleshooting %rocess. List the commands #ou used to gather information and" as #ou %rogress" record #our thoughts as to +hat #ou thin' the %roblem might be and +hat actions #ou +ill ta'e to correct the %roblems.

Device Actions and +es&"ts

AL1 emoved stic'# mac addresses so PC!6 could be learned 1!& $ssued no!shutdo+n command on gig interfaces

AL1 %anning!tree mode +as mst. +itched to ra%id!%vst

(7)

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

)se this s%ace to ma'e notes of the 'e# learning %oints that #ou %ic'ed u% during the discussion of this trouble tic'et +ith #our instructor. The notes can include %roblems encountered" solutions a%%lied" useful commands em%lo#ed" alternate solutions" methods" and %rocesses" and %rocedure and communication im%rovements.

Spanning tree will not work when devices are configured with multiple modes. Key commands we used were “show run,” “show run | beg Span,” to determine what looked off among all the devices. _____ _________________________________________________________________________________ The problems we encountered with lab might not have been directly connected to the lab, but we could not get our FA0/1-4 on ALS1 and FA0/1-2 on DLS1 to come back up. We had to save the configuration and reboot the devices. After reboot, we turned on those ports and they came up. ________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(8)

Task 0( Tro&b"e Ticket Lab 4)- TT)%

Step -( +evie. tro&b"e ticket Lab 4)- TT)%/

After an e?ui%ment failure" a net+or' technician +as as'ed to configure bundled 9thernet lin's bet+een the AL1 access s+itch and the t+o distribution la#er s+itches in the net+or' 4(L1 and (L2. hortl# after the changes +ere made" users on AL1 +ere unable to access the $nternet 4simulated b# Lo1 on 2. >ou have been as'ed to loo' into the %roblem and have determined that #ou are able to %ing the $nternet from ,1.

>our tas' is to diagnose the issues" allo+ hosts on AL1 to connect to the $nternet via (L1 o r (L2" and verif# that the s+itching environment redundant %aths are functional.

Note( To simulate an $nternet connection" #ou can %ing the 2 Lo1 address at 2.2.2.2. Alternatel#" #ou can use the PC bro+ser to connect to 2.2.2.2. >ou +ill then be %rom%ted for a login to the router management )$ b# 2. 9nter the username cisco and enable %ass+ord cisco.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)%/

ALS- Lab1!AL1!TT!6!Cfg.t@t DLS- Lab1!(L1!TT!6!Cfg.t@t DLS0 Lab1!(L2!TT!6!Cfg.t@t +- Lab1!1!TT!6!Cfg.t@t +0 Lab1!2!TT!6!Cfg.t@t +3 Lab1!&!TT!6!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1 (efault gate+a#: 10.1.100.25/2 and

2001:(6:CA9:100::(1/

PC)% -/A (<CP 4release and rene+ for $Pv and $Pv after loading device configurations

PC)C -/A (<CP 4release and rene+ for $Pv and $Pv after loading device configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers as described in Task -/

Step 4( +e"ease and rene. t!e DHCP "ease 1or PC)% and PC)C as described in Task -/

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

)se this s%ace to identif# #our troubleshooting a%%roach and the 'e# ste%s to verif# that the %roblem is resolved. . Troubleshooting a%%roaches to select from include follo+!the!%ath" %erform!com%arison" bottom!u%" to%!do+n" divide!and!con?uer" shoot!from!the!hi%" and s+a%!com%onents 4move!the!%roblem methods.

Note( $n addition to a s%ecific a%%roach" #ou can use the generic troubleshooting %rocess.

Follow-the-path approach divide-and-conquer approach___________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(9)

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

)se this log to document #our actions and results during the troubleshooting %rocess. List the commands #ou used to gather information. As #ou %rogress" record +hat #ou thin' the %roblem might be and +hat actions #ou +ill ta'e to correct the %roblem.

(L2 9nca%sulation +as isl for A0/1!2. Changed that to dot1?.

(L1 9nca%sulation +as isl for PortChannel 1. Changed that to dot1?.

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

)se this s%ace to ma'e notes of the 'e# learning %oints that #ou %ic'ed u% during the discussion of this trouble tic'et +ith #our instructor. The notes can include %roblems encountered" solutions a%%lied" useful commands em%lo#ed" alternate solutions" methods and %rocesses" and %rocedure and communication im%rovements.

Commands used included “show etherchannel summary,” “show run | beg interface”_____________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(10)

Task 3( Tro&b"e Ticket Lab 4)- TT)C

Step -( +evie. tro&b"e ticket Lab 4)- TT)C/

This morning" the hel% des' received a call from an e@ternal consultant that needed access to the ,1 guest account 4simulated b# %ing. <er PC" PC!C" +as %lugged into one of the outlets that is %atched to the guest ,LA-on s+itch (L2. <o+ever" she has not been able to get an $Pv address and cannot get ,LA-onto the net+or'.

>our tas' is to diagnose and solve this %roblem" ma'ing sure that the consultant gets access to ,1.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)C/

ALS- Lab1!AL1!TT!C!Cfg.t@t DLS- Lab1!(L1!TT!C!Cfg.t@t DLS0 Lab1!(L2!TT!C!Cfg.t@t +- Lab1!1!TT!C!Cfg.t@t +0 Lab1!2!TT!C!Cfg.t@t +3 Lab1!&!TT!C!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1 (efault gate+a#: 10.1.100.25/2 and

2001:(6:CA9:100::(1/

PC)% -/A (<CP 4release and rene+ for $Pv and $Pv after loading device configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers, as described in Task -/

Step 4( +e"ease and rene. t!e DHCP "ease 1or PC)% and PC)C as described in Task -/

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

)se this s%ace to identif# #our troubleshooting a%%roach and the 'e# ste%s to verif# that the %roblem is resolved. . Troubleshooting a%%roaches to select from include follo+!the!%ath" %erform!com%arison" bottom!u%" to%!do+n" divide!and!con?uer" shoot!from!the!hi%" and s+a%!com%onents 4move!the!%roblem methods.

Follow-the-path divide-and-conquer approach___________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(11)

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

)se this log to document #our actions and results during the troubleshooting %rocess. List the commands #ou used to gather information. As #ou %rogress" record #our thoughts as to +hat #ou thin' the %roblem might be and +hich actions #ou ta'e to correct the %roblem.

(L2 Trun' lin's +ere not allo+ing ,lan 110 4uest. Added the configuration to allo+ 110

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

)se this s%ace to ma'e notes of the 'e# learning %oints that #ou %ic'ed u% during the discussion of this trouble tic'et +ith #our instructor. The notes can include %roblems encountered" solutions a%%lied" useful commands em%lo#ed" alternate solutions and methods" and %rocedure and communication im%rovements.

Commands used included “show run”

Compared the running config with DLS1 and DLS2 to notice that Vlan110 was not being allowed on DLS2____________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(12)

CCNPv TSHOOT

Cha%ter  Lab !2" 8i@ed La#er 2!& Connectivit#

P!ysica" Topo"o#y

(13)

(14)

(15)

Ob$ectives

• Load the trouble tic'et device configuration files for each trouble tic'et.

• (iagnose and resolve %roblems related to s+itch virtual interfaces and multila#er s+itching. • (iagnose and resolve %roblems related to irst <o% edundanc# Protocols.

• (ocument troubleshooting %rogress" configuration changes" and %roblem resolution.

%ack#ro&nd

8ultila#er s+itches have the ca%abilit# to act as routers b# +a# of s+itch virtual interfaces 4,$s" routed interfaces" and routing %rotocols. ,$s are La#er & logical interfaces re%resenting ,LA-s and routed %orts are La#er & %h#sical interfaces. 8ultila#er s+itches are fre?uentl# used as %art of the LA- s+itch fabric and can be configured +ith a irst <o% edundanc# Protocol 4<P. T+o or more La#er & s+itches 4or routers can %rovide redundant %aths to the net+or' edge for local hosts. A host is configured +ith a virtual default

gate+a# address. $f one of the gate+a#s goes do+n" the other can ta'e over for the client +ithout the clients 'no+ledge. <Ps used in CC-Pv;.0 are <ot tandb# outer Protocol 4<P" ,irtual outer edundanc# Protocol 4,P" and ate+a# Load 6alancing Protocol 4L6P.

$n this lab" #ou +ill troubleshoot %roblems related to La#er & s+itching and <Ps. or each tas' or trouble tic'et" the scenario and %roblem s#m%toms are described. *hile troubleshooting" #ou +ill discover the cause of the %roblem" correct it" and then document the %rocess and results.

P!ysica" and Lo#ica" Topo"o#y Dia#ra's

The %h#sical and logical to%ologies" including interface designations and $Pv/$Pv addresses" are %rovided to assist the troubleshooting effort.

Note( This lab uses Cisco $ 2 routers running Cisco $3 15.4& images +ith $P 6ase and ecurit# %ac'ages enabled" and Cisco Catal#st &50 and 270 s+itches running Cisco $3 15.042 $P ervices and LA- 6ase images" res%ectivel#. The &50 and 270 s+itches are configured +ith the (8 tem%lates d&a") ipv4)and)ipv* ro&tin# and "anbase)ro&tin# " res%ectivel#. 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. An# changes made to the baseline configurations or to%olog# 4other than errors introduced are noted in the trouble tic'et so that #ou are a+are of them %rior to beginning the troubleshooting %rocess.

+e&ired +eso&rces

• & routers 4Cisco $3 elease 15. or com%arable

• 2 multila#er s+itches and 1 access la#er s+itch 4Cisco $3 elease 15.042 or com%arable +ith ast

9thernet interfaces

• ,1 4PC +ith static $P address: *indo+s ; +ith A($)" TTP" and s#slog servers" %lus an <

client and * irehar' soft+are

• PC!6 4(<CP client: *indo+s ; +ith < client and *irehar' soft+are • PC!C 4(<CP client: *indo+s ; +ith < client and *irehar' soft+are

(16)

Task -( Tro&b"e Ticket Lab 4)0 TT)A

Step -( +evie. tro&b"e ticket Lab 4)0 TT)A/

(uring last rida#s maintenance +indo+" a series of failover tests at head?uarters and the branch offices +ere e@ecuted. $t +as discovered during a reboot of s+itch (L1 that connectivit# bet+een clients in 3$C9 ,LA-120 and the $nternet +as lost. After router (L1 came bac' online" the clients regained connectivit#. This +as not the e@%ected behavior" because the net+or' %rovides gate+a# first!ho% redundanc# for clients in the 3$C9 to ensure correct failover during outages: $f one of the <P s+itches fails" the hosts on the 3$C9 ,LA-should still be able to access the $nternet 4b# %inging 2 Lo1 2.2.2.2 during the outage.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)A/

)sing the %rocedure described in the 6A9 Lab" verif# that the lab configuration files are %resent in flash. Load the %ro%er configuration files indicated in the (evice Configuration ile Table.

Note( >ou can test the simulated $nternet access b# o%ening a bro+ser and entering the $P address o f the 2 Lo1 interface 2.2.2.2. >ou +ill be %rom%ted for a username and %ass+ord. >ou can gain access to the router )$ management interface b# entering username cisco and the enable %ass+ord cisco.

ALS- Lab2!AL1!TT!A!Cfg.t@t DLS- Lab2!(L1!TT!A!Cfg.t@t DLS0 Lab2!(L2!TT!A!Cfg.t@t +- Lab2!1!TT!A!Cfg.t@t +0 Lab2!2!TT!A!Cfg.t@t +3 Lab2!&!TT!A!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1

(efault gate+a#: 1 0.1.100.25/2 and 2001:(6:CA9:100::(1/ PC)% -/A (<CP 4release and rene+ for $Pv and $Pv after loading device

configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers/

a. 9nsure that ,1 has the static $P address 10.1.100.1 and default gate+a# 10.1.100.25.

b. tart the s#slog server on ,1" +hich is the s#slog server for the entire net+or'. *hen the net+or' is %ro%erl# configured" all devices send s#slog messages to ,1.

c. tart the TTP server on ,1" +hich is the archive server for the entire net+or'. *hen the net+or' is %ro%erl# configured" all devices send archives of their running configurations to this server

+henever the running config is co%ied to the startu% config. 9nsure that the default TTP director# on ,1 is set to the director# +here #ou +ant to store the archives.

Step 4( +e"ease and rene. t!e DHCP "eases on PC)% and PC)C/

a. 9nsure that PC!6 and PC!C are configured as (<CP clients.

b. After loading all TT!A device configuration files" issue theipconfig/release and

ipconfig/renew commands on PC!6 and PC!C. >ou might need to re%eat this %rocess after the TT %roblems have been resolved.

Note( Problems introduced into the net+or' b# the trouble tic'et might %revent one or both of the PCs from ac?uiring an $P address. Be sure to attempt to release and renew the DHCP leases on PCB and PCC! Do not assign either PC a static address!

(17)

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

)se this s%ace to identif# #our troubleshooting a%%roach and the 'e# ste%s to verif# that the %roblem is resolved. Troubleshooting a%%roaches to select from include the follo+!the!%ath" %erform!com%arison" bottom!u%" to%!do+n" divide!and!con?uer" shoot!from!the!hi%" and s+a%!com%onents 4move!the!%roblem methods.

Note( $n addition to a s%ecific a%%roach" #ou can use the generic troubleshooting %rocess: defining a %roblem" gathering information" anal#Bing the information" eliminating %ossible %roblem causes" formulating a h#%othesis about the li'el# cause of the %roblem" testing that h#%othesis" and solving the %roblem.

Follow-the-path divide-and-conquer approach___________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

(L1 (efault router for 3ffice vlan +as set to 10.1.120.252. Changed that address from the stand# address to: 10.1.120.25

(18)

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

)se this s%ace to ma'e notes of the 'e# learning %oints that #ou %ic'ed u% during the discussion of this trouble tic'et +ith #our instructor. The notes can include %roblems encountered" solutions a%%lied" and useful commands em%lo#ed. $t can also include a lternate solutions" methods" and %rocedures and communication im%rovements.

Command used: “show run”__________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

Task 0( Tro&b"e Ticket Lab 4)0 TT)%

Step -( +evie. tro&b"e ticket Lab 4)0 TT)%/

)%on arriving at the office this morning" #ou find the follo+ing tic'et in the s#stem:

+itch AL1 has been sho+ing CC errors on a grou% of eight %orts for several da#s. $t +as sus%ected that

hard+are +as the cause. (uring #esterda# evenings maintenance +indo+" the s+itch +as re%laced +ith a similar s+itch from the lab. After this re%lacement" clients could connect" and no errors +ere sho+n on the %orts.

<o+ever" ma'ing a bac'u% of the AL1 configuration to server ,1 did not +or'" and no s#slog messages from AL1 are being received b# ,1. The s+itch is not reachable via < from server ,1. There +as no time for further research #esterda# so" because there is no im%act to users" it +as decided to leave the s+itch and %ic' u% this issue the ne@t da#.

>our tas' is to diagnose the issue and restore connectivit# bet+een s+itch AL1 and server ,1. After resolving the %roblem" ma'e a bac'u% of the configuration to server ,1.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)%/

Load the %ro%er configuration files indicated in the (evice Configuration ile Table.

Note( The follo+ing device access methods are in effect after loading the configuration files:

• Console access re?uires no username or %ass+ord. • < re?uires the username ad'in and %ass+ord cisco. • The enab"e %ass+ord is cisco.

ALS- Lab2!AL1!TT!6!Cfg.t@t DLS- Lab2!(L1!TT!6!Cfg.t@t DLS0 Lab2!(L2!TT!6!Cfg.t@t +- Lab2!1!TT!6!Cfg.t@t +0 Lab2!2!TT!6!Cfg.t@t +3 Lab2!&!TT!6!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1

(efault gate+a#: 10.1.100.25/2 and 2001:(6:CA9:100::(1/ PC)% -/A (<CP 4release and rene+ for $Pv and $Pv after loading device

(19)

configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers, as described in Task -/

Step 4( +e"ease and rene. t!e DHCP "eases on PC)% and PC)C, as described in Task -/

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

)se this s%ace to identif# #our troubleshooting a%%roach and the 'e# ste%s to verif# that the %roblem is resolved. Troubleshooting a%%roaches to select from include follo+!the!%ath" %erform!com%arison" bottom!u%" to%!do+n" divide!and!con?uer" shoot!from!the!hi%" and s+a%!com%onents 4move!the!%roblem methods.

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

& 0/1 subnet +as 255.255.255.252. Changed that to 255.255.255.0 (L1 a0/5 subnet +as 255.255.255.252. Changed that to 255.255.255.0 AL1 $P addesses for each vlan +ere set to @.10.@.@ instead of @.1.@.@

(20)

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

)se this s%ace to ma'e notes of the 'e# learning %oints that #ou %ic'ed u% during the discussion of this trouble tic'et +ith #our instructor. The notes can include %roblems encountered" solutions a%%lied" useful commands em%lo#ed" alternate solutions" methods and %rocesses" and %rocedure and communication im%rovements.

Used syslog server to determine we had a subnet issue on Router 3 and DLS1

Used the command “show ip int brief,” “show run,” “show run | begin interface”________________ Show ip int brief told us that the ip addresses were not set correctly___________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

Task 3( Tro&b"e Ticket Lab 4)0 TT)C

Step -( +evie. tro&b"e ticket Lab 4)0 TT)C/

8ar# %erformed a %ass+ord recover# on AL1 last night after hours so that no users +ould be affected. This morning no trouble tic'ets +ere %osted and a%%arentl# em%lo#ees have normal net+or' access. >ou +ent to reconfigure a s+itch %ort on AL1 to the 3$C9 ,LA- for a ne+ cubicle" but %ing" Telnet" and < to AL1 via $Pv are failing from the $P management station at 10.1.202.1. >ou can %ing AL1 interfaces using $Pv. >ou tr# to < via $Pv" but #ou get the message % Connection refused by remote hostD #ou then recall

baseline %olic# dictates AL1 to have an $Pv ACL a%%lied to its vt# lines to %revent $Pv access.

>ou chec' the logs on ,1 and notice that all net+or' devices indicate %eriodic entries from this morning" e@ce%t AL1. >ou can < into (L1 and (L2" +hich have net+or's in common +ith AL1D thin'ing that it ma# be easier to attem%t < from a device on the same net+or' as ,LA- 77" #ou tr# to < from ,$ 77 on (L1 directl# to ,$ 77 on AL1. 6ut 8ar# changed the account information for remote access on AL1E >ou have no o%tion but to console into AL1 to troubleshoot F fortunatel# #ou still have console access. >our tas' is to

reestablish remote access functionalit# to AL1 via $Pv from the $P management station and reestablish logging to ,1 from AL1.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)C/

Load the %ro%er configuration files indicated in the (evice Configuration ile Table. Device Con1i#&ration 2i"e Tab"e

ALS- Lab2!AL1!TT!C!Cfg.t@t

(21)

DLS- Lab2!(L1!TT!C!Cfg.t@t DLS0 Lab2!(L2!TT!C!Cfg.t@t +- Lab2!1!TT!C!Cfg.t@t +0 Lab2!2!TT!C!Cfg.t@t +3 Lab2!&!TT!C!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1

configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers, as described in Task -/

Step 4( +e"ease and rene. t!e DHCP "eases on PC)% and PC)C, as described in Task -/

Step 6( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

Step *( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

AL1 Changed the login bac' to username cisco secret cisco AL1 Changed sdm tem%late to Glanbase routingH

(22)

Step ( Doc&'ent tro&b"e ticket debrie1 notes/

Performed do show ip route on ALS1 and noticed there weren’t any routes. We needed IP Routing turned on

Before we enter the configs, we check the “sdm template” __________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

Task 4( Tro&b"e Ticket Lab 4)0 TT)D

Step -( +evie. tro&b"e ticket Lab 4)0 TT)D/

>ou assigned Iohn the tas' of securing the <P im%lementation +ith 8(5 authentication on the 9,9 ,LA-. After Iohn com%letes the tas'" initial re%orts are %romising" but turn out to be %remature. ome com%an# guests are com%laining about intermittent server access that seems to correlate +ith the <P authentication changes. Iohn often %erforms above!and!be#ond e@%ectations" and he too' it u%on himself to im%rove LA-securit# b# adding configuration commands on the multila#er s+itches to %revent traffic storms. >our tas' is to revie+ and verif# the im%lementation of <P and fi@ issues that remain to return the net+or' to a stable state.

Step 0( Load t!e device tro&b"e ticket con1i#&ration 1i"es 1or TT)D/

Load the %ro%er configuration files indicated in the (evice Configuration ile Table. Device Con1i#&ration 2i"e Tab"e

ALS- Lab2!AL1!TT!(!Cfg.t@t DLS- Lab2!(L1!TT!(!Cfg.t@t

(23)

DLS0 Lab2!(L2!TT!(!Cfg.t@t +- Lab2!1!TT!(!Cfg.t@t +0 Lab2!2!TT!(!Cfg.t@t +3 Lab2!&!TT!(!Cfg.t@t

S+- -/A tatic $P: 10.1.100.1 and 2001:(6:CA9:100::1

configurations

Step 3( Con1i#&re S+- and start t!e sys"o# and T2TP servers, as described in Task -/

Step 4( +e"ease and rene. t!e DHCP "eases on PC)% and PC)C, as described in Task -/

Step 6( Si'&"ate tra11ic "oad 1ro' PC)C to S+-/

imulate server traffic load on from com%an# guests: 9nter the user 9J9C mode commands ttcp receive on 1 and ttcp transmit 10.1.2.2 on &. A TTCP session can be sto%%ed b# entering CtrlKhiftK follo+ed b# @. eenter the TTCP commands on 1 and & as necessar# throughout this tic'et.

To simulate the intermittent server access e@%erienced b# com%an# guests" enter ping -t -l 19500 10.1.100.1 on PC!C F antivirus and fire+all soft+are ma# need to be disabled on some PCs to %ermit this command. $f re?uests are %eriodicall# timing out then the server access issue has not been resolvedE

Step *( O&t"ine t!e tro&b"es!ootin# approac! and va"idation steps/

Step ( +ecord t!e tro&b"es!ootin# process and con1i#&ration c!an#es/

Note( >ou might need to issue the ipcon1i# 5re"ease and ipcon1i# 5rene. commands on (<CP clients after the net+or' device %roblems are resolved.

(L2 6oost the PP to 200 instead of 15 (L1 6oost the PP to 200 instead of 15 (L1 Changed the %ass+ord in the e#!string (L2 Changed the %ass+ord in the e#!string

(24)

T+o useful commands for this tic'et are described belo+. $n this tic'et the focus is on the unicast o%tion.

Co''and 7ey 8n1or'ation Disp"ayed

s!o. stor')contro" Minterfaceid N Mbroadcast 9 '&"ticast 9 &nicastN

(is%la#s storm control su%%ression levels set on the s%ecified interface for the s%ecified traffic t#%e. $nterfaces +ill a%%ear as "orwarding or Bloc#ing or $in# Down.

s!o. "o##in#

(is%la#s the state of s#slog error and event logging" and +hether console logging is enabled. $t also dis%la#s -8P configuration %arameters.

Step :( Doc&'ent tro&b"e ticket debrie1 notes/

We used “show storm-control unicast” to verify that the pps was too low for the network

We used “show run | begin Interface” to see what port channels had configured for storm control We used “show run” and noticed that the key-string passwords on DLS1 and DLS2 did not match__ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________

(25)

_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________