Unit 3

Fault detection
Fault management is the component of network management that detects,
isolates and fixes problems. When properly implemented, network fault
management can keep connectivity, applications and services running at an
optimal level, provide fault tolerance and minimize downtime. Fault
management systems are platforms or tools designed specifically for this
purpose.
Faults result from malfunctions or events that interfere with, degrade or
obstruct service delivery. Examples of faults include hardware failure,
connectivity loss or port status change. Once the fault management platform
detects a fault, it notifies the administrator -- and any additional authorized or
designated parties -- via an alarm or alert.

Fault correction
Error detection is the detection of errors caused by noise or other
impairments during transmission from the transmitter to the receiver.
Error correction is the detection of errors and reconstruction of the
original, error-free data.
Network trouble report
Business networks are complex, and many things can go wrong that disrupt
network performance. End users often complain about what appears to be
poor application performance, and there can be many possible reasons for
these hiccups. Here are nine of the most common network issues to
troubleshoot.

1. Slow network
Users complain the network is too slow. There can be many reasons why a
network that provided adequate performance in the past is now frustrating its
users. For instance, a new application, such as video conferencing or online
training videos, may have been added. A failing switch port or link could cause
traffic to route around the failure and overload another link.
In other cases, the network could be part of a larger organizational network.
As a result, a change in the larger network has resulted in more traffic through
the internet connection point, slowing responses to cloud-resident
applications.

Another network speed issue could emerge if employees decide to download

high-definition videos while at work because downloading in the office is faster
than using their home internet connection. A network monitoring tool helps
solve any of these common network issues.

2. Weak Wi-Fi signal

Wi-Fi signal strength may be adequate almost everywhere, but it could be weak or
nonexistent in other areas. Rearranging an office area can result in a weak wireless
connection, where signal strength had been adequate before the move. For example, a
large metal object, like a file cabinet, can block the Wi-Fi signal.

Devices such as microwave ovens, cordless phones and Bluetooth can interfere with
Wi-Fi signals, too. A Wi-Fi network test tool can help identify the source of the
problem.

3. Physical connectivity issues

A network connection can suddenly break because of physical connectivity issues. A
common problem is when a network cable becomes damaged or knocked loose.
Cables might be added or removed from a switch, and one of the other cables might
accidentally get disconnected.

Or a cable was damaged when it was pulled around a sharp edge while work was done
on the heating or air conditioning pipes. It should be clear from the segment of the
network affected which cable was damaged. But finding the problem along a cable
stretching across the ceiling

4. Excessive CPU usage

Task Manager is the first thing to use to find which application is using a high
proportion of system resources, such as CPU, memory or disk space. This basic
troubleshooting step may not reveal a problem since some applications may be
performing complex calculations, receiving high-speed video or interacting with large
databases. A virus may also consume resources, so make sure antivirus software is up
to date.

If an application has been running for a long time, it may slowly leak resources. The
quickest way to improve performance is to stop and restart the application, although
sometimes you may need to stop and restart the entire system. Updating device drivers
may also improve performance.

Task Manager also shows applications you didn't know were running in the
background. One example would be Windows including games upon system startup.
Editing startup files can eliminate this problem.

5. Slow DNS lookups

The DNS matches the common name used to match server or service names with the
internet address that routes a network request. For commonly used names, the
matchup is probably already stored in the system's DNS cache, and the lookup is
quick. For less commonly used names, the matchup may be stored in a more distant
cache, such as the root server of the top-level name, such as .com, .org or a national
root, such as .uk.

Each DNS server along the path checks its cache before making a request to the next
server along the path. The next server then checks its cache, repeating the process. If
lookup is slow, there may be a slow link along the path or a slow or overloaded
server. To address this issue, your local network administrator can reconfigure local
routers to shift requests to a faster chain of servers.

6. Duplicate and static IP addresses

On a network, no two systems can share the same internet address. If there are
duplicate internet addresses, neither system can access the network reliably. The
addresses for most network devices are assigned when Dynamic Host Configuration
Protocol (DHCP) boots up the systems on the local network. DHCP maintains a pool
of addresses assigned to the local network, assigning a different address from the pool
to each system.

Workstations are not assigned permanent addresses but receive one for a limited time
from DHCP. Systems re-request before the time runs out and usually receive the same
address. If the system shuts down without re-requesting and the time runs out, it loses
this address and may receive a different one upon startup.

The DHCP administrator may assign a static IP address to some network devices,
such as printers or web servers, because external systems won't be updated if an
address changes. One issue is users sometimes set up a private web server to support a
hobby, allocating a static address without informing the network administrator. Both
share a DHCP server in either an organization or home network. So, if the static
address matches one assigned by DHCP, it disrupts the network.

Often, these private web servers are set up to upload and download licensed music or
video and consume excessive network bandwidth.

7. Exhausted IP addresses
Internet addresses are in limited supply. Each service provider is given a supply based
on the expected number necessary. Most familiar are the IPv4 addresses, which were
originally thought to be adequate so every system could be allocated one. But, with
the proliferation of cellphones and other devices, it's been necessary to move
to IPv6 with 128-bit addresses for some networks.

A widely used method to stretch the supply of addresses is Network Address

Translation (NAT), a feature often built into routers. Each is assigned a single internet
address allocated from the worldwide set of addresses. Its internal DHCP server
allocates private addresses to systems on connected local networks -- usually, an
Ethernet or wireless network.

Private addresses generally start with either 10 or 192.168 on networks using 32-bit
IPv4 addresses. These address ranges can be used many times, which helps to save
addresses. The NAT server maps traffic to its global address to communicate with the
internet. Responses are mapped back via the private addresses.

8. Can't connect to printer

When users can't connect to a printer, the first step is to check simple things like
whether the printer is plugged in, turned on and has paper. Also, make sure the printer
appears on Devices and Printers on Windows. If it does, click to check whether the
file is queued.

Sometimes, you need to stop and restart the print spooler, the software that stores files
until the printer is ready to print them. Also, check the printer vendor's website
because some brands have a downloadable app that can diagnose and fix problems.

If the OS was just upgraded, scan for other people with similar problems, or check
Microsoft.com to see if the company is aware of a problem. Shut off the printer, and
turn it back on. Also, shut down your system, and turn it back on.

Finally, update printer drivers and your OS. In some cases, you may need to
temporarily shut down your antivirus software. For a wireless printer, make sure it's
connected to the signal.

9. VLAN and VPN problems

Check for virtual LAN (VLAN) misconfiguration issues. Review the configuration on
each switch, carefully comparing configurations to ensure compatibility of switch
configuration.
The most common VPN problem is a failure to connect. First, check to see if you're
successfully logging in to the service, and make sure your account is up to date and
you're entering your correct credentials. Next, check firewall settings. You need to
open some ports. Check if that is the problem by temporarily shutting down your
firewall. Finally, restart your system.

Try accessing the VPN from a different network, such as switching from Wi-Fi to
Ethernet to the router. If there is still a problem, refer to the firewall documentation
for other solutions, or contact the VPN vendor support.

In sum, networks are complex, and problems do occur. These are just some of the
most common types of network problems. When other types of network issues occur,
scan the web for help, or contact network service providers or device vendor support.

Symtoms

Identify Symptoms

Indicators are either physical or logical symptoms that help determine the nature of the
situation, the reach of the trouble, etc. These symptoms enable a network administrator
to adopt timely preventive measures to solve the challenge before it grows up beyond
control

Causes
Whether you're a phone service provider, internet service provider, or some other
type of telecommunications company, it's your responsibility to ensure that your
communication services are always operating correctly for your customers.

Network downtime will cause a whole list of problems, and all of them can be
very costly. You can even face fines for every minute of the network outage. If
your network is down for longer than a few minutes, you can be facing a lot of
money in fines, penalties, or SLA refunds.

Network failure can also lead to angry customers, which often leads to loss of
revenue.
Network Troubleshooting & Diagnostics

Network troubleshooting and diagnostic tools help network

administrators and technicians identify and resolve issues.

These tools are designed to analyze network performance, identify

problems, and provide insights into the functioning of the network.

Network analysis can show you the leading causes of network problems
such as; slow speeds, network connection problems, packet loss on
overloaded network devices or missing information in your routing table
and other system databases.

Here’s our list of the best network diagnostic tools and troubleshooting
software:

1. Datadog Network Performance Monitoring EDITOR’S

CHOICE A cloud-based network monitoring and management
service that includes autodiscovery, topology mapping,
performance alerts,
2. SolarWinds Network Configuration Manager (FREE TRIAL) An
essential system security and administration tool that automatically
checks on device settings. The NCM will gather all device
configurations, allow the creation of standard settings, and ensure
that any unauthorized changes are immediately rolled back.
3. N-able N-sight (FREE TRIAL) A remote monitoring and
management tool that enables central IT departments to manage
networks on several remote sites.
4. ManageEngine OpManager Plus (FREE TRIAL) This bundle of
seven ManageEngine tools provides full network monitoring and
analysis capabilities. Installs on Windows Server and Linux.
5. Paessler Network Troubleshooting with PRTG Infrastructure
management system that includes port monitoring.
6. Ping Simple command-line utility that checks on the speed of
connections.
7. Tracert Free command-line utility that lists the probable hops to a
network or internet destination address.
 8. Ipconfig This command-line tool reports the IPv4 and IPv6
addresses, subnets, and default gateways for all network adapters
on a PC.
9. Netstat This tool displays active connections on your computer.
10. Nslookup Available for Windows, Unix, Linux, and Mac OS,
this tool gives you DNS server diagnostics.
11. Uptrends Uptime Monitor A free online tool that will make
repeated checks on the availability of a website.
12. Sysinternals Set of Microsoft tools for Windows that help
troubleshoot and configure Active Directory.
13. Wireshark Free packet sniffer that will help you analyze
traffic flows.
14. Nmap Network security and monitoring tool that needs a
companion utility, Zenmap, as a user interface.

Network Monitoring

Network monitoring is the process of constantly monitoring a computer network for

problems such as slow traffic or component failure. Network Monitoring tools are
always scanning the network and are designed to automatically notify network
administrators via text, email, or other application such as Slack when a problem
occurs. Network monitoring software differs from network security or intrusion
detection systems in that network monitoring is focused on internal network issues
such as overloaded routers, server failures, or network connection issues that could
impact other devices.

Network monitoring solutions can also initiate failover to remove problem device or
circuits from duty until remediation can be performed to repair the issue. Ideally, a
proactive network monitoring solution will prevent downtime or failures before they
occur by identifying anomalies that could lead to outage if unchecked.

Continuous monitoring is critical to maintaining network integrity. The best network

monitoring tools provide visualization or a dashboard that provides at-a-glance status
of monitored network components, indicating any out-of-norm parameters that require
further examination or components such as switches, routers, firewalls, servers, and
software services, applications, or URLs that could be the source of network
disturbances. For maximum effectiveness, a network monitoring system should
include high availability components so that a hardware or software failure of systems
running the network management tool can be automatically remediated by fail-over to
another network monitoring installation. Network Monitoring should provide:

 Visualization of the organization’s complete IT and network infrastructure

 Monitoring, troubleshooting, and remediation of network performance
issues.
 Root cause analysis tools when problems occur.
 Dashboard with clear visualization tools and reports
Network monitor baseline
In the simplest terms, a network performance baseline is a set of
metrics used in network performance monitoring to define the normal
working conditions of an enterprise network infrastructure. Engineers
use network performance baselines for comparison to catch changes in
traffic that could indicate a problem.
items that can be monitored
Network monitoring is a critical IT process where all networking
components like routers, switches, firewalls, servers, and VMs are
monitored for fault and performance and evaluated continuously to
maintain and optimize their availability.
Alarm
Athenalarm network alarm monitoring system integrates the network
alarm system and the monitoring system in one solution. It links
previously separated network alarm systems and monitoring systems
(CCTV) together in the cloud platform via TCP/IP or 4G. The high
sensitivity transmission and powerful functions make this ideal
for setting up an alarm monitoring center for centralized network
security management.
It consists of 3 parts:
 Alarm software: The AS-ALARM network alarm center
management software is used as the management system of the
alarm monitoring center. The alarm software is divided into two
parts, the server and the client. The server of the alarm software
must be installed on Windows server 2008 or Windows server
2012 (users can build or rent the server); the client of the alarm
software can be installed on any Windows OS personal computer
connected to the Internet.
 Alarm system: Adopts Athenalarm AS-9000 series alarm control
panels, detection devices, linkage devices and other devices.
 Monitoring system (CCTV): The monitoring products compatible
with the alarm software can be used (such as HIKVISION DAHUA,
XM, and other brand monitoring products).
Network log
Network logs include information about requests between the web
browser and the site being tested. During the test execution, network
logs are collected and displayed as part of the test results. The network
logs can be viewed at the step level or at the test level.
Network polling
Poll the network to retrieve information from network devices that you
can use to monitor the behavior of the devices.
About this task
 About polling the network
To poll the network, Network Manager periodically sends queries
to the devices on the network. These queries determine the
behavior of the devices, for example operational status, or the
 data in the Management Information Base (MIB) variables of the
devices.
 Enabling and disabling polls
To activate Network Manager polling, you must enable the poll
policies.
 Creating and editing poll policies
Create a poll policy if the existing poll policies do not meet your
requirements. Either customize a copy of an existing or default
poll policy, or create a new poll policy from scratch.
 Creating and editing poll definitions
Create a poll definition if the existing poll definitions do not meet
your requirements. Either customize a copy of an existing or
default poll definition, or create a new poll definition from
scratch.
 Managing adaptive polling
Adaptive polls dynamically react to events on the network. You
can create adaptive polls that manage a wide range of network
problem scenarios.
 Administering network polling
Use the command-line interface to perform a wide range of
polling administration tasks, including managing the multiple
poller feature, copying network polls across network domains,
suspending network polling, enabling and disabling polls,
retrieving poll status, and refreshing polls.
 Troubleshooting network polling
Use this information to understand how to troubleshoot network
polling.
identifying the cause of fault
Common network issues could be down to: Cabling – broken, or not
providing the required speeds. WiFi – interference, capacity, or design
issues. Switching – capacity/spanning tree/design issues.
Human failure
Network outages can often be traced to four error-prone
activities: fault analysis and response, configuration changes, scaling
and failover, and security policies. You might have been alarmed to
read recently that half of all network problems are due to human error
Network fault

To maintain our connectivity, applications and services at an optimal level is something that
´s essential in our network management. Network Fault Management is what helps you to
identify, avoid and resolve problems that endanger optimum performance of our digital
transmission network.

Protocol Layering
A protocol is a set of rules and standards that primarily outline a language that
devices will use to communicate. There are an excellent range of protocols in
use extensively in networking, and that they are usually implemented in
numerous layers.

It provides a communication service where the process is used to exchange the

messages. When the communication is simple, we can use only one simple
protocol.

When the communication is complex, we must divide the task between different
layers, so, we need to follow a protocol at each layer, this technique we used to
call protocol layering. This layering allows us to separate the services from the
implementation.

Each layer needs to receive a set of services from the lower layer and to give
the services to the upper layer. The modification done in any one layer will not
affect the other layers.
Basic Elements of Layered Architecture
The basic elements of the layered architecture are as follows −

 Service − Set of actions or services provided from one layer to the higher layer.
 Protocol − It defines a set of rules where a layer uses to exchange the information with its
peer entity. It is concerned about both the contents and order of the messages used.
 Interface − It is a way through that the message is transferred from one layer to another layer.

Reasons
The reasons for using layered protocols are explained below −

 Layering of protocols provides well-defined interfaces between the layers, so that a change in
one layer does not affect an adjacent layer.
 The protocols of a network are extremely complicated and designing them in layers makes
their implementation more feasible.

Protocol Layering and fault

 The main disadvantages of layered systems consist primarily of overhead each in
computation and in message headers caused by the abstraction barriers between layers.
Because a message typically should pass through several (10 or more) protocol layers the
overhead of those boundaries is commonly more than the computation being done.
 The upper-level layers cannot see what is within the lower layers, implying that an
application cannot correct where in an exceedingly connection a problem is or precisely what
the matter is.
 The higher-level layers cannot control all aspects of the lower layers, so that they cannot
modify the transfer system if helpful (like controlling windowing, header compression,
CRC/parity checking, et cetera), nor specify routing, and should rely on the lower protocols
operating, and cannot specify alternatives when there are issues.