Netman 4000 OMC-A

System Overview & Architecture

UT斯达康大学客户技术培训中心

UT斯达康内部资料 1
Netman 4000 Overview

UT斯达康大学客户技术培训中心

UT斯达康内部资料 2
 UT’s Network Management
Solution
UT’s
Third-party OSS/NMS/SMS System
mBOSS Open Northbound I/F

NMS
UT’s Netman UT’s iNMS

Third-party
EMS / OMC-S OMC-A OMC-I
EMS
SNMS

Network
NE Radius Svr CG, SAM
iMS
SLR
IN&CAMEL IPIPBackbone
Backbone
Parlay GW Paraly APP
CS-P NN eetwork
twork
iUMG NGN
NGNCN
CN++mBOSS
mBOSS iAN8000

NetmanLite/LCT
UT斯达康内部资料 3
NM4K Overview

The Netman 4000 system employs advanced object-oriented

design with platform-independent Java programming, and is
based on TCP/IP, and SNMP protocols.

It provides a unified network management solution for telecom

network infrastructures of various size and complexity as well
as for multiple applications.

It provides network management functions defined by the TMN

framework, including configuration, fault, security and log
management.

UT斯达康内部资料 4
 NM4K Overview - System Features

• Complex System Architecture

-- Modular system architecture and Advanced system modelling
-- FE-BE mode
-- Platform independence
-- Open standards
-- Intuitive user interface
-- Wizard based system installation

• High Dependability and Stability (HA Solution)

• High Security
– Netman 4000 system is equipped with flexible and powerful access
controls

• Web enabled GUI clients, can be operated from any web.

UT斯达康内部资料 5
 NM4K Overview - System Features

• Integrated Management

-- Netman 4000 OMC-A can effectively manage the entire UTStarcom broadband access
product line
-- Netman 4000 OMC-A provides subsystems that conform to TMN standards including
management for network TOPO, configuration, faults, security and logs.
-- The system can discover the network elements automatically.
-- The system provides an accurate, convenient, intuitive and data sensitive topology map.
-- The system provides simplify query and location services.
-- The system provides real-time alarms, alarm history and events.
-- The system security management applies User-Role-Managed domain/Privilege policies to
control access to Network resources and operations.
-- The Netman 4000 system provides a comprehensive array of tools.
-- User-friendly online help.

UT斯达康内部资料 6
NM4K Overview - NM4K
Components
Netman 4000 is a network management system solution, and has the
following functional components

– OMC-A: it is located in the EMS layer of the network

management system architecture, and can manage IPDSLAM,
MSAN, etc.

– LCT: it is a low cost GUI based local craft terminal to configure

equipment point-to-point and for field on-site trouble shooting.

– Alarm Panel: it is a wall-mountable audio/visual alarm device with a

large Liquid Crystal Display (LCD). The alarm functions are
customized to meet OAM requirements. The panel can be mounted in
equipment rooms and works with Netman 4000 to provide audible
and visual alarms for broadband networks

UT斯达康内部资料 7
NM4K Overview – Hardware & Software
Configuration

n Sun Server Machines / Windows

PCs
n Sun Solaris Operating System
n Client/Server Architecture
n Oracle/Sybase RDBMS
n AdventNet NMS platform
n iLog Map Management System
n Veritas HA/GR solution
n Web Based System – WebStart
Technology

UT斯达康内部资料 8
Netman 4000 OMC-A Current Status
Netman 4000 OMC-A Current Status
Scalabilities Performance
• Support up to 8000 nodes, 2 250 alarms per second
million subscribers Polling/TFTP based PM collection
• Support 100 concurrent client 100 XML NBI message per second
session with FE/BE
architecture

List Of Features Supported:

• Topology Management
• Log Management
• Fault Management
• Performance Management
• Security Management
• NBI Interface (XML based)
• Integrated Loop Test
Deployment • NE Software Upgrade
• Japan SBB • Alarm Forwarding Platforms
• India BSNL
• Device Configuration &
• India Reliance • Sun Solaris + ORACLE
Configuration Management
• PLDT • Windows + Sybase
• Cyprus CYTA • Subscriber Management • Windows + ORACLE
• Thailand UIH
• China Telecom
• And many more ……

UT斯达康内部资料 9
Netman 4000
Architecture

UT斯达康大学客户技术培训中心

UT斯达康内部资料 10
 Network Management Protocol –
SNMP
SNMP (simple network management protocol)

Set : Modify the management information，for example, configure the NE

Get：Get the management information，for example, retrieve the NE status

Response: Response from Agent for the commands send by NMS

UT斯达康内部资料 11
 Network Management Protocol – SNMP

Trap： Report the Network event etc. the NE trap message/event.

UT斯达康内部资料 12
Netman Architecture
Common Network
Common System Communications Infrastructure Database

Network Common
NMS Management
Components
Network Network Inventory
Network Topology
FM,PM,SM,LM Data Network State
Common Common
Access Fault/Performance
Security Management
Network GUI Infrastructure
Customer Info.
iPlatform
Common Network Communications Infrastructure

Device Device Device

Device Device Device
Manager Manager Manager
Device Manager Manager Manager
GEPON Rolling For 3rd
IPDSLAM MSAN mSwitch
Management Stream Party

Module

Additional
Transport /
GEPON Services
Routers and Access /
Telecom SoftSwitch Network Radio Network
IP switching DSL

Networks
and Devices

iPlatform: a framework to provide common FM/PM/SM/LM/TM

functionalities to all EMSs
EMS（OMC） = iPlatform + Related Device Managers
UT斯达康内部资料 13
Common Platform - iPlatform
• A in-house designed software platform provides common frameworks, basic FCAPS
and system functionality for all EMSs
• Common Framework For
– Client
– NBI
– Module Plug -In/Out
– Module Startup/Shutdown
– XML-based System Configuration
– Debugging & Diagnosis
• Common System Functionality
– Application Server (Apache&Tomcat)
– License Management
– Data Archiving, Backup/Restoration
– HA/GR and Load Balance
– Heart Beat and Notification Services
UT斯达康内部资料
• Common Protocol stacks and API
– SNMP, TFTP, etc.
– XML Lib, Logging Lib, etc.
– Job Scheduling API
• Unified Network Management
Functional Modules
– Unified Fault Management Module
– Unified Topology Management
Module
– Unified Security Management Module
– Unified Performance Management
Module
– Unified Log Management Module
– Unified Inventory Management
Module
– Unified NE Software download and
upgrade Module
14
Common Platform - Advantages

• Same look & feel for common GUIs

• Same flow and experience for Common Operation
• Enriched features shared by different EMSs
• Standardized system functionality for better stability and performance
• Re-usable common code-base to save development effort, and reduce the
time to market period.
• Better quality, usability, stability & scalability

UT斯达康内部资料 15
iPlatform Architecture - Overview
Presentation Clients
PresentationLayer
Layer

RMI/HTTP Common Client Framework RMI/CORBA/XML to iNMS/3rd Party NMS

Middle Server Layer

HTTP (Apache+Tomcat) NBI OR-Mapping API

JDBC Cache Mgmt

Database
uFM uTM uSM uLM uPM DB API
FM TM
NS
Schedule API
Inventory Common Data License
DB Backup/Restore Management Archive Mgmt SMPP API

Resource Mgmt. Logging Lib

Node Fail-over/Loading Heart-
Upgrade/Backup Balance beat XML Lib
NSM

SNMP API UNCP API TFTP API RPC API/Others

Protocol API Layer

NE Layer

UT斯达康内部资料 16
iPlatform Architecture - High
Availability
HA Deployment Scenarios: Co-Located or Geographic Redundancy

FE for Multiple
Clients Load
Sharing

FE/BE Heart
Beat

UT斯达康内部资料 17
iPlatform Architecture - Load
Balance
Clients
Clients

FE
FE Servers
Servers
Loading Balance
Service FE 1 FE 2 FE n
Services Services Services
Database
Module Naming
Service
BE Server
Trap Managers BE Core
Modules

PM
PM North Notification Should be deployed
PM Heart Unified
collector
collector Bound IF service together
collector Beating PM

Can be separately
deployed with other
Distributed Computing Proxy modules
NE
NE Layer
Layer
Layer, works for clients to provide
requested module services, it can be Support multi-instances
deployed in BE server machine. and separately
deployment

UT斯达康内部资料 18
 iPlatform Architecture – High
Performance Solution
• Load Balance and Distributed Architecture
ü BE&FE architecture
ü FE does most read-only operations from Database
ü Provide module Naming Service to make module distribution (on FEs) be
transparent for clients
ü Load-balance is supported through distributed deployment, esp. for heavy-
loaded modules, all of the following modules are registered as services.
• Distributed PM Data collectors
• Heart-beat module
• Notification-service
• FM (or Trap managers only)
• NBI
• PM Server (including: reporting service, data analysis)
• Combined Module Deployment for small networks; and Distributed Modules Deployment for
large networks.

UT斯达康内部资料 19
NM4K Topology Management
Architecture

Topo/Map Client

Topo is Data
Model;Map is
Data Changes View
Proxy APIs

Notification Server
Discovery O-R
Filters Mapping

TopoAPI,MapAPI Topo
Storage
NE Discovery
MO Info
Model and
Protocol API Discover and Relationship
Construct

Heart-beat Define

Network devices

UT斯达康内部资料 20
NM4K Security Management
Architecture

User
One role has only 0..1
managed domain,
one managed Assigns (1..N)
domain can be
attached to N role(s)
Role
Attaches (N..1) Contains (1..N)

MO set Managed Domain Privileges

SM Data
SM Functions
User Session
Authenticate
& Authorize

UT斯达康内部资料 21
NM4K Fault Management
Architecture

Network Trap
Element Sending Trap Parsing and
filtering
(NE)
Automatically Alarm Analysis,
clear alarm or Alarm Sync.
Event Alarm manually clear
History Real-time alarm
Event & Alarm Filter Alarm client, Real-time
alarm mornitoring

Event&Alarm&His
toryalarm

UT斯达康内部资料 22
NM4K Fault Data Processing Work
Flow

Understanding Fault Module through fault data processing flow

Alarm Monitor Client

Query/Notifications Ack/Clear/Sync/Archive

Alarm Notification Alarm API

Alarm Sync

Event/Alarm Storage

Storage Event Filter Alarm Filter&Aging&Shaping

Of
Event/Alarm/
History Alarm Trap Parser/Filter

Trap Receiver(s)

Network devices

UT斯达康内部资料 23
 NM4K Fault Management
Enhancement
It resolves the alarm consistency problem between NETMAN
and NEs
The following case will do the alarm
SYNC:
üRequest the alarm SYNC.
In TOPO, right-click and select the
NE sync action.
üNetman restart
üNode reset
üWhen Netman4K BE server found
some alarms lost due to the Network
reason.
üWhen NE change state from
unreachable to reachable
üEnter Maintance State->Exit
Maintance state UT斯达康内部资料 24
Netman 4000 OMC-A

• Questions?

UT斯达康内部资料 25
UT斯达康大学客户技术培训中心

UT斯达康内部资料 26
Thank You

This presentation is provided by UTStarcom for planning purposes only. Changes in market conditions and/or other changes in circumstances,
can affect the assumptions upon which this presentation was based or otherwise impact the contents of this presentation and therefore such
contents cannot be guaranteed and are subject to change at any time without notice. Nothing contained in this presentation shall be deemed to
create, modify or supplement any commitments or warranty made by the company, whether expressed, implied or statutory, in connection with
the products, technology and/or services referenced herein.

*Some features may require addition development and may not be ready for immediate implementation.

UT斯达康内部资料 27