CCNA Troubleshooting Tid-bits....
Netstudent
Member Posts: 1,693 ■■■□□□□□□□
in CCNA & CCENT
Here are some quotes from the exam blue-print.
"The exam covers topics on Extending Switched Networks with VLANS, Determining IP Routes, Managing IP traffic with Access Lists, Establishing Point-to-Point connections, and Establishing Frame Relay Connections."
So everyone should know that there is a very good chance that you could get a SIM covering anyone of these topics. Thats a given!
Here is Another Quote:
CCNA Troubleshooting includes:
Utilize the OSI model as a guide for systematic network troubleshooting
Perform LAN and VLAN troubleshooting
Troubleshoot routing protocols
Troubleshoot IP addressing and host configuration
Troubleshoot a device as part of a working network
Troubleshoot an access list
Perform simple WAN troubleshooting
So lets say you are sitting in front of a router in a job interview for your first job and the interviewer required you to gather information about what is wrong and how to fix it, but he didn't tell you anything else. This is a basic troubleshooting type of problem, and everyone should know that they exist because of the Blueprint.
These are the types of questions you should be asking yourself and trying to answer as you implement the troubleshooting process.
What type of encapsulation is being used? Is this PPP, frame-relay, ISDN
Once you figure out what type of network is being used, you can begin to troubleshoot the network based on what you know about the technologies that are being used.
You have to be able to use all your show commands to figure out the network. Find your routes/routing protocols, look at the IP addressing, ping around, look at your interfaces, Line up? prototcol up? Find the problem!
DLCI/PVC problem? IP addressing problem? incorrect VLAN/Trunk/default gateway problem? PPP/CHAP problem? I think you have to first snoop around, and then begin the troubleshooting process.
you must be extremely analytical to solve these types of problems. In the real world YOU MUST have analytical skill. You have to be able to use all the facts you know about the technologies, and run with it to solve complex problems. Is your boss going to come up to you and say "okay Beavis we have a problem, is the solution A B C or D? No, you have to figure that out on your own.
Also look at the devices they give you access to. If they only give you access to 2 routers and a switch, well then this may be a VLAN probelm and it may be a routing problem. If they only gave you access to one router, then it could be a routing problem. You have to be able to take in all the information they give you, and read between the lines.
Also look at the answer choices to see what genre of problem the question pertains to.
Never forget that the answer is staring you right in the face.
I suggest people do Suduko puzzles to help you work on being analytical. It may sound stupid, but it's all about how you think.
One other thing, If they instruct you to telnet somewhere, then you know that layer 2 and 3 between the source and destination is just fine or you would not have been able to telnet to it right?
If you could not telnet into the router and that is a problem, then check ACL's, make sure you have a LINE VTY password set on the destination router.
Overall, just master the main topics and know everything about it. You can't analyze a complex problem with minimal knowledge of the technology being used.
Being analytical requires knowing the facts, and practice, and a detailed way of thinking.
For people with gear, get some buddies together, set up some simple networks, and have one person start messing stuff up. Have someone mess it up that knows what they're doing of course, having your g/f or wife try to outsmart you at your own game isn't going to work.
Anyways, just some thoughts about troubleshooting since that is where a lot of people have low scores.
"The exam covers topics on Extending Switched Networks with VLANS, Determining IP Routes, Managing IP traffic with Access Lists, Establishing Point-to-Point connections, and Establishing Frame Relay Connections."
So everyone should know that there is a very good chance that you could get a SIM covering anyone of these topics. Thats a given!
Here is Another Quote:
CCNA Troubleshooting includes:
Utilize the OSI model as a guide for systematic network troubleshooting
Perform LAN and VLAN troubleshooting
Troubleshoot routing protocols
Troubleshoot IP addressing and host configuration
Troubleshoot a device as part of a working network
Troubleshoot an access list
Perform simple WAN troubleshooting
So lets say you are sitting in front of a router in a job interview for your first job and the interviewer required you to gather information about what is wrong and how to fix it, but he didn't tell you anything else. This is a basic troubleshooting type of problem, and everyone should know that they exist because of the Blueprint.
These are the types of questions you should be asking yourself and trying to answer as you implement the troubleshooting process.
What type of encapsulation is being used? Is this PPP, frame-relay, ISDN
Once you figure out what type of network is being used, you can begin to troubleshoot the network based on what you know about the technologies that are being used.
You have to be able to use all your show commands to figure out the network. Find your routes/routing protocols, look at the IP addressing, ping around, look at your interfaces, Line up? prototcol up? Find the problem!
DLCI/PVC problem? IP addressing problem? incorrect VLAN/Trunk/default gateway problem? PPP/CHAP problem? I think you have to first snoop around, and then begin the troubleshooting process.
you must be extremely analytical to solve these types of problems. In the real world YOU MUST have analytical skill. You have to be able to use all the facts you know about the technologies, and run with it to solve complex problems. Is your boss going to come up to you and say "okay Beavis we have a problem, is the solution A B C or D? No, you have to figure that out on your own.
Also look at the devices they give you access to. If they only give you access to 2 routers and a switch, well then this may be a VLAN probelm and it may be a routing problem. If they only gave you access to one router, then it could be a routing problem. You have to be able to take in all the information they give you, and read between the lines.
Also look at the answer choices to see what genre of problem the question pertains to.
Never forget that the answer is staring you right in the face.
I suggest people do Suduko puzzles to help you work on being analytical. It may sound stupid, but it's all about how you think.
One other thing, If they instruct you to telnet somewhere, then you know that layer 2 and 3 between the source and destination is just fine or you would not have been able to telnet to it right?
If you could not telnet into the router and that is a problem, then check ACL's, make sure you have a LINE VTY password set on the destination router.
Overall, just master the main topics and know everything about it. You can't analyze a complex problem with minimal knowledge of the technology being used.
Being analytical requires knowing the facts, and practice, and a detailed way of thinking.
For people with gear, get some buddies together, set up some simple networks, and have one person start messing stuff up. Have someone mess it up that knows what they're doing of course, having your g/f or wife try to outsmart you at your own game isn't going to work.
Anyways, just some thoughts about troubleshooting since that is where a lot of people have low scores.
There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
Comments
-
Delirious Member Posts: 79 ■■□□□□□□□□Good advice, thanks for taking the time to share. My girlfriend likes those suduko puzzles, maybe its time i give them a try