NETWORK MANAGEMENT SYSTEM

INTRODUCTION :
UNITRANS ZXONM IS THE TRADEMARK OF THE SERIES ZTE TRANSMISSION MANAGEMENT PRODUCT. ZXONM E300 IS A NETWORK ELEMENT LAYER MANAGEMENT SYSTEM. IT IS BASED ON WINDOWS AND UNIX PLATFORMS, AND FULFILLS THE MANAGEMENT OF DWDM & SDH EQUIPMENT.

ZXONM E300 IMPLEMENTS THE FUNCTION OF SYSTEM MANAGEMENT, CONFIGURATIION MANAGEMENT, PERFORMANCE MANAGEMENT, ALARM MANAGEMENT, SECURITY MANAGEMENT AND MAINTENANCE MANAGEMENT.
ZXONM E300 EXTENSIBLE IS DESIGNED TO BE AND FLEXIBLE SYSTEM. AN

IT IS AVAILABLE TO MANAGE DIVERSIFIED EQUIPMENT, WHICH INCLUDES NOT ONLY THE EXISTING ZXWM-32-(V1.X), ZXWM-32(V2), ZXMP M800, BUT ALSO OXC, ASON THAT ARE BEING DEVELOPED NOW, WITH THE CAPABILITY OF FORWARD COMPATIBILITY AND BACKWARD COMPATIBILITY.

ZXONM E300 SOFTWARE SYSTEM ARCHITECTURE

THIS SYSTEM INCLUDES FOUR LAYERS:

EQUIPMENT LAYER

NETWORK ELEMENT LAYER

NETWORK ELEMENT MANAGEMENT LAYER NETWORK MANAGEMENT SYSTEM LAYER

Net work Management Layer

Net work Management System

GUI
F Element Management Layer f LCT

Q3/Corba F

Q3/Corba

GUI
F

MANAGER DB
Qx

MANAGER DB

ECC

AGENT

ECC

Qx
AGENT ECC AGENT ECC AGENT ECC AGENT ECC AGENT

Element Layer
S Equipment MCU Layer

AGENT

S MCU

S MCU

S MCU

Figure 1 Structure of ZXONM E300 Network Management System

MANAGER (OR SERVER)

MANAGER (OR SERVER) IS THE CORE OF NETWORK ELEMENT MANAGEMENT LAYER.

IT CAN MANAGE ONE OR MORE SUBNET.

IT CAN BE ACCESSED FROM SEVERAL GUI (CLIENT).

AGENT
AGENT IS THE CORE OF NETWORK ELEMENT LAYER. IT CAN BE MANAGED BY ONE OR MORE MANAGERS. BUT ONLY ONE OF THE MANAGERS HAS THE AUTHORITY OF WRITE. AGENT ROUTES AUTOMATICALLY AND TRANSMITS NETWORK MANAGEMENT INFORMATION THROUGH ECC CHANNEL.

ZXONM E300 HIERARCHY :

1. EQUIPMENT LAYER [MCU]:
MONITORS THE BOARD SITUATION SUCH AS ALARM AND PERFORMANCE. RECEIVES THE NMS COMAND AND CONTROLS THE BOARD TO IMPLEMENT SPECIFIC OPERATION.

2. NETWORK ELEMENT LAYER [NE]:

NE IS AN AGENT IN THE NETWORK MANAGEMENT SYSTEM. WHEN NE IS POWER ON, AGENT FULFILLS BOARD CONFIGURATION OPERATION.

MONITORS ALARMS PERFORMANCES STATUS IN WORKING CONDITION.

AND NORMAL

RECEIVES THE SUPERVISORY COMMAND FROM MANAGER [NETWORK ELEMENT MANAGEMENT LAYER] AND DEALS WITH THEM.

3.

NETWORK ELEMENT LAYER [MANAGER]:

MANAGEMENT

IT CONTROLS AND COORDINATES SERIES NE. IT INCLUDES MANAGER, GUI AND LCT. MANAGER IS THE CORE OF NE MANAGEMENT LAYER. IT CAN MANAGE SEVERAL SUBJECT, CONTROLS AND COORDINATE NE EQUIPMENT AND PROVIDE CORBA INTERFACE TO NETWORK MANAGEMENT LAYER. GUI OFFERS GRAPHIC USER INTERFACES. IT CONVERTS THE USERS MANAGEMENT REQUIREMENT INTO INTERNAL COMMAND AND SENDS IT TO MANAGER. LCT MAINTAINS LOCAL NETWORK ELEMENT IS OFTEN USED TO SET UP OR MAINTAIN LACAL NE.

ZXONM E300 SOFTWARE INTERFACE

THE POSITION OF INTERNAL INTERFACE OF ZXONM E300 SOFTWARE ARE1.Qx: THE INTERFACE BETWEEN AGENT AND MANAGER, COMPLIES WITH TCP/IP. 2.F: THE INTERFACE BETWEEN GUI AND MANAGER, COMPLIES WITH TCP/IP. 3.f: THE INTERFACE BETWEEN AGENT AND LCT, COMPLIES WITH TCP/IP. 4.S: THE INTERFACE BETWEEN AGENT AND MCU, POINT TO MULTI COMMUNICATION BASED ON HDLC. 5.ECC: THE INTERFACE BETWEEN AGENT AND AGENT COMMUNICATES VIA ECC. 6.Q3/CORBA: THE INTERFACE BETWEEN MANAGER AND ABOVE LAYERS.

NMS COMPONENTS
ZXONM E300 NETWORK MANAGEMENT SOFTWARE COMPRISES FOUR MODULES :

MANAGER
GUI

DATABASE
AGENT

GUI

Manager

DB

Agent

Figure 2 Structure of NE Management Layer

1. MANAGER
IT IS NAMED SERVER. MANAGER CAN BE REGARDED AS A SERVER TO GUI. WHICH TRANSMITS MANAGEMENT COMMAND TO CORRESPONDING AGENT AND RECEIVES THE NOTIFICATIONS FORM AGENT. MANAGER SRORES ALL THE MANAGEMENT DATA OF THE NETWORK. FOR EXAMPLE: PRIMARY DATA SUCH AS SYSTEM MANAGEMENT, CONFGURATION MANAGEMENT, ALARM MANAGEMENT, MAINTENANCE MANAGEMENT ETC. ONLY THE MANAGEMENT DATA OF THE DOMAIN NETWORK OF ITSELF CAN BE STORED IN A MANAGER.

2. GUI
IT IS NAMED CLIENT. GUI STORES FEW DATA OF NMS. THESE DATA CAN BE OBTAINED FROM DATABASE VIA MANAGER BY GUI, IF NECESSARY.

3. DATABASE
DATABASE IMPLEMENT THE INFORMATION QUERY FOR GUI AND MANAGER.

IT STORES THE INFORMATION OF CONFIGURATION, ALARM AND PERFORMANCE, AS WELL AS ENSURE THE DATA CONSISTENCY.

4. AGENT

IT LOCATES THE NE.

IT MANAGES THE MANAGEMENT OBJECTS DIRECTLY. RESPONDS THE COMMAND FROM MANAGER AND INFORMS THE CORRESPONDING MANAGER OF THE NOTIFICATION OF OBJECT.

GUI, MANAGER AND DATABASE CAN BE INSTALLED IN THE SAME COMPUTER OR DISPERATE COMPUTER.
THEY CAN RUN ON THE PLATEFORM OF HP WORK STATION, SUN WORK STATION OR PC.
IT REQUIRES COMPUTERS OF DIFFERENT CONFIGURATION DEPENDING ON DIFFERENT INSTALLED SOFTWARE PACKAGE. AGENT IS IMPLEMENTED IN NCP. EQUIPMENT LAYER IS IMPLEMENTED ON MCU IN BOARDS.

SOFTWARE CHARACTERISTICS
WELL DESIGNED HIERARCHY. POWERFUL MANAGEMENT FUNCTIONS. POWERFUL MANAGEMENT CAPABILITY.

POWERFUL SECURITY MECHANISM.

SOLUTION OF CROSS-PLATFORM.

FRIENDLY USER INTERFACE.

DOWNLOAD SOFTWARE ONLINE REMOTELY.

LOCAL CRAFT TERMINAL

LCT OVERVIEW :
ZXONM LCT IS A PART OF NMS. IT HAS FULL MANAGEMENT FUNCTIONS TOWARDS ONE NE. IT CAN ACCESS NE DIRECTLY FROM ENTHERNET NETWORK PORT AND WORK TOGETHER WITH ZXONM E300. ZXONM LCT DO NOT AFFECT THE NETWORK TRANSPORT SERVICE WHEN LOG IN/LOT OUT NE. IT IS USED TO INITIALIZE THE CONFIGURATION OF LOCAL NE BEFORE THE NETWORK CONSTRUCT. IT IS USED TO SOLVE THE SERIOUS PROBLEMS WHICH ZXONM E300 CAN NOT ACCESS WHEN THE NETWORK HAS FAILURE.

DIFFERENCES BETWEEN LCT AND ZXONM E300

LCT ZXONM E300

1. TARGET
IT IS USED TO SET UP OR MAINTAIN LOCAL NE. IT IS USED TO MONITOR AND CONTROL ENTIRE NETWORK.

2. MANAGEMENT ABILITY
IT CAN ONLY MANAGE SINGLE NE.

IT CAN MANAGE ENTIRE NETWORK.

IT CAN ACCEPT MANY CLIENT.

3. MANAGEMENT FUNCTION
LCT PROVIDES FULL MANAGEMENT FUNCTIONS OF LOCAL NE. IT LACK THE NETWORK MANAGEMENT FUNCTIONS. LCT NORMALLY RUN ON PORTABLE PC. IT HAS ALL OF THE NETWORK MANAGEMENT FUNCTIONS.

4. HARDWARE AND SOFTWARE SETTING

IT RUN ON UNIX SERVIR.
OPERATION SYSTEM PLATEFORM OF ZXONM E300 IS HP-UX OR WINDOWS 2000 SERVER.

LCT OPERATION SYSTEM PLATEFORM IS WINDOWS 2000 PROFESSIONAL.

5. EFFICIENCY AND RELIABILITY

DEEPLY RELATIVE TO THE HARDWARE CONFIGURATION. IT IS MORE EFFICIENT AND MORE RELIABLE.

BASIC USAGE OF LCT

ZXONM LCT HAS THE SIMILAR LOOK AND OPERATION AS ZXONM E300. LCT COOPERATES WITH EMS TO EXECUTE NETWORK INITIALIZATION

FOLLOWING STEPS:

DATA PREPARATION
CREATE THE NETWORKS NEs IN EMS. CREATE SEVERAL MANAGER ID FOR LCT IN EMS. BACKUP THE NES DATABASE IN EMS.

RESTORE APPROPRIATE NEs IN LCT FROM EMSs NE BACKUP FILES.

NE CONFIGURATION

CARRY THE LCT TO LOCAL NE STATION. DOWNLOAD THE NEs DATABASE SETTING THE NEs PARAMETER AND MAKE NE WORK PROPERLY. CONNECT NEs EACH OTHER THROUGH ECC.

DATA SYNCHRONIZATION

IF LCTs CONFIGURATION HAS BEEN MODIFIED, IT NEED SYNCHRONIZE DATA TO EMS.

THERE ARE THREE METHODS :

1. i) UPLOAD NEs DATABASE. ii) COMPARE THE DIFFERENCE DATA
BETWEEN NE AND EMS.

iii) THEN MODIFY THE EMS CONFIGURATION. 2. BACKUP NEs DATA AND RESTORE IN EMS. 3. MODIFY EMS CONFIGURATION ACCORDING TO
LCTS ALTERATION.

NETWORK RUN
IN THIS STAGE, NETWORK RUN NORMALY.
EMS MANAGE THE WHOLE NETWORK. LCT EXIT FROM THE NEs MANAGEMENT.

CONFIGURATION MANAGEMENT

CONFIGURATION MANAGEMENT IS THE MOST IMPORTANT MODULE OF NETWORK MANAGEMENT SYSTEM. IT IS THE BASE TO OPERATE SYSTEM VIZ PERFORMANCE MNGT., ALARM MNGT, MAINTENANCE MNGT., SERVICE MNGT AND SECURITY MNGT.

IT INCLUDES INSTALLATION CONFIGURATION, SERVICE AND PROTECTION CONFIGURATION.

CREATING DIFFERENT EQUIPMENTs NETWORK ELEMENT, MODIFYING NEs PROPERLY, MANAGING THE CONNECTION RELATIONSHIP BETWEEN ALL NEs. NEs BOARD CONFIGURATION ARE IN INSTALLATION CONFIGURATION.
SERVICE CONFIGUNATION INCLUDES CONFIGURING OW BETWEEN ALL NEs AND CONFIGURE USER CHANNEL [DCC].

CONFIGURING PROTECTION PROTECTION RELATIONSHIP PROTECTION CONFIGURATION.

GROUP, ARE IN

CONFIGURE DCC CONNECTION

THE CONSUMER CAN CONFIGURE DCC CONNECTION. THE WINDOWS THAT CONFIGURE DCC CONNECTION BELOW.
DCC Configure

Src NE

DLH(GZB-Tx) SCC4 Add

Dest NE

DLH(GZB-Rx) SCC3

Transmitter Port

Receiver Port Remove DestNE

SrcNE

Transmitter Port

Receiver Port

Apply

Close

FUNCTION DESCRIPTION :
1. SreNE : USED TO CHOOSE SOURCE NE. 2. TRANSMITTER PORT: USED TO SELECT TRANSMITTER PORT. 3. Dest NE: USED TO CHOOSE DESTINATION NE. 4. RECEIVER PORT: USED TO SELECT RECEIVER PORT. 5. ADD: CLICK THE ADD BUTTON, SO AS TO ONLY ADD THE CURRENTLY DISPLAYED DCC PORT CONFIGURATION, AND NO DOWNWARD SETTING WILL BE MADE. 6. REMOVE: CLICK THE REMOVE BUTTON, SO AS TO DELETE THE CURRENTLY DISPLAYED DCC PORT CONFIGURATION, AND NO DOWNWARD SETTING WIL BE MADE SUPPORT MULTIPLE CHOICES.

7. APPLY: DOWNWARD SETTING. 8. CLOSE: EXIT DIALOG BOX. 9. HELP: HELP DOCUMENT ABOVE THIS INTERFACE.

OPERATION GUIDE:
9. OPEN THE CONFIGURATION DIALOG BOX OF DCC CONNECTION, CONFIGURING DCC CONNECTION, ADD OR DELETE SOME CONTENT THEN CLICK APPLY.

HUB CONNECTIVITY : IP
A B
SCC4 SCC4 SCC4 SCC4 SCC4 SCC4 SCC4 SCC4

- TML
- OLA

TML - TML TML - OLA OLA - OLA OLA - TML

A
SCC4 SCC4 SCC4 SCC3 SCC3 SCC3 SCC3 SCC4

TML - TML TML - OLA OLA - OLA OLA - TML

CREATING DCC
IP IP

DLH(GZB-Tx)
SCC4

IP SCC4

DLH(GZB-Rx)
IP

A-dir
SCC4

B-dir
SCC3

NOIDA
SCC4 SCC3 SCC4 IP

A-dir
SCC4

B-dir
IP IP

GZB(DLH-Tx)

IP

GZB(DLH-Rx)

SOURCE NE
DLH(GZB-Tx) DLH(GZB-Rx) DLH(GZB-Tx) NOIDA

Tx Port
IP IP SCC4 SCC4 SCC4 SCC3 IP IP

DESTINATION
DLH(GZB-Rx) DLH(GZB-Tx) NOIDA GZB(DLH-Tx)

Rx Port
IP IP SCC4 SCC4

GZB(DLH-Tx)
NOIDA GZB(DLH-Tx) GZB(DLH-Rx)

NOIDA
DLH(GZB-Tx) GZB(DLH-Rx) GZB(DLH-Tx)

SCC3
SCC4 IP IP

DLH(GZB-Tx)

OPA OUT

IP
IP
ODU

OBA OUT OPA IN (10 db)

DLH(GZB-Rx)

A-dir
OLA-TERMINAL
OLA-1
IN

B-dir
OUT

NOIDA
OUT

OLA-2
IN (10 db)

A-dir

B-dir
OBA OUT

IN

GZB(DLH-Tx)
OPA

IP IP

GZB(DLH-Rx)
ODU

OUT

73

60

60

38

PATNA

JAHANABAD

GAYA

NAWADHA

RAJAULI

40

65

53

44

JHAUMRI TALAIYYA

HAZARIBAG

RAM GARH

RANCHI

CONFIGURE DCC CONNECTION BETWEEN PATNA AND RANCHI

IP IP

PAT (RA-TX)
SCC4 SCC4 IP IP

PAT (RA-RX)
SCC4 SCC3

JAHANABAD
SCC4 SCC4 SCC3 SCC3

GAYA
SCC4 SCC4 SCC3 SCC3

NAWADH
SCC4 SCC3

SCC4

SCC3

RAJAULI
SCC4 SCC4 JHUMRI TALAIYYA SCC4 SCC4 SCC3 SCC3 SCC3 SCC3

HAZARIBAG
SCC4 SCC4 SCC3 SCC3

RAM GARH
SCC4 SCC4 IP IP IP IP SCC3 SCC4

RA (PAT-RX)

RA (PAT-TX)

SOURCE NE
PAT (RA-TX) PAT (RA-RX) PAT (RA-TX) JAHANABAD GAYA NAWADH RAJAULI JHUMRI TALAIYYA

Tx Port
IP
IP SCC4 SCC4 SCC4 SCC4 SCC4 SCC4 SCC4 SCC4

DESTINATION Rx Port
PAT (RA-RX) PAT (RA-TX) JAHANABAD GAYA NAWADH RAJAULI JHUMRI TALAIYYA HAZARIBAG RAM GARH
RANCHI

IP IP
SCC4 SCC4 SCC4

SCC4
SCC4 SCC4

HAZARIBAG
RAM GARH

SCC4
SCC4

RA (PAT-TX) RA (PAT-RX) RA (PAT-TX)

IP
IP SCC4

RA (PAT-RX) RA (PATA-TX) RAMGARH

IP IP
SCC3

RAMGARH
HAZARIBAG JHUMRI TALAIYYA

SCC3
SCC3 SCC3 SCC3 SCC3 SCC3 SCC3

HAZARIBAG
JHUMRI TALAIYYA RAJAULI

SCC3
SCC3 SCC3 SCC3 SCC3 SCC3 SCC4

RAJAULI
NAWADH GAYA JAHANABAD

NAWADH
GAYA JAHANABAD PAT (RA-TX)