U2000 O&m

HUAWEI
iManager U2000 Client Application
1
© 2017 Huawei Technologies Co.,Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any means
without prior written consent of Huawei technologies Co., Ltd
Trademarks
HUAWEI, C&C08, EAST8000, HONET, ViewPoint, Intess, ETS, DMC, TELLIN, InfoLink,
Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge,
Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI Optix, C&C08 iNET, NETENGINE, Optix,
SoftX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX are trademarks of Huawei
Technologies Co., Ltd.
All other trademarks mentioned in this manual are the property of their respective holders.
Notice
The information in this manual is subject to change without notice, every effort
has been made in the preparation of this manual to ensure accuracy of the
contents, but all statements, information, and recommendations in this manual do
not constitute a warranty of any kind, express or implied.
2
TABLE OF CONTENT
1. iManager U2000 V200R016 Topology Management
2. iManager U2000 V200R016 Alarm Management
3. iManager U2000 V200R016 Configuration Management
4. iManager U2000 V200R016 Performance Management
5. iManager U2000 V200R016 Log Management
3
U2000 V200R016 Topology Management P-0
Confidential Information of Huawei. No Spreading Without Permission

4

5

6
Topology management is a way to present the topology relationships between NEs, subnets,
and links on a network by graphics. The main functions are as follows: importing data from or
exporting data into a file, setting the background, as well as NE layout and monitored NEs.
Topology management provides the following functions:
Displays NEs and links by subnets. Each subnet can be displayed in a different
topology view.
Customizes topology view, displaying or hiding types of NEs and links.
Queries the information about NEs and links between NEs.
Creates, modifies, and deletes subnets, NEs, links.
Zooms out, zooms in, locks, and unlocks a view.
Sets the background (including an empty background) for a view.
Arranges the objects in the current subnet in good order.
Moves, cuts, and pastes the objects in a subnet.
Filters topology objects by object types.
Supports discovering SNMP NEs instantly or as scheduled.
Monitors the statuses of all devices on the main topology view in a centralized
manner. The main topology view displays the device alarms of all severities and
devices statuses with multiple types of icons, and provides alarm information in tips.
The user can customize the display effect of alarms as required.

7
The topology view provides the function of displaying RNC pool topology. The
RNC pool is a disaster tolerance mechanism that is implemented by configuring
two RNCs for one NodeB to prevent system breakdown caused by an RNC fault.
In the Inter-RNC pool, you can specify the primary RNC and the secondary RNC
for a NodeB. Generally, the transport links are configured between the NodeB
and the primary RNC. When a fault occurs on the primary RNC, the secondary
RNC automatically takes over the services of the NodeB to ensure that the
NodeB services are running properly.
The topology view configures dual maintenance channel NEs and uses different
icons to identify the connection modes. Dual maintenance channel indicates that
one NE has two IP addresses. Currently, only the NodeB/eNodeB/BTS3900
supports dual maintenance channel.
The NE can be connected to the network when either of the IP addresses are
reachable. Therefore, when an NE is disconnected, U2000 automatically
switches between the two IP addresses to ensure network communication. If both
IP addresses are valid, U2000 preferentially uses IP address 1.
The dual homing topology view can be used to monitor the alarm statuses of the
devices on a dual homing network.
Pool topology can be used to monitor the alarms of the pool network and the NEs
in the pool network and check the load balance of the pool network.

8
The signaling topology view can be used to monitor the status of signaling links
and DSPs. You can search for an object, filter objects, and report alarms about the
objects in the topology view.
Confidential Information of Huawei. No Spreading Without

Permission
9
(1)Topology navigation tree: Displays the hierarchy of the objects on the topology view.
You can precisely locate the objects on the topology view through the topology
navigation tree.
(2)Current view type: You can select views through the list box beside Current View,
including Physical Root, Electronic View, BSC Pool View, RNC Pool View, RNC in Pool
View, Core Network Pool, Core Network MME Pool, Multimode Base Station View,
NetEco View, GBTS Group View, and Signaling Network View.
(3)Topology tool bar: The shortcut icon on the topology tool bar can be used to perform
operations easily and quickly on the physical topology.
(4)Physical topology view: Displays all the networks managed by U2000 in a map.
(5)Extend Apply: You can click the icon on the toolbar to select lists to be displayed,
including Browse Current Alarm, Cell List and Monitor RNC in Pool.

10
Subnet
On U2000, a large network can be divided into several smaller networks based on a specific rule
(for example, by region), for the convenience of network management. On U2000, these smaller
networks are called subnets. Subnets are located in the physical view and electronic map.
NE
NEs are used to identify concrete entity devices, such as switches and routers. NEs can be
grouped into physical NEs and virtual NEs.
Physical NEs are the Huawei Technologies Co., Ltd. communication devices that exist in the
network. The physical NEs can be managed by U2000.
Virtual NEs are the communication devices that do not truly exist or devices that do not belong to
Huawei Technologies Co., Ltd.. You cannot manage the virtual NEs by U2000, but you can add
the existing virtual NEs to the physical view, and know the entire communication network.
Link
A link is used to identify the physical or logical connection between two topological nodes in the
topology view. It is the general name of connections in the topology view and includes physical
links, optical fibers, and service paths or virtual connections between two nodes. Including
physical links and virtual links.
A physical link indicates that there actually exits physical connection between physical NEs,
subnets, and a physical NE and a subnet. A virtual link refers to the logic link between NEs
(including physical NEs and virtual NEs), subnets, and an NE and a subnet.

11
Physical subnets reflect the network hierarchy in the topology view. Setting up physical
subnets properly can improve the visibility of the communication network and operability
of U2000. Setting up a physical subnet involves the operations such as designing a
physical view and creating subnets, NEs, and links.

12

13
Before deploying NEs in a physical topology view, you need to design the view. The
physical topology view should clearly reflect the actual communication network structure
to facilitate routine maintenance and operations.
The topology management window consists of a navigation tree on the left and a
topology view on the right. The navigation tree displays all the topology objects and their
hierarchical relationships in a tree, and the topology view displays all the topology
objects and their positions in the physical topology view.

14
By setting the background for the specified subnet or container NE, you can view the
positions of the topology objects under the subnet or container NE in a distinguished
manner.
On U2000, only the image files in the formats of .gif or .jpg can be imported, and the file
size cannot exceed 1 MB.
Container NEs refer to multi-subrack devices on a network. NEs in a container NE refer
to boards in subracks of a multi-subrack device. If a subrack of a multi-subrack device
has multiple boards, the subrack is also a container NE. In other words, container NEs
can contain container NEs. Container NEs provide the same functions as subnets and
common NEs do except that: Container NEs do not allows NEs to be moved in or out,
but subnets allow.
Container NEs provide some functions of subnets, but common NEs do not.

15
You can create a subnet in the physical view or on the electronic map and add NEs to
the subnet to facilitate management.

16
The recommended number of objects (including NEs and subnets) deployed in the same
subnet is not more than 500; otherwise, the performance may be reduced, especially in
low bandwidth of the network.

17

18
U2000 categorizes network devices according to their home networks.

Bearer network
Router series include: AR46, Eudemon1000, Eudemon200, Eudemon500,
NE08E, NE16E, NE40E, NE80E, NE5000E, CX600 and ATN
Switch series include: S2000, S2000B, S3000, S3328, S3500, S5328, S5500,
S8500, and S9300
Security NE series include: Eudemon, SIG, and SVN
Optical network transmission devices. The series include: RTN310, RTN380,
RTN605, RTN610, RTN620, RTN905, RTN910, RTN950, RTN950A, RTN980,
RTN910(NA) and RTN950(NA)
Domain name server DNS
Access network
GSM & UMTS: BSC, PCU, RNC, NodeB, BSC6900 GSM, BSC6900(GSM-R),
BSC6900 UMTS, BSC6910 GSM, BSC6910 UMTS, BSC6000(GSM-R), and
GSM-R BTS, and GBTS
CDMA: CBSC and CBTS (3606 and 3612)
RASYS: RAC and RAU
WiMAX: WiMAX BTS (including BTS3701B, BTS3702C, BTS3702E, and

19
DBS3900 WiMAX)

Permission
20
LTE: eNodeB
SingleRAN: BTS3900, MICRO BTS3900, MBSC, and PICO BTS3900
Other networking devices: TGW, DCU, IP Clock Server (ICS), eRelay, and
ECO6910, USU, SVA-AE, DBS3900 IBS
Core network
GSM&UMTS: SGSN, UAG, GGSN80, SIG, DNS9816, CG, RADIUSProxy,
MSCServer, SigProbe, SigProbeTDM, EER, GUHLR, UEIR, UNP, UIM,
CGPOMU, USCDB, RM, UPCC, ENS, FMCMGW, MGW, iGWB,SG7000, SPS,
HSS9860, UPA
CDMA: PDSN, HA, MSCe, RCC, CHLR9820, CGPOMU, USCDB, RM, UPCC,
AAA, AAAOMD, AAABMP, ATAEHardware, MGW, FMCMGW, SG7000, iGWB
WiMAX: ASNGW, AAA, AAAOMD, AAABMP, ATAEHardware
IMS: CGPOMU, CSCF, ATS, AIM, IPCTRX, MRFP, CCF, MEDIAX, UGC, ENUM,
SPG, OSG, PGM, CSE, ViewPoint, MRMU, Mediation, MRFC, AGCF, CAS9910,
SE2600, USCDB, RM, UPCC, HSS, FMCMGW, SBC, ENS, SoftX3000, RCS,
RCS9880, RCS9880BMP, ATAEHardware, TMS, SVN, UGW9500, NRS
EPC: USN, UGW, CG, UCGPOMU, USCDB, RM, UPCC, SAE-HSS, SPSV3,
HSS9860
NGN: STP, SHLR, SoftX3000, MEDIAX, SG7000, SPS, SBC, iGWB, FIXMGW,
MiniMGW, MRS6100
Common: GenexCNNastar
Others
AAA
Security Gateway
HA
Third-party server

21
NE Creating NEs Creating NEs in Creating NEs Creation Mode

One by One Batches in Batches
(Automatic Search (Template
Mode) Mode)
NodeB, BTS3900 √ √ √ •Creating NEs in batches (automatic
search mode): U2000 creates
NodeBs/BTS3900s managed by the
base station controller by using
automatic detection. After being created,
the NodeBs/BTS3900s can be operated
and maintained on U2000.
GBTS - √ - No manual intervention is required for

creating physical GBTSs. U2000
automatically searches for them. If
GBTSs exist under a base station
controller, U2000 automatically creates
these GBTSs when it synchronizes the
controller information.
SNMP device √ √ √ •Creating NEs in batches (automatic

search mode): U2000 can create SNMP
devices in batches by searching for
SNMP devices based on the IP
addresses of the SNMP devices or the IP
network segment that the SNMP devices
are located.

22
eGBTS must be created under their controller NEs, such as BSC6900 GSM, BSC6900
GU, BSC6910 GSM and BSC6910 GU, to which eGBTS belongs.
NodeBs must be created under their controller NEs, such as RNC, BSC6900 UMTS, and
BSC6900 GU, to which NodeBs belongs.
After an NE is created, it is displayed in the topology navigation tree and topology view.
At the same time, U2000 automatically synchronizes NE configuration data. If the NE is
in an abnormal status, U2000 displays an NE status icon to the upper-left of the NE icon.
Typical NE status is as follows: :
indicates the NE and U2000 server are disconnected. In this case, you need to
check whether the connection between the NE and U2000 is normal or whether
the IP address of the NE is correctly set.
indicates the NE has not been configured or the NE version does not match
the mediation version installed on U2000 server. In this case, you need to check
whether the NE is correctly configured or whether the matching mediation version
is installed.

23
U2000 does not support the batch creation of virtual NEs.

If the type of the new NE is NodeB, a virtual or physical RNC must be selected as the
subnet where the new NE is located.

24
Procedure
Open the Batch Create Topo Objects dialog box.
Choose Topology > Main Topology (traditional style); alternatively, double-click
Topo View in Application Center and choose Topology > Main Topology
(application style) . The Main Topology window is displayed.
In the topology navigation tree or physical topology view, right-click the subnet of
the NE or a base station controller to be created, and choose Batch > Create
Topo Objects from the shortcut menu. You can also right-click in the topology
view and choose Batch > Create Topo Objects from the shortcut menu.
Export the script file template for creating NEs in batches.
Select the NE node under the Batch Create node from the navigation tree of the
Batch Create Topo Objects dialog box.
In the right Export Template pane, select INI File or CSV File, and then click
Export.
In the Export NE Info Template window, select By NE type or Specified NE,
specify a file save path, and click OK.
If you select By NE type, information about multiple NE types in a file can
be exported simultaneously using the template in INI format, but
information about only one NE type can be exported using the template in
CSV format.

25
If you select Specified NE, only information about one or multiple NEs of
the same type can be exported using the template in CSV format..

Permission
26
Enter the information about NEs to be created in the exported script file template
Create physical NEs in batches.
In the right pane of the Batch Create Topo Objects dialog box, select a script
file.
Click Verify to check the configuration of the script file. If any error occurs on the
configuration, correct the error by referring to Template Verify Information.
You can select Stop Creating in Case of Errors according to the actual
requirement.
Click OK to start creating NEs. The Create NE Progress dialog box is displayed,
showing the progress of NE creation and results.
Click Close to close the Create NE Progress dialog box.

27
This section describes how to enable U2000 to automatically detect and create
NodeBs/BTS3900s. After a specified controller for NodeBs/BTS3900s, such as the RNC,
BSC6900 UMTS, BSC6900 GU, and BSC6900 GSM, has been created in the topology
view, U2000 synchronizes the information about the NodeBs/BTS3900s managed by the
controller by using the automatic detection function, and automatically creates the
NodeBs/BTS3900s. Then, you can perform operation and maintenance on the
NodeBs/BTS3900s on U2000 client.
Prerequisites
The controller managing NodeBs/BTS3900s has been created and
communicates with the U2000 server properly.
The NodeB/BTS3900 mediation software has been installed.
Check whether the relay server of the controller managing NodeBs/BTS3900s
has been configured properly. See Configuration Management course for details.

28
You need to manually create the MTP3Link, MTP3BLink, DataLink, FiberLink, and
MicroWaveLink, which cannot be automatically created by the system.
Procedure
Choose Topology > Main Topology (traditional style); alternatively, double-click Topo
View in Application Center and choose Topology > Main Topology (application style) .
The Main Topology window is displayed.
Use either of the following methods to create a physical link in a topology navigation tree
or physical view:
Create a physical link.
Right-click the subnet node in the topology navigation tree or on the
topology view, and then choose New > Link.
Under in the navigation tree, select a specific link type.
Configure link information.
Create physical links in Batches.
Right-click the subnet node in the topology navigation tree or the topology
view, and select Batch Create Topo Objects.
Choose Batch Create > Link in the navigation tree in the left pane.
Click Add in the right pane.

29

30

31
The NE reconnection states are described as follows:

Enable connection: When an NE is disconnected from U2000 server, U2000
attempts to reconnect to the NE. By default, new NEs are set to enable
connection.
Disable connection: When an NE is disconnected from U2000 server, U2000
does not attempt to reconnect to the NE.

32
NodeBs may be in the disconnected state because they are deleted or reparented.
Therefore, you need to determine the reason why the NodeBs are disconnected before
performing the related operation such as deleting, reconnecting, and waiting for the
NodeBs to be reparented.

33
You can monitor the status of cells in the topology view only for GSM, UMTS, and LTE
network elements (NEs). The cell display entry is unavailable for NEs of other radio
access technologies (RATs).
Currently, this function applies to GBTSs, separate-MPT base stations, NodeBs, and
eNodeBs in compatible with GBSS13.0, WRAN13.0, eRAN2.1, and later versions.

34

35
You can select the style for displaying the client: Application style which is new style and
displaying all the applications on the client or Traditional style which is the old one that
you used to see and use in the previous U2000 versions.

36
You can customize some settings on topology such as the background color, Node icon,
Node Label and etc. here.

37

38

39

40

41

42
U2000 V200R016 Alarm Management P-1

43

44

45

46
You can choose the style you prefer in Preferences window under file menu .
In this course, we will use the application style and you can try another style if you are
interested in it.

47

48

49
To recover system services, fault alarms must be properly handled.

Events occur all the time, which have no negative impact on system running and do not
need intervention.

50
The handling policies for different alarms are different, depending on the severity of the
alarms. U2000 provides the function of redefining alarm severity. Using this function, you
can redefine the severity of an alarm. For example, a large quantity of critical alarms
(alarm M) are generated during the upgrade of NE Z. If alarm M can be ignored, you can
redefine alarm M as a warning alarm.

51
The status change of an alarm is triggered when certain preset conditions are met.

52
Alarms are classified into ADAC and ADMC alarms in terms of automatic alarm
clearance.
ADAC indicates that the U2000 reports a clear alarm after automatically detecting
rectification of the fault related to a fault alarm, and the fault alarm is
automatically cleared.
ADMC indicates that the U2000 does not report a clear alarm after automatically
detecting rectification of the fault related to a fault alarm, and the fault alarm is
manually cleared or is wrapped around and cleared after being dumped to the
historical alarm library.

53
Technical Specifications for Alarm Management

Function Specification Value
Category
Current alarm Maximum number of alarms in the Sun/HP:100,000
current alarm list ATAE:200,000
Storage limit When the total number of alarms in the current alarm list
reaches the limit, 10% of them, which are the earliest, are
deleted from the list.
Life cycle of a current alarm (After how The value is 0 by default. The alarms that have been
many days the alarms in the current acknowledged and cleared will be deleted from the current
alarm list will be deleted) alarm list.
Alarm logs Total number of alarm logs •Sun Netra240: 1,040,000
•Sun M4000: 12,580,000
•Sun M5000: 12,580,000
•ATAE (400/1200/1600/2000/3200 equivalent NEs):
12,580,000
•Virtual (400/1200/1600/2000/3200/4000 equivalent NEs):
12,580,000
Storage duration of an alarm log list (unit: 90 NOTE: The value ranges from 1 to 90.
day)
Event logs Total number of event logs •Sun Netra240: 1,040,000
•Sun M4000: 12,580,000
•Sun M5000: 12,580,000
•ATAE (400/1200/1600/2000/3200 equivalent NEs):
12,580,000
•Virtual (400/1200/1600/2000/3200/4000 equivalent NEs):
12,580,000
Storage duration of an event log list (unit: 3
month)

54
Technical Specifications for Fault Monitoring

Alarm display Maximum length of an alarm location •750
information record (unit: byte)
Intermittent Intervals for intermitted alarms and 0 to 60. The default value is 10.
alarms/repetitive repetitive events (unit: second)
event correlation Number of times faults are intermitted 2 to 6000. The default value is 5.
or events are repeated
Root Maximum number of root alarms A maximum of 10 root alarms and subalarms can be
alarms/subalarms set in a rule.
Maximum number of subalarms A maximum of 10 root alarms and subalarms can be
set in a rule.
Maximum number of correlation rules 300
Analysis period (unit: second) 2 to 60. The default value is 10.

Custom environment Range of IDs that can be used for 65334 to 65533, 65033 to 65233
alarms customizing environment alarms
Scheduled alarm Scheduled acknowledgment period 0 to 30. The default period is one day, and the value
acknowledgment (unit: day) can be configured.
Default scheduled acknowledgment The default time is 01:00, and the value can be
time configured.
Scheduled alarm Scheduled synchronization period 1 to 366. The default period is one day, and the value
synchronization (unit: day) can be configured.
Alarm file export Export period (unit: day) 1 to 366. The default period is one day, and the value
can be configured.
Alarm supplementary Maximum number of lost alarms that All alarms collected after the NE and U2000 are
collection can be automatically retrieved disconnected. The default value is 5000. You can set
0 to 100,000 alarms.

55
Technical Specifications for Fault Monitoring(cont.)
Alarm report delay Delay for reporting alarms (unit: second) 5

Maintenance mode Types of customized maintenance modes 10
management (unit: type)
Alarm/Event name Maximum number of alarm IDs that can be 2000

group management added to a name group
Maximum number of name groups that can 100
be created
Object group Maximum number of alarm 10000
management sources that can be added to a
name group
Maximum number of name 100
groups that can be created
Remote Maximum number of objects that can be 2000
Alarm/Event monitored concurrently
Notification

56

57

58

59

60
The filter modes are as follows:

MBTS: Multiple BTS.
MO: A specific MO, such as a subrack, slot, cell, link, RRU and so on..
Object Group: Multiple NEs will be selected if an object group is
selected.
Maintenance Region: NEs within a maintenance region.(By setting
maintenance regions, you can divide NEs based on maintenance regions.
Values of Details for alarms contain information about maintenance
personnel, which helps maintenance personnel understand alarm status
of devices within their maintenance scopes and promptly handle alarms,
Each NE belongs to only one maintenance region, Maintenance regions
cannot be nested, The user can add only visible NEs to maintenance
regions. Choose Topology Management > File > Maintenance Region
Management (application style) or Maintenance > Maintenance Region
Management (traditional style))

61
The attributes are as follows:

Time type: Query alarms by the server time.
Location information: Where the alarm occurred.
List Serial Number: serial number of an alarm in the alarm list.
Identifier: Set whether alarms are filtered by identifier. Identifiers are icons such
as displayed in the first column of the alarm table to identify special alarms
or events.(Remarks, Intermittent Alarm, High Frequency Intermittent Alarm,
Toggling Alarm can be selected).
Common Alarm Identifier(To set whether common alarms are filtered. This
parameter is valid only for multimode base stations and for history alarm and
alarm log query).
Acknowledgment time: time when an alarm is acknowledged.
Additional information: Set if some additional information is included.

62
Common query or statistic criteria can be saved as templates. The templates can be
used directly when you need to query or collect statistics on alarms or events by the
same criteria.
Monitor template: It is used for the alarm indicators in the upper right corner on the
U2000 client GUI to display the statistics of alarms of different severities. It must be the
current alarm browse templates.
Shared template: Shared templates are visible to all users.
Startup template: It opens automatically when a user logs in to the client. A maximum
of five auto loaded template can be set.
Default template: It is used when the corresponding functional window is opened. Each
functional window corresponds to a default template.

63
Occurrence times: Quantity of merged alarms. It records the number of times that same
alarms are reported to draw users' attention and improve efficiency.
Select Show latest alarms to refresh alarms displayed in the window in real time.
Select Scroll lock to keep the alarms displayed in the window unchanged.
Intermittent alarm.
High-frequency intermittent alarm.
Correlative alarm.
Root alarm.
Toggling alarm.
Indicates that the alarm message has remarks.
Indicates that the U2000 has sent the remote alarm notification by email or short
message.
Repeat event, which is converted into an ADMC alarm.
High-frequency repeat event, which is converted into an ADMC alarm.

64

65
Name: Name of an alarm. You can know what fault occurs on the alarm source by alarm
name.
Reason and Advice: Possible causes and troubleshooting suggestions of an alarm
provided in the Online Help. These information helps you identify and rectify faults
quickly.
MO Name: Refers to the name of the managed object (MO) that generates alarms.
List Serial Number: Serial number of an alarm in the current alarms.
Log Serial Number: Serial number of an alarm in the alarm log. The log serial number is
the keyword of an alarm. A log serial number corresponds to a unique alarm.
Equipment Alarm Serial Number: Serial number of a device where an alarm is generated.
Associated Alarm Group ID:ID of the associated alarm group which contains a specified
alarm.
Experience: Handling experience on an alarm.

66
Click the buttons 1, 2, 3, and 4 to open or close the panels corresponding to the numbers

67
Click the buttons 1, 2, 3, and 4 to open or close the panels corresponding to the numbers

68
You can learn about the number of alarms of specified severities on NEs using the alarm
panel on the U2000 client.
Choose Browse Alarm > Display Alarm Panel (application style) or Monitor > Display
Alarm Panel (traditional style) or click the icon on the toolbar to open the alarm panel.
Choose System > Preference > Alarm Local Terminal Setting to modify the display styles
for alarms.
The alarm panel displays alarm information according to the preset template which is the
monitor template, you can add a current alarm template to the alarm panel if you want to
monitor the alarms of specified severities on NEs.
After you set the alarm display in the topology view, when the devices in the network
generate alarms, the alarms of the highest severity will be displayed on the corresponding
topology objects in the topology view. This helps you learn about the device faults timely.

69

70
U2000 provides the function of locating the NE that generates an alarm or event in the
topology view based on the alarm or event record. Using this function, the positions of
faulty NEs on the live network can be located.

71

72
Each clearance alarm maps an alarm. When the equipment becomes faulty, an alarm is
generated. When the fault is rectified, a clearance alarm is generated, and the original
alarm is cleared.

73
If the network has been interrupted, the alarm data on U2000 may be inconsistent with
that on the NEs. To learn the actual alarms on the NEs, you can manually synchronize
the alarm data from the NEs to U2000.

74

75

76
The window for Query alarm logs is similar to that for Query the alarm list.
The period of the alarm logs needs to be set. By default, the alarm logs of the latest
three days can be queried. Query all alarm logs is forbidden.
In the Query Alarm Logs window, you can query logs of all alarms, which include
alarms in the current and historical alarm lists.

77

78

79

80
Alarms that have been acknowledged and cleared and whose life cycle end are historical
alarms. All the other alarms are current alarms.

81

82
By collecting statistics on alarms and events, you can detect network faults and gather
network information to improve network quality.
Statistic Row: The rows of the statistic result table can be set in this area. A maximum
of three tiers of rows can be selected. The final statistic results will be listed as set.
Tier-1, tier-2, and tier-3 statistical items:
Available statistical items for alarm logs are NE, NE type, Name, Severity, Type, Status,
By month, By day, By hour, Link, Link type.
Available statistical items for event logs are NE, NE type, Name, Severity, Type, By
month, By day, By hour, Link, and Link type.
Statistic Column: For statistical results displayed in a table, this parameter is used to
set column headers of the table.
Available statistical items for alarm logs are (Count), NE Type, Severity, Type, Status, By
Hour, Link Type.
Available statistical items for event logs are (Count), NE Type, Severity, Type, By Hour,
and Link Type.

83

84
Save the result

85

86

87
The alarm panel refers to a shortcut icon and four color blocks on the upper right of the
toolbar of U2000 client. Each color block indicates an alarm severity. The number in
each color block indicates the alarm quantity of the corresponding severity on U2000.
When a new alarm is reported, the color block of the corresponding severity will blink.
You can learn whether a new alarm is reported, the severity of the new alarm, and the
statistics on the alarms of each severity in the alarm panel.

88
The alarm panel is a client window. You can click Add below Alarm Panel to bind an
alarm list template and Alarm Panel. In this case, Alarm Panel displays the alarm
statistics of the bound template in real time based on the alarm status and alarm
severity.

89
On the Query Alarm Bar Chart tab page, a bar chart is provided for users to learn the
statistics of the corresponding alarm list template through figures and numbers.
By default, U2000 provides the bar chart of all objects. This bar chart monitors all alarms
in the alarm list and cannot be deleted.
Locate a bar chart to the current alarm: Select one bar chart, and then click Locate to
Current Alarm to display the Browse Current Alarm window.

90

91
When you check the alarm, you are comparing one or more unclearred alarms on the
U2000 with those on the NE. You can check alarms to ensure that the selected alarms
on the U2000 are the same as the alarms on the NE.
If the selected alarms include cleared alarms, the U2000 ignores the cleared alarms and
processes only unclearred alarms.
If the NE generates this alarm, the alarm on the U2000 is in the uncleared state. If the
NE does not generate this alarm, the alarm on the U2000 is in the cleared state.

92

93

94
To facilitate maintenance, U2000 provides the functions of automatically acknowledging

cleared but unacknowledged alarms by severity or preset rules.

95
1. Select Rule.
2. Click Add….
3. In the Add Acknowledgment Rule dialog box, set the acknowledgment rules,
acknowledgment mode, remarks, and whether to enable the rules, and click OK.
4. Set the acknowledgment delay in the Auto Acknowledge (Server Setting) area.

96
An NE object group is a set of NEs.

NE object groups can be used as a type of user-defined alarm or event source. Multiple
NEs will be selected when an NE object group is selected.

97

98
On U2000 client, you can set the monitoring template, startup template, and default
template for the current user.

99
On U2000 client, you can set the monitoring template, startup template, and default
template for the current user.

100
You can set alarm masking rules to mask the alarms that can be ignored.

101

102
Set the start time, end time, and duration of mask rules.

103
Set the start time, end time, and duration of mask rules.

104
If an alarm needs more attention or can be ignored, you can set alarm redefinition rules
to adjust the severity of the alarm.
When the alarm is reported to U2000, U2000 displays the alarm according to the
redefined severity.

105
You can set the communication parameters for remote notification on both the remote
notification client and the integrated client.
The sending devices include: Email, GSM Modem, CDMA Modem, and SMS
Gateway(SMS Center). In Email type, U2000 server must communicate with the email
server properly. In the other types, SMS are sent to users. U2000 supports the
WMOD2B GSM/GPRS Modem and TD-8022R Modem.
When the type of the sending device is modem, if you select a server, you need to install
a modem correctly on the server. Then you can send short messages from any client of
this server after setting the modem parameters. If you select a client, you need to install
a modem on the specified client. Then you can send remote notification through short
messages from this client only.

106
The default number of the SMTP port is 25. Ensure that the SMTP port on the Email
server is available.
GSM Modem, CDMA Modem, and their related parameters are displayed in the Device
Name drop-down list in the Add Communication Device dialog box on the integrated
client only when U2000 runs on a 32-bit server.

107
Communication parameters can be set on the remote notification client or an integrated

client.

108
By setting alarm/event remote notification rules, you can set the conditions, time, and
mode of remote notification.

109
Communication parameters can be set on the remote notification client or an integrated

client.

110
Notification conditions include the alarm name and alarm severity of the remote
notification. The notification time determines when the remote notification is to be sent.
The notification mode is used to set the Email address and mobile phone number of the
receiver.

111
Notification conditions include the alarm name and alarm severity of the remote
notification. The notification time determines when the remote notification is to be sent.
The notification mode is used to set the Email address and mobile phone number of the
receiver.

112
The cell phone number must contain the country code, such as +8613800755500.

113
This function can convert an event into an ADMC alarm and display the alarm in the
alarm list to call your attention to the event.
After the event is converted into an ADMC alarm, the alarm is only displayed in the alarm
list. After the setting is canceled, the alarm is no more displayed in the alarm list.

114
Set the storage duration of acknowledged and cleared alarms in the alarm list.
When the earlier one of the acknowledgment time and clearance time of an ADAC alarm
exceeds the preset value or the acknowledgment time of the ADMC alarm exceeds the
preset value, the alarm will be deleted from the alarm list.

115
Maintenance Mode alarm: During network deployment, expansion, upgrade, or

commissioning, NE services may be affected for a short period of time due to
engineering operations, and alarms will be reported. Usually, large quantities of alarms
of high severity are reported, which are caused by resetting, switchover, communication
link interruption. These alarms will be automatically cleared after the operations are
complete. To prevent these alarms from affecting normal network monitoring, U2000
defines all alarms reported during engineering operations as maintenance mode alarms
and provides a dedicated mechanism for handling these alarms.

116
NE Maintenance Mode indicates whether engineering operations are being performed

on an NE and what kind of engineering operations are being performed. When an NE is
in maintenance mode, the system starts the mechanism for handling maintenance mode
alarms. When an NE is in NORMAL state, no engineering operation is being performed
on the NE.
After the maintenance mode alarm feature is enabled, the NE marks the alarms
generated in different maintenance modes as common or maintenance mode alarms
based on the maintenance mode settings. U2000 identifies the marks of the alarms and
handles the maintenance mode alarms by using the dedicated mechanism. By default,
maintenance mode alarms are not displayed. You can set special filter criteria to monitor
them.

117
The procedure for Query maintenance mode alarms is as follows: Choose Browse
Alarm > Browse Current Alarm. Click Filter…, in the Filter dialog box, there is a
Maintenance Status area and set the relevant parameters.
If Maintenance Status is set to NORMAL, maintenance mode alarms cannot be
queried.

118

119
In networks, physical or logical correlations exist between devices. A fault may cause
repetitive and non-root alarms that are not important for reference. By alarm correction,
U2000 can shield repetitive or non-root alarms so that you can obtain useful alarm
information.
Correlated alarms indicate that the causes of these alarms are correlated. One alarm
has the root cause for the other alarms.
Correlative alarms affect fault identification or analysis by the maintenance personnel.
Therefore, on U2000 you can set a correlation rule based on the alarm features such as
the alarm generation time and physical location, to discard the correlative alarms that
meet the rule, set to a correlative alarm, or decrease the alarm severities.

120
U2000 carries out the correlation rule of higher severity, and then the rule of lower
severity. When the severities of two correlation rules are the same, U2000 carries out
them according to the sequence in which they are loaded to the correlation analysis
template.

121

122
1.Set a root and a correlative alarm and its actions, as in picture 1.

Correlative alarm of can be one or more. It is suggested that the number of root
alarm and correlative alarms are not more than 4.
When the time interval of the occurrence time of the root alarm and its correlative
alarms is less than the analysis period set in picture 3, the actions set to both
alarms in picture 1 will be done to both alarms. For root alarm, raise level and
none can be chosen, for correlative alarms, redefine level, set to a correlative
alarm and discard can be chosen.
When set to a correlative alarm chosen, the alarms filled in the correlative
alarm field will be set as the correlative alarm of the root alarm, and not display
when you browse the alarm list until you tick the display correlative alarm
option in the filter.
2. Set the advanced conditions for the correlation rules.
Click property button, choose properties for root alarm and its correlative alarms
in picture A. For example, choose NE property for the former and generation
time property for the latter.
Then click value… to set the value of those properties by using either of the
following methods:

123
Alarm: Select an alarm in the alarm list, as in picture B. This alarm has the
specified relationship with the alarm described in Property.

124
1.Set a root and a correlative alarm and its actions, as in picture 1.

Correlative alarm of can be one or more. It is suggested that the number of root
alarm and correlative alarms are not more than 4.
When the time interval of the occurrence time of the root alarm and its correlative
alarms is less than the analysis period set in picture 3, the actions set to both
alarms in picture 1 will be done to both alarms. For root alarm, raise level and
none can be chosen, for correlative alarms, redefine level, set to a correlative
alarm and discard can be chosen.
When set to a correlative alarm chosen, the alarms filled in the correlative
alarm field will be set as the correlative alarm of the root alarm, and not display
when you browse the alarm list until you tick the display correlative alarm
option in the filter.
2. Set the advanced conditions for the correlation rules.
Click property button, choose properties for root alarm and its correlative alarms
in picture A. For example, choose NE property for the former and generation
time property for the latter.
Then click value… to set the value of those properties by using either of the
following methods:

125
Alarm: Select an alarm in the alarm list, as in picture B. This alarm has the
specified relationship with the alarm described in Property.

126
Value: Select an NE or NE type, Or enter the generation time, location

information, and additional information of an alarm, as in picture C.
In this case, set UMTS Cell Unavailable--22202-(correlative).NE as the NE

property of the root alarm E1/T1 Loss of Signal--21201-(root), set = as the
operator, then the correlation will display in the correlation description, as
in picture 2, which means the NEs of these two alarm should be equal. Then
set generation time of the correlative alarm UMTS Cell Unavailable--22202-
(correlative).NE is later than the root alarm E1/T1 Loss of Signal--21201-
(root)’s.
3. Set the correlation analysis period, priority and memo.
Analysis period is the time interval within which the root alarm and correlative
alarm should occur so that the correlation rules can work.
Alarms which reported to U2000 will be analysed by all the correlation rules one
by one according to its Priority in pic 3. If two correlation rules have the same
priority, U2000 performs the actions at random.
Enable the correlation rule checkbox need to be ticked to enable this function.

127

128
Handling Policy including

Change the alarm severity. For example, if Time segment is set to 5, Alarm
count is set to 3, and change the alarm severity to Critical, then the severities
of the 4th and later alarms in 5 minutes are changed to Critical.
Generate OMC alarms. When the number of alarms generated in Time segment
is larger than the value of Alarm count, an avalanche alarm is generated to warn
the maintenance people. When the number of alarms generated in Time
segment is less than the value of Alarm count, U2000 clears the avalanche
alarm.
Mask and generate OMC alarms. The same as the above, besides, the alarms
which meet the rule will be masked.
Generate toggling alarms. Toggling alarm is the alarm that is trigger by U2000
system When the number of one kind of alarms generated in Time segment
larger than the value of Alarm count, its name is the same as the previous alarm
and‘Identifier=Toggling Alarm’information will be added in its location information
when it generates . The icon of the toggling alarm is .When the number of
alarms generated in Time segment is less than the value of Alarm count,
U2000 clears the toggling alarm.

129

130
Suppose T1 to T12 <=10s, T13 > 10s, U2000 will generate a E1/T1 Loss of Signal alarm
for MSC at t1 whose level is Critical and this alarm will clear at t2.
The first alarm is saved to fault alarm current table and the 2-12 alarms are abandon

131
After the rules for analyzing the time of acknowledged but uncleared alarms are set,
U2000 can adjust the severity of the alarms that are acknowledged but uncleared for a
long period of time and handle them properly.

132
Technical Specifications for Fault Monitoring(cont.)

Current alarm Maximum number of objects that can be monitored A maximum of 5000 alarm sources can be selected. If this
browse concurrently criterion is not set, alarms of all NEs are monitored.
Maximum number of concurrently opened browse A maximum of 20 windows for Query, browsing, and
windows collecting statistics about alarms/events can be concurrently
opened on a client.
Maximum number of alarms that can be 50,000
concurrently viewed on the GUI
Alarm log Maximum number of objects that can be queried A maximum of 5000 alarm sources can be selected. If this
query concurrently criterion is not set, alarms of all NEs are queried.
Maximum number of concurrently opened query A maximum of 20 windows for Query, browsing, and
opened on a client.
Maximum number of alarm logs that can be 20,000
Event log Maximum number of objects that can be queried A maximum of 5000 alarm sources can be selected. If this
query concurrently criterion is not set, alarms of all NEs are queried.
Maximum number of concurrently opened query A maximum of 20 windows for Query, browsing, and
opened on a client.
Maximum number of event logs that can be 20,000
Alarm browse Maximum number of objects that can be queried A maximum of 5000 alarm sources can be selected. If this
by status concurrently criterion is not set, alarms of all NEs are monitored.
Maximum number of alarms displayed in the alarm 50,000
window that consists of four subwindows
Maximum number of alarms displayed in each 50,000

subwindow when alarms are reported in real time

133

134

135

136
On U2000, you can set rules for redefining the severity of an alarm or mask an alarm at
the NE side.

137

138
After the severity of the alarm is redefined on U2000, the NE reports the alarm according
to its new severity to U2000.

139
The attributes of user-defined alarms are stored in U2000 databases. You can query the
information about the user-defined alarms in the current database. User-defined alarm
attributes include NE type, alarm ID, alarm name, alarm severity, and alarm type.
To add a user-defined alarm, you need to set the name and ID of the alarm.

140
The user-defined alarms of NEs are used to monitor the physical environment of
hardware. They can take effect only after being bound to specific subracks, slots, or
ports. The procedure is as follows: Add a user-defined alarm on U2000, and bind it to an
NE that is being monitored. The operations can be performed in the Add Alarm Binding
dialog box. Alternatively, you can run the SET ALMPORT command to send the cabinet
ID, subrack ID, slot ID, and port ID directly to an NE.

141

142

143

144
U2000V200R016 Configuration Management P-0

145

146

147
This chapter is to have a look at some important features of configuration function.

148
Configuration function can be divided into three main parts: Information browser, NE
report, NE management.
In the first chapter is the overview of every functions to let you know what is the
configuration functions mainly about.

149

150

151
The picture is the example of NE synchronization management.

This Senior level is only used to super network configuration management staff who will
do some very complicated configuration on M2000.

152

153

154
The MIT(Management Information Tree) browsing interface supports the function of

searching for information on the navigation tree. On the MIT browser, you can search for
physical and logical information about NEs, such as NE name, NE type, NE version,
DST, IP address, and time zone.
If an NE has more than 200 configuration records, the U2000 displays the configuration
records in paged mode. You can click an NE node to view the button for browsing in
paged mode.

155

156
Link type: Type of a physical link. Currently, the M2000 supports the following link types:
MTP3Link, MTP3BLink, DataLink, M3UALink, H248Link, BICCSCTPLINK, FiberLink,
and MicrowWaveLink.
MTP3Link, MTP3BLink, DataLink, FiberLink, MicroWaveLink can only be created
manually. The supported NE types are as follows:
MTP3Link and MTP3BLink links can be set up between the MGW and the
MSCServer, between the MGW and the MSCe, between the SGSN and the
MSCe, between base station controllers of the same NE, and between base
station controllers of different types of NEs.
The BSCs that support MTP3Link and MTP3BLink links are RNCs, BSC6900
UMTSs, BSC6900 GUs, BSC6910 UMTSs, and BSC6910 GUs.
DataLink links can be set up between the CG and the GGSN80, and between the
CG and the SGSN.
The physical NEs at both ends of a FiberLink are optical transmission devices.
The physical NEs at both ends of the MicroWaveLink are RTNs in the optical
transmission devices.
M3UA, H248, and BICCSCTP links are automatically created by the system.
They support the following types of NEs: One end of an H248 or M3UA link must
be an MGW, and the other end of the link can be an MSCServer or MSCe.
BICCSCTP links can only be created between MSCServers.

157
Query what subarea some special NEs are in. An NE partition refers to the U2000 server
that manages the NE. If the U2000 server adopts the cluster solution, NEs can be
managed by different servers (partitions). On the U2000 client, you can query different
NE partitions.

158
You can manage inventory data only after you have the license of the inventory
management function. In a multimode base station, you also need to have a license for
each Radio Access Technology (RAT) of this MBTS. Then, you can manage the
inventory data of the MBTS.
Inventory management involves physical inventory management and logical inventory
management. The objects of logical inventory management are cells and versions when
the RNC is taken as an example.
The objects of physical inventory management are cabinets, subracks, slots, boards,
ports, antennas, and optical modules when the RNC is taken as an example.
Most components of NEs report their inventory data to the U2000 when the U2000
queries them for inventory data. Therefore, you can query or manually synchronize
inventory data in the Inventory Management window. In addition, the U2000 provides
the function of manually adding inventory data because some specific components of
NEs cannot report their inventory data to the M2000.

159
You can also add information manually.

160

161

162

163
By this function you can view the basic information about multiple NEs, including the NE
name, NE type, version, IP address, physical location, Vendor, description, district,
longitude, latitude, capacity, maintenance region, status, and multimode base station
RAT.

164
Parameter Description
NE Name Name of an NE.
NE Type Type of an NE.
Version Version of an NE mediation.
IP Address 1 (Master) IP address of an NE.
IP Address 2 Slave IP address.
Physical Location Physical location of an NE.
Vendor Name of an NE vendor.
Description Description of an NE.
District District of an NE. Users outside China need to import the files providing their
own district information.
Longitude Longitude of an NE.
Latitude Latitude of an NE.
Capacity Maximum value of a traffic parameter of an NE, such as Maximum of Users,
Maximum of concurrent Gsm calls, or Maximum of concurrent Call Hold
calls.
The displayed parameter varies from one NE to another. Currently, this
parameter is valid for only SOFTX3000 and MSCServer.
Maintenance Region Maintenance region of an NE. The maintenance region of an NE is defined by
customers.
Status •Connection status of the NE. Online
•Offline
Multimode Base Station RAT Radio access technologies (RATs) of the multimode base station.
Product Type Product type of an NE.
Statistics Statistics collected by NE type, which is displayed in the format online NE
quantity/total NE quantity.

165
By viewing NE statistical reports, you can query the information about NEs, such as the
quantity, version of some NE type.
In the NE Statistical Report window, you can query, save, and print reports.

166
By viewing the RAN reports, you can learn about the information about the NE resources.
You can save RAN reports to a local PC or print the reports.
The network types that support the RAN report are UMTS, LTE, CDMA, and GSM. The
reports provided by RAN reports vary according to network types.
NE Reports Provided by the RAN Report

UMTS UMTS site report and UMTS cell report.
LTE LTE site report, LTE cell report, LTE X2 interface report, LTE S1 interface report, LTE CPRI
port report and LTE statistical reports.
CDMA CDMA BTS report, CDMA cell report, CDMA carrier report, CDMA carrier statistic report,
and CDMA TRM report.
In addition to the resource information, the CDMA carrier report displays the operation
status and management status of carriers. You can check whether the physical device of
a carrier resource is intact and check the management operations performed on the
resource by referring to the operation status and management status respectively.
GSM GSM BTS report, GSM cell report, GSM carrier report, GSM channel report, neighboring
GSM cell report, and external GSM cell report

167
By viewing the RAN reports, you can learn about the information about the NE resources.
You can save RAN reports to a local PC or print the reports.
The network types that support the RAN report are UMTS, LTE, CDMA, and GSM. The
reports provided by RAN reports vary according to network types.
NE Reports Provided by the RAN Report

UMTS UMTS site report and UMTS cell report.
LTE LTE site report, LTE cell report, LTE X2 interface report, LTE S1 interface report, LTE CPRI
port report and LTE statistical reports.
CDMA CDMA BTS report, CDMA cell report, CDMA carrier report, CDMA carrier statistic report,
and CDMA TRM report.
In addition to the resource information, the CDMA carrier report displays the operation
status and management status of carriers. You can check whether the physical device of
a carrier resource is intact and check the management operations performed on the
resource by referring to the operation status and management status respectively.
GSM GSM BTS report, GSM cell report, GSM carrier report, GSM channel report, neighboring
GSM cell report, and external GSM cell report

168
You can query the information about the links related to a specified NE.
Currently, only the SGSN, MSCServer, RNC, BSC6900 GSM, BSC6900 UMTS,
BSC6900 GU, BSC6910 GSM, BSC6910 UMTS, BSC6910 GU and BSC6000(GSMR)
support the function of viewing NE link reports.
In the Link Report window, multiple tab pages corresponding to different links exist. On
the corresponding tab page, you can click Query to continue querying relevant NE link
reports. You can also save and print link reports.
Report Type Link Type
SGSN Supports MTP3 link reports, MTP3 route reports, MTP3B link reports, NSVC
reports, and MTP3B route reports.
MTP3 Supports MTP3 link reports and MTP3 route reports.
RNC Supports PPP link reports, MLPPP link reports, MLPPP group link reports, IPPATH
link reports, and SCTP link reports.
MBSC Supports PPP link reports, MLPPP link reports, MLPPP group link reports, IPPATH
link reports, and SCTP link reports in IP networking mode.

169
You can query the information about the links related to a specified NE.
Currently, only the SGSN, MSCServer, RNC, BSC6900 GSM, BSC6900 UMTS,
BSC6900 GU, BSC6910 GSM, BSC6910 UMTS, BSC6910 GU and BSC6000(GSMR)
support the function of viewing NE link reports.
In the Link Report window, multiple tab pages corresponding to different links exist. On
the corresponding tab page, you can click Query to continue querying relevant NE link
reports. You can also save and print link reports.
Report Type Link Type
SGSN Supports MTP3 link reports, MTP3 route reports, MTP3B link reports, NSVC
reports, and MTP3B route reports.
MTP3 Supports MTP3 link reports and MTP3 route reports.
RNC Supports PPP link reports, MLPPP link reports, MLPPP group link reports, IPPATH
link reports, and SCTP link reports.
MBSC Supports PPP link reports, MLPPP link reports, MLPPP group link reports, IPPATH
link reports, and SCTP link reports in IP networking mode.

170
View an MBTS report to know the details about an MBTS and the correlations of the
single-mode base stations in the MBTS.

171
Each MBTS relationship report provides the information about the involved single-mode
base stations, such as name, FDN, and capability.

172

173

174

175
Automatic synchronization: Currently, all the NEs except cBSC and RAC support the
automatic synchronization function. Generally, automatic synchronization is triggered by
NE configuration data change and NE reconnections.

176
In the Task Management window, you can enable the configuration data of an NE to be
synchronized on a scheduled basis (the synchronization time and period are
configurable). After receiving the information, the server synchronizes the configuration
data as scheduled. All the configuration data of the NE is synchronized during the
scheduled synchronization.

177

178
Only one synchronization task can be performed for an NE at a time. If a synchronization

task is in progress for the NE, the new synchronization task will be put into the Waiting
for Synchronization queue and be executed until the previous task is finished.
In the Waiting for Synchronization queue, a manual synchronization task is
preferentially performed than a scheduled synchronization task, and a scheduled
synchronization task is preferentially performed than an automatic synchronization task.
If a higher-priority synchronization task is triggered later than a lower-priority
synchronization task in the Waiting for Synchronization queue, the higher-priority
synchronization task will replace the lower-priority synchronization task.
For the NEs other than new physical NEs, you need to manually refresh the navigation
tree in the MIT Browser window after each synchronization. Then, you can obtain the
latest navigation structure.
To stop a synchronization task, right-click the NEs and choose Cancel Synchronization
from the shortcut menu.
To view detailed information about the NE synchronization, right-click the NEs and
choose Monitoring NE Synchronization from the shortcut menu.

179
You can view the details of the synchronized tasks here.

180
This function is to check the highest severity of alarm on some NEs and the connection
status between NEs and U2000.
Also you can save the information display on the screen to a file.

181

182

183
During network operation and maintenance, users adopt different policies and
concentrate on different aspects. When an NE is under maintenance operations such as
construction, upgrade, and commissioning, the NE may report a large number of alarms
to the U2000 due to these operations. Most of these alarms are automatically cleared
after the maintenance operations are finished. Users need to differentiate these alarms
from normal mode alarms to avoid the impacts of these alarms on normal network
monitoring. To meet user requirements, the U2000 provides the maintenance mode
management feature and allows users to adopt different methods of maintaining NEs
based on NE modes.
Maintenance mode: The maintenance mode of an NE specifies whether the NE is under

maintenance operations and what operations are in progress on the NE. If an NE is
under maintenance operations, the U2000 enables the mechanism for handling
maintenance modes. If an NE is in NORMAL mode, it indicates that the NE is not under
maintenance operations.
Maintenance mode alarms: When an NE is under maintenance operations such as

construction, upgrade, commissioning, and expansion, the NE may fail to function
properly within a short time period and therefore report a large number of alarms to the
U2000. Most of these alarms such as reset, switchover, and link disconnection alarms
are of high severities and are automatically cleared after the maintenance operations are
finished. To avoid these alarms from affecting normal network monitoring, the U2000

184
defines all the alarms reported during NE maintenance as maintenance mode alarms and
specifies a mechanism to handle them.(The smoke alarm, water alarm, and burglar alarm
related to direct damages on devices are not maintenance mode alarms and are reported
as common alarms.)

185
The NEs in the following versions support this function:

GSM
BSC6000: V900R008C12SPH019 and later versions , BSC6900 GSM:
V900R011C00SP700 and later versions
BSC6910 GSM: All versions , BSC6000(GSM-R): V901R008 and later versions
BSC6000(R11+): All versions , GBTS: All GBTSs managed by a GBSC supporting this
function
UMTS
BSC6810: V200R011C00SPC180 and later versions , BSC6900 UMTS:
V900R011C00SP700 and later versions
BSC6910 UMTS: All versions , BSC6810(R11+): All versions
NodeBV1: V100R011C00SPC500 and later versions , NodeBV2: V200R011C00SPC230
and later versions
LTE: eNodeB in V100R001C01SPC110 and later versions
SingleRAN
BSC6900 GU: V900R011C00SP700 and later versions , BSC6910 GU: All versions
BTS3900: All versions , DCU: All versions
CDMA
CBSC: V300R007C00SPC200 and later versions
CBTS: All CBTSs managed by a base station controller supporting this function
WiMAX
DBS3900 WiMAX: V300R003C00 and later versions , BTS3701B: V300R003C00 and
later versions
BTS3702E: V300R003C01 and later versions , BTS3702C: V300R003C01 and later
versions

186
Prerequisites:
You have the operation permission Maintenance Mode Definition. The
permission type is Network Management Application.
The time on the U2000 and that on NEs are synchronized and the time on all NEs
are also synchronized. Otherwise, applying maintenance mode alarm settings to
the NEs fails. When this occurs, maintenance mode alarms are displayed on the
U2000 client and also reported to the NMS.
Maintenance mode are INSTALL, EXPAND, UPGRADE and TESTING.
You are not allowed to set the maintenance mode of an MBTS or MBSC. You need to
set it based on each single-mode NE. If you set NEs of only a single mode to enter the
maintenance mode, the setting will not affect NEs of other modes and common modules
of the MBTS or MBSC.
After maintenance operations are complete, remember to restore the NE to the
NORMAL mode.

187
If the maintenance modes predefined on the U2000 do not meet your requirements, you
can add maintenance modes to the U2000. This function does not apply to GBSS NEs
earlier than GBSS14.0 and WRAN NEs earlier than WRAN14.0.
Prerequisites: You have the operation permission Maintenance Mode Definition. The
permission type is Network Management Application.
In addition to the preceding modes, the U2000 reserves 10 modes for future
customization. The internal names of the 10 modes are EXPANDSTATUS1 to
EXPANDSTATUS10. You can use these modes and assign aliases to them based on
your requirements. Each internal name refers to a mode name defined on the NE and
each alias refers to a mode name defined on the U2000. On the U2000, the aliases of
the modes rather than their internal names are displayed.
The newly added maintenance mode is displayed in the table and takes effect on all NEs
that support this function.

188
To help NEs automatically obtain IP addresses by using the DHCP service, the U2000
provides the DHCP configuration management function. This function helps users query
and maintain the DHCP information about each NE and view the DHCP process of each
NE through the graphical user interface (GUI).

189
The dynamic host configuration protocol (DHCP) is developed on the basis of the
bootstrap protocol (BOOTP). The DHCP provides information such as IP addresses to
Internet hosts on the TCP/IP network. In the radio communication system, the DHCP is
used to automatically search for NEs when the NEs are powered on and to assign initial
configuration data for NEs, such as IP addresses. The application scenarios of the
DHCP are as follows:
Initial site deployment: The information such as the IP address is configured
(synchronized) on the U2000. After an NE is powered on, the IP address request
process is triggered.
NE reparenting The information such as the IP address is reconfigured
(resynchronized) on the U2000. After the NE is reparented and reset, the IP
address request process is triggered.
The U2000 provides the GUI for you to query DHCP information and DHCP process logs
of NEs in real time. You can also perform various operations such as importing and
exporting DHCP information, configuring DHCP information about NEs in batches,
creating, modifying, and deleting the DHCP information about a single NE, and detecting
the VLAN ID used by the OM service of NEs. The U2000 client provides different DHCP
configuration management functions based on NE type.

190
The entire network is divided into several VLANs to fulfill the security and management
requirements. After an NE is initially configured, the VLAN detection is required to obtain
the VLAN ID of the VLAN on which the DHCP server is located. The NE sends DHCP
requests to the DHCP server according to the obtained VLAN ID.
After receiving the DHCP detection request, the layer 2 network devices add the VLAN
ID to the UDP detection message and forward the detection message to the VLANs that
are managed by the layer 2 network. The NEs in the VLAN obtain VLAN IDs according
to the detection message. When initiating a DHCP request, the NE advertises the DHCP
request to specific VLANs according to the obtained VLAN IDs.
After the VLAN detection, the NE obtains the VLAN ID of the network where the U2000
is located. Then, the NE sends a DHCP request to a specific VLAN. After receiving the
DHCP request, the DHCP server queries the DHCP configuration information according
to the electronic serial number of the NE and sends the information to the NE through
UDP messages.

191

192

193

194
U2000 V200R016 Performance Management

195

196

197
This slide is based on the application style of the client, you can also switch to the
traditional style on preference menu.

198

199
Performance function is mainly about two parts, measurement management and result
management, the previous one is how to set all kinds of counters to measure and how to
check the measurement status and so on, the latter is how to get the results and manage
them.
And additional, some performance monitor functions also provided.

200
A measurement counter defines what is to be measured. It is the basic unit of

performance measurement.
A measurement object defines who is to be measured. It can be a logical object (such as
a board or subrack) or a logical object (such as a cell or neighboring cell). There is
certain mapping between measurement objects and measurement counters. Each
measurement object maps a few measurement counters. Measurement counters are not
independent of measurement objects.
The measurement period defines the internal at which an NE reports measurement
results. The reporting period varies according to measurement counters. It can be 5-
minute, 15-minute, 30-minute, 60-minute, or 24-hour.

201

202
To facilitate management, measurement counters are classified into function sets and
function subsets.
Level 1: function set
A function set contains several function subsets that are related to a group
of system functions. Function set is also called measurement set.
Level 2: function subset
A function subset contains a few measurement counters that are related to
a system function. Function subset is also called measurement unit.
Level 3: measurement counter

203
Measurement counters can be classified by source into two categories:

System counters: These counters are defined by NEs. NEs report the
measurement results of system counters periodically to U2000. System counters
are grouped into common counters and extended counters.
Custom counters: These counters are customized by users on U2000 client.

204
You can save the settings of some parameter-based system functions by using the
preferences settings.
When you log in to U2000 client next time, U2000 client will be automatically adjusted to
the settings of the last login.
Specific Query: The default interval of querying result.
Synchronize Result: The default interval of synchronization of result.
Result Segment: The default interval of querying result in section time.

205

206

207

208
Only after you set the measurement counters, measured objects, and measurement
period for an NE on U2000, can the NE reports the results, that is, the performance data,
to U2000 when the measurement period comes.

209

210
Switch to the status index, if the light is green and the description is active, then the
measure is normal, if not, please check the reason of the fault.

211
User-defined counters refer to the counters that are defined by adding, subtracting,
multiplying, and dividing system counters. The sources of user-defined counters are as
follows:
Defining the counters on U2000 client.
Defining the counters in the files before importing the counters into U2000.
User-defined counters can be nested to create other user-defined counters. You can add,
modify, and delete user-defined counters when U2000 is running.

212
Double-click a counter in Available Counter List, or manually enter a counter to edit the
formula. The format of a manually entered counter is as follows:
(Counter 1 + Counter 2) x {100}/(Counter 3 + Counter 4 + Counter 6)

213
Double-click a counter in Available Counter List, or manually enter a counter to edit the
formula. The format of a manually entered counter is as follows:
(Counter 1 + Counter 2) x {100}/(Counter 3 + Counter 4 + Counter 6)

214
You can group objects of the same type into an object group. In this way, you can
perform the same operation on all the objects in this object group. U2000 allows you to
create, view, and modify the information about a user-defined object group. This function
is used only for commissioning cells.

215
You can group objects of the same type into an object group. In this way, you can
perform the same operation on all the objects in this object group. U2000 allows you to
create, view, and modify the information about a user-defined object group. This function
is used only for commissioning cells.

216
The data of a performance object on U2000 may be different from that on a specific NE. If you find
that some objects are missing, the Diagnose Missing Object function can diagnose missing
object and provide the cause and troubleshooting suggestions to help find missing objects.
Object missing involves the following scenarios: Objects are actually missing.
Data of a specific object fails to be correctly synchronized to U2000 system because the
link between U2000 and the desired NE is faulty.
Synchronization is performed by schedule and time difference exists between two
synchronization tasks. In this case, the information of a specific object may be not
synchronized in time.
The performance object information is converted from configuration object information. If
the information of some configuration objects is incomplete, the data of the specific
performance objects may be missing.
Objects are actually not missing but are regarded as being lost.
If information of an NE's objects are not configured, U2000 displays that no object
information is present.
The performance object information is converted from configuration object information.
The conversion rules are complex, and users may mistakenly take the configuration
objects as the performance objects and think that the performance objects are missing.
Type 3 objects need to be imported manually. If users fail to import the objects, the
system thinks that the objects are missing.

217

218

219
Through U2000 client, you can query the performance data of the OSS server and
subscribe to and query the performance measurement results of the NEs that are set for
measurement on U2000. U2000 allows you to check the integrity and reliability of the
performance measurement results reported by NEs. You can also check whether
missing performance measurement results exist by specifying query conditions.
The number of function subsets can not exceed 10 for one query. In the displayed
Result Query dialog box, the query results are displayed in a table. You can choose to
display them in a line chart or a bar chart.
Two modes are provided for querying performance measurement results:

By criteria
By template
Before returning the results, U2000 estimates the number of results for this query. If the
estimated number is greater than 500,000, U2000 displays a message asking you to
export the results to your local PC.

220

221

Permission
222

Permission
223
For OSS performance result:

The OSS performance results can be stored for fifteen days by default in U2000
performance database. System deletes the data whose storage duration expires at a fixed
time every day.
The OSS performance results are displayed only in tables.
A maximum of six query result windows can be concurrently opened.
For NE’s performance result:
You can query the NE performance measurement results of the current and the historical
measurement objects. A historical measurement object is an object that has been
removed or deactivated on an NE but is still available in the performance database on
U2000.
A maximum of six result subscription windows can be concurrently opened on each client.
When reporting performance measurement results, an NE identifies whether each result for an
object is reliable. Result reliability is used to measure whether a performance measurement result
is reliable. Formula: Number of reliable result records/Number of queried result records x 100%.
When displayed in a table, results in grey are unreliable and in white are reliable. You can right-
click in the table and choose Reliability from the shortcut menu to check reliability of the whole
performance measurement results.

224
Busy Time: Some counters can be queried by using this option. This option becomes
available after some Function subset is selected in the Organization Style area.
Busy hour query supports 60-minute period only.
Buy hour query is not supported in certain time systems.
Busy hour query can be executed only when a busy-hour counter is set to be measured.
Busy hour counters are defined by specific NEs.

225
Busy Time: Some counters can be queried by using this option. This option becomes
available after some Function subset is selected in the Organization Style area.
Busy hour query supports 60-minute period only.
Buy hour query is not supported in certain time systems.
Busy hour query can be executed only when a busy-hour counter is set to be measured.
Busy hour counters are defined by specific NEs.

226

Permission
227

Permission
228

Permission
229
Select one or multiple or all OSS performance measurement results to save.

The results can be exported as a txt, xls, xlsx, csv, or html file.

230
Select one or multiple or all OSS performance measurement results to save.

The performance query results in tables can be saved as an xls, xlsx, csv, html, or txt file.

231
The performance query result in line charts or bar charts can be saved as a JPG file.
You can choose to print it as well.

232

233
One or multiple rows of data may be lost and not be displayed on GUIs when you
perform result query. In this case, you can use the result loss diagnosis tool to make a
diagnosis.
Prerequisites
U2000 service is running properly.
The period for result loss diagnosis is not a summary period.
The period for result loss diagnosis is not a history period.
The objects for result loss diagnosis are not neighboring cells.
The time segment for result loss diagnosis is continuous.
The counters for result loss diagnosis are not busy-hour counters.
The objects for result loss diagnosis are not historical cells.
The result loss diagnosis for the process of reporting 5-minute results is not
supported.
The result loss diagnosis for the process of reporting cBSC results is not
supported.

234
The causes of result loss are as follows:

Objects are not set to be measured.
NEs are disconnected.
Some records are missing from the result files reported by NEs.
A delay occurs when NEs report the result.
The space of system database is insufficient, the directory for saving the result
files does not exist, or the permission on the folder is incorrect.
An error occurs during the process when NEs report results.
You can also query results and then click Diagnose Result Loss for the queried result.

235
Synchronizing NE measurement results manually refers to the manual supplementary

collection of missing measurement results. When detecting missing NE performance
measurement results, U2000 automatically collects the NE performance measurement
results that are reported during the latest six hours again. In addition, you can perform
manual synchronization to collect the NE measurement results that cannot be collected
again through the automatic supplementary collection of U2000.
The NEs that are in the SNMP measurement mode do not support this function.
Before synchronizing NE measurement results manually, you are advised to check
whether the measurement result synchronization task exists. This can avoid repetitive
operations, thus saving system resources.
You can save synchronize result as files of xls or xlsx format.

236
After you subscribe to NE performance measurement results, the newly reported

performance measurement results are automatically displayed in the Subscribe to
Measurement Results window so that you can view the performance results in real time.
Only one result subscription window can be opened on each client. In each result
subscription window, you can subscribe to the measurement results of only one NE and
one function subset.
This function is optional. If the shortcut menu Subscribe Result or the icon is
unavailable, you can infer that the product of the current version does not support this
function.
User-defined counters do not support this function.

237
A large deal of traffic statistics on neighboring cells will be generated and if all this data
get into the database, the database IO may break down and the database space may be
insufficient, so the traffic statistics of neighboring cells are not imported into the database
by default but saved as files. If you want to query the data, import the files into the
database.
The intermediate file storing the performance measurement data of neighboring cells can
be stored for a maximum of 15 days on U2000 server. The performance measurement
data of neighboring cells imported from the performance database can be stored for a
maximum of 3 days.
A maximum of five import tasks can be performed at a time on U2000 server.
Only the data that is collected for a maximum of three days can be imported. Otherwise,
an error message is displayed on the GUI.
The imported files are saved in /export/home/omc/var/pm/NeighborCellPMData.

238
The Neighboring Cell Data Import window displays all the running neighboring cell
import tasks. Tasks that are newly created are automatically displayed. Tasks that have
been completed are not automatically deleted. When you open the Neighboring Cell
Import Task window again, the Neighboring Cell Data Import window displays only
the running neighboring cell import tasks but does not display the complete tasks.

Permission
239
When reporting performance measurement results, an NE identifies whether each result

for an object is reliable. Result reliability is used to measure whether a performance
measurement result is reliable. Formula: Number of reliable result records/Number of
queried result records x 100%.
When displayed in a table, results in grey are unreliable and in white are reliable. You
can right-click in the table and choose Reliability from the shortcut menu to check
reliability of the whole performance measurement results.

Permission
240
Performance result can be exported to files which are stored on the PC and then the
result will be deleted from the database to ensure the later result can enter the database
normally.
This is a system task and can not be deleted but suspended.

Permission
241
After the storage period reach the value that are set on the Extend parameters, the
corresponding performance result will be deleted from the database.

Permission
242

243

244
You can query the system performance counters preset by U2000 or the existing custom
performance monitoring counters to learn about the monitored objects and the formula of
the counters. If the counters meet the monitoring requirements, you can directly select
the corresponding counters when creating monitoring tasks. Otherwise, you must
customize monitoring counters.

Permission
245
A simple threshold of performance counter refers to a threshold set for a single counter.
After a threshold is correlated to a threshold alarm name, a threshold alarm
corresponding to the alarm name is generated when the measurement result of a
counter goes beyond the preset threshold range.
You can set a simple threshold for all objects of one type or some objects of a specific
NE. You are not allowed, however, to set a simple threshold for objects of different object
types. You can set simple thresholds of four alarm severities in one simple threshold task.
If a counter threshold is not correlated to a threshold alarm name, this threshold is
automatically correlated to the default threshold alarm name. The default threshold alarm
name is Performance Threshold Default Alarm, and the default alarm ID is 40925

Permission
246

Permission
247
You can create a new threshold by copy an old one and modify some parameters of it,
the modifications do not affect the old threshold alarms.

Permission
248
A combined counter threshold refers to the threshold defined for the value obtained
through logical or arithmetic operations of multiple counter values. After correlating a
preset threshold to a threshold name, the threshold alarm is generated when the
measurement results of a counter meet the alarm triggering conditions for successive
periods. When the measurement results of a counter meet the alarm clearance
conditions for successive periods, the threshold alarm is automatically cleared.
You can set a combined threshold for all objects of one object type or some objects of a
specific NE. You are not allowed, however, to set a combined threshold for objects of
different types.
If a counter threshold is not correlated to a threshold alarm name, this threshold is
automatically correlated to the default threshold alarm name. The default threshold alarm
name is Performance Threshold Default Alarm, and the default alarm ID is 40925.

Permission
249
This function is to set the time segment for suspending the counter thresholds of each
NE. Thus, the activated counter thresholds are automatically suspended during the
specified time segment. After the counter thresholds of an NE are suspended, the
system no longer performs threshold check on the counter values of this NE.
When the time segment set for suspending the counter thresholds of an NE conflicts with
the time segment set for activating the counter thresholds, the suspending operation
takes priority.
You can set only one time segment for suspending counter thresholds of one NE. If a
suspending time segment is preset for the NE, a new time segment replaces the preset
one.
You can manually activate the counter thresholds that are within the suspending time
segment. After a counter threshold is activated, it will not be suspended at the specified
suspending time segment. To suspend this counter threshold again, you must suspend it
manually.

Permission
250
U2000 provides the function of performance counter threshold alarms so that one or more
counters of a measurement object can be monitored during periodical measurements. When the
performance results of NEs meet the triggering conditions, the corresponding threshold alarms
are generated. Performance counter thresholds are categorized into simple thresholds and
combined thresholds.
The principles for generating the corresponding threshold alarms are as follows:
When a counter value of an NE meets the preset alarm severity conditions, the U2000
generates only the threshold alarms corresponding to the measurement period and alarm
severity. It cannot generate threshold alarms of other periods.
If a threshold alarm of another severity is generated for a counter in the system, the
U2000 clears this alarm and then generates a threshold alarm of the corresponding
severity.
Only when the alarm generation conditions are met for a simple threshold, the alarm of
the current severity is generated, the history alarms are cleared, and repeated alarms are
not sent.
An alarm is generated or cleared for a combined threshold only when the preset times for
triggering or clearing alarms are reached.
If a threshold alarm of the same severity is generated for a counter in the system, the
threshold alarm of this severity is not generated repeatedly.
If no result generated within the period corresponding to the threshold conditions is
reported, no threshold alarm is generated.

251

252

253
Note: Select BSC6900 GU/GSM Cell Performance Measurement.

254
Note: Select BSC6900 GU/GSM TRX Performance Measurement.

255

256
U2000 V200R016 Log Management P-0

Permission
257

Permission
258

Permission
259

Permission
260

Permission
261
U2000 Operation Logs

Operation logs of U2000 record the user operations on U2000 client, which helps rectify faults.
U2000 System Logs
U2000 system logs record the operating information about U2000, helping detect faults and
ensuring that U2000 runs properly.
U2000 Security Logs
U2000 security logs record the security-affected operations on U2000 client, ensuring that U2000
runs properly.
NE Operation Logs
By browsing NE operation logs, you can know the operations performed by a user at a certain
time. The operation information is used for future reference.
NE Security Logs
By browsing NE security logs periodically, you can find security vulnerabilities of the NEs and take
proper measures to ensure the security of the NEs.
MML Logs
MML log management helps query MML command issue, which facilitates fault identification and
improves maintenance efficiency.

Permission
262

Permission
263
You can query U2000 operation logs to know the operation records of U2000.
Operation logs are stored in the database. You can query them through the client.
You can dump operation logs from the database to a file. Querying operation logs:
Choose System > Log Management > Query Operation Logs (traditional style);
alternatively, double-click Security Management in Application Center and choose
Log Management > Query Operation Logs (application style) from .
After the operation logs are dumped, U2000 generates the associated folder and log file:
Folder: In the dump path, U2000 generates a folder named the date of the dump
operation. The format of the name is YYMMDD.
Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
operation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-log-
dateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
number.extension saved the information about the dumped logs.
Operation logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be
compressed to a .zip package.
To prevent insufficient space in the database, you can configure U2000 to dump
operation logs periodically or immediately. Dumped operation logs are saved to files, and
the original operation logs are deleted from the database.

Permission
264
Right-click a log in the window and choose Details from the shortcut menu, or double-
click the log.

Permission
265
You can query system logs of U2000 to understand the running status of U2000, that is
the important events that occur when U2000 is running.

Permission
266
You can query U2000 security logs to know U2000 security operations of U2000.
If a value in the Operation User column in the log query result is an invalid user, the
system may have been attacked.

Permission
267
You can query NE operation logs to know the operation records of an NE.
Statistics results are generated based on the existing data in the database and sorted by
time (Greenwich Mean Time). If the database is empty, no statistics result is displayed
accordingly.

Permission
268

Permission
269

Permission
270
You can know the operation status by collecting statistics and analyzing the U2000
operation logs. For example, you can collect statistics about the frequently performed
operations within a period.
Choose Log Management > Operation Log Statistics (application style) or System >
Log Management > Operation Log Statistics (traditional style).
In the Filter window, set the statistics settings and filter criteria, and then click OK.
The display mode of statistical results varies according to the settings on the Statistics
Settings tab page in the Filter dialog box. The display mode of statistical results varies
according to the settings on the Statistics Settings tab page.

Permission
271

Permission
272

Permission
273
By this function you can save original NE log files to the U2000 database after NE log
synchronization so that you can view NE logs on U2000 server without connecting to
NEs.
Subscription Type
Subscribing to NEs by NE
Subscribing to NEs by NE type
Subscribing to NEs on the entire network
If you select this subscription type, the system overhead will increase greatly. Therefore,
narrow down the subscription range as required.

Permission
274
This function is to synchronize the operation logs and security logs on the U2000 server
with those on NEs. This helps you obtain the latest logs from NEs.
The original log files of all NEs will be saved. When synchronizing logs of subscribed
NEs, the U2000 parses the original log files and saves the parsing result into the
database. When synchronizing logs of NEs that have not been subscribed to, the U2000
does not save the original log files into the database. You can view these log files by
importing them.
You can manually synchronize NE logs by this function or set automatic scheduled NE
logs synchronization in Task Management function.

Permission
275
You can view NE operation and security logs by importing original NE log files.
The database capacity size is limited. You are advised to import log data by specifying a
time range as required to avoid significant increase of system overhead.
When the database capacity reaches a threshold, the system displays a message stating
that the NE log data fails to be imported.
Only one user can import NE log data within a time segment.
If NE log data is being imported, do not synchronize NE logs until the import is complete.
Otherwise, the selected data to be imported may be deleted because of the limited
database capacity.

Permission
276

Permission
277
The directory which save the trace is U2000 client installation directory
client\client\tracefile\*

Permission
278

Permission
279
root@osssvr-1 # more messages.0

May 15 11:30:02 osssvr-1 vxvm:vxconfigd: [ID 702911 daemon.warning] WARNING V-
365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server.
May 15 11:30:02 osssvr-1 As set forth in the End User License Agreement (EULA) you
must complete one of the two options set forth below. To comply with this condition of
the EULA and stop logging of this message, you have33 days to either:
May 15 11:30:02 osssvr-1 - make this host managed by a Management Server (see
http://go.symantec.com/sfhakeyless for details and free download), or
May 15 11:30:02 osssvr-1 - add a valid license key matching the functionality in use on
this host using the command 'vxlicinst' and validate using the command 'vxkeyless set
NONE'.

Permission
280

Permission
281

Permission
282

Permission
283
Log Collection Method.

Login U2000 server as user root or omcuser
# cd /export/home/omc/var/logs,
# tail -f iMAP.****.trace > /tmp/mytrace.txt.
Come to U2000 client, execute the operation which has problem, Back to the telnet
window executing tail command, wait for one minutes, collect enough information, press
Crtl+C to stop the tail.
Download the result file /tmp/mytrace.txt using FTP ASC format.

Permission
284
When do we need this information
When some services exits abnormally and core files are created.
When there are alarms of service exits abnormally.
How to get or check the core information?
# pmap core.imapsvcd.0.22531.1086 > core.imapsvcd.0.22531.1086.mapinfo
# pstack core.imapsvcd.0.22531.1086 | c++filt >
core.imapsvcd.0.22531.1086.stack
# pflags core.imapsvcd.0.22531.1086 > core.imapsvcd.0.22531.1086.pflags
# gtar cvfz core.stack.tar.gz core.xxx.xxx.xxx.stack

Permission
285

Permission
286
This function is to collect U2000 fault information by scenarios. Fault information includes trace
information, configuration files and database information required to locate faults.
Prerequisites
You have logged in to the OSMU server as user ossuser.
Context
In an HA or remote HA system, perform this operation on only the active server. In a Sun
SLS system, perform this operation on only the master server. If services on the master
server or a slave server are switched over to the standby server, fault information cannot
be collected.
Procedure
In the OSMU main window, click Smart Assistant.
Choose Trouble Shooting > Trace Collection.
Choose Module Name > Problem Scenario from the navigation tree in the left pane. The
GUI for collecting information about the corresponding problem is displayed in the right
pane.
Type the relevant parameter and click Execute to complete data collection.
Click Report to view the collected fault information.
Click Download to download the collected fault information.
Click Task Historyto view or download collected historical fault information.

Permission
287
This task performs a health check for U2000 business and hardware and software of U2000
server. This includes things such as the operating system, database and disk array.
Prerequisites
You have logged in to the OSMU server as user ossuser.
Procedure
In the OSMU main window, click Smart Assistant.
In the navigation tree in the left pane, choose HealthCheck > OSS Health Check > OSS
Health Check.
Set disk array parameters. If no disk array is configured or no disk array information
needs to be collected, skip this step without setting disk array parameters.
Array Controller A IP Address: indicates the IP address of controller A on the disk
array.
Array Controller B IP Address: indicates the IP address of controller B on the disk
array.
Array Controller Password: indicates the password for logging in to a controller on
the disk array. Set a password in Array Controller Password when the S2600 or
S3900 disk array is used. If other types of disk arrays are used, you do not need
to set the password.
Click Collect.
Click Report to view a check report.
Click Download to download a check report.
Click Task History to view or download a historical check report.

Permission
288

Permission
289

Permission
290

Permission
291

U2000 O&m

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

U2000 O&m

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI

iManager U2000 Client Application

All Rights Reserved

1. iManager U2000 V200R016 Topology Management

2. iManager U2000 V200R016 Alarm Management

3. iManager U2000 V200R016 Configuration Management

4. iManager U2000 V200R016 Performance Management

5. iManager U2000 V200R016 Log Management

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

U2000 categorizes network devices according to their home networks.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without Permission

NE Creating NEs Creating NEs in Creating NEs Creation Mode

GBTS - √ - No manual intervention is required for

SNMP device √ √ √ •Creating NEs in batches (automatic

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

U2000 does not support the batch creation of virtual NEs.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

The NE reconnection states are described as follows:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

To recover system services, fault alarms must be properly handled.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission