Identify Network Problem, Implement Regular Network Monitoring

IDENTIFYING AND RESOLVING
NETWORK PROBLEMS
IMPLEMENT REGULAR NETWORK MONITORING
3/5/2022 ELLAGOLDU19@GMAIL.COM 1
Structured Network Troubleshooting
Troubleshooting Overview
In today’s world, a company’s success is highly
dependent on its network availability.
As a result, companies are increasingly less
tolerant of network failures.
Therefore, network troubleshooting has become a
crucial element to many organizations.
General Problem-Solving Model
When you’re troubleshooting a network environment, a
systematic approach works best.
Unsystematic approach to troubleshooting can result in
wasting valuable time and resources, and can sometimes
make symptoms even worse.
The following steps detail the problem-solving process
outlined here:
Step 1. when analyzing a network problem, make a clear
problem statement. You should define the problem in
terms of a set of symptoms and potential causes.
CONT,..
For example, hosts might not be responding to service
requests from clients (a symptom)
Step 2. Gather the facts that you need to help isolate
possible causes.
Ask questions of affected users, network administrators,
managers, and other key people.
Collect information from sources such as network
management systems, protocol analyzer traces, output
from router diagnostic commands, or software release
notes.
CONT,..
Step 3. Consider possible problems based on the facts
that you gathered.
Using the facts, you can eliminate some of the potential
problems from your list.
Depending on the data, for example, you might be able to
eliminate hardware as a problem so that you can focus on
software problems.
At every opportunity, try to narrow the number of
potential problems so that you can create an efficient plan
of action.
CONT,..
Step 4. Create an action plan based on the remaining potential
problems.
Begin with the most likely problem, and devise a plan in which
only one variable is manipulated.
Changing only one variable at a time enables you to reproduce
a given solution to a specific problem.
If you alter more than one variable simultaneously, you might
solve the problem, but identifying the specific change that
eliminated the symptom becomes far more difficult and will
not help you solve the same problem if it occurs in the future.
3/5/2022
ELLAGOLDU19@GMAIL.COM 6
CONT,..
Step 5. Implement the action plan, performing each
step carefully while testing to see whether the
symptom disappears.
Step 6. Whenever you change a variable, be sure to
gather results.
Generally, you should use the same method of
gathering facts that you used in Step 2 .
That is, working with the key people affected, in
conjunction with utilizing your diagnostic tools.
3/5/2022
ELLAGOLDU19@GMAIL.COM 7
CONT,..
Step 7. Analyze the results to determine
whether the problem has been resolved.
If it has, then the process is complete.
Step 8. If the problem has not been
resolved, you must create an action plan
based on the next most likely problem in
your list.
CONT,..
Return to Step 4, change one variable
at a time, and repeat the process until
the problem is solved.
Note:- If you exhaust all the common
causes and actions, you should contact
your Cisco
technical support representative.
network problem troubleshooting strategies
and documentation
Networks can be composed of many types of
physical components, from copper wire or fiber-
optic cables to wireless Access Points and network
adapters,
Although each device, protocol, or standard that is
a part of your network may come with its own tools
used for troubleshooting purposes,
It's important to realize that you should take a
structured approach to solving problems on the
network.
Documented Network Is Easier to Troubleshoot
Some of the important things Documented
Network Is
A logical map of the network. This may or
may not match up with the physical way the
network is laid out.
A physical map of the network. This
documentation should describe each physical
component and illustrate the ways in which
the different components are connected.
Logical map and Physical map
A logical map of the network shows the relationships
between components and the flow of information through
the network.
A physical map of the network tries to approximate on
paper a representation of how each component of the
network is connected to the network.
For example, a logical map for a Windows network might
show computers grouped by domains, even though the
computers are not located physically in the same part of
the network.
CONT,..
Cabling and patch panel information you'll need to
know which cable connects this to that.
An application that manages servers, network
components, and client computers is even better.
Listings of applications and the computers or
users that make use of them, as well as software
versions, patch levels, and so on.
If you are a network administrator, you are
primarily responsible for the underlying network.
CONT,..
Information about the user accounts, and
associated permissions and rights, for the users and
user groups on the network.
A network overview. It's nice to be able to give a
new user a document that explains what she/he
needs to know about the network.
Problem reports. Keep track of problems as they
arise, and document the cause and remedy.
CONT,..
A physical mapping refers to a direct
physical path.
 In general, logical maps can be used to help
isolate configuration or application problems,
whereas physical maps can be used to isolate
a problem that affects only a portion of the
network, perhaps a single computer or other
device.
Problem detection and isolation
Network Problem-Solving Techniques
In any troubleshooting procedure a series of tests
narrows down the possible causes of a problem.
The following procedure can be used as a
guideline — each organization will have their own
procedures to suit their computing environment.
CONT,..

Item Commands

Check that the network cables are securely in place at the back of
the computer.

Check that cables to hubs, switches, bridges and routers are fixed
securely in their sockets.

Check the network configuration on Use the commands
workstations involved, to ensure ‘ipconfig/all’ and ‘ping’.
that they are correct.

Check that you can access other Use the commands ‘ping’
computers and peripherals on the or ‘tracer’ if part of your
network. network is on the other
side of a router.
Check the permissions to ensure that the user has the right levels
of access network resources.
Check that an individual user is in the correct group that has

access to network resources
Check and replace the network cards and drivers, as required.

Check the configurations of the Use the command
default gateway and browser proxy ‘ipconfig/all’ for the
server setting. default gateway, and
‘Tools’, ‘Internet Options’
in the browser to check
proxy settings.
Identifying common network problems
THE FIVE MOST COMMON NETWORK PROBLEMS
1.Physical Connectivity Problems:
Possible problems include these
Configuration is incorrect.
Cable is faulty or improperly connected.
Wiring closet cross-connect is faulty or improperly
connected.
Hardware (interface or port) is faulty.
Interface has too much traffic
CONT,..
Cable Problem:
Cables that connect different parts of a network can be cut or shorted.
A short can happen when the wire conductor comes in contact with
another conductive surface, changing the path of the signal.
Cable testers can be used to test for many types of cable problems
such as:
◦ Cut cable
◦ incorrect cable connections
◦ Cable shorts
◦ Interference level
◦ Connector Problem etc.
Testing Cables
Things that are usually tested include the following:
Cable length— The physical network topology restricts
the length of certain segments in the network.
If a desktop is just a few meters farther from a switch
than the standard allows(100m or 328 feet), you may get
complaints from that user!
Resistance— Electricity encounters resistance as it
travels along a copper wire.
CONT,..
Noise— Interference can come from other cables that
are bundled together or from outside sources.
Attenuation— As the cable encounters resistance
traveling down the wire, and as part of the signal
radiates out of the wire, the signal weakens.
Near-end cross-talk — From the transmission end of a
cable, it is necessary to remove the surrounding
material that encloses the copper wires and attach
each wire to a pin in the cable connector.
CONT,..
Rule Out a Configuration Problem
Check to make sure that all cables are connected
to the appropriate ports.
 Make sure that all cross-connects are properly
patched to the correct location using the
appropriate cable and method.
Check the Configuration:
 If the device is connected to a hub or switch,
verify that the port on the hub or switch is
configured properly and is not shut down.
Check the Network Interface card
Most interfaces or NICs will have indicator lights that
show whether there is a valid connection; often this
light is called the link light.
The interface may also have lights to indicate whether
traffic is being sent (TX) or received (RX).
If the interface has indicator lights that do not show a
valid connection, power off the device and reseat the
interface card.
2.Connectivity Problem: A connectivity problem with
one or more devices in a network can occur after a
change is made in configuration or by a malfunction of
a connectivity component, such as hub, a router or a
Switch.
Troubleshooting Local Connectivity Problems
Possible problems include these:
o Configuration problem
o DHCP or BOOTP issue
o Physical layer issue
o Duplicate IP address
Note:-BOOTP is networking protocol used to assign ip address
automatically to the network device.
Check for Configuration Problems
To begin troubleshooting, display and examine
the IP configuration of the source device.
The method to determine this information varies
greatly from platform to platform.
 Refer to the following examples:On a Cisco router,
use show ip interface and show running-config.
o On Windows 95 or 98, use winipcfg.exe.
o On Windows 2000 or NT, use ipconfig.exe.
o On a UNIX platform, use ipconfig.
o On Window 7,8 and10 use ipconfig.
 If no IP address is configured, verify that this
node receives its IP address from BOOTP or
DHCP.
 Otherwise, an IP address should be statically
configured for this interface.
 If the incorrect IP address, subnet mask, or
default gateway is configured, verify that this
node receives its IP address from BOOTP or
DHCP.
 If the address is statically configured, configure
the correct address.
3.Excessive Network Collisions: These often
lead to slow connectivity.
The problem can occur as a result of bad
network setup/plan.
Software-Based Analyzers
Software analyzers are the cheapest route for
large, complex networks.
4. Software Problem: Network problems can
often be traced to software configuration such as
DNS configuration, WINS configuration, the
registry etc.
Troubleshooting Domain Name Server
Problem
 Ping the destination by name, and look for an
error message indicating that the name could
not be resolved. Otherwise, continue
troubleshooting as follows:
1. Determine which name server you are using.
2.Verify that you can ping the name server using
its IP address.
3. Verify that you can resolve names within your
domain.
4.Verify that you can resolve one or more domain
names outside your domain.
5. Duplicate IP Addressing: A common
problem in many networking environments
occurs when two machines try to use the
same IP address.
IP Troubleshooting
When you’ve selected the two devices
Where to start:
1. Try to ping from the source to destination device by IP address.
 If the ping fails, verify that you are using the correct address, and try the ping
again.
 If the ping still fails, go to the next section, “Troubleshooting Local
Connectivity Problems.” Otherwise, proceed to Step 2.
2. Try to ping from the source to the destination device by name.
 If the ping fails, verify that the name is correctly spelled and that it refers to
the destination device, and then try the ping again.
3. If you can ping the destination by both name and address, it appears that the
problem is an Upper-layer problem.
END OF LESSO
N ONE

Identify Network Problem, Implement Regular Network Monitoring

Uploaded by

Copyright:

Available Formats

Identify Network Problem, Implement Regular Network Monitoring

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Identify Network Problem, Implement Regular Network Monitoring

Uploaded by

Copyright:

Available Formats

IDENTIFYING AND RESOLVING

Check that an individual user is in the correct group that has

Check and replace the network cards and drivers, as required.

You might also like