Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Product Description
Version: 12.10.040
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Revision History
Revision No.
Revision Date
Revision Reason
R1.1
2011-1216
R1.0
2011-0916
First Edition
Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Functions........................................................................................................... 1-2
1.3 Standards Followed............................................................................................ 1-2
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
Configuration management
Fault management
Performance management
Topology management
Security management
Purpose
This manual describes the functions, features, working principles, and networking of the
NetNumen U31 Unified Element Management System.
Intended Audience
l
l
Maintenance engineers
Debugging engineers
Summary
Chapter 4, Configuration
Requirements
of NetNumen U31.
Section
Summary
Protocols
Chapter 8, Networking
Modes
Chapter 9, Environment
Requirements
U31 system.
II
Chapter 1
System Overview
Table of Contents
Overview ....................................................................................................................1-1
Functions ...................................................................................................................1-2
Standards Followed....................................................................................................1-2
1.1 Overview
According to the network management definition specified in Telecommunications
Management Network (TMN), NetNumen U31 is located in the network element
management layer, as shown in Figure 1-1.
Figure 1-1 Network Management Model
The NetNumen U31 network element management system is located between the network
element layer and the network management layer. It belongs to the network element
management layer.
The NetNumen U31 system manages and controls various connected radio network
systems, implementing centralized management of the radio network systems, including:
l
l
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
l
Centralized
Centralized
Centralized
Centralized
fault management
performance management
command line tool
maintenance tool
The NetNumen U31 system provides interfaces for the network management layer,
reporting information of the managed elements, including the alarm data, performance
data, and configuration data.
The NetNumen U31 system improves centralized management of the telecommunication
enterprises.
1.2 Functions
The NetNumen U31 system is a centralized management system of the mobile radio
products of ZTE Corporation. Through NetNumen U31, users can manage all the radio
devices over the entire network in a centralized manner. It also provides the standard
northbound interfaces to the upper-layer Network Management System (NMS).
The NetNumen U31 system manages the lower-level network element systems in a
centralized manner, and provides unified interfaces to the upper-layer applications.
The managed elements report the topology data, alarm data, and performance data
through their interfaces. The NetNumen U31 system implements centralized information
displaying and management through centralized modeling and conversion.
The NetNumen U31 system provides the following network management functions:
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
Configuration management
Topology management
Fault management
Performance management
Security management
System management
Task management
Command line tool
Graphical User Interface (GUI)
Maintenance tool
Role-based and domain-based management
Backup and restoration
Three-layered networking
Northbound interface
Network Time Protocol (NTP) function
1-2
SJ-20110823134613-002|2011-12-16(R1.1)
ITU-T
l
l
l
l
l
l
l
l
l
l
l
l
l
l
RFC
l
l
l
l
l
l
l
l
l
l
l
l
l
TMF
l
l
l
l
1-3
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
l
l
l
l
OMG
l
1-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 2
System Features
Table of Contents
Conformity to Standards.............................................................................................2-1
Integrated Network Management................................................................................2-1
System Expansion......................................................................................................2-1
System Openness ......................................................................................................2-1
System Reliability .......................................................................................................2-2
System Operation Security .........................................................................................2-2
Ease of Use ...............................................................................................................2-2
ZTE UMTS
GSM
TD-SCDMA
CDMA
LTE (including LTE-FDD and LTE-TDD)
WiMAX
Microwave
2-1
SJ-20110823134613-002|2011-12-16(R1.1)
The NetNumen U31 server has redundant network ports, dual power supplies, and
hard disks that can be mirrored, which improves hardware reliability.
Local High Availability (HA) and remote disaster recovery capability ensure that the
services can be switched to the standby server when the active server is down.
NetNumen U31 provides a complete system management capability, which helps
monitor the system running condition.
Disk mirroring and data backup ensure the data saving security.
Disk mirroring: In one host, all data modifications on the active disk are
synchronously backed up to the standby disk.
Data backup: Through the network management system, users can back up or
dump the specified data to the specified peripheral storage devices, such as disks
and magnetic tapes. Users can restore the system with the data in the peripheral
storage devices as required. It provides various choices for data saving and
backup.
Chapter 3
System Structure
Table of Contents
Hardware Structure ....................................................................................................3-1
Software Structure......................................................................................................3-3
Local HA System
The two servers are located in the same LAN and share the disk array.
3-1
SJ-20110823134613-002|2011-12-16(R1.1)
The two servers are managed through the HA software. One server is in the service
running status, saving the real-time data to the disk array. The other server is in the standby
status, not providing services to external devices. The two servers are connected by the
heartbeat cable. When the active server is down, the applications are switched to the
standby server, as shown in Figure 3-2
Figure 3-2 Hardware Structure of Local HA System
3-2
SJ-20110823134613-002|2011-12-16(R1.1)
server software
client software
NetNumen U31 uses the client/server architecture, and TCP/IP is used in communication
between different parts.
The NetNumen U31 software system consists of the following software modules:
l
l
l
l
l
l
l
l
l
l
l
l
3-3
SJ-20110823134613-002|2011-12-16(R1.1)
3-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 4
Configuration Requirements
Table of Contents
Server Configuration Requirements............................................................................4-1
Client Configuration Requirements .............................................................................4-3
Model1
Model2
Server
SUN M4000
SUN M4000
Memory: 32G
Memory: 64G
ST6180(8*300G FC 15K)
ST6180(16*300G FC 15K)
or
or
EMC CX4-120C(8*300G FC
EMC CX4-120C(15*300G FC
15K)
15K)
SUN T5220
SUN T5220
Memory: 16G
Memory: 16G
HD: 2*146G
HD: 2*146G
SL 24 (12*400G)
SL 24 (12*400G)
DiskArray
Backup server
TAPE
4-1
SJ-20110823134613-002|2011-12-16(R1.1)
Model1
Model2
Server
IBM P740
IBM P740
Memory: 32G
Memory: 64G
DiskArray
Backup server
IBM P520
IBM P520
TAPE
Memory: 16G
Memory: 16G
HD: 2*146G
HD: 2*146G
TS3310 (12*400G)
TS3310 (12*400G)
Operating system
Solaris 10 U9 sparc
Database
HA software
Operating system
AIX 6103
Database
HA software
PowerHA+SnapMirror 6105
4-2
SJ-20110823134613-002|2011-12-16(R1.1)
Configuration
CPU
Memory
2 GB
500 GB
Disk array
None
Configuration
Operating system
Windows XP
Windows 7
Browser
Document viewer
Antivirus software
4-3
SJ-20110823134613-002|2011-12-16(R1.1)
4-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 5
System Principles
Table of Contents
Working Principle .......................................................................................................5-1
Remote Client Principle ..............................................................................................5-2
NMS Hierarchy Model ................................................................................................5-2
The relation between NetNumen U31 and the upper-layer NMS and the lower-layer OMMs
are described as follows:
l
l
NetNumen U31 provides the basic data of the devices and the device management
services for the upper-layer OSS or integrated NMS.
Operation analysis
NetNumen U31 provides the original statistic analysis data for the operation analysis
system.
Resource management
NetNumen U31 provides centralized device configuration information for the resource
management system.
SJ-20110823134613-002|2011-12-16(R1.1)
Through the interface between NetNumen U31 and the managed NEs, the OMMs of the
managed NEs report topology, fault, performance and report data to NetNumen U31.
Through centralized modeling and conversion, NetNumen U31 presents and manages
the data in a centralized manner.
The NetNumen U31 server collects the NE data through each NE and process the
data.
The NetNumen U31 client displays the data that is collected and handled by the
NetNumen U31 server through GUI.
Through the TCP/IP protocol, the remote NetNumen U31 client selectively presents
collected network management information to different areas.
To ensure the network security, user rights can be customized for different areas
through the security management functions of NetNumen U31.
5-2
SJ-20110823134613-002|2011-12-16(R1.1)
NMS layer:
It manages all NEs within the controlled area, and coordinates the actions of all NEs.
EMS layer:
It implements operations on or manages one or multiple NEs, providing the
coordination function for the communication between NMS and NEs. The NetNumen
U31 system is located in this layer.
NE layer:
It includes the local OMM and NEs. The NetNumen U31 system connects an NE
through a local OMM. The local OMM shields the difference between various NEs,
collects the NE data and reports it to NetNumen U31, and converts the requests issued
by NetNumen U31 to instructions that can be processed by NEs.
Here, the northbound interface is the interface between NetNumen U31 and NMS, and the
southbound interface is the interface between NetNumen U31 and a managed NE.
5-3
SJ-20110823134613-002|2011-12-16(R1.1)
5-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 6
Product Functions
Table of Contents
Topology Management ...............................................................................................6-1
Fault Alarm Management ...........................................................................................6-3
Performance Management .........................................................................................6-7
Security Management ................................................................................................6-8
Log Management .......................................................................................................6-9
System Backup ........................................................................................................6-10
System Monitoring....................................................................................................6-10
Task Management ....................................................................................................6-11
Command Line Terminal...........................................................................................6-12
Radio Configuration Application ...............................................................................6-12
Northbound Interface................................................................................................6-13
Viewing and editing the location, network structure, link connection, and service
distribution of the network resources in each service system.
Displaying the topology relationship between service subnets, and supporting access
management.
6-1
SJ-20110823134613-002|2011-12-16(R1.1)
The following describes the functions of topology display, topology operations and topology
monitoring.
Topology Display
This function requires that the network resources are presented through a combination of
the resource tree and network topology view. According to different resource management
requirements, it provides different management views.
Topology Operations
NetNumen U31 supports the following topology operations:
l
l
l
l
l
l
l
l
l
l
Topology Monitoring
The network topology view can dynamically display the running status of the managed
network in real time, implementing configuration monitoring, alarm monitoring, and
performance monitoring.
l
Configuration Monitoring
Through periodic synchronization, the topology view can dynamically show the
change of the network device configuration, including addition/deletion of NEs and
NE configuration change. In this way, users can obtain relevant prompts from the
topology view.
Users can set the information update period.
Alarm monitoring
The topology view can display the alarms generated in each lower-layer network
management system in the entire network, and remind users of the alarms in a
visible and audible manner.
The object icons corresponding to the faulty NEs are colored differently according to
the alarm levels. Acknowledged, unacknowledged, handled and cleared alarms are
also displayed differently.
On the lower part of the topology view on the client, all alarms of the current NE are
displayed in a list.
Performance Monitoring
6-2
SJ-20110823134613-002|2011-12-16(R1.1)
In the topology view, users can monitor the performance tables or performance prompt
messages of specified NEs.
In the topology view, after setting the counters and NEs to be monitored, users can
click a NE in the topology tree to view the counter values of it. The performance prompt
message monitoring enables users to learn the latest information of the customized
key performance indices.
On the lower part of the topology view on the client, the performance data related to
the current NE is displayed in a list.
Server
The server processes the alarms normalized by the NetNumen U31 system, and
stores the processed alarms in the alarm database. At the same time, it sends the
processed alarm data to the client for display.
Client
The client filters the alarms received from the server, and performs the user security
check. Then, it displays the alarms required by the user on the alarm list and topology
view.
6-3
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
NetNumen U31 can control the alarm and notification reporting condition and
implement alarm masking.
NetNumen U31 ensures correctness of the data obtained from the lower-layer OMMs.
After the synchronization starts, the system will prompt the initiation and result of the
synchronization in the down-left message bar.
Customizing the display of alarm information to show the needed information of the
alarms
Setting filter conditions to display qualified alarms only
Querying historical alarms by customized conditions
Customizing the colors and sounds of alarms based on alarm severity level.
SJ-20110823134613-002|2011-12-16(R1.1)
The query and statistics result can be displayed in many forms, such as report and
chart. The result can be saved and printed. Users can set the output condition, output
destination and output mode (such as printer or file).
Alarm statistics includes basic historical alarm statistics and busy-hour historical alarm
statistics.
l
Alarm Forwarding
NetNumen U31 can automatically forward alarm information to network management
users or maintenance personnel for timely processing. Users can customize the alarm
forwarding condition, forwarding recipients and forwarding mode.
NetNumen U31 uses the following alarm forwarding methods:
l
l
l
E-mail
Mobile phone short messages
Alarm box
Alarm Redefinition
This function is to redefine severity level of an alarm according to the alarm code, alarm
source, and NE type.
Alarm Filtering
User can filter out certain unimportant alarms according to a combination of alarm type,
alarm code and alarm cause. Alarm filtering effectively reduces the number of alarms.
Alarm filtering can be performed respectively on the server and the client:
l
Alarm filtering for all users: In this case, alarm filtering is performed during alarm
preprocessing, and the selected alarms will not be sent to the client.
Alarm filtering for a filter creator: In this case, the selected alarms will not be sent
to the client to which the filter creator logs in.
6-6
SJ-20110823134613-002|2011-12-16(R1.1)
Template Management
Two template types are defined: common template and query template.
6-7
SJ-20110823134613-002|2011-12-16(R1.1)
Common template: a common template defines the NE type, measured object type,
and performance object. The NE position and the measured object position often
change in actual queries, so they are not defined in the common template. Users can
specify such positions in an actual query.
Query template: a query template is often used in a performance data query. Users
can save the query conditions in it. By using an appropriate query template, users can
quickly query performance data at any time without setting the same query conditions
repeatedly.
The query template parameters include the queried index, queried object, and queried
time.
6-8
SJ-20110823134613-002|2011-12-16(R1.1)
Role Management
The role management involves two aspects: role set management and role management.
l
Role Management
A role defines the user rights, including operation rights and resource rights.
Users can create, modify, duplicate and delete a role within the scope of authority
assigned by the system.
User Management
User management is the most important part of security management of the NetNumen
U31 system.
Through user management, the system administrator can perform the following operations:
l
l
l
l
l
l
l
Creating a user
Querying a user
Modifying a user
Assigning operation rights to a user
Setting the working period for a user
Deleting a user
Prohibiting a user
A newly created user can log in to the NetNumen U31 system with its user name and
password, and performs network management operations within the scope of rights
assigned to it.
A department is used to manage the executive affiliation of users. In practical applications,
for the convenience of user management, departments can be established corresponding
to the real network management departments.
SJ-20110823134613-002|2011-12-16(R1.1)
Exporting logs
Users can export the logs in the form of a file to a remote log server, either manually
or by customizing a exporting task.
Backup Tasks
File backup
Restoration Tasks
SJ-20110823134613-002|2011-12-16(R1.1)
monitoring period, compares them with the preset thresholds, and decides
whether to report alarms in the monitoring view.
Database Monitoring
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
l
l
l
l
l
l
l
l
l
6-13
SJ-20110823134613-002|2011-12-16(R1.1)
6-14
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 7
7-1
SJ-20110823134613-002|2011-12-16(R1.1)
Object service
The object service provides a set of basic objects with the aim of implementing and
using objects. The object service is independent of the application area.
Public facilities
7-2
SJ-20110823134613-002|2011-12-16(R1.1)
The public facilities provides the user with a group of interfaces for shared services,
such as system management, compound document and E-mail.
l
Application interface
The application interface is the interface that expand the application, which is similar
to the application presentation layer.
Domain interface
The domain interface is the interface that is provided for the application domain
service.
CORBA
CORBA
CORBA
CORBA
northbound
northbound
northbound
northbound
interface
configuration interface
performance interface
inventory interface
Reporting alarms
Synchronizing alarms
Acknowledging alarms
Unacknowledging alarms
Acquiring the number of alarms
Adding the description of alarms
Clearing alarms
Notifying the change of alarm acknowledgement status
Reporting the addition of alarm description
Reporting the reestablishment of alarm information list
SJ-20110823134613-002|2011-12-16(R1.1)
In NetNumen U31, configuration data, performance data, and inventory data are
transferred to the NMS in the format of XML file or CSV file via the FTP northbound
interface.
NetNumen U31 also supports the SSH-based SFTP protocol, which ensures safer
northbound file transmission services.
Management Node
The management node runs the SNMP agent program. It maintains a local database,
describes the status and history of the node, and influences the running of the node.
Management Station
The management station runs a special network management program (manager) to
implement communication with the SNMP agent on the managed node, and maintains
the management information base.
Management Protocol
The management protocol is used by the management station to query and modify
the status of the managed node. The management node can use the management
protocol to send Trap messages to the management station.
Get_Request
Get_Next_Request
SNMP Manager uses a Get_Request message to search for information in a network
device with SNMP Agent. Get_Request and Get_Next_Request messages can be
used together to get an object in a table, where Get_Request is used for getting a
7-5
SJ-20110823134613-002|2011-12-16(R1.1)
specific object in the table and Get_Next_Request is used for getting the next object
in the same table.
l
Get_Response
SNMP Agent responds to the Get_Request message with a Get_Response message.
It exchanges much information with SNMP Manager, such as system name, how
long the system runs properly after starting automatically, and the number of network
interfaces in the system.
Set_Request
SNMP Agent can use the Set_Request message to remotely configure the parameters
of a device.
Trap
Trap is a non-request message sent by SNMP Agent to the management station. It is
used to notify the server of a certain event.
The functions of SNMP Manager are used when the lower-level network element systems
are managed by the SNMP protocol. In this case, all NEs are managed by NetNumen U31
as SNMP agents.
7-6
SJ-20110823134613-002|2011-12-16(R1.1)
The functions of SNMP Agent are used when the upper-layer NMS manages NetNumen
U31 by the SNMP protocol. In this case, the upper-layer NMS manages NetNumen U31
as an SNMP manager.
SNMP Manager functions and SNMP Agent functions have no coupling relation.
NetNumen U31 provides SNMP Manager and SNMP Agent functions according to the
actual requirements.
7-7
SJ-20110823134613-002|2011-12-16(R1.1)
7-8
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 8
Networking Modes
Table of Contents
Local Networking Mode ..............................................................................................8-1
Remote Networking Mode ..........................................................................................8-2
Remote Client Networking Mode ................................................................................8-3
8-1
SJ-20110823134613-002|2011-12-16(R1.1)
2. Device requirement
Few network devices are needed for the local networking mode. According to the
quantity of hosts (namely, the number of servers and clients), select proper 10/100
Mbps adaptive HUBs with enough ports and prepare necessary twisted pairs (namely,
Ethernet cables) to construct the network.
8-2
SJ-20110823134613-002|2011-12-16(R1.1)
According to transmission mode, the remote networking mode supports transmission over
the Digital Data Network (DDN) dedicated line, E1 line, or High-data-rate Digital Subscriber
Line (HDSL).
Figure 8-2 shows an example of remote networking. The NMS server and NEs are located
in the same LAN. The remote client connects the local NMS server through DCN and
performs maintenance management operations.
Figure 8-2 Remote Networking Example
8-3
SJ-20110823134613-002|2011-12-16(R1.1)
8-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 9
Environment Requirements
Table of Contents
Grounding Requirements ...........................................................................................9-1
Temperature and Humidity Requirements...................................................................9-2
Cleanness Requirements ...........................................................................................9-3
Air Conditioning and Ventilation Requirements ...........................................................9-3
Anti-EMI Requirements ..............................................................................................9-3
Lightning Protection Requirements.............................................................................9-4
Anti-Static Requirements............................................................................................9-5
Quakeproof Requirements .........................................................................................9-5
Illumination.................................................................................................................9-5
Fire Prevention Requirements ....................................................................................9-6
Atmospheric Pressure Requirement ...........................................................................9-6
Air Pollution Limitation ................................................................................................9-6
Adopt the joint grounding mode: The working groundings, protective groundings and
the lightning protection grounding of the building share one grounding body.
The temperature and humidity may also affect the grounding resistance.
If the temperature is lower than 0 or the humidity is too low, the grounding
resistance may change largely. In this case, bury the grounding pole deeply or
add chemical additives to meet the requirement on the grounding resistance.
The requirements on the grounding pole and the connection cable between the
grounding pole and the grounding bolt of the main device are as follows:
The angle iron that is used by the grounding pole should be shorter than 2 m. If
conditions permit, adopt the grounding net.
9-1
SJ-20110823134613-002|2011-12-16(R1.1)
The connection cable between the grounding pole and the grounding bolt of the
main device should adopt the copper core. The sectional area of the copper
cable should be equal to or larger than 50 mm2, and the length of the copper
cable should be as short as possible. If the length is longer than 50 m, use a
copper cable with a larger sectional area. Tin coat or flow promoter solder the
two ends of the connection cable. Remove the coating, varnish, oil paint, and
oxid coating from the fastening point to ensure good contact between the mental
surfaces.
To ensure a grounding resistance smaller than 1 , users need to consider the factors
that affect the grounding resistance. The factors include soil status, resistance of the
grounding body, grounding cable, and so on.
Before device commissioning, measure the accurate grounding resistance.
If the grounding resistance does not meet the requirement, usually you need to stop
the office deployment temporarily. If the user want to continue the office deployment,
the user needs to make a written commitment in which the user promises to be
responsible for any problem caused by grounding. The office deployment cannot
continue before the written commitment is allowed by the corresponding department
of ZTE Corporation.
After the device is put to use, the maintenance personnel must measure the grounding
resistance periodically and record the resistance. If the grounding resistance grows
larger, take proper measures to reduce it so that it meet the grounding resistance
requirement of the device.
9-2
SJ-20110823134613-002|2011-12-16(R1.1)
Relative Humidity
Long-Term Operating
Short-Term Operating
Long-Term Operating
Short-Term Operating
Conditions
Conditions
Conditions
Conditions
10 ~ 30
0 ~ 45
30% ~ 85%
20% ~ 90%
Measure the temperature of the operating environment inside the equipment room at the spot that is
1.5 m above the floor and 0.4 m before the rack when there is no protective plate in front or back of
the equipment rack.
Short-term operating conditions mean that the successive operating time is not more than 48 hours
and the accumulated operating time per year is not more than 15 days.
l
l
The percentage of fresh air in the equipment room should be at least 5%, ensuring
the freshness of the air.
In addition to percentage of dust and the size of the dust particle, there are also strict
requirements on the concentration of salt, acid and sulfide in the air, because they
cause the erosion of metal and aging of certain parts.
Harmful gases, such as SO2 and H2S, should be kept out of the equipment room to
protect the health of the maintenance personnel.
The concentration of the dust particles with a diameter of larger than 5 um should be
equal to or smaller than 3104 particles/m3.
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
Twist the signal line and the return line to counteract the induced voltage caused by
the EMI on the lines.
Separate the power cable and signal cable and do not lay them in parallel.
The grounding cable of the AC power supply and that of the DC power supply must
be separated strictly.
If the height of the main building or affiliated facilities such as chimney, antenna and
water tower is higher than 15 m, adopt effective lightning protection measures based
on the lightning protection requirements on class-2 civil buildings and structures.
Take measures to prevent direct lightning strokes and lightning current invasion. If a
high-rise building acts as the equipment room, take measures to prevent side thunder
strokes. In the areas where thunders are frequent, side thunder strokes are common.
In design, adopt measures to prevent side thunder strokes. For example, connect the
metal windows to the lightning protection down lead, and attach horizontal lightning
protection bars to the external wall surface with a specified distance.
The following lightning protection measures should be taken for the main building of the
equipment room.
l
l
Install a lightning protection grid or lightning protection bar in the locations where
lightning attacks are liable to occur.
On the top of the objects that are higher than the building roof, such as chimney,
antenna, and water tower, install the lightning protection wire or lightning arrester on
them.
The sectional area of the down lead of the lightning protection device should be at
least 200 mm2, and distance between the down leads should be equal to or smaller
than 30 m. In the case of joint grounding, the grounding resistance should be equal to
or smaller than 1 ; in the case of independent grounding, the grounding resistance
should be equal to or smaller than 10 .
In the past, the lightning protection grounding of the building and that of the power
supply system are separated. It is required that a certain distance be reserved
between the grounding bodies. However, the building space is limited, the distance
requirement is usually not met.
In fact, the grounding bodies cannot be separated in many cases, so a joint grounding
system is recommended, that is, the working grounding, protection grounding, and
the lightning protection grounding of the building share one grounding system. In this
case, the grounding resistance is high.
l
l
Before entering a building, the cables and metal pipes should be grounded.
The metal part (such as the reinforcing steel bar within the building or column) is
recommended as the down lead of the lightning protection grounding. The down leads
should be electrically interconnected for equalizing potential within the building.
9-4
SJ-20110823134613-002|2011-12-16(R1.1)
External electric field such as high-voltage transmission line and thunder and lightning.
External system such as in-door environment, floor material, and integrated
equipment structure.
Human contact of the maintenance personnel with the device which may leak the
static electricity of the human body to the device
To eliminate the damage that is caused by static electricity, take the following measures:
l
l
l
9.9 Illumination
The illumination in the equipment room should meet the following requirements:
l
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
Colored glass is recommended as the window glass, and dark and non-transparent
curtains are recommended.
Fluorescent lamps that are embedded in the ceiling of the equipment room are used
for illumination, and the recommended average illumination is 150 lx ~ 200 lx.
9-6
SJ-20110823134613-002|2011-12-16(R1.1)
Figures
Figure 1-1 Network Management Model ................................................................... 1-1
Figure 3-1 Single-Server System Hardware Structure ............................................... 3-1
Figure 3-2 Hardware Structure of Local HA System .................................................. 3-2
Figure 3-3 Hardware Structure of Remote Disaster Recovery System ...................... 3-3
Figure 5-1 Working Principle of NetNumen U31 ........................................................ 5-1
Figure 5-2 Remote Client Position ............................................................................ 5-2
Figure 5-3 NetNumen U31 System Hierarchy ........................................................... 5-3
Figure 7-1 Northbound Interface Position.................................................................. 7-2
Figure 7-2 Application of SNMP in NMS.................................................................... 7-6
Figure 8-1 Local Networking Topology ...................................................................... 8-2
Figure 8-2 Remote Networking Example................................................................... 8-3
Figure 8-3 Remote Client Networking Example......................................................... 8-4
Figures
Tables
Table 4-1 Server Hardware Configuration (SUN)....................................................... 4-1
Table 4-2 Server Hardware Configuration (IBM)........................................................ 4-2
Table 4-3 Server Software Configuration (SUN) ........................................................ 4-2
Table 4-4 Server Software Configuration (IBM) ......................................................... 4-2
Table 4-5 Client Hardware Configuration................................................................... 4-3
Table 4-6 Client Software Configuration .................................................................... 4-3
Table 9-1 Temperature and Humidity Requirements.................................................. 9-3
III
Tables
Glossary
CDMA
- Code Division Multiple Access
CMOS
- Complementary Metal-Oxide-Semiconductor
CORBA
- Common Object Request Broker Architecture
DCN
- Data Communications Network
DDN
- Digital Data Network
EMS
- Network Element Management System
ERT
- Embedded Remote Terminal
FDD
- Frequency Division Duplex
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
GUI
- Graphical User Interface
HA
- High Availability
HDSL
- High-data-rate Digital Subscriber Line
IETF
- Internet Engineering Task Force
IP
- Internet Protocol
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
J2EE
- JAVA 2 platform Enterprise Edition
V
LAN
- Local Area Network
LDAP
- Lightweight Directory Access Protocol
LTE
- Long Term Evolution
MIB
- Management Information Base
MML
- Man Machine Language
NE
- Network Element
NM
- Network Management
NMF
- Network Management Function
NMS
- Network Management System
NTP
- Network Time Protocol
OMM
- Operation & Maintenance Module
OSS
- Operation Support System
PC
- Personal Computer
RFC
- Request For Comments
SFTP
- Secure File Transfer Protocol
SLA
- Service Level Agreement
SMI
- Structure of Management Information
SNMP
- Simple Network Management Protocol
SSH
- Secure Shell
VI
Glossary
TCP
- Transfer Control Protocol
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
TDD
- Time Division Duplex
TMF
- Telecommunication Management Forum
TMN
- Telecommunications Management Network
UDP
- User Datagram Protocol
UMTS
- Universal Mobile Telecommunication System
WAN
- Wide Area Network
WiMAX
- Worldwide Interoperability for Microwave Access
VII