02 Network Management Basics - PPT-72

Network Management Basics
ZTE University
Content
Overview of Network Management

System Architecture
Management Functions
2
Content of This Topic

 Concept and Development of Network
Management
 Theoretical Basis – Telecommunication

Management Network (TMN)
 Theoretical Basis - Organizations and Standards
 Development Trends
3
Concept and Development

 A structured communication network Development Stages
offers improved operating efficiency and
reliability. By properly scheduling and
controlling network resources, it satisfies
Centralized
users' requirements for high-quality
Distributed
network services with the optimal
Management
efficiency and the highest reliability.
Distributed Computer-
Assisted Management
Manual
Management
4
Limits of Early-Stage NM and Requirements

for New NM
Low Integration
Unshared Resources
Limits of Early-Stage NM Manual Intervention
Non-standard Interfaces
Low Efficiency, High Cost
Evolution of the Telecom Industry

Factors Pushing the Development Emergence of New Services
of NM Customer Requirements
Competitiveness
Open and Integrated

Requirements for New NM Distributed
Data Shared
5
Theoretical Basis – TMN (1)

 The TMN (Telecommunication Management
Network) provides a network architecture specified
by a series of protocols, which is defined by ITU-T
for managing telecommunication networks. It is
logically separate from the telecommunication
networks.
 The TMN defines a set of standard interfaces for
controlling and operating the telecommunication
networks. The series of technical standards and
specifications focus on the functional model,
information model and interface model of the TMN.
6
Theoretical Basis – TMN (2)

 The following figure illustrates the relationship between a TMN and the
telecommunication network that is managed.
7
Logical Layers of TMN (1)
Business
Management
Layer
Service
Management Layer
Network Management Layer
Element Management Layer
8
Logical Layers of TMN (2)

 Business Management
 Provides the management functions that support the business
decision of enterprises, and performs functions related to business
aspects, analyzes trends and quality issues, for example.
 Service Management
 Provides the functions for the handling of services in the network:
service provisioning, service monitoring, global fault diagnosis and
service quality guarantee.
 Network Management
 Provides the functions for managing all NEs in the area that is
managed: coordinating and controlling the actions of all NEs from
the aspect of the whole network.
 Element Management
 Provides the functions for handling individual or multiple network
elements, coordinating the communication between network
elements and the network management layer.
9
Five Management Functions of TMN (FCAPS)
Security Fault
Management Management
Performance Configuration
Accounting
Management
10
Information Model of TMN

 The TMN defines an information model for the description and exchange of
management information. The information model is based on OSI's
management information model.
 Manager/Agent Concept
 Managed Object (MO), Managed Object Class (MOC), Guidelines for the Definition
of Managed Objects (GDMO),and Abstract Syntax Notation (ASN.1)
 Management Information Exchange: based on CMIP when Q3 interface is used
between modules.
Managed Open System

Open System for
Management
Management Information
CMIP Database
Management operation Execution

command
Manager Agent
Notification
Notification
Managed Object
11
Functions and Interface Model of TMN

g
 Function Blocks :
 OSF (Operation System
Function) TMN WSF
f
 MF (Mediation Function) f
 QAF (Q Adapter Function) q3
 DCF (Data Communication q3 OSF
x
Function) qx MF
 NEF (Network Element qx q3
Function) q3
qx
 WSF (WorkStation Function)
 Interfaces:
QAF NEF
 Q3
 Qx m
 F
 X
12
Summary
Four Logical Layers
 The TMN can be simply  Business Management
summarized into the  Service Management
following three aspects:  Network Management
 Four-Layer Architecture  Element Management
 FCAPS
 Q3
FCAPS
Q3 (Five Management Areas)
 GDMO - Object Definitions (Classes)  Fault
 CMIP - Management Operations (Methods)  Configuration
 OSI - Communications Protocol (Transport)  Accounting
 Performance
 Security
13
Organizations and Standards (1)

 TMF
 Telecommunication Management Forum (TMF) was founded in 1988,
headquartering in U.S. It pursues operation and business management
solutions for communication, media and information service providers.
TMF embraces over 600 members from 63 countries, including
telecommunication service providers, network operators, device vendors
and system integrators. Its main technical achievements include:
Telecommunication Operations Map (TOM), enhanced TOM (eTOM) and
Next-Generation Operation System and Software (NGOSS).
 3GPP
 The 3rd Generation Partnership Project (3GPP) was established in
December 1988. It makes 3G mobile phone system specifications based
on GSM core network and Universal Terrestrial Radio Access (UTRA)
radio interface. (Note that FDD is a technology used for WCDMA; while
TDD is a technology used for TD-CDMA.) The working scope of 3GPP
covers 3G telecom management principles and high level requirements,
telecom management architecture, Configuration Management (CM), Fault
Management (FM), Performance Management (PM) and Security
Management (SM).
14
Organizations and Standards (2)

 3GPP2
 The 3rd Generation Partnership Project 2 (3GPP2) was
established in January 1999. It makes 3G mobile phone system
specifications based on ANSI-4 core network and CDMA2000
radio interface. 3GGP2 is the standardization group for
CDMA2000. It shares related contents provided by 3GGP on the
upper layers of the network management framework. The available
network management version provided by 3GGP2 is Release 5.
 China Communications Standards Association (CCSA)
 CCSA/NMTC (TC7) makes network management standards. In the
technical committee, the WG1 (radio communication management
workgroup) makes the series of standards and specifications for
3G network management, including GSM, CDMA, GPRS,
WCDMA, CDMA2000 and TD-SCDMA radio communication
networks as well as their services and applications. CCSA has
made specifications of four parts in 17 volumes.
15
Development Trends of TMN

 Centralization
 Integration
 Distribution
 Intelligence
 Scalability
 Standardization
 Concept Change
16
Review of Key Points

 Logical Layers of TMN
 Management Functions of TMN
 TMN Architecture
 Information Model
 Function Blocks
 Interface Model
 Major Organizations and Standards
17
Content

System Architecture
18
Contents of This Topic

 Typical Architecture of Operation & Maintenance
System
 Networking Modes
 Access Modes and Client Types
 Interfaces and Protocols
19
Typical Architecture of Operation &

Maintenance System
20
Networking Modes
 Centralized Networking
 Domain-Based Networking
 Distributed Networking
 Cascade Networking
21
Networking Mode - Centralized Networking

Management
Center
EMS
Server in the Client-Group
server
Centralized EMS
DCN
… …
Client-1 Client-2
NE1 NE2 … NEn NEa NEb … NEm

22
Networking Mode - Domain-Based

Networking
Upper-Level
Management System
EMS Server in
EMS Server in DCN Management
Management EMS Domain 2
Domain 1 Server-1 EMS
Server-2
Domain 1 Domain 2
… …
Client-1 Client-2
23
Networking Mode - Distributed Networking

(Load Distribution)
Management Center
EMS APP EMS DB EMS

Server1 server2 WEB Client Group
server3
DCN
… …
Client-1 Client-2
24
Networking Mode - Distributed Networking

(Function Distribution)
Management Center
EMS EMS EMS EMS Client Group

PM Server FM server CM server server…
DCN
… …
Client-1 Client-2
25
Networking Mode - Cascade Networking

Management
Center
Upper- EMS
Server-3 Client Group
Level EMS
Server
NE
Lower-
Level EMS
Lower-Level DCN Server
EMS Server EMS
Server-1 EMS
Server-2
Domain 1 Domain 2
… …
Client-1 (Management Client-2 (Management
Domain 1) Domain 2)
26
Access Modes and Client Types
Access Modes of the Client:

 Local Client Access
 Remote Client Access
 Return Client Access GUI Client
Server
MML Client
Client Types:
 GUI
 MML
 WEB WEB Client
27
Local Client Access Mode

NMS
LAN/WAN
Server
Router
TCP/IP Network
Local Client
Local NE
In this access mode, the local client and the server locate in the
same LAN. The local client access mode is the most typical access
mode featuring convenience, security and high efficiency.
28
Remote Client Access Mode (1)

NMS
Router
X.25/Frame
LAN/WAN Remote Client
Server Relay/DDN
Router Router
TCP/IP Network
Local Client
Local NE
Remote clients are deployed in different LANs from the server.

They are connected to the server via routers through X.25, frame
relay, DDN or WAN, to implement remote monitoring,
maintenance and management of the network.
29
Remote Client Access Mode (2)

LAN 1 Server
TCP/IP Network
Local NE Local Client

DCN
LAN 2 LAN 3
TCP/IP Network TCP/IP Network
Remote NE Return Client Remote NE Return Client
This remote access mode is called return client access, in which the
clients locate in the LAN where NEs locate but not the LAN where the
server locates.
30

 Typical Architecture of Operation & Maintenance
System
 Networking Modes
 Centralized Networking
 Domain-Based Networking
 Distributed Networking
 Cascade Networking
 Access Modes and Client Types
 Local Access
 Remote Access
 Client Types (MML/GUI/WEB)
31
Introduction to Main Interfaces

 IF1 is the interface between an
EMS and an NE, also called Other Management
south interface. Generally, IF 1 Systems
is a private interface defined by
vendors. IF3
 IF2 is the interface between an
NMS and an EMS, also called NMS
north interface. Available IF 2
interfaces include CORBA, IF2
SNMP, FILE, DB, TL1, Syslog,
and MML etc. EMS
 IF3 is the interface between an IF4
NMS and another network
IF1
management system.
 IF4 is the interface between an NE NE
NMS and an NE. Generally, IF4
is a private interface. No
standard or protocol is available
now to specify IF4 interface.
32
Analysis of NM Interface Technologies - DB

 Generally, the equipment vendor opens a middle database to the NMS. The
Operation & Maintenance Center (OMC) of the vendor periodically updates the
data in the middle database. And the NMS periodically synchronizes its data
from the middle database.
Advantage Drawback
 Convenient interconnection,  DB is not applicable for alarm

simple development, convenient reporting due to its low
data recollection, easy security and poor real-time
installation and upgrade. performance. It is commonly
used for configuration and
performance management.
In addition, the data
synchronization of the NMS
may influence the system
performance.
33
Analysis of NM Interface Technologies - FILE

 The equipment vendor creates a file involving the local data at regular
time and places the file under a specific path. The NMS accesses and
obtains the file at regular time, or the vendor sends the file to the NMS
through FTP.
Advantage Drawback
 Simple development, convenient  Difficulty of data recollection;

installation and upgrade, interconnection problems
avoidance of the interference on caused by inconsistent file
system performance when formats; poor real-time
compared with DB. performance, which makes it
inappropriate for alarm
reporting. FILE interface is
generally used for
configuration and
performance management.
34
Analysis of NM Interface Technologies - MML

 MML interface is a character-string message interface. It,
based on TCP/IP, uses Socket to accomplish the
communication and interaction.
Advantage Drawback
 Simple, easy accessible, and  No standard is made to

low-cost. specify the interface.
Therefore, it is generally a
private interface of the
vendor and not proper
opened to external users.
35
Analysis of Q3 Interface
Designed on the base of Open System Interconnection
(OSI), a set covering seven layers of the OSI model
Contents Features
 OSI - Communications Protocol  Classified into transaction

(Transport) type and file transfer type
 GDMO - Object Definitions  Manager/Agent model
(Classes)  Use the Common
 CMIP - Management Operations Management Information
(Methods) Service Element (CMISE)
protocol
 Use the Common
Management Information
Protocol (CMIP) at the
application layer
36
Analysis of Q3 Interface - Advantages and

Drawbacks of CMIP
Advantage Drawback
 The best feature of CMIP is that  As a large and

each variable not only transfers comprehensive protocol,
information but also completes a CMIP occupies a lots of
certain network management resources and raises high
task, which relieve the burden of requirements for hardware
the manager and reduce the equipment.
network load.  Large amounts of CMIP
 CMIP ensures the security by processes running on the
using a series of security network proxy greatly
management methods, including increase the burden on the
authentication, access control network proxy. The MIB is too
and security log etc. complicated and difficult to be
achieved.
37
Introduction to Main Protocols - SNMP

 The Simple Network Management Protocol (SNMP) is a
protocol used at the application layer. It is used to for
managing network nodes in IP networks, including servers,
workstations, routers, switches and HUBs etc.
 The SNMP, being easy to use, is the factual network
management standard. It is mainly used for fault
management and configuration management in network
management systems. Generally, it is not used for
performance management because it does not support
operations on large amounts of data.
38
Introduction to Main Protocols - SNMP
SNMPV3 was
SNMPV2C is a released in 1998,
revision of SNMPV2 which inherits the
SNPMV2, released in system architecture as
1993, supports released in 1996. It
provides enhanced well as all functions of
SNMPV1, released distributed network SNMPV1 and
in May.1990, management, extends functions without
improving the SNMPV2. It introduces
supports monitoring the data types, a new security
and managing improves the security
performance. mechanism, which
computer networks. processing efficiency of supports
It becomes the large amounts of data, SNMPV2C still uses
the user authentication and
factual industry diversifies the fault encryption. In addition,
standard. processing capability, authentication mode
based on plaintext SNMPV3 specifies a
adds the sum set of network security
processing function, key specified in
SNMPV1. and access control
and improves the data rules.
deification language.
SNMPV1 SNMPV2 SNMPV2C SNMPV3
39
Introduction to Main Protocols - Advantages

and Drawbacks of SNMP
Advantage Drawback
 Simple, easy to implement,  Efficiency bottleneck in large-scale

low requirements for networks because SNMP is based on
resources the polling mechanism
 Widely applicable, low-cost,
 Not applicable to query large
and high cost performance amounts of data or query according
to complicated conditions
 Popular as the factual
 Low reliability due to the use of User
industry standard
Datagram Protocol (UDP)
 Not support the operations of
creating, deleting and acting etc.,
which must be triggered by set
commands
 Low security due to the lack of a
comprehensive security mechanism
40
Introduction to Main Protocols - CORBA

 The Common Object Request
Broker Architecture (CORBA) is
a solution defined by the Object Application Common
Management Group (OMG) that Object Utility
enables the inter-operation of
different software/hardware
products in a distributed
computer environment. ORB
 OMA Reference Model

 The CORBA supports the
following applications for
Object Service
network management:
 Configuration Management
 Fault Management
 Performance Management
41

and Drawbacks of CORBA
Advantage Drawback
 High scalability of the framework, and

high service support capability  The configuration of
 Simple interface specification CORBA is more
 Convenient interconnection and complicated than SNMP
extension due to the Object Request configuration.
Broker that shields the low-level details
 Effective for application inter-operation  A high-cost third-party
and system integration in a CORBA software platform
heterogeneous environment
is needed.
 Easier implementation than Q3 because
it avoids the complication caused by
small granularities
 More powerful than SNMP with better
real-time feature
 Popularized and widely accepted
42
Introduction to Main Protocols - TL1

 Overview
 Transaction Language 1 (TL1), defined by Telecordia (previous
BELLCORE), is an ASCII man-machine interaction protocol. It is
widely used as the telecom management protocol, especially in
North America.
 TL1 is a standard Command Line Interface (CLI). Compared with
other CLIs, TL1 uses conventional syntax and fixed format. A fixed
format is used by different commands.
 Features
 Man-machine language Example of TL1 Input Message:
 Readable messages ENT-EQPT:ABC:SLOT-3:123:210198,08-06-
 Delayed activation 12,23-00-00:OC3::OOS;
 Reporting initiative
 Acknowledgement mechanism
 TL1 applications for network management: configuration
management, fault management, and performance
management
43

and Drawbacks of TL1
Advantage Drawback
 The simple standard interface  TL1 uses the format of

protocol makes TL1 interface command line. As a north
easy to implement and interface, it is generally
convenient to debug. Text-based used to interconnect work
commands are easy to order systems at the upper
understand. application layer.
 With the reporting initiative
function, it can report current
performance, alarm and
configuration data to users.
 TL1 provides a message
acknowledge mechanism, which
ensures a high reliability.
44
Introduction to Main Protocols - Syslog

 Overview
 Syslog is a UDP-based communication protocol defined
by University of California Berkeley Software
Distribution (BSD).
 Syslog is transferred at a high speed based on UDP.
However, it can not be ensured that the Syslog
successfully reaches the server on the opposite end.
Port 514 is used for Syslog.
 Syslog applications for network management
 Syslog is generally used to report alarms in one
direction in a network management system.
45

and Drawbacks of Syslog
Advantage Drawback
 The Syslog protocol is simple and easy  No acknowledgement

to implement. Strict coordination mechanism is defined for
between the transmitter and the receiver messages.
of the protocol is not required. It is  It only supports
allowed to start the transfer of Syslog
unidirectional transmission,
messages when the receiver has not
i.e. reporting messages.
been configured or even there is no
receiver. On the contrary, a receiver
may receive messages when it has not
been clearly configured or defined. This
simple principle greatly encourage the
acceptance and push the development
of Syslog.
 The speed of transmission based on
UDP is high.
46

 Interfaces and Protocols
 DB
 File
 MML
 Q3
 SNMP
 CORBA
 TL1
 Syslog
47
Content

System Architecture
48
Contents of This Topic

 Fault Management
 Configuration Management
 Performance Management
 Security Management
49
Fault Management - Overview

 The fault management functions include detecting
faults, locating faults quickly, isolating and recovering
faulty points, and sending maintenance information to
related users in time.
 Main Contents
 Fault Detection
 Fault Acknowledgement
 Fault Diagnosis
 Events
 Alarm
 Notification
50
Fault Management - Classification of Alarms

 Processing Alarm
 Quality of Service Alarm
 Environmental Alarm
 Equipment Alarm
 Communication Alarm
51
Fault Management - Severity Levels of Alarms

 Critical Alarm
 Major Alarm
 Minor Alarm
 Warning
Critical Major
Minor Warning
52
Fault Management - Four Statuses of Alarms

Current Alarm History Alarm
Clear Unacknowledged,
Unacknowledged,
Uncleared Cleared
Negative Negative
Acknowledgement
Acknowledgemen Acknowledgemen Acknowledgement
t t
Clear Acknowledged,
Acknowledged,
Uncleared Cleared
53
Fault Management - Alarm Management Functions (1)
 Alarm Collection Customized Alarm

 Alarm Processing Filtering
Client A Client B
 Alarm Filtering
 Alarm Synchronization
 Alarm Delay
 Correlation Analysis Global Alarm Filtering
 Redefinition of Severity Level
 Alarm Display
 Alarm Monitoring Interfaces EMS Server
 Rack Map
Alarm Filtering Before
 Topology Management
Putting Alarms into
 Alarm Box the Database
 Alarm Forwarding
NE
 Alarm Query and Count
Alarm Masking
54
 Correlation Analysis
 Alarm Suppression

When an alarm with high severity level occurs, only this major alarm is
reported while the lower-level alarms related to this alarm are not
reported.
 Alarm Timing

It is used for defining the action when an alarm exists for a long time,
for example, changing the alarm to a higher severity level or
generating a new alarm.
 Alarm Merging

The alarms of the same type merge into one alarm, which is reported
as a representative.
 Alarm Counting

A new user-defined alarm is generated when the count of the same
alarm occurring during a unit time reaches the specified value.
55
 Alarm Forwarding
Destinations
 NMS
 SMS
 Email
 Alarm Box

Software Alarm Box

Hardware Alarm Box
56
Configuration Management - Overview

 It supports the configuration of equipment and services for
commissioning a network and provisioning services.
 Plan which resources need to be deployed and how to design the
resources (network planning)
 Deploy the resources to meet the requirements of services
(resource supply)
 Allocate the resources to the users who need the services (service
provision)
 Contents of Configuration Management
 Network Topology Configuration
 Board Configuration in Racks
 Service Parameter Configuration of Equipment
57
Configuration Management - Processing

Functional Modules
Configuration
Management Server
Upper-Level
Access for Configuration (Command Line/GUI)
Management System Configuration Data
Processing in NE
MML/
CORBA Foreground System
Offline
CommandMML Configuration Server Configuration
Line NE DB
Subsystem Other
User Configuration
Management/ Subsystems
Internal Online of NE
Configuration
GUI Processing Support
F interface Platform
messages Subsystem
Internal Interface
Database
58
Configuration Management - Key Functions

 Offline Configuration
 The user sets the data of NEs in the EMS and saves the data in the EMS
database in advance. After that, the user synchronizes all the configuration
data in the EMS database to corresponding NE databases in one time and
then activate the data.
 Online Configuration
 Each configuration command issued by the user in the EMS is instantly
sent to corresponding NE.
 Software Loading
 Upload/download of configuration data, and software version management
 Status Management
 Used to show the status of the configured physical/logical resources, e.g.
active, standby, idle, usable, occupied, faulty etc.
 Data Management
 Import/export of NE data files
 Validity check of NE data, which ensures the consistency, integrity and
accuracy of NE data
59
Performance Management - Overview

 The performance management is the process of
monitoring the performance of a network, a network
element or equipment, collecting related performance
data, appraising the network and network element,
reporting the status of telecom equipment, and
supporting the network analysis and planning.
 Main Contents
 Performance Task Measurement and Management
 Performance Threshold Management
 KPI Monitoring
 QoS Monitoring
 Performance Data Analysis and Report
60
Performance Management - Basic Concepts

Each type of equipment involves one or more performance objects. A
Performance performance object has an independent significance, reflecting one
Object characteristic of the equipment. A performance object may include multiple
performance object attributes.
A performance object attribute is involved in a performance object, reflecting
Performance
one data feature of the performance object. It is dependent on the performance
Object Attribute
object.
In a performance object, a key performance object attribute or the calculation
KPI result of several attributes is specified as a Key Performance Index (KPI), which
is also called performance threshold index.
The maximum and minimum allowable values (i.e. upper limit and lower limit)
Performance
are set for each performance index, which are called performance upper and
Threshold
lower thresholds.
A collection point is the specified source in an NE from which the EMS obtains
Collection Point
needed data during the performance collection.
A collection item refers to the data of a performance object to be collected and
Collection Item
analyzed.
The granularity defines the data collection cycle of performance objects.
Granularity
Generally, the granularity is 15-minitue or 24-hour.
The performance collection is an interactive collection procedure like this: the
Performance
EMS issues a command to an NE for obtaining its performance data; then the
Collection
NE returns the performance data to the EMS.
61
Performance Management - Predefined Task

 Predefined Task
 The EMS loads the mandatory performance tasks to
collect required performance data after it starts up.
 These predefined performance tasks are not created by
users. The EMS automatically generate them in the
performance database according to the configuration
information.
 Difference between Performance Task and
Predefined Task
 Their customization and creation modes are different.
 It is not allowed to modify predefined tasks, which can
only be viewed or deleted.
62
Performance Management - QoS Alarms

 Threshold Crossing Alarm
 A threshold crossing alarm appears when the
performance data value is higher than the upper
threshold, and disappears when the value becomes
lower than the lower threshold.
 Severity Levels of Threshold Crossing Alarms
 The thresholds are classified into different levels. Each
threshold level corresponding to a alarm severity level.
 Report Threshold Crossing Alarm or Not
 Set the threshold status
 Set whether to report an alarm in a threshold crossing
case
63
Performance Management - Main Functions

Create, modify, delete, query, and suspend/activate performance tasks
Performance Parameters: performance object, performance object attribute table,
Task granularity, start time, end time, measurement period, task status (suspended,
Management activated, or stopped)
Performance thresholds are generated during the initialization of the system,

Performance which can be modified. It is not allowed to add or delete any performance
Threshold threshold. The generation of threshold crossing alarms depends on the
Management performance thresholds.
Performance Collect various performance data from the foreground NEs, i.e. perform the
Data operations required by corresponding performance tasks
Collection
Query related performance data in the performance database according to the

Performance query conditions, analyze the statistical result of the performance data, display
Data the performance data in the format of table or chart, and support the storage of
Analysis performance data in various format, e.g. in files
Performance Put the performance data into the database, back up the data, transfer the
Data data to another place, archive the data or delete the data
Management
64
Security Management - Overview

 It guarantees the proper operation of a network,
prevents the information in the network from being
stolen or damaged by external users. The security
management functions include the authentication of
both receivers and senders, access control and
encryption inside the network etc.
 Main Contents
 Network Security
 Host Security
 Data Security
 Security of the Network Management System
65
Main Issues Involved in Network Security

 Firewall
 Antivirus
 Intrusion Detection
 Data Encryption
 Data Backup and Recovery
 Disaster Recovery
66
Host Security Architecture

 Access Control
 Intrusion
Detection
 Encryption Other Host
Technique
Transmission
 Authentication
Encrypted
Authentication Server
Access Intrusion
Control Detection
Encrypted
Transmission
Host
Client
Resource
67
Typical Authentication Model of Network

Management System
0 ..* 0 ..*
Role Set
0 ..*
0 ..*
0 ..* 0 ..*
User Role
0 ..*
0 ..* 0 ..*
1 0 ..* 0 ..*
User Group Command Set Resource
 The security model is an abstract of user,

resource and authority management in the
network management system.
68
4A Requirements in the Security Management

of Network Management Systems
Centralized
Account Account
Centralized
Audit
Authentication 4A Audit
Centralized
Authentication
Authorization
Centralized
Authorization
69
Security Management - Security of the

Network Management System
 Access Authority
 User Management
 Operation Authority
 Administration Authority
 Security Log
 Operation Records
 Security Records
 User View
 The view varies from user to user. The system is open
in a limited way to prevent users from exceeding their
authorities.
70

 Task, Content, Two Events
 Alarm Classification and Severity Levels
 Alarm Filtering and Four Alarm Statuses
 Alarm Forwarding, Correlation, Alarming Rules (Suppression, Merging,
Timing, and Counting)
 GUI/MML
 Offline and Online Configuration
 Data Consistency, Software Load, Status Management
 Basic Concepts: Performance Task, KPI, Collection Item, Collection Cycle,
Collection Granularity
 Predefined Task and Performance Task, QoS Alarms
 Performance Management Task
 Network Security, Host Security Architecture, Typical Authentication
Model, 4A
71

02 Network Management Basics - PPT-72

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 Network Management Basics - PPT-72

Uploaded by

Copyright:

Available Formats

Network Management Basics

Overview of Network Management

Content of This Topic

 Theoretical Basis – Telecommunication

 Theoretical Basis - Organizations and Standards

Concept and Development

Limits of Early-Stage NM and Requirements

Evolution of the Telecom Industry

Open and Integrated

Theoretical Basis – TMN (1)

Theoretical Basis – TMN (2)

Logical Layers of TMN (1)

Network Management Layer

Element Management Layer

Logical Layers of TMN (2)

Five Management Functions of TMN (FCAPS)

Information Model of TMN

Managed Open System

Management operation Execution

Functions and Interface Model of TMN

Organizations and Standards (1)

Organizations and Standards (2)

Development Trends of TMN

Review of Key Points

Overview of Network Management

Contents of This Topic

 Access Modes and Client Types

 Interfaces and Protocols

Typical Architecture of Operation &

Networking Mode - Centralized Networking

NE1 NE2 … NEn NEa NEb … NEm

Networking Mode - Domain-Based

NE1 NE2 … NEn NEa NEb … NEm

Networking Mode - Distributed Networking

EMS APP EMS DB EMS

NE1 NE2 … NEn NEa NEb … NEm

Networking Mode - Distributed Networking

EMS EMS EMS EMS Client Group

NE1 NE2 … NEn NEa NEb … NEm

Networking Mode - Cascade Networking

Access Modes and Client Types

Access Modes of the Client:

Local Client Access Mode

Remote Client Access Mode (1)

Remote clients are deployed in different LANs from the server.

Remote Client Access Mode (2)

Local NE Local Client

TCP/IP Network TCP/IP Network

Remote NE Return Client Remote NE Return Client

Review of Key Points

Introduction to Main Interfaces

Analysis of NM Interface Technologies - DB

 Convenient interconnection,  DB is not applicable for alarm

Analysis of NM Interface Technologies - FILE

 Simple development, convenient  Difficulty of data recollection;

Analysis of NM Interface Technologies - MML

 Simple, easy accessible, and  No standard is made to

 OSI - Communications Protocol  Classified into transaction

Analysis of Q3 Interface - Advantages and

 The best feature of CMIP is that  As a large and

Introduction to Main Protocols - SNMP

Introduction to Main Protocols - SNMP

Introduction to Main Protocols - Advantages