Scribd
Upload
3 views

ICT Assignment

Uploaded by

nardossunflowerandualem
Copyright
© © All Rights Reserved
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
3 views

ICT Assignment

Uploaded by

nardossunflowerandualem
Copyright
© © All Rights Reserved
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 7

Network troubleshooting

*.What is network troubleshooting?


NETWORK TROUBLESHOOTING is the act of discovering & correcting
problems with connectivity , performance, security and other aspects of
networks.
*.What is the value of network troubleshooting?
Fast effective , troubleshooting is a cornerstone of a business resilience.
Today's networks perform more mission-critical business tasks than
ever without robust troubleshooting and speedy resolution of issues,
networks can suffer downtime.
The cost of downtime includes reduced productivity and the economic
impacts of disrupted or underperforming services, data breaches and
malware. This consequences can result in steep costs and cause long
lasting damage to brands.
How do organizations handle troubleshooting?
Of course, troubleshooting isn’t just about resetting user passwords or
restarting devices. Especially in large organizations, it’s about a set of
procedures, practices, and tools used to process numerous requests by a
complex mix of users and dispersed network assets and infrastructure.

Typically, a large organization has an entire team devoted to network


troubleshooting. The team’s engineers address problems at various
levels: Tier 1 for basic issues such as password resets, Tier 2 for issues
that can’t be resolved by Tier 1, and Tier 3 for mission-critical issues.
Frequently, Tier 1 troubleshooting is outsourced. An escalation
framework is used to route requests efficiently and make sure that
upper-level engineers are tasked appropriately.

In recent years, artificial intelligence (AI), machine learning (ML), and


automation have been used to bridge skills gaps. These technologies
offer guided remediation tools that empower Tier 1 engineers to solve
complex network problems more rapidly.

Many organizations have separate network troubleshooting tools, but


the addition of these tools may require training and management by IT
departments. More commonly, network troubleshooting is embedded in
a network management system (NMS).
How do NMSs relate to troubleshooting?
In large organizations, network troubleshooting teams are not simply
waiting for users to report issues.

An NMS monitors networks continuously. It sends status updates—and


alerts, when needed—on network key performance indicators (KPIs)
such as connection speed, bandwidth, latency, users, and access.

The NMS performs monitoring by querying the various parts and nodes
of the network to update status, at an interval determined by the IT
team. Newer network elements, however, use telemetry to transmit
their KPIs automatically.
An essential part of network troubleshooting is tracking and collecting
data on network events. A system of IT service management (ITSM)
tickets is used for this process. The data aggregated from the tickets can
provide insights to identify problem areas and guide network
optimization and upgrades.
Dashboards
Engineers benefit from a network troubleshooting interface that
provides a global view of an entire network as well as a view into
specific KPIs. As networks become more complex and dispersed, the
design and ease of use of this interface become even more important.

Customizable views
The ability to filter network data by location, department, device, or
network improves the early stages of diagnosing network problems.

Cross-domain visibility
The idea of viewing the network as a series of interconnected domains
is becoming obsolete. The typical enterprise network includes not just
local-area networks (LANs) connected to the internet, but also remotely
hosted databases, applications, and data processing. Up-to-date
troubleshooting tools are designed to manage these new, more complex
networks.
How does troubleshooting work?
Computer problems that troubleshooters address can show up in any
number of places. Examples of places troubleshooters find themselves
working include the following:
 Operating systems
 Applications
 Central processing units or CPUs
 Firewalls
 Hard drives
 Solid-state drives
 Servers

What is troubleshooting?
Troubleshooting is a systematic approach to problem-solving that is
often used to find and correct issues with complex machines,
electronics, computers and software systems. The first step in most
troubleshooting methods is gathering information on the issue, such as
an undesired behavior or a lack of expected functionality.

Once the issue and how to reproduce it are understood, the next step is
to eliminate unnecessary components to determine if the issue persists.
This can help identify component incompatibility issues and problems
caused by third-party products.

Troubleshooting methodologies usually try to isolate a problem so that


it can be examined. The initial goal is to diagnose the problem and try
obvious solutions, such as performing a system reboot, powering down
and up, and checking that the power cord is connected.
Troubleshooters initially look for common, known causes. For example,
when a laptop won’t boot up, an obvious first step is to check whether
the power cable is working. Once common issues are ruled out,
troubleshooters must run through a checklist of components to identify
where the failure is happening.

The primary objectives of troubleshooting are to figure out why


something doesn’t work as intended and provide a solution to resolve
the issue.

How does troubleshooting work?


Computer problems that troubleshooters address can show up in any
number of places. Examples of places troubleshooters find themselves
working include the following:

 Operating systems
 Applications
 Central processing units or CPUs
 Firewalls
 Hard drives
 Solid-state drives
 Servers
List of steps for troubleshooting server problems IT pros usually follow
basic guidelines when troubleshooting server issues.
One basic troubleshooting method is to press Control-Alt-Delete on a
PC, which opens the Microsoft Windows Task Manager where users can
determine which applications have become unresponsive, close them
and restart the computer. Similarly, Option-Command-Escape will force
quit apps on a Mac.

IT and help desk professionals use more extensive ways to troubleshoot


problems. Troubleshooting methodologies vary, but the following seven
steps are often used.

Step 1. Gather information


Step 2. Describe the problem
By comprehensively describing the issue, troubleshooters will know
where to look for the root cause. It can help to ask the following
questions:

What are the symptoms?


When does the problem occur?
Where does the problem occur?
What are the conditions when the problem occurs?
Is the problem reproducible?

Step 3. Determine the most probable cause.

Step 4. Create a plan of action and test a solution


Step 5. Implement the solution
Step 6.Analyse the results
Step 7. Document the process

You might also like