CHAPTER 1:

INTRODUCTION TO
NETWORK MANAGEMENT

NETWORK MANAGEMENT
Outlines
 What is network management?
 ISO network management categories
 Network management architecture
 Evolution of network management
 Management tools
 Network Documentation
Can you give any example of
common network problems?
Common Network Problems
 Loss of connectivity (Link, Node, Interface)
 Duplicate IP address (Procedural)
 Intermittent problems
 A system interface problem in a shared medium
 Network configuration issues
 Non-problems
 The cause of failure is a mystery. (Turn off , Turn on)
 Performance problems
 The cause of long network delay and increasing the
response time
Network Management?
 Network management refers to the activities, methods,
procedures, and tools that pertain to the operation,
administration, maintenance, and provisioning of networked
systems.

 What is the goal of network management?

 To ensure that the users of a network receive the IT services
with the quality of service (QoS) that they expect
Network Management?
 Why do we need network management?
 Why good network management is important?
 ISO Network Management Categories

The ISO divided the Network Management Model into five categories

Functions of Network
Management Model

Configuration Accounting
Fault Management
Management Management

Performance Security
Management Management
 Fault management – log, detect and respond to
fault conditions in the network
 Configuration management – track devices and
their hardware and software configurations
 Accounting management - specify, log and control
user access to network resources
 Performance management – quantify, measure,
report, analyze and control performance of
network components
 Security Management – control access to network
resources according to some well-defined policy
HOW DOES FCAPS PROMOTE
NETWORK MANAGEMENT?
What is FCAPS?
Fault Management

 Function: detects, logs, and notifies network managers of any

network issues
 network problems are found and fixed
Scenario: Link failure
 When a network event occurs, an alarm is sounded
 network manager detects the alarm and begin to identify what the
problem is in the network (link failed).
 troubleshoot the problem until you have found a solution that works
and
fixes the problem. Figure 1: Link Failure- If possible,
fault management can
 log the initial fault and what you did to correct it, so that if it
happens again you don't have to re-create your efforts. In other automatically fix network issues -
words, if that little red light lights up again, you'll know what to do >network will be detour
because you did it before
Configuration Management

 Function: involves collection and storage of

configuration from various network devices,
and includes tracking changes to a device
configuration
 Changes, additions, and deletions from the
network must be coordinated with the network
manager or network management personnel,
often in a network operations center (NOC)
 Before any change is made to the network, it is
good practice to have all parties involved in
the change discuss what will change, how it will
be changed, who will make the change, when
the change will occur and what to do if the
change doesn't work
Configuration Management (cont.)
 The configuration management comprises a number of elements:
 Inventory hardware? An inventory of active and spare network
hardware.
 Inventory software? An inventory of software in use and its
associated license keys.
 Configuration information? A baseline of hardware firmware
updates and software patches that have been applied within your
network, and the function of each update and patch. The baseline is
often used in the installation of new devices as a template or
standard.
 Change control? A process whereby network hardware and software
changes are managed in a controlled environment without back-out
procedures in place, in case an update does not take or goes bad,
and the network is down as a result. You can think of change control
as the Reset button on your network.
Accounting Management

 Function: billing and track network resource

utilization
 intended to measure network utilization so
that individuals or group users on a network
can be regulated to prevent one person, or
group of people, from using all the network
bandwidth and keeping others from using the
network to its full capacity.
 also provides the network manager a means
to bill network usage back to customers or
internal departments
Performance Management

 Function: measure various aspects of

network performance
 To make sure that the network can be
maintained at an acceptable
threshold, not over- or underutilized
 provides you the tools and methods to
collect and analyze network statistics,
enabling you to "paint a picture" of
your network and how it behaves.
Performance Management (cont.)
 Performance management baseline and trend analyses examine the
following network characteristics:
 Network-capacity planning? The total amount of network bandwidth.
 Availability? The total amount of time your network is up and available to
its users.
 Response time? The total amount of time it takes for a transaction to
complete (for example, a frame being sent from an end user to its
destination).
 Throughput? The average network bandwidth your network is capable of
sustaining. If you have a 100-Mbps Fast Ethernet local-area network (LAN),
but your users can use only about 50 kbps of it, there is likely a throughput
issue.
 Utilization? The average amount of bandwidth and time your network is
being used by the network end users.
Security Management

 Function: controlling access to resources in the network

 Security management systems perform the following
functions:
 The identification of sensitive network resources
 The establishment of maps between sensitive network
resources and user sets, mapping out which users can access
which resources
 The monitoring of sensitive network access points and the
logging of inappropriate or failed access to these resources

Security Management (cont.)
 The components of security management are as follows:
 Policy? The organization has a security policy on user access to
certain network resources. The policy spells out who can access what
and what happens when a security compromise occurs.
 Authority? An individual is identified who has the authority to grant
access to sensitive network resources so that users cannot provide
themselves access to certain information.
 Access level? Sensitivity level of information is identified as well as
user access to these levels. Information can be categorized as
confidential, secret, or top secret.
 Exceptions? Any exceptions to the security policy or access level must
be documented to prevent accidental compromises.
 Logging? All activities are logged, whether users logging in to their
own machines or someone attempting to log in to a network switch.
Question
 List three common characteristics share by
Accounting management and Performance
management
Network Management Architecture
Network Management Architecture
 Managed Device
 Devices to be monitored/controlled, e.g., router, switch, hub,
bridge, workstation.
 Managing Entity
 Used by the manager/Admin to do network management
 PC, notebook, terminal, etc., installed with a software called
Network Management System (NMS)
 NMS displays/analyzes data from management agents
 Network Management Protocol
 Runs between the managing entity and the managed
devices
E.g., SNMP: Simple Network Management Protocol
 Network Management Tools
Company Product URL Comments

Network Observer 8 http://www.netinst.com/html/observer.ht Supports Ethernet, Token Ring, FDDI, GigaBit and
Instruments ml Windows 98/ME and NT/2000/XP. Includes capture
for protocol analysis. Price is $995.00

Precision LANwatch32 v6.0 http://www.guesswork.com/snmptool.ht Described to be an easy-to-use command-line application

Guesswork ml that allows you to GET a variable, SET a variable, get
the NEXT variable, or even get all the variables.
Provides programs for receiving ALERTS, as well as
a simple monitoring program that allows you to tell if
your hosts are SNMP reachable, IP reachable, or not
reachable. Allows you to remotely monitor, gather
and change networking information from hosts on
your network. Enables you to diagnose existing
problems on the network, predict where problems are
likely to occur, pinpoint faulty routers and interfaces,
and, in general, exert control over your network.

Cisco Small Network http://www.cisco.com/warp/public/cc/pd/ Cisco produces many network management products. These
Management wr2k/wrsnms/ products seem most appropriate for audience of this
LAN Management book.
http://www.cisco.com/warp/public/cc/pd/
wr2k/lnmn/
MDF
 Main Distribution Frame
 The MDF is the main computer room for servers, hubs,
routers, DSL's, etc. to reside.
 It interconnects and manages the telecommunications
wiring between itself and any number of IDFs
 The MDF connects private or public lines coming into a
building with the internal network
MDF Scheme
IDF
 Independent Distribution Frame
 The IDF is a remote room or closet connected to the MDF by
fiber optic cable
 Cables entering a building run through a centralized MDF, then
each individual IDF and then on to specific workstations
 For example, an enterprise that encompasses a building with
several floors may have one MDF on the first floor and one IDF
on each of the floors that is connected to the MDF
 Hubs and patch panels can be found in IDF
IDF Scheme

IDF 1

IDF 2
Network Documentation
 Having a well documented network offers a number
of advantages:
 Troubleshooting
 When something goes wrong on the network (e.g:
wiring problem), up to date documentation is an
importance reference to guide the troubleshooting
effort. It will save your money and time in isolating the
problem.
Network Documentation
 Training new administrators
 New administrator do not have time to try and figure
out where cabling is run, what cabling is use. The up-to-
date documentation helps new administrator quickly
see the network layout.
 Contractors and consultants
 Consultants and contractors occasionally may need to
visit the network to make future recommendation to
network. If it were missing, more time and money would
be required.
Information in Document

1. IP addresses of all devices on the network with static IP addresses.

2. Server documentation on all servers as outlined in the "Server
Documentation" document.
3. Network drawings showing:
 The locations and IP addresses of all hubs, switches, routers, and firewalls on
the network.
 The various security zones on the network and devices that control access
between them.
 The locations of every network drop and the associated switch and port on
the switch supplying that connection.
 The interrelationship between all network devices showing lines running
between the network devices.
 All subnets on the network and their relationships including the range of IP
addresses on all subnets and netmask information.
 All wide area network (WAN) or metropolitan area network (MAN)
information including network devices connecting them and IP addresses of
connecting devices.
Information in Document – cont.

4. Configuration information on all network devices

including:
 Switches
 Routers
 Firewalls
5. Configuration shall include but not be limited to:
 IP Address
 Netmask
 Default gateway
 DNS server IP addresses for primary and secondary DNS servers.
 Any relevant WINS server information
 Information in Document – cont.
6. Network connection information including:
 Type of connection to the internet or other WAN/MAN including T1,T3,
frame relay.
 Provider of internet/WAN/MAN connection and contact information for
sales and support.
 Configuration information including netmask, network ID, and gateway.
 Physical location of where the cabling enters the building and circuit number.
7. DHCP server settings showing:
 Range of IP addresses assigned by all DHCP servers on all subnets.
 Subnet mask, default gateway, DNS server settings, WINS server settings
assigned by all DHCP servers on all subnets.
 Lease duration time
Additional Document Contents

 All key service accounts an login account user-id and

passwords
 Procedures on how to maintain the network technology,
including Operating Systems, security related services,
backup and disaster recovery (business continuity), and
firewall technologies
 Operating System and application licensing
 Key contact information

The above is just the basic items that need to be

documented within a computer network. There are many
more aspects to network documentation.
Best Practice

 Label
 Create the labeling scheme with the idea that the
structure of the network will be constantly changing
as will the people who use the network
 Logbook
 Log the configurations of your servers, workstations,
and users
 Example: server log, workstation log, security log
Documentation Tools
 Microsoft Visio
 Physical layout (OSI Layers 1 & 2)
 Logical Layout (OSI Layer 3)

 Flow Charting

 MDF & IDF planning and layout

 Network services & application structure (OSI layers 4-

7)
 Auto discovery of network topologies
 Visio

 Diagraming
 Devices
Internet

 Topology

 Data Flow
Router

Workstation #1 Server

Ethernet

Workstation #2 Laser printer

 MDF & IDF Layouts

 Documentation will include

 Map of location
 physical layout of rack
mounts
 auxiliary equipment, and
servers
 patch panel labels to
identify cable
terminations.
 Identification and
configuration details of all
Created with Microsoft Visio 2000 equipment located in the
distribution facility
Reflection

Based on the problems you have

identified, did you think network
management system can overcome
the issues? Why?
Answer
 Monitoring and measuring of network bandwidth
utilization.
 Analysis of usage patterns and the trend of those
usage patterns. Is usage decreasing, increasing, or
holding steady?
 Ongoing measurement of network bandwidth. This
measurement can result in bandwidth utilization and
billing information, helping you ensure there is
enough network bandwidth for all your users.
References
 http://etutorials.org/Networking/Lan+switching+fir
st-
step/Chapter+11.+Switch+Network+Management
/Network+Management+Model/
 http://www.solarwinds.com/network-monitoring-
design-philosophy
 www.comp.hkbu.edu.hk/~chxw/course/comp4690/
notes/a02.ppt