6.4.3.4 Packet Tracer - Troubleshooting Default Gateway Issues Instructions IG

7/21/2019 6.4.3.4 Packet Tracer - Troubleshooting Default Gateway Issues Instructions IG

http://slidepdf.com/reader/full/6434-packet-tracer-troubleshooting-default-gateway-issues-instructions-56d9f95d64236 1/4

Packet Tracer - Troubleshooting Default Gateway Issues

(Instructor Version)Instructor Note: Red font color or Gray highlights indicate text that appears in the instructor copy only.

Topology

Aressing Table

De!ice Interface IP Aress "ubnet #ask Default Gateway

R1G0/0 192.168.10.1 255.255.255.0 /!

G0/1 192.168.11.1 255.255.255.0 /!

"1 #$! 1 192.168.10.2 255.255.255.0 192.168.10.1

"2 #$! 1 192.168.11.2 255.255.255.0 192.168.11.1

%&1 '& 192.168.10.10 255.255.255.0 192.168.10.1

%&2 '& 192.168.10.11 255.255.255.0 192.168.10.1

%&( '& 192.168.11.10 255.255.255.0 192.168.11.1

%&) '& 192.168.11.11 255.255.255.0 192.168.11.1

$b%ecti!es

Part &' Verify Network Docuentation an Isolate Probles

Part ' Ipleent* Verify* an Docuent "olutions

+ackgroun

*or a de+ice to co,,unicate across ,ultiple net-ors it ,ust e configured -ith an '% address sunet,as and a default gate-ay. he default gate-ay is used -hen the host -ants to send a pacet to a de+iceon another net-or. he default gate-ay address is generally the router interface address attached to the

201( &isco and/or its affiliates. !ll rights reser+ed. his docu,ent is &isco %ulic. %age & of ,




local net-or to -hich the host is connected. 'n this acti+ity you -ill finish docu,enting the net-or. 3ou -illthen +erify the net-or docu,entation y testing end4to4end connecti+ity and trouleshooting issues. hetrouleshooting ,ethod you -ill use consists of the follo-ing steps:

1 #erify the net-or docu,entation and use tests to isolate prole,s.

2 eter,ine an appropriate solution for a gi+en prole,.

( ',ple,ent the solution.

) est to +erify the prole, is resol+ed.

5 ocu,ent the solution.

hroughout your &&! studies you -ill encounter different descriptions of the trouleshooting ,ethod as-ell as different -ays to test and docu,ent issues and solutions. his is intentional. here is no set standardor te,plate for trouleshooting. ach organi7ation de+elops uniue processes and docu,entation standardse+en if that process is -e don;t ha+e one<=. >o-e+er all effecti+e trouleshooting ,ethodologies generallyinclude the ao+e steps.

Note' 'f you are proficient -ith default gate-ay configurations this acti+ity ,ight see, ,ore in+ol+ed than itshould e. 3ou can ,ost liely uicly disco+er and sol+e all the connecti+ity issues faster than follo-ingthese procedures. >o-e+er as you proceed in your studies the net-ors and prole,s you encounter -ill

eco,e increasingly ,ore co,plex. 'n such situations the only effecti+e -ay to isolate and sol+e issues is touse a ,ethodical approach such as the one used in this acti+ity.

Verify Network Docuentation an Isolate Probles

'n %art 1 of this acti+ity co,plete the docu,entation and perfor, connecti+ity tests to disco+er issues. 'naddition you -ill deter,ine an appropriate solution for i,ple,entation in %art 2.

"tep &' Verify the network ocuentation an isolate any probles

a. ?efore you can effecti+ely test a net-or you ,ust ha+e co,plete docu,entation. otice in theAressing Table that so,e infor,ation is ,issing. &o,plete the Aressing Table y filling in the,issing default gate-ay infor,ation for the s-itches and the %&s.

. est connecti+ity to de+ices on the sa,e net-or. ?y isolating and correcting any local access issuesyou can etter test re,ote connecti+ity -ith the confidence that local connecti+ity is operational.

! +erification plan can e as si,ple as a list of connecti+ity tests. @se the follo-ing tests to +erify localconnecti+ity and isolate any access issues. he first issue is already docu,ented ut you ,usti,ple,ent and +erify the solution during %art 2.

Testing an Verification Docuentation

est"uccessful

A 'ssues "olution #erified

P.& to P. No IP aress on P.& .hange P.& IP aress

%&1 to "1

%&1 to R1

201( &isco and/or its affiliates. !ll rights reser+ed. his docu,ent is &isco %ulic. %age of ,




Note' he tale is an exa,pleB you ,ust create your o-n docu,ent. 3ou can use paper and pencil todra- a tale or you can use a text editor or spreadsheet. &onsult your instructor if you need furtherguidance.

c. est connecti+ity to re,ote de+ices such as fro, %&1 to %&)= and docu,ent any prole,s. his isfreuently referred to as end-to-end connectivity . his ,eans that all de+ices in a net-or ha+e the fullconnecti+ity allo-ed y the net-or policy.

Note' Re,ote connecti+ity testing ,ay not e possile yet ecause you ,ust first resol+e localconnecti+ity issues. !fter you ha+e sol+ed those issues return to this step and test connecti+ity et-eennet-ors.

"tep ' Deterine an appropriate solution for the proble

a. @sing your no-ledge of the -ay net-ors operate and your de+ice configuration sills search for thecause of the prole,. *or exa,ple "1 is not the cause of the connecti+ity issue et-een %&1 and %&2.he lin lights are green and no configuration on "1 -ould cause traffic to not pass et-een %&1 and%&2. "o the prole, ,ust e -ith %&1 %&2 or oth.

. #erify the de+ice addressing to ensure it ,atches the net-or docu,entation. *or exa,ple the '%address for %&1 is incorrect as +erified -ith the ipconfig co,,and.

c. "uggest a solution that you thin -ill resol+e the prole, and docu,ent it. *or exa,ple change the '%address for %&1 to ,atch the docu,entation.

Note' Cften there is ,ore than one solution. >o-e+er it is a trouleshooting est practice to i,ple,entone solution at a ti,e. ',ple,enting ,ore than one solution could introduce additional issues in a ,oreco,plex scenario.

Part ' Ipleent* Verify* an Docuent "olutions

'n %art 2 of this acti+ity you -ill i,ple,ent the solutions you identified in %art 1. 3ou -ill then +erify thesolution -ored. 3ou ,ay need to return to %art 1 to finish isolating all the prole,s.

"tep &' Ipleent solutions to connecti!ity probles

Refer to your docu,entation in %art 1. &hoose the first issue and i,ple,ent your suggested solution. *orexa,ple correct the '% address on %&1.

"tep ' Verify that the proble is now resol!e

a. #erify your solution has sol+ed the prole, y perfor,ing the test you used to identify the prole,. *orexa,ple can %&1 no- ping %&2A.

. 'f the prole, is resol+ed indicate so in your docu,entation. *or exa,ple in the tale ao+e a si,plechec,ar -ould suffice in the #erified< colu,n.

"tep /' Verify that all issues are resol!e

a. 'f you still ha+e an outstanding issue -ith a solution that has not yet een i,ple,ented return to %art 2

"tep 1.

. 'f all your current issues are resol+ed ha+e you also resol+ed any re,ote connecti+ity issues such ascan %&1 ping %&)=A 'f the ans-er is no return to %art 1 "tep 1c to test re,ote connecti+ity.

Issues

• %&1 cannot ping %&2 ecause %&1 has an '% address that does not elong to the net-or %&1 is

attached to.

201( &isco and/or its affiliates. !ll rights reser+ed. his docu,ent is &isco %ulic. %age / of ,




• e+ices cannot ping "2 and "2 cannot ping any de+ice ecause "2 is ,issing an '% address.

• Re,ote de+ices cannot ping %&) ecause %&) has the -rong default gate-ay configured.

• Re,ote de+ices cannot ping "1 ecause "1 is ,issing a default gate-ay configuration.

"uggeste "coring 0ubric

TaskPossiblePoints

1arnePoints

.oplete Network Docuentation 2

Docuent Issues an "olutions ,3

Packet Tracer "core (Issues 0esol!e) /3

Total "core &22

201( &isco and/or its affiliates. !ll rights reser+ed. his docu,ent is &isco %ulic. %age , of ,

Documents

6.4.3.4 Packet Tracer - Troubleshooting Default Gateway Issues Instructions IG