UNIT

15 Network Management System

Names of Sub-Units

Introduction to Network Management System: Con�iguration Management, Fault Management,

Performance Management, Simple Network Management Protocol (SNMP)

Overview

This unit begins by discussing the concept of network management system. Next, the unit discusses
the con�iguration management and fault management. Further, the unit explains the performance
management. Towards the end, the unit discusses the Simple Network Management Protocol (SNMP).

Learning Objectives

In this unit, you will learn to:

 Discuss the concept of network management system
 Explain the concept of con�iguration management
 Describe the fault management
 Explain the signi�icance of performance management
 Discuss the importance of Simple Network Management Protocol (SNMP)
 Data Communication and Computer Networks

Learning Outcomes

At the end of this unit, you would:

 Evaluate the concept of network management system
 Assess the concept of con�iguration management
 Evaluate the importance of fault management
 Determine the signi�icance of performance management
 Assess the importance of Simple Network Management Protocol (SNMP)

Pre-Unit Preparatory Material

 https://www.jcboseust.ac.in/computers/images/studymaterial/networkmanagement1.pdf

15.1 INTRODUCTION
A Network Management System (NMS) is a programme or group of programmes that allows network
managers to control the network’s distinct components inside a larger network management
framework. NMS may be used to keep track of both software and hardware in a network. It generally
collects data from a network’s distant locations and sends it to a system administrator for reporting.
The fundamental bene�it of NMS is that it allows users to monitor and manage all aspects of their
business from a single computer
Network device detection is aided by a network management system. Monitoring network devices,
network performance analysis, network device management and customisable alerts or intelligent
noti�ications are just a few examples.
The following characteristics are seen in high-quality network management systems:
 Money is saved: To monitor and administer the whole network, only one system administrator is
necessary at a single location, which reduces recruiting costs.
 Time is saved: When needed, any IT provider has immediate access to any data. Using their own
computers, any team member may easily input or retrieve data. The network manager may be able
to control their access at the same time.
 Boosts productivity: Assists with the management of the whole of�ice network, including software,
hardware, and other peripherals. The NMS detects a problem as soon as it happens; ensuring that
no production is hampered or data is lost.

15.2 NETWORK MANAGEMENT SYSTEM

Network management means controlling routing and data traf�ic, debugging problems, controlling
network equipment, and �inding computers that violate protocol standards. In this section, you will
consider about the ideas behind TCP/IP network management software and describe a network
management protocol called SNMP. Although most of the sophisticated network equipments are
provided with control utility by the manufacturer, as the network increases in size, it is bounded to have
some problems that may arise due to standalone reasons or incompatibility. Therefore, it is better to
discard these individual control utilities and use an integrated network management system that can
manage almost all devices in a network.

2
UNIT 15: Network Management System

Figure 1 depicts the classi�ication of network management system:

Functions of a Network
Management System

Con�iguration Fault Performance Security Accounting

Management Management Management Management Management

Recon�iguration Reactive Capacity

Documentation Proactive Traf�ic

Throughput
Response Time

Figure 1: Classi�ication of Network Management System

15.2.1 Con�iguration Management

The main aim of con�iguration management is to observe the con�iguration information of the
network components. It helps in tracking and managing function of different versions of hardware and
software in the network. Each network component has a variety of version information related to it.
The con�iguration management system stores the version information in a database for future access.
When a problem occurs, this database can be referred for solving the problem.
Hundreds of entities are generally physically or conceptually linked in a big network. When the network
is �irst set up, these entities have a default con�iguration, but this might vary over time. Users may
be moved from one group to another, and desktop machines may be replaced by others. Application
software may also be upgraded to a newer version. The con�iguration management system has to know
the status of each entity and its relationships with other entities at all times. Con�iguration management
has two subsystems, i.e., recon�iguration and documentation.

Recon�iguration
In a big network, recon�iguration, or altering network components and features, can be a regular event.
Hardware recon�iguration, software recon�iguration, and user-account recon�iguration are the three
forms of recon�iguration. All modi�ications to the hardware are covered under hardware recon�iguration.
A desktop computer, for example, may need to be replaced. It is possible that a router will need to be
relocated to another area of the network. The network can have a subnetwork created or deleted. All of
this necessitates network management’s time and attention. In a big network, specialist employees must
be educated in hardware recon�iguration quickly and ef�iciently. This sort of recon�iguration, however,
cannot be automated and must be performed manually on a case-by-case basis. All modi�ications to
the programme are covered by software recon�iguration. New software, for example, might need to
be deployed on servers or clients. It is possible that your operating system needs to be updated. The
majority of software recon�iguration can, fortunately, be automated. Updating an application on some
or all clients, for example, can be done electronically from the server. Adding or removing users on a
system is not the same as recon�iguring their accounts. You must also think about your user privileges,
both as an individual and as a group member. A user may, for example, have read and write permission

3
 Data Communication and Computer Networks

on certain �iles but only read permission on others. To some extent, user account recon�iguration can be
automated. For example, new students are admitted to the system at the beginning of each section or
semester in a college or university. Students are usually divided into groups based on the courses they
are taking or the majors they are pursuing.

Documentation
The initial network setup, as well as any later changes, must be properly documented. This implies
that documentation for hardware, software, and user accounts is required. Typically, hardware
documentation consists of two types of documents: maps and speci�ications. Maps keep track of each
piece of hardware and its network connection. Each subnetwork’s logical relationship may be shown on
a single generic map. A second general map that displays the physical location of each subnetwork is
also possible. Then there are one or more maps for each subnetwork that display all of the equipment.
The maps are standardised in some way so that present and future workers can read and understand
them. Maps alone are insuf�icient. Each piece of hardware must be recorded as well. Each piece of
hardware linked to the network must have its own set of requirements. Hardware type, serial number,
vendor (address and phone number), time of purchase, and warranty information must all be included
in these specs. All software must be documented as well. The type of programme, the version, the time it
was installed, and the licence agreement are all included in the software documentation. The majority
of operating systems include a tool for documenting user accounts and their rights. The management
must ensure that the �iles containing this data are up to date and safe. Some operating systems keep
track of access rights in two documents: one lists all �iles and access kinds for each user, and the other
lists the users who have access to a certain �ile.

15.2.2 Fault Management

The main aim of fault management is to identify the network problems and notify it to the users. The
fault management system, if possible, automatically �ixes network problems. Fault management is the
most widely implemented function of the network management system because faults frequently occur
in a network. These faults cause downtime or unacceptable network degradation. Fault management
involves the following functions:
 Determining symptoms
 Separating the problem
 Fixing the problem
 Testing the solution on powerful subsystems
 Recording the detection and resolution of the problem
Hundreds, if not thousands, of components make up today’s complex networks. The network’s correct
operation is contingent on the appropriate operation of each component separately and in relation to
one another. The �ield of network management that deals with this problem is fault management. There
are two subsystems in an ef�icient fault management system: reactive fault management and proactive
fault management.

Reactive Fault Management

Detecting, isolating, repairing, and documenting problems are the responsibilities of a reactive fault
management system. It deals with quick �ixes for problems. A reactive fault management system’s initial
step is to pinpoint the exact location of the issue. A defect is a state in the system that is abnormal. When

4
UNIT 15: Network Management System

a failure occurs, the system either stops operating properly or produces a large number of errors. A
faulty communication channel is an excellent illustration of a �law. This �law may cause communication
to be disrupted or result in a large number of errors. A reactive fault management system’s next step
is to isolate the fault. If a problem is isolated, then it generally only impacts a few users. Following
isolation, the af�licted individuals are alerted promptly and given an approximate time of recovery. The
third step is to �ix the problem. It may be necessary to replace or repair the malfunctioning component
(s). It is necessary to document the defect once it has been recti�ied. The record should include the
speci�ic location of the defect, the potential cause, the action(s) done to remedy the issue, the cost, and
the amount of time it took to complete each step. Documentation is critical for a number of reasons:
 The issue might return. Documentation can aid a current or future administrator or technician in
resolving a similar issue.
 The occurrence of the same type of failure on a regular basis indicates a serious problem in the
system. If a component fails regularly, it should be replaced with one that is comparable, or the
entire system should be modi�ied to prevent using that sort of component.
 Another aspect of network administration, performance management, can bene�it from the statistic.

Proactive Fault Management

Proactive fault management aims to avoid the occurrence of problems. Some forms of failures can be
foreseen and avoided, however, this is not always achievable. If a manufacturer provides a lifetime for a
component or a part of a component, for example, replacing it before that period is a smart approach.
For example, if a network failure occurs frequently at one location, then it is prudent to carefully modify
the network to avoid the fault from occurring again.

15.2.3 Performance Management

The main aim of performance management is to evaluate and provide different features of network
performance so that internetwork performance can be maintained at a satisfactory level. Some of the
performance management factors are network throughput, user response times, and line utilisation.
The performance management function of the network model involves the following three main steps:
1. Data is collected on the basis of variables of interest to the administrators.
2. The data is examined periodically to check whether the managed devices are functioning normally.
3. Suitable performance thresholds are decided for each important variable, exceeding these thresholds
speci�ies a network problem that needs to be resolved.

The performance management system can be reactive or proactive. In a reactive management

subsystem, the managers constantly observe the performance of the variables. As soon as the
performance threshold is surpassed, an alert message is generated and transmitted to the network
management system. When the performance reaches to the level that is equivalent to user-de�ined
threshold, the system responds by sending a message.
In a proactive management subsystem, network simulation is applied to plan how network growth will
in�luence the performance metrics. Such simulation alerts managers about the pre-speci�ied problems
that probably may happen, so that suitable actions can be taken on time.
Performance management, which is closely connected to fault management, attempts to monitor and
regulate the network in order to guarantee that it operates as effectively as possible. Performance
management seeks to quantify performance through the use of quanti�iable metrics such as capacity,
traf�ic, throughput, and response time.

5
 Data Communication and Computer Networks

Capacity
The network’s capacity is one element that a performance management system must keep track of.
Every network has a certain amount of capacity, and the performance management system must
guarantee that this capacity is not exceeded. A LAN built for 100 stations at a data rate of 2 Mbps, for
example, will not function correctly if 200 stations are joined to the network. The data rate will drop, and
there may be some blockage.

Traf�ic
Internal and external traf�ic may be monitored in two ways. The amount of packets (or bytes) moving
within the network is used to measure internal traf�ic. The exchange of packets (or bytes) outside the
network is used to measure external traf�ic. Blocking may occur during peak hours, when the system is
frequently used, if there is suf�icient traf�ic.

Throughput
You can measure the throughput of a single device (such as a router) or a network segment. The
throughput is monitored by performance management to ensure that it does not fall below acceptable
limits.

Response Time
The time it takes for a user to request a service to be given is commonly referred to as response time.
The response time might be in�luenced by other variables such as capacity and traf�ic. The average
response time and peak-hour response time are monitored by performance management. Any increase
in response time is a severe problem since it means the network is working above its capacity.

15.2.4 Security Management

The main aim of security management is to manage access to network resources so that the network
cannot be disrupted and secured information cannot be accessed without appropriate authorisation.
For example, a security management system can monitor users’ authentication and deny access to
those who enter wrong password.
The security management system functions by separating network resources into authorised and
unauthorised domains. For some users, access to any network resource is inappropriate; on the other
hand, for others, a set of information is inappropriate. The security management system performs the
following functions:
 Discovers sensitive network resources
 Creates mappings between sensitive network resources and user sets
 Monitors access points to sensitive network resources
 Logs improper access to sensitive network resources

15.2.5 accounting Management

The main aim of accounting management is to evaluate network utilisation parameters that facilitate
in regulating the network usage. By regulating the network usage, network problems are minimised
and the network access capacity is maximised. For accounting management, �irst of all, network

6
UNIT 15: Network Management System

utilisation parameters of the essential network resources are measured and analysed. Analysis of the
utilisation parameters enables to comprehension the way of network usage and to take appropriate
steps to resolve any issue, if exist.

15.3 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)

The Simple Network Management Protocol (SNMP) is a protocol suite that uses the TCPIIP protocol suite
to manage devices on the Internet. It provides a collection of basic Internet monitoring and maintenance
activities. The terms “manager” and “agent” are used in SNMP. That is, a manager, generally a host,
supervises and controls a group of agents, most often routers, as shown in Figure 2:

Agent variables

Internet

Manager
Agent

Figure 2: Components of SNMP

SNMP is an application-level protocol that allows a small number of management stations to control a
large number of agents. The protocol was created at the application level to allow it to monitor devices
from various manufacturers and placed on various physical networks. In other words, SNMP decouples
administration duties from the physical features of monitored devices as well as the underlying
networking technology. It may be utilised in a heterogeneous Internet consisting of several LANs and
WANs linked by routers from various manufacturers.

15.3.1 Managers and agents

A manager, or management station, is a host that executes the SNMP client software. An agent, also
known as a managed station, is a router (or host) that runs the SNMP server application. Simple
contact between a manager and an agent is used to achieve management. The agent maintains track
of performance in a database. The database values are accessible to the management. The number of
packets received and routed, for example, can be stored in suitable variables by a router. The manager
can get the values of these two variables and compare them to see if the router is congested. The
management can also instruct the router to carry out certain tasks. A router, for example, checks the
value of a reboot counter on a regular basis to determine when it should reboot itself. If the value of the
counter is O, for example, it reboots. This functionality allows the management to remotely reboot the
agent at any moment. It just sends a packet to reset the counter to zero. Agents can participate in the
management process as well.
The server software on the agent can monitor the environment and, if it detects anything out of the
ordinary, send a trap message to the manager.

7
 Data Communication and Computer Networks

In other terms, SNMP management is built on three key concepts:

 A manager veri�ies an agent’s performance by requesting information that re�lects the agent’s
actions.
 By resetting settings in the agent database, a manager can force an agent to complete a job.
 An agent assists in the management process by alerting the manager to a potentially hazardous
scenario.

15.3.2 application of Simple Network Management Protocol (SNMP)

The Simple Network Management Protocol (SNMP) was designed by the Internet Architecture Board
(IAB) as an application – layer protocol for exchanging management information between network
devices in RFC1157. The Transmission Control Protocol Internet Protocol (TCP/IP) protocol suite includes
it.
SNMP operates by delivering messages, known as Protocol Data Units (PDUs), to devices that “speak”
SNMP on your network. Network administrators may track almost any data value they specify using
these queries. All of the data that SNMP collects may be sent to a product that requests it.

15.3.3 SNMP Runtime Components

In an SNMP-enabled environment, the following are the major runtime components:
 SNMP-managed devices and resources: The devices and network parts on which an agent runs are
referred to as “agents.”
 SNMP agent: This software collects data on different metrics such as CPU utilisation, bandwidth
usage, and disc space usage on the device or service being monitored using SNMP. The agent �inds
and delivers this information back to SNMP management systems after being queried by the SNMP
manager.
 SNMP manager: (also referred to as SNMP server) this component acts as a centralised management
station, running an SNMP management programme on multiple operating systems. It makes it a
point for agents to deliver SNMP updates on a frequent basis.
 Management Information Base (MIB): This data structure is a text �ile (.mib extension) that
describes all data items that may be queried or controlled via SNMP, as well as access control. There
are numerous distinct managed objects that may be recognised by Object Identi�iers within the MIB.
A MIB identi�ication called an Object Identi�ier (OID) is used to distinguish between devices in the
MIB. OIDs are unique numeric identi�iers that are used to access MIB objects.
There are three different versions of SNMP:
 SNMP version 1 (SNMPv1): This was the initial implementation, which was speci�ied in RFC 1157 and
operated inside the structure management information standard.
 SNMP version 2 (SNMPv2): RFC 1901 describes this version, which has been modi�ied to allow
more ef�icient error handling. RFC 1441 was the name given to it when it was originally published.
SNMPv2c is another name for it.
 SNMP version 3 (SNMPv3): Security and privacy have been improved in this version. RFC 3410 was
the �irst to mention it.
SNMP version 2 is the most widely used version of the SNMP protocol today. SNMP version 3 is a most
recently version which has some additional security abilities such as SNMP message authentication
and encryption and also has a packet security during transit.

8
UNIT 15: Network Management System

Conclusion 15.4 CONCLUSION

 A Network Management System (NMS) is a programme or group of programmes that allows

network managers to control the network’s distinct components.
 Con�iguration management helps in tracking and managing function of different versions of
hardware and software in the network.
 The main aim of fault management is to identify the network problems and notify it to the users.
 Proactive fault management aims to avoid the occurrence of problems.
 Performance management helps to evaluate and provide different features of network performance.
 The main aim of security management is to manage access to network resources so that the
network cannot be disrupted and secured information cannot be accessed without appropriate
authorisation.
 The accounting management is to evaluate network utilisation parameters that facilitate in
regulating the network usage.
 The Simple Network Management Protocol (SNMP) is a protocol suite that uses the TCPIIP protocol
suite to manage devices on the Internet.
 A manager, or management station, is a host that executes the SNMP client software.
 An agent, also known as a managed station, is a router (or host) that runs the SNMP server
application.

15.5 GLOSSARY

 Network management system (NMS): It is a programme or group of programmes that allows

network managers to control the network’s distinct components.
 Con�iguration management: It helps in tracking and managing function of different versions of
hardware and software in the network.
 Fault management: The main aim of fault management is to identify the network problems and
notify it to the users.
 Proactive fault management: Its aims to avoid the occurrence of problems.
 Performance management: It helps to evaluate and provide different features of network
performance.
 Security management: The main aim of security management is to manage access to network
resources so that the network cannot be disrupted.
 accounting management: It helps to evaluate network utilisation parameters that facilitate in
regulating the network usage.
 Simple Network Management Protocol (SNMP): It is a protocol suite that uses the TCPIIP protocol
suite to manage devices on the Internet.
 SNMP manager: It is a host that executes the SNMP client software.
 SNMP agent: It is also known as a managed station, is a router (or host) that runs the SNMP server
application.

9
 Data Communication and Computer Networks

15.6 SELF ASSESSMENT QUESTIONS

a. Essay Type Questions

1. Network device detection is aided by a network management system. What do you understand by
the term network management system?
2. The con�iguration management system stores the version information in a database for future
access. De�ine con�iguration management.
3. The security management system functions by separating network resources into authorised and
unauthorised domains. Describe the signi�icance of security management.
4. The performance management system can be reactive or proactive. Explain the role of performance
management in network system.
5. SNMP is an application-level protocol that allows a small number of management stations to control
a large number of agents. Discuss

15.7 ANSWERS AND HINTS FOR SELF ASSESSMENT QUESTIONS

a. Hints for Essay Type Questions

1. A network management system (NMS) is a programme or group of programmes that allows network
managers to control the network’s distinct components inside a larger network management
framework. Refer to Section Introduction
2. The main aim of con�iguration management is to observe the con�iguration information of the
network components. Refer to Section Network Management System
3. The main aim of security management is to manage access to network resources so that the
network cannot be disrupted and secured information cannot be accessed without appropriate
authorisation. Refer to Section Network Management System
4. The main aim of performance management is to evaluate and provide different features of network
performance so that internetwork performance can be maintained at a satisfactory level. Refer to
Section Network Management System
5. The Simple Network Management Protocol (SNMP) is a protocol suite that uses the TCPIIP protocol
suite to manage devices on the Internet. Refer to Section Simple Network Management Protocol
(SNMP)

@ 15.8 POST-UNIT READING MATERIAL

 https://www.itprc.com/what-is-snmp/
 https://www.google.co.in/books/edition/Network_Management_Concepts_And_Practice/FV9z-
JMLHHgC?hl=en&gbpv=1&dq=advantages+and+disadvantages+of+network+management+syste
m&pg=PA147&printsec=frontcover

15.9 TOPICS FOR DISCUSSION FORUMS

10
UNIT 15: Network Management System
 Discuss the concept of a network management system with your friends and classmates. Also, try to
�ind some real world examples based on network system.

11