Professional Documents
Culture Documents
1 - NWM Introduction and Basics PDF
1 - NWM Introduction and Basics PDF
Chapter 1
Data Communications
and
NM Overview
Outline
• Analogy of telephone network
• Data and telecommunication network
• Distributed computing environment
• Internet
• Protocols and standards
• IT management
• Network and system management
• Current status and future of network management
Notes
Telephone Network
• Characteristics:
• Reliable - does what is expected of it
• Dependable - always there when you need
it (remember 911?)
• Good quality (connection) - hearing each
other well
• Reasons:
• Good planning, design, and implementation
• Good operation and management of
network
Notes
To other
Sectional Center Sectional Center Primary centers
Class 2 switch Class 2 switch Toll centers
End offices
Notes
•Tele-end (Loop),2 end offices(direct trunk),end-toll(toll c
•Notice the hierarchy of switches
• Primary and secondary routes programmed
• Automatic routing
• Where is the most likely failure?
• Use of Operations Systems to ensure QoS
Network Management: Principles and Practice 1-4
© Mani Subramanian 2000
Chapter 1
Notes
Terminal Terminal
Host
Voice
Voice
Telecommunication network
Notes
•Circuit switched vs packet switched vs message switch
•Computer data is carried over long distance by
telephone (telecommunication network)
• Output of telephone is analog and output of
computers is digital
• Modem is used to “modulate” and “demodulate”
computer data to analog format and back
• Clear distinction between the two networks is
getting fuzzier with modern multimedia networks
Network Management: Principles and Practice 1-6
© Mani Subramanian 2000
Chapter 1
Ethernet
Workstation
Host
Notes
• Driving technologies for DCE:
• Desktop processor
• LAN
• LAN - WAN network
LAN-WAN Network
LAN A LAN B
Bridge / Bridge /
Router Router
Bridge /
Router
LAN C
WAN
communication link
Notes
• Major impacts of DCE:
• No more monopolistic service provider
• No centralized IT controller
• Hosts doing specialized function
• Client/Server architecture formed the core
of DCE network
Client/Server Model
Request
Control
transfer
Client Server
Control
transfer
Response
Notes
• Post office analogy; clerk the server, and the
customer the client
• Client always initiates requests
• Server always responds
• Notice that control is handed over to the receiving
entity.
Client/Server Examples
Client A Client Z
Server
(a) Se rve r with M ultiple Clients
Client
(joe.stone)
to sally.jones@dest.com
Bridge
Domain
Mail server Name
Server
(b) Dual Role of Clie nt-Serv er
Notes
Notes
Internet Configuration
Workstation
Mail Server
(Joe)
Workstation
LAN A LAN B
Bridge / Bridge /
Router Router
Domain
Name Bridge /
Server Router
LAN C
Gateway
WAN
Gateway
LAN X
Bridge /
Router
Bridge /
Bridge / Router
Router
LAN Y LAN Z
Workstation
Notes
• Walk through the scenario of e-mail from Joe to Sally
• Communication architecture
• Modeling of communication systems, comprising
• functional components and
• operations interfaces between them
• Communication protocols
• Operational procedures
• intra- and inter-modules
• Communication standards
• Agreement between manufacturers on protocols
of communication equipment on
• physical characteristics and
• operational procedures
Notes
• Examples: (Students to call out)
Communication Architecture
User A User Z
Peer-Protocol Interface
Physical Medium
User A User Z
Peer-Protocol Interface
Transport Layer
Transport Layers Transport Layers
Conversion
Notes
• Inter-layer interface: user and service provider
• Peer-layer protocol interface
• Analogy of hearing-impaired student
• Role of intermediate systems
• Gateway: Router with protocol conversion as
gateway to an autonomous network or subnet
Layer 7 Application
Layer 6 Presentation
Layer 4 Transport
Layer 3 Network
Layer 1 Physical
Physical medium
Notes
• Importance of the knowledge of layer structure
in NM
Notes
• Importance of services offered by different layers
and the protocol conversion at different layers in NM
Us er A UD Us er Z
Physical Physical
(D)PDU Data stream
Physical Medium
Notes
• What is the relevance of PDU model in NM?
Gateway
DTE-A A N Z
DTE-N1 N1 N2
Notes
•Sub N/W independent convergence prot
•Sub N/W dependent convergence prot
•Sub N/W dependent Adapter/Access Protocol
•cc:mail from a station in Novel IPX network to
Network Management: Principles and Practice 1-19
an Internet©station with SMTP
Mani Subramanian 2000 e-mail
Chapter 1
SNICP
Network
IP
Path Control Network SNDCP
SNDAP
Figure 1.18 Comparison of OSI, Internet, and SNA Protocol Layer M odels
Notes
• Similarity between SNA and OSI
• Simplicity of Internet; specifies only layers 3 and 4
• Integrated application layers over Internet
• Commonality of layers 1 and 2 - IEEE standard
Application Protocols
OSI User Internet User
Terminal
VT TELNET
Application
Mail / Message
MOTIS SMTP
Transfer
Management
CMIP SNMP
Application
Notes
Internet user OSI user
Telnet Virtual Terminal
Notes
Challenges of IT Managers
• Reliability
• Non-real time problems
• Rapid technological advance
• Managing client/server environment
• Scalability
• Troubleshooting tools and systems
• Trouble prediction
• Standardization of operations - NMS helps
• Centralized management vs “sneaker-net”
Notes
Network Management
Network
Management
Notes
• OAM&P
• Operations
• Administration
• Maintenance
• Provisioning
Users
TT Restoration
New Performance & Traffic Data
Technology
Fault TT
Installation
Notes
NM Components
NMS
Network Network
Agent Agent
Network Network
Objects Objects
Notes
Interoperability
NMS Messages NMS
Vendor A Services & Protocols Vendor B
Application
Services
Objects Objects
Management
Vendor A Vendor B
Protocol
Objects Objects
Transport
Protocols
Notes
• Message exchange between NMSs managing
different domains
Notes
1
Computers 1940s-1950s
2
Network Management
Administration deals with keeping track of resources in the network and how
they are assigned. It includes all the "housekeeping" that is necessary to keep
the network under control.
3
Management Functions and Domains
A common way of characterizing network management functions
is FCAPS - Fault, Configuration, Accounting, Performance and
Security. It is ISO Architecture for Network Management. The five
functional areas form the basis of all network management
systems for both data or telecommunications.
Functions
Fault
Management Domains/Layers
Configuration
Management
Accounting
Management
Performance
Management
Security
Management
Aftab Hussain CIIT Abbottabad
4
Fault Management
• Problem identification
• Problem isolation
• Analysis procedures & tools
• Problem resolution
Configuration Management
5
Accounting Management
• System usage
• Disk usage
• Link utilization
• CPU time
• License metering
Performance Management
To measure and make available various aspects of
network performance for network performance
monitoring and optimization. The network
performance variables include network throughput,
user response times, and line utilization.
– Traffic analysis
– Baseline performance
– Trending performance
– Capacity planning & system sizing
– Application Performance
6
Security Management
To control access to network resources so that the
network cannot be sabotaged and sensitive
information can only be accessed by those with
authorization.
Network Management
7
Polling and Event Reporting
• Availability
• Response time / RTT
• Accuracy
• Throughput
• Utilization
• Arrival rate
• Latency / Delay
• Bandwidth
• Loss
• Path / Routing
8
Network Management System
A network management system (NMS) is a collection of tools for
network monitoring and control.
9
Network Monitoring Information
Network Management
10
OSI Network Management Model
Manager Agent
SNMP (Internet)
Communication Communication
CMIP (OSI)
Module Module
11
Management Database
12
Two-Tier Network Management Model
The manager manages the managed element. There is a database in the
manager, but not in the agent. The manager queries the agent and receives
management data, processes it and stores it in its database.
MDB Manager
Managed objects
Unmanaged objects
• Agent built into network element, Example: Managed hub, managed router
• An agent can manage multiple elements, Example: Switched hub, ATM switch
• MDB is a physical database
• Unmanaged objects are network elements that are not managed - both physical
(unmanaged hub) and logical (passive elements)
Aftab Hussain CIIT Abbottabad
Managed objects
MDB Management Database
Agent process
13
MoM Network Management Model
MoM presents integrated view of domains. Manager of Managers (MoM)
operate, administer, maintain and provision the networks and elements using
‘probes’ to interrogate and interact with the lower level Management Systems.
14
Geographical MoM
15