You are on page 1of 30

Telecommunications Network

Management
Telecommunication network

 Characteristics
 Reliable - does what is expected of it
 Dependable - always there when you need it
 Good quality (connection) - hearing each other well
 Reasons
 Good planning, design, and implementation
 Good operation and management of network
Operations Systems / NOC
 Operations support systems
 Monitor telephone network parameters
 S/N ratio, transmission loss, call blockage, etc.
 Real-time management of network
 Trunk (logical entity between switches) maintenance
system measures loss and S/N.Trunks not meeting
QoS are removed before customer notices poor
quality
 Traffic measurement systems measure call blockage.
Additional switch planned to keep the call blockage
below acceptable level
 Operations systems are distributed at central offices
 Network management done centrally from Network
Operations Center (NOC)
Data Communication Network
Internet Configuration
Internet Topology
http://personalpages.manchester.ac.uk/staff/m.dodge/cybergeography/atlas/topology.html
TCP/IP Based Networks
 TCP/IP is a suite of protocols
 Internet is based on TCP/IP
 IP is Internet protocol at the network layer level
 TCP is connection-oriented transport protocol
and ensures end-to-end connection
 UDP is connectionless transport protocol and
provides datagram service
 E-mail, WWW, FTP, Telnet: TCP/IP
 Network mgmt. (SNMP): UDP/IP
 ICMP: part of TCP/IP suite
Comparison
Telephone Network TCP/IP, Internet

Terminal Terminal
telephone PDAs, PC, Workstations, …
Application (Content) Application (Content)
Voice Data: File, Message
Voice, Image, Video.
Bandwidth Requirement Bandwidth Requirement
Static (64 kbps) Dynamic (kbps ~ Mbps)
Transmission Transmission
Loop: UTP Access: UTP, Coaxial Cable, …
Trunk: Optical Fiber Trunk: Coaxial Cable, Optical Fiber
Network Elements (NEs) Network Elements (NEs)
CPE, Switch, Mux, Hub, Switch, Bridge, Router
Cross connect
Comparison (cont.)
Telecommunication Network TCP/IP, Internet
Addressing Addressing
telephone number MAC, IP, Port, Domain Name, URL
Intelligent Networks
Network Configuration Network Configuration
fixed, or Changed frequently
seldom changed
Growth Growth
Stable, not changed grow in dog years, new applications
Network Management Network Management
Well planned ?
NOCs Network Management Tools/Systems
Protocols used in NM
 SNMP(v1, v2, v3)
 Simple Network Management Protocol
 ICMP
 Internet Control Message Protocol
 Ping , traceroute
 ARP/RARP
 Address Resolution Protocol/ (Reverse ARP)
 TCP
 Socket
 Telnet/SSH
 HTTP+XML
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
What is Network Management?
 Goal
 To ensure that the users of a network receive the IT services with
the quality of service (QoS) that they expect.

"Network management includes the deployment, integration


and coordination of the hardware, software, and human
elements to monitor, test, configure, analyze, evaluate,
and control the network and element resources to meet the
real-time, operational performance, and Quality of Service
requirements at a reasonable cost."
Top-down View of NM functions
Network
Management

Network Network Network


Provisioning Operations Maintenance

Planning Fault Management / Service Restoration Fault Management

Design Configuration Management Trouble Ticket


Administration
Performance Management / Traffic Management
Network Installation
Security Management
Network Repairs
Accounting Management
Facilities Installation
Reports Management & Maintenance
Routine Network
Inventory Management Tests

Data Gathering & Analyses

Figure 1.21 Network Management Functional Groupings


NM Functional
Network

Users

Management Config uratio n Data


Decision

TT Restoratio n
New Performance & Traffic Data
Technology

Engineering Group Operations Group I & M Group


NOC
- Network Planning & -Network Installation &
Design - Network Operations Maintenance

Fault TT

Installa tion

Figure 1.22. Network Management Functional Flow Chart


NM Functional Requirements
 Fault Management
 detection, isolation and correction of abnormal operations
 Configuration Management
 identify managed resources and their connectivity, discovery
 Accounting Management
 keep track of usage for charging
 Performance Management
 monitor and evaluate the behavior of managed resources
 Security Management
 allow only authorized access and control

FCAPS
Fault Management
 Manages network problems to keep the network
running reliably and efficiently.
 Fault management process involves the following
steps
 Detecting the problem symptoms.
 Isolating the problem.
 Fixing the problem automatically (if possible) or manually.
 Logging the detection and resolution of the problem.
Configuration Management
 Configuration Management monitors network and
system configuration information and stores it in a
configuration management database.
 The maintenance of this database allows network
administrators to track hardware, software, and
other network resources
Configuration Management (2)
 Each network device has a variety of information
associated with it:
 Software version information for the operating system,
protocol software, or management software.
 Hardware version information for the interfaces or hardware
controllers.
 Contact information indicating who to contact if problems with
the device arise.
 Location information indicating the physical location of the
device.
Configuration Management (3)
 CM Information Associated with a Managed Device
Accounting Management
 Measures network utilization parameters in order
to regulate individual and group uses of the
network.
 Minimizes network problems and maximizes
fairness of user access to the network because
network resources can be portioned based on
network capacity and user needs.
Performance Management
 Maintains internetwork performance at acceptable levels by
measuring and managing various network performance
variables.
 Performance variables include network throughput, user
response times, line utilization, and others.
 Performance management involves three basic steps:
1. Gathering data relating to key performance variables.

2. Analyzing data to determine the normal (baseline)


performance levels.
3. Determining appropriate performance thresholds for each
variable so that exceeding these thresholds indicates a
network problem worthy of attention.
Performance Management (2)
Performance
Console Window Help
Action View Favorites
Tree Favorites
Console Root
System Monitor 100
Performance Logs and Alerts
80

60

40

20

10
Last 3.000 Average 16.154 Minimum 2.000
Maximum 63.000 Duration 1:40
Color Scale Counter Instance Parent Object Computer
1.000 % Processor Time _Total --- Processor \\LONDON
1.000 % Processor Time explorer --- Process \\LONDON
1.000 % Disk Time 0 C: D: --- PhysicalDisk \\LONDON
1.000 Page/sec --- --- Memory \\LONDON
1.000 Bytes Received/sec Default FTP Site - - - FTP Service \\LONDON
Performance Management (3)
 Reactive
 when performance becomes unacceptable (that is,
a user-defined threshold is exceeded), the
managed device reacts by sending an alert to the
network management system (NMS).
 Proactive
 simulation is used to project how network growth
will affect performance metrics. These simulations
alert administrators to impending problems before
they affect network users.
Performance Management (4)
 Reactive PM Components
 The management entity continually monitors performance
variables in managed devices.
 When a particular performance threshold is exceeded, the
NMS or the managed device detects the problem.
 If the managed device detects the problem, it generates
an alert and sends it to the NMS.
 The NMS takes an appropriate action, such as alerting the
network administrator.
Windows Task Manager
Windows Task Manager Windows Task Manager
Windows Task Manager File Options View Help
File Options View Windows Help
File Options View Help
Applications ProcessesPerformance
Applications Processes
Applications Performance
Processes Performance
CPU Usage CPU Usage History
Task Image Name PID CPUStatus
CPU Time Mem Usage
Building Schematic
System - Paint
Idle Process 0 96Running
4:52:37 16 K
System 8 00
Memo to Supervisor - WordPadRunning 0:00:27 212 3%
K
smss.exe 168 00 0:00:00 344 K
Calculator
csrss.exe 196 00Running
0:00:20 1,820
MEMK Usage Memory Usage History
winlogon.exe 220 00 0:00:09 4,408 K
My Computer
services.exe 148 00Running
0:00:14 8,228 K
lsass .exe 160 00 0:00:32 15,768 K
svchost .exe 472 00 0:00:00 2,648 K
spoolsv .exe 492 00 0:00:00 10 1600K
4,184 K
mspaint .exe 624 00 0:00:04 352 K
msdtc .exe 704 02 0:00:00 3,428 K
Totals Physical Memory (K)
inojobsv .exe 808 00 0:07:46 5,704 K
Handles 5932 Total 130612
dfssvc .exe 824 00 0:00:00 2,336 K
Threads 381 Available 27740
svchost .exe 840 00 0:00:00 3,416 K
Processes 30 System Cache 50704
ismserv .exe 864 00 0:00:00 5,348 K
llssrv .exe 880 00 0:00:01 3,860 K Charge (K)
Commit Kernel Memory (K)
ntfrs.exe 928 00 0:00:09 1,108
TotalK 101600 Total 22804
regsvc.exe 968 00 0:00:00 844 K
Limit 310892 Paged 15704
Peak 116896 Nonpaged 7100
Show processes from all users End Process
End Task Switch To New Task...
Processes: 30 CPU Usage: 3% Mem Usage: 101600K / 310892K

Processes: 30 CPU Usage: 6% Mem Usage: 103452K / 310892K


Processes: 30 CPU Usage: 2% Mem Usage: 103500K / 310892K
Security Management
 Access control
 Controls access to network resources, and prevents network
sabotage (intentional or unintentional) and unauthorized access to
sensitive information.
 Aids administrators in creating a secure network environment. This
includes:
 partitioning network resources into authorized and unauthorized areas,
 mapping groups of users to those areas, and
 monitoring, policing, and logging user access to resources in those
areas.
 Security monitoring
 Security event collection
 Event analysis, correlation and alert generation
 Alert handling
Infrastructure for network management
definitions:

managing entity agent data


managing managed devices contain
data managed device
entity managed objects whose
data is gathered into a
agent data Management Information
network
management Base (MIB)
managed device
protocol

agent data
agent data
managed device

managed device
Network Management Systems
 A network management system (NMS) is a collection of
tools for network monitoring and control
 based on the manager-agent paradigm
 the manager sends mgmt requests to one or more agents
 an agent performs the requested operation and returns results
 when agents detect faults and they report to the manager
 NMS typically provides a GUI through which most or all
management tasks can be performed
 Many commercial and freely available NMSs exist:
 Commercial
 HP OpenView, IBM NetView, Sun Net Manager, Cisco works and
etc.
 Open source
 OpenNMS , Nagios and etc.
Interoperability
NMS Messages NMS
Vendor A Services & Protocols Vendor B

Network Network Network Network


Agent Agent Agent Agent

Network Network Network Network


Objects Objects Objects Objects

Application
Services
Objects Objects

Management
Vendor A Vendor B
Protocol

Objects Objects
Transport
Protocols

(b) Services and Protocols

Figure 1.23 Network Management Dumbbell Architecture

Notes
• Message exchange between NMSs managing different domains
Standard Management Frameworks
 Internet Network Management Framework (IETF)
 SNMPv1

 SNMPv2

 SNMPv3

 OSI Network Management Framework (ISO/ITU-T)


 CMIP (X.700 Series)

 Telecommunication Management Network (ITU-T)


 TMN (M.3000 Series)

 Distributed Management Task Force (DMTF)


 DMI, CIM, WBEM

 TeleManagement Forum
 MTNM, eTOM, and etc.

You might also like