IManager U2000 Product Description

iManager U2000
V200R014
Product Description
Issue 02
Date 2014-05-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made
between Huawei and the customer. All or partial products, services and features described in this
document may not be within the purchased scope or the usage scope. Unless otherwise agreed by
the contract, all statements, information, and recommendations in this document are provided “AS
IS” without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements, information,
and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2014-05-15) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies Co., Ltd.
iManager U2000
Product Description Contents
Contents
1 Introduction.................................................................................................................................... 1
1.1 Positioning ....................................................................................................................................................... 1
1.2 NEs Managed by the U2000 ............................................................................................................................ 1
1.2.1 WRAN NEs ............................................................................................................................................ 1
1.2.2 GBSS NEs............................................................................................................................................... 2
1.2.3 SingleRAN NEs ...................................................................................................................................... 2
1.2.4 GU CN NEs ............................................................................................................................................ 2
1.2.5 LTE/EPC NEs ......................................................................................................................................... 3
1.2.6 eRelay NEs.............................................................................................................................................. 3
1.2.7 SingleDAS NEs ...................................................................................................................................... 3
1.2.8 STP NEs .................................................................................................................................................. 3
1.2.9 NGN NEs ................................................................................................................................................ 3
1.2.10 IMS NEs ............................................................................................................................................... 4
1.2.11 SmartCare/SmartPCC Network Devices ............................................................................................... 4
1.2.12 Wireless Bearer Network Devices ........................................................................................................ 5
1.2.13 Auxiliary Networking Devices .............................................................................................................. 5
1.3 Benefits ............................................................................................................................................................ 6
2 Architecture .................................................................................................................................... 8
2.1 Overview .......................................................................................................................................................... 8
2.2 Hardware Structure .......................................................................................................................................... 8
2.3 Software Structure .......................................................................................................................................... 11
2.4 External Interfaces ......................................................................................................................................... 11
3 Products and Application Scenarios ....................................................................................... 14

3.1 Overview ........................................................................................................................................................ 14
3.2 OM Solutions ................................................................................................................................................. 14
3.3 Network Management .................................................................................................................................... 26
4 Configuration............................................................................................................................... 28
5 Operation and Maintenance ..................................................................................................... 31
5.1 Overview ........................................................................................................................................................ 31
5.2 OM Functions................................................................................................................................................. 31
6 Technical Specifications ............................................................................................................ 32

6.1 Overview ........................................................................................................................................................ 32
6.2 Management Capability ................................................................................................................................. 32
Issue 02 (2014-05-15) Huawei Proprietary and Confidential iii

iManager U2000
Product Description Contents
6.3 Hardware Specifications ................................................................................................................................ 34

6.4 Reliability Specifications ............................................................................................................................... 36
6.5 Compliant Safety Standards ........................................................................................................................... 37
6.6 EMC Specifications ....................................................................................................................................... 38
6.7 Environmental Requirements ......................................................................................................................... 38
6.7.1 Storage Environment............................................................................................................................. 38
6.7.2 Transportation Environment ................................................................................................................. 41
6.7.3 Operating Environment ......................................................................................................................... 43
Issue 02 (2014-05-15) Huawei Proprietary and Confidential iv

iManager U2000
Product Description 1 Introduction
1 Introduction
1.1 Positioning
This document is applicable to iManager U2000 MBB network management system
V200R014.
The iManager U2000 centrally manages Huawei mobile network elements (NEs), including
WRAN NEs, GBSS NEs, SingleRAN NEs, GSM/UMTS core network (CN) NEs, LTE/EPC
NEs, SingleDAS NEs, eRelay NEs, NGN NEs, STP NEs, and IMS NEs. It also manages the
wireless bearer network devices and auxiliary networking devices used in the mobile network.
The U2000 provides basic functions, such as configuration management, performance
management, fault management, security management, log management, topology
management, software management, and system management. It also provides various
optional functions.
By default, SingleRAN NEs are managed by one U2000 system.
The U2000 provides centralized operation and maintenance (OM) functions for the Huawei
mobile element management solution. The U2000 adopts a modular design that allows the
modules to communicate with one another through the CORBA bus. In addition, the U2000
provides mediations for connecting various types of NEs.
The U2000 also provides external interfaces for interoperability with non-Huawei systems.
1.2 NEs Managed by the U2000

1.2.1 WRAN NEs
The U2000 manages the following WRAN NEs:
 Radio network controller: BSC6800
 Multimode base station controller: BSC6900 UMTS and BSC6910 UMTS
 Co-MPT base station: BTS3900
 Base station: NodeB
 IP clock server
Issue 02 (2014-05-15) Huawei Proprietary and Confidential 1

iManager U2000
1.2.2 GBSS NEs

The U2000 manages the following GBSS NEs:
 Base station controller: BSC6000 (GSM-R)
 Multimode base station controller: BSC6900 GSM and BSC6910 GSM
 Base station: GSM BTSs except BTS3900B and BTS3900E
 GSM Pico BTS: BTS3900B
 GSM compact BTS: BTS3900E
 IP clock server
1.2.3 SingleRAN NEs

The U2000 manages the following SingleRAN NEs:
 Multimode base station controller: BSC6900 GU and BSC6910 GU
 Separate-MPT base station: MBTS (GU), MBTS (GL), MBTS (UL), MBTS (GUL), and
MBTS (WL)
1.2.4 GU CN NEs
GU CN NEs consist of UMTS CN NEs and GSM CN NEs. Huawei CN NEs can be used on
both UMTS and GSM networks. The U2000 manages the following GU CN NEs:
 Serving GPRS support node: SGSN
 Gateway GPRS support node: GGSN
 Report server: SUR
 Mobile switching center server: MSC server
 Home location register: HLR9820
 Home subscriber server: HSS9860
 Home location register (service node): HLR-FE
 Media gateway: MGW
 Fixed-mobile convergence media gateway: FMC MGW
 Charging gateway: CG
 Signaling gateway: SG7000
 Signaling Application Network Expert: SANEX9510
 Interworking function: IWF
 Enhanced name server: ENS
 Unified number portability: UNP
 Unified identity management: UIM
 Unified equipment identity register: UEIR
 Unified subscriber center database: USCDB
 Visual IP
 Security immunity gateway: SIG

iManager U2000
 Embedded edge router: EER

 SigProbe
 SigProbeTDM
 UPortal
1.2.5 LTE/EPC NEs

The U2000 manages the following LTE/EPC/SingleDAS NEs:
 eNodeB: DBS3900 LTE, BTS3900 LTE, BTS3900A LTE, BTS3900L LTE, BTS3900AL
LTE, BTS3202E, BTS3202B, and BTS3203E
 Home subscriber server: HSS9860
 Universal switching unit: USU
 SAE-home subscriber server: SAE-HSS
 Unified serving node: USN
 Unified gateway: UGW
 Charging gateway: CG
 Unified policy and charging controller: UPCC
 Signaling service processing system: SPSV3
 IP clock server
1.2.6 eRelay NEs

 Wireless backhaul system: eRelay, including eRelay BS and eRelay Remote Node
(RRN)
1.2.7 SingleDAS NEs

 DAS control unit: DCU
1.2.8 STP NEs

The U2000 manages the following STP NEs:
 Convergent server: CAS9910
 Signaling service processing system: SPS
1.2.9 NGN NEs

The U2000 manages the following NEs involved in the NGN solution:
 Softswitch system: SoftX3000
 Signaling service processing system: SPS

iManager U2000
 Media switch server: MediaX3600

 Session border controller: SBC (SE2300/SE2600/SE2900)
 Media resource server: MRS6100
 iGateway Bill: iGWB
 Signaling transfer point: STP
 Smart home location register: SHLR9200
 Convergent application server: CAS9910
1.2.10 IMS NEs

The U2000 manages the following IMS NEs:
 Session border controller: SBC (SE2300/SE2600/SE2900)
 Home subscriber server: HSS (HSS9820)
 Calling session control function: CSCF (CSC3300)
 Unified policy and charging controller: UPCC
 Charging collection function: CCF (iCG9815)
 Advanced telephony server: ATS (ATS9900)
 Multimedia exchange server: MediaX (MediaX3600)
 IP Centrex: IPCTRX (ETAS9960)
 Multimedia resource function processor: MRFP (MRP6600)
 Unified subscriber center database: USCDB
 Attachment information management system: AIM (AIM6300)
 Service provisioning gateway: SPG (SPG2800)
 Unified gateway controller: UGC (UGC3200)
 E.164 Number: ENUM
 Convergent application server: CAS9910
 Mediation
 Presence server, Group server, Messaging server: PGM
 Enhanced name server: ENS
 ViewPoint
 Open service gateway: OSG
 Access gateway control function: AGCF (UAC3000)
 Rich communication suite: RCS (RCS9100/RCS9880)
 Terminal management system: TMS9950
 Network Recording&Playback Server: MediaX3600NRS (NRS2000)
 Communication Exposure Gateway: Tropo
 Openness Management Platform: OMP9360
1.2.11 SmartCare/SmartPCC Network Devices

The U2000 manages the following SmartCare/SmartPCC network devices:
 SEQ Analyst

iManager U2000
 NetProbe3010
 NetProbe9000
1.2.12 Wireless Bearer Network Devices

The U2000 manages the following wireless bearer network devices:
 RTN-series equipment: RTN 605, RTN 610, RTN 620, RTN 905, RTN 910, RTN 950,
RTN 950A, RTN 980, RTN 310, RTN 380, RTN 360, PTP500, PTP250, PMP450.
 OSN-series equipment: OSN1500, OSN2500, OSN3500, OSN7500, OptiX OSN 7500
II.
 NG WDM-series equipment: OSN 1800, OSN 3800, OSN 6800.
 BITS
 FFTx-series equipment: MA5694S, MA5898, MA5698.
1.2.13 Auxiliary Networking Devices

The U2000 manages the following auxiliary networking devices:
 MAN service platform: CX600-4/8/16, CX600-X3/X8/X16, CX600-X1/X2.
 NE-series routers: NE40, NE80, NE16E/NE08E/NE05, NE20E-8, NE20-2/4/8,
NE16/NE08, NE40E/NE40E-4/NE40E-8, NE80E, NE40E-X1/-X2, NE40E-X3/X8/X16,
NE5000E, NE5000E-Multi, NE20E-X6.
 Eudemon-series firewalls: Eudemon 8040, Eudemon 8080, Eudemon 1000, Eudemon
500, Eudemon 300, Eudemon 8080E, Eudemon 8160E, Eudemon 8000E-X, Eudemon
6080E, Eudemon 1000E, Eudemon 100E, Eudemon 200S, Eudemon 200E-B, Eudemon
200E-C, Eudemon 200E-F, Eudemon 200E-BW, Eudemon 200E-F-D, Eudemon 200E-X,
Eudemon 1000E-N, Eudemon 1000E-X, SeMG9811.
 S-series LAN switches: S2300, S3300, S5300, S9300, S2700, S3700, S5700, S6700,
S7700, S9700, S6300, S8500, S6500, S5600, S5500, S5000, S3900, S3500, S3000,
S2000.
 ATN-series equipment: ATN905, ATN910I, ATN910, ATN950, ATN950B, ATN980,
ATN990.
 AR46-series routers: AR4640, AR46-20.
 SVN-series equipment: SVN3000, SVN2200, SVN5300, SVN5500, SVN5560.
 SIG-series equipment: SIG9800, SIG9800-X3, SIG9800-X8, SIG9800-X16.
 Domain name server (DNS)
 Dynamic host configuration protocol server: DHCP server
 NE bearing server, a server bearing the services of the SG7000, MSC server, and iGWB
 Wi-Fi device: Skyway Excel XL5810 from the third-party
When the enhanced management functions, such as DNS and DHCP, are required, users need to
purchase Huawei customization services.

iManager U2000
1.3 Benefits
Open Structure Allowing for Smooth Evolution
iManager U2000 MBB network management system is a future-proof solution for managing
mobile networks. It provides a centralized network management platform for supporting
telecom operators in their long-term network evolution and shielding the differences between
various network technologies. The U2000 focuses on the continuous efforts of telecom
operators toward better network OM and retains the OM experience of previous network
management systems.
The U2000 is a centralized wireless network management platform. The U2000 server
software consists of the main version software and mediation software. The main version
software implements system functions, and the mediation software is used for the adaptation
of different NE interfaces. The U2000 can manage new NEs after the corresponding
mediation software is installed. The U2000 adopts an open structure so that it can manage the
eRelay, SingleDAS, CN, NGN, STP, IMS, and radio networks of various technologies, such
as GSM, WCDMA, and LTE. In addition, the U2000 can evolve accordingly when the
network evolves.
The U2000 provides the Co-control BTS management solution to manage the NE type of
Co-MPT base station. This operates and maintains GBTS, NodeB, and eNodeB in a
centralized manner, improving SingleRAN OM efficiency.
The U2000 provides standard CORBA, SNMP, file, and alarm streaming interfaces. In
addition, the U2000 allows for interoperability with other systems provided by HP, Aircom,
IBM, Inspur, Remedy, Vallent, Mycom, and Bright Oceans.
Powerful Network Management

Centralized management of large-scale networks requires high system performance. In
addition, today's market demand focuses on hardware reuse and smooth expansion.
To address these requirements, the U2000 provides the multi-server load-sharing (SLS)
system based on the Sun platform and the cluster solution based on the ATAE platform. This
enables smooth network expansion, during which users can enhance the management
capability of the U2000 by adding one or more servers to the SLS system or by adding service
boards to the ATAE cluster system. This protects the telecom operator's hardware investments
and reduces network deployment costs.
Reduced OPEX
The Configuration Management Express (CME), a radio configuration solution, provides
powerful functions through wizards, templates, and GUIs. It enables users to plan
configuration items, check the data of the entire network, and compare cell configuration data
against the baseline cell. This facilitates data configuration for the entire radio access network.
The CME enables users to create sites in batches remotely, expand network capacity quickly,
optimize network efficiently, and reparent base stations easily. This improves the
configuration efficiency and accuracy.
The iSStar enhancement maintenance platform enables OM engineers to customize the
service process by editing programs. With it, the U2000 can automatically handle OM tasks in
batches.
In addition, the U2000 provides a series of featured functions, including a network health
check, remote and batch upgrade of NEs, automatic base station planning, automatic

iManager U2000
optimization of neighboring cell relationships, remote base station commissioning, device

panels, maintenance-mode alarm setting, and RAN sharing management.
These functions greatly facilitate operation and maintenance and therefore reduce the total
cost of operation (TCO).

iManager U2000
Product Description 2 Architecture
2 Architecture
2.1 Overview
The U2000 system works in client/server (C/S) mode.
The U2000 software consists of the client software, server software, and NE mediation
software. The client software runs on the U2000 client, and the server software and mediation
software run on the U2000 server.
This chapter describes the hardware and software structures of the U2000 system.
2.2 Hardware Structure

Hardware Structure
The U2000 system typically consists of U2000 servers, U2000 clients, alarm boxes, and some
networking devices. Figure 2-1 shows the hardware structure of the U2000 single-server
system. The U2000 provides multiple solutions to meet the specific scenario requirements of
telecom operators. For details about these solutions, see section 3.2 "OM Solutions".
Figure 2-1 Hardware structure of the U2000 single-server system

iManager U2000
Hardware Description
The U2000 server supports multiple hardware platforms. This section describes the ATAE
cluster system. The hardware of the ATAE cluster system comprises the cabinet, ATAE
subracks, boards, and disk arrays, as shown in Figure 2-2.
Figure 2-2 Hardware of the ATAE cluster system
An ATAE subrack consists of components with different functions. Boards in the subrack
communicate with one another through the backplane to function as an independent work
unit.
Figure 2-3 Appearance of the ATAE subrack

iManager U2000
Table 2-1 ATAE subrack
No. Board Type Description
1 Service It is installed in slots 1 to 6 or 9 to 14. You can install application

processing software on the board for data service processing.
unit
2 Switching It is installed in slots 7 and 8 and provides all Layer 2 (L2) network
board switching functions within the ATAE subrack.
3 Subrack It is installed at the bottom of the ATAE subrack and manages all
management ATAE hardware devices. It provides functions, such as device
module management, event management, asset management, power
management, remote maintenance, configuration recovery, energy
saving, and power supply management.
Figure 2-4 shows the appearance of front and rear boards for each type.
Figure 2-4 Appearance of ATAE boards

iManager U2000
2.3 Software Structure

As shown in Figure 2-5, the U2000 software is classified into the following types:
 U2000 server software
 U2000 client software
 NE mediation software
NE mediation software varies according to the NE version. Through the adaptation of the NE
mediation software, the U2000 connects to the NE of the corresponding version.
Figure 2-5 Software structure of the U2000 system
2.4 External Interfaces

To interconnect with external systems and software, the U2000 provides the following
interfaces:
 CORBA interface
The CORBA interface is based on CORBA interface specifications and is in compliance
with 3GPP R6 specifications.
Through the CORBA interface, the NMS manages U2000 alarms, sets performance
measurement tasks, queries U2000 configuration data, and queries and delivers
configuration parameters in batches.
 CORBA security interface
Through the CORBA security interface, the NMS manages U2000 users and user rights,
such as creating users and maintaining user information.

iManager U2000
 File interface
The U2000 saves alarm data, performance data, configuration data, inventory data, and
LTE tracing data as files. Through the file interface, the NMS obtains and processes
these files.
The NMS can use the configuration file interface to obtain configuration data from the
U2000. In addition, after the CME is installed, the configuration file interface can be
used to integrate the data planning tools of telecom operators into the U2000. In that way,
data planning, modification, and activation are automatically performed through the
configuration file interface. The configuration file interface is applicable to OM
scenarios, such as site creation, site relocation, network parameter optimization, and the
optimization of neighboring cell relationships.
 Alarm streaming interface
The U2000 forwards NE alarms to the NMS in the form of character stream in real time.
The NMS can actively obtain the list of active alarms from the U2000.
 SNMP interface
Through the SNMP alarm interface, the U2000 forwards alarms to the NMS for handling
in real time. The SNMP interface supports the SNMPv1, SNMPv2, and SNMPv3
protocols.
 XML interface
Complying with the TMF MTOSI 2.0 series standards, the XML NBI enables the U2000
to provide unified alarm, performance, inventory, service provisioning, diagnostic test,
and protection group management on transport and IP equipment for OSSs.
 MML transparent transmission interface
The MML transparent transmission interface serves as a proxy for transferring MML
commands between the NMS and NEs. With this interface, the NMS can operate and
maintain the related NEs using MML commands.
 Syslog interface
The U2000 forwards operating system logs, U2000 logs, and NE logs using the Syslog
protocol.
 LDAP user management interface
This interface complies with LDAP. Through this interface, the security management
system provided by a third party can create, modify, delete, and query Huawei OSS
systems accounts.
 LDAP user authentication interface
This interface supports the account authentication based on LDAP as well as remote
authentication of user names and passwords.
 RADIUS user authentication interface
This interface supports the account authentication based on RADIUS as well as remote
authentication of user names and passwords.
 Northbound line test interface
The line test system connects to the NEs managed by the U2000 server through the
northbound interfaces for line test. In this way, the line test system works with the NEs
to automatically handle and manage subscriber complaints, conduct test, and rectify
faults.
 TL1 northbound interface
The TL1 northbound interface of the U2000 is used to interconnect the EMS with the
OSS. By using the TL1 northbound interface, the OSS or NMS can provide services and
perform OM operations for integrated access devices (IADs), multimedia terminals,

iManager U2000
voice subscribers, basic rate access (BRA) subscribers, primary rate adaptation (PRA)
subscribers, and multimedia subscribers. In addition, the OSS or NMS manages NGN
resources and services of the SHLR, AGCF and SoftX3000 by using the TL1 northbound
interface. NEs report notification messages to the OSS or NMS by using the TL1
northbound interface of the U2000.

iManager U2000
Product Description 3 Products and Application Scenarios
3 Products and Application Scenarios
3.1 Overview
The U2000 provides various OM solutions for telecom operators to meet the requirements of
network deployment, network monitoring, network adjustment, and service management.
Telecom operators can select proper U2000 systems as required.
3.2 OM Solutions
The U2000 provides various OM solutions based on different hardware platforms. Table 3-1
describes whether the hardware platforms support these OM solutions.
Table 3-1 Hardware/networking types
Server Single- HA Remote SLS Emergency ATAE ATAE ATAE

Server HA Cluster Cluster Cluster
Remote Emergency
HA System
ATAE N N N N N Y Y Y
Sun Y Y Y Y Y N N N
HUA Y N N N N N N N
WEI
PC
Server
 In Table 3-1, Y indicates support and N indicates not support.

 The ATAE cluster, ATAE cluster remote HA, and ATAE Cluster Emergency systems are developed
based on the ATAE platform.
 The SLS, remote HA, and emergency systems are developed based on the Sun platform.
 The low-cost solution, which uses the single-server system based on the HUAWEI platform, manages
devices only on IMS, eRelay or SingleDAS networks.

iManager U2000
Table 3-2 describes the application scenarios of the U2000 OM solutions.
Table 3-2 Application scenarios of the U2000 OM solutions
Server Solution Application Scenario
ATAE ATAE The solution is based on the ATAE platform and uses the
cluster cluster system comprising boards. It can centrally manage
solution a large-scale network, and supports the centralized
deployment of the U2000 (including the Trace Server),
PRS, and Nastar (including the eSAU). The ATAE cluster
solution helps telecom operators greatly reduce energy
consumption and save equipment room space. It also helps
telecom operators reduce CAPEX and improve
competitiveness through centralized hardware monitoring
and maintenance.
ATAE The ATAE cluster remote HA system has the same
cluster features as those of the ATAE cluster solution. It can
remote HA also effectively reduce the possible losses caused by power
system failures, fires, and earthquakes and minimizes the duration
of U2000 service interruption caused by software or
hardware faults. This improves the availability of the
U2000 and the reliability of the network.
ATAE-based The emergency system is a backup of the primary system.
emergency If the primary system fails to provide services properly, the
system emergency system can provide basic network management
services.
The ATAE-based emergency system guarantees the high
reliability of the ATAE cluster. During a failover or
upgrade of the ATAE cluster, the emergency system can
significantly reduce service disruption time, keep
monitoring services to the maximum extent, and enhance
system robustness.
Sun Sun-based The Sun-based SLS system comprises multiple servers. It
SLS system uses one set of OSS to centrally manage devices on the
entire network and allows for central management of
large-scale networks. This significantly reduces the
number of OSSs, required workload, and OM costs.
Sun-based The Sun-based remote HA system provides the same
remote HA software and hardware redundancy as that of the HA
system system. It can also effectively reduce the possible losses
caused by power failures, earthquakes, fires, wars,
tsunamis, and mudflows. Remote protection is
implemented on both of the U2000 servers and the disaster
recovery capability of the U2000 is improved.

iManager U2000
Server Solution Application Scenario
Sun-based The emergency system has lower hardware requirements

emergency than typical local and remote HA systems and is applicable
system to U2000 single-servers and SLS systems that are based on
the Sun platform. The emergency system is a backup of the
primary system. If the primary system fails to provide
services properly, the emergency system can provide basic
network management services.
Sun HA system The HA system provides complete local dual-node
redundancy for servers, disk arrays, network interfaces,
and Ethernet switches. When a fault occurs, the U2000
automatically performs a switchover, providing enhanced
system reliability and improving system maintainability.
HUAWEI Low-cost The U2000 provides a low-cost solution, which uses the
PC Server solution single-server system based on the HUAWEI platform to
manage IMS, eRelay or SingleDAS network devices. This
solution meets users' demands for routine maintenance. In
addition, it helps telecom operators reduce their purchasing
costs. Compared with the single-server system based on
the Sun platform, the low-cost solution uses PC server and
does not need disk arrays.
ATAE Cluster Solution

Developed on the ATAE platform, the ATAE cluster system allows the deployment of multiple
boards to provide powerful management capabilities.
Consisting of service boards, switching boards, OSS self management unit (OSMU), and disk
arrays, the ATAE cluster system has the following features:
 High integration
 High performance
 N:1 redundancy
 Hardware redundancy
 Board plug-and-play
 OSMU intelligent management
With the increasing demand of enhanced management capability, users can implement
capacity expansion by adding boards. In addition, multiple OSS products, such as the U2000,
the PRS, and the Nastar, can be deployed on the ATAE cluster system in a centralized manner.
This enables telecom operators to use multiple OSS products at the same time. Figure 3-1
shows the physical structure of an ATAE cluster system.

iManager U2000
Figure 3-1 Physical structure of the ATAE cluster system
Table 3-3 describes the devices in the ATAE cluster system.
Table 3-3 Devices in the ATAE cluster system
Device Description
ATAE subrack The following typical configuration uses the Sybase database as an
example.
 The OSMU board monitors and manages the entire ATAE cluster
system and can be accessed through a web browser.
 200 equivalent NEs solution: two U2000 service boards (one master
and one standby) and one database board.
 400 equivalent NEs solution: three U2000 service boards (one
master, one slave, and one standby) and one database board.
 800 equivalent NEs solution: four U2000 service boards (one
master, two slave, and one standby) and two database boards (one
master and one slave).
 1200 equivalent NEs solution: five U2000 service boards (one
master, three slave, and one standby) and three database boards (one
master and two slave).
 1600 equivalent NEs solution: six U2000 service boards (one
master, four slave, and one standby) and fix database boards (one
master, three slave, and one standby).
 2000 equivalent NEs solution: seven U2000 service boards (one
master, five slave, and one standby) and six database boards (one
master, four slave, and one standby).
 The Sybase database shares the standby board with the U2000
system.
 Two switching boards function as switches.
 Trace Server boards must be configured when the U2000 manages
NEs of the LTE network.
Disk array Other service boards except the OSMU use the disk array as a storage
device.

iManager U2000
ATAE Cluster Remote HA System

The ATAE cluster remote HA system is available in online mode. The system effectively
prevents losses brought by disasters, such as earthquakes, fires, and power failures. It provides
remote redundancy for U2000 server nodes, improving disaster recovery capability of U2000
servers.
The U2000 ATAE cluster remote HA system is composed of two ATAE cluster systems that
are located in different places. Two ATAE cluster systems synchronize data in real time over a
dedicated channel. In case the active node is faulty, the standby node can be started in time
and take over the services from the active node after data synchronization is complete. This
mechanism ensures service continuity.
Figure 3-2 shows the physical structure of the ATAE cluster remote HA system.
Figure 3-2 Physical structure of the ATAE cluster remote HA system
Table 3-4 describes the devices in the ATAE cluster remote HA system in Figure 3-2.
Table 3-4 Devices in the ATAE cluster remote HA system
Device Description
Server Functions as the U2000 server that runs the U2000 server software.
The servers in equipment room I and equipment room II use the
cluster software to monitor and switch over system resources.
Disk array Provides highly reliable storage space for the servers.
ATAE Cluster Emergency System

As a backup system for the primary system, the emergency system (ES) and the primary
system can be deployed on the same LAN and managed by the same OSMU (local
deployment) or be deployed on different LANs and managed by different OSMUs (remote
deployment). Figure 3-3 and Figure 3-4 show the networking scheme of the emergency
system.

iManager U2000
Figure 3-3 Networking scheme of the local emergency system

iManager U2000
Figure 3-4 Networking scheme of the remote emergency system
Sun-based SLS System

Developed on the Sun platform, the SLS system allows the deployment of multiple servers to
implement the centralized management of large-scale networks.
In the U2000 SLS system, multiple servers are deployed to form an EMS, and services are
loaded and processed on different servers in a distributed manner. The SLS system manages
multiple U2000 servers in a centralized manner and supports the smooth expansion of the
U2000. Therefore, the costs for operating and maintaining multiple U2000 systems are
reduced. Figure 3-5 shows the physical structure of a U2000 SLS system.

iManager U2000
Figure 3-5 Physical structure of the U2000 SLS system
Table 3-5 describes the devices in the SLS system.
Table 3-5 Devices in the SLS system
Device Description
Master server The master server runs the U2000 server software and balances load
with slave servers.
Slave server Slave servers run the U2000 server software and balance load with the
master server.
Standby server The standby server functions as a backup for the master or slave
server. If the master server or a slave server becomes unavailable, the
services carried by the master or slave server are switched over to the
standby server through the cluster software.
Disk array The disk array provides reliable storage for the master and slave
servers. When an exception occurs on the master server or on a slave
server, the cluster software mounts the disk array to the standby
server.
HA System
Huawei provides a U2000 high availability (HA) system where services are automatically
switched over from the active server to the standby server when an exception occurs in the
active server. In this way, the reliability of the U2000 system is improved.
The active and standby servers are located at the same place to constitute an HA system
through the cluster software. The active and standby servers communicate with each other on
a local area network (LAN) and access the same disk array. Figure 3-6 shows the physical
structure of a U2000 HA system.

iManager U2000
Figure 3-6 Physical structure of the U2000 HA system
Table 3-6 describes the devices in the HA system.
Table 3-6 Devices in the U2000 HA system
Device Description
Active server The active server functions as the U2000 system active server. It runs
the U2000 server software. The active server, together with the
standby server, performs resource monitoring and service switchover
through the cluster software.
Standby server The standby server functions as a backup for the active server. When
the active server becomes unavailable, the resources carried by the
active server are switched over to the standby server through the
cluster software.
Disk array Two disk arrays, one of which is the mirror of the other, provide
reliable storage space. When an exception occurs on the active server,
the cluster software mounts the disk arrays to the standby server.
Sun-based Remote HA system

Huawei remote HA system provides software and hardware redundancy. It also effectively
reduces the impact of power failures, earthquakes, fires, wars, tsunamis, and mudslides.
Remote protection is implemented on both of the U2000 servers and the disaster recovery
capability of the U2000 is improved.
The active and standby servers in different locations constitute a remote HA system through
the cluster software. The active and standby servers communicate with each other through the
OM network and access different disk arrays. Figure 3-7 shows the physical structure of a
remote HA system.

iManager U2000
Figure 3-7 Physical structure of the remote HA system
Table 3-7 describes the devices in the remote HA system.
Table 3-7 Devices in the remote HA system
Device Description
Server The server functions as the U2000 system server. It runs the U2000 server
software. The servers in equipment rooms I and II perform resource
monitoring and service switchover through the cluster software.
Disk array The disk array provides the server with reliable storage.
Sun-based Emergency System

The emergency system has lower hardware requirements than typical local and remote HA
systems and is applicable to U2000 single-servers and SLS systems that are based on the Sun
platform. The emergency system functions as a backup for the U2000 primary system. It
provides basic network management services when the primary system fails to provide
services properly. The emergency system and the primary system can be deployed on the
same LAN. They can also be deployed on different LANs and in this case they communicate
with each other through an IP network.
An emergency system can back up no more than four U2000 single-server systems or no more
than two U2000 SLS systems. The system to be backed up is referred to as a primary system.
When the emergency system takes over the services of one primary system, it cannot take
over the services of any other primary system.
Figure 3-8 shows the physical structure of the emergency system that backs up no more than
four U2000 single-server systems. Figure 3-9 shows the physical structure of the emergency
system that backs up no more than two U2000 SLS system.

iManager U2000
Figure 3-8 Physical structure of the U2000 emergency system when it backs up N (N ≤ 4) U2000
single-server system
Figure 3-9 Physical structure of the U2000 emergency system when it backs up N (N ≤ 2) U2000
SLS systems
Table 3-8 describes the devices in the emergency system.
Table 3-8 Devices in the emergency system
Device Description
Server The server in the emergency system functions as a backup for the
server in the primary system. When the server in the primary system
becomes unavailable, the carried services are manually switched over
to the server in the emergency system.
Disk array The disk array provides the server with reliable storage.
Low-Cost Solution
The U2000 provides a low-cost solution, which uses the single-server system based on the
HUAWEI platform to manage IMS, eRelay or SingleDAS networks. This solution meets
users' demands for routine network OM operations. In addition, it helps operators or users to
reduce their purchase cost. For example, the Sun-based single-server system uses disk arrays.
However, the single-server system based on the HUAWEI platform uses PC server and does
not need disk arrays.

iManager U2000
Web-based Client Access

The U2000 provides the Citrix access solution, which enables users to log in to the U2000
client.
In the Citrix access solution, one or more servers are added to the existing U2000 system. The
Citrix access solution has the following advantages:
 Solving the problem that the number of connected clients is restricted by the hardware
capacity of the U2000 server
 Reducing the costs of upgrading and maintaining the U2000 client
 Reducing the hardware configuration costs of the PC that the U2000 client is running on
 Lowering the requirements for the operating system environment of the PC that the
U2000 client is running on
Comprehensive System Security Solution

Based on the features of the OM plane, the OSS security solution is designed to meet the
requirements on the following security layers:
 Network security: Secure networking technologies, such as security domain division,
firewall, secure remote maintenance, and intrusion detection, to protect the OSS
network.
 Platform security: Security measures, such as system hardening, security patching, and
antivirus protection, are implemented to promote the security level of the operating
system OS and therefore provide a secure and reliable platform for OSS service
applications.
 Application security: Security policies, such as transmission security, user management,
session management, log management, and security alarm, are implemented to protect
the security of specific applications.
Network Time Synchronization Solution

The U2000 supports the Network Time Protocol (NTP)/Simple Network Time Protocol
(SNTP) to synchronize its time with NEs on the entire network.
 The clock source and NTP server are provided by the telecom operator, and the U2000
server functions as the NTP client or intermediate NTP server. When functioning as an
intermediate NTP server, the U2000 can synchronize time with the upper-layer NTP
server and provide a clock source that managed NEs can synchronize with.
 A dedicated clock server is provided, along with two NTP service channels working in
active/standby mode. The clock source server can be deployed as the top NTP server, or
as a intermediate NTP server.
Veritas System Backup and Restore Solution

The U2000 adopts the Veritas system backup and restore solution. Through this solution,
users can back up and restore the database software, application software, system
configuration files, service data stored in the database, and important NE data.

iManager U2000
3.3 Network Management

This section describes the main functions of the U2000 network management. For information
about more functions, see iManager U2000 V200R014 Feature List and Description. You can
contact Huawei technical support to obtain this document.
Figure 3-10 shows the U2000 network management functions.
Figure 3-10 U2000 client GUI (application style)
Table 3-9 describes the U2000 network management functions.
Table 3-9 U2000 network management functions
Category Function Description
General Topology Users can use this function to construct and manage the
management topology of the entire network, query the networking and
running status of NEs, and monitor the running status of the
entire network in real time.
Fault Users can use this function to monitor, query, and collect
management statistics of network alarms or events, and quickly detect,
locate, and rectify network or device faults.
Configuration Users can use this function to display NE configuration
management information and monitor NE resource status.
Performance Users can use this function to manage performance data and
management effectively evaluate the operation network, ensuring the
network QoS.
Security Users can use this function to control the U2000 operation
management rights, and record the running status and operations of the
U2000, ensuring system security.

iManager U2000
Category Function Description
Software Provides professional OM procedures to manage NE version

management files and upgrade NE software and patches, and allows you to
query, upgrade, back up, or delete NE version software,
patches, configuration data, and licenses.
Trace and Provides the inventory management, device panel, signaling
maintenance tracing, transmission management, and RF performance test
for network maintenance, helping you locate network
problems and rectify faults.
RAN service CME The wireless configuration solution provides quick
management deployment and efficient maintenance of GBSS, WRAN, and
LTE network in wizard, template, and GUI modes.
SON Users can use this function to achieve automatic planning and
optimization of the network.
CN service CN The CN dual-homing management is a disaster tolerance
management dual-homing mechanism that prevents the disconnection of mobile network
management services in the managed domain due to MSC Server, UGC, or
UAC breakdown, or system faults. This mechanism is used to
ensure the secure and reliable operation of mobile networks.
CN Pool Users can use this function to achieve data configuration,
management monitoring, and maintenance for MSC Pool, CDMA Pool,
SingleSD, CSCF Pool, SGSN Pool, and MME Pool networks.
Signaling Users can use this function to monitor the correctness and
network status of the configurations, such as the DSP, link group, and
service connection group and help manage signaling network devices.
management
IMS and Users can use this function to query IMS subscribers and
NGN service configure NGN services.
management
IMS Users can use this function to query all information (including
Subscriber basic information, service information, and status information)
Information about a subscriber served by an IMS NE, which facilitates
Query customer complaint handling and fault identification.
Wireless Transmission Users can centrally manage mobile devices and wireless
Bearer bearer network management devices through a single OSS.
Network
Management

iManager U2000
Product Description 4 Configuration
4 Configuration
The U2000 system can be installed on different types of servers. Telecom operators can select
appropriate servers according to the number of managed NEs.
Table 4-1 describes a typical server configuration.
 The single-server system based on the HUAWEI platform manages only IMS/eRelay/SingleDAS
network devices.
 If the U2000 system needs to provide more advanced management functions for wireless bearer
network management featrue, the management components of the MBB backhaul devices are
deployed on one independent ATAE board.
 This chapter describes only the typical U2000 server configurations, and the configurations may
vary with application scenarios. For details, see iManager U2000 Configuration Principle. You
can contact Huawei technical support to obtain this document.
Table 4-1 Typical U2000 server configuration
Platform Networking Server CPU Memory Hard Operating

Type Disk System
and
Database
Sun Single-server Sun Sparc 2 x 2.66 16 GB 2 x Solaris and

system, HA Enterprise GHz 300 Sybase
system, and M4000 GB
remote HA Server
system 4 x 2.66 32 GB 2 x
GHz 300
GB
Sun Sparc 4 x 2.66 32 GB 2 x
Enterprise GHz 300
M5000 GB
Server
6 x 2.66 48 GB 2 x
GHz 300
GB
8 x 2.66 64 GB 2 x
GHz 300
GB

iManager U2000
Platform Networking Server CPU Memory Hard Operating

Type Disk System
and
Database
SLS system Sun Sparc 8 x 2.66 64 GB 2 x

Enterprise GHz 300
M5000 GB
Server
Emergency Sun Sparc 2 x 2.66 16 GB 2 x
system Enterprise GHz 300
M4000 GB
Server
Sun Sparc 8 x 2.66 64 GB 2 x
Enterprise GHz 300
M5000 GB
Server
HUAWEI Single-sever RH5885H 4 x 2.0 32 GB 8 x SUSE
system V3 GHz 300 Linux and
GB Sybase
ATAE Cluster OSMU board 1 x 2.4 16 GB 2 x SUSE
system and GHz 600 Linux and
cluster quad-core GB Sybase
remote HA
system U2000/Trace 1 x 2.4 48 GB None
Server GHz
service board hexa-core
Database 1 x 2.4 48 GB None
board GHz
hexa-core
Emergency ES board 1 x 2.4 48 GB 2 x
system GHz 600
hexa-core GB
The Sun T5220 server is no longer delivered for installing U2000 V200R014. Customers
using servers configured with any of the items described in Table 4-2 can still install and run
U2000 V200R014 on their servers. Table 4-3 lists the minimum configuration items of the
U2000 client.
Table 4-2 U2000 server minimum hardware requirements
Server Model CPU Memory Hard Disk

Sun T5220 1 x 1.2 GHz 8 GB Local: 4 x 146 GB
Sun M4000 2 x 2.4 GHz 16 GB Local: 2 x 146 GB;
Disk array: 16 x 146 GB

iManager U2000
Sun M5000 4 x 2.4 GHz 32 GB Local: 2 x 146 GB;

Disk array: 16 x 146 GB
IBM x3850 X5 4 x 2.0 GHz 32 GB Local: 8 x 300 GB
RH5885H V3 4 x 2.0 GHz 32 GB Local: 8 x 300 GB
ATAE Cluster OSMU 1 x 2.4 GHz 16 GB Local: 2 x 300 GB
board quad-core
U2000/ 1 x 2.4 GHz 48 GB None
Trace hexa-core
Server
service
board
Database 1 x 2.4 GHz 48 GB None
board hexa-core
Table 4-3 U2000 client minimum hardware requirements
Item Configuration
CPU E5300 or above
Memory 2 GB
Hard disk 160 GB
Accessories DVDRW-Integrated Ethernet adapter-Integrated audio
adapter-Built-in sound box-19'' LCD
Operating system The following operating systems are supported:
 Windows 7 (32-bit) and (64-bit)
 Windows 2003 Server (32-bit) and (64-bit)
 Windows 2003 R2 Server (32-bit) and (64-bit)
 Windows 2008 Server (64-bit)
 Windows 2008 R2 Server (64-bit)
Application software U2000 client application software
If the U2000 client runs on the Windows 7 Professional operating system, the 32-bit version of Internet
Explorer 8 must be used.

iManager U2000
Product Description 5 Operation and Maintenance
5 Operation and Maintenance
5.1 Overview
The U2000 provides a powerful and efficient OM functions, all of which significantly
improve OM efficiency.
5.2 OM Functions
This section provides the main OM functions of the U2000. For information about more
functions, see iManager U2000 V200R014 Feature List and Description. You can contact
Huawei technical support to obtain this document.
Table 5-1 Main OM functions of the U2000

OM Functions Description
System Provides maintenance functions, such as data backup and restore,
management system monitoring, file transfer, task scheduling, license
application management, and OSS health check.
(U2000 client)
OSMU The OSS Self-Maintenance Unit (OSMU) enables users to operate
(web-based) and maintain the U2000 on the GUI through the web. With the
OSMU, users can collect data, perform automatic inspection, clear
data, install mediations, and manage northbound interfaces without
installing the client. As a result, field support engineers no longer
need to remember Unix and Linux commands or database-related
commands when commissioning and maintaining the U2000. This
reduces the maintenance cost and improves the maintenance
efficiency.
In addition, the U2000 provides the OSMU smart hardware
management tool for the ATAE system. As the navigation path to
the ATAE cluster device maintenance, the OSMU provides
centralized maintenance for devices in the ATAE cluster system.
Log collection Collects fault logs of the U2000.
tool (installed on
the U2000 client)

iManager U2000
Product Description 6 Technical Specifications
6 Technical Specifications
6.1 Overview
This chapter describes the following system specifications:
 Management capability
 Reliability specifications
 Compliant safety standards
 EMC specifications
 Environmental requirements
6.2 Management Capability

The management capability of the U2000 is calculated according to equivalent NEs, and the
NMS server is configured according to the number of equivalent NEs.
If the U2000 server hardware configurations are the same, the capability of managing NEs
varies according to the versions of the operating system and database on the U2000 server.
Table 6-1 describes the capability of the U2000.
The Solaris10 operating system and the Sybase15 database are installed on Sun servers. The
HUAWEI PC server uses the SUSE Linux10 operating system and Sybase15.5 database.
Table 6-1 provides the NE management capability data that is calculated when the CME and
U2000 are deployed on one server. If the PRS and the U2000 are deployed on one server, the
NE management capability decreases by 30%.
Table 6-1 NE management capability of the U2000 (except SLS system)
Hardware Platform Management Capability (Number of Equivalent NEs)

2 CPU Sun M4000 ≤ 100
4 CPU Sun M4000 ≤ 190
4 CPU Sun M5000 ≤ 190
6 CPU Sun M5000 ≤ 270

iManager U2000
Hardware Platform Management Capability (Number of Equivalent NEs)

8 CPU Sun M5000 ≤ 340
4 CPU RH5885H V3 ≤ 100
The management capability of an SLS system depends on the number of servers. Assume that
the management capability of one single server is 1, the total management capability is the
result of multiplying 1 by a coefficient if another server is added. This coefficient varies
according to the number of added servers. Table 6-2 shows an example of the management
capability of the full configuration M5000 server.
Table 6-2 Estimation of the management capability on NEs in the Sun SLS system (M5000)
Number of Servers Total Management Capability Coefficient

Single 1
2:1 1.6
3:1 2.3
4:1 3.6
5:1 4.8
6:1 6
The management capability of the ATAE cluster system depends on the number of boards in
use. The ATAE cluster system can manage a maximum of 2000 equivalent NEs.
The number of equivalent NEs is determined by the following factors:
 Physical NE type and version: Different NE types and versions use different amounts of
U2000 resources. As a result, the number of equivalent NEs converted varies according
to the NE type.
 Number of measurement counters: KPI or all counters can be set to measure an NE's
performance. In either scenario, the required amount of U2000 hardware resources is
different. Therefore, the number of measurement counters has an impact on the
equivalent NE conversion.
 Performance statistical period: Each NE reports performance data to the U2000 at certain
intervals. Processing data reported every 60 minutes requires different amount of U2000
hardware resources from that reported every 15 minutes.
The number of equivalent NEs for the same type of NEs varies according to performance
measurement requirements of users. For details, see the table of calculating equivalent NEs in
iManager U2000 V200R014 Configuration Principles. You can contact Huawei technical
support to obtain this document. You can ask Huawei engineers to analyze and calculate the
number of equivalent NEs for the measurement unavailable in the table.

iManager U2000
6.3 Hardware Specifications

The U2000 cabinet allows for the flexible configuration of devices. The hardware weight is
equal to that of the cabinet and inside devices. The hardware power consumption is equal to
that of all devices inside the cabinet. For details about device parameters, see Table 6-3 and
Table 6-4.
Table 6-3 Device parameters (Sun)
Server Dimension Weight (kg) Power

Configuration Consumption
Width Depth Height (W)
(mm) (mm) (mm)
Sun M4000 444 810 263 (6U) 84 2350

Sun M5000 444 810 440 125 4590
(10U)
S2600 disk array 446 536 86.1 28.9 420
S3900 disk array 446 582 86.1 32.54 539
Quidway 390.0 220.0 44.5 3.60 52
AR1220
Quidway 442.0 420.0 44.5 8.45 95
AR2220
Quidway 420 256 43.6 5 15 W (maximum
SRG1220 power
consumption per
device)
Quidway 442 414 43.6 7 31 W (maximum
SRG2220 power
consumption per
device)
KVM (1708A) 447.4 594.1 42.5 15 36
Quidway 442 220 43.6 2.5 20
S3328TP (1U)
Quidway 442 420 43.6 7.8 60
S5328C-EI (1U)
Mecury3600 430 330 44 3 20
Fiber channel 428.8 610.5 43 9.34 84
switch
Sun LTO4 483 641 44.4 9.52 140
VTL 6900 446 585 86.1 22.84 650
N610E-22 600 1000 2200 150, including -
cabinet power distribution
boxes, guide rails,

iManager U2000

(mm) (mm) (mm)
and preinstalled
cables
N68E-22 cabinet 600 800 2200 120, including -
power distribution
boxes, guide rails,
and preinstalled
cables
Table 6-4 Device parameters (ATAE)

(mm) (mm) (mm)
S3900 controller 446 582 86.1 32.54 539
enclosure
S3900 disk 446 412 86.1 19.94 249
enclosure
AT8280 subrack 436 420 619.5 39, excluding 450, excluding
service boards service boards
Service board 30.48 385 322.25 4.8 170
(including
interface board)
Quidway 390.0 220.0 44.5 3.60 52
AR1220
Quidway 442.0 420.0 44.5 8.45 95
AR2220
Quidway 420 256 43.6 5 15
SRG1220
Quidway 442 414 43.6 7 31
SRG2220
KVM (1708A) 447.4 594.1 42.5 15 36
Quidway 442 220 43.6 2.5 20
S3328TP
Quidway 442 420 43.6 8.5 88
S5352C-EI
Mecury3600 430 330 44 3 20
Primary power 442 436 88.9 25 -

iManager U2000

(mm) (mm) (mm)
supply
N610E-22 600 1000 2200 150, including -
power distribution
boxes, guide rails,
and preinstalled
cables
N68E-22 600 800 2200 120, including -
power distribution
boxes, guide rails,
and preinstalled
cables
6.4 Reliability Specifications

The reliability of the U2000 system varies according to the server model and the hardware
configuration.
Table 6-5, Table 6-6, and Table 6-7 describe the specifications for configuring the Sun-based
single-server system, HA system, and SLS system.
Table 6-8 describes the specifications for configuring the RH5885H V3 PC server.
Table 6-9 describes the specifications for configuring the ATAE cluster server.
Table 6-5 Hardware reliability specifications (Sun-based single-server system)
Server Model MTBF (Hour) MTTR (Hour) Annual Mean Availability

Failure Time (Hour)
2 CPU M4000 64776 3.4376545 0.464867472 0.999946933

4 CPU M4000 57110 3.372342 0.51724692 0.999940954
4 CPU M5000 49238 3.3053582 0.588021329 0.999932874
6 CPU M5000 40980 3.3493621 0.715910545 0.999918275
8 CPU M5000 31629 3.3989344 0.941271176 0.999892549
Table 6-6 Hardware reliability specifications (Sun-based HA system)

Failure Time (Hour)
2 CPU M4000 64776 0.61666667 0.083394291 0.99999048

iManager U2000
4 CPU M4000 57110 0.68333333 0.104814015 0.999988035

4 CPU M5000 49238 0.71666667 0.127501292 0.999985445
6 CPU M5000 40980 0.81666667 0.174569484 0.999980072
8 CPU M5000 31629 0.96666667 0.267720801 0.999969438
Table 6-7 Hardware reliability specifications (Sun-based SLS system)

Failure Time (Hour)
2 CPU M4000 50993.76207 0.616666667 0.10593324 0.999987907

4 CPU M4000 38385.24089 0.683333333 0.15594258 0.999982198
4 CPU M5000 32572.64978 0.716666667 0.19273415 0.999977998
6 CPU M5000 26077.96584 0.816666667 0.27432262 0.999968685
8 CPU M5000 20382.88129 0.966666667 0.41542696 0.999952577
Table 6-8 Hardware reliability specifications (HUAWEI PC server)
Server Configuration MTBF (Hour) Annual Mean Failure Availability

Time (Hour)
4 CPU RH5885H V3 76299.6 0.1146667 0.9999869
Table 6-9 Hardware reliability specifications (ATAE cluster system with typical U2000
configuration)
MTBF (Year) MTBF (Hour) MTTR (Hour) Annual Mean Failure Availability
Time (Minute)
44.87 393110 3 4.01 0.9999923
6.5 Compliant Safety Standards

The U2000 complies with the following safety standards:
 IEC 60950-1
 IEC/EN41003
 EN 60950-1
 UL 60950-1

iManager U2000
 CSA C22.2 No 60950-1

 AS/NZS 60950-1
 BS EN 60950-1
 IS 13252
 GB4943
6.6 EMC Specifications

The U2000 complies with the following Electromagnetic Compatibility (EMC) standards:
 CISPR22 Class A
 EN55022 Class A
 EN50024
 ETSI EN 300 386 Serial Class A
 ETSI EN 301 489 Class A
 ICES 003 Class A
 AS/NZS CISPR22 Class A
 GB9254 Class A
 VCCI Class A
 CNS 13438 Class A
6.7 Environmental Requirements

Environmental requirements include the requirements for the storage, transportation, and
operation of the equipment.
The environmental requirements comply with the following standards:
ETS 300019 "Equipment Engineering (EE); Environmental conditions and environmental
tests for telecom equipment"
IEC 60721 "Classification of environmental conditions"
6.7.1 Storage Environment

This section describes the climatic, waterproof, biological, air purity, and mechanical stress
requirements for storing the equipment.
Climatic Requirements
Table 6-10 lists the climatic requirements for equipment storage.
Table 6-10 Climatic requirements for equipment storage
Item Range
Temperature -20°C (-4 ºF) to +60°C (140 ºF)

iManager U2000
Item Range
Relative humidity 8% to 93%
Altitude  5,000 m (16,404 ft.)
Atmospheric pressure 70 kPa to 106 kPa
Solar radiation  1,120 W/s²
Heat radiation  600 W/s²
Wind speed  30 m (98.42 ft.)/s
Waterproof Requirements
The equipment must be stored in a room where:
 Water does not accumulate on the ground or fall on the package.
 Water sources, such as a hydrant and air-conditioner, are placed at a distance.
If the equipment is placed outdoors, ensure that:
 The package is intact.
 Waterproof measures are taken to prevent water penetration.
 Water does not accumulate on the ground or flow into the package.
 The package is not exposed directly to sunlight.
Biological Requirements
Ensure that the place for equipment storage is free of:
 Fungus or mildew
 Rodents, such as rats
Air Purity Requirements

The air must be free of explosive, conductive, magnetic, conductive, or corrosive dust.
The density of physically active materials must comply with the requirements listed in Table
6-11.
Table 6-11 Storage requirements for physically active materials
Physically Active Material Unit Density
Suspended dust mg/m³  5.00

Falling dust mg/m²·h  20.0
Sand mg/m³  300

iManager U2000
NOTE
Suspended dust: diameter  75 m
Falling dust: 75 m  diameter  150 m
Sand: 150 m  diameter  1 000 m
The density of chemically active materials must comply with the requirements listed in Table
6-12.
Table 6-12 Storage requirements for chemically active materials
Chemically Active Material Unit Density

SO2 mg/m³  0.30
H2S mg/m³  0.10
NO2 mg/m³  0.50
NH3 mg/m³  1.00
Cl2 mg/m³  0.10
HCl mg/m³  0.10
HF mg/m³  0.01
O3 mg/m³  0.05
Mechanical Stress Requirements

Table 6-13 lists the mechanical stress that the equipment can endure during storage.
Table 6-13 Storage requirements regarding mechanical stress
Item Subitem Range

Sinusoidal vibration Offset  7.0 mm (0.28 None
in.)
Accelerated speed None  20.0 m (65.62
ft.)/s²
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz
Unsteady impact Impact response spectrum  250 m (820.20 ft.)/s²
II
Static payload  5 kPa

iManager U2000
Item Subitem Range
NOTE
Impact response spectrum: refers to the maximum acceleration response curve generated by the
equipment under specified impact excitation. Impact response spectrum II means that the duration of
semi-sine impact response spectrum is 6 ms.
Static payload: refers to the capability of the equipment to bear the pressure from the top when it is
packed in the normal pile-up method.
6.7.2 Transportation Environment

requirements for transporting the equipment.
Table 6-14 lists the climatic requirements for transporting the equipment.
Table 6-14 Climatic requirements for transporting the equipment
Item Range
Temperature -20°C (-4 ºF) to +60°C (140 ºF)
Humidity 8% to 93%
Altitude  5,000 m (16,404 ft.)
Solar radiation  1,120 W/s²
Heat radiation  600 W/s²
Waterproof Requirements
Before transporting the equipment, ensure that:
 The package is intact.
 Waterproof measures are taken to prevent water penetration.
 There is no water in the vehicle.
Ensure that the vehicle is free of:

iManager U2000

6-15.
Table 6-15 Requirements for physically active materials in the transportation environment

Suspended dust mg/m³ No requirement
Falling dust mg/m²·h  3.0
Sand mg/m³  100
NOTE
Suspended dust: diameter  75 m
Falling dust: 75 m  diameter  150 m
Sand: 150 m  diameter  1,000 m
6-16.
Table 6-16 Requirements for physically active materials in the transportation environment

SO2 mg/m³  0.30
H2S mg/m³  0.10
NO2 mg/m³  0.50
NH3 mg/m³  1.00
Cl2 mg/m³  0.10
HCl mg/m³  0.10
HF mg/m³  0.01
O3 mg/m³  0.05

Table 6-17 lists the mechanical stress that the equipment can endure during transportation.

iManager U2000
Table 6-17 Transportation requirements regarding mechanical stress
Item Subitem Range

Sinusoidal Offset  7.5 mm (0.30 N/A --
vibration in.)
Accelerated speed N/A  20.0 m (65.62  40.0 m (131.23
ft.)/s² ft.)/s²
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz
Random Spectrum density of accelerated 10 m²/s³ 3 m²/s³ 1 m²/s³
vibration speed
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz
Unsteady Impact response spectrum II  300 m (984.24 ft.)/s²
impact
Static payload  10 kPa
NOTE
Impact response spectrum: refers to the maximum acceleration response curve generated by the equipment under specified
impact excitation. Impact response spectrum II means that the duration of semi-sine impact response spectrum is 6 ms.
Static payload: refers to the capability of the equipment to bear the pressure from the top when it is packed in the normal pile-up
method.
6.7.3 Operating Environment

requirements for operating the equipment.
Table 6-18 and Table 6-19 list the climatic requirements for operating the equipment.
Table 6-18 Temperature and humidity requirements for operating the U2000
Temperature Relative Humidity

5°C (41 ºF) to 35°C (95 ºF) 20% to 80%
NOTE
The values are measured 1.5 meters above the floor and 0.4 meters in front of the equipment, without
protective panels in front of or behind the cabinet.
Safe operation refers to continuous operation for not more than 48 hours or operation of not more than
15 days accumulated in a year.

iManager U2000
Table 6-19 Other climatic requirements for the operation of the U2000
Item Range
Altitude  4,000 m (13,123.20 ft.)
Solar radiation  700 W/m²
Heat radiation  600 W/m²
Ensure that the place for storing the equipment is free of:

6-20.
Table 6-20 Operation requirements for physically active materials
Physically Active Unit Density

Material
Dust particles Particles/m³  3 x 104

(Ensure that the dust accumulated for
three days on the desktop is not visible.)
NOTE
Dust particles: diameter  5 m
6-21.
Table 6-21 Operation requirements for chemically active materials
SO2 mg/m³  0.20

H2S mg/m³  0.006
NH3 mg/m³  0.05

iManager U2000

Cl2 mg/m³  0.01

Table 6-22 lists the mechanical stress that the equipment can endure during its operation.
Table 6-22 Operation requirements regarding mechanical stress
Item Subitem Range

Sinusoidal Offset  3.5 mm (0.14 in.) N/A
vibration
Accelerated speed N/A  10.0 m (32.81
ft.)/s²
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz
Unsteady Impact response  100 m (328.08 ft.)/s²
impact spectrum II
Static payload 0
NOTE
Impact response spectrum: refers to the maximum acceleration response curve generated by the
equipment under specified impact excitation. Impact response spectrum II means that the duration of
semi-sine impact response spectrum is 6 ms.
Static payload: refers to the capability of the equipment to bear the pressure from the top when it is
packed in the normal pile-up method.

iManager U2000
Product Description A Acronyms and Abbreviations
A Acronyms and Abbreviations
Numerics
3GPP 3rd Generation Partnership Project
A
ATAE Advanced Telecommunications Application Environment
C
CORBA Common Object Request Broker Architecture
E
EMC Electromagnetic Compatibility
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute
I
IEC International Electrotechnical Commission
L
LTE Long Term Evolution
M
MML Man-Machine Language
MTBF Mean Time Between Failures
MTTR Mean Time To Repair

iManager U2000
Product Description A Acronyms and Abbreviations
N
NMS Network Management System
NGN Next Generation Network
NTP Network Time Protocol
O
OPEX Operation Expenditure
P
PC Personal Computer
R
RTN Radio Transmission Node
S
SLS Multi-Server Load-Sharing
SNMP Simple Network Management Protocol
STP Signaling Transfer Point


IManager U2000 Product Description

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IManager U2000 Product Description

Загружено:

Авторское право:

Доступные форматы

iManager U2000

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2014-05-15) Huawei Proprietary and Confidential ii

3 Products and Application Scenarios ....................................................................................... 14

6 Technical Specifications ............................................................................................................ 32

Issue 02 (2014-05-15) Huawei Proprietary and Confidential iii

6.3 Hardware Specifications ................................................................................................................................ 34

Issue 02 (2014-05-15) Huawei Proprietary and Confidential iv

1.2 NEs Managed by the U2000

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 1

1.2.2 GBSS NEs

1.2.3 SingleRAN NEs

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 2

 Embedded edge router: EER

1.2.5 LTE/EPC NEs

1.2.6 eRelay NEs

1.2.7 SingleDAS NEs

1.2.8 STP NEs

1.2.9 NGN NEs

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 3

 Media switch server: MediaX3600

1.2.10 IMS NEs

1.2.11 SmartCare/SmartPCC Network Devices

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 4

1.2.12 Wireless Bearer Network Devices

1.2.13 Auxiliary Networking Devices

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 5

Powerful Network Management

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 6

optimization of neighboring cell relationships, remote base station commissioning, device

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 7

2.2 Hardware Structure

Figure 2-1 Hardware structure of the U2000 single-server system

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 8

Figure 2-2 Hardware of the ATAE cluster system

Figure 2-3 Appearance of the ATAE subrack

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 9

Table 2-1 ATAE subrack

No. Board Type Description

1 Service It is installed in slots 1 to 6 or 9 to 14. You can install application

Figure 2-4 Appearance of ATAE boards

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 10

2.3 Software Structure

Figure 2-5 Software structure of the U2000 system

2.4 External Interfaces

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 11

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 12

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 13

3 Products and Application Scenarios

Table 3-1 Hardware/networking types

Server Single- HA Remote SLS Emergency ATAE ATAE ATAE

 In Table 3-1, Y indicates support and N indicates not support.

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 14

Table 3-2 describes the application scenarios of the U2000 OM solutions.

Table 3-2 Application scenarios of the U2000 OM solutions

Server Solution Application Scenario

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 15

Server Solution Application Scenario

Sun-based The emergency system has lower hardware requirements

ATAE Cluster Solution

Issue 02 (2014-05-15) Huawei Proprietary and Confidential 16

Figure 3-1 Physical structure of the ATAE cluster system