GU - NetNumen U31 R18 V12.18 Test Guide - Distributed - R1.0
Uploaded by
Mohammad AslamGU - NetNumen U31 R18 V12.18 Test Guide - Distributed - R1.0
Uploaded by
Mohammad AslamGU_NetNumen U31 R18
V12.18 Test Guide_Distributed
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
LEGAL INFORMATION
Copyright © 2021 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any
reproduction or distribution of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the
contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service
marks, of ZTE CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations
or conditions are disclaimed, including without limitation any implied warranty of merchantability,
fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors
shall not be liable for damages resulting from the use of or reliance on the information contained
herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or
applications covering the subject matter of this document. Except as expressly provided in any
written license between ZTE CORPORATION and its licensee, the user of this document shall not
acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product
without further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to
inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
ZTE CORPORATION
Address NO. 55
:
Hi-tech Road South
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
ShenZhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: [email protected]
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Revision History
Product Version Document Version Serial Number Reason for Revision
V12.17 R1.0 First published
Author
Date Document Version Prepared by Reviewed by Approved by
2018-07-16 R1.0 Kou Zhanchuan Hou Chengyi, Li Wei 10024220
Intended audience: NetNumen U31 commissioning & maintenance engineer
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
About This Document
Summary
Chapter Description
1 Test Guide Provides a general description.
2 Server Hardware Test Describes the details of the server hardware test.
3 Disk Array Hardware Test Describes the details of the disk array hardware test.
4 Online Help Describes the test items of online help.
5 Topology Management Describes the test items of topology management.
6 Fault Management Describes the test items of fault management.
7 Performance Management Describes the test items of performance management.
8 Inventory Management Describes the test items of inventory management.
9 Configuration Management Describes the test items of configuration management.
10 Security Management Describes the test items of security management.
11 Maintenance Management Describes the test items of maintenance management.
12 Northbound Interface Describes the northbound interface related test items.
13 LTE SON Describes the LTE SON related test items.
14 Inspection Tool Test (V1) Describes the details of inspection tool test (V1).
15 Inspection Tool Test (V2) Describes the details of inspection tool test (V2).
16 Controller NE Management Describes the controller NE management related test items.
17 BS NE Management Describes the BS NE management related test items.
18 Software Management Describes the software management test items.
19 System Tool Describes the system tool test items.
20 HA Test Describes the HA test items.
TABLE OF CONTENT
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1 Test Guide........................................................................................................1
2 Server Hardware Test......................................................................................1
2.1 HP Hardware Test.............................................................................................1
2.1.1 Power Module Function Test.............................................................................1
2.1.2 Adapter Module Function Test...........................................................................2
2.1.3 HBA Module Function Test................................................................................3
2.1.4 Local Disk Function Test....................................................................................4
2.1.5 Server CPU and Memory Checking...................................................................5
2.2 E9000 Hardware Test........................................................................................6
2.2.1 Power Module Function Test.............................................................................6
2.2.2 Adapter Module Function Test...........................................................................6
2.2.3 HBA Module Function Test................................................................................7
2.2.4 Local Disk Function Test....................................................................................8
2.2.5 Server CPU and Memory Checking...................................................................9
3 Disk Array Hardware Test.............................................................................10
3.1 HP Disk Array Hardware Test..........................................................................10
3.1.1 Power Module Function Test...........................................................................10
3.1.2 Disk Function Test...........................................................................................11
3.2 KS3200 Disk Array Hardware Test..................................................................12
3.2.1 Power Module Function Test...........................................................................12
3.2.2 Disk Function Test...........................................................................................12
3.3 EMC 3200 Disk Array Hardware Test..............................................................13
3.3.1 Power Module Function Test...........................................................................13
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3.3.2 Disk Function Test...........................................................................................14
3.4 IBM 3700 Disk Array Hardware Test................................................................15
3.4.1 Power Module Function Test...........................................................................15
3.4.2 Disk Function Test...........................................................................................16
3.5 KU5200 Disk Array Power-down Test..............................................................17
3.5.1 Power Module Function Test...........................................................................17
3.5.2 Disk Function Test...........................................................................................17
4 Online Help.....................................................................................................18
4.1 Online Help......................................................................................................18
5 Topology Management..................................................................................19
5.1 Topology View Management............................................................................19
5.1.1 [ALL] Viewing the Topology.............................................................................19
5.1.2 [ALL] Refreshing the Data................................................................................20
5.1.3 [ALL] Statistics Topology..................................................................................21
5.1.4 [ALL] Configuring Coordinate Synchronization.................................................22
5.1.5 [ALL] Customizing GUI Elements.....................................................................23
5.1.6 [ALL] Exporting the GUI Display Style..............................................................24
5.1.7 [ALL] Importing the GUI Display Style..............................................................25
5.1.8 [ALL] Setting the Alarm Display Style...............................................................26
5.1.9 [ALL] Searching Cell........................................................................................27
5.1.10 [ALL] Displaying Global BS Statistical Information...........................................28
5.1.11 [ALL] Creating/Activating an NE Agent Using MML Command........................28
5.1.12 [ALL] Displaying BBU/RRU/RSU Information...................................................30
5.2 NE Agent Management....................................................................................31
5.2.1 [ALL] Creating an NE Agent.............................................................................31
5.2.2 [ALL] Starting an NE Agent..............................................................................32
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
5.2.3 [ALL] Stopping an NE Agent............................................................................33
5.2.4 [ALL] Modifying an NE Agent...........................................................................34
5.2.5 [ALL] Deleting an NE Agent.............................................................................34
5.2.6 [ALL] Viewing an NE Agent..............................................................................35
5.2.7 [ALL] Synchronizing the Configuration.............................................................36
5.2.8 [ALL] Querying the Operation Problem............................................................37
6 Fault Management.........................................................................................38
6.1 Alarm Monitoring..............................................................................................38
6.1.1 [ALL] Active Alarm Monitoring..........................................................................38
6.1.2 [ALL] Active Notification Monitoring..................................................................39
6.1.3 [ALL] Active Alarm Statistics Monitoring...........................................................40
6.2 Alarm Query.....................................................................................................41
6.2.1 [ALL] Active Alarm Query.................................................................................41
6.2.2 [ALL] History Alarm Query...............................................................................42
6.2.3 [ALL] Notification Query...................................................................................43
6.3 Alarm Statistics................................................................................................44
6.3.1 [ALL] History Alarm Basic Statistics.................................................................44
6.3.2 [ALL] History Alarm Busy-time Statistics..........................................................45
6.3.3 [ALL] History Alarm Important Alarm-Code Statistics.......................................46
6.3.4 [ALL] Timing Statistic Task Management.........................................................47
6.3.5 [ALL] Timing Export Task Management...........................................................48
6.3.6 [ALL] Suppressing Plan Task Management.....................................................49
6.3.7 [ALL] Alarm Panel............................................................................................50
6.3.8 [ALL] Site Alarm Statistics................................................................................51
6.4 Alarm Synchronization.....................................................................................52
6.4.1 [ALL] Synchronizing Active Alarms..................................................................52
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
6.4.2 [GUTAM] History Alarm Re-gathering..............................................................53
6.5 Setting.............................................................................................................. 55
6.5.1 [ALL] Rule Setting............................................................................................55
6.5.2 [ALL] Handling Suggestion Setting...................................................................56
6.5.3 [ALL] Severity Regrading Setting.....................................................................57
6.5.4 [ALL] Alarm Box Setting...................................................................................58
6.5.5 [ALL] Alarm Code Description Setting..............................................................59
6.5.6 [ALL] Reason Setting.......................................................................................60
6.5.7 [ALL] Alarm Forward Template Setting............................................................61
6.5.8 [ALL] TOP Alarm Restraining Setting...............................................................62
6.5.9 [ALL] Intermittent Alarm Setting.......................................................................63
6.5.10 [ALL] Alarm Prompting Setting.........................................................................64
6.5.11 [ALL] Automatically Acknowledging History Alarms.........................................65
7 Performance Management............................................................................66
7.1 Measurement Task Management.....................................................................66
7.1.1 [ALL] Creating a Measurement Task................................................................66
7.1.2 [ALL] Modifying a Measurement Task..............................................................67
7.1.3 [ALL] Deleting a Measurement Task................................................................68
7.1.4 [ALL] Copying a Measurement Task................................................................69
7.1.5 [ALL] Suspending a Measurement Task..........................................................70
7.1.6 [ALL] Activating a Measurement Task..............................................................71
7.1.7 [ALL] Viewing the Task Information..................................................................72
7.1.8 [ALL] Checking the Consistency Status of a Task............................................73
7.1.9 [ALL] Synchronizing Measurement Tasks........................................................74
7.1.10 [ALL] Synchronizing the Measurement Tasks with the Lower System.............75
7.1.11 [ALL] Exporting and Importing Measurement Tasks.........................................76
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.1.12 [ALL] Measurement Task Integrity...................................................................77
7.2 Counter and Index Management......................................................................79
7.2.1 [ALL] Viewing an Index....................................................................................79
7.2.2 [ALL] Creating an Index...................................................................................80
7.2.3 [ALL] Modifying an Index..................................................................................81
7.2.4 [ALL] Deleting an Index....................................................................................82
7.3 Threshold Task Management..........................................................................83
7.3.1 [ALL] Creating a Threshold Task......................................................................83
7.3.2 [ALL] Modifying a Threshold Task....................................................................84
7.3.3 [ALL] Activating a Threshold Task....................................................................85
7.3.4 [ALL] Suspending a Threshold Task................................................................86
7.3.5 [ALL] Deleting a Threshold Task......................................................................87
7.4 Common Template Management.....................................................................88
7.4.1 [ALL] Creating a Common Template................................................................88
7.4.2 [ALL] Modifying a Common Template..............................................................89
7.4.3 [ALL] Deleting a Common Template................................................................90
7.5 [ALL] Query Template Management................................................................91
7.6 [ALL] Template Task Management..................................................................93
7.7 [ALL] History Performance Query....................................................................94
7.8 [ALL] History Performance Monitoring.............................................................95
7.9 [ALL] Real-time Performance Monitoring.........................................................96
7.10 [ALL] Data Integrity Query................................................................................97
7.11 [ALL] Group Management................................................................................98
8 Inventory Management..................................................................................99
8.1 Inventory Data Query.......................................................................................99
8.1.1 [ALL] Querying Hardware Inventory.................................................................99
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
8.1.2 [ALL] Querying Software Inventory................................................................100
8.1.3 [ALL] Querying the Usage of Software Inventory...........................................101
8.2 Inventory Data Statistics................................................................................103
8.2.1 [ALL] Counting Hardware Inventory by Object...............................................103
8.2.2 [ALL] Counting Software Inventory.................................................................104
8.3 Inventory Information Export and Import........................................................105
8.3.1 [ALL] Exporting Inventory Data (XLS, CSV, and XML)...................................105
8.3.2 [ALL] Importing Inventory Data (XLS, CSV, and XML)...................................106
8.4 Inventory Data Synchronization.....................................................................107
8.4.1 [ALL] Synchronizing Hardware and Software Inventory Manually..................107
8.5 Spare Parts Management..............................................................................108
8.5.1 [ALL] Changing the Status of a Spare Part....................................................108
9 Configuration Management.........................................................................110
9.1 MML Terminal................................................................................................110
9.1.1 [ALL] MML Terminal.......................................................................................110
9.2 Wireless Configuration Application.................................................................111
9.2.1 [GUT] NE Relation Management....................................................................111
9.2.2 [GUTLL] Maintenance Status Query and Setting...........................................112
9.2.3 [GUT] VIP NodeB Priority Query and Setting.................................................113
9.2.4 [GUT] Site Transfer........................................................................................115
9.2.5 [GU] CBC Management.................................................................................117
9.2.6 [GUTLL] CM Data Collection..........................................................................118
9.2.7 [GUT] Interconnection Parameter Management.............................................120
9.3 NE Management............................................................................................122
10 Security Management..................................................................................123
10.1 [ALL] Role Management................................................................................123
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
10.2 [ALL] User Management................................................................................124
10.3 [ALL] User Popular Functions........................................................................125
10.4 [ALL] Log Management..................................................................................126
11 Maintenance Management..........................................................................127
11.1 System Backup..............................................................................................127
11.1.1 [ALL] Backup Task.........................................................................................127
11.1.2 [ALL] Restoration Task...................................................................................129
11.2 System Monitoring.........................................................................................130
11.2.1 [ALL] Server Monitoring.................................................................................130
11.2.2 Database Monitoring......................................................................................131
11.3 Task Management.........................................................................................134
11.3.1 [ALL] Modifying the Task Time.......................................................................134
11.3.2 [ALL] Historical Data Archiving.......................................................................135
11.3.3 [ALL] Basic Data/Whole DB Structure/File Backup........................................136
11.3.4 [ALL] File Clean-up........................................................................................137
11.3.5 [ALL] Automatically Acknowledging History Alarms.......................................138
11.3.6 [ALL] MML Timing Task.................................................................................139
12 Northbound Interface...................................................................................140
12.1 CORBA Interface...........................................................................................141
12.1.1 [GUTLLNAG] CORBA Process Check...........................................................141
12.1.2 [GUTLL] Obtaining IOR Files.........................................................................142
12.2 [GTLL] Socket Interface.................................................................................143
12.3 [GULLNAG] DB Interface...............................................................................145
12.4 [GUT] Network Planning and Optimization Interface......................................147
12.5 [GULLN] File Interface Customization Tool....................................................148
12.6 [LLN] CTCC I1 Interface.................................................................................150
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
12.7 [ALL] SNMP Interface....................................................................................151
12.8 [TLLN] CMCC New Socket Interface..............................................................154
12.9 [LLN] CTCC I1 Socket Interface.....................................................................155
13 LTE SON.......................................................................................................157
13.1 General Requirements of SON Policy Management......................................157
13.1.1 [LTE] Logging in to SON Policy Management................................................157
13.1.2 [LTE] Creating SON Policy Template.............................................................158
13.1.3 [LTE] Setting SON Policy Template...............................................................159
13.2 [LTE] Configuring the SON Breakpoint..........................................................159
13.3 [LTE] Triggering the SON Breakpoint.............................................................160
13.4 [LTE] Recovering the SON Breakpoint...........................................................161
13.5 [LTE] Viewing the SON Breakpoint................................................................162
14 Inspection Tool Test (V1)............................................................................163
14.1 [GUTFTL] Connecting to the Inspection Equipment.......................................163
14.2 [GUTFTL] Scene Management......................................................................164
14.3 Inspection Task..............................................................................................165
14.3.1 [GUTFTL] Creating a Task.............................................................................165
14.3.2 [GUTFTL] Viewing a Task..............................................................................166
14.3.3 [GUTFTL] Modifying a Task...........................................................................167
14.3.4 [GUTFTL] Activating a Task...........................................................................168
14.3.5 [GUTFTL] Deleting a Task.............................................................................168
14.4 [GUTFTL] Report Management......................................................................169
14.5 [GUTFTL] Fault Collection Management........................................................170
15 Inspection Tool Test (V2)............................................................................171
15.1 [ALL] Connecting to the Inspection Equipment..............................................171
15.2 [ALL] Scene Management..............................................................................172
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
15.3 Inspection Task..............................................................................................173
15.3.1 [ALL] Creating a Task....................................................................................173
15.3.2 [ALL] Viewing a Task.....................................................................................174
15.3.3 [ALL] Modifying a Task...................................................................................175
15.3.4 [ALL] Activating a Task..................................................................................176
15.3.5 [ALL] Deleting a Task.....................................................................................177
15.4 [ALL] Report Management.............................................................................178
16 Controller NE Management.........................................................................179
16.1 Configuration Management............................................................................179
16.1.1 [GUT] Logging in to Configuration Management............................................179
16.1.2 [GUT] Creating an NE....................................................................................180
16.1.3 [GUT] Applying for/Releasing the Mutex Right...............................................181
16.1.4 [GUT] Viewing the NE Information.................................................................182
16.1.5 [GUT] Modifying the NE Information..............................................................183
16.1.6 [GUT] Synchronizing All/Modified Tables.......................................................184
16.1.7 [GUT] Data Backup........................................................................................185
16.1.8 [GUT] Deleting an NE....................................................................................186
16.1.9 [GUT] Data Recovery.....................................................................................187
16.2 Software Version Management (V3)..............................................................188
16.2.1 [GUT] Logging in to Software Version Management......................................188
16.2.2 [GUT] Creating a Version Package................................................................189
16.2.3 [GUT] Viewing a Software Version.................................................................190
16.2.4 [GUT] Downloading a Version Package.........................................................191
16.2.5 [GUT] Activating a Version Package..............................................................192
16.3 Software Version Management (V4)..............................................................193
16.3.1 [GUAM] Logging in to Software Version Management...................................193
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
16.3.2 [GUAM] Downloading a Version Package......................................................194
16.3.3 [GUAM] Viewing a Software Version..............................................................195
16.3.4 [GUAM] Validating a Software Version..........................................................196
16.4 [GUAM] Status Management.........................................................................196
17 BS NE Management.....................................................................................198
17.1 Configuration Management............................................................................198
17.1.1 [ALL] Exporting the BS Data..........................................................................198
17.1.2 [ALL] Importing the BS Data..........................................................................199
17.1.3 [ALL] Synchronizing All/Modified Tables of BS..............................................200
17.1.4 [ALL] Comparing the Configuration Data........................................................201
17.1.5 [ALL] Uploading Configuration Data from NEs...............................................202
17.2 SDR Software Version Management.............................................................203
17.2.1 [ALL] Logging in to Software Version Management.......................................203
17.2.2 [ALL] Version Repository Management..........................................................204
17.2.3 [ALL] Upgrade Task Management.................................................................205
17.2.4 [ALL] Query Task Management.....................................................................206
17.2.5 [ALL] Special Task Management...................................................................207
17.3 [GUT] [N] SDR Dynamic Data Management..................................................209
18 Software Management.................................................................................210
18.1 Version Management.....................................................................................210
18.1.1 [ALL] Querying a Registered Software Version..............................................210
18.1.2 [ALL] Registering a Software Version on EMS...............................................211
18.2 One-Touch Upgrade......................................................................................212
18.2.1 [ALL] Creating a One-Touch Upgrade Task...................................................212
18.2.2 [ALL] Executing a One-Touch Upgrade Task.................................................214
18.2.3 [ALL] Alarm/NE Status Collection and Comparison Task...............................215
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
18.2.4 [ALL] KPI Comparison Task...........................................................................216
19 System Tool..................................................................................................218
19.1 Signaling Trace..............................................................................................218
19.1.1 [ALL] Cell Signaling........................................................................................218
19.1.2 [ALL] IMSI Signaling......................................................................................219
20 HA Test......................................................................................................... 221
20.1 Manual HA Switchover Test...........................................................................221
20.2 Plugging out an Ethernet Cable Will Not Cause HA Switchover.....................222
20.3 Stopping the EMS Application to Simulate the Fault......................................223
20.4 Stopping a Blade Server to Simulate the Server Hardware Fault...................225
20.5 Master/slave Data Synchronization Status Can Be Displayed in the DR
Environment..................................................................................................227
20.6 Master-slave Switchover Test in the DR Scenario.........................................228
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1 Test Guide
This test guide is mainly used to guide the acceptance test of the OMC software
function. It contains the partial contents of the server hardware and software test. The
user can cut some contents according to the needs of the project in the field.
2 Server Hardware Test
2.1 HP Hardware Test
2.1.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Item No.: 2.1.1 Test Object: Hardware Server
Test Item: Server Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
Test Procedure:
HP Blade Server Startup Method:
1) Log in to the OA management interface through your browser.
2) Select the blade server to be started, and click the Momentary Press button in the
Virtual Devices window.
Expected Result:
1) The system can be powered on and start up.
2) The indicator of the server power is in the normal status.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
2.1.2 Adapter Module Function Test
Test Content: Test whether the functions of the adapter module are normal.
Test No.: 2.1.2 Test Object: Hardware Server
Test Item: Server Test Sub-item: Adapter Module
Input Parameter: None
Prerequisites:
1) The adapter module installation is completed.
2) The server starts up normally. View the adapter information with the ifconfig
command, and the server IP should be in the same subnet as the laptop IP.
3) Connect the server adapter with the laptop adapter, and test the functions of the
adapters one by one.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Check the indicator status of the adapter on the server.
2) Perform ping packet test on the client to see whether the client is ping-reachable and
whether there is packet loss.
Expected Result:
1) The adapter connection indicator is ON in green, or the adapter connection indicator
is ON in green and the data transmission indicator is ON in orange.
2) The adapter is ping-reachable and there is no packet loss.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
2.1.3 HBA Module Function Test
Test Content: Test whether the functions of the HBA module are normal.
Test No.: 2.1.3 Test Object: Hardware Server
Test Item: Server Test Sub-item: HBA Module
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) The HBA module installation is completed.
2) The server is started up successfully.
Test Procedure:
1) Check the indicator status of the HBA on the server.
2) Query the WMN number of the HBA on the server with commands. The following commands
are for reference:
The commands for redhat system:
a) View the WWN number of the HBA.
# more /sys/class/fc_host/host*/port_name
::::::::::::::
/sys/class/fc_host/host1/port_name
::::::::::::::
0x10000090fa6c04f4
::::::::::::::
/sys/class/fc_host/host2/port_name
::::::::::::::
0x10000090fa6c04f5
Expected Result:
1) The indicator of HBA is ON in green and flashes stably.
2) The unique HBA No. can be queried.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
2.1.4 Local Disk Function Test
Test Content: Test whether the functions of the local disk are normal.
Test No.: 2.1.4 Test Object: Hardware Server
Test Item: Server Test Sub-item: Local Disk
Input Parameter: None
Prerequisites:
1) The local disk is installed normally.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Start the server.
2) Check the indicator status of the local disk on the server.
3) Check whether the server is started up normally and whether there is hard disk
related error information. The following command is for reference:
redhat: Check the /var/log/message system log.
Expected Result:
1) The server can be started up successfully.
2) The hard disk indicator is ON in green.
3) There is no hardware error information in the /var/log/message system log.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2.1.5 Server CPU and Memory Checking
Test Content: Check whether the CPU and memory of the server are normal.
Test No.: 2.1.5 Test Object: Hardware Server
Test Item: Server Sub-item: CPU and Memory
Input Parameter: None
Prerequisites:
1) The CPU and the memory bank are installed properly.
Test Procedure:
1) Start the server.
2) Query the number of CPUs. The following command is for reference:
Redhat:
View the number of CPUs with the cat /proc/cpuinfo | grep "physical
id" | sort | uniq | wc -l command.
3) Query the size of the memory with the following command:
Redhat:
cat /proc/meminfo |grep MemTotal
Expected Result:
1) The server can be started up successfully.
2) The queried number of CPUs is consistent with the actual number and the CPU
utilization rate is normal.
3) The memory size is consistent with the actual size of the memory bank when it is
installed and the memory size utilization rate is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
2.2 E9000 Hardware Test
2.2.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 2.2.1 Test Object: Hardware Server
Test Item: Server Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
E9000 Blade Server Startup Method:
a) Log in to the OA management interface through your browser.
b) Select the blade server to be started, and click Go to iSAC > KVM > Start
KVM.
2.2.2 Adapter Module Function Test
Test Content: Test whether the functions of the adapter module are normal.
Test No.: 2.2.2 Test Object: Hardware Server
Test Item: Server Test Sub-item: Adapter Module
Input Parameter: None
Prerequisites:
1) The adapter module installation is completed.
2) The server starts up normally. View the adapter information with the ifconfig
command, and the server IP should be in the same subnet as the laptop IP.
3) Connect the server adapter with the laptop adapter, and test the functions of the
adapters one by one.
Test Procedure:
1) Check the indicator status of the adapter on the server.
2) Perform ping packet test on the client to see whether the client is ping-reachable and
whether there is packet loss.
Expected Result:
1) The adapter connection indicator is ON in green, or the adapter connection indicator
is ON in green and the data transmission indicator is ON in orange.
2) The adapter is ping-reachable and there is no packet loss.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
2.2.3 HBA Module Function Test
Test Content: Test whether the functions of the HBA module are normal.
Test No.: 2.2.3 Test Object: Hardware Server
Test Item: Server Test Sub-item: HBA Module
Input Parameter: None
Prerequisites:
1) The HBA module installation is completed.
2) The server is started up successfully.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Check the indicator status of the HBA on the server.
2) Query the WWN number of the HBA on the server with commands. The following
commands are for reference:
Reference Commands for CGSL OS:
a) View the WWN number of the HBA.
# more /sys/class/fc_host/host*/port_name
::::::::::::::
/sys/class/fc_host/host1/port_name
::::::::::::::
0x10000090fa6c04f4
::::::::::::::
/sys/class/fc_host/host2/port_name
::::::::::::::
0x10000090fa6c04f5
Expected Result:
1) The indicator of HBA is ON in green and flashes stably.
2) The unique HBA No. can be queried.
2.2.4 Local Disk Function Test
Test Content: Test whether the functions of the local disk are normal.
Test No.: 2.2.4 Test Object: Hardware Server
Test Item: Server Test Sub-item: Local Disk
Input Parameter: None
Prerequisites:
1) The local disk is installed normally.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Start the server.
2) Check the indicator status of the local disk on the server.
3) Check whether the server is started up normally and whether there is hard disk
related error information. The following command is for reference:
CGSL: Check the /var/log/message system log.
Expected Result:
1) The server can be started up successfully.
2) The hard disk indicator is ON in green.
3) There is no hardware error information in the /var/log/message system log.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2.2.5 Server CPU and Memory Checking
Test Content: Check whether the CPU and memory of the server are normal.
Test No.: 2.2.5 Test Object: Hardware Server
Test Item: Server Sub-item: CPU and Memory
Input Parameter: None
Prerequisites:
The CPU and the memory bank are installed properly.
Test Procedure:
1) Start the server.
2) Query the number of CPUs. The following command is for reference:
CGSL:
View the number of CPUs with the cat /proc/cpuinfo | grep "physical id" | sort |
uniq | wc -l command.
3) Query the size of the memory with the following command:
CGSL:
cat /proc/meminfo |grep MemTotal
Expected Result:
1) The server can be started up successfully.
2) The queried number of CPUs is consistent with the actual number and the CPU
utilization rate is normal.
3) The memory size is consistent with the actual size of the memory bank when it is
installed and the memory size utilization rate is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3 Disk Array Hardware Test
3.1 HP Disk Array Hardware Test
3.1.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 3.1.1 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Turn on the power module switches of the two RNCs at the rear of the disk array.
2) If expansion cabinet is used, power on the expansion cabinet first, and then power
on the primary cabinet. The power-down should be made in the reverse sequence,
i.e., power down the primary cabinet first and then the expansion cabinet.
Expected Result:
1) The disk array can be powered on and the indicator is in the normal status.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.1.2 Disk Function Test
Test Content: Test whether the disk functions of the disk array are normal.
Test No.: 3.1.2 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Disk
Input Parameter: None
Prerequisites:
1) The disk array is installed properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Power on the disk array.
2) Check the indicator status of the disk array on the server.
3) Check whether there are critical alarms through the disk array software
management.
Expected Result:
1) The hard disk indicator is ON in green.
2) There are no critical alarms displayed in the disk array software management.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.2 KS3200 Disk Array Hardware Test
3.2.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 3.2.1 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Power Module
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
Test Procedure:
1) Turn on the power module switches of the two RNCs at the rear of the disk array.
2) If expansion cabinet is used, power on the expansion cabinet first, and then power
on the primary cabinet. The power-down should be made in the reverse sequence,
i.e., power down the primary cabinet first and then the expansion cabinet.
Expected Result:
1) The disk array can be powered on and the indicator is in the normal status.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.2.2 Disk Function Test
Test Content: Test whether the disk functions of the disk array are normal.
Test No.: 3.2.2 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Disk
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) The disk array is installed properly.
Test Procedure:
1) Power on the disk array.
2) Check the indicator status of the disk array on the server.
3) Check whether there are critical alarms through the disk array software
management.
Expected Result:
1) The hard disk indicator is ON in green.
2) There are no critical alarms displayed in the disk array software management.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3.3 EMC 3200 Disk Array Hardware Test
3.3.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 3.3.1 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
Test Procedure:
1) Turn on the power module switches of the two RNCs at the rear of the disk array.
2) If expansion cabinet is used, power on the expansion cabinet first, and then power
on the primary cabinet. The power-down should be made in the reverse sequence,
i.e., power down the primary cabinet first and then the expansion cabinet.
Expected Result:
1) The disk array can be powered on and the indicator is in the normal status.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
3.3.2 Disk Function Test
Test Content: Test whether the disk functions of the disk array are normal.
Test No.: 3.3.2 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Disk
Input Parameter: None
Prerequisites:
1) The disk array is installed properly.
Test Procedure:
1) Power on the disk array.
2) Check the indicator status of the disk array on the server.
3) Check whether there are critical alarms through the disk array software
management.
Expected Result:
1) The hard disk indicator is ON in green.
2) There are no critical alarms displayed in the disk array software management.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
3.4 IBM 3700 Disk Array Hardware Test
3.4.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 3.4.1 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
Test Procedure:
1) Turn on the power module switches of the two RNCs at the rear of the disk array.
2) If expansion cabinet is used, power on the expansion cabinet first, and then power
on the primary cabinet. The power-down should be made in the reverse sequence,
i.e., power down the primary cabinet first and then the expansion cabinet.
Expected Result:
1) The disk array can be powered on and the indicator is in the normal status.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.4.2 Disk Function Test
Test Content: Test whether the disk functions of the disk array are normal.
Test No.: 3.4.2 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Disk
Input Parameter: None
Prerequisites:
1) The disk array is installed properly.
Test Procedure:
1) Power on the disk array.
2) Check the indicator status of the disk array on the server.
3) Check whether there are critical alarms through the disk array software
management.
Expected Result:
1) The hard disk indicator is ON in green.
2) There are no critical alarms displayed in the disk array software management.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.5 KU5200 Disk Array Power-down Test
3.5.1 Power Module Function Test
Test Content: Test whether the functions of the power module are normal.
Test No.: 3.5.1 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Power Module
Input Parameter: None
Prerequisites:
1) The power module installation is completed.
2) The cable routing is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Turn on the power module switches of the two RNCs at the rear of the disk array.
2) If expansion cabinet is used, power on the expansion cabinet first, and then power
on the primary cabinet. The power-down should be made in the reverse sequence,
i.e., power down the primary cabinet first and then the expansion cabinet.
Expected Result:
1) The disk array can be powered on and the indicator is in the normal status.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
3.5.2 Disk Function Test
Test Content: Test whether the disk functions of the disk array are normal.
Test No.: 3.5.2 Test Object: Disk Array
Test Item: Disk Array Test Sub-item: Disk
Input Parameter: None
Prerequisites:
The disk array is installed properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Power on the disk array.
2) Check the indicator status of the disk array on the server.
3) Check whether there are critical alarms through the disk array software
management.
Expected Result:
1) The hard disk indicator is ON in green.
2) There are no critical alarms displayed in the disk array software management.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
4 Online Help
4.1 Online Help
Test Content: Check that the online help is available.
Test No.: 2.1 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: Online Help Test Sub-item: Online Help
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Press F1 or select the help option from the main menu.
Expected Results:
1) The Alarm Monitoring tab can be displayed.
2) The displayed help dialog box is relevant with the current view.
3) If there is no current view, the UEMS profile will be displayed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
5 Topology Management
5.1 Topology View Management
5.1.1 [ALL] Viewing the Topology
Test Content: Check that the topology view can be displayed.
Test No.: 3.1.1 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Viewing the Topology
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Switch to another view.
3) Select Topology > View Topology from the menu.
Expected Results:
1) After you log in to the client, the system will enter the topology view by default.
2) The topology view can be switched back to another view.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.1.2 [ALL] Refreshing the Data
Test Content: Check that the topology view can be refreshed.
Test No.: 3.1.2 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Refreshing the Data
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Refresh Data from the menu.
Expected Results:
1) The client will perform the topology refreshing automatically and the successful
information will be displayed on the Show Message tab page.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.1.3 [ALL] Statistics Topology
Test Content: Check that the statistical information is right.
Test No.: 3.1.3 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Statistics Topology
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Show Statistics Topology from the menu.
Expected Results:
1) The correct statistics data is shown in the opened window pane.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.1.4 [ALL] Configuring Coordinate Synchronization
Test Content: Check that the function of configuring coordinate synchronization works properly.
Test No.: 3.1.4 Test Object: NetNumen U31 R18
Test Sub-item: Configuring Coordinate
Test Item: Topology View Management
Synchronization
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Configure Coordinate Synchronization from the menu.
3) When Yes is selected, the coordinate of the local-level NE is synchronized with that
of the NE agent. Choose an NE from the Topology view, move it to another
position, and then click Save Position.
4) Choose the NE agent from the topology tree, and select NE Agent Management >
Synchronize Configuration. When the configuration synchronization is finished,
view the NE (configured in Step 3) position from the Topology view. The NE
coordinate is moved back to the original position.
5) When No is selected, the coordinate of the local-level NE is not synchronized with
that of the NE agent. Choose an NE from the Topology view, move it to another
position, and then click Save Position.
6) Choose the NE agent from the topology tree, select NE Agent Management >
Synchronize Configuration. When the configuration synchronization is finished,
view the NE (configured in Step 5) position from the topology view. The NE
coordinate remains unchanged.
Expected Results:
1) The function of configuring coordinate synchronization is proper.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.5 [ALL] Customizing GUI Elements
Test Content: Check that the GUI elements can be customized.
Test No.: 3.1.5 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Customizing GUI Elements
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Display Style Management > Customize GUI Elements from
the menu. The Customize GUI Elements window is displayed.
3) Customize the GUI elements and then click OK.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) GUI elements are customized successfully, and the topology view is displayed by
customization.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.6 [ALL] Exporting the GUI Display Style
Test Content: Check that the GUI display style can be exported.
Test No.: 3.1.6 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Exporting the GUI Display Style
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Display Style Management > Export GUI Display Style from
the menu. The Save dialog box is displayed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) In the displayed dialog box, set the path and file name, and then click Save.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
1) The GUI display style can be exported successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.7 [ALL] Importing the GUI Display Style
Test Content: Check that the GUI display style can be imported.
Test No.: 3.1.7 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Importing the GUI Display Style
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Select Topology > Display Style Management > Import GUI Display Style from
the menu.
3) The Open dialog box is displayed. Select the file to be imported and then click
Open.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
1) The correct GUI display style file can be imported successfully and displayed
normally, and is consistent with the export style.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.8 [ALL] Setting the Alarm Display Style
Test Content: Check that the alarm display style can be set.
Test No.: 3.1.8 Test Object: NetNumen U31 R18
Test Item: Topology View Management Test Sub-item: Setting the Alarm Display Style
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select Topology > Set Alarm Display Style > Show NE Alarms Table from the
menu. The alarms table below the topology is switched to the NE alarms table.
3) Select Topology > Set Alarm Display Style > Show Important Alarms Table from
the menu. The alarms table below the topology is switched to the primarily
monitored alarms table.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
1) The alarm display style is set successfully. The content of alarm monitoring
displayed in the topology management window is displayed as set by the user.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.9 [ALL] Searching Cell
Test Content: Check that the serving cell can be searched.
Test No.: 3.1.9 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: Topology View Management Test Sub-item: Searching Cell
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly, and the user is authorized to perform
cell searching operations.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Right-click the EMS server node in the NE tree, and select Topology Management
> Search Cell from the displayed shortcut menu. The Search Cell window is
displayed.
3) Set the relevant parameters, such as cell name and BS name in the displayed
window.
4) Click Search, and check whether the displayed content of the cell can match the
specified query conditions.
5) Right-click one record of the cell and select Show Topo App View from the
displayed shortcut menu. Then, check the detailed information of the cell in the view.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) The relevant query conditions can be set in the window.
3) The cell information that matches the specified query conditions is shown on the
client.
4) The cell’s icon is displayed in the cell component diagram, and the cell’s detailed
information can be viewed.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.1.10 [ALL] Displaying Global BS Statistical Information
Test Content: Check that the function of displaying global BS statistical information works properly.
Test No.: 3.1.10 Test Object: NetNumen U31 R18
Test Sub-item: Displaying Global BS Statistical
Test Item: Topology View Management
Information
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly, and the user is authorized to perform
topology viewing operations.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Click Topology > Display Global BS Statistical Information on the menu bar to
open the Display Global BS Statistical Information window.
3) The total number of BSs, the number of enabled BSs, the number of tested BSs, the
number of alarmed BSs, and the number of link-broken BSs are displayed.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) The statistics of global BS data is successful, and the total number of BSs, the
number of enabled BSs, the number of tested BSs, the number of alarmed BSs, and
the number of link-broken BSs are consistent with the actual situation.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
5.1.11 [ALL] Creating/Activating an NE Agent Using MML Command
Test Content: Check that the function of creating/activating an NE agent using MML command
works properly.
Test No.: 3.1.11 Test Object: NetNumen U31 R18
Test Sub-item: Creating/Activating an NE Agent
Test Item: Topology View Management
Using MML Command
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly, and the user is authorized to perform
topology viewing operations.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Click Configuration > MML Terminal > Open MML Terminal from the main menu.
The MML terminal window is displayed.
3) Enter the command for creating NE agent to create an NE agent:
CREATEOMM:MOC="gv3.omm",NAME="gsmomm7",TIMEZONE="0",IPADDRESS="10.62.44.77",
PORT="21",FTPPORT="20021",VENDOR="0",LOCATION="0",MEMO="0",EMSIP="10.62.44.31",E
MSIPRESERVE="10.62.44.28",SSHPORT="0",MINOSSLAVE="minosslave1".
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Parameter Meaning:
MOC means MOC value of each product, and cannot be null.
NAME means the name of NE agent, and cannot be null.
TIMEZONE must be filled in according to the required format, and can also be filled in with “0”,
meaning the default time zone.
IPADDRESS means the IP address of the lower-level system, and cannot be null.
PORT and FTPPORT means the port of the lower-level system, and cannot be null.
EMSIP means the IP address of EMS, and cannot be null.
The following parameters are optional parameters. These parameters can be excluded in the
command, but once they are included, their value cannot be null:
VENDOR, LOCATION, SSHPORT, MINOSSLAVE, and MEMO.
4) Enter the command for activating NE agent to activate an NE agent
ACTIVATEOMM:AMOID="OMMOID=i44v5hvv-5"
Parameter meaning:
AMOID means AMOID of the NE agent, and cannot be null, using “OMMOID=” as the prefix.
Expected Results:
1) After the command for creating NE agent is executed successfully, a success
message is displayed, and AMOID of the NE agent is displayed.
2) The command for activating NE agent is executed successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.1.12 [ALL] Displaying BBU/RRU/RSU Information
Test Content: Check that the function of displaying BBU/RRU/RSU information works properly.
Test No.: 3.1.12 Test Object: NetNumen U31 R18
Test Sub-item: Displaying BBU/RRU/RSU
Test Item: Topology View Management
Information
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly, and the user is authorized to search
cells.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Right-click the NodeB NE node in the NE tree, and select Display BBU/RRU/RSU
Information from the displayed shortcut menu to open the display interface.
3) BBU/RRU/RSU information is displayed in the topology view.
Expected Results:
1) The login is successful and the Topology Management view can be opened.
2) The BBU/RRU/RSU information related to the NodeB is displayed in the topology
view.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2 NE Agent Management
5.2.1 [ALL] Creating an NE Agent
Test Content: Check that an NE agent can be created.
Test No.: 3.2.1 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Creating an NE Agent
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Right-click the EMS server node in the NE tree, and select Create Object >
Basestation > Multi-mode > MO SDR NE Agent from the displayed shortcut menu.
Enter the relevant parameters in the MO SDR NE Agent window.
3) Click OK to exit.
Expected Results:
1) The MO SDR NE Agent is created successfully and it can be viewed on the topology
map.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2.2 [ALL] Starting an NE Agent
Test Content: Check that an NE agent can be started.
Test No.: 3.2.2 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Starting an NE Agent
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE Agent has been created.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select a stopped NE agent node from the NE topology tree, right-click it and select
NE Agent Management > Start from the displayed shortcut men.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Check the operation result at the client. If the operation fails, an error message will
be given. If it is successful, the NE agent status on the topology map will be shown
as Started.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2.3 [ALL] Stopping an NE Agent
Test Content: Check that an NE agent can be stopped.
Test No.: 3.2.3 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Stopping an NE Agent
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE Agent has been created, and the NE agent has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Select an activated NE agent node from the NE topology tree, right-click it and select
NE Agent Management > Stop from the displayed shortcut men. Click OK when
you are asked to confirm the action.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) Check the operation result at the client. If the operation fails, an error message will
be given. If it is successful, the NE Agent icon on the topology map will turn grey
(the color can be customized via the interface element customization function).
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2.4 [ALL] Modifying an NE Agent
Test Content: Check that an NE agent can be modified.
Test No.: 3.2.4 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Modifying an NE Agent
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
function is available.
3) An NE agent has been created, and the NE Agent is in the status of stopped.
Test Procedure:
1) Log in to the client and open the Topology Management window.
2) Select a stopped NE agent node from the NE topology tree, right-click it and select
NE Agent Management > Modify from the displayed shortcut menu. When the
parameter window is opened, modify the relevant parameters and then click OK.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) The NE agent can be modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2.5 [ALL] Deleting an NE Agent
Test Content: Check that an NE agent can be deleted.
Test No.: NE Agent Management Test Object: NetNumen U31 R18
Test Item: 3.2.5 Test Sub-item: Deleting an NE Agent
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE agent has been created.
Test Procedure:
1) Log in to the client and open the Topology Management window.
2) Select an NE Agent node from the NE topology tree, right-click it and select NE
Agent Management > Delete from the displayed shortcut men. Press OK when you
are asked to confirm the deletion.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) The NE agent can be deleted successfully and it can be found deleted from the
topology tree.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
5.2.6 [ALL] Viewing an NE Agent
Test Content: Check that NE agent information can be viewed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 3.2.6 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Viewing an NE Agent
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE agent has been created.
Test Procedure:
1) Log in to the client and open the Topology Management window.
2) Select an NE Agent node from the NE topology tree, right-click it and select NE
Agent Management > View from the displayed shortcut menu.
Expected Results:
1) The login is successful and the Topology Management window can be opened.
2) The NE agent can be shown successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
5.2.7 [ALL] Synchronizing the Configuration
Test Content: Check that the function of synchronizing the configuration works properly.
Test No.: 3.2.7 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Synchronizing the Configuration
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE agent has been created, and the NE agent has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node from the NE topology tree, right-click it and
select NE Agent Management > Synchronize Configuration from the displayed
shortcut menu. Press YES when you are asked to confirm the action.
Expected Results:
1) The user can log in to the client and open the Topology Management view.
2) The configuration has been synchronized successfully, and the success information
is displayed in the Info area.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
5.2.8 [ALL] Querying the Operation Problem
Test Content: Check that the function of querying NE agent operation problem works properly.
Test No.: 3.2.8 Test Object: NetNumen U31 R18
Test Item: NE Agent Management Test Sub-item: Querying the Operation Problem
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The client is connected to the server properly and the Topology Management
function is available.
3) An NE agent has been activated.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node from the NE topology tree, right-click it and
select NE Agent Management > Query Operation Problem from the displayed
shortcut menu. Press OK when you are asked to confirm the action.
3) The reasons for the NE agent operation problem are displayed. Click Operation
Problem and select Clear. The NE agent operation problem can be cleared.
Expected Results:
1) The user can log in to the client and open the Topology Management view.
2) The NE agent operation problem has been queried successfully.
3) The NE agent operation problem can be cleared normally.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6 Fault Management
6.1 Alarm Monitoring
6.1.1 [ALL] Active Alarm Monitoring
Test Content: Check that active alarms can be monitored in real time.
Test No.: 4.1.1 Test Object: NetNumen U31 R18
Test Item: Alarm Monitoring Test Sub-item: Active Alarm Monitoring
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Alarm Monitoring from the Fault menu. The Alarm Monitoring page
appears.
2) View the total number of alarms displayed on the Alarm Monitoring page, on which
the alarms are displayed in real time. Moreover, view the total number of alarms of a
specific severity and the details of the alarms.
3) If a new alarm is generated by the NE, check that the alarms are displayed in the
Alarm Monitoring view.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) When clearing the alarm, check that the alarms are displayed on the History
Alarms page.
Expected Results:
1) The Alarm Monitoring page can be displayed.
2) The user can view the generated alarms in real time through the client.
3) If a new alarm is generated by the NE, the alarms are displayed on the Alarm
Monitoring page.
4) When clearing the alarm, the alarms are displayed on the History Alarms page.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.1.2 [ALL] Active Notification Monitoring
Test Content: Check that a notification can be monitored in real time.
Test No.: 4.1.2 Test Object: NetNumen U31 R18
Test Item: Alarm Monitoring Test Sub-item: Active Notification Monitoring
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Notification Monitoring from the Fault menu. The Notification Monitoring
page appears.
2) View the total number of notifications displayed on the Notification Monitoring
page on which notifications are displayed in real time. Moreover, view the total
number of notifications of a specific severity and the details of a notification.
Expected Results:
1) The Notification Monitoring page can be displayed.
2) The user can view the generated notification in real time through the client.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.1.3 [ALL] Active Alarm Statistics Monitoring
Test Content: Check that active alarms statistics can be monitored in real time.
Test No.: 4.1.3 Test Object: NetNumen U31 R18
Test Sub-item: Active Alarm Statistics
Test Item: Alarm Monitoring
Monitoring
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Alarm Monitoring by NE and Alarm Monitoring by NE type from the Fault
menu. The Alarm Monitoring by NE or the Alarm Monitoring by NE type appears.
2) View the total number of alarms displayed on the Alarm Statistics Monitoring
page, on which the alarms are displayed in real time. Moreover, view the total
number of alarms of a specific severity.
Expected Results:
1) The Alarm Monitoring by NE page or the Alarm Monitoring by NE type page can
be displayed.
2) The user can view the number of alarms in real time through the client.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
6.2 Alarm Query
6.2.1 [ALL] Active Alarm Query
Test Content: Check that active alarms can be queried by combined conditions.
Test No.: 4.2.1 Test Object: NetNumen U31 R18
Test Item: Alarm Query Test Sub-item: Active Alarm Query
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Query Active Alarms from the main menu of Fault. The Query Active
Alarms page appears.
2) Set the query condition including the alarm generation location, alarm code, alarm
severity, alarm type, alarm raised time, alarm (un) ack time, ack state, and NE IP.
3) Click OK and check that the alarms displayed on the Query Active Alarms page
can match the specified search condition.
Expected Results:
1) The user can log in to the client and open the Query Active Alarms view.
2) The active alarms that match the specified condition are shown on the client.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
6.2.2 [ALL] History Alarm Query
Test Content: Check that history alarms can be queried by combined conditions.
Test No.: 4.2.2 Test Object: NetNumen U31 R18
Test Item: Alarm Query Test Sub-item: History Alarm Query
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm management operations.
Test Procedure:
1) Select Query History Alarms from the main menu of Fault. The Query History
Alarms page appears.
2) Set the query condition including the alarm generation location, alarm code, alarm
severity, alarm type, alarm raised time, alarm (un) ack time, ack state, and the
cleared time.
3) Click OK, and then check that the alarms displayed on the History Alarm page can
match the specified search condition.
Expected Results:
1) The user can log in to the client and open the History Alarm Query view.
2) The history alarms that match the specified condition are shown on the client.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.2.3 [ALL] Notification Query
Test Content: Check that a notification can be queried by combined conditions.
Test No.: 4.2.3 Test Object: NetNumen U31 R18
Test Item: Alarm Query Test Sub-item: Notification Query
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Query Notifications from the main menu of Fault. The Notification Query
page appears.
2) Set the location where notifications occur, notification codes, and the time when
notifications occur.
3) Click OK and check that the notifications displayed on the Notifications page can
match the specified search condition.
Expected Results:
1) The user can log in to the client and open the Notification Query view.
2) The notifications that match the specified condition are shown on the client.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3 Alarm Statistics
6.3.1 [ALL] History Alarm Basic Statistics
Test Content: Check that the function of history alarm basic statistics works properly.
Test No.: 4.3.1 Test Object: NetNumen U31 R18
Test Item: Alarm Statistics Test Sub-item: History Alarm Basic Statistics
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select History Alarm Basic Statistics from the main menu of Fault. The History
Alarm Basic Statistics page appears.
2) Set the statistics template and the filtering conditions of the history alarms. The basic
statistical conditions of alarms that meet the alarm conditions can be set according
to different statistical items and different statistical indicators.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) Click OK and check that the content displayed on the History Alarm Basic
Statistics page can match the specified search condition.
Expected Results:
1) The user can log in to the client and open the History Alarm Basic Statistics page.
2) The basic statistics that match the specified condition are shown on the client.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.2 [ALL] History Alarm Busy-time Statistics
Test Content: Check that the function of history alarm busy-time statistics works properly.
Test No.: 4.3.2 Test Object: NetNumen U31 R18
Test Sub-item: History Alarm Busy-time
Test Item: Alarm Statistics
Statistics
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) Select History Alarm Busy-time Statistics from the main menu of Fault. The
History Alarm Busy-time Statistics page appears.
2) Set the statistics template and the filtering conditions of the history alarms. The
busy-time statistics of alarms that meet the alarm conditions can be set according to
effective periods and statistical indicators.
3) Click OK and check that the content displayed on the History Alarm Busy-time
Statistics page can match the specified search condition.
Expected Results:
1) The user can log in to the client and open the History Alarm Busy-time Statistics
page.
2) The busy-time statistics that match the specified condition are shown on the client.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.3 [ALL] History Alarm Important Alarm-Code Statistics
Test Content: Check that the function of history alarm important alarm-code statistics works
properly.
Test No.: 4.3.3 Test Object: NetNumen U31 R18
Test Item: Alarm Statistics Test Sub-item: History Alarm Important Alarm-
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Code Statistics
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select History Alarm Important Alarm-Code Statistics from the main menu of
Fault. The History Alarm Important Alarm-Code Statistics dialog box is
displayed.
2) Set the alarm code and reporting time in the displayed window. History alarms that
meet the alarm conditions can be counted according to the settings.
3) Click OK and check whether the content displayed on the History Alarm Important
Alarm-Code Statistics page can match the selected conditions.
Expected Results:
1) The user can log in to the client and open the History Alarm Important Alarm-
Code Statistics page.
2) The important alarm code statistics of history alarms that match the specified
condition are shown on the client.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
6.3.4 [ALL] Timing Statistic Task Management
Test Content: Check that the function of the timing statistic task management works properly.
Test No.: 4.3.4 Test Object: NetNumen U31 R18
Test Sub-item: Timing Statistic Task
Test Item: Alarm Statistics
Management
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Timing Statistic Task Management from the main menu of Fault. The
Timing Statistic Task Management page appears.
2) Click the New button, the Statistic Task Management page appears.
3) Set the Statistics Template, Time, Task Status, File Type, Task Execution Plan,
Email Forward, and Ftp Push.
4) Click OK and check that the timing statistic task created appears on the Timing
Statistic Task Management page.
5) Check that the content displayed on the Timing Statistic Task Management page
can match the specified search condition.
6) For the active task, the statistic results appear in the results of the Timing Statistic
Task page when the execution begins.
7) Modify, activate, and suspend the existing task.
Expected Results:
1) The user can log in to the client and open the Timing Statistic Task Management
page.
2) A new timing statistics task can be created.
3) The timing statistics task can be automatically executed and the statistics results can
be automatically exported.
4) The timing statistics task can be modified, activated and suspended successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.5 [ALL] Timing Export Task Management
Test Content: Check that the function of timing export task management works properly.
Test No.: 4.3.5 Test Object: NetNumen U31 R18
Test Item: Alarm Statistics Test Sub-item: Timing Export Task Management
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Timing Export Task Management from the main menu of Fault. The
Timing Export Task Management page appears.
2) Click the New button, the Timing Export Task Management page appears.
3) Set the Output Type, Time, Task Status, File Type, Task Execution Plan, Ftp
Push, and Query Condition.
4) Click OK and check that the timing statistic task created appears on the Timing
Export Task Management page.
5) Check that the content displayed on the Timing Statistic Task Management page
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
can match the specified search condition.
6) For the active task, the results appear in the results of the Timing Export Task
page when the execution begins.
7) Modify, activate, and suspend the existing task.
Expected Results:
1) The user can log in to the client and open the Timing Export Task Management
page.
2) A new timing export task can be created.
3) The timing export task can be automatically executed and the timing export results
can be automatically exported.
4) The timing export task can be modified, activated and suspended successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.6 [ALL] Suppressing Plan Task Management
Test Content: Check that the function of suppressing plan task management works properly.
Test No.: 4.3.6 Test Object: NetNumen U31 R18
Test Item: Alarm Statistics Test Sub-item: Suppressing Plan Task
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Management
Input Parameter: none
Prerequisites:
1) Both EMS server and client operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operation.
Test Procedure:
1) Select Suppress Plan Task Management from the main menu of Fault. The
Suppress Plan Task Management tab is displayed.
2) Click the New button on the toolbar. The New Suppress Plan Task dialog box is
displayed.
3) Set Task Name, Task Type, Task Status, Task Period and NE etc.
4) Click OK and check whether the suppressing plan task created appears in the
Suppress Plan Task Management window.
5) Check whether the content displayed in the Suppress Plan Task Management
window can match the specified search conditions.
6) For a suppressing plan task in the status of activated, suppress the alarms
generated in the task period. If alarms that meet the task conditions are reported,
then the system generates a new alarm as the root alarm, and the reported alarms
are acted as the derivative alarms of the root alarm.
7) For the existing task, modify, activate, and suspend it.
Expected Results:
1) The user can log in to the client and open the Suppress Plan Task Management
tab.
2) A suppressing plan task can be created.
3) The suppressing plan task is executed regularly at the set time.
4) The suppressing plan task can be modified, activated, and suspended successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.7 [ALL] Alarm Panel
Test Content: Check that the function of alarm panel works properly.
Test No.: 4.3.7 Test Object: NetNumen U31 R18
Test Item: Alarm Statistics Test Sub-item: Alarm Panel
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
Test Procedure:
1) Select Alarm Panel from the main menu of Fault. The Alarm Panel window is
displayed, and the number of acknowledged alarms of each severity level and the
number of unacknowledged alarms of each severity level can be viewed in the
displayed window.
2) Click the flash button or the sound button on the GUI.
3) You can see the alarm icon on the GUI is flashing or hear the alarm sound.
Expected Results:
1) The user can log in to the client and open the Alarm Panel window, and can view
the number of acknowledged alarms of each severity level and the number of
unacknowledged alarms of each severity level.
2) The alarm mode flashing or sounding can be set on the GUI.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.3.8 [ALL] Site Alarm Statistics
Test Content: Check that the function of the site alarm statistics works properly.
Test No.: 4.3.8 Test Object: NetNumen U31 R18
Test Item: Alarm Management Test Sub-item: Site Alarm Statistics
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm viewing operations.
3) The VIP site, class B site or class C site has been set.
Test Procedure:
1) Select VIP Site Alarm Statistics, Class B Site Alarm Statistics, or Class C Site
Alarm Statistics from the main menu of Fault. The VIP Site Alarm Statistics page,
Class B Site Alarm Statistics page, or Class C Site Alarm Statistics page
appears.
2) View whether the VIP site, Class B site or Class C site screen display is consistent
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
with the configuration settings.
3) Check whether the summary of the current alarm on the VIP site, Class B site, or
Class C site of each time, and the number of alarms at various levels are consistent
with the alarm query result.
4) Double-click a line of site records, and open the corresponding list of the alarm data.
Expected Results:
1) The user can log in to the client and open the VIP Site Alarm Statistics page,
Class B Site Alarm Statistics page, or Class C Site Alarm Statistics page.
2) The VIP, Class B, or Class C site interface information and alarm information are
correct.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.4 Alarm Synchronization
6.4.1 [ALL] Synchronizing Active Alarms
Test Content: Check that the function of synchronizing active alarms works properly.
Test No.: 4.4.1 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: Alarm Synchronization Test Sub-item: Synchronizing Active Alarms
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Synchronize Active Alarm from the main menu of Fault. The Synchronize
Active Alarm page appears.
2) Set the NE location parameter information that needs to be synchronized from the
displayed window pane.
3) Check that the alarm synchronization information is sent successfully. After
synchronization, the active alarms displayed by the client are consistent with those
on the NE.
Expected Results:
1) The user can log in to the client and open the Synchronize Active Alarm page.
2) Set the NE location parameter information that needs to be synchronized from the
displayed window pane
3) The system can be synchronized with the specified NEs.
4) The client prompts that the synchronization is successful. After synchronization, the
active alarms displayed by the client are consistent with those on the NE.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
6.4.2 [GUTAM] History Alarm Re-gathering
Test Content: Check that the function of history alarm re-gathering works properly.
Test No.: 4.4.2 Test Object: NetNumen U31 R18
Test Item: Alarm Re-gathering Test Sub-item: History Alarm Re-gathering
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform alarm management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select History Alarm Re-gathering from the main menu of Fault. The History
Alarm Re-gathering page appears.
2) In the displayed window pane, set the parameter information that needs to be re-
gathered, such as controller NE agent and time period.
3) Click OK to see whether the history alarms of the NE agent that is re-gathered in the
specified time period are consistent with those on the NEs.
Expected Results:
1) The user can log in to the client and open the History Alarm Re-gathering page.
2) The information of NE agent and time period that needs to be re-gathered can be
set.
3) History alarms can be re-gathered according to the conditions set above.
4) The client gives the message about successful alarm re-gathering, and after
synchronization, the history alarms of the NE agent re-gathered on the client are
consistent with those on the NEs.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5 Setting
6.5.1 [ALL] Rule Setting
Test Content: Check that the rules can be created successfully and take effect.
Test No.: 4.5.1 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Rule Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly and the user is authorized to
perform alarm rule operations.
2) When the alarm forwarding rules are sent by e-mail or SMS, the mail server and
SMS need to be configured in the configuration center.
Test Procedure:
1) Open the Rule Setting window by selecting Fault > Setting > Rule Setting.
2) Select Alarm Filtering Rule, Alarm Acknowledgement Rule, Alarm Clear Rule,
Alarm Delaying Rules, Alarm Merging Rule, Alarm Counting Rule, Alarm
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Persisting Rule, Alarm Forwarding Rule, Alarm Masking Rules, Alarm
Triggering Script Rule, Alarm Restraining Rule-NE, Alarm Restraining Rule-NE
Type, or Notification Filtering Rules from the Rule Type.
3) Click the New button. The Rule Setting page appears. Import the selected rule
parameter.
4) Click OK to create the rule and enable it.
5) The selected Rule takes effect.
6) Modify, disable and delete the selected rule.
Expected Results:
1) The user can log in to the client and open the Rule Setting page, and the rule can
be created successfully.
2) Different rules can take effect when created successfully and in the active mode.
3) The rule can be modified, disabled and deleted.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.2 [ALL] Handling Suggestion Setting
Test Content: Check that the function of handling suggestion setting can operate properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 4.5.2 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Handling Suggestion Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Handling Suggestion Setting window by selecting Fault > Setting >
Handling Suggestion Setting.
2) Select a deep node from the tree of the resource type on the left.
3) The alarm causes, default and user-defined alarm handling methods are shown in
the right window pane. Modify the default and user-defined alarm handling methods
and save them.
4) View the alarm so as to modify it. Make sure it takes effect.
5) View the corresponding information of the alarm so as to modify it in the alarm
query. Make sure it is modified synchronously.
Expected Results:
1) The user can log in to the client and open the Handling Suggestion Setting page.
2) The handling suggestion can be modified successfully.
3) The handling suggestion of the alarm query result can be modified synchronously.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
6.5.3 [ALL] Severity Regrading Setting
Test Content: Check that the function of severity regrading setting can operate properly.
Test No.: 4.5.3 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Severity Regrading Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Severity Regrading Setting window by selecting Fault > Setting >
Severity Regrading Setting.
2) Select the alarm code packet that needs to be at the redefined level from the drop-
down box of the toolbar alarm code group.
3) Set the custom level of alarm code in the code list.
4) Click Save and the alarm code level of the newly reported alarm is shown as
previously set.
Expected Results:
1) The user can log in to the client and open the Severity Regrading Setting page.
2) The custom level of alarm code in the code list can be set successfully.
3) The alarm code level of alarm newly reported is shown as previously set.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.4 [ALL] Alarm Box Setting
Test Content: Check that the function of the alarm box setting works properly.
Test No.: 4.5.4 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Alarm Box Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
3) The server and the alarm box are linked properly.
Test Procedure:
1) Open the Alarm Box Setting window by selecting Fault > Setting > Alarm Box
Setting.
2) Click the New button on the toolbar, the Alarm Box Setting page appears.
3) Set the alarm box name, IP address, and the alarms that are sent to the alarm box.
4) Click OK. The alarm box is set successfully.
5) Modify, activate and delete the alarm box.
Expected Results:
1) The user can log in to the client and open the Alarm Box Setting page.
2) A new alarm box can be created successfully, and the alarm box information can be
shown in the alarm box view.
3) The rule can be modified, activated and deleted successfully.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.5 [ALL] Alarm Code Description Setting
Test Content: Check that the function of the alarm code description setting works properly.
Test No.: 4.5.5 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Alarm Code Description Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Alarm Code Description Setting window by selecting Fault > Setting >
Alarm Code Description Setting.
2) Select the group of alarm code that requires customizing alarm code settings from
the drop-down box of alarm code group in the toolbar.
3) Select an alarm code, and then click the Modify button on the toolbar or right-click it,
the Alarm Code Description Setting page appears.
4) Enter the custom name, select the custom level of the alarm code (the alarm code
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
level, such as threshold cross-border, cannot be set for some alarms), and then click
OK.
5) Check whether the alarm code level and the alarm code name in the alarm view are
modified as previously set.
Expected Results:
1) The user can log in to the client and open the Alarm Code Description Setting
page.
2) The alarm code level and the alarm code name in the alarm view are modified
successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.6 [ALL] Reason Setting
Test Content: Check that the function of the reason setting works properly.
Test No.: 4.5.6 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Reason Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Reason Setting window by selecting Fault > Setting > Reason Setting.
2) Select a reason code, and then click the Modify button on the toolbar or right-click it,
the Reason Setting page appears.
3) Set the Modified Name, and then click OK.
4) Check whether the reason name in the alarm reason view is modified as previously
set.
Expected Results:
1) The user can log in to the client and open the Reason Setting page.
2) The reason name in the alarm reason view is modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.7 [ALL] Alarm Forward Template Setting
Test Content: Check that the function of alarm forward template setting works properly.
Test No.: 4.5.7 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Alarm Forward Template Setting
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Alarm Forward Template Setting window by selecting Fault > Setting >
Alarm Forward Template Setting.
2) Set the SMS Template, Mail Subject, and Mail Content.
3) Click OK and check whether the alarm forward template is modified as previously
set.
Expected Results:
1) The user can log in to the client and open the Alarm Forward Template Setting
window.
2) The SMS Template, Mail Subject, and Mail Content are modified successfully, and
the Alarm Forward Template is shown as previously set.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
6.5.8 [ALL] TOP Alarm Restraining Setting
Test Content: Check whether the function of TOP Alarm Restraining Setting works properly.
Test No.: 4.5.8 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: TOP Alarm Restraining Setting
Input Parameter: None
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the TOP Alarm Restraining Setting window by selecting Fault > Setting >
TOP Alarm Restraining Setting.
2) In the displayed dialog box, set the name, start restraining and quit restraining
conditions, and set the alarm location and alarm code in Advanced Settings.
3) The settings take effect after clicking OK. Check whether a root alarm with the same
content as a derivative alarm is added after the number of occurrence times of the
same alarm at the same location that meets the conditions exceeds a specified
number of times. Then, start to make a repeat count for the derivative alarm until it
meets the quit restraining conditions.
Expected Results:
1) The user can log in to the client and open the TOP Alarm Restraining Setting
window.
2) In the displayed dialog box, the handling of TOP alarm restraining setting is enabled,
and TOP alarm restraining conditions are set.
3) A root alarm with the same content as a derivative alarm is added after the number
of occurrence times of the same alarm at the same location that meets the
conditions exceeds a specified number of times in accordance with the set
restraining conditions. A repeat count is made for the derivative alarm until it meets
the quit restraining conditions.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.9 [ALL] Intermittent Alarm Setting
Test Content: Check that the function of the intermittent alarm setting works properly.
Test No.: 4.5.9 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Intermittent Alarm Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Intermittent Alarm Setting window by selecting Fault > Setting >
Intermittent Alarm Setting.
2) Click the New button on the toolbar. The Intermittent Alarm Setting dialog box is
displayed.
3) In the displayed dialog box, set the criteria of intermittent alarm, and enable the
handling of intermittent alarm.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) Click OK. Then, check whether multiple alarms with the same NE and alarm code
are merged into one alarm as previously set.
Expected Results:
1) The user can log in to the client and open the Intermittent Alarm Setting window.
2) The criteria of intermittent alarm are set and the handling of intermittent alarm is
enabled in the displayed dialog box.
3) After the operation, multiple alarms with the same NE and alarm code are merged
into one alarm as previously set.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
6.5.10 [ALL] Alarm Prompting Setting
Test Content: Check that the function of the alarm prompting setting works properly.
Test No.: 4.5.10 Test Object: NetNumen U31 R18
Test Item: Setting Test Sub-item: Alarm Prompting Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Open the Alarm Prompting Setting window by selecting Fault > Setting > Alarm
Prompting Setting.
2) Click the New button on the toolbar. The Alarm Prompting Setting dialog box is
displayed.
3) Set the Name and Notify Method.
4) Click OK. The alarm that meets the conditions can be displayed as previously set.
5) Modify, activate and delete the alarm prompting.
Expected Results:
1) The user can log in to the client and open the Alarm Prompting Setting window.
2) The alarm prompting can be set successfully, and the alarm prompting can be
displayed in the Alarm Prompting view.
3) The alarm that meets the conditions can be displayed as previously set.
4) The alarm prompting can be modified, activated and deleted successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
6.5.11 [ALL] Automatically Acknowledging History Alarms
Test Content: Check that the function of automatically acknowledging history alarms works
properly.
Test No.: 4.5.11 Test Object: NetNumen U31 R18
Test Sub-item: Automatically Acknowledging
Test Item: Setting
History Alarms
Input Parameter: none
Prerequisites:
1) Both EMS server and client operate properly.
2) The user is authorized to perform alarm management operations.
Test Procedure:
1) Select Fault > Setting > Automatically Acknowledge History Alarms Setting
from the main menu to open the Automatically Acknowledge History Alarms
Setting window.
2) Set the number of days of automatic acknowledgement.
Expected Results:
1) The user can log in to the client and open the Automatically Acknowledge History
Alarms Setting window successfully.
2) The number of days of automatic acknowledgement can be set.
3) After setting, the system has automatically acknowledged the history alarms that are
cleared before the configured days.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
7 Performance Management
7.1 Measurement Task Management
7.1.1 [ALL] Creating a Measurement Task
Test Content: Check that a measurement task can be created successfully.
Test No.: 5.1.1 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Creating a Measurement Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Click the Add Measurement Task button on the toolbar.
3) Enter the Measurement Task parameters.
4) Click OK.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The measurement task can be created successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.2 [ALL] Modifying a Measurement Task
Test Content: Check that a measurement task can be modified.
Test No.: 5.1.2 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Modifying a Measurement Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) There is a measurement task whose Consistency Status is proper and whose
status is Suspended.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Select a suspended Measurement task, right-click it and choose Modify
Measurement Task from the displayed shortcut menu.
3) Modify the measurement task parameters.
4) Click OK.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened.
2) The measurement task can be modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.3 [ALL] Deleting a Measurement Task
Test Content: Check that a measurement task can be deleted.
Test No.: 5.1.3 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Deleting a Measurement Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) There is a measurement task whose Consistency Status is proper and whose
status is Suspended.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select a suspended task and then click the Delete Measurement Task button on
the toolbar.
3) The Delete Measurement Task dialog box is displayed. Click Yes.
Expected Results:
1) The suspended measurement task can be deleted.
2) The deleted task is not displayed in the Measurement Task Management window.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.4 [ALL] Copying a Measurement Task
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 5.1.4 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Copying a Measurement Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) The measurement task’s wildcard level is select to NE.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select an NE node from the left NE tree, right-click it and select Copy Measurement
Task from the displayed shortcut menu.
3) Select the NE to be copied on the left, and select the measurement task to be
copied on the right from the displayed dialog box.
4) Click OK.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened.
2) The measurement task can be copied successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
7.1.5 [ALL] Suspending a Measurement Task
Test Content: Check that the measurement task status can be suspended successfully.
Test No.: 5.1.5 Test Object: NetNumen U31 R18
Test Sub-item: Suspending a Measurement
Test Item: Measurement Task Management
Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) There is a measurement task whose Consistency Status is proper and whose
status is Activated.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select an active and proper task and then click the Suspend Measurement Task
button on the toolbar.
3) The Consistency Status of the task changes from Activated to Suspended.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened.
2) The status of the measurement task can be changed to Suspended.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.6 [ALL] Activating a Measurement Task
Test Content: Check that the measurement task status can be activated successfully.
Test No.: 5.1.6 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Activating a Measurement Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) There is a measurement task whose Consistency Status is proper and whose
status is Suspended.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select a suspended task, and then click the Activate Measurement Task button on
the toolbar.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) The Consistency Status of the task changes from Suspended to Activated.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened.
2) The status of the measurement task can be changed to Activated.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.7 [ALL] Viewing the Task Information
Test Content: Check that the measurement task information is correct.
Test No.: 5.1.7 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Viewing the Task Information
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Double-click a task or right-click it and choose View Measurement Task from the
displayed shortcut menu.
3) Check the measurement task information.
4) Click Close.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The measurement task information can be displayed properly.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.8 [ALL] Checking the Consistency Status of a Task
Test Content: Check that the consistency status of a task is proper.
Test No.: 5.1.8 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Sub-item: Checking the Consistency
Test Item: Measurement Task Management
Status of a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select a task and then click the View Consistency Status button on the toolbar, or
right-click a task and choose View Measurement Task from the displayed shortcut
menu.
3) Check the consistency status of the measurement task.
4) Click Close.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The consistency status of the task can be checked successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
7.1.9 [ALL] Synchronizing Measurement Tasks
Test Content: Check that the measurement task information can be synchronized.
Test No.: 5.1.9 Test Object: NetNumen U31 R18
Test Sub-item: Synchronizing Measurement
Test Item: Measurement Task Management
Tasks
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the serve, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select some measurement tasks.
3) Click the Synchronize Measurement Task button on the toolbar to start
synchronizing the selected measurement tasks.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The measurement tasks can be synchronized successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.10 [ALL] Synchronizing the Measurement Tasks with the Lower System
Test Content: Check that the function of synchronizing the measurement tasks with the lower
system works properly.
Test No.: 5.1.10 Test Object: NetNumen U31 R18
Test Sub-item: Synchronizing the Measurement
Test Item: Measurement Task Management
Tasks with the Lower System
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select one or more measurement tasks.
3) Right-click it, and select the menu Synchronize Measurement Task with Lower
System.
4) Select NE Type, and select NE Agent from the displayed dialog box, and then click
OK.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
5) The successful information is shown at the bottom of the status bar.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The measurement tasks have been synchronized with the lower system
successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.11 [ALL] Exporting and Importing Measurement Tasks
Test Content: Check that the measurement task information can be exported and imported.
Test No.: 5.1.11 Test Object: NetNumen U31 R18
Test Sub-item: Exporting and Importing
Test Item: Measurement Task Management
Measurement Tasks
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) EMS is connected to the NEs properly.
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Select one or more measurement tasks.
3) Click the Export Measurement Task button on the toolbar.
4) Set the Save Position, File Name and Files of Type in the Export Measurement
Task dialog box and then click the Save button.
5) A message prompts that measurement tasks are exported successfully in the status
bar.
6) Click the Import button on the toolbar, and select Import Test Task or Import
Measurement Task from the Predefined Template from the drop-down menu, or
right-click the measurement task list, and select Import Test Task or Import
Measurement Task from the Predefined Template from the displayed menu. The
Import Measurement Task dialog box is displayed.
7) Select the Save Position and File Name for import. The imported task name cannot
be the same as an existing task name, otherwise the import will fail. The task name
can be modified through Import Measurement Task from the Predefined
Template.
8) Perform the subsequent operations according to the prompts.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The selected measurement tasks can be exported to the file successfully.
3) The measurement tasks imported successfully are displayed in the measurement
task list. Users must be given the prompt information about the measurement tasks
that fail to be imported.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.1.12 [ALL] Measurement Task Integrity
Test Content: Check that the measurement task integrity can be checked.
Test No.: 5.1.12 Test Object: NetNumen U31 R18
Test Item: Measurement Task Management Test Sub-item: Measurement Task Integrity
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) A measurement task has been created.
Test Procedure:
1) Log in to the client and choose Measurement Task Management from the
Performance menu.
2) Click the Measurement Task Integrity button on the toolbar.
3) Select NE type in the Measurement Task Integrity dialog box and then click the
Check button.
4) Click the YES button in the Confirm dialog box, and then click the OK button in the
Message box. The checked results are shown in the Measurement Task Integrity
dialog box.
5) Click the Set button, and select the filter PO object. The Measurement Task
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Integrity check filter condition is set.
6) Click the Create button, and click the YES button in the Confirm dialog box, and
then click the OK button in the Message dialog box. The created message tasks are
shown in the Message Task list.
Expected Results:
1) The login is successful and the Measurement Task Management window can be
opened properly.
2) The creating status of a measurement task of NE of a specific type can be displayed
correctly after clicking the Check button.
3) The system can create a measurement task of NE of a specific type automatically
according to the results of integrity check after clicking the Create button.
4) The scope of PO to be checked of a specific NE type can be set in the displayed Set
PO dialog box after clicking the Set button.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.2 Counter and Index Management
7.2.1 [ALL] Viewing an Index
Test Content: Check that an index can be viewed.
Test No.: 5.2.1 Test Object: NetNumen U31 R18
Test Item: Counter and Index Management Test Sub-item: Viewing an Index
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) An index has been created.
Test Procedure:
1) Log in to the client and choose Counter and Index Management from the
Performance menu.
2) Expand the node of target measuring type in navigation of model management to
find the target measuring object.
3) Click the sub-node of performance counters under the node of target measuring
object, or right-click on the node of measuring type to select “Display all
performance objects” in the context menu, to view all performance objects under
the target measuring object.
4) Click on one performance object to view all performance counters under the object.
Expected Results:
1) The login is successful and the Counter and Index Management window can be
opened.
2) The index can be shown successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.2.2 [ALL] Creating an Index
Test Content: Check that an index can be created.
Test No.: 5.2.2 Test Object: NetNumen U31 R18
Test Item: Counter and Index Management Test Sub-item: Creating an Index
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and choose Counter and Index Management from the
Performance menu
2) Expand the nodes from the left-sided navigation tree until Counter and Key PI are
found, and then click the Create a KPI button on the toolbar.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) Select Key PI or Ordinary PI, and then click the button to create an index.
4) The Add Index dialog box is displayed. Enter the parameter, and then click OK.
Expected Results:
1) The login is successful and the Counter and Index Management window can be
opened.
2) The Add Index dialog box can be opened properly.
3) The index can be created successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.2.3 [ALL] Modifying an Index
Test Content: Check that an index can be modified.
Test No.: 5.2.3 Test Object: NetNumen U31 R18
Test Item: Counter and Index Management Test Sub-item: Modifying an Index
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) An index has been created.
Test Procedure:
1) Log in to the client and choose Counter and Index Management from the
Performance menu.
2) Find the index KPI or PI in the list.
3) Click the button on the toolbar or right-click to select Modify Counter from the
context menu, and modify the index parameter.
4) Click OK.
Expected Results:
1) The login is successful and the Counter and Index Management window can be
opened.
2) The index can be modified successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
7.2.4 [ALL] Deleting an Index
Test Content: Check that an index can be deleted.
Test No.: 5.2.4 Test Object: NetNumen U31 R18
Test Item: Counter and Index Management Test Sub-item: Deleting an Index
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) The counter and index have been created.
Test Procedure:
1) Log in to the client and choose Counter and Index Management from the
Performance menu.
2) Select an Index that is just created, and then click the Delete Index button on the
toolbar, or right-click to select Delete Index from the context menu.
3) Click OK.
Expected Results:
1) The login is successful and the Counter and Index Management window can be
opened.
2) The index created by the user can be deleted successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.3 Threshold Task Management
7.3.1 [ALL] Creating a Threshold Task
Test Content: Check that a threshold task can be created.
Test No.: 5.3.1 Test Object: NetNumen U31 R18
Test Item: Threshold Task Management Test Sub-item: Creating a Threshold Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and choose Threshold Task Management from the
Performance menu
2) Click the Add Threshold Task button on the toolbar.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) Enter the threshold task parameter.
4) Click OK.
Expected Results:
1) The login is successful and the Threshold Task Management window can be
opened.
2) The threshold task can be created successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.3.2 [ALL] Modifying a Threshold Task
Test Content: Check that a threshold task can be modified.
Test No.: 5.3.2 Test Object: NetNumen U31 R18
Test Item: Threshold Task Management Test Sub-item: Modifying a Threshold Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) EMS is connected to the NEs properly.
4) A threshold task has been created, and a suspended threshold task is available.
Test Procedure:
1) Log in to the client and choose Threshold Task Management from the
Performance menu.
2) Select a suspended threshold task, right-click it and choose Modify Threshold Task
from the displayed shortcut menu.
3) Modify the threshold task parameter.
4) Click OK.
Expected Results:
1) The login is successful and the Threshold Task Management window can be
opened.
2) The Modify Threshold Task dialog box can be opened properly.
3) The threshold task can be modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.3.3 [ALL] Activating a Threshold Task
Test Content: Check that a threshold task can be activated.
Test No.: 5.3.3 Test Object: NetNumen U31 R18
Test Item: Threshold Task Management Test Sub-item: Activating a Threshold Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and choose Threshold Task Management from the
Performance menu to open the Threshold Task Management window.
2) In the Threshold Task Management window, select a suspended task, and click the
Activate Threshold Task button on the tool bar.
Expected Results:
1) The login is successful and the Threshold Task Management window can be
opened.
2) The threshold task is activated successfully, and a threshold alarm will be raised if
the threshold task conditions are met.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
7.3.4 [ALL] Suspending a Threshold Task
Test Content: Check that a threshold task can be suspended.
Test No.: 5.3.4 Test Object: NetNumen U31 R18
Test Item: Threshold Task Management Test Sub-item: Suspending a Threshold Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and choose Threshold Task Management from the
Performance menu to open the Threshold Task Management window.
2) In the Threshold Task Management window, select an activated task, and click the
Suspend Threshold Task button on the tool bar. The confirmation dialog box of
suspending threshold task is displayed. Suspend the task according to the message.
Expected Results:
1) The login is successful and the Threshold Task Management window can be
opened.
2) The threshold task is suspended successfully, and no threshold alarm will be raised.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.3.5 [ALL] Deleting a Threshold Task
Test Content: Check that a threshold task can be deleted.
Test No.: 5.3.5 Test Object: NetNumen U31 R18
Test Item: Threshold Task Management Test Sub-item: Deleting a Threshold Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) A threshold task has been created, and a suspended threshold task is available.
Test Procedure:
1) Log in to the client and choose Threshold Task Management from the
Performance menu.
2) Select a suspended threshold task and then click the Delete Threshold Task button
on the toolbar.
Expected Results:
1) The login is successful and the Threshold Task Management window can be
opened.
2) The threshold task can be deleted successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.4 Common Template Management
7.4.1 [ALL] Creating a Common Template
Test Content: Check that a common template can be created.
Test No.: 5.4.1 Test Object: NetNumen U31 R18
Test Item: Common Template Management Test Sub-item: Creating a Common Template
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select Query Template Management from the Performance
menu. The Common Template Management window is displayed.
2) Click the Add Template button on the toolbar. The Add Common Template Task
dialog box is displayed.
3) On the Basic Info tab, input the template name, and select the parameters such as
the index and counter information, whether to calculate the data integrity ratio, and
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
index filtering etc.
4) Switch to the Statistic Info tab, and enter position summation level, query level, and
valid time period.
5) Click OK to finish the creation of a common template.
6) In the Common Template Management window, right-click a common template and
select Query by Template. The Performance Data Query dialog box is displayed.
7) Set the querying conditions of performance data that are not included in the
template, and click OK to query the performance data as set in the common
template.
Expected Results:
1) The login is successful and the Common Template Management window can be
opened properly.
2) The common template can be created successfully, and can be referenced in the
template task.
3) When querying performance data by common template, the querying conditions in
the displayed dialog box must be consistent to that set in the template, and the
performance data can be queried successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.4.2 [ALL] Modifying a Common Template
Test Content: Check that a common template can be modified.
Test No.: 5.4.2 Test Object: NetNumen U31 R18
Test Item: Common Template Management Test Sub-item: Modifying a Common Template
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select Query Template Management from the Performance
menu. The Common Template Management window is displayed.
2) Select a customized template, and click the Modify button on the toolbar. The
Modify Common Template dialog box is displayed.
3) On the Basic Info tab, input the template name, and select the parameters such as
the index and counter information, whether to calculate the data integrity ratio, and
index filtering etc.
4) Switch to the Statistic Info tab, and enter position summation level, query level, and
valid time period.
5) Click OK to finish the modification of a common template.
6) In the Common Template Management window, right-click the common template and
select Query by Template.
7) Set the querying conditions of performance data that are not included in the
template, and click OK to query the performance data as set in the common
template.
Expected Results:
1) The login is successful and the Common Template Management window can be
opened properly.
2) The common template can be modified successfully, and can be referenced in the
template task.
3) When querying performance data by common template, the querying condition in the
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
displayed dialog box must be consistent to that set in the template, and the
performance data can be queried successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.4.3 [ALL] Deleting a Common Template
Test Content: Check that a common template can be deleted.
Test No.: 5.4.3 Test Object: NetNumen U31 R18
Test Item: Common Template Management Test Sub-item: Deleting a Common Template
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select Query Template Management from the Performance
menu. The Common Template Management window is displayed.
2) Select a customized common template, and click the Delete Template button on the
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
toolbar of the Common Template Management window.
3) Click OK to finish the deletion of the common template.
Expected Results:
1) The login is successful and the Common Template Management window can be
opened properly.
2) The common template can be deleted successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.5 [ALL] Query Template Management
Test Content: Check that the function of query template management works properly.
Test No.: 5.5 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: Query Template Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) The Query Template Management view has been opened.
Test Procedure:
1) Select the Template Tree on the left side of the Query Template Management
view.
2) Right-click the History Performance Query Template, and select New Template
from the displayed shortcut menu. The New Template dialog box is displayed.
3) Set the Template Name and the Operation Mode.
4) Click OK and the History Performance Data Query dialog box is displayed.
5) Set the Query Condition and then click OK. The Query Template is created
successfully. The Query Template created just now is displayed under the current
user node.
6) Right-click the Query Template created just now and select Query by Template
from the displayed shortcut menu. Set the Query Condition and then click OK.
7) Right-click the Query Template created just now and select Modify Template from
the displayed shortcut menu. The History Performance Data Query dialog box is
displayed. Reset the Query Condition and then click OK
8) Right-click the Query Template created just now and select Modify Attribute from
the displayed shortcut menu. The Modify Attribute dialog box is displayed. Modify
the Template Name and the Operation Mode and then click OK.
9) You can also delete, import and export the query template.
Expected Results:
1) The login is successful and the Query Template Management view can be opened
properly.
2) The query template is created successfully, and can be referenced in the template
task.
3) The query template can be modified, deleted, imported and exported successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.6 [ALL] Template Task Management
Test Content: Check that the function of the template task management works properly.
Test No.: 5.6 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: Template Task Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select Template Task Management from the Performance
menu. The Template Task Management view is displayed.
2) Click the New Query Template Task button on the toolbar. The New Query
Template Task dialog box is displayed.
3) Set parameter such as Task name, Template name, File type and Task execution
time, and then click OK to finish creating the template task.
4) Click the New Common Template Task button on the toolbar. The New Common
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Template Task dialog box is displayed.
5) Set the Basic Info, such as Task name, Template name, File type, and Task
execution time.
6) Set the Location Info, such as Location group, Wildcard level, NE Location, and
MO Location.
7) Set the Time Info, such as Query granularity, Effective date, and Effective time,
and then click OK to finish creating the template task.
8) Select a template task. If this task was run at least once, you can see the result files
below.
9) Click the Export button on the toolbar and save the result files to the local disk.
10) Select a result record, and then click the Redo button on the toolbar. This task will
be performed on the EMS again.
11) You can also modify, view, delete, activate, suspend and finish the template task.
Expected Results:
1) The login is successful and the Template Task Management view can be opened
properly.
2) The Template Task Management function is available
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.7 [ALL] History Performance Query
Test Content: Check that the function of the history performance query works properly.
Test No.: 5.7 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: History Performance Query
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select the History Performance Query from the
Performance menu. The History Performance Query dialog box is displayed.
2) Set the Query Condition, such as Index/Counter Selection, Object Selection and
Time Selection, and then click OK.
3) The query result is displayed in the query table. The query result can be exported
and refreshed.
4) Click the Save as Template button on the toolbar. The New Template dialog box is
displayed.
5) Set the Name and Operation mode and then click OK.
6) After creating the query template, run the template, the results of the query appear
properly.
7) Click the Chart button on the toolbar. The Chart Configuration dialog box is
displayed.
8) Select a Chart type, set the parameter, and then click OK. The result is displayed by
chart.
Expected Results:
1) The login is successful and the Performance Management view can be opened
properly.
2) The History Performance Query function is available
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) After creating the query template, run it. You can get the right performance date.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.8 [ALL] History Performance Monitoring
Test Content: Check that the function of the history performance monitoring works properly.
Test No.: 5.8 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: History Performance Monitoring
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select the History Performance Monitoring from the
Performance menu. The History Performance Monitoring dialog box is displayed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Set the Monitoring parameters and then click OK.
3) The monitoring results are displayed on the EMS.
Expected Results:
1) The login is successful and the Performance Management view can be opened
properly.
2) The History Performance Monitoring function is proper.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
7.9 [ALL] Real-time Performance Monitoring
Test Content: Check that the function of the real-time performance monitoring works properly.
Test No.: 5.9 Test Object: NetNumen U31 R18
Test Sub-item: Real-time Performance
Test Item: Performance Management
Monitoring
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
authorized to perform performance management operations.
3) EMS is connected to the NEs properly, and the link between the NE Agent and the
NE is proper.
Test Procedure:
1) Log in to the client and select the Real-time Performance Monitoring from the
Performance menu. The Add Real-time History Performance Monitoring dialog
box is displayed.
2) Select the NE type and MO type.
3) Set the indices/counters, NE location and MO location to be monitored.
4) Select Task life cycle and collection granularity, and then click OK. The
monitoring result is displayed.
5) Click the Chart button on the toolbar, set the columns to be displayed and then click
OK. The monitoring result is displayed by chart.
Expected Results:
1) The login is successful and the Performance Management view can be opened
properly.
2) The Real-time Performance Monitoring function is proper.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
7.10 [ALL] Data Integrity Query
Test Content: Check that the data integrity query function is available.
Test No.: 5.10 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: Data Integrity Query
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
Test Procedure:
1) Log in to the client and select the Data Integrity Query from the Performance
menu. The Add Data Integrity Query dialog box is displayed.
2) Set the Object Info, Location Info and Time Info, and then click OK.
3) The Query result is displayed in the table.
4) If the Integrity Status of a record is No Data, right-click this record and select the
Recollect Data. The Add Data Recollection dialog box is displayed.
5) Set the Object Info and Location Info, and then click OK.
6) You can also modify the integrity query conditions and export the query result.
Expected Results:
1) The login is successful and the Performance Management view can be opened
properly.
2) The Data Integrity Query function is proper.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
7.11 [ALL] Group Management
Test Content: Check that the group management function is available.
Test No.: 5.11 Test Object: NetNumen U31 R18
Test Item: Performance Management Test Sub-item: Group Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform performance management operations.
3) EMS is connected to the NEs properly.
4) The Performance Management View is opened.
Test Procedure:
1) Select Group Management on the left side of the Performance Management view.
2) Right-click the Group Tree node, and select the New Group Type from the
displayed shortcut menu. The New Group Type dialog box is displayed.
3) Set the Group type name, select the NE type, MO type and Wildcard level, and
then click OK.
4) The group type added just now is under the Group Tree node.
5) You can view, modify and delete the group type.
6) Select a group type, right-click it and select the New Group from the displayed
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
shortcut menu. The New Group dialog box is displayed.
7) Set the Group name, NE type, MO type, Wildcard level, NE location, and MO
location, and then click OK.
8) The group added just now is under the selected group type.
9) You can view, modify and delete the group.
Expected Results:
1) The login is successful and the Performance Management view can be opened
properly.
2) The Group Management function is proper.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
8 Inventory Management
8.1 Inventory Data Query
8.1.1 [ALL] Querying Hardware Inventory
Test Content: Check that hardware inventory can be queried successfully.
Test No.: 6.1.1 Test Object: Inventory Management
Test Item: Inventory Data Query Test Sub-item: Querying Hardware Inventory
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Hardware inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Query and Stats tab.
2) Click the Query tab, select hardware inventory in the query type, and set the query
NE.
3) Set the query conditions (such as Date of Manufacture, Date of Last Repair, Active
or Passive, Inventory Unit Type, Vendor Unit Family Type, Unit Position, Vendor
Name and Pack Silk-screen).
4) Click Query.
Expected Results:
1) The inventory information can be displayed correctly according to the query
conditions set by the user.
2) The query results can be queued according to ascending and descending order of
every column.
3) The query results can be exported successfully, and the exported file is consistent
with the system.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
8.1.2 [ALL] Querying Software Inventory
Test Content: Check that software inventory can be queried successfully.
Test No.: 6.1.2 Test Object: Inventory Management
Test Item: Inventory Data Query Test Sub-item: Querying Software Inventory
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Software inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Query and Stats tab.
2) Click the Query tab, and select software inventory in the query type.
3) Set the query conditions (such as Gathering Type, Active or Passive, Inventory Unit
Type, Vendor Unit Family Type, and Vendor Name).
4) Click Query.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The inventory information can be displayed correctly according to the query
conditions set by the user.
2) The query results can be queued according to ascending and descending order of
every column.
3) The query results can be exported successfully, and the exported file is consistent
with the system.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
8.1.3 [ALL] Querying the Usage of Software Inventory
Test Content: Check that the usage of software inventory can be queried successfully.
Test No.: 6.1.3 Test Object: Inventory Management
Test Sub-item: Querying the Usage of Software
Test Item: Inventory Data Query
Inventory
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Software inventory information exists in the system.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Query and Stats tab.
2) Click the Query tab, and select software inventory usage in the query type.
3) Set the query conditions (such as Service Date, Gathering Type, Active or Passive,
Inventory Unit Type, Vendor Unit Family Type, and Vendor Name).
4) Select NE.
5) Click Query.
Expected Results:
1) The inventory information can be displayed correctly according to the query
conditions set by the user.
2) The query results can be queued according to ascending and descending order of
every column.
3) The query results can be exported successfully, and the exported file is consistent
with the system.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
8.2 Inventory Data Statistics
8.2.1 [ALL] Counting Hardware Inventory by Object
Test Content: Check that hardware inventory can be counted by NE, subnetwork and EMS.
Test No.: 6.2.1 Test Object: Inventory Management
Test Sub-item: Counting Hardware Inventory by
Test Item: Inventory Data Statistics
Object
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Query and Stats tab.
2) Click the Stats tab, select Stats by Object on the Stats Type sub-tab, and select
the EMS to be counted (All inventory data is counted by default).
3) Select the object of statistics.
4) Set the statistical conditions (such as Date of Manufacture, Date of Last Repair,
Active or Passive, Inventory Unit Type, Vendor Unit Family Type, Unit Position,
Vendor Name and Board Silk-screen).
5) Click Stats.
Expected Results:
1) The statistical results can be displayed correctly according to the statistical
conditions set by the user.
2) The statistical results can be queued according to ascending and descending order
of every column.
3) The statistical results can be exported successfully, and the exported file is
consistent with the system.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
8.2.2 [ALL] Counting Software Inventory
Test Content: Check that software inventory can be counted successfully.
Test No.: 6.2.2 Test Object: Inventory Management
Test Item: Inventory Data Statistics Test Sub-item: Counting Software Inventory
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Query and Stats tab.
2) Click the Stats tab, and select Software Inventory on the Stats Type sub-tab.
3) Set the statistical conditions (such as Gathering Type, Inventory Unit Type, Vendor
Unit Family Type, and Vendor Name).
4) Click Stats.
Expected Results:
1) The statistical results can be displayed correctly according to the statistical
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
conditions set by the user.
2) The statistical results can be queued according to ascending and descending order
of every column.
3) The statistical results can be exported successfully, and the exported file is
consistent with the system.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
8.3 Inventory Information Export and Import
8.3.1 [ALL] Exporting Inventory Data (XLS, CSV, and XML)
Test Content: Check that inventory data can be exported successfully.
Test No.: 6.3.1 Test Object: Inventory Management
Test Item: Inventory Information Export and
Test Sub-item: Exporting Inventory Data
Import
Input Parameter: none
Prerequisites:
1) EMS is started normally.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Inventory Management tab.
2) Select a node from the resource tree, right-click it and select View active inventory
or View passive inventory from the shortcut menu.
3) Select the inventory to be exported (or all inventory) in the inventory result.
4) Click Export Selected or Export All.
5) Select the exporting path.
6) Select the pattern XLS, CSV or XML to export.
Expected Results:
1) The inventory data file can be exported according to the pattern set by the user.
2) The inventory data in the file is the same as that in the system.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
8.3.2 [ALL] Importing Inventory Data (XLS, CSV, and XML)
Test Content: Check that inventory data can be imported successfully.
Test No.: 6.3.2 Test Object: Inventory Management
Test Item: Inventory Information Export and
Test Sub-item: Importing Inventory Data
Import
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) Inventory information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Inventory Management tab.
2) Click Import.
3) Select Online Hardware Inventory from the inventory type drop-down list.
4) Select the file to be imported according to the file pattern.
5) Select the import strategy (Skip, Overwrite or Error-reporting), and click Next.
6) Click Check.
7) Click Import. The hardware inventory has been imported.
Hardware inventory has been imported.
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Inventory Management tab.
2) Click Import.
3) Select Software Inventory from the inventory type drop-down list.
4) Select the file to be imported according to the file pattern.
5) Select the import strategy (Skip, Overwrite or Error-reporting), and click Next.
6) Click Check.
7) Click Import.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
The software inventory has been imported.
Expected Results:
1) The warehoused inventory data is the same as the content of the imported file.
2) Perform a validity check on the imported file, and invalid file can be reported to the
user.
3) The same inventory data will be overwritten in the strategy of Overwrite, and will be
ignored in the strategy of Skip. The system will report an error and stop importing if
the inventory data is the same in the strategy of Error-reporting.
4) Import operation cannot modify the inventory data reported by the NE, and the
reported inventory data can only be modified in the state of offline.
5) The pattern of imported file includes XLS, CSV, and XML.
6) After a system that is valid at the beginning and invalid in the middle is detected, a
corresponding message will be displayed, prompted the user of modifying. Import
the inventory data after correct modification.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
8.4 Inventory Data Synchronization
8.4.1 [ALL] Synchronizing Hardware and Software Inventory Manually
Test Content: Check that hardware and software inventory can be synchronized manually.
Test No.: 6.4.1 Test Object: Inventory Management
Test Sub-item: Synchronizing Hardware and
Test Item: Inventory Data Synchronization
Software Inventory Manually
Input Parameter: none
Prerequisites:
1) EMS is started normally.
2) A link has been established between the EMS and NE.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Inventory Management tab.
2) Select a node from the resource tree, right-click it and select Synchronize
hardware and software inventory from the shortcut menu (The inventory
synchronization of nodes such as OMM, subnetwork, and NE is supported in the
EMS).
3) After the system returns the synchronization result, right-click the online hardware
inventory node and select View active inventory. Right-click the software inventory
node and select View inventory.
Expected Results:
1) The inventory data is consistent with the actual software and hardware data.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
8.5 Spare Parts Management
8.5.1 [ALL] Changing the Status of a Spare Part
Test Content: Check that the status of a spare part can be changed successfully.
Test No.: 6.5.1 Test Object: Inventory Management
Test Sub-item: Changing the Status of a Spare
Test Item: Spare Parts Management
Part
Input Parameter: none
Prerequisites:
1) EMS is running normally.
2) Spare part information exists in the system.
Test Procedure:
1) Open the Inventory Management window by clicking Configuration > Common
Wireless Configuration Application > Inventory Management in the menu bar on
the client, and click the Spare Parts Management tab.
2) Click the View all spare parts button.
3) Select the inventory according to inventory status and gathering method to perform
the operations in the context menu.
Expected Results:
1) The inventory statuses include Out of Service, In Warehouses, Under Repair, and
Out of Use.
2) Change: Online, Under Repair, Out of Service, In Warehouses, Out of Use.
3) Operation: Out of Service > Out of Use and In Warehouses, Under Repair > In
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Warehouses and Out of Use, In Warehouses > Online, Under Repair and Out of
Use. Other operations are not allowed.
4) The inventory status must be written into the database after the changing is
successful.
5) No log of failure to warehouse is printed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
9 Configuration Management
9.1 MML Terminal
9.1.1 [ALL] MML Terminal
Test Content: Check that the MML Terminal is available.
Test No.: 7.1.1 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: MML Terminal
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform MML terminal operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > MML Terminal > Open MML Terminal. The MML Terminal
page appears.
2) View the top left corner. Select the EMS Server node from the topology tree. The
MML command supported by the EMS server can be seen.
3) Select the command from the topology tree, such as User Management, System
Check, and Task Management.
4) View the top left corner. Select the OMM Server node from the topology tree. The
MML command supported by the OMM server can be shown.
5) Select the command from the topology tree, such as Security Management and
Configuration Management.
6) Select a different command, enter the parameter, and then press F5 or click
Execute. The results can be shown.
7) Enter the command directly. Press F5 or click Execute. The results can be shown.
Expected Results:
1) The results can be shown in the window.
2) The history command you have executed can be queried from the drop-down box.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
9.2 Wireless Configuration Application
9.2.1 [GUT] NE Relation Management
Test Content: Check that the NE relation management is available.
Test No.: 7.2.1 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: NE Relation Management
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management query operation.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
5) The relation between the controller and the base station has been configured.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > NE
Relation Management to open the NE Relation Management page.
2) The NE Relation Management window appears. Click Filter to open the NE
Relation Data Filter dialog box.
3) Select the product type from the product drop-down box, for example, “UMTS”. Enter
the keywords in the corresponding dialog box to set the filtering conditions. For
example, enter 60.158 in the OMM-B Name dialog box.
4) Click OK. The NE relations are filtered and only the NE relations that meet the
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
filtering conditions are shown on the NE Relation Management window.
5) Click Export in the NE Relation Management window to open the Save dialog box.
Select the save path from the Save dialog box, enter the file name, and then click
the Save button. When prompted with the message of exported successfully, click
OK.
Expected Results:
1) You can log in to the client successfully and enter the NE Relation Management
windows.
2) The pre-set data can be filtered.
3) The NE relation data can be exported.
4) The new relation can be obtained on the NE Relation Management page after the
relation has changed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
9.2.2 [GUTLL] Maintenance Status Query and Setting
Test Content: Check that the function of maintenance status query and setting works properly.
Test No.: 7.2.2 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: Maintenance Status Query and
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > Maintain
Status Query and Setting to open the Maintain Status Query and Setting dialog
box.
2) Set the query conditions in the opened dialog box, such as NE agent, status, site ID,
site name.
3) Click OK to open the Maintain Status Query and Setting dialog box.
4) You can see the status of all base stations for the selected subnetwork in the
Maintain Status Query and Setting dialog box.
5) Right-click the row corresponding to the base station to be set in the Maintain
Status Query and Setting dialog box, and then click Test in the shortcut menu.
6) Click the Execute button to change the status of the base station.
7) The function of import and export can be executed successfully.
Expected Results:
1) You can log in to the client successfully and enter the Maintain Status Query and
Setting dialog box.
2) The maintenance status of relevant base stations can be displayed in accordance
with the setting of query conditions in the Maintain Status Query and Setting
dialog box.
3) The function of setting the maintenance status can be executed successfully.
4) The function of import and export can be executed successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
9.2.3 [GUT] VIP NodeB Priority Query and Setting
Test Content: Check that the function of VIP NodeB priority query and setting is available.
Test No.: 7.2.3 Test Object: NetNumen U31 R18
Test Sub-item: VIP NodeB Priority Query and
Test Item: Configuration Management
Setting
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > VIP
NodeB Priority Query and Setting to open the VIP NodeB Priority Query and
Setting page.
2) Select the NE agent from the Select dialog box.
3) Click OK to open the VIP NodeB Priority Query and Setting window, in which the
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
priorities of all NodeBs for the selected subnetwork are listed.
4) The NodeB priority can be shown in the list.
5) Right-click the row corresponding to the Node B to be set in the VIP NodeB Priority
Query and Setting window, and then click VIP in the shortcut menu,
6) Click the Execute button to change the priority of the base station.
7) The function of import and export can be executed successfully.
Expected Results:
1) You can log in to the client successfully and enter the VIP NodeB Priority Query
and Setting windows.
2) The VIP NodeB Priority Query and Setting dialog box can be displayed in
accordance with the setting of the query conditions related to the base station
priority.
3) The function of setting the NodeB priority can be executed successfully.
4) The function of import and export can be executed successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
9.2.4 [GUT] Site Transfer
Test Content: Check that the function of site transfer is available.
Test No.: 7.2.4 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: Site Transfer
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
5) The ICM configuration model of the corresponding version of NE agent has been
uploaded.
Test Procedure:
Online Transfer:
1) In the client window, select Configuration > ICM Configuration Management >
Plan Data Management from the menu bar. The Plan Data Management view is
displayed.
2) Select the source NE and target NE for transfer from the Live Area list in the right
pane, and click Create Plan Area from the context menu. Then, set the parameters
in the displayed window and click OK.
3) Select the plan area created in the above step in the left data area, and click
Transfer Site from the context menu. The Transfer Site window is displayed.
4) Select GU-OMMR online in the left pane, and switch to the Online Transfer window
in the right pane.
5) Click Add in Transfer Site Template, and select the transfer site template file.
6) Select whether to import the plan data of target RNC/BSC bureau as required, click
Add in Plan Data of Target RNC/BSC Bureau (Optional) to select the bureau plan
data file.
7) Click Execute. The execution progress of online transfer is displayed in Transport
Progress. After the transfer is completed, the system will give a message.
8) Close the Transfer Site window. Select the transferred plan area and click Check
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
from the context menu. The Data Check-Conflict window is displayed.
9) Execute conflict check and validity check in order. After both checks are successfully
executed, then execute submission.
10) Select Configuration > ICM Configuration Management > Plan Data Activation
from the menu bar. The Activation Task Management view is displayed.
11) Select the corresponding activation task of the transferred plan area, and click
Generate Script from the context menu.
12) After the script is generated successfully, click Download from the context menu.
13) After successful downloading, select Activate from the context menu. After
activation, the data of the source NE and target NE for transfer has been sent to
corresponding NEs for validation.
Offline Transfer:
1) On the U31 client of the source NE and the target NE, select Configuration > ICM
Configuration Management > Plan Data Management from the menu bar. The
Plan Data Management view is displayed.
2) Select the source NE and target NE for transfer in the right Live Area list, and create
a plan area.
3) Select the source NE and the target plan area, and click Export from the context
menu. The Query and Export window is displayed.
4) Select Optimization from the left pane, select the data to be exported as required,
select Ground, GSM wireless or UMTS wireless from Data Type in the right pane,
and click Next. Switch the window and select the path for saving the exported file.
The file has been saved successfully.
5) Select the plan area of the source NE and target NE, and click Transfer Site from
the context menu. The Transfer Site window is displayed.
6) Select GU-OMMR offline in the left pane, and switch to the Offline Transfer
window in the right pane.
7) Select the Cell and Neighbor Cell Data Transfer tab, and select the transfer site
template, source RNC/BSC data and target RNC/BSC data in order.
8) Click Execute. The execution progress of offline transfer is displayed in Transport
Progress. After the transfer is completed, the system will give the saving path of the
offline transfer result file.
9) Open the offline transfer result file, select the plan area of the source NE and import
the transfer result file of the source NE, and select the plan area of the target NE
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
and import the transfer result file of the target NE.
10) After data import is completed, select the plan area of the source NE and the target
NE, and click Check from the context menu. The Data Check-Conflict window is
displayed.
11) Execute conflict check and validity check in order. After both checks are successfully
executed, then execute submission.
12) Select Configuration > ICM Configuration Management > Plan Data Activation
from the menu bar. The Activation Task Management view is displayed.
13) Select the corresponding activation task of the transferred plan area of the source
NE and target NE, and click Generate Script from the context menu.
14) After the script is generated successfully, click Download from the context menu.
15) After successful downloading, select Activate from the context menu. After
activation, the data of the source NE and target NE for transfer has been sent to
corresponding NEs for validation.
Expected Results:
1) The login is successful and the Transfer Site window is opened.
2) Online transfer and offline transfer are all successful.
3) The data of site transfer can be successfully sent to the source NE and target NE for
validation.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
9.2.5 [GU] CBC Management
Test Content: Check that the function of the CBC Management is available.
Test No.: 7.2.5 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: CBC Management
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > CBC
Management to open the CBC Management page.
2) Right-click on the topology tree ZTE Cell Broadcast Management > Resource
Management > channel to create a channel.
3) Perform the basic operations to the channel, such as modify, delete and refresh.
4) Right-click on the topology tree ZTE Cell Broadcast Management > Resource
Management > cell, refresh the cell and restart the cell.
5) Right-click on the topology tree ZTE Cell Broadcast Management > Resource
Management > channel, refresh the cell and restart the cell. Select the shortcut
menu to restart, and view the results.
6) Right-click on the topology tree ZTE Cell Broadcast Management > Resource
Management > broadcast to create a broadcast.
7) Perform the basic operations to the broadcast, such as modify, delete and refresh.
8) Right-click on the topology tree ZTE Cell Broadcast Management > Short
Message, to create a short message.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
9) Perform the basic operations to the short message, such as modify, delete and
export.
Expected Results:
1) You can log in to the client successfully and enter the CBC Management window.
2) Selecting different nodes from the topology tree, the short message or channel or
cell or broadcast can be shown in the message blank.
3) The basic functions of the channel management, cell management, broadcast
management and short message management work properly.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
9.2.6 [GUTLL] CM Data Collection
9.2.6.1 [GUTLL] Report Manager
Test Content: Check that the function of Report Manager is available.
Test No.: 7.2.6.1 Test Object: NetNumen U31 R18
Test Item: CM Data Collection Test Sub-item: Report Manager
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > CM Data
Collect > Report Manager to open the Report Manager page.
2) Click Get Report on the toolbar in the front of CM Data Collect window to open the
Get Report page.
3) Select the NE type, subnetwork ID and template, and then click OK. The system
begins to collect the CM data to a file.
4) Right-click one line of the result file list, and select the export button. The report file
can be obtained after you set a path.
Expected Results:
1) You can log in to the client successfully and enter the Report Manager window.
2) Te report is exported successfully to the local path.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
9.2.6.2 [GUTLL] Template Manager
Test Content: Check that the function of Template Manager is available.
Test No.: 7.2.6.2 Test Object: NetNumen U31 R18
Test Item: CM Data Collect Test Sub-item: Template Manager
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > Common Wireless Configuration Application > CM Data
Collect > Template Manager to open the Template Manager page.
2) Click Create on the toolbar in the front of Template Manager window to open the
Create Template page.
3) Set the parameter and then click OK. The new template will be shown in the window.
4) The origin template can only be viewed while the user-defined template can be
modified, viewed and deleted.
Expected Results:
1) You can log in to the client successfully and enter the Template Manager window.
2) The template can be created successfully.
3) The user-defined template can be modified, viewed and deleted successfully.
4) The origin template can only be viewed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
9.2.7 [GUT] Interconnection Parameter Management
Test Content: Check if Inter NE Management can be used normally.
Test No.: 7.2.7 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: Inter NE Compare
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS is connected to the NEs properly.
Test Procedure:
1) In the client window, select Configuration > Common Wireless Configuration
Application > InterNE Compare from the menu bar. The InterNE Manage Option
dialog box is displayed.
2) In step 1, select product. In step 2, select management type. Select Compare for
operation type, and then click Next.
3) Perform the following operations according to the message, and click OK. The
InterNE Batch Compare Result dialog box is displayed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) In the dialog box, you can see the batch comparison results. Export the batch
comparison results to the local.
5) Open the exported file to view the details of the comparison results. Based on the
file, modify inconsistent parameters and mark Y in the Comparative result (Y/N)
column for a modified parameter.
6) Open the InterNE Manage Option dialog box in the same way. In step 1, select
product, which is the same as that selected in comparison.
7) In step 2, select Modify for operation type corresponding to the management type.
Then, import the modified file, such as the file mentioned in step 5.
8) Click OK, and check whether the modification is successful in the InterNE Batch
Compare Result dialog box.
Expected Results:
1) You can log in to the client successfully and enter the InterNE Manage Option
dialog box.
2) In the InterNE Manage Option dialog box, the interconnection parameters between
the RNC and the NodeBs under its control can be compared in batches.
3) In the InterNE Manage Option dialog box, the interconnection parameters between
the RNC and the NodeBs can be modified in batches.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
9.3 NE Management
Test Content: Check that the function of the NE management is available.
Test No.: 7.3 Test Object: NetNumen U31 R18
Test Item: Configuration Management Test Sub-item: NE Management
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) An NE agent has been created.
4) EMS interacts with NEs properly.
Test Procedure:
1) Select Configuration > NE Configuration to open the NE Configuration page.
2) Right-click an NE agent under the EMS server node. If the NE management of this
version is started initially by the client, the Start NE Management shortcut menu is
disabled.
3) After the NE version has been uploaded, right-click the NE agent again. The shortcut
menu Start NE Management is enabled. Click it to start the NE management.
Test Procedure:
4) Select Configuration > NE Configuration to open the NE Configuration page.
5) Select NE Agent and right-click on the EMS server. If the NE is started by the client,
the Start button is disabled.
6) When the Start button is enabled, click it to start the NE management.
Expected Results:
1) You can log in to the client successfully and enter the NE management window.
2) The NE is started successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
10 Security Management
10.1 [ALL] Role Management
Test Content: Check that roles can be managed.
Test No.: 8.1 Test Object: NetNumen U31 R18
Test Item: Security Management Test Sub-item: Role Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform security management operations.
3) For the projects involving GDPR, do not input personal information when testing this
function.
Test Procedure:
1) Choose Role Management from the Security main menu to open the Role
Management window.
2) Select a node from the role tree, right-click it and choose Create Role from the
displayed shortcut menu.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) Fill in the role attributes including role name, description, lockout indicator,
permissions, and operation set.
4) Click OK to exit.
5) Right-click the role to modify, duplicate and delete it.
Expected Results:
1) The login is successful and the Role Management window can be opened.
2) The role is created successfully.
3) The role can be modified, duplicated and deleted.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
10.2 [ALL] User Management
Test Content: Check that users can be managed.
Test No.: 8.2 Test Object: NetNumen U31 R18
Test Item: Security Management Test Sub-item: User Management
Input Parameter: none
Prerequisites:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform security management operations.
3) For the projects involving GDPR, do not input personal information when testing this
function. The test should be performed under the supervision of the project
compliance manager.
Test Procedure:
1) Click User Management from the Security main menu to open the User
Management window.
2) Select a user or department, right-click it and choose Create User from the
displayed shortcut menu.
3) Set the user information.
4) Fill in the user name, full name, password, and password control on the Basic
Information page, and decide whether to disable or cancel the account.
5) Assign roles or role sets to the user on the Right tab page.
6) Open the User Department page to specify the user’s department.
7) Fill in the user description, telephone number, Email, max number of concurrent
logins, working time and login IP range for advanced information.
8) Click OK for saving.
9) Right-click the user to modify, duplicate and delete the user.
Expected Results:
1) The login is successful and the User Management window can be opened.
2) Users can be created successfully.
3) Roles can be modified, duplicated and deleted.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
10.3 [ALL] User Popular Functions
Test Content: Check that the user popular functions are available.
Test No.: 8.3 Test Object: NetNumen U31 R18
Test Item: Security Management Test Sub-item: User Popular Functions
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform security management operations.
3) For the projects involving GDPR, the operations should be performed under the
supervision of the compliance manager. Besides, the permission from the related
manager is required before the operations. If it is not clear whether the operations
meet the compliance requirements, confirm with the compliance manager of the
project team before the operations.
Test Procedure:
1) Select Security > View User Lock Detail from the main menu, and select a user to
be unlocked in the displayed window. Then, click Unlock.
2) Select Security > Modify Common Users’ Password in Batch from the main
menu to modify the all common users’ password. Only administrator users can
perform the operation.
3) Select Security > Login User Management from the main menu. Then, select a
user in the displayed window, and perform the operations, such as Send Massage,
Force to Log Out, etc.
4) Select Security > Set User Account Rule from the main menu, account rules and
password rules can be set in the displayed window, and only administrator users can
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
perform the operation.
5) Select Security > User Blacklist from the main menu. Then, select a user in the
displayed window, click Add to Blacklist, and click OK.
6) Select Security > Set User Login Mode from the main menu to set the User Login
Mode, administrator users can perform the operation.
7) Select Security > Clear Account from the main menu to clear the disabled account,
administrator users can perform the operation.
8) Select Security > Set User Auto-Logout Idle Time from the main menu to set the
idle time for the user to log out automatically, and then click OK.
Expected Results:
1) The login is successful and the Security Management window can be opened.
2) The users can be managed by the user popular functions.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
10.4 [ALL] Log Management
Test Content: Check that the log management function is available.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 8.4 Test Object: NetNumen U31 R18
Test Item: Security Management Test Sub-item: Log Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) A connection is established between the client and the server, and the user is
authorized to perform log management operations.
Test Procedure:
1) Choose Log Management from the Security main menu to open the Log
Management view.
2) Perform some operations and check the corresponding Operation/Security/System
log.
3) Click to query the log.
4) Click to export the log.
Expected Results:
1) The login is successful and the Log Management window can be opened.
2) There are Operation/Security/System log records.
3) The logs can be queried and exported.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
11 Maintenance Management
11.1 System Backup
11.1.1 [ALL] Backup Task
Test Content: Check that the system information can be backed up.
Test No.: 9.1.1 Test Object: NetNumen U31 R18
Test Item: System Backup and Restoration Test Sub-item: Backup Task
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
4) For the projects involving GDPR, the operations should be performed under the
supervision of the compliance manager. Besides, the permission from the related
manager is required before the operations. After the backup is completed, delete the
manually backed-up data from the PC or public computer completely.
Test Procedure:
1) Select Maintenance > System Backup and Restore in the main menu to open the
Backup and Restore window.
2) In the left navigation tree, select Backup and Restore > Backup > Backup Whole
DB Structure, Backup and Restore > Backup > Backup Basic Data, and Backup
and Restore > Backup > Backup File separately to display the corresponding
parameter setting window in the right pane.
3) Set the parameters, and click the Execute button to execute the backup operation,
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
and the backup information will be displayed in the result box.
4) In the left navigation tree, select Backup and Restore > Backup > Backup and
Deletion Log Data, Backup and Restore > Backup > Backup and Deletion
Alarm Data separately to display the corresponding parameter setting window in the
right pane.
5) Set the parameters, and click the Execute button to execute the deletion operation
of the backup, and the backup and deletion information will be displayed in the result
box.
Expected Results:
1) The login is successful and the Backup and Restore window can be opened.
2) The whole DB structure, basic data, and the files can be backed up successfully.
3) The backup of log data and alarm data can be deleted successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
11.1.2 [ALL] Restoration Task
Test Content: Check that the system information can be restored.
Test No.: 9.1.2 Test Object: NetNumen U31 R18
Test Item: System Backup and Restoration Test Sub-item: Restoration Task
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance > System Backup and Restore from the main menu to open
the Backup and Restore window.
2) In the left navigation tree, select Backup and Restore > Restore > Restore Log
Data, and select Backup and Restore > Restore > Restore Alarm Data separately
to display the corresponding parameter setting window in the right pane.
3) Click the Browse button to display the Open dialog box.
4) Select the files to be restored, and click the Open button to return to the Backup
and Restore main interface.
5) Click the Execute button to execute the restoration operation.
Expected Results:
1) The login is successful and the Backup and Restore window can be opened.
2) Log data and alarm data have been restored successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
11.2 System Monitoring
11.2.1 [ALL] Server Monitoring
Test Content: Check that the function of server monitoring works properly.
Test No.: 9.2.1 Test Object: NetNumen U31 R18
Test Item: System Monitoring Test Sub-item: Server Monitoring
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform server monitoring and setting operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select System Monitoring from the main menu of Maintenance to open the
System Monitoring window.
2) Click Equipment Tree > Server > Application Server*** in the navigation tree of
system monitoring. The application server monitoring is displayed in the right pane.
3) Click the View button in the server performance viewing box. The View Application
Server Performance window is displayed.
4) Click the Set button in the server performance monitoring box. The Configure
Performance Monitoring window is displayed.
5) Select monitored objects, including CPU, memory and hard disk.
6) Click OK and close the dialog box.
7) Click the Stop button in the server performance monitoring box to close server
performance monitoring.
8) Click the Start button in the server performance monitoring box to start server
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
performance monitoring.
Expected Results:
1) The user can log in to the client successfully, and the System Monitoring window can
be opened.
2) The server performance monitoring parameters can be configured, and the alarm
and log that meet the threshold value can be generated according to the configured
monitoring contents.
3) Basic operations, such as starting, stopping and viewing the server performance
monitoring can be performed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
11.2.2 Database Monitoring
11.2.2.1 [ALL] Oracle Database Monitoring
Test Content: Check that the function of Oracle database monitoring works properly.
Test No.: 9.2.2.1 Test Object: NetNumen U31 R18
Test Item: System Monitoring Test Sub-item: Oracle Database Monitoring
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform database monitoring and setting operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select System Monitoring from the main menu of Maintenance to open the
System Monitoring window.
2) Click Equipment Tree > Database > Oracle: *** in the navigation tree of system
monitoring. The database resource monitoring attributes and the basic information of
the database server are displayed in the right pane.
3) Click the View button in the database resource viewing. The View Database
Resource window is displayed.
4) Click the Set button on the right of database resource monitoring. The Configure
Database Resource dialog box is displayed.
5) Select monitored objects, and set the monitoring period, including the monitoring of
total database space (the allocated database space) and the monitoring of used
database space (actually used database space).
6) Click OK and close the dialog box.
7) Click the Stop button on the right of database resource monitoring to stop database
resource monitoring.
8) Click the Start button on the right of database resource monitoring to start database
resource monitoring.
Expected Results:
1) The user can log in to the client successfully, and the System Monitoring window
can be opened.
2) The database resource monitoring parameters can be configured, and the alarm and
log that meet the threshold value can be generated according to the configured
monitoring contents.
3) Basic operations, such as starting, stopping and viewing the database resource
monitoring can be performed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
11.2.2.2 [ALL] Sybase IQ Database Monitoring
Test Content: Check that the function of Sybase IQ database monitoring works properly.
Test No.: 9.2.2.2 Test Object: NetNumen U31 R18
Test Item: System Monitoring Test Sub-item: Sybase IQ Database Monitoring
Input Parameter: None
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform database monitoring and setting operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select System Monitoring from the main menu of Maintenance to open the
System Monitoring window.
2) Click Equipment Tree > Database > SybaseIQ@*** in the navigation tree of
system monitoring. The database resource monitoring attributes and the basic
information of the database server are displayed in the right pane.
3) Click the View button in the database resource viewing. The View Database
Resource window is displayed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) Click the Set button on the right of database resource monitoring. The Configure
Database Resource dialog box is displayed.
5) Select monitored objects, and set the monitoring period, including the monitoring of
total database space (the allocated database space) and the monitoring of used
database space (actually used database space).
6) Click OK and close the dialog box.
7) Click the Stop button on the right of database resource monitoring to stop database
resource monitoring.
8) Click the Start button on the right of database resource monitoring to start database
resource monitoring.
Expected Results:
1) The user can log in to the client successfully, and the System Monitoring window
can be opened.
2) The database resource monitoring parameters can be configured, and the alarm and
log that meet the threshold value can be generated according to the configured
monitoring contents.
3) Basic operations, such as starting, stopping and viewing the database resource
monitoring can be performed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
11.3 Task Management
11.3.1 [ALL] Modifying the Task Time
Test Content: Check that the task time can be modified.
Test No.: 9.3.1 Test Object: NetNumen U31 R18
Test Item: Task Management Test Sub-item: Modifying the Task Time
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance > Task Management > Modify Task Time to open the Modify
Task Time dialog box.
2) In the displayed dialog box, select a task type to be modified.
3) Double-click the task to be modified. The Modify Execution Time dialog box is
displayed.
4) Set the execution time and click OK to quit the Modify Execution Time dialog box.
5) Click OK to quit the Modify Task Time dialog box.
Expected Results:
1) The Modify Task Time dialog box can be opened.
2) The task time can be modified, and the task will be executed according to the new
time.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
11.3.2 [ALL] Historical Data Archiving
Test Content: Check that the historical data can be activated.
Test No.: 9.3.2 Test Object: NetNumen U31 R18
Test Item: Task Management Test Sub-item: Historical Data Archiving
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance >Task Management > Show Timing Task from the main
menu to open the Task Management view.
2) Select Log Data/Alarm Data/Performance Data Backup and Deletion task from
the navigation tree on the left.
3) The description of the log/alarm data backup and deletion task is shown in the right
middle of the interface.
4) There are the following buttons: Refresh, Modify, View Missing Task, View Log,
Set Capacity and Stop Backup on this page.
5) Click Modify to modify the backup data selection and then click Save to submit the
modification.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The Task Management view can be displayed.
2) The description of the log/alarm data backup and deletion task can be queried and
modified.
3) The backup and deletion task will be executed according to the modified strategy.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
11.3.3 [ALL] Basic Data/Whole DB Structure/File Backup
Test Content: Check that the function of basic data/whole DB structure/file backup is available.
Test No.: 9.3.3 Test Object: NetNumen U31 R18
Test Sub-item: Basic Data/Whole DB
Test Item: Task Management
Structure/File Backup
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) EMS interacts with NEs properly.
4) For the projects involving GDPR, the permission from the customer’s manager is
required before the operations. Besides, the operations should be performed under
the supervision of the compliance manager.
Test Procedure:
1) Select Maintenance >Task Management > Show Timing Task from the main
menu to enter the Task Management view.
2) Select Backup Basic Data/Whole DB Structure/File from the navigation tree on
the left.
3) The backup and period information of the Backup Basic Data/Whole DB
Structure/File is shown in the right middle of the interface.
4) There are the following buttons: View Log, Stop Backup and Suspend Backup
Task on this page.
5) Click Suspend Backup Task to open the Confirm dialog box and then click OK to
suspend the selected backup task.
6) Click Activate Backup Task to open the Confirm dialog box and then click OK to
activate the selected backup task.
Expected Results:
1) The Task Management view can be displayed.
2) The Backup Basic Data/Whole DB Structure/File task can be suspended, activated
and stopped.
3) The log of the backup task can be viewed.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
11.3.4 [ALL] File Clean-up
Test Content: Check that the function of file clean-up is available.
Test No.: 9.3.4 Test Object: NetNumen U31 R18
Test Item: Task Management Test Sub-item: File Clean-up
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance >Task Management > Show Timing Task from the main
menu to enter the Task Management view.
2) Select any node from the navigation tree under File Clean-up on the left, such as
Alarm Data Backup Directory Monitoring.
3) The description of the Alarm Data Backup Directory Monitoring task, such as
monitoring directory, execution period and cleanup strategy is shown in the right
middle of the window.
4) There are the following buttons: Refresh, Modify, Instantly Execute, View Log,
and File Information on this page.
5) Click Modify to modify the cleanup strategy and then click OK to submit the
modification.
6) Click Instantly Execute, the executed result dialog box is displayed.
7) Click View Log to view the task log.
8) Click File Information to query the backup file information.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The Task Management view can be displayed.
2) The cleanup strategy of the task can be queried and modified.
3) The backup and deletion task will be executed according to the modified strategy.
4) The clean-up task can be executed instantly.
5) The log and file information can be queried.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
11.3.5 [ALL] Automatically Acknowledging History Alarms
Test Content: Check that history alarms can be automatically acknowledged.
Test No.: 9.3.5 Test Object: NetNumen U31 R18
Test Sub-item: Automatically Acknowledging
Test Item: Task Management
History Alarms
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
authorized to perform task management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance >Task Management > Show Timing Task from the main
menu to open the Task Management window.
2) In the Task Management navigation tree, click Task Management > Common
Task > Alarm Background Task > Automatically Acknowledge History Alarms
Setting.
3) Click Modify, and set the number of days that is automatically acknowledged.
4) Click Save to quit the window.
Expected Results:
1) The user can log in to the client and open the Task Management window.
2) The automatically acknowledged history alarm task is modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
11.3.6 [ALL] MML Timing Task
Test Content: Check that the MML timing task can be managed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 9.3.6 Test Object: NetNumen U31 R18
Test Item: Task Management Test Sub-item: MML Timing Task
Input Parameter: none
Prerequisites:
1) Both the server and the client of EMS operate properly.
2) A connection is established between the client and the server, and the user is
authorized to perform maintenance management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Select Maintenance >Task Management > Show Timing Task from the main
menu to enter the Task Management view.
2) Select MML Timing Task from the navigation tree on the left. The related
information of the task will be displayed on the right
3) Click to create a new MML timing task, fill in the basic information and polity in
the Create Task window, and then click OK.
4) Select the task row and then click to view the task information.
5) Select the task row and then click to suspend the activated task.
6) Select the task row and then click to delete, modify and activate the
suspended task.
7) Select the task row and then click to view Log and show the executed
results.
Expected Results:
1) The Task Management view can be displayed.
2) The MML timing task can be created, modified and deleted.
3) The log and executed results of the task can be viewed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
12 Northbound Interface
The field engineers should select the northbound interface to be tested according to the
on-site commissioning situation.
12.1 CORBA Interface
12.1.1 [GUTLLNAG] CORBA Process Check
Test Content: Check that the CORBA process can be started properly.
Test No.: 10.1.1 Test Object: NetNumen U31 R18
Test Item: CORBA Interface Test Sub-item: CORBA Process Check
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) Make sure which CORBA standard specification is used (such as UMTS, TD, GSM,
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
LTETDD, and LTEFDD).
Test Procedure:
1) Check whether northbound CORBA processes are started normally according to the
following method:
a) Log in to the EMS server with a graphical interface tool and enter the ums-server
folder in the version installation directory, set the DISPLAY parameter correctly
with the user to start the EMS server, and then execute console-client.sh to start
the console client.
b) Check CORBA related processes on the server and on the console client.
Expected Results:
1) The returned results are different for different CORBA standard specifications. Use
UMTS as an example. If the icons are displayed as shown in the following figure,
then the three processes have been started normally. Please check the processes of
corresponding product according to CORBA standard.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
12.1.2 [GUTLL] Obtaining IOR Files
Test Content: Check that IOR files can be obtained properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 10.1.2 Test Object: NetNumen U31 R18
Test Item: CORBA Interface Test Sub-item: Obtaining IOR Files
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) Make sure which CORBA standard specification is used (such as UMTS, TDS,
GSM, LTETDD, and LTEFDD).
4) The CORBA processes are started properly.
Test Procedure:
1) Log in to the directory of the northbound process, and query northbound files
deployed in the /ums-server/procs/ppus/naf.ppu/ directory, containing different
CORBA standard specification files, such as:
/ums-server/procs/ppus/naf.ppu/naf-****-corba.pmu/(****which means different
standard specifications, such as UMTS, TDS, GSM, LTETDD, and LTEFDD)
2) Make sure which CORBA standard specification is used, and find the corresponding
directory, taking UMTS standard specification for example, IOR files directory is:
/ums-server/procs/ppus/naf.ppu/naf-umts-CORBA.pmu/ems-naf-umts-CORBA-
common-impl.par/conf/persistent/
Expected Results:
1) You can see the following IOR files in the persistent directory for the UMTS
standard specification:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
For different CORBA standard specifications, the IOR files may be different.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
12.2 [GTLL] Socket Interface
Test Content: Check that the function of Socket interface works properly.
Test No.: 10.2 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: Socket Interface
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) The northbound process has been started successfully.
Test Procedure:
1) Find the socket configuration file nafproc. Properties in the EMS server directory
/ums-server /procs/ppus/naf.ppu/naf-platform.pmu/ems-rtalarm-naf.par/conf. In
the file some parameters are:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) Configure the file parameters, such as the IP, the port according to the scene.
Expected Results:
1) The configuration file is in the directory, and the parameter is configurable.
2) After finish the configuration, the socket can be communicated.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
12.3 [GULLNAG] DB Interface
Test Content: Check that the function of northbound DB interface works properly.
Test No.: 10.3 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: DB Interface
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) The northbound process has been started successfully.
Test Procedure:
1) Use a northbound user and corresponding password to log in to the EMS DB: such
as: ztepmdb/Zte_pmdb_123 (use ORACLE DB for the small-machine environment,
and use SYSBASEIQ DB for the blade environment. For the login user name and
password, see the corresponding northbound DB interface commissioning guide).
2) Check whether the user can log in to the EMS DB and see the view.
Expected Results:
1) The login is successful and the user can see the view.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
But using other users cannot see the view.
2) And the view fields are the same as the DB interface document.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
12.4 [GUT] Network Planning and Optimization
Interface
Test Content: Check that the function of network planning and optimization interface works
properly.
Test No.: 10.4 Test Object: NetNumen U31 R18
Test Sub-item: Network Planning and
Test Item: Northbound Interface
Optimization Interface
Input Parameter: none
Prerequisites:
1) U31 server has been started normally.
2) The corresponding northbound service has been deployed in U31.
Test Procedure:
1) Start the task of network planning and optimization according to the corresponding
northbound file interface commissioning guide of V12.17 series.
2) Set the reported time and frequency.
Expected Results:
1) The file of network planning and optimization is generated in the designated path
and time.
2) The generated file of network planning and optimization satisfies the requirement of
the interface file.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
12.5 [GULLN] File Interface Customization Tool
Test Content: Check that the function of northbound file interface works properly.
Test No.: 10.5 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: File Interface Customization Tool
Input Parameter: none
Prerequisites:
1) The “NAF COMMON” package and “GUT NAF” package have been installed on
U31.
2) U31 server has been started normally.
3) The license of the file interface customization tool has been obtained and uploaded
to U31 server.
Test Procedure:
1) Log in to the U31 server using the graphical interface tool. Go to \ums-
server\utils\NafConfigCenter under the version installation directory, and run
NafConfigCenterTool.bat or NafConfigCenterTool.sh to log in to the tool. You
need to bind the license when using the tool for the first time. The user name for the
timing task of the configuration file interface is file, and the password is
U_tybx_2012_f. Select the language and click Login.
2) Enter the parameter configuration window of the tool, and create a customized rule.
You can use the base rule as the template to create. Select the created rule, and
click the Edit button of counter properties to edit, add or modify the counter. The
response time is long when you click Edit for the first time.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) Create a performance task, and use the customized rule created in step 2. After the
performance task is successfully created, click Activate Task, and then click Save.
The task can be executed periodically at the scheduled time.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) When the designated time is up, find the file generated by the task according to the
local file path displayed in the customized rule properties.
Expected Results:
1) The file interface customization tool can be used to customize the performance rule
and task.
2) The file can be generated at the scheduled time according to the task and rule
settings.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
12.6 [LLN] CTCC I1 Interface
Test Content: Check that the function of CTCC I1 interface works properly.
Test No.: 10.6 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: CTCC I1 Interface
Input Parameter: none
Prerequisites:
1) The “NAF COMMON” package and “NAF CTCC I1 Interface” package have been
installed on U31.
2) U31 server has been started normally.
Test Procedure:
1) Check CTCC I1 process is normally started, using the following methods for
reference:
a) Use the graphical interface tool to login to U31 server, and enter the ums-server
directory under the version installation path. Use the user for starting U31 server to
correctly set the DISPLAY parameter, and execute console-client.sh to start the
console client.
b) On the server console client, check CTCC I1 process.
2) Check whether the I1 performance task is created: open EMS client, click
Performance > Performance Task Management, and check whether the I1
performance task exists in the window.
3) Check whether the performance file exists under the northbound directory of I1
interface (For the directory and login username and password, refer to the relevant
northbound performance l1 interface commissioning guide).
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) Check that the following two processes are normally started. The icons displayed as
below indicate normal.
2) Performance task starting with l1 exists in the measurement task management
window of EMS client.
3) The performance file is generated in the designated directory, and is consistent with
the definition in the interface document.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
12.7 [ALL] SNMP Interface
Test Content: Check that the function of SNMP interface works properly.
Test No.: 10.7 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: SNMP Interface
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) The northbound process has been started successfully.
Test Procedure:
1) Commission the unified SNMP interface in accordance with NetNumen U31 R18
V12.17 unified northbound SNMP interconnection guide. Of the common agents,
agent 1 is recommended to use. Without the operator’s special requirement, the
default agent and other agents do not need to be opened.
2) When the NE connected to U31 has alarm reporting or restoration, check whether
the trap message received by the upper-level northbound is correct.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The unified SNMP interface can be commissioned in accordance with the guide.
2) In accordance with the site conditions, if there is the upper-level northbound client,
trap message can be successfully received. If the site has the mibBrowser testing
tool, the tool can be used for interconnection to get trap message.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
12.8 [TLLN] CMCC New Socket Interface
Test Content: Check that the function of CMCC new Socket interface works properly.
Test No.: 10.8 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: CMCC New Socket Interface
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can communicate
with U31 server normally).
3) The northbound process has been started successfully.
Test Procedure:
1) Run the NafConfigCenterTool.sh script under the /ums-server/utils/NafConfigCenter
directory. Enter the user name and password: admin/U_tybx_2012_admin. On the
CMCC 2016 page, commission and deploy the CMCC new Socket interface. For
details, refer to the commissioning guide of corresponding version.
2) Run the Socket testing tool to receive Socket message.
3) Perform message and file synchronization.
Expected Results:
1) The message is normally received.
2) The message is consistent with the description in the interface file.
3) Message and file synchronization is performed successfully.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
12.9 [LLN] CTCC I1 Socket Interface
Test Content: Check that the function of CTCC l1 Socket interface works properly.
Test No.: 10.9 Test Object: NetNumen U31 R18
Test Item: Northbound Interface Test Sub-item: CTCC I1 Socket Interface
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The network communication is proper (The upper-level northbound can
communicate with U31 server normally).
3) The northbound process has been started successfully.
Test Procedure:
1) Run theNafConfigCenterTool.sh script under the /ums-server/utils/NafConfigCenter
directory. Enter the user name and password: admin/U_tybx_2012_admin. On the
CTCC l1 Interface page, commission and deploy the CTCC l1 Socket interface. For
details, refer to the commissioning guide of corresponding version.
2) Run the Socket testing tool to receive Socket message.
3) Send the alarm synchronization request.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The message is normally received.
2) The message is consistent with the description in the interface file.
3) The alarm is synchronized successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
13 LTE SON
13.1 General Requirements of SON Policy
Management
13.1.1 [LTE] Logging in to SON Policy Management
Test Content: Check that the function of logging in to SON Policy Management works properly.
Test No.: 11.1.1 Test Object: NetNumen U31 R18
Test Item: General Requirements of SON Policy Test Sub-item: Logging in to SON Policy
Management Management
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform configuration management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) Select Configuration > MO SDR SON Configuration Management > MO SDR
SON Configuration Management, the MO SDR SON Configuration Management
interface appears.
2) In the SON Management tree, select SON Policy Management, the SON Policy
Management can be opened.
Expected Results:
1) The SON Policy Management window can be opened.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
13.1.2 [LTE] Creating SON Policy Template
Test Content: Check that SON Policy Template can be created.
Test No.: 11.1.2 Test Object: NetNumen U31 R18
Test Item: General Requirements of SON Policy
Test Sub-item: Creating SON Policy Template
Management
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform configuration management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) In the SON Management tree, select SON Policy Management > SON Policy
Template, the SON Policy Template interface can be opened in the right window.
2) In the Policy Template tree, select the template, and click the Create button to create
SON Policy Template.
Expected Results:
1) The SON Policy Template can be created.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
13.1.3 [LTE] Setting SON Policy Template
Test Content: Check that SON Policy Template can be set.
Test No.: 11.1.3 Test Object: NetNumen U31 R18
Test Item: General Requirements of SON Policy
Test Sub-item: Setting SON Policy Template
Management
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform configuration management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) In the SON Management tree, select SON Policy Management > SON Policy
Template, the SON Policy Template interface can be opened in the right window.
2) In the Policy Template tree, select the created template and click the Set button.
Then, in the displayed window, select the NE or Cell that needs to set the policy
template.
Expected Results:
1) The SON Policy Template can be set.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
13.2 [LTE] Configuring the SON Breakpoint
Test Content: Check that SON Breakpoint can be configured.
Test No.: 11.2 Test Object: NetNumen U31 R18
Test Item: LTE SON Test Sub-item: Configuring the SON Breakpoint
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform SON management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) In the SON Management tree, select SON Policy Management > SON Policy
Template, the SON Policy Template interface can be opened in the right window.
2) In the Policy Template tree, select the template, and click the Create button to create
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
SON Policy Template.
3) In the displayed window, configure the Reference Point as Break Point.
Expected Results:
1) The SON Reference Point can be configured as Break Point.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
13.3 [LTE] Triggering the SON Breakpoint
Test Content: Check that SON Breakpoint can take effect.
Test No.: 11.3 Test Object: NetNumen U31 R18
Test Item: LTE SON Test Sub-item: Triggering the SON Breakpoint
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform SON management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Trigger the SON process in accordance with the set policy template.
2) In the SON Management tree, select SON Policy Management > SON Monitor
Management > Real-Time Monitoring > Deploy Monitoring, and observe the
process of SON. The Break Point will take effect in accordance with the set policy
template.
Expected Results:
1) The SON Break Point can take effect in accordance with the set policy template.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
13.4 [LTE] Recovering the SON Breakpoint
Test Content: Check that SON Breakpoint can be recovered.
Test No.: 11.4 Test Object: NetNumen U31 R18
Test Item: LTE SON Test Sub-item: Recovering the SON Breakpoint
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The connection between the client and the server is normally established, and the
user is authorized to perform SON management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) In the SON Management tree, select SON Policy Management > SON Monitor
Management > Real-Time Monitoring > Deploy Monitoring, and select a
monitoring message about the taking effect of Break Point. The users can choose to
continue or cancel the process of SON.
2) When timed out, the system automatically chooses to continue or cancel the process
of SON in accordance with the set policy.
Expected Results:
1) The SON Break Point can be recovered in accordance with the set policy.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
13.5 [LTE] Viewing the SON Breakpoint
Test Content: Check that SON Breakpoint can be viewed.
Test No.: 11.5 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: LTE SON Test Sub-item: Viewing the SON Breakpoint
Input Parameter: None
Prerequisites:
1) EMS server and client are started properly.
2) The connection between the client and the server is normally established, and the
user is authorized to perform SON management operations.
3) EMS server interacts with NEs properly, and the NE Management has been started.
Test Procedure:
1) In the SON Management tree, select SON Policy Management > SON Monitor
Management > Monitoring Query, the messages can be viewed whether the
Breakpoint takes effect.
Expected Results:
1) The SON Break Point can be viewed in the Monitoring Query interface.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
14 Inspection Tool Test (V1)
14.1 [GUTFTL] Connecting to the Inspection
Equipment
Test Content: Check that the inspection tool is connected to the inspection equipment properly.
Test No.: 12.1 Test Object: NetNumen U31 R18
Test Sub-item: Connecting to the Inspection
Test Item: Inspection Tool Test
Equipment
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started properly.
2) A connection is established between the client and the server.
Test Procedure:
1) Enter the intelligent inspection tool interface from the client portal.
2) Open the inspection tool client.
Expected Results:
1) The directory of the inspection tool is found on the client, and the inspection tool
client of EMS is opened successfully.
2) The user logs in to the inspection tool successfully.
3) The corresponding inspection function menus are displayed on the main page of the
inspection tool.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
14.2 [GUTFTL] Scene Management
Test Content: Check that the function of scene management works properly.
Test No.: 12.2 Test Object: NetNumen U31 R18
Test Item: Inspection Tool Test Test Sub-item: Scene Management
Input Parameter: None
Prerequisites:
1) EMS server and client are started normally.
2) Log in to the client of inspection tool and connect to EMS inspection equipment
successfully.
Test Procedure:
1) Open the client of inspection tool and log in.
2) In the menu of inspection tool, click View > Scene to open the Scene view, and click
New on the toolbar.
3) Input the scene name in the displayed box, and select the scene type.
4) All the items related to the scene type are displayed on the tab of inspection item
setting selection. Select the corresponding inspection item according to the
requirement, and click OK to finish the scene creation after the configuration is
completed.
Expected Results:
1) The newly-created scene can be displayed in the scene list on the left of the scene
interface.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
14.3 Inspection Task
14.3.1 [GUTFTL] Creating a Task
Test Content: Check that an inspection task can be created.
Test No.: 12.3.1 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Creating a Task
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
Test Procedure:
1) Click View >Task in the menu of inspection tool to open the Task view, and click the
New button on the toolbar to open the New Task dialog box.
2) In the displayed inspection task dialog box, enter the task name.
3) On the Inspection Content page, select a scene or an inspection item such as the
item of system basic information. The items can be filtered by product, NE type, NE
version.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
4) Switch to the Equipment page, and select Inspection Object.
5) Switch to the Parameter page, and select the Execute Type such as Instant. And
set other parameters according to the requirement. Then, click OK to create an
inspection task.
Expected Results:
1) The inspection task just created is displayed in the task list.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
14.3.2 [GUTFTL] Viewing a Task
Test Content: Check that the inspection task can be viewed.
Test No.: 12.3.2 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Viewing a Task
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task has been created.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Select a task from the task list, and click the View button on the toolbar to open the
dialog box of viewing the task.
2) View the task information such as task name, check item and inspection object etc.
in the pop-up dialog box.
Expected Results:
1) The instant task can be viewed successfully, and the task information is consistent
with the settings.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
14.3.3 [GUTFTL] Modifying a Task
Test Content: Check that the inspection task can be modified.
Test No.: 12.3.3 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Modifying a Task
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) An inspection task in the status of suspended already exists.
Test Procedure:
1) Select from the task list an inspection task in the status of suspended, and click the
Modify button on the toolbar to open the dialog box of modifying the task.
2) Modify the task information such as check item and inspection object etc. in the
displayed dialog box, and click OK to save the modification.
Expected Results:
1) The inspection task has been modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
14.3.4 [GUTFTL] Activating a Task
Test Content: Check that inspection task can be activated.
Test No.: 12.3.4 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Activating a Task
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The inspection tool client has been connected to the inspection equipment.
3) An instant inspection task has been created.
Test Procedure:
1) Select from the task list a created inspection task in the status of suspended, and
click the Activate button on the toolbar.
2) The task status becomes activated, and the task begins to run.
3) The task execution progress is displayed in the result bar in the lower part of the
window.
Expected Results:
1) The selected task can be activated, and executed successfully.
2) During activation, the Activate button on the toolbar is disabled.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
14.3.5 [GUTFTL] Deleting a Task
Test Content: Check that the inspection task can be deleted.
Test No.: 12.3.5 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Deleting a Task
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task in the status of suspended already exists.
Test Procedure:
1) Select from Task List a task in the status of suspended, and then click the Delete
button on the toolbar. The Confirm dialog box is displayed.
2) Click OK to delete the selected task.
Expected Results:
1) The selected task can be successfully deleted and disappears from in the task list.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
14.4 [GUTFTL] Report Management
Test Content: Check that the report generated by the inspection task is correct.
Test No.: 12.4 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: Inspection Tool Test Test Sub-item: Report Management
Input Parameter: None
Prerequisites:
1) EMS server and client have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task that has been executed exists.
Test Procedure:
1) Select View > Report on the menu bar of inspection tool to open the report view.
The corresponding report of the inspection task that has been executed is displayed
in the left pane. Choose a report file, and inspection items are displayed in the upper
right pane of the window. Click a corresponding inspection item, and the specific
inspection result is displayed in the lower part of the window.
2) Or you can select a task that has been executed in the inspection task view. Then,
select a row of record about task execution in the lower part of the window and click
Navigate to Report Folder from the context menu. The folder that includes the
corresponding Excel report file of the task report can be opened.
Expected Results:
1) The report of task execution result is viewed successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
14.5 [GUTFTL] Fault Collection Management
Test Content: Check that the function of collecting NE faults works properly.
Test No.: 12.5 Test Object: NetNumen U31 R18
Test Item: Inspection Tool Test Test Sub-item: Fault Collection Management
Input Parameter: None
Prerequisites:
1) EMS server and client have been started.
2) The inspection tool client has been connected to the inspection equipment.
Test Procedure:
1) Select View > Fault Collection on the menu bar of inspection tool to open the Fault
Collection view. Then, click New on the toolbar to open the Fault Collection Task
dialog box.
2) Enter the task name in the displayed dialog box.
3) On the Fault Collection Content page, select the required fault collection items,
and check the corresponding fault collection items.
4) Switch to the Equipment page, and select an NE device that requires fault
collection.
5) Switch to the Parameter page, and set the conditions as required, such as fault
collection time. Then, click OK.
6) The task that has been created can be seen in the fault collection task list. The initial
status of the task is suspended by default. Select the task and click Activate from
the context menu, or click Activate on the toolbar. Then, the task begins to be
executed.
7) The situation of task execution such as status, execution progress and details can
be seen below the task list.
8) After execution, select a row of record about a task that has been executed, and
click Navigate to Report Folder from the context menu. Then, you can see the
generated report file.
Expected Results:
1) The fault collection task can successfully finish collection and generate a report, and
a message can be displayed if failed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
15 Inspection Tool Test (V2)
15.1 [ALL] Connecting to the Inspection Equipment
Test Content: Check that the inspection tool is connected to the inspection equipment properly.
Test No.: 13.1 Test Object: NetNumen U31 R18
Test Sub-item: Connecting to the Inspection
Test Item: Inspection Tool Test
Equipment
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started properly.
2) A connection is established between the client and the server.
Test Procedure:
1) Enter the intelligent inspection tool interface from the client portal.
2) Open the inspection tool client.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The directory of the inspection tool is found on the client, and the inspection tool
client of EMS is opened successfully.
2) The user logs in to the inspection tool successfully.
3) The corresponding inspection function menus are displayed on the main page of the
inspection tool.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
15.2 [ALL] Scene Management
Test Content: Check that the function of creating scene template works properly.
Test No.: 13.2 Test Object: NetNumen U31 R18
Test Item: Inspection Tool Test Test Sub-item: Scene Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started properly.
2) The inspection tool client has been connected to the inspection equipment.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) Open the inspection tool client and log in to it.
2) Click Configuration > Scene to open the Scene Management view. Right-click the
Customized Scene node, and select Add.
3) In the displayed window, enter the scene name. You can select an existing scene to
copy.
4) In the right-side group tree, mount all the current groups that support inspection,
select and click Save. A message about saved successfully is displayed.
Expected Results:
1) You can see the created scene under the Customized Scene node in the left scene
tree in the Scene Management view.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
15.3 Inspection Task
15.3.1 [ALL] Creating a Task
Test Content: Check that an inspection task can be created.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 13.3.1 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Creating a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
Test Procedure:
1) Click the New button on the toolbar to open the New Task dialog box.
2) In the displayed inspection task dialog box, enter the task name, and select the
scene.
3) In the left Inspection Object tree, select inspection objects. The selected inspection
objects are displayed in the right list.
4) Switch to the Parameter page, select the Execute Type such as Instant, and set
the data collection time.
5) Click OK to create an inspection task.
Expected Results:
1) The inspection task just created is displayed in the task list.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
15.3.2 [ALL] Viewing a Task
Test Content: Check that an inspection task can be viewed.
Test No.: 13.3.2 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Viewing a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task has been created.
Test Procedure:
1) Select a task from the task list, and click the View button on the toolbar to open the
dialog box of viewing the task.
2) In the displayed dialog box, view the task information, such as task name, scene,
inspection object, and inspection parameter.
Expected Results:
1) The inspection task can be viewed successfully, and the task information is
consistent with the settings.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
15.3.3 [ALL] Modifying a Task
Test Content: Check that an inspection task can be modified.
Test No.: 13.3.3 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Modifying a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task in the status of suspended already exists.
Test Procedure:
1) Select from the task list an inspection task in the status of suspended, and click the
Modify button on the toolbar to open the dialog box of modifying the task.
2) In the displayed dialog box, modify the task information, such as scene, inspection
object and inspection parameter, and click OK to save the modification.
Expected Results:
1) The inspection task has been modified successfully.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
15.3.4 [ALL] Activating a Task
Test Content: Check that an inspection task can be activated.
Test No.: 13.3.4 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Activating a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task has been created.
Test Procedure:
1) Select from the task list a task in the status of suspended that has been created, and
click the Activate button on the toolbar.
2) The task state becomes activated. The instant task begins to run. The timing task is
executed when the waiting time is up.
3) In the lower result bar, the task execution progress is displayed.
Expected Results:
1) After activation is finished, the task state becomes activated. The instant task begins
to run. The timing task is executed when the waiting time is up.
2) In the process of activation, the Activate button on the toolbar is disabled and
unavailable.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
15.3.5 [ALL] Deleting a Task
Test Content: Check that an inspection task can be deleted.
Test No.: 13.3.5 Test Object: NetNumen U31 R18
Test Item: Inspection Task Test Sub-item: Deleting a Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) An inspection task in the status of suspended already exists.
Test Procedure:
1) Select from the task list an inspection task in the status of suspended, and click the
Delete button on the toolbar to open the dialog box of confirming to delete the task.
2) Click OK to delete the selected task.
Expected Results:
1) The selected task can be successfully deleted and disappears from the task list.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
15.4 [ALL] Report Management
Test Content: Check that the report generated in the inspection task is correct.
Test No.: 13.4 Test Object: NetNumen U31 R18
Test Item: Inspection Tool Test Test Sub-item: Report Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS have been started.
2) The inspection tool client has been connected to the inspection equipment.
3) Finished tasks exist in the inspection tasks.
Test Procedure:
1) Select from the task list an inspection task that has been successfully executed, and
click it. The lower table displays the details of the task execution. Click the
Download Report button. In the displayed file saving dialog box, set the saving
path.
2) After saving successfully, you are reminded of whether to navigate. Click OK to open
the download path.
Expected Results:
1) The result report of the executed task can be viewed successfully.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
16 Controller NE Management
16.1 Configuration Management
16.1.1 [GUT] Logging in to Configuration Management
Test Content: Check that the user can log in to the Configuration Management view.
Test No.: 14.1.1 Test Object: NetNumen U31 R18
Test Sub-item: Logging in to Configuration
Test Item: GU Configuration Management
Management
Input Parameter: none
Prerequisites:
1) The network environment is well prepared. Both the server and the client of EMS
operate properly.
2) The user can log in to the client and is authorized to perform the configuration
management operations.
3) EMS interacts with NEs properly.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node of GSM or UMTS from the NE topology tree,
right-click it and select NE Management > Configuration Management from the
displayed shortcut menu.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The Configuration Management page can be opened.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.2 [GUT] Creating an NE
Test Content: Check that GSM or UMTS NE can be created.
Test No.: 14.1.2 Test Object: NetNumen U31 R18
Test Item: GU Configuration Management Test Sub-item: Creating an NE
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Log in to the client, select the root node GSM or UMTS from the configuration
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
resource tree, right-click it and then select Create > Subnetwork. The Command
Process page appears.
2) Enter the user label, subnetwork id and other parameters in the displayed dialog box
then click OK.
3) Right-click the created subnetwork, select the menu Create NE.
4) In the pop-up dialog box, set the NE type as GSM or UMTS. Configure the
parameters such as userlabel and OMC IP of log server.
5) Click Save button from the tool bar to create NE of GSM or UMTS.
Expected Results:
1) Input the correct parameters and the sub-network can be created successfully.
2) Input the correct parameters and the NE can be created successfully.
3) If the input parameters are not correct, creating of the NE and sub-network failed,
and gives the error reason.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.3 [GUT] Applying for/Releasing the Mutex Right
Test Content: Check that GSM or UMTS mutex right can be applied for or released.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test No.: 14.1.3 Test Object: NetNumen U31 R18
Test Sub-item: Applying for/Releasing the
Test Item: GU Configuration Management
Mutex Right
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Log in to the client, select the NE node last created from the configuration resource
tree. Right-click it and then select apply mutex right.
2) Select the node last created, right-click it and then select release mutex right
(option).
Expected Results:
1) The NE mutex right can be applied and released. When the mutex right is applied,
the operator can add, delete and modify the NE data, and import or export the
configuration data.
2) When mutex right is released, NE information can only be viewed.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
16.1.4 [GUT] Viewing the NE Information
Test Content: Check that the NE Information can be viewed.
Test No.: 14.1.4 Test Object: NetNumen U31 R18
Test Item: GU Configuration Management Test Sub-item: Viewing the NE Information
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Log in to the client, select the Managed element node last created from the
configuration resource tree.
2) Double-click it, and the NE information is displayed in the right view.
Expected Results:
1) The NE configuration information can be viewed.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
16.1.5 [GUT] Modifying the NE Information
Test Content: Check that the NE Information can be modified.
Test No.: 14.1.5 Test Object: NetNumen U31 R18
Test Item: GU Configuration Management Test Sub-item: Modifying the NE Information
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Log in to the client, select the Managed element node last created from the
configuration resource tree.
2) Double-click it, and the NE information is displayed in the right view.
3) Right-click the NE node, and select the menu applies mutex right.
4) Click the modify button in the tab.
5) Set the NE properties.
6) Click the save button in the tab.
Expected Results:
1) The NE configuration information can be modified.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.6 [GUT] Synchronizing All/Modified Tables
Test Content: Check that the BSC can be synchronized with the NE information.
Test No.: 14.1.6 Test Object: NetNumen U31 R18
Test Sub-item: Synchronizing All/Modified
Test Item: GU Configuration Management
Tables
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Log in to the client, select the Managed element node which is connected with the
BSC from the configuration resource tree.
2) Right-click the NE node, and select the menu applies mutex right.
3) Click the Synchronize modified Tables button or the Synchronize all Tables
button in the tab.
4) Click OK.
Expected Results:
1) The NE synchronizing information can be viewed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.7 [GUT] Data Backup
Test Content: Check that the data can be backed up.
Test No.: 14.1.7 Test Object: NetNumen U31 R18
Test Item: GU Configuration Management Test Sub-item: Data Backup
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The BSC NE has been created.
Test Procedure:
1) Log in to the Configuration Management page, and select the menu Management
> Data Management > Data Backup, the Data Backup dialog box is displayed.
2) Select the storage path from the dialog box, enter the file name prefix, select the
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
managed elements to be backed up, and then click OK. The progress bar is
displayed.
3) Later, the command will be finished. The Data Backup Result text is displayed
asking whether the backup is successful and displaying the information of the
backup file path.
Expected Results:
1) The backup is successful. The information of the backup result and the storage path
of the backup file will be displayed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.8 [GUT] Deleting an NE
Test Content: Check that an NE can be deleted.
Test No.: 14.1.8 Test Object: NetNumen U31 R18
Test Item: GU Configuration Management Test Sub-item: Deleting an NE
Input Parameter: none
Prerequisites:
1) The EMS server operates properly.
2) A connection is established between the client and the server, and the user is
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
authorized to perform configuration management operations.
3) The EMS server interacts with the OMM properly.
Test Procedure:
1) Enter the Configuration Management window, select GSM or UMTS ME that has
been created, and apply for mutex rights.
2) Select Configuration Management > Advanced > Batch NE Operation to display
the Batch NE Operation window.
3) Select an ME to be deleted, and click Delete.
4) Fill in the verification code in the displayed dialog box, and then click OK.
Expected Results:
1) The NE has been deleted successfully, and the deleted NE has appeared from the
left resource tree.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.1.9 [GUT] Data Recovery
Test Content: Check that the data can be recovered.
Test No.: 14.1.9 Test Object: NetNumen U31 R18
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Item: GU Configuration Management Test Sub-item: Data Recovery
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the Configuration Management page, and select the menu Management
> Data Management > Data Recover, the Data Recover dialog box is displayed.
2) Select a backup file from the dialog box, select ConfigSet(s) to recover, check the
Create the needed subnetworks and managed elements if necessary (if there
isn’t subnetwork or NE to be imported in the current OMM, you must check it,
otherwise the button OK is disabled), and then click OK, then the progress bar is
displayed.
3) Later, the command will be finished. The Data Recover Result text pops up
displaying the information of the data recovery.
Note: It is recommended that data recovery be performed on the tested NEs. Do not perform
this operation in the existing network.
Expected Results:
1) The recovery is successful. You can see the data recovered from the configuration
resource tree.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
16.2 Software Version Management (V3)
16.2.1 [GUT] Logging in to Software Version Management
Test Content: Check that the user can log in to Software Version Management.
Test No.: 14.2.1 Test Object: NetNumen U31 R18
Test Sub-item: Logging in to Software Version
Test Item: GU Software Version Management
Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node from the NE tree, right-click it and select NE
Management > Software Management from the displayed shortcut menu.
Expected Results:
1) The Software Management page can be opened.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
16.2.2 [GUT] Creating a Version Package
Test Content: Check that a software version package can be created.
Test No.: 14.2.2 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Creating a Version Package
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The version package has been prepared.
Test Procedure:
1) Enter the Software Version Management window, right-click the controller software
package management node in the left configuration resource tree, and select Create
Version Package from the displayed shortcut menu.
2) Select a BSC version file, and then fill in the userlabel information.
3) Click OK.
Expected Results:
1) The BSC software version package can be created.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
16.2.3 [GUT] Viewing a Software Version
Test Content: Check that a software version can be viewed.
Test No.: 14.2.3 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Querying a Software Version
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Enter the Software Version Management window, expand the configuration
resource tree, and expand the controller software package management node. The
created software versions can be shown in the resource tree. Right-click a specific
software version node to open the corresponding window in the right pane.
2) The details of the corresponding software version can be viewed in the opened
window.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The software version information shown on the client GUI is true.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.2.4 [GUT] Downloading a Version Package
Test Content: Check that a software version package can be downloaded.
Test No.: 14.2.4 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Downloading a Version Package
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The version package has already been created.
Test Procedure:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) Enter the Software Version Management window, select the created version
package from the left configuration resource tree, right-click it and select Download
from the displayed shortcut menu. A dialog box indicating version selection is
displayed.
2) In the upper part of the displayed dialog box, select Select All from the drop-down
box, and click OK. A dialog box indicating NE selection is displayed.
3) In the displayed dialog box, select ME and click OK.
Expected Results:
1) The result information on whether the version package has been downloaded
successfully can be displayed, and the reasons for failure will be given if failed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.2.5 [GUT] Activating a Version Package
Test Content: Check that a software version package can be activated.
Test No.: 14.2.5 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Activating a Version Package
Input Parameter: none
Prerequisites:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) A link must be connected with the NE.
Test Procedure:
1) Enter the Software Version Management window, select the downloaded version
package from the left configuration resource tree, right-click it and select Activate
from the displayed shortcut menu. A dialog box indicating version selection is
displayed.
2) In the upper part of the displayed dialog box, select Select All from the drop-down
box, and click OK. A dialog box indicating NE selection is displayed.
3) In the displayed dialog box, select ME and click OK.
Expected Results:
1) The result information on whether the version package has been activated
successfully can be displayed, and the reasons for failure will be given if failed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
16.3 Software Version Management (V4)
16.3.1 [GUAM] Logging in to Software Version Management
Test Content: Check that the user can log in to Software Version Management.
Test No.: 14.3.1 Test Object: NetNumen U31 R18
Test Sub-item: Logging in to Software Version
Test Item: GU Software Version Management
Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node of from the NE tree, right-click it and select NE
Management > Software Version Management from the displayed shortcut menu.
Expected Results:
1) The Software Version Management page can be opened.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
16.3.2 [GUAM] Downloading a Version Package
Test Content: Check that a version package can be downloaded.
Test No.: 14.3.2 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Downloading a Version Package
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The version package has already been created.
Test Procedure:
1) Enter the Software Version Management window, right-click controller-OMP node
and select Version Download from the displayed shortcut menu. A dialog box
indicating version download is displayed.
2) Click the Add button, and select the software package to be downloaded.
Expected Results:
1) The result information on whether the version package has been downloaded
successfully can be displayed, and the reasons for failure will be given if failed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
16.3.3 [GUAM] Viewing a Software Version
Test Content: Check that a software version can be viewed.
Test No.: 14.3.3 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Viewing a Software Version
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Enter the Software Version Management window, and select Created Version
Package Management from the menu in the window.
2) The software version information of corresponding NEs can be viewed in the opened
window.
Expected Results:
1) The software version information shown on the client GUI is true.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
16.3.4 [GUAM] Validating a Software Version
Test Content: Check that a software version can be validated.
Test No.: 14.3.4 Test Object: NetNumen U31 R18
Test Item: GU Software Version Management Test Sub-item: Validating a Software Version
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) A link must be connected with the NE.
Test Procedure:
1) Enter the Software Version Management window, right-click controller-OMP node
and select Version Download from the displayed shortcut menu. A dialog box
indicating version download is displayed.
2) Enter the verification code and click OK.
Expected Results:
1) The result information on whether the version package has been validated
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
successfully can be displayed, and the reasons for failure will be given if failed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
16.4 [GUAM] Status Management
Test Content: Check that the function of GU status management works properly.
Test No.: 14.4 Test Object: NetNumen U31 R18
Test Item: GU NE Management Test Sub-item: Status Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform status management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node from the NE tree, right-click it and select NE
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Management > Status Management from the displayed shortcut menu. The Status
Management window is displayed.
3) Expand the nodes in the configuration resource tree, right-click each object node
under the corresponding NE node to open the status information window in the right
pane.
4) The status information of corresponding objects can be viewed in the opened
window.
Expected Results:
1) The status information of the objects shown on the client GUI is true.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
17 BS NE Management
17.1 Configuration Management
17.1.1 [ALL] Exporting the BS Data
Test Content: Check that the function of exporting the BS data works properly.
Test No.: 15.1.1 Test Object: NetNumen U31 R18
Test Item: SDR Configuration Management Test Sub-item: Exporting the BS Data
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Enter the SDR Configuration Management window, and select Configuration
Management > Data Export. The Data Export dialog box is displayed.
2) In the displayed dialog box, select the NEs to be exported and the export directory,
and click Export. The execution progress dialog box is displayed.
3) After execution is finished, the operation result dialog box is displayed.
Expected Results:
1) The data information of selected NEs can be successfully exported to the set
storage path, and the operation result information can be given.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
17.1.2 [ALL] Importing the BS Data
Test Content: Check that the function of importing the BS data works properly.
Test No.: 15.1.2 Test Object: NetNumen U31 R18
Test Item: SDR Configuration Management Test Sub-item: Importing the BS Data
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Enter the SDR Configuration Management window, and select Configuration >
Data Import. The Data Import dialog box is displayed.
2) In the displayed dialog box, click Browse to open the file to be imported.
3) Click Import to import the file. After execution is finished, the operation result dialog
box is displayed.
Expected Results:
1) NE information can be successfully imported, and the operation result information
can be given.
2) NE information that has been successfully imported can be seen in the configuration
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
resource tree.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
17.1.3 [ALL] Synchronizing All/Modified Tables of BS
Test Content: Check that the function of synchronizing all/modified tables of BS works properly.
Test No.: 15.1.3 Test Object: NetNumen U31 R18
Test Sub-item: Synchronizing All/Modified
Test Item: SDR Configuration Management
Tables of BS
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The SDR managed NE has been created. The configuration set used in the test
must be connected with the foreground.
Test Procedure:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) In the SDR Configuration Management window, select the created SDR managed
NE, and apply for Mutex Right. The NE information window is displayed by double-
clicking. Click the Modify button on the toolbar to modify some configuration items
that do not affect the business.
2) Select SDR managed NE on the left, right-click it and select Synchronize All Tables
or Synchronize Modified Tables from the context menu.
3) Perform the follow-up operations according to the messages. After synchronization,
the message of successful synchronization is displayed.
Expected Results:
1) Synchronizing all tables or synchronizing modified tables can be performed
successfully, and the message of successful synchronization is displayed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
17.1.4 [ALL] Comparing the Configuration Data
Test Content: Check that the function of comparing the configuration data works properly.
Test No.: 15.1.4 Test Object: NetNumen U31 R18
Test Sub-item: Comparing the Configuration
Test Item: SDR Configuration Management
Data
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Expand the configuration resource tree, right-click one Configset in the SDR
Configuration Management window, and select Source Subtree from the
displayed shortcut menu.
2) Right-click another Configset, and select Compare with Source Subtree from the
displayed shortcut menu.
Expected Results:
1) After setting the source subtree and destination subtree, if the NE type is different, a
warn dialog box will be displayed, indicating that the NE type is different. If the type
is the same, the comparison result dialog box will be displayed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
17.1.5 [ALL] Uploading Configuration Data from NEs
Test Content: Check that the function of uploading configuration data from NEs works properly.
Test No.: 15.1.5 Test Object: NetNumen U31 R18
Test Sub-item: Uploading Configuration Data
Test Item: Configuration Management
from NEs
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Enter the SDR Configuration Management window, and select Configuration
Management > Upload Configuration Data from NEs. The Upload Configuration
Data from NEs window is displayed.
2) In the displayed window, select the NEs to be uploaded, and click Upload.
Expected Results:
1) The configuration data is uploaded successfully, and the corresponding message is
displayed.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
17.2 SDR Software Version Management
17.2.1 [ALL] Logging in to Software Version Management
Test Content: Check that the user can log in to the Software Version Management view.
Test No.: 15.2.1 Test Object: NetNumen U31 R18
Test Sub-item: Logging in to Software Version
Test Item: SDR Software Version Management
Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node of SDR from the NE topology tree, right-click it
and select NE Management > Software Version Management from the displayed
shortcut menu.
Expected Results:
1) The Software Version Management view can be opened.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
17.2.2 [ALL] Version Repository Management
Test Content: Check that the function of version repository management works properly.
Test No.: 15.2.2 Test Object: NetNumen U31 R18
Test Item: SDR Software Version Management Test Sub-item: Version Repository Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The version package has been prepared.
Test Procedure:
1) Enter the Software Version Management window, and click the Version
Repository Management node in the left tree. The Version Repository
Management window is displayed.
2) Click the Add Version Package button. The Open dialog box is displayed. Select
the version package to be added and click Open.
Expected Results:
1) The correct version package can be added successfully, and can be displayed in the
version package list.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
17.2.3 [ALL] Upgrade Task Management
Test Content: Check that the function of upgrade task management works properly.
Test No.: 15.2.3 Test Object: NetNumen U31 R18
Test Item: SDR Software Version Management Test Sub-item: Upgrade Task Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The version package has already been created.
Test Procedure:
1) Enter the Software Version Management window, and click Upgrade Task
Management in the left tree. The Upgrade Task Management window is displayed.
2) In the displayed window, click the New Upgrade Task button on the toolbar to open
the New Upgrade Task window. Select the NEs and version package to be
upgraded, and select the operation (download, activate, etc.), and click OK.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
3) A confirmation dialog box is displayed. Enter the verification code and click OK.
4) The created task can be seen in the task list. Right-clicking the task can execute the
task again, view the task and delete the task, etc.
Note: The specific operation steps may be slightly different due to version difference of
the lower-level system. Please perform the operations according to the messages
displayed in the window.
Expected Results:
1) The upgrade task is created successfully. All the operations are normally performed.
If one of them fails, the cause of failure will be given in the details.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
17.2.4 [ALL] Query Task Management
Test Content: Check that the function of query task management works properly.
Test No.: 15.2.4 Test Object: NetNumen U31 R18
Test Item: SDR Software Version Management Test Sub-item: Query Task Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) A link must be connected with the foreground.
Test Procedure:
1) Enter the Software Version Management window, and click Query Task
Management in the left tree. The Query Task Management window is displayed.
2) In the displayed window, click the New Query Task button on the toolbar to open the
New Query Task window.
3) Enter the task name, select NE, version package and board standard, and click OK.
4) In the task list, you can view the task status, or right-click the task to execute again,
stop and delete the task, etc.
5) Click the Version Package Status tab in the lower pane to view the version
package information.
Note: The specific operation steps may be slightly different due to version difference of
the lower-level system. Please perform the operations according to the messages
displayed in the window.
Expected Results:
1) After the version package is activated, the result information of activating the version
package successfully or not will be given. If the activation fails, the cause of failure
will be given.
Note: This test item may affect the business, so the test requires the consent of the
operator, and is conducted at night when necessary. Restore the version to the old
version after test.
Test Records:
Test Results: □Pass □Not pass
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
User: ZTE Staff:
17.2.5 [ALL] Special Task Management
Test Content: Check that the function of special task management works properly.
Test No.: 15.2.5 Test Object: NetNumen U31 R18
Test Item: SDR Software Version Management Test Sub-item: Special Task Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
Operations steps for creating rollback task
1) Enter the Software Version Management window, and click Special Task
Management in the left tree. The Special Task Management window is displayed.
2) In the displayed window, click New Rollback Task button on the toolbar to open the
New Rollback Task dialog box. Fill in the task name, select NE and board standard,
and click OK.
3) In the displayed confirmation dialog box, enter the verification code and click OK.
4) Right-clicking one or more records in the task list can perform the operations such
as rerun, rerun failed NEs, stop, delete, etc.
Operation steps for creating special firmware pre-activation task:
1) Enter the Software Version Management window, and click Special Task
Management in the left tree. The Special Task Management window is displayed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
2) In the displayed window, click New Special Firmware Pre-activation Task button
on the toolbar to open the New Special Firmware Pre-activation Task dialog box.
Fill in the task name, select NE and board firmware, version package and NE
standard, and click OK.
3) In the displayed confirmation dialog box, enter the verification code and click OK.
4) Right-clicking one or more records in the task list can perform the operations such
as rerun, rerun failed NEs, stop, delete, etc.
Operation steps for creating file storage task:
1) Enter the Software Version Management window, and click Special Task
Management in the left tree. The Special Task Management window is displayed.
2) In the displayed window, click New File Storage Task button on the toolbar to open
the New File Storage Task dialog box. Fill in the task name, select NE and version
package, certificate and board standard, and click OK.
3) In the displayed confirmation dialog box, enter the verification code and click OK.
4) Right-clicking one or more records in the task list can perform the operations such
as rerun, rerun failed NEs, stop, delete, etc.
Operations steps for creating spare part upgrade task:
1) Enter the Software Version Management window, and click Special Task
Management in the left tree. The Special Task Management window is displayed.
2) In the displayed window, click New Spare Part Upgrade Task button on the toolbar
to open the New Spare Part Upgrade Task dialog box. Fill in the task name, select
NE, version package and NE standard, and click OK.
3) In the displayed confirmation dialog box, enter the verification code and click OK.
4) Right-clicking one or more records in the task list can perform the operations such
as rerun, rerun failed NEs, stop, delete, etc.
Expected Results:
1) Each task is executed successfully, and the right-click operations are normal.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
17.3 [GUT] [N] SDR Dynamic Data Management
Test Content: Check that the user can log in to SDR Configuration Management.
Test No.: 15.3 Test Object: NetNumen U31 R18
Test Sub-item: SDR Dynamic Data
Test Item: SDR NE Management
Management
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform configuration management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
Test Procedure:
1) Log in to the client and open the Topology Management view.
2) Select an activated NE Agent node of SDR from the NE topology tree, right-click it
and select NE Management > Dynamic Management from the displayed shortcut
menu.
3) Select the managed NE in the configuration resource tree, select the object to be
queried in the object tree, and click the Query button on the right.
Expected Results:
1) After the query conditions are set, clicking the Query button can display the dynamic
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
data information that meet the set conditions normally.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
18 Software Management
18.1 Version Management
18.1.1 [ALL] Querying a Registered Software Version
Test Content: Check that a software version registered on EMS can be queried.
Test No.: 16.1.1 Test Object: NetNumen U31 R18
Test Sub-item: Querying Registered Software
Test Item: EMS Version Management
Version
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Version
Management to open the Version Management window.
2) In the Version Management window, click the Query Software Version button to
display registered software versions.
Expected Results:
1) All the software versions registered in the version repository will be listed in the
Query Software Version window.
2) If the queried list is empty, it indicates that no software version is registered.
Test Records:
Test Results:□Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
18.1.2 [ALL] Registering a Software Version on EMS
Test Content: Check that a software version can be registered on EMS.
Test No.: 16.1.2 Test Object: NetNumen U31 R18
Test Sub-item: Registering a Software Version
Test Item: EMS Version Management
on EMS
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
3) The target version package that needs to be registered and the description file have
been obtained.
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Version
Management to open the Version Management window.
2) In the Version Management window, click the Register Software Version button.
3) Enter the Register Software Version window.
4) Select the description file of the target version package that needs to be registered.
5) Select Automatically register from Registration method.
6) Select the target version package that needs to be registered.
7) Click OK to automatically register a version.
Expected Results:
1) The target version package is automatically registered successfully.
2) The software version information of the registered target version package will be
displayed in the Query Software Version window.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results:□Pass □Not pass
User: ZTE Staff:
18.2 One-Touch Upgrade
18.2.1 [ALL] Creating a One-Touch Upgrade Task
Test Content: Check that the function of creating a one-touch upgrade task works properly.
Test No.: 16.2.1 Test Object: NetNumen U31 R18
Test Sub-item: Creating a One-Touch Upgrade
Test Item: EMS One-Touch Upgrade
Task
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) The target version package to be upgraded has been registered in Version
Management of EMS.
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Upgrade
Management to open the Upgrade Management window.
2) In the Upgrade Management window, click the New button. The Create Job dialog
box is displayed.
3) In the Create Job window, select the upgrade object type, target version package
and the objects that need to be upgraded.
4) Click Next. The Set parameters dialog box is displayed (For the upgrade of
NODEB, this dialog box will not be displayed. The Set Steps dialog box will be
displayed directly). In this dialog box, fill in the parameters.
5) Click Next. The Set Steps dialog box is displayed. In this dialog box, select the
upgrade steps and corresponding key steps.
6) Click Finish.
Expected Results:
1) The one-touch upgrade task is created successfully.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results:□Pass □Not pass
User: ZTE Staff:
18.2.2 [ALL] Executing a One-Touch Upgrade Task
Test Content: Check that the function of executing a one-touch upgrade task works properly.
Test No.: 16.2.2 Test Object: NetNumen U31 R18
Test Sub-item: Executing a One-Touch
Test Item: EMS One-Touch Upgrade
Upgrade Task
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
3) The connection between the EMS and the NE is properly established, and the NE
Management has been started.
4) In the one-touch upgrade window of EMS, there is already a to-be-started upgrade
task that has been created.
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Upgrade
Management to open the Upgrade Management window.
2) In the Upgrade Management window, select the to-be-started task that has been
created.
3) Click the Start button to start the created task.
4) When the task is executed to key steps, the task stops and is in the state of to-be-
acknowledged.
5) Click the Continue button to let the task continue to be executed.
6) Wait until all the upgrade steps have been executed.
Expected Results:
1) The one-touch upgrade task is normally executed. All the operations are normally
performed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results:□Pass □Not pass
User: ZTE Staff:
18.2.3 [ALL] Alarm/NE Status Collection and Comparison Task
Test Content: Check that the function of alarm/NE status collection and comparison task works
properly.
Test No.: 16.2.3 Test Object: NetNumen U31 R18
Test Sub-item: Alarm/NE Status Collection and
Test Item: EMS One-Touch Upgrade
Comparison Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
3) In the one-touch upgrade window of EMS, there is already a NODB upgrade task
that can be normally executed.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Upgrade
Management to open the Upgrade Management window.
2) In the Upgrade Management window, select the NODEB upgrade task that can be
normally executed.
3) Before performing the upgrade steps, right-click this task and select Create
Collection Task from the context menu.
4) In the displayed dialog box, select both Collect alarm and Collect NE status.
5) Click OK. The collection task is created successfully.
6) After the upgrade steps have been performed, select the Collection and
Comparison Task window.
7) Right-click Alarm task and NE Status task respectively, and select Create
Comparison Task from the context menu.
8) In the Collection and Comparison Task window, the corresponding comparison
tasks are displayed in the comparison task list.
Expected Results:
1) The alarm/NE status collection task is executed successfully. The user can obtain
the collection report by right-clicking the corresponding collection task, and can view
the detailed collection contents through the report.
2) The comparison task of alarm/NE status collection task is executed successfully.
The user can obtain the comparison result report by right-clicking the corresponding
comparison task, and can view the detailed comparison contents through the report.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results:□Pass □Not pass
User: ZTE Staff:
18.2.4 [ALL] KPI Comparison Task
Test Content: Check that the function of KPI comparison task works properly.
Test No.: 16.2.4 Test Object: NetNumen U31 R18
Test Item: EMS One-Touch Upgrade Test Sub-item: KPI Comparison Task
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established, and the
user is authorized to perform software management operations.
3) In the one-touch upgrade window of EMS, there is already a NODB upgrade task
that has been executed.
Test Procedure:
1) On EMS client, select Maintenance > Software Management > Upgrade
Management to open the Upgrade Management window.
2) In the Upgrade Management window, select the NODEB upgrade task that has
been executed.
3) Right-click the NODEB upgrade task that has been executed, and select Create KPI
Comparison Task from the context menu. The Create KPI Comparison Task
dialog box is displayed.
4) In the Create KPI Comparison Task dialog box, fill in the relevant parameters of the
KPI comparison task.
5) Click OK.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Results:
1) The KPI comparison task is created successfully. In the Collection and
Comparison Task window, the corresponding KPI comparison task is displayed in
the comparison task list.
2) The KPI comparison task is executed successfully. The user can obtain the
comparison result report by right-clicking the corresponding comparison task, and
can view the detailed comparison contents through the report.
Test Records:
Test Results:□Pass □Not pass
User: ZTE Staff:
19 System Tool
19.1 Signaling Trace
19.1.1 [ALL] Cell Signaling
Test Content: Check that the function of cell signaling works properly.
Test No.: 17.1.1 Test Object: NetNumen U31 R18
Test Item: System Tool Test Sub-item: Signaling Trace
Input Parameter: none
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established.
3) The cell service is normal.
Test Procedure:
1) On EMS client, click Configuration > NE Management. Select one OMMB NE
agent, right-click and select Start NE Management.
2) After the NE management has been started, right-click and select System Tool.
3) Select LTE/NB-IoT Trace > Ordinary Task > Signaling Trace > Cell Signaling,
right-click and select New Task.
4) Select the trace range, select the observation object, and set the trace parameters,
and then click Finish.
5) Select the created task, right-click and select Synchronize Task.
6) Select the synchronized task, right-click and select View Task Data.
7) Trigger the cell service.
Expected Results:
1) The task is created normally.
2) The task is synchronized normally.
3) The data is reported normally.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results:□Pass □Not pass
User: ZTE Staff:
19.1.2 [ALL] IMSI Signaling
Test Content: Check that the function of IMSI signaling works properly.
Test No.: 17.1.2 Test Object: NetNumen U31 R18
Test Item: System Tool Test Sub-item: Signaling Trace
Input Parameter: none
Prerequisites:
1) The server and the client of EMS are started properly.
2) The connection between the client and the server is properly established.
3) The cell service is normal.
4) The core network is normal.
Test Procedure:
1) On EMS client, click Configuration > NE Management. Select one OMMB NE
agent, right-click and select Start NE Management.
2) After the NE management has been started, right-click and select System Tool.
3) Select LTE/NB-IoT Trace > Ordinary Task > Signaling Trace > IMSI Signaling,
right-click and select New Task.
4) Select the trace range, select the observation object, and set the trace parameters,
and then click Finish.
5) Select the created task, right-click and select Synchronize Task.
6) Select the synchronized task, right-click and select View Task Data.
7) Trigger the UE access to perform the service.
Expected Results:
1) The task is created normally.
2) The task is synchronized normally.
3) The data is reported normally.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Content: Check that the online help is available.
Test No.: 2.1 Test Object: NetNumen U31 R18
Test Item: Online Help Test Sub-item: Online Help
Input Parameter: none
Prerequisites:
3) The server and the client of EMS have been started.
4) The client is connected to the server properly and the Topology Management
function is available.
Test Procedure:
3) Log in to the client and open the Topology Management view.
4) Press F1 or select the help option from the main menu.
Expected Results:
4) The Alarm Monitoring tab can be displayed.
5) The displayed help dialog box is relevant with the current view.
6) If there is no current view, the UEMS profile will be displayed.
Test Records:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Results: □Pass □Not pass
User: ZTE Staff:
Test Results:□Pass □Not pass
User: ZTE Staff:
20 HA Test
20.1 Manual HA Switchover Test
Test Content: Check the switchover function of the HA system.
Test No.: 16.1 Test Object: HA
Test Item: HA Test Test Sub-item: System shutdown and restart
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) HA is normal.
3) The HA client is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
VCS scenario (refer to the corresponding documents for details):
1) The HA client displays that HA is normal.
2) Log in to the master EMS server.
3) Right-click on the NetNumen icon and select “switch to” to switch the HA system.
4) After switching to the slave server, follow Step 3 to switch back to the master server.
5) Log in to the master EMS server.
Skybility scenario (refer to the corresponding documents for details):
1) Use web browser to log in to HA through http:// xxx.xxx.xxx.xxx:8088, in which
“xxx.xxx.xxx.xxx” is the IP of a random server in HA cluster. The default
username/password is admin/admin.
2) Query the status of the services in the Overview interface and make sure it is normal for all
services. EMS server can be visited from the client.
3) Select EMS service in the Overview interface, and click the Start button on the top. Set the
expected target server to the slave node, and click OK. Overview
4) After the switchover ends and EMS is started up, log in to EMS server through the client.
Make sure the login is normal.
5) Switch back to the master node according to Step 3.
6) Log in to EMS server again from the client, and the login is normal.
Expected Result:
1) Manual HA switchover can be performed normally. HA can be switched to the slave server
and back to the master server normally.
2) Before HA is switched over to the slave server, EMS client can connect to the master EMS
server. After HA switchover, EMS client can connect to the slave EMS server.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
20.2 Plugging out an Ethernet Cable Will Not Cause
HA Switchover
Test Content: Check the functions of the HA system when the network is abnormal.
Test No.: 16.2 Test Object: HA
Test Sub-item: Plugging out an Ethernet cable
Test Item: HA Test
will not cause HA switchover
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) HA is normal.
3) The SkybilityHA view can be connected normally from the VCS client or the Web
browser.
4) Configure spare Ethernet cables for the service network.
Test Procedure:
1) Log in to the master EMS server. HA is displayed normally on the HA client.
2) Remove one service Ethernet cable from the blade shelf.
Expected Result:
1) After one Ethernet cable is removed from the blade shelf, HA switchover will not
happen.
2) After one Ethernet cable is removed in the network, the EMS client can connect to
the master EMS server normally.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
20.3 Stopping the EMS Application to Simulate the
Fault
Test Content: Check the switchover function of the HA system in the case of EMS application fault.
Test No.: 16.3 Test Object: HA
Test Item: HA Test Test Sub-item: Application fault
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) HA is normal.
3) The HA client is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
VCS scenario (refer to the corresponding documents for details):
1) The HA client displays that HA is normal.
2) Log in to the main EMS server.
3) Stop the EMS main process with commands, and verify whether the corresponding
EMS process can be restored (EMS can switch to other blades or restart on the
current blade, depending on the HA configuration). If there is local reset
configuration, try to stop the EMS main process for several times (depending on the
configured number of times for HA restart) until the EMS switches to the slave node.
4) After the EMS process starts up, log in to the master EMS server
5) Clear the fault status of the EMS process.
6) Stop the EMS once or several times (depending on the configured number of times
for EMS reboot) on the slave node, and test whether EMS can be switched back to
the master node.
7) After the EMS process starts up, visit the master EMS server.
Skybility scenario (refer to the corresponding documents for details):
1) Use web browser to log in to HA through http:// xxx.xxx.xxx.xxx:8088, in which
“xxx.xxx.xxx.xxx” is the IP of a random server in HA cluster. The default
username/password is admin/admin.
2) Log in to the master EMS server.
3) Stop the EMS main process with commands, and verify whether the corresponding
EMS process can be restored (EMS can switch to other blades or restart on the
current blade, depending on the HA configuration). If there is local reset
configuration, try to stop the EMS main process for several times (depending on the
configured number of times for HA restart) until the EMS switches to the slave node.
4) After the EMS process starts up, log in to the master EMS server
5) Reset the fault status of the EMS process on the master node.
6) Stop the EMS once or several times (depending on the configured number of times
for EMS reboot) on the slave node, and test whether EMS can be switched back to
the master node.
7) After the EMS process starts up, visit the master EMS server.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Result:
1) When there is some EMS process fault (simulated by stopping EMS), HA can ensure
normal EMS operation. Note: This mechanism is used only to make sure EMS
works properly when there is some EMS process fault. It cannot restore the
fault if there is some problem in the EMS application itself or some related file
is damaged.
2) Before the fault simulation, EMS client can access the master EMS server normally.
After the fault happens and the HA switches the EMS running node, EMS client can
access the slave EMS server.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
20.4 Stopping a Blade Server to Simulate the Server
Hardware Fault
Test Content: Check the switchover function of the HA system in the case of EM hardware fault.
Test No.: 16.5 Test Object: HA
Test Item: HA Test Test Sub-item: Application fault
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) HA is normal.
3) The HA client is normal.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Test Procedure:
VCS scenario (refer to the corresponding documents for details):
1) The HA client displays that HA is normal.
2) Log in to the master EMS server.
3) Stop the EMSmain blade through the operating system commands, and verify
whether all the application processes of the corresponding blade can be switched
back to the slave node.
4) After the related process starts up, visit the master EMS server.
5) Start the server and clear all the original fault status.
6) Stop the slave blade, and test whether the application can be switched back to the
master node.
7) After the EMS process starts up, visit the master EMS server.
Skybility scenario (refer to the corresponding documents for details):
1) Use web browser to log in to HA through http:// xxx.xxx.xxx.xxx:8088, in which
“xxx.xxx.xxx.xxx” is the IP of a random server in HA cluster. The default
username/password is admin/admin.
2) Log in to the master EMS server.
3) Stop the EMSmain blade through the operating system commands, and verify
whether all the application processes of the corresponding blade can be switched
back to the slave node.
4) After the related process starts up, visit the master EMS server.
5) Start the server and reset all the original fault status.
6) Stop the slave blade, and test whether the application can be switched back to the
master node.
7) After the EMS process starts up, visit the master EMS server.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Result:
1) When there is some fault on the blade (simulated by stopping the blade), the
application can run properly on the slave node.
2) Before the fault simulation, EMS client can access the master EMS server normally.
After the fault happens and the HA switches the EMS running node, EMS client can
access the slave EMS server.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
20.5 Master/slave Data Synchronization Status Can
Be Displayed in the DR Environment
Test Content: Check whether the master/slave data synchronization status can be viewed in the
DR environment.
Test No.: 16.6 Test Object: HA
Test Sub-item: Data synchronization in the DR
Test Item: HA Test
environment.
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) Both HA and DR are normal.
Test Procedure:
VCS scenario (refer to the corresponding documents for details):
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
1) The HA client displays that HA is normal.
2) Log in to the master EMS server.
3) On the active site of the DR environment, view the dg with the vxdg list command.
4) View the rvg under dg with the vradmin -g dgemscfs1 printrvg command.
5) Check the synchronization status of rvg and confirm the synchronization link name
with the vradmin -g dgemscfs1 -l repstatus rvgemscfs command.
6) Check the real-time synchronization status of the synchronization link with the vxrlink
-g dgemscfs1 -i 2 status emslink1 command.
Skybility scenario:
None
Expected Result:
1) The synchronization status can be viewed.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
20.6 Master-slave Switchover Test in the DR Scenario
Test Content: Check the standby site can take over the service of the active site in the DR
environment.
Test No.: 16.7 Test Object: HA
Test Sub-item: The standby site can take over
Test Item: HA Test the service of the active site in the DR
environment.
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Input Parameter: None
Prerequisites:
1) The EMS system is normal.
2) Both HA and DR run properly.
Test Procedure:
VCS scenario (refer to the corresponding documents for details):
1) The HA client displays that HA is normal.
2) Log in to the master EMS server.
3) Check the synchronization status with commands and make sure the status is up-to-
date.
4) Stop the application services of the active site through the HA GUI or command line
according to the planned sequence and steps.
5) After the services of the active site are stopped, switch the RVG service to the
standby site through commands.
6) After RVG starts up on the standby site, start the application services through GUI or
command line according to the planned sequence and steps.
7) After the services are all started, verify whether all the application related services
are normal.
8) Check the synchronization status and make sure it is up-to-date.
9) Stop the application services of the standby site through the HA GUI or command
line according to the planned sequence and steps.
10) After the services of the standby site are stopped, switch the RVG service to the
active site through commands.
11) After RVG starts up on the active site, start the application services through GUI or
command line according to the planned sequence and steps.
12) After the services are all started, verify whether all the application related services
are normal.
Skybility scenario:
None
GU_NetNumen U31 R18 V12.18 Test Guide_Distributed Internal Use Only▲
Expected Result:
1) The application can run properly on the standby site and the related service are
normal.
2) After the application is switched back to the active site, it can run properly and the
related services are normal.
3) Because the history performance data and the history alarm data are not
synchronized, some history data will be missing in the query result. The missing data
on the standby site is generated by the related application in the period when the
active site is running, while the missing data on the active site is generated by the
related application during the period when the standby site is running.
Test Records:
Test Results: □Pass □Not pass
User: ZTE Staff:
You might also like
- WO - NAST3021 - E01 - 1 ZXPOS CNT Introduction-45No ratings yetWO - NAST3021 - E01 - 1 ZXPOS CNT Introduction-4545 pages
- SJ-20140724091740-001-NetNumen U31 R18 (V12.13.50) Documentation GuideNo ratings yetSJ-20140724091740-001-NetNumen U31 R18 (V12.13.50) Documentation Guide18 pages
- 12 NetNumen U31 R22 (V12.13.10) Product DescriptionNo ratings yet12 NetNumen U31 R22 (V12.13.10) Product Description67 pages
- SJ-20141104150738-001-NetNumen U31 R18 (V12.13.51) Documentation GuideNo ratings yetSJ-20141104150738-001-NetNumen U31 R18 (V12.13.51) Documentation Guide17 pages
- Maintenance Experience Issue160 (Data Products)No ratings yetMaintenance Experience Issue160 (Data Products)32 pages
- Netnumen U31 r18 Unified Element Management System Configuration Application Operastion Guide PDFNo ratings yetNetnumen U31 r18 Unified Element Management System Configuration Application Operastion Guide PDF108 pages
- Farm Management Systems and The Future Internet EraNo ratings yetFarm Management Systems and The Future Internet Era15 pages
- The Definitive Guide To Transforming Your Practice With Online AccountingNo ratings yetThe Definitive Guide To Transforming Your Practice With Online Accounting17 pages
- sjzl20073072-NetNumenN31 Integrated Network Management Troubleshooting - 127424 PDFNo ratings yetsjzl20073072-NetNumenN31 Integrated Network Management Troubleshooting - 127424 PDF21 pages
- SJ-20140403193534-001-NetNumen U31 R06 (V12.14.10) Unified Element Management System Product Description - 573489No ratings yetSJ-20140403193534-001-NetNumen U31 R06 (V12.14.10) Unified Element Management System Product Description - 57348967 pages
- Netnumen™ U31 R50: Unified Element Management SystemNo ratings yetNetnumen™ U31 R50: Unified Element Management System35 pages
- 1-12 ZTE CN EMS - ZTE NetNumen U31 (CN) Product Description0% (1)1-12 ZTE CN EMS - ZTE NetNumen U31 (CN) Product Description70 pages
- SJ-20180108102206-008-NetNumen U31 (ICT) R22 (V12.18.10) Management System Alarm Handling - 806898No ratings yetSJ-20180108102206-008-NetNumen U31 (ICT) R22 (V12.18.10) Management System Alarm Handling - 806898181 pages
- SJ-20180108102206-001-NetNumen U31 (ICT) R22 (V12.18.10) Management System Installation Guide - 806905No ratings yetSJ-20180108102206-001-NetNumen U31 (ICT) R22 (V12.18.10) Management System Installation Guide - 80690549 pages
- NetNumen U31 R22 (V12.16.10) Unified Network Management System Product Description - V1.0100% (2)NetNumen U31 R22 (V12.16.10) Unified Network Management System Product Description - V1.068 pages
- SJ-20160328171815-023-ZXUR 9000 UMTS (V4.15.10.20) Calling Trace Operation GuideNo ratings yetSJ-20160328171815-023-ZXUR 9000 UMTS (V4.15.10.20) Calling Trace Operation Guide74 pages
- Digital Strategies and Organizational Transformation (G Reza Djavanshir, G. Reza DJNo ratings yetDigital Strategies and Organizational Transformation (G Reza Djavanshir, G. Reza DJ338 pages
- 19.IM SM2001 E04 1ZXUNIMSOperationandMaintenance-78No ratings yet19.IM SM2001 E04 1ZXUNIMSOperationandMaintenance-7878 pages
- SJ-20180108102206-002-NetNumen U31 (ICT) R22 (V12.18.10) Management System Operation Guide - 806904No ratings yetSJ-20180108102206-002-NetNumen U31 (ICT) R22 (V12.18.10) Management System Operation Guide - 806904129 pages
- ZTE NetNumen U31 RAN Basic Features Description100% (2)ZTE NetNumen U31 RAN Basic Features Description123 pages
- PCE FUE Health Check_Sanlam Pan Africa Maroc_Customer Number_1328881 (1)No ratings yetPCE FUE Health Check_Sanlam Pan Africa Maroc_Customer Number_1328881 (1)17 pages
- Determinants of Employee Turnover and Its Effect On Organisational Performance - A Case of Airtel Kenya LimitedNo ratings yetDeterminants of Employee Turnover and Its Effect On Organisational Performance - A Case of Airtel Kenya Limited68 pages
- NetNumen U31 R10 (V12.17.30) Security Management - 813166No ratings yetNetNumen U31 R10 (V12.17.30) Security Management - 81316675 pages
- LTE Principle: - UMTS Radio Network Planning & Optimization DeptNo ratings yetLTE Principle: - UMTS Radio Network Planning & Optimization Dept48 pages
- NetNumen U31 R06. Backup and Recovery GuideNo ratings yetNetNumen U31 R06. Backup and Recovery Guide49 pages
- SNOC CM MOP 3G NodeB Rehoming Via TransferSiteTool ZTE v1.0No ratings yetSNOC CM MOP 3G NodeB Rehoming Via TransferSiteTool ZTE v1.025 pages
- ZXUN USPP (V4.13.20) Universal Subscriber Profile Platform Software Installation Guide100% (1)ZXUN USPP (V4.13.20) Universal Subscriber Profile Platform Software Installation Guide177 pages
- 03 Interface Protocol and Signaling Flow 51No ratings yet03 Interface Protocol and Signaling Flow 5150 pages
- NetNumen U31 R18 Unified Element Management System System Management Operation Guide100% (1)NetNumen U31 R18 Unified Element Management System System Management Operation Guide37 pages
- Cloud Computing Characteristics and Services A Brief ReviewNo ratings yetCloud Computing Characteristics and Services A Brief Review7 pages
- SNOC - CM - MOP - GUFTL Removing Insufficient Space On CC Board - ZTE - V1.0No ratings yetSNOC - CM - MOP - GUFTL Removing Insufficient Space On CC Board - ZTE - V1.012 pages
- SJ-20120319104909-013-ZXUR 9000 UMTS (V4.11.20) MML Command ReferenceNo ratings yetSJ-20120319104909-013-ZXUR 9000 UMTS (V4.11.20) MML Command Reference463 pages
- SNOC - CM - MOP - 3G - NODEB - VLAN Change - ZTE - v1.0No ratings yetSNOC - CM - MOP - 3G - NODEB - VLAN Change - ZTE - v1.012 pages
- SNOC - CM - MOP - 2G - BTS - VLAN Change - ZTE - v1.0No ratings yetSNOC - CM - MOP - 2G - BTS - VLAN Change - ZTE - v1.010 pages
- Snoc CM Mop 4g Enodeb Software Upgrade Zte v1.0No ratings yetSnoc CM Mop 4g Enodeb Software Upgrade Zte v1.012 pages
- SNOC - CM - MOP - 4G - eNodeB - VLAN Change - ZTE - v1.0No ratings yetSNOC - CM - MOP - 4G - eNodeB - VLAN Change - ZTE - v1.09 pages
- Customer Service Representative Resume Objective100% (1)Customer Service Representative Resume Objective6 pages
- TO Genex Probe Drive Test Operation: BY Imran Hashmi100% (4)TO Genex Probe Drive Test Operation: BY Imran Hashmi33 pages
- ZTE GU NetNumen M31 (RAN) Product Description100% (3)ZTE GU NetNumen M31 (RAN) Product Description45 pages
- Software Process Improvement: Nizam Farid Ahmed Senior Software Architect, LEADSNo ratings yetSoftware Process Improvement: Nizam Farid Ahmed Senior Software Architect, LEADS12 pages
- MOP For G900 To G1800 Implementation and Site ID ChangeNo ratings yetMOP For G900 To G1800 Implementation and Site ID Change7 pages
- 2-2 ZTE Radio Network EMS - ZTE NetNumen U31 Product Description75% (4)2-2 ZTE Radio Network EMS - ZTE NetNumen U31 Product Description33 pages
- 30 Ways To Make Money Online (Kazybek TolegenNo ratings yet30 Ways To Make Money Online (Kazybek Tolegen43 pages
- NetNumen U31 R10 V12.14.30 Unified Element Management System Product Description 595609100% (1)NetNumen U31 R10 V12.14.30 Unified Element Management System Product Description 59560959 pages
- Zxur 9000 gsmv65020 BSC Commissioning Guide r11 - Compress PDFNo ratings yetZxur 9000 gsmv65020 BSC Commissioning Guide r11 - Compress PDF206 pages
- SJ-20121213161606-007-ZXWR RNC (V3.12.10) OMM Software Installation GuideNo ratings yetSJ-20121213161606-007-ZXWR RNC (V3.12.10) OMM Software Installation Guide51 pages
- 08 NetNumen U31 Alarm Management Operation - 50PNo ratings yet08 NetNumen U31 Alarm Management Operation - 50P50 pages
- Customer Relationship Management: Internship Presentation100% (1)Customer Relationship Management: Internship Presentation18 pages
- NetNumen U31 R22 (V12.15.10) System Configuration Guide - V1.0100% (3)NetNumen U31 R22 (V12.15.10) System Configuration Guide - V1.0190 pages
- ZXSDR OMMB (V12.12.30) Version Management Operation Guide PDFNo ratings yetZXSDR OMMB (V12.12.30) Version Management Operation Guide PDF25 pages
- ZTE V4 RNC Commissioning and Integration TrainingNo ratings yetZTE V4 RNC Commissioning and Integration Training2 pages
- SJ-20100211152857-006-ZXWN MSCS (V3.09.21) MSC Server Data Configuration Guide (MSCS)50% (2)SJ-20100211152857-006-ZXWN MSCS (V3.09.21) MSC Server Data Configuration Guide (MSCS)396 pages
- 10 ZCNA-PTN NetNumen U31 Introduction 114PNo ratings yet10 ZCNA-PTN NetNumen U31 Introduction 114P114 pages
- NetNumen U31 Unified Element Management System Software Installation Guide100% (1)NetNumen U31 Unified Element Management System Software Installation Guide69 pages
- Devops Engineer Interview Questions & Answers: by Sandip DasNo ratings yetDevops Engineer Interview Questions & Answers: by Sandip Das17 pages
- Living in The IT Era - Lesson 3 Activity 3No ratings yetLiving in The IT Era - Lesson 3 Activity 310 pages
- NetNumen (CORBA) Interface Performance IndicesNo ratings yetNetNumen (CORBA) Interface Performance Indices25 pages
- ZTE IEnergy ElasticNet UME System Product DescriptionNo ratings yetZTE IEnergy ElasticNet UME System Product Description13 pages
- G - TM - ZXUR 9000 GSM OMM Commissioning - R1.0No ratings yetG - TM - ZXUR 9000 GSM OMM Commissioning - R1.026 pages
- ZXSDR Upgrade Guide (From OMCB V4.11 To OMMB V12.12.40P29) 20140410No ratings yetZXSDR Upgrade Guide (From OMCB V4.11 To OMMB V12.12.40P29) 2014041066 pages
- Azure Devops - FEST - Course Content - 2No ratings yetAzure Devops - FEST - Course Content - 24 pages
- ZTE Software Release Notes: Version: ZXWR SDR V4.09.21.14P01No ratings yetZTE Software Release Notes: Version: ZXWR SDR V4.09.21.14P0116 pages
- 08 ZXWR RNC Structure and Principle - PPT-52100% (1)08 ZXWR RNC Structure and Principle - PPT-5252 pages
- 002-ElasticNet UME R32 (V16.22.40) Product DescriptionNo ratings yet002-ElasticNet UME R32 (V16.22.40) Product Description41 pages
- 003-ElasticNet UME R32 (V16.22.40) Configuration ManagementNo ratings yet003-ElasticNet UME R32 (V16.22.40) Configuration Management323 pages
- ZTE RNC Alarm and Notification Handling ReferenceNo ratings yetZTE RNC Alarm and Notification Handling Reference183 pages
- ZXSDR BS8700 Base Station Technical Specification - V2.2 PDFNo ratings yetZXSDR BS8700 Base Station Technical Specification - V2.2 PDF22 pages
- 5 LF - SS1007 - E01 - 1 ZXSDR ENodeB Hardware Structure 74pdf100% (1)5 LF - SS1007 - E01 - 1 ZXSDR ENodeB Hardware Structure 74pdf74 pages
