00366248-M2000 Operator Guide (V200R006 - 06)

M2000 V200R006
Operator Guide
Issue Date Part Number
06 2008-12-16 00366248
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
M2000 Operator Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Getting Started............................................................................................................................1-1
1.1 Logging In to the M2000................................................................................................................................1-3 1.1.1 Logging In to theM2000 Server.............................................................................................................1-3 1.1.2 Logging Out the User Account..............................................................................................................1-6 1.1.3 Exiting the M2000 Client.......................................................................................................................1-7 1.1.4 Checking Whether the Client Need Upgrade.........................................................................................1-7 1.1.5 Setting the Interval for Update Checking of M2000 Client...................................................................1-7 1.1.6 Automatically Upgrading the Client Software.......................................................................................1-8 1.2 Changing Password.........................................................................................................................................1-9 1.3 Shortcuts to Client GUI Controls....................................................................................................................1-9 1.4 Customizing Client GUI Style......................................................................................................................1-10 1.4.1 Setting Output Information..................................................................................................................1-11 1.4.2 Setting the Display Effect of Alarm Status in the Topology View......................................................1-12 1.4.3 Setting the Toolbar...............................................................................................................................1-12 1.4.4 Custom Menu.......................................................................................................................................1-13 1.4.5 Customizing Client Time Display Mode.............................................................................................1-14 1.4.6 Customizing the Display Mode of Numbers........................................................................................1-16 1.4.7 Customizing the Mesurement...............................................................................................................1-16 1.4.8 Setting Common Options for Performance Management....................................................................1-17 1.5 Locking Client...............................................................................................................................................1-17 1.5.1 Locking the Client Automatically........................................................................................................1-18 1.5.2 Locking Client Manually.....................................................................................................................1-18 1.6 Unlocking the Client.....................................................................................................................................1-18 1.7 Setting the Running Mode of the System......................................................................................................1-19 1.8 Setting the Alarm Sound When the Network Is Disconnected.....................................................................1-20 1.9 Setting the LMT Proxy..................................................................................................................................1-20 1.10 Setting the LMT Prompt.............................................................................................................................1-21 1.11 Sending Broadcasting Messages.................................................................................................................1-21 1.12 Viewing NM License Information..............................................................................................................1-22 1.13 Viewing NE Partitioning ............................................................................................................................1-22 1.14 Downloading NE Mediation Data to the M2000 Client.............................................................................1-23 1.15 Managing the Exported Files in the Server.................................................................................................1-24 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
1.16 Managing User-Defined Object Groups.....................................................................................................1-24 1.16.1 User-Defined Object Groups..............................................................................................................1-24 1.16.2 Adding a User-Defined Object Group...............................................................................................1-25 1.16.3 Modifying a User-Defined Object Group..........................................................................................1-26 1.16.4 Viewing User-Defined Object Groups...............................................................................................1-27 1.17 Reference for M2000 Client Interfaces.......................................................................................................1-27 1.17.1 Interface Description: M2000 Client Interface..................................................................................1-28 1.17.2 Interface Description: Common Options for Performance Management..........................................1-36 1.17.3 Parameters for Logging In to the M2000 Server................................................................................1-39 1.17.4 Tool Buttons.......................................................................................................................................1-40 1.17.5 Parameters for Output GUI Information............................................................................................1-43 1.17.6 Parameters for Viewing NM License Information.............................................................................1-44 1.17.7 Parameters for Setting the Time Style................................................................................................1-44 1.17.8 Parameters for Setting Common Options for Performance Management..........................................1-45 1.17.9 Parameters for the NE Partitioning Information................................................................................1-47 1.17.10 Parameters for User-Defined Object Groups...................................................................................1-47
2 Network Monitoring................................................................................................................. 2-1

2.1 Basic Knowledge of Monitoring.....................................................................................................................2-3 2.1.1 Alarm Management................................................................................................................................2-3 2.1.2 Alarm Levels..........................................................................................................................................2-5 2.1.3 Alarm Status...........................................................................................................................................2-5 2.1.4 Fault Alarms and Event Alarms.............................................................................................................2-6 2.1.5 Alarm Types...........................................................................................................................................2-8 2.1.6 Alarm Reporting Procedure...................................................................................................................2-9 2.1.7 Alarm Auto-Triggering Script..............................................................................................................2-10 2.2 Monitoring Network Alarms.........................................................................................................................2-10 2.2.1 Setting Columns in an Alarm Interface................................................................................................2-11 2.2.2 Manually Synchronizing NE Alarms...................................................................................................2-12 2.2.3 Locating Alarms...................................................................................................................................2-13 2.2.4 Manually Clearing an Alarm................................................................................................................2-13 2.2.5 Monitoring Alarms Through the Topology View................................................................................2-13 2.2.6 Setting Alarm Real-Time Monitoring..................................................................................................2-14 2.2.7 Querying Alarms..................................................................................................................................2-14 2.2.8 Collecting Alarm Statistics...................................................................................................................2-24 2.2.9 Saving Alarm Data...............................................................................................................................2-26 2.2.10 Printing Alarm Data...........................................................................................................................2-27 2.2.11 Handling Alarms................................................................................................................................2-28 2.2.12 Setting the Displaying Location for a New Alarm.............................................................................2-37 2.3 Setting Alarm Auto Processing.....................................................................................................................2-38 2.3.1 Alarm Auto Processing Policies...........................................................................................................2-38 2.3.2 Setting Alarm Notification...................................................................................................................2-39 2.3.3 Setting Alarm Remote Notification......................................................................................................2-44 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
2.3.4 Setting Alarm Filter Rules....................................................................................................................2-47 2.3.5 Setting Alarm Auto Acknowledgement...............................................................................................2-48 2.3.6 Setting Redefinition of Alarm Level....................................................................................................2-49 2.3.7 Setting Alarm Correlation Rules..........................................................................................................2-50 2.3.8 Managing Auto-Triggering Script Tasks.............................................................................................2-57 2.4 Setting NE Alarms........................................................................................................................................2-62 2.4.1 Shielding an NE Alarm........................................................................................................................2-62 2.4.2 Querying the Shielding of an NE Alarm..............................................................................................2-64 2.4.3 Modifying the Shielding of an NE Alarm............................................................................................2-65 2.4.4 Redefining the Level of an NE Alarm.................................................................................................. -66 2 2.4.5 Querying the Redefinition of an NE Alarm Level...............................................................................2-67 2.4.6 Modifying the Setting of NE Alarm Level Redefinition......................................................................2-68 2.4.7 Defining an NE Alarm.........................................................................................................................2-69 2.4.8 Binding a User-Defined Alarm............................................................................................................2-72 2.5 Monitoring NE Performance in Real Time...................................................................................................2-78 2.5.1 Real-Time Monitoring Performance Counters.....................................................................................2-78 2.5.2 Starting Real-Time Performance Monitoring......................................................................................2-92 2.5.3 Displaying Monitoring Results............................................................................................................2-99 2.5.4 Handling Monitoring Data.................................................................................................................2-104 2.6 Integrated Network Monitoring..................................................................................................................2-107 2.6.1 Basic Knowledge................................................................................................................................2-108 2.6.2 Managing Monitored Object Groups.................................................................................................2-113 2.6.3 Monitoring Object Groups.................................................................................................................2-119 2.6.4 Checking Information of Monitored Objects.....................................................................................2-123 2.6.5 Checking the Status of Monitored Objects........................................................................................2-129 2.6.6 Summarizing Alarms of Monitored Objects......................................................................................2-132 2.7 NM System Monitoring..............................................................................................................................2-140 2.7.1 Setting Monitoring Parameters...........................................................................................................2-140 2.7.2 Monitoring the M2000 Performance Status.......................................................................................2-143 2.7.3 Monitoring the M2000 Hard Disk Status...........................................................................................2-143 2.7.4 Monitoring the M2000 Database Status.............................................................................................2-144 2.7.5 Monitoring the M2000 Service Status...............................................................................................2-144 2.7.6 Monitoring the M2000 Process Status...............................................................................................2-145 2.8 Reference for Network Monitoring Interfaces............................................................................................2-146 2.8.1 Interface Description: Local Terminal Settings.................................................................................2-151 2.8.2 Interface Description: Fault Service Settings.....................................................................................2-153 2.8.3 Interface Description: NE Alarm Settings..........................................................................................2-159 2.8.4 Interface Description: Alarm Browse, Query and Statistics..............................................................2-159 2.8.5 Interface Description: Performance Monitor.....................................................................................2-161 2.8.6 Interface Description: Management of Monitored Object Groups....................................................2-163 2.8.7 Interface Description: RAN Network Monitoring.............................................................................2-164 2.8.8 Interface Description: Monitoring Panel............................................................................................2-165 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
M2000 Operator Guide 2.8.9 Interface Description: System Monitor Browser...............................................................................2-165 2.8.10 Parameters for Setting Columns in an Alarm Interface...................................................................2-167 2.8.11 Parameters for Monitoring Alarms in Real Time.............................................................................2-169 2.8.12 Parameters for Setting Alarm Query/Browse...................................................................................2-170 2.8.13 Parameters for Setting Alarm Statistics...........................................................................................2-175 2.8.14 Parameters for Selecting NE for Query............................................................................................2-179 2.8.15 Parameters for Selecting Alarm Objects..........................................................................................2-180 2.8.16 Parameters for Selecting Alarm Name.............................................................................................2-181 2.8.17 Parameters for the Alarm Explanation and Maintenance Experience..............................................2-182 2.8.18 Parameters for Acknowledging Alarms Automatically...................................................................2-183 2.8.19 Parameters for Setting Alarm Filter Conditions...............................................................................2-184 2.8.20 Parameters for Viewing Alarm Details............................................................................................2-186 2.8.21 Parameters for Querying the Shielding of an NE Alarm..................................................................2-188 2.8.22 Parameters for Shielding an NE Alarm............................................................................................2-189 2.8.23 Parameters for Redefining NMS Alarm Level ................................................................................2-191 2.8.24 Parameters for Redefining/Modifying the Level of an NE Alarm...................................................2-192 2.8.25 Parameters for Alarm Severity Redefinition....................................................................................2-192 2.8.26 Parameters for Querying the Redefinition of an NE Alarm Level...................................................2-193 2.8.27 Parameters for User-Defined Alarms...............................................................................................2-194 2.8.28 Parameters for Querying a User-Defined Alarm..............................................................................2-195 2.8.29 Parameters for Querying the Binding of a User-Defined Alarm .....................................................2-196 2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm......................................2-197 2.8.31 Parameters for Setting the Alarm Box.............................................................................................2-199 2.8.32 Parameters for Setting Alarm Remote Notification Rules...............................................................2-201 2.8.33 Parameters for Setting Notification by Email..................................................................................2-205 2.8.34 Parameters for Advanced Settings of Notification by Email...........................................................2-207 2.8.35 Parameters for Setting Notification by Modem...............................................................................2-207 2.8.36 Parameters for Advanced Settings of Notification by Modem........................................................2-209 2.8.37 Parameters for Setting Notification by SMS Gateway.....................................................................2-209 2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway..............................................2-210 2.8.39 Parameters for Setting Simple Correlation Rules............................................................................2-213 2.8.40 Parameters for Setting Advanced Correlation Rules........................................................................2-214 2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks........................................................2-216 2.8.42 Parameters for Auto-Triggering Conditions....................................................................................2-218 2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script..................................2-219 2.8.44 Parameters for Searching Auto-Triggering Tasks............................................................................2-219 2.8.45 Parameters for Searching Auto-Triggering Records........................................................................2-221 2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter........................................................2-222 2.8.47 Parameters for Setting a Background Color for a Monitoring Chart...............................................2-222 2.8.48 Parameters for Setting Filtering Conditions for a Monitoring Table...............................................2-223 2.8.49 Parameters for Setting Properties for a Monitoring Chart...............................................................2-223 2.8.50 Parameters for Setting Real-Time Monitoring Thresholds..............................................................2-224
iv
Issue 06 (2008-12-16)
Contents
2.8.51 Parameters for Setting Rules for Monitoring Thresholds................................................................2-224 2.8.52 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Chart........................2-225 2.8.53 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Table........................2-225 2.8.54 Parameters for Summarizing Alarms of RNC/NodeB.....................................................................2-226 2.8.55 Parameters for Checking Values of RNC Monitoring Counters......................................................2-228 2.8.56 Parameters for Checking the Information on Basic RNC Configuration.........................................2-229 2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC................................................2-229 2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface.....................2-230 2.8.59 Parameters for Checking the Information on the Iub Interface of the RNC....................................2-230 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface.........................2-231 2.8.61 Parameters for Checking the E1/T1 Status of the RNC...................................................................2-232 2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC...................................2-232 2.8.63 Parameters for Checking the Information on Basic NodeB Configuration......................................2-233 2.8.64 Parameters for Checking the Information on Basic Cell Configuration..........................................2-234 2.8.65 Parameters for Configuration Status................................................................................................2-235 2.8.66 Parameters for Checking the Information on CCH Configuration...................................................2-236 2.8.67 Parameters for Checking the Information on Neighbors..................................................................2-237 2.8.68 Parameters for Checking the Values of Cell Monitoring Counters..................................................2-242 2.8.69 Parameters for Searching for Objects...............................................................................................2-242 2.8.70 Parameters for Setting Thresholds of the M2000 Server.................................................................2-243 2.8.71 Parameters for Monitoring Performance of the M2000 Server........................................................2-245 2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server............................................................2-246 2.8.73 Parameters for Monitoring Database of the M2000 Server.............................................................2-247 2.8.74 Parameters for Monitoring Services of the M2000 Server...............................................................2-248 2.8.75 Parameters for Monitoring Process of the M2000 Server................................................................2-249
3 Topology Management.............................................................................................................3-1
3.1 Basic Knowledge of Topology........................................................................................................................3-3 3.1.1 Topology Management Function...........................................................................................................3-3 3.1.2 Objects in a Topology View...................................................................................................................3-3 3.2 Constructing a Physical Subnet.......................................................................................................................3-4 3.2.1 Designing the Physical Topology..........................................................................................................3-5 3.2.2 Setting the Topology Background..........................................................................................................3-5 3.2.3 Creating a Physical Subnet.....................................................................................................................3-6 3.2.4 Creating Physical NEs............................................................................................................................3-7 3.2.5 Creating a Virtual NE.............................................................................................................................3-7 3.2.6 Creating IP Device.................................................................................................................................3-7 3.2.7 Creating a Physical Link........................................................................................................................3-8 3.2.8 Creating a Virtual Link..........................................................................................................................3-9 3.2.9 Creating Links in Batches....................................................................................................................3-10 3.2.10 Setting an NE as a Transfer Server....................................................................................................3-11 3.3 Creating Physical NEs...................................................................................................................................3-12 3.3.1 NE Type...............................................................................................................................................3-12 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
M2000 Operator Guide 3.3.2 Basic NE information...........................................................................................................................3-19 3.3.3 Creating a Physical NE........................................................................................................................3-21 3.3.4 Creating Multiple Physical NEs...........................................................................................................3-22
3.4 Managing SNMP Parameter Templates........................................................................................................3-31 3.4.1 Creating SNMP Parameter Templates.................................................................................................3-32 3.4.2 Modifying SNMP Parameter Templates..............................................................................................3-32 3.4.3 Deleting SNMP Parameter Templates.................................................................................................3-33 3.5 Monitoring NEs.............................................................................................................................................3-33 3.5.1 Monitoring NE Status...........................................................................................................................3-33 3.5.2 Allowing Reconnection to an NE.........................................................................................................3-34 3.5.3 Manually Reconnecting an NE............................................................................................................3-35 3.6 Adjusting the Network Topology..................................................................................................................3-35 3.6.1 Searching for Topology Objects..........................................................................................................3-36 3.6.2 Adjusting the Position of an NE...........................................................................................................3-37 3.6.3 Moving a NodeB..................................................................................................................................3-41 3.6.4 Viewing/Modifying the Basic Attributes of a Subnet..........................................................................3-45 3.6.5 Viewing/Modifying NE Properties......................................................................................................3-46 3.6.6 Viewing/Modifying a Physical Link....................................................................................................3-47 3.6.7 Viewing/Modifying a Virtual Link......................................................................................................3-48 3.6.8 Deleting Subnets..................................................................................................................................3-48 3.6.9 Deleting a Virtual NE...........................................................................................................................3-49 3.6.10 Deleting Physical NEs in Batches......................................................................................................3-49 3.6.11 Deleting a Physical Link....................................................................................................................3-50 3.6.12 Deleting a Virtual Link......................................................................................................................3-50 3.6.13 Refreshing a Topology View.............................................................................................................3-51 3.7 Adjusting the Topology View.......................................................................................................................3-51 3.7.1 Showing/Hiding the Navigation Tree of a Topology View.................................................................3-52 3.7.2 Setting Alarm Display on the Topology View.....................................................................................3-53 3.7.3 Switching the Current Subnet..............................................................................................................3-53 3.7.4 Display the filtered topology view.......................................................................................................3-54 3.7.5 Zooming In/Out on a Topology View..................................................................................................3-54 3.7.6 View the topology aerial view.............................................................................................................3-55 3.7.7 Laying Out Topology Objects Automatically......................................................................................3-55 3.7.8 Expand or Collapse Child Objects.......................................................................................................3-56 3.7.9 Sorting Topology Objects....................................................................................................................3-56 3.7.10 Displaying the Alarm Pop-Up Pane...................................................................................................3-57 3.7.11 Customizing Topology Tips...............................................................................................................3-57 3.7.12 Setting a Subnet Displayed When the Topology View is Started......................................................3-58 3.7.13 Enabling the E-Map...........................................................................................................................3-58 3.8 Printing a Topology View.............................................................................................................................3-59 3.9 Reference for Topology Management Interfaces..........................................................................................3-59 3.9.1 Interface Description: Topology Management.....................................................................................3-61 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
3.9.2 Interface Description: Moving a NodeB..............................................................................................3-69 3.9.3 Parameters for Setting a Physical Subnet.............................................................................................3-70 3.9.4 Parameters for Creating an IP Device..................................................................................................3-72 3.9.5 Parameters for Physical Link...............................................................................................................3-75 3.9.6 Parameters for Setting a Virtual Link..................................................................................................3-76 3.9.7 Parameters for Setting the Topology View..........................................................................................3-77 3.9.8 Parameters for Exporting an NE Information Template (in .ini Format).............................................3-78 3.9.9 Parameters for Creating an NE.............................................................................................................3-79 3.9.10 Parameters for Batch Creating Physical NEs.....................................................................................3-80 3.9.11 Parameters for Monitoring the Status of an NE.................................................................................3-80 3.9.12 Parameters for Viewing/Modifying the Basic Attributes of a Subnet................................................3-81 3.9.13 Parameters for Setting Topology Filter Display................................................................................3-81 3.9.14 Parameters for Printing a Topology View..........................................................................................3-82 3.9.15 Parameters for SNMP Parameter Templates......................................................................................3-84 3.9.16 Parameters for Moving a NodeB........................................................................................................3-87
4 Security Management................................................................................................................4-1
4.1 Basic Knowledge of Security Management....................................................................................................4-3 4.1.1 Centralized User Management...............................................................................................................4-3 4.1.2 User Authority........................................................................................................................................4-4 4.1.3 NE User..................................................................................................................................................4-5 4.1.4 Introduction to the FTPS........................................................................................................................4-5 4.2 Refreshing the Security Management Interface..............................................................................................4-6 4.3 Configuring the M2000...................................................................................................................................4-6 4.3.1 Setting the M2000 Security Policy.........................................................................................................4-7 4.3.2 Setting Single-User Mode......................................................................................................................4-9 4.3.3 Setting the System ACL.......................................................................................................................4-10 4.3.4 Setting FTPS Parameters......................................................................................................................4-10 4.4 Customizing MML Authority.......................................................................................................................4-11 4.4.1 Customizing an NE Type Command Group........................................................................................4-12 4.4.2 Customizing an NE Command Group.................................................................................................4-13 4.4.3 Setting Authority Rules for NE Types.................................................................................................4-13 4.4.4 Issuing Authority Rules for NE Types.................................................................................................4-14 4.4.5 Synchronizing NE Security Data.........................................................................................................4-16 4.5 Creating OM Users........................................................................................................................................4-16 4.5.1 Process for Creating OM Users............................................................................................................4-17 4.5.2 Creating an OM User Group................................................................................................................4-18 4.5.3 Setting the Managed Domain for an M2000 User Group....................................................................4-19 4.5.4 Assigning Operation Rights to an OM User Group.............................................................................4-19 4.5.5 Assigning Rights of New NEs to an OM User Group.........................................................................4-20 4.5.6 Granting MML Authority to an OM User Group................................................................................4-21 4.5.7 Creating an OM User Account.............................................................................................................4-22 4.5.8 Synchronize OM User Data.................................................................................................................4-23 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
M2000 Operator Guide 4.5.9 Adding an OM User to a User Group..................................................................................................4-23 4.5.10 Assigning Operation Rights to an OM User......................................................................................4-24 4.5.11 Setting the Managed Domain for an OM User..................................................................................4-24 4.5.12 Setting the User ACL.........................................................................................................................4-25 4.5.13 Grant MML Authority to an OM user................................................................................................4-25
4.6 Modifying an OM User.................................................................................................................................4-27 4.6.1 Viewing the Details of an OM User.....................................................................................................4-27 4.6.2 Modifying the Public Authority of an OM User..................................................................................4-28 4.6.3 Modifying the Private Authority of an OM User.................................................................................4-32 4.6.4 Modifying the Information About an OM User ..................................................................................4-36 4.6.5 Resetting the Password of an OM User...............................................................................................4-36 4.7 Deleting an OM User Group.........................................................................................................................4-37 4.8 Deleting an OM User....................................................................................................................................4-37 4.9 Querying Authorization.................................................................................................................................4-38 4.10 Comparing the OM User Rights..................................................................................................................4-38 4.11 Managing NE Users....................................................................................................................................4-38 4.11.1 Creating an NE User..........................................................................................................................4-39 4.11.2 Deleting an NE User..........................................................................................................................4-40 4.11.3 Changing the Password of an NE User..............................................................................................4-41 4.11.4 Associating OM User with NE User..................................................................................................4-42 4.11.5 Disassociating OM User with NE User..............................................................................................4-43 4.12 Monitoring OM Users.................................................................................................................................4-43 4.12.1 User Operation Logs..........................................................................................................................4-44 4.12.2 User Sessions......................................................................................................................................4-44 4.12.3 Monitoring Operation of OM Users on the M2000...........................................................................4-46 4.12.4 Viewing Operation of NE Users........................................................................................................4-47 4.12.5 Setting the Status of Special NE User................................................................................................4-48 4.12.6 Forcing an OM User to Exit from the M2000....................................................................................4-48 4.12.7 Forcing an NE User to Exit from the LMT........................................................................................4-49 4.12.8 Unlocking an OM User......................................................................................................................4-49 4.12.9 Setting OM User Auto-Locking.........................................................................................................4-50 4.13 Reference for Security Management Interfaces..........................................................................................4-50 4.13.1 Interface Description: NM Security Management.............................................................................4-51 4.13.2 Interface Description: NE User Management Interface.....................................................................4-52 4.13.3 Interface Description: NE Login Management Interface...................................................................4-54 4.13.4 Interface Description: MML Authority Information of an OM User.................................................4-55 4.13.5 Interface Description: Authority Rules for NE Type.........................................................................4-55 4.13.6 Interface Description: Viewing Operations of OM Users on the M2000..........................................4-56 4.13.7 Interface Description: Viewing Operations of NE Users...................................................................4-57 4.13.8 Parameters for Adding an OM User Group.......................................................................................4-58 4.13.9 Parameters for the Operation Authority of an OM User or an OM User Group................................4-59 4.13.10 Parameters for the MML Authority to an OM User Group or an OM User....................................4-60 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
4.13.11 Parameters for the Information of an OM User...............................................................................4-61 4.13.12 Parameters for NE User....................................................................................................................4-62 4.13.13 Parameters for Creating an M2000 User Account...........................................................................4-63 4.13.14 Parameters for Customizing an NE Command Group.....................................................................4-66 4.13.15 Parameters for the System Security Policy......................................................................................4-67 4.13.16 Parameters for FTPS Parameter.......................................................................................................4-71
5 Log Management........................................................................................................................5-1
5.1 Basic Knowledge of Log Management...........................................................................................................5-2 5.1.1 Log Types...............................................................................................................................................5-2 5.1.2 Log Templates........................................................................................................................................5-2 5.1.3 Procedure for Reporting NE Logs..........................................................................................................5-3 5.2 Synchronizing NE Logs..................................................................................................................................5-7 5.3 Querying Logs.................................................................................................................................................5-7 5.3.1 Creating a Log Query Template.............................................................................................................5-8 5.3.2 Querying Operation Logs.......................................................................................................................5-8 5.3.3 Querying System Logs...........................................................................................................................5-9 5.3.4 Querying Security Logs.......................................................................................................................5-10 5.3.5 Querying NE Operation Logs..............................................................................................................5-11 5.3.6 Saving Log Query Results....................................................................................................................5-12 5.3.7 Printing Log Query Results..................................................................................................................5-12 5.4 Taking Statistics of Logs...............................................................................................................................5-13 5.4.1 Creating a Log Statistical Template.....................................................................................................5-13 5.4.2 Collecting Statistics on Operation Logs...............................................................................................5-14 5.4.3 Collecting Statistics on System Logs...................................................................................................5-14 5.4.4 Collecting Statistics on Security Logs.................................................................................................5-15 5.4.5 Taking Statistics of an NE Log............................................................................................................5-16 5.5 Managing Log Templates..............................................................................................................................5-17 5.5.1 Creating Log Templates.......................................................................................................................5-17 5.5.2 Modifying Log Template Condition....................................................................................................5-18 5.5.3 Deleting Log Template.........................................................................................................................5-19 5.6 References for Log Management Interfaces.................................................................................................5-20 5.6.1 Interface Description: Log Management..............................................................................................5-21 5.6.2 Parameters for Operation Log Details..................................................................................................5-22 5.6.3 Parameters for System Log Details......................................................................................................5-23 5.6.4 Parameters for Security Log Details....................................................................................................5-23 5.6.5 Parameters for NE Operation Log Information....................................................................................5-24 5.6.6 Parameters for NE Security Log Information......................................................................................5-25 5.6.7 Parameters for Operation Log Statistics...............................................................................................5-26 5.6.8 Parameters for Security Log Statistics.................................................................................................5-28 5.6.9 Parameters for System Log Statistics...................................................................................................5-30 5.6.10 Parameters for Statistics of an NE Operation Log.............................................................................5-31 5.6.11 Parameters for Statistics of an NE Security Log................................................................................5-32 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
M2000 Operator Guide 5.6.12 Parameters for Querying Operation Logs..........................................................................................5-32 5.6.13 Parameters for Querying System Logs...............................................................................................5-34 5.6.14 Parameters for Querying Security Logs.............................................................................................5-35 5.6.15 Parameters for Querying NE Operation Logs....................................................................................5-36 5.6.16 Parameters for Querying NE Security Logs.......................................................................................5-37
6 Performance Management........................................................................................................6-1
6.1 Basic Knowledge of Performance Management.............................................................................................6-3 6.1.1 Performance Measurement Counters.....................................................................................................6-3 6.1.2 Performance Measurement Objects........................................................................................................6-4 6.1.3 Measurement Function Sets and Subsets...............................................................................................6-5 6.1.4 Performance Measurement Periods........................................................................................................6-5 6.1.5 Performance Measurement Results........................................................................................................6-6 6.1.6 Performance Counter Thresholds...........................................................................................................6-6 6.1.7 Performance Measurement States..........................................................................................................6-7 6.1.8 Performance Measurement Procedure....................................................................................................6-7 6.2 Monitoring NE Performances.........................................................................................................................6-9 6.2.1 Setting a Performance Measurement Range for an NE........................................................................6-10 6.2.2 Managing Class 3 Object.....................................................................................................................6-11 6.2.3 Synchronizing NE Measurement Results.............................................................................................6-13 6.2.4 Subscribing to NE Measurement Results.............................................................................................6-14 6.2.5 Querying the Reliability of Measurement Results...............................................................................6-14 6.2.6 Querying Missing Measurement Results.............................................................................................6-15 6.2.7 Checking the Integrity of NE Results .................................................................................................6-16 6.2.8 Managing NE Measurement States......................................................................................................6-18 6.3 Querying Performance Measurement Results...............................................................................................6-19 6.3.1 Querying Results by Templates...........................................................................................................6-20 6.3.2 Querying Results by New Conditions..................................................................................................6-21 6.3.3 Query Results by Busy Hour................................................................................................................6-21 6.3.4 Re-querying Results.............................................................................................................................6-22 6.3.5 Setting Result Query Conditions..........................................................................................................6-23 6.3.6 Displaying Performance Measurement Results...................................................................................6-27 6.3.7 Saving Performance Measurement Results..........................................................................................6-30 6.3.8 Printing Performance Measurement Results........................................................................................6-30 6.3.9 Managing Result Query Templates......................................................................................................6-31 6.4 Managing Measurement Objects...................................................................................................................6-34 6.4.1 Querying Measurement Objects...........................................................................................................6-34 6.4.2 Querying Measurement Counters.........................................................................................................6-35 6.4.3 Importing Measurement Object Data...................................................................................................6-36 6.4.4 Exporting Measurement Object Data...................................................................................................6-36 6.4.5 Importing Setting of Measurement......................................................................................................6-37 6.4.6 Exporting Setting of Measurement......................................................................................................6-37 6.4.7 Modifying Remarks of a Measurement Object....................................................................................6-38 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
6.4.8 Activating/Deactivating a Measurement Task.....................................................................................6-38 6.5 Managing User-Defined Counters................................................................................................................6-39 6.5.1 Adding a User-Defined Counter..........................................................................................................6-40 6.5.2 Modifying a User-Defined Counter.....................................................................................................6-41 6.5.3 Importing a User-Defined Counter......................................................................................................6-42 6.5.4 Exporting a User-Defined Counter......................................................................................................6-42 6.6 Managing Counter Thresholds......................................................................................................................6-43 6.6.1 Setting a Simple Counter Threshold....................................................................................................6-44 6.6.2 Setting a Combined Counter Threshold...............................................................................................6-45 6.6.3 Modifying a Counter Threshold...........................................................................................................6-46 6.6.4 Modifying a Combined Counter Threshold.........................................................................................6-47 6.6.5 Activating/Deactivating a Counter Threshold......................................................................................6-47 6.7 Reference for Performance Management Interfaces.....................................................................................6-48 6.7.1 Interface Description: Query Result.....................................................................................................6-49 6.7.2 Interface Description: Measure Management......................................................................................6-50 6.7.3 Interface Description: Threshold Management....................................................................................6-52 6.7.4 Interface Description: User-defined Counter Management.................................................................6-53 6.7.5 Parameters for Adding/Modifying a User-Defined Counter................................................................6-54 6.7.6 Parameters for Setting the Conditions for Filtering Result .................................................................6-54 6.7.7 Parameters for Querying Missing Measurement Results.....................................................................6-55 6.7.8 Parameters for Querying the Reliability of Measurement Results.......................................................6-55 6.7.9 Parameters for Setting the Mode of Sorting Displayed Results...........................................................6-56 6.7.10 Parameters for Setting a Background Color for a Measurement Results Chart.................................6-56 6.7.11 Parameters for Synchronizing NE Measurement Results..................................................................6-56 6.7.12 Parameters for Setting a Simple Counter Threshold..........................................................................6-57 6.7.13 Parameters for Setting a Combined Counter Threshold.....................................................................6-59 6.7.14 Parameters for Setting Threshold Alarm Triggering or Restoration..................................................6-61 6.7.15 Parameters for Specifying the Time Range of Results.......................................................................6-61 6.7.16 Parameters for Measurement States of Measurement Objects and Counters.....................................6-62
7 Performance Report Management..........................................................................................7-1

7.1 Basic Knowledge of Performance Report Management.................................................................................7-3 7.2 Managing Performance Reports......................................................................................................................7-3 7.2.1 Generating a Performance Report..........................................................................................................7-4 7.2.2 Setting a Template for Querying Performance Reports.........................................................................7-5 7.2.3 Filtering the Contents of a Performance Report.....................................................................................7-6 7.2.4 Setting the Display of a Performance Report Based on Conditions...................................................... 7-8 7.2.5 Displaying a Performance Report in a Sequence Chart.........................................................................7-9 7.2.6 Displaying a Performance Report in a Comparison Chart...................................................................7-10 7.2.7 Setting a Related Report.......................................................................................................................7-12 7.2.8 Viewing the Attributes of a Performance Report Template.................................................................7-13 7.2.9 Saving a Performance Report...............................................................................................................7-13 7.2.10 Printing a Performance Report...........................................................................................................7-14 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
M2000 Operator Guide 7.2.11 Managing a Custom Performance Report Template..........................................................................7-15
7.3 Managing KPIs..............................................................................................................................................7-20 7.3.1 Viewing KPIs.......................................................................................................................................7-21 7.3.2 Filtering KPIs.......................................................................................................................................7-21 7.3.3 Setting the Display of a KPI Based on Conditions..............................................................................7-22 7.3.4 Managing Custom KPIs.......................................................................................................................7-23 7.4 MSC Server Performance Reports................................................................................................................7-26 7.4.1 MSC Basic Service Report...................................................................................................................7-26 7.4.2 Mobility Management Report..............................................................................................................7-29 7.4.3 CPU Load Report.................................................................................................................................7-30 7.4.4 Office Direction Traffic Report............................................................................................................7-31 7.4.5 Trunk Group Report.............................................................................................................................7-32 7.4.6 Signaling Link Report..........................................................................................................................7-33 7.5 MSC POOL Report Group............................................................................................................................7-39 7.5.1 Global Traffic of a Pool Report............................................................................................................7-40 7.5.2 Local Traffic of a Pool Report.............................................................................................................7-41 7.5.3 Incoming Traffic of a Pool Report.......................................................................................................7-42 7.5.4 PoolOutTerCall Report........................................................................................................................7-42 7.5.5 MobileOfficeInTfc Report...................................................................................................................7-43 7.5.6 MobileOfficeOutTfc Report.................................................................................................................7-44 7.5.7 VLRSubscriber Report.........................................................................................................................7-45 7.5.8 MeasurementForSMS Report...............................................................................................................7-45 7.5.9 MeasurementForMTC Report..............................................................................................................7-46 7.5.10 MeasurementForLOCUp Report........................................................................................................7-47 7.5.11 Pool Cell Handover Report................................................................................................................7-48 7.5.12 Traffic Measurement For LAI Report................................................................................................7-49 7.5.13 GSM Call Drop Report......................................................................................................................7-50 7.5.14 UMTS Call Drop Report....................................................................................................................7-51 7.5.15 Traffic Measurement of BSCOFI Assignment Report.......................................................................7-52 7.5.16 Traffic Measurement of RNCOFI Assignment Report......................................................................7-52 7.6 MSCe Pool Report Group.............................................................................................................................7-53 7.6.1 Global Traffic of a Pool Report............................................................................................................7-54 7.6.2 Local Traffic of a Pool Report.............................................................................................................7-55 7.6.3 Pool Incoming Traffic Report..............................................................................................................7-56 7.6.4 Pool Outgoing Traffic Report..............................................................................................................7-57 7.6.5 VLR Subscriber Report........................................................................................................................7-57 7.6.6 Pool Cell Handover Report..................................................................................................................7-58 7.6.7 LAI Traffic Measurement Report.........................................................................................................7-59 7.6.8 SMS Measurement Report...................................................................................................................7-60 7.6.9 Paging Measurement Report................................................................................................................7-60 7.6.10 Location Update Measurement Report...............................................................................................7-61 7.6.11 Assignment Measurement Report......................................................................................................7-62 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
7.7 RNC Performance Reports............................................................................................................................7-62 7.7.1 RNC Reports........................................................................................................................................7-63 7.7.2 Cell Reports..........................................................................................................................................7-68 7.7.3 Troubleshooting Reports......................................................................................................................7-74 7.8 PCU Performance Reports............................................................................................................................7-79 7.8.1 Data Throughput Report.......................................................................................................................7-79 7.8.2 Transmission Report............................................................................................................................7-81 7.8.3 Accessibility Report.............................................................................................................................7-82 7.8.4 Availability Report...............................................................................................................................7-83 7.8.5 Retainability Report.............................................................................................................................7-84 7.9 Reference for Performance Report Management Interfaces.........................................................................7-85 7.9.1 Interface Description: KPI List............................................................................................................7-85 7.9.2 Parameters for Setting Conditions for Querying Performance Reports...............................................7-86 7.9.3 Parameters for Setting Filter Conditions for Performance Reports.....................................................7-91 7.9.4 Parameters for Setting the Condition Display of the KPIs...................................................................7-92 7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance Reports........7-93 7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports.....................................................................................................................................7-94 7.9.7 Parameters for Creating or Modifying a Custom Performance Report Template................................7-94 7.9.8 Parameters for Creating or Modifying a Sub-Report...........................................................................7-95 7.9.9 Parameters for KPIs.............................................................................................................................7-95
8 Software Management..............................................................................................................8-1
8.1 Basic Knowledge of Software Management...................................................................................................8-2 8.1.1 NE Software...........................................................................................................................................8-2 8.1.2 Software Patch........................................................................................................................................8-2 8.1.3 Patch States............................................................................................................................................8-3 8.1.4 Software Management File Types..........................................................................................................8-4 8.1.5 RAN License..........................................................................................................................................8-6 8.1.6 Software Management Procedure..........................................................................................................8-7 8.2 Managing Software and Files..........................................................................................................................8-8 8.2.1 Viewing File Information on the Server................................................................................................8-9 8.2.2 Viewing File Information on an NE.......................................................................................................8-9 8.2.3 Transferring Files from the Server to the Client....................................................................................8-9 8.2.4 Transferring Files from the Server to an NE........................................................................................8-10 8.2.5 Transferring Files from the Client to the Server..................................................................................8-11 8.2.6 Transferring Files from an NE to the Server........................................................................................8-12 8.2.7 Managing Task List..............................................................................................................................8-13 8.2.8 Setting Parameters of File Transferring...............................................................................................8-15 8.2.9 Managing Voice Files..........................................................................................................................8-15 8.3 Upgrading NE Software and Patches............................................................................................................8-19 8.3.1 Managing a Scheduled Upgrade..........................................................................................................8-20 8.3.2 Upgrading the RNC Software and Patch..............................................................................................8-23 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
M2000 Operator Guide 8.3.3 Upgrading the SGSN Software and Patch............................................................................................8-28 8.3.4 Upgrading the GGSN Software and Patch...........................................................................................8-35 8.3.5 Upgrading the MSC Server Software Patch.........................................................................................8-41 8.3.6 Upgrading the MGW Software and Patch............................................................................................8-45 8.3.7 Upgrading the AG Software and Patch................................................................................................8-46 8.3.8 Upgrading the ICS Software................................................................................................................8-52 8.3.9 Upgrading NodeB NE Software and Patch..........................................................................................8-53 8.3.10 Upgrading the BSC Software and Patch............................................................................................8-55 8.3.11 Upgrading the BTS Software.............................................................................................................8-61 8.3.12 Upgrading the ASN-GW Software and Patch....................................................................................8-65 8.3.13 Monitoring the Procedure of Software Upgrade................................................................................8-71
8.4 Managing NE Licenses................................................................................................................................. 8-71 8.4.1 Managing RAN Licenses.....................................................................................................................8-72 8.4.2 Managing Licenses Between NEs........................................................................................................8-79 8.5 Querying Version Information on Software Installed on the Server.............................................................8-91 8.6 Reference for Software Management Interfaces...........................................................................................8-93 8.6.1 Interface Description: Software Browser.............................................................................................8-93 8.6.2 Interface Description: NE Licenses Management................................................................................8-95 8.6.3 Parameters for RNC Patch................................................................................................................... 8-99 8.6.4 Parameters for Other NE Software and Patch....................................................................................8-100 8.6.5 Parameters for NE Data......................................................................................................................8-101 8.6.6 Parameters for Upgrading the NodeB Software.................................................................................8-103 8.6.7 Parameters for License Information of NodeBs Controlled by an RNC............................................8-104 8.6.8 Parameters for Setting Parameters of Files Transferring...................................................................8-106 8.6.9 Parameters for the Operator...............................................................................................................8-106 8.6.10 Parameters for Adding/Modifying License Sharing Groups............................................................8-109 8.6.11 Parameters for Version Information on Software Installed..............................................................8-110
9 Configuration Management.....................................................................................................9-1
9.1 Basic Knowledge of Configuration Management...........................................................................................9-3 9.1.1 Management Information Tree (MIT)....................................................................................................9-3 9.1.2 MML command......................................................................................................................................9-3 9.1.3 NE Resource States................................................................................................................................9-4 9.1.4 CBSS Device Panel................................................................................................................................9-5 9.2 Configuring NEs by MML Commands...........................................................................................................9-8 9.2.1 Executing an MML Command...............................................................................................................9-9 9.2.2 Viewing the Result of an MML Command............................................................................................9-9 9.2.3 Viewing Follow-Up Reports................................................................................................................9-10 9.2.4 Setting the Attributes of the "MML Command" Interface...................................................................9-11 9.2.5 Setting Report Redirection...................................................................................................................9-11 9.2.6 Setting Report Scroll Display...............................................................................................................9-12 9.2.7 Clearing History Commands................................................................................................................9-12 9.2.8 Saving the Result of an MML Command............................................................................................ 9-12 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
9.3 Viewing NE Configuration Information.......................................................................................................9-13 9.3.1 Viewing NE MIT Information.............................................................................................................9-14 9.3.2 Viewing NE Resource Reports............................................................................................................9-15 9.3.3 Viewing NE Link Reports....................................................................................................................9-15 9.3.4 Viewing NE Statistics Reports.............................................................................................................9-16 9.3.5 Viewing NE Reports............................................................................................................................9-16 9.4 Handling NE Configuration Data..................................................................................................................9-16 9.4.1 Manually Synchronizing NE Configuration Data................................................................................9-17 9.4.2 Manually Exporting NE Configuration Data.......................................................................................9-19 9.4.3 Importing the Configuration Files of PCU...........................................................................................9-19 9.4.4 Exporting the Configuration Files of PCU...........................................................................................9-20 9.5 Managing Inventory Data..............................................................................................................................9-20 9.5.1 Adding Inventory Data.........................................................................................................................9-21 9.5.2 Querying Inventory Data......................................................................................................................9-22 9.5.3 Importing Inventory Data.....................................................................................................................9-23 9.5.4 Modifying Inventory Data....................................................................................................................9-24 9.5.5 Manually Synchronizing Inventory Data.............................................................................................9-24 9.5.6 Manually Exporting Inventory Data....................................................................................................9-25 9.6 Viewing NE Resource Information...............................................................................................................9-25 9.6.1 Viewing NE Resource States...............................................................................................................9-26 9.6.2 Monitoring NE Resource States in Real Time.....................................................................................9-27 9.7 Starting the CME...........................................................................................................................................9-28 9.8 Starting the LMT of an NE...........................................................................................................................9-29 9.9 Starting the Telnet.........................................................................................................................................9-29 9.10 Operating CBSS Device..............................................................................................................................9-30 9.10.1 Operating CBSS Board......................................................................................................................9-30 9.10.2 Maintaining CBSC.............................................................................................................................9-36 9.10.3 Maintaining CBTS.............................................................................................................................9-58 9.11 Reference for Configuration Management Interfaces.................................................................................9-69 9.11.1 Interface Description: MML Command.............................................................................................9-71 9.11.2 Interface Description: Follow-Up Reports Browser..........................................................................9-72 9.11.3 Interface Description: MIT Browsing................................................................................................9-72 9.11.4 Interface Description: Inventory Management...................................................................................9-74 9.11.5 Interface Description: Device Panel...................................................................................................9-75 9.11.6 Parameters for Monitoring NE Resource States in Real Time...........................................................9-76 9.11.7 Parameters for Setting the Attributes of the MML Command Interface............................................9-76 9.11.8 Parameters for NE MIT Information..................................................................................................9-78 9.11.9 Parameters for NE Resource Report..................................................................................................9-79 9.11.10 Parameters for NE Statistics Report.................................................................................................9-79 9.11.11 Parameters for Querying Inventory Data.........................................................................................9-79 9.11.12 Parameters for Querying the Board Information..............................................................................9-82 9.11.13 Parameters for Querying the Subsystem Status...............................................................................9-83 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
M2000 Operator Guide 9.11.14 Parameters for Querying the Clock Status.......................................................................................9-84 9.11.15 Parameters for Querying the A2 Circuit Status................................................................................9-86 9.11.16 Parameters for Querying the PCF Buffer Usage..............................................................................9-86 9.11.17 Parameters for Querying the DSP Information................................................................................9-87 9.11.18 Parameters for Querying the EVC Timeslot Occupancy................................................................. 9-87 9.11.19 Parameters for Querying the L Interface Channel............................................................................9-88 9.11.20 Parameters for Downloading the BTS Software or Data.................................................................9-88 9.11.21 Parameters for Blocking the BTS CPM Board................................................................................ 9-89 9.11.22 Parameters for Querying the BTS Ethernet IP.................................................................................9-90 9.11.23 Parameters for Querying the FE Port Information...........................................................................9-90
10 Data Management..................................................................................................................10-1
10.1 Basic Knowledge of Data Management......................................................................................................10-3 10.1.1 NM Backup Data................................................................................................................................10-3 10.1.2 NE Backup Data.................................................................................................................................10-4 10.1.3 NM Log Data..................................................................................................................................... 10-4 10.2 NE Backup Data..........................................................................................................................................10-5 10.2.1 Manual NE Backup Data....................................................................................................................10-5 10.2.2 Viewing NE Backup File................................................................................................................... 10-6 10.2.3 Restoring NE Data............................................................................................................................. 10-6 10.3 NM Backup Data.........................................................................................................................................10-7 10.3.1 Manual Backup of M2000 Data.........................................................................................................10-7 10.3.2 Viewing NM Backup File..................................................................................................................10-8 10.4 Collecting Network Optimization Data.......................................................................................................10-9 10.4.1 Collecting Neighbor Cell Optimization Data.....................................................................................10-9 10.4.2 Collecting the Uplink ARFCN Data................................................................................................10-13 10.5 Collecting NM Log File............................................................................................................................10-15 10.6 Reference for Data Management Interfaces..............................................................................................10-16 10.6.1 Interface Description: Backup Management....................................................................................10-17 10.6.2 Interface Description: Log Information Collector............................................................................10-17 10.6.3 Parameters for Collecting NM Logs Parameters..............................................................................10-18 10.6.4 Parameter Description of the Fields in the Backup and Restore Task List......................................10-20 10.6.5 Parameters for NE Backup File........................................................................................................10-21 10.6.6 Parameters for NM Backup File.......................................................................................................10-21 10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization.......................10-22 10.6.8 Parameters for Creating a Task of Collecting the Uplink ARFCN Data.........................................10-24
11 Dual-Homing and LN Domain Management...................................................................11-1

11.1 Basic Knowledge.........................................................................................................................................11-2 11.1.1 Dual-Homing......................................................................................................................................11-2 11.1.2 Local Network Domain......................................................................................................................11-3 11.2 Managing the Dual-Homing........................................................................................................................11-4 11.2.1 Checking the Dual-Homing Information........................................................................................... 11-5 11.2.2 Checking the Dual-Homing Data.......................................................................................................11-5 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
11.2.3 Setting the Attributes for Data Check Interface.................................................................................11-6 11.2.4 Saving the Audit Result of Dual-Homing Data.................................................................................11-7 11.2.5 Generating the Script for Adjusting Difference Data.........................................................................11-8 11.2.6 Delivering the MML Command.........................................................................................................11-9 11.2.7 Synchronizing the Dual-Homing Data.............................................................................................11-10 11.3 Managing the Local Network Domain......................................................................................................11-11 11.3.1 Creating a Local Network Domain..................................................................................................11-12 11.3.2 Managing Local Network Resources...............................................................................................11-12 11.3.3 Managing Users in the Local Network Domain...............................................................................11-12 11.3.4 Managing NEs in the Local Network Domain.................................................................................11-13 11.3.5 Modifying the Name of Local Network Domain.............................................................................11-14 11.3.6 Synchronizing the Information of Local NE Domain......................................................................11-14 11.3.7 Deleting Local Network Domain.....................................................................................................11-15 11.3.8 Instances of Area-Based Privilege Configuration............................................................................11-16 11.4 Reference for Management of Dual-Homing and Local Network Domain Interfaces.............................11-16 11.4.1 Interface Description: Managing the Dual-Homing.........................................................................11-17 11.4.2 Interface Description: Checking the Dual-Homing Data.................................................................11-18 11.4.3 Interface Description: Managing the Local Network Element Domain...........................................11-19
12 MSC Pool Management........................................................................................................12-1

12.1 Basic Knowledge of MSC Pool..................................................................................................................12-3 12.1.1 Basic Scheme of MSC Pool...............................................................................................................12-3 12.1.2 Load balance scheme of MSC Pool...................................................................................................12-5 12.1.3 Transfer Scheme of MSC Pool Users................................................................................................12-7 12.1.4 MSC Pool Networking Application.................................................................................................12-10 12.1.5 User Authority Management of the MSC Pool................................................................................12-11 12.2 Creating MSC Pool Topology on the M2000...........................................................................................12-13 12.3 Initial Configuration of MSC Pool............................................................................................................12-15 12.3.1 Setting an Alarm for MSC Pool Load Imbalance............................................................................12-15 12.3.2 Creating the Task of Auto-Checking MSC Pool..............................................................................12-16 12.3.3 Setting the Attributes of MSC Pool..................................................................................................12-18 12.4 Routine Maintenance of MSC Pool..........................................................................................................12-36 12.4.1 Viewing the Alarms of MSC Pool...................................................................................................12-37 12.4.2 Monitoring the Load of MSC Pool in Real Time.............................................................................12-40 12.4.3 Viewing the Operation Logs of MSC Pool......................................................................................12-42 12.4.4 Viewing the MSC Where a Specific User Is Located......................................................................12-43 12.4.5 Viewing the Relation Between the MGW and the RAN..................................................................12-44 12.4.6 Viewing the Proxy Relation Between the MGW and the RAN.......................................................12-44 12.4.7 Displaying MSC Pool Topology......................................................................................................12-45 12.4.8 Managing the Task of Auto-Checking MSC Pool...........................................................................12-45 12.4.9 Viewing the MSC Pool Performance Report...................................................................................12-47 12.5 MSC Pool Network Maintenance.............................................................................................................12-48 12.5.1 Balancing MSC Pool Load...............................................................................................................12-48 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
M2000 Operator Guide 12.5.2 Checking MSC Pool Data................................................................................................................12-54
12.6 Management Interface of MSC Pool.........................................................................................................12-60 12.6.1 Interface Description: Main Interface of Pool OM..........................................................................12-62 12.6.2 Interface Description: Viewing MSC Pool Alarms..........................................................................12-65 12.6.3 Interface Description: MSC Pool Configuration..............................................................................12-66 12.6.4 Parameters for Creating/Modifying MSC Pool................................................................................12-68 12.6.5 Parameters for Browsing MSC Pool Basic Information..................................................................12-69 12.6.6 Parameters for Viewing the Connection Between MGW and RAN................................................12-70 12.6.7 Parameters for Transferring MSC Pool Users Manually.................................................................12-70 12.6.8 Parameters for Specifying User Numbers to Be Transferred...........................................................12-73 12.6.9 Parameters for Setting the Auto-Check of MSC Pool......................................................................12-74 12.6.10 Parameters for Setting CN ID of an MSC Server..........................................................................12-75 12.6.11 Parameters for Setting NRI of an MSC Pool.................................................................................12-76 12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool........................................................12-77 12.6.13 Parameters for Setting Load-Balancing of an MSC Pool..............................................................12-77 12.6.14 Parameters for Setting NE State of MSC Pool...............................................................................12-79 12.6.15 Parameters for Superior Settings....................................................................................................12-80 12.6.16 Parameters for Setting Load Unbalance Alarm..............................................................................12-81
13 CDMA Pool Management....................................................................................................13-1

13.1 Basic Knowledge of CDMA Pool...............................................................................................................13-3 13.1.1 Basic Scheme of CDMA Pool............................................................................................................13-3 13.1.2 Load Balancing Scheme of CDMA Pool...........................................................................................13-5 13.1.3 Transfer Scheme of CDMA Pool Users.............................................................................................13-6 13.1.4 CDMA Pool Networking Application................................................................................................13-6 13.1.5 User Authority Management of the CDMA Pool..............................................................................13-7 13.2 Creating CDMA Pool..................................................................................................................................13-9 13.3 Initial Configuration of CDMA Pool........................................................................................................13-11 13.3.1 Setting an Alarm for CDMA Pool Load Imbalance.........................................................................13-11 13.3.2 Creating the Task of Auto-Checking CDMA Pool..........................................................................13-12 13.3.3 Setting the Parameters of CDMA Pool............................................................................................13-14 13.4 Commissioning the CDMA Pool Network...............................................................................................13-20 13.5 Routine Maintenance of CDMA Pool.......................................................................................................13-20 13.5.1 Viewing the Alarms of CDMA Pool................................................................................................13-21 13.5.2 Monitoring the Load of CDMA Pool in Real Time.........................................................................13-24 13.5.3 Viewing the Operation Logs of CDMA Pool...................................................................................13-27 13.5.4 Viewing the MSCe Where a Specific User Is Located....................................................................13-27 13.5.5 Displaying CDMA Pool Topology..................................................................................................13-29 13.5.6 Managing the Task of Auto-Checking CDMA Pool........................................................................13-29 13.5.7 Viewing the CDMA Pool Performance Report................................................................................13-31 13.6 CDMA Pool Network Maintenance..........................................................................................................13-32 13.6.1 Balancing CDMA Pool Load...........................................................................................................13-32 13.6.2 Checking CDMA Pool Data.............................................................................................................13-36 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
13.7 Management Interface of CDMA Pool.....................................................................................................13-42 13.7.1 Interface Description: Main Interface of Pool OM..........................................................................13-43 13.7.2 Interface Description: Viewing CDMA Pool Alarms......................................................................13-47 13.7.3 Interface Description: CDMA Pool Configuration..........................................................................13-48 13.7.4 Parameters for Creating/Modifying CDMA Pool............................................................................13-49 13.7.5 Parameters for Browsing the Basic Information About the CDMA Pool........................................13-50 13.7.6 Parameters for Setting the Auto-Check of CDMA Pool..................................................................13-51 13.7.7 Parameters for Setting MSCe Server ID of CDMA Pool.................................................................13-52 13.7.8 Parameters for Setting Load Balancing of CDMA Pool..................................................................13-53 13.7.9 Parameters for Setting NE State of CDMA Pool.............................................................................13-54 13.7.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool....................................................13-55
14 Integrated Task Management..............................................................................................14-1

14.1 Basic Knowledge.........................................................................................................................................14-3 14.1.1 Types of Integrated Tasks..................................................................................................................14-3 14.1.2 System Timing Tasks.........................................................................................................................14-7 14.1.3 User Timing Tasks.............................................................................................................................14-9 14.1.4 Task Scheduling Parameters............................................................................................................14-10 14.1.5 States of a Scheduled Task...............................................................................................................14-11 14.1.6 Customizing the Interface for Managing Timing Tasks..................................................................14-12 14.2 Creating Timing Tasks for Users..............................................................................................................14-13 14.2.1 Creating MML Command Script.....................................................................................................14-14 14.2.2 Creating Software Download...........................................................................................................14-16 14.2.3 Creating NE Backup.........................................................................................................................14-17 14.2.4 Creating CME Upload......................................................................................................................14-18 14.2.5 Creating CME Download.................................................................................................................14-19 14.2.6 Creating HSL Script.........................................................................................................................14-20 14.2.7 Creating Dual-Home Management..................................................................................................14-22 14.2.8 Copying User Timing.......................................................................................................................14-24 14.3 Modifying Timing Tasks for Users...........................................................................................................14-24 14.3.1 Modifying MML Command Script..................................................................................................14-25 14.3.2 Modifying Software Download........................................................................................................14-26 14.3.3 Modifying NE Backup.....................................................................................................................14-27 14.3.4 Modifying CME Upload..................................................................................................................14-28 14.3.5 Modifying CME Download.............................................................................................................14-28 14.3.6 Modifying HSL Script......................................................................................................................14-29 14.3.7 Modifying Dual-Home Management...............................................................................................14-30 14.4 Modifying Data Synchronization..............................................................................................................14-31 14.4.1 Modifying NE Alarm Synchronization............................................................................................14-32 14.4.2 Modifying the Synchronization of NE Configuration Data.............................................................14-33 14.4.3 Modifying the Synchronization of NE Log......................................................................................14-34 14.4.4 Modifying the Synchronization of Inventory Data..........................................................................14-34 14.5 Modifying Database Capacity...................................................................................................................14-35 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
M2000 Operator Guide 14.5.1 Modifying the Capacity of Operation Log Database.......................................................................14-36 14.5.2 Modifying the Capacity of System Log Database...........................................................................14-37 14.5.3 Modifying the Capacity of Security Log Database..........................................................................14-37 14.5.4 Modifying the Capacity of NE Operation Log Database.................................................................14-38 14.5.5 Modifying the Capacity of NE Security Log Database....................................................................14-39 14.5.6 Modifying the Capacity of Alarm Database.....................................................................................14-40 14.5.7 Modifying the Capacity of Performance Database..........................................................................14-41
14.6 Modifying Data Export.............................................................................................................................14-41 14.6.1 Modifying the Export of Performance Data.....................................................................................14-43 14.6.2 Modifying the Export of Alarm Data...............................................................................................14-44 14.6.3 Modifying the Export of Configuration Data...................................................................................14-45 14.6.4 Modifying the Export of Operation Log..........................................................................................14-46 14.6.5 Modifying the Export of System Log..............................................................................................14-47 14.6.6 Modifying the Export of Security Log.............................................................................................14-48 14.6.7 Modifying the Export of NE Operation Log....................................................................................14-49 14.6.8 Modifying the Export of NE Security Log.......................................................................................14-49 14.6.9 Modifying the Export of Inventory Data..........................................................................................14-50 14.6.10 Modifying the Export of Basic NE Information............................................................................14-51 14.7 Modifying Data Backup in the M2000.....................................................................................................14-52 14.8 Modifying Alarm Timing Acknowledgement...........................................................................................14-53 14.9 Modifying NE License Sharing Management...........................................................................................14-54 14.10 Managing Timing Tasks..........................................................................................................................14-55 14.10.1 Deleting Timing Tasks...................................................................................................................14-56 14.10.2 Suspending Timing Tasks..............................................................................................................14-56 14.10.3 Resuming Timing Tasks.................................................................................................................14-57 14.10.4 Cancelling Timing Tasks...............................................................................................................14-57 14.10.5 Setting Time of Timing Tasks........................................................................................................14-58 14.10.6 Browsing CME Subtask.................................................................................................................14-59 14.10.7 Setting Period of CME Subtask.....................................................................................................14-59 14.10.8 Terminating Descendant Tasks......................................................................................................14-60 14.10.9 Rolling Back Descendant Tasks.....................................................................................................14-61 14.11 Browsing the Information of Timing Tasks............................................................................................14-61 14.12 Checking the Task Progress....................................................................................................................14-62 14.13 Checking the Task Execution..................................................................................................................14-62 14.14 Downloading Result Files.......................................................................................................................14-63 14.15 Reference for Integrated Task Management Interfaces..........................................................................14-65 14.15.1 Interface Description: Managing Timing Tasks.............................................................................14-67 14.15.2 Parameters for Setting Filtering Conditions...................................................................................14-69 14.15.3 Parameters for Creating/Copying Common Information...............................................................14-69 14.15.4 Parameters for Setting Common Information................................................................................14-70 14.15.5 Parameters for Setting Common Information for CME Download Tasks.....................................14-71 14.15.6 Parameters for Creating/Copying Time Settings for Scheduled Tasks..........................................14-71 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Contents
14.15.7 Parameters for Creating/Copying Time Settings for One-Off Tasks.............................................14-72 14.15.8 Parameters for Creating/Modifying/Copying MML Command Script..........................................14-73 14.15.9 Parameters for Creating/Modifying Software Download..............................................................14-74 14.15.10 Parameters for Creating/Modifying/Copying NE Backup...........................................................14-74 14.15.11 Parameters for Creating/Modifying/Copying CME Upload........................................................14-75 14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data ................................14-75 14.15.13 Parameters for Modifying the Synchronization of Inventory Data..............................................14-76 14.15.14 Parameters for Creating/Modifying CME Download..................................................................14-76 14.15.15 Parameters for Creating/Modifying/Copying HSL Script...........................................................14-77 14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management.....................................14-77 14.15.17 Parameters for Modifying Alarm Timing Acknowledgement.....................................................14-78 14.15.18 Parameters for Modifying Database Capacity..............................................................................14-79 14.15.19 Parameters for Modifying the Export of Alarm Data...................................................................14-80 14.15.20 Parameters for Modifying the Export of Configuration Data......................................................14-81 14.15.21 Parameters for Modifying the Export of NE Log........................................................................14-83 14.15.22 Parameters for Modifying the Export of Operation Log..............................................................14-83 14.15.23 Parameters for Modifying the Export of Performance Data........................................................14-84 14.15.24 Parameters for Modifying the Export of Inventory Data.............................................................14-85 14.15.25 Parameters for Modifying Data Backup in the M2000................................................................14-85 14.15.26 Parameters for Setting Time of Timing Tasks.............................................................................14-86 14.15.27 Parameters for Browsing CME Subtask.......................................................................................14-87 14.15.28 Parameters for Setting Period of CME Subtask...........................................................................14-88
15 NE Commissioning................................................................................................................15-1
15.1 Managing a NodeB Commissioning Project...............................................................................................15-2 15.1.1 NodeB Commissioning Items............................................................................................................ 15-2 15.1.2 Creating a NodeB Commissioning Project........................................................................................ 15-3 15.1.3 Viewing the NodeB Commissioning Progress...................................................................................15-5 15.1.4 Adjusting the Commissioning Object................................................................................................15-6 15.1.5 Deleting an NE Commissioning Task................................................................................................15-7 15.1.6 Starting/Stopping a NodeB Commissioning Task............................................................................. 15-7 15.2 Obtaining the NodeB Commissioning Report............................................................................................ 15-8 15.3 Reuploading the NE Configuration File......................................................................................................15-9 15.4 Reference to the NE Commissioning Interface...........................................................................................15-9 15.4.1 Interface Description: Viewing the NodeB Commissioning Progress.............................................15-10 15.4.2 Parameter for Creating an NodeB Commissioning Project.............................................................15-11 15.4.3 Parameter for Selecting the Path to the Configuration File..............................................................15-12
16 NE Maintenance Enhanced Management.........................................................................16-1

16.1 Upgrading the Version of Enhanced NE Maintenance...............................................................................16-2 16.2 Equipment Management............................................................................................................................. 16-3 16.3 Tracing Management...................................................................................................................................16-3 16.4 Monitoring Management.............................................................................................................................16-3 16.5 Realtime Performance Monitoring Management........................................................................................16-3 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
17 FAQ...........................................................................................................................................17-1
17.1 Why Cannot I Log In to the Client?............................................................................................................17-3 17.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and correct." .......................................................................................................................................................................17-3 17.1.2 Prompt "Invalid user account." .........................................................................................................17-4 17.1.3 Prompt "Invalid login duration."........................................................................................................17-4 17.1.4 Prompt "Invalid password." ..............................................................................................................17-5 17.1.5 Prompt "The password has expired. Please change your password!"................................................17-5 17.1.6 Prompt "Maintenance Mode." ...........................................................................................................17-5 17.1.7 Prompt "The User Has Reached the Maximum Login Attempts. The User Account Has Been Locked, and It Can Be Unlocked in 1 Minute."..........................................................................................................17-6 17.1.8 Prompt "The Server Doesn't Exist or Service Is Not Running."........................................................17-6 17.1.9 Prompt "Exceed Maximum Sessions."...............................................................................................17-7 17.1.10 Prompt "Loading Module Failed, System Will Exit."......................................................................17-7 17.1.11 Prompt "Failed to Log in to the Server after the Auto Client Upgrade or Running Exception" .......................................................................................................................................................................17-7 17.2 Why Does the Client Abort?.......................................................................................................................17-8 17.3 Why Can't the Client Work?.......................................................................................................................17-8 17.4 Why Is the Client Interface Abnormal?......................................................................................................17-9 17.5 Why Is the Connection Between Client and Server Discontinuous?..........................................................17-9 17.6 Why Can't a Topology View Be Refreshed?............................................................................................17-10 17.7 Why Does the Automatic NodeB Search Fail?.........................................................................................17-11 17.8 Why Is the Name of a New Topology Object a Repeat One?...................................................................17-11 17.9 Why Cannot Creating/Deleting an NE /Be Completed after a Long Time?.............................................17-11 17.10 Why Does a Real-Time Print Delay?......................................................................................................17-12 17.11 Why Can't Alarm Notifications by SMS Be Received?..........................................................................17-13 17.12 How to select or unselect multiple nodes?..............................................................................................17-13
18 Terms, Acronyms, and Abbreviations...............................................................................18-1

18.1 Terms...........................................................................................................................................................18-2 18.2 Abbreviations..............................................................................................................................................18-2
Index.................................................................................................................................................i-1
xxii
Issue 06 (2008-12-16)
Figures
Figures
Figure 1-1 Process of login authentication...........................................................................................................1-5 Figure 1-2 M2000 client interface......................................................................................................................1-29 Figure 1-3 Organization tree..............................................................................................................................1-36 Figure 1-4 Status table........................................................................................................................................1-37 Figure 1-5 Time parameter.................................................................................................................................1-38 Figure 1-6 Others................................................................................................................................................1-39 Figure 2-1 Model of the fault Alarm status conversion.......................................................................................2-6 Figure 2-2 Alarm reporting procedure.................................................................................................................2-9 Figure 2-3 Fault handling procedure..................................................................................................................2-30 Figure 2-4 Alarm Board Icon.............................................................................................................................2-40 Figure 2-5 Alarm Board.....................................................................................................................................2-41 Figure 2-6 Model of WRAN configured objects..............................................................................................2-109 Figure 2-7 Highlighting Alarms.......................................................................................................................2-151 Figure 2-8 Color settings..................................................................................................................................2-151 Figure 2-9 Sound settings.................................................................................................................................2-152 Figure 2-10 Alarm Board.................................................................................................................................2-152 Figure 2-11 Alarm Box....................................................................................................................................2-153 Figure 2-12 Remote Notification interface.......................................................................................................2-154 Figure 2-13 Simple correlation rule.................................................................................................................2-155 Figure 2-14 Advanced alarm correlation rule..................................................................................................2-155 Figure 2-15 Alarm Filtering interface..............................................................................................................2-156 Figure 2-16 Automatic Acknowledgement......................................................................................................2-157 Figure 2-17 Knowledge and Explanation.........................................................................................................2-158 Figure 2-18 Alarm Level Redefinition.............................................................................................................2-158 Figure 2-19 NE Alarm Settings dialog box......................................................................................................2-159 Figure 2-20 Alarm Query.................................................................................................................................2-160 Figure 2-21 Alarm statistics interface..............................................................................................................2-160 Figure 2-22 Performance Monitor interface-1.................................................................................................2-161 Figure 2-23 Performance Monitor interface-2.................................................................................................2-162 Figure 2-24 Performance Monitor interface-3.................................................................................................2-163 Figure 2-25 Object Group Manager interface..................................................................................................2-163 Figure 2-26 RAN network monitoring.............................................................................................................2-164 Figure 2-27 Monitoring panel..........................................................................................................................2-165 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Figures
M2000 Operator Guide Figure 2-28 System Monitor Browser interface...............................................................................................2-166
Figure 3-1 An example of CSV templates.........................................................................................................3-31 Figure 3-2 NE Property......................................................................................................................................3-38 Figure 3-3 Process for moving a NodeB in the same RNC................................................................................3-42 Figure 3-4 Process for moving a NodeB to another RNC..................................................................................3-44 Figure 3-5 Main Topology interface.................................................................................................................3-61 Figure 3-6 NodeB Re-Parent interface...............................................................................................................3-70 Figure 4-1 Security Management Interface.....................................................................................................4-52 Figure 4-2 NE User Management Interface.....................................................................................................4-53 Figure 4-3 NE Login Management Interface...................................................................................................4-54 Figure 4-4 OM User Binded NE Tab................................................................................................................4-55 Figure 4-5 NE Type Rules Tab..........................................................................................................................4-56 Figure 4-6 OM User Monitor Tab....................................................................................................................4-57 Figure 4-7 Local Maintenance MonitorTab....................................................................................................4-58 Figure 5-1 Process for reporting NE logs through the FTP server.......................................................................5-4 Figure 5-2 Process for reporting NE logs rather than through the FTP server.....................................................5-6 Figure 5-3 Log management interface...............................................................................................................5-21 Figure 6-1 Levels of measurement counters........................................................................................................6-5 Figure 6-2 Procedure of performance measurement............................................................................................6-8 Figure 6-3 Query result interface - 1..................................................................................................................6-49 Figure 6-4 Query result interface - 2..................................................................................................................6-49 Figure 6-5 Query result interface - 3..................................................................................................................6-50 Figure 6-6 Measure management interface - 1...................................................................................................6-51 Figure 6-7 Measure management interface - 2...................................................................................................6-51 Figure 6-8 Threshold management interface......................................................................................................6-52 Figure 6-9 User-defined counter management interface....................................................................................6-53 Figure 7-1 KPI list..............................................................................................................................................7-86 Figure 8-1 State transition of a patch...................................................................................................................8-3 Figure 8-2 Server tab File Structure of NodeB ...................................................................................................8-5 Figure 8-3 Server tab File Structure of Other NEs..............................................................................................8-5 Figure 8-4 NE tab File Structure of NodeB.........................................................................................................8-6 Figure 8-5 NE tab File Structure of Other NEs....................................................................................................8-6 Figure 8-6 Flow chart of software management...................................................................................................8-7 Figure 8-7 Software management networking.....................................................................................................8-8 Figure 8-8 Process for checking NE licenses.....................................................................................................8-88 Figure 8-9 Software Browser interface under the Server tab.............................................................................8-94 Figure 8-10 Software browser interface under the NE tab.................................................................................8-95 Figure 8-11 Interface of NE license sharing management.................................................................................8-96 Figure 8-12 Interface of license management in the RAN system.....................................................................8-98 Figure 9-1 MML Command interface on the client...........................................................................................9-71 Figure 9-2 Follow-Up Reports Browser Interface..............................................................................................9-72 Figure 9-3 MIT browsing interface....................................................................................................................9-73 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
Figures
Figure 9-4 Inventory management interface......................................................................................................9-74 Figure 9-5 Client window of the GBSS device panel........................................................................................9-75 Figure 9-6 Setting search conditions..................................................................................................................9-81 Figure 9-7 Search results....................................................................................................................................9-82 Figure 10-1 Backup Management Interface.....................................................................................................10-17 Figure 10-2 Log Information Collector interface.............................................................................................10-18 Figure 11-1 Dual Homing window (for 1+1 mutual-aid networking mode)..................................................11-17 Figure 11-2 Dual Homing window (for 1+1 active/standby networking mode).............................................11-18 Figure 11-3 Dual Homing window (for N+1 active/standby networking mode)............................................11-18 Figure 11-4 The Consistency Check tab page..................................................................................................11-19 Figure 11-5 Interface for managing the local network element domain..........................................................11-20 Figure 12-1 Networking of the MSC Pool.........................................................................................................12-4 Figure 12-2 Load balancing principle................................................................................................................12-6 Figure 12-3 TMSI Structure.............................................................................................................................12-23 Figure 12-4 Load balancing principle..............................................................................................................12-50 Figure 12-5 Main Interface of MSC Pool OM...............................................................................................12-62 Figure 12-6 Main Interface of CDMA Pool OM...........................................................................................12-64 Figure 12-7 Alarm Viewing interface of the MSC Pool..................................................................................12-66 Figure 12-8 Pool Parameter Setting interface................................................................................................12-67 Figure 13-1 Networking of the CDMA Pool......................................................................................................13-4 Figure 13-2 Main Interface of MSC Pool OM...............................................................................................13-43 Figure 13-3 Main Interface of CDMA Pool OM...........................................................................................13-45 Figure 13-4 Interface for viewing the CDMA Pool alarms..............................................................................13-47 Figure 13-5 CDMA Pool parameter setting interface......................................................................................13-48 Figure 14-1 State transition of a scheduled task...............................................................................................14-12 Figure 14-2 Timing Task Management interface.............................................................................................14-68 Figure 15-1 NodeB Commissioning interface................................................................................................15-10 Figure 17-1 The connection fails between the client and the server..................................................................17-9 Figure 17-2 Check box arrange style 1............................................................................................................17-13 Figure 17-3 Selected check boxes style 1.........................................................................................................17-14 Figure 17-4 Selected check boxes style 2.........................................................................................................17-14 Figure 17-5 Check box arrange style 2............................................................................................................17-14 Figure 17-6 Selected check boxes style 3.........................................................................................................17-14
Issue 06 (2008-12-16)
xxv
Tables
Tables
Table 1-1 Parameters..........................................................................................................................................1-29 Table 1-2 Menu bar............................................................................................................................................1-30 Table 1-3 System management tool buttons.......................................................................................................1-32 Table 1-4 Description of the fault management tool..........................................................................................1-33 Table 1-5 Buttons of the performance management tool...................................................................................1-33 Table 1-6 Descriptions of software management tool buttons...........................................................................1-34 Table 1-7 Descriptions of the configuration management tool buttons.............................................................1-34 Table 1-8 Descriptions of integrated task management tool buttons.................................................................1-35 Table 2-1 Differences between fault alarms and event alarms.............................................................................2-7 Table 2-2 Examples..............................................................................................................................................2-7 Table 2-3 Complete procedure for creating a user...............................................................................................2-8 Table 2-4 Fault handling procedure....................................................................................................................2-31 Table 2-5 MSC server performance monitoring counters..................................................................................2-79 Table 2-6 RNC performance monitoring counters.............................................................................................2-83 Table 2-7 BSC performance monitoring counters..............................................................................................2-84 Table 2-8 BSC6000 performance monitoring counters......................................................................................2-85 Table 2-9 GGSN80 performance monitoring counters......................................................................................2-85 Table 2-10 SGSN performance monitoring counter on the MML interface......................................................2-87 Table 2-11 SGSN performance monitoring counter on the FTP MML interface..............................................2-88 Table 2-12 HLR performance monitoring counters...........................................................................................2-90 Table 2-13 PCU performance monitoring counters...........................................................................................2-90 Table 2-14 iMSC performance monitoring counters..........................................................................................2-90 Table 2-15 MSC Pool performance monitoring counters..................................................................................2-91 Table 2-16 CDMA Pool performance monitoring counters...............................................................................2-91 Table 2-17 System Task.....................................................................................................................................2-98 Table 2-18 RNC Monitoring Counters.............................................................................................................2-110 Table 2-19 Cell Monitoring Counters..............................................................................................................2-112 Table 2-20 Description of the tabs i the NE Alarm Settings dialog box..........................................................2-159 Table 2-21 Description of the monitoring panel..............................................................................................2-165 Table 2-22 Functions of tabs on the system monitor browser interface...........................................................2-166 Table 2-23 Parameters related to the settings of alarm statistics .....................................................................2-226 Table 2-24 Parameters related to alarm statistics by levels .............................................................................2-227 Table 2-25 Parameters related to alarm statistics by IDs.................................................................................2-227 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Tables
M2000 Operator Guide Table 2-26 Parameters related to alarm statistics on a TopN basis .................................................................2-228 Table 2-27 Parameters about the information on basic configuration of the RNC object group.....................2-228 Table 2-28 Parameters about the information on basic configuration of object groups...................................2-229 Table 2-29 Parameters about the information on the Iu/Iur interface..............................................................2-229 Table 2-30 Parameters about the information on specified links of the Iu/Iur interface..................................2-230 Table 2-31 Basic parameters of the Iub interface.............................................................................................2-230 Table 2-32 Basic parameters of the Iub interface.............................................................................................2-231 Table 2-33 Parameters about E1T1 status........................................................................................................2-232 Table 2-34 Parameters about the distribution of NodeB and cells on the RNC...............................................2-233 Table 2-35 Parameters about the information on basic configuration of object groups...................................2-233 Table 2-36 Parameters related to the basic configuration of a cell...................................................................2-234 Table 2-37 Parameters related to the basic configuration of the common channel in a cell............................2-236 Table 2-38 Parameters related to intra-frequency neighboring cells................................................................2-238 Table 2-39 Parameters related to inter-frequency neighboring cells................................................................2-239 Table 2-40 Parameters related to GSM neighboring cells................................................................................2-241 Table 2-41 Parameters related to NodeB and cell statistics ............................................................................2-242 Table 2-42 Parameters for searching for monitored objects.............................................................................2-242 Table 3-1 Network devices categorized according to their home networks.......................................................3-13 Table 3-2 Categorize According to Service Functions.......................................................................................3-15 Table 3-3 NEs categorized according to the supported functions......................................................................3-18 Table 3-4 Basic NE information.........................................................................................................................3-20 Table 3-5 Description of the Physical Topology interface.................................................................................3-61 Table 3-6 Description of topology legends........................................................................................................3-62 Table 3-7 Description of NE connection states..................................................................................................3-63 Table 3-8 Samples of alarm states......................................................................................................................3-64 Table 3-9 Samples of alarm states......................................................................................................................3-64 Table 3-10 Description of the topology tool bar................................................................................................3-65 Table 3-11 Description of the shortcut menu.....................................................................................................3-67 Table 3-12 Description of the NodeB Re-Parent interface.................................................................................3-70 Table 4-1 Impact of ESN and license on Maximum Sessions............................................................................4-8 Table 4-2 Simple process for creating OM users...............................................................................................4-17 Table 4-3 Complete Process for Creating OM Users.........................................................................................4-18 Table 4-4 Examples of user sessions..................................................................................................................4-45 Table 4-5 Impact of ESN and license on Maximum Sessions..........................................................................4-45 Table 4-6 NE User Management Interface Description...................................................................................4-53 Table 5-1 Parameters related to NE operation logs............................................................................................5-24 Table 5-2 Parameters Related to NE security logs.............................................................................................5-25 Table 5-3 Parameters for querying NE operation logs.......................................................................................5-36 Table 5-4 Parameters for querying NE security logs.........................................................................................5-37 Table 6-1 Description of the options under Query Result................................................................................6-20 Table 6-2 Interface description...........................................................................................................................6-50 Table 6-3 Interface description...........................................................................................................................6-52
xxviii
Issue 06 (2008-12-16)
Tables
Table 6-4 Interface description...........................................................................................................................6-52 Table 6-5 Interface description...........................................................................................................................6-53 Table 6-6 Simple Threshold Parameters............................................................................................................6-57 Table 6-7 Counter Measurement Status.............................................................................................................6-63 Table 6-8 Object measurement status.................................................................................................................6-63 Table 8-1 Mapping relationship between NEs and files.......................................................................................8-4 Table 8-2 Scheduled download template............................................................................................................8-22 Table 8-3 Scheduled activation template............................................................................................................8-22 Table 8-4 Concepts related to license sharing....................................................................................................8-80 Table 8-5 Process for checking NE licenses......................................................................................................8-88 Table 8-6 Interface description...........................................................................................................................8-94 Table 8-7 File type..............................................................................................................................................8-94 Table 8-8 Interface description of NE license sharing management..................................................................8-96 Table 8-9 Interface description of license management in the RAN system.....................................................8-99 Table 8-10 Parameters of RNC patch.................................................................................................................8-99 Table 8-11 Parameters used to upgrade NE software and patches...................................................................8-100 Table 8-12 NE data...........................................................................................................................................8-101 Table 8-13 Parameters related to the NodeB software upgrade.......................................................................8-103 Table 8-14 NodeB license list.......................................................................................................................... 8-105 Table 8-15 NodeB license distribution list.......................................................................................................8-105 Table 8-16 File transfer parameters..................................................................................................................8-106 Table 9-1 NE Resource States..............................................................................................................................9-4 Table 9-2 Operations supported by the CBSC board...........................................................................................9-5 Table 9-3 Operations supported by the CBTS board...........................................................................................9-7 Table 9-4 Link types matching the NE link reports...........................................................................................9-15 Table 9-5 Resetting parameters in the A2 circuit...............................................................................................9-53 Table 9-6 Operating and maintaining the EMUA..............................................................................................9-66 Table 9-7 Operating and maintaining the PSU...................................................................................................9-68 Table 9-8 Operating and maintaining the PSU (DC/DC)...................................................................................9-69 Table 9-9 Description of the MIT Browsing interface.......................................................................................9-73 Table 9-10 Description of the interface management interface..........................................................................9-74 Table 9-11 Descriptions of the parameters for real-time monitoring of NE resources......................................9-76 Table 9-12 Descriptions of the parameters for configuring MML Command Client.........................................9-77 Table 9-13 Parameters for querying NE configuration......................................................................................9-78 Table 9-14 Parameters for querying the resource status of the NEs...................................................................9-79 Table 9-15 Descriptions of the parameters in the NE statistic report.................................................................9-79 Table 9-16 Parameters for querying the board information...............................................................................9-82 Table 9-17 Parameters for querying the subsystem status.................................................................................9-83 Table 9-18 Parameters for querying the clock status..........................................................................................9-85 Table 9-19 Parameters for querying A2 circuit status........................................................................................9-86 Table 9-20 Parameters for querying PCF or BSC buffer usage.........................................................................9-87 Table 9-21 Parameters for querying the DSP information.................................................................................9-87 Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Tables
M2000 Operator Guide Table 9-22 Parameters for querying the EVC timeslot occupancy....................................................................9-88 Table 9-23 Parameters for querying the L interface channel.............................................................................9-88 Table 9-24 Parameters for downloading the BTS software or data....................................................................9-89 Table 9-25 Parameters for blocking the BTS CPM board..................................................................................9-89 Table 9-26 Parameters for querying the BTS Ethernet IP address.....................................................................9-90 Table 9-27 Parameters for querying the FE port information............................................................................9-90 Table 10-1 Fields in the backup and restore task list.......................................................................................10-20 Table 10-2 Parameters for backing up NE files...............................................................................................10-21 Table 10-3 Parameters used for backing up the M2000 files...........................................................................10-21 Table 11-1 Interface description.......................................................................................................................11-19 Table 12-1 Basic concepts concerning the MSC Pool.......................................................................................12-4 Table 12-2 Load balance scheme of MSC Pool.................................................................................................12-5 Table 12-3 Principles of user transfer.................................................................................................................12-8 Table 12-4 Scenarios of MSC Pool..................................................................................................................12-10 Table 12-5 MSC Pool operation settings..........................................................................................................12-12 Table 12-6 MSC Pool operation rights list.......................................................................................................12-12 Table 12-7 Parameters of Pool attributes.........................................................................................................12-19 Table 12-8 Description of the operations.........................................................................................................12-28 Table 12-9 Real-time monitoring counters.......................................................................................................12-42 Table 12-10 Load balance scheme of MSC Pool.............................................................................................12-49 Table 12-11 Transfer Mode..............................................................................................................................12-51 Table 12-12 Description of the Main Interface of MSC Pool OM.................................................................12-62 Table 12-13 Description of the Main Interface of CDMA Pool OM.............................................................12-64 Table 12-14 Pool Parameter Setting interface...............................................................................................12-67 Table 13-1 Basic concepts concerning the CDMA Pool....................................................................................13-5 Table 13-2 User block table................................................................................................................................13-6 Table 13-3 Scenarios of CDMA Pool.................................................................................................................13-7 Table 13-4 CDMA Pool Operation Settings.......................................................................................................13-8 Table 13-5 CDMA Pool Operation Rights List..................................................................................................13-8 Table 13-6 Parameters of CDMA Pool attributes............................................................................................13-15 Table 13-7 Real-time monitoring counters.......................................................................................................13-26 Table 13-8 User block table..............................................................................................................................13-33 Table 13-9 Manually transferring users............................................................................................................13-34 Table 13-10 Description of the Main Interface of MSC Pool OM.................................................................13-44 Table 13-11 Description of the Main Interface of CDMA Pool OM.............................................................13-45 Table 13-12 CDMA Pool parameter setting interface......................................................................................13-48 Table 14-1 Tasks divided according to execution period...................................................................................14-3 Table 14-2 Tasks divided according to functions...............................................................................................14-4 Table 14-3 Tasks divided according to task features..........................................................................................14-6 Table 14-4 System timing tasks..........................................................................................................................14-7 Table 14-5 User timing tasks..............................................................................................................................14-9 Table 14-6 Description of the task description parameters..............................................................................14-11
xxx
Issue 06 (2008-12-16)
Tables
Table 14-7 Allowable operations for different task types................................................................................14-63 Table 14-8 Description of the Timing Task Management interface.................................................................14-68 Table 14-9 Descriptions of extended parameters............................................................................................. 14-80 Table 14-10 Extension parameters of NIC CMExport tasks............................................................................14-81 Table 14-11 Extension parameters of Configuration Data Export tasks..........................................................14-82 Table 14-12 Descriptions of extended parameters........................................................................................... 14-83 Table 14-13 Descriptions of extended parameters........................................................................................... 14-83 Table 14-14 Descriptions of extended parameters........................................................................................... 14-84 Table 14-15 Descriptions of extended parameters........................................................................................... 14-85 Table 14-16 Descriptions of parameters for setting timing task time.............................................................. 14-86 Table 14-17 Descriptions of CME subtask parameters....................................................................................14-87 Table 14-18 Descriptions of parameters of execution time of each period......................................................14-88 Table 15-1 NE commissioning items.................................................................................................................15-3
Issue 06 (2008-12-16)
xxxi
About This Document
About This Document
Purpose
This guide describes how to operate and maintain the network equipment.
Related Versions
The following table lists the product versions related to this document. Product Name M2000 Version V200R006
Intended Audience
The intended audiences of this document are:
l l
Network administrator Shift operator
Update History 06(2008-12-16)

Sixth formal release. Compared with V200R006 05(2008-09-26), the following content is modified. Context Integrated Task Management Data Management Description Add the contents related to NE Basic Information Export and NIC CM Export. Add the contents related to collecting network optimization data.
05(2008-09-26)
Fifth formal release. Compared with V200R006 04(2008-05-20), the following content is modified.
Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1
About This Document
Context Data Management Monitoring NE Performance in Real Time Performance Management
Description Add the contents related to selecting storage medium for backup of M2000 data. Add the contents related to setting the triggering times for monitor threshold alarms. Add the contents related to adding class 3 objects in batches.
04(2008-05-20)
Fourth formal release. Compared with V200R006 03(2008-03-15), the following content is modified. Context Integrated Task Management FAQ Description Modified the contents related to MML Command Script task. Add the contents related to causes of running client failure.
03(2008-03-15)
Third formal release. Compared with V200R006 02(2008-01-08), the following content is modified. Context Getting Started Software Management CDMA Pool Management Description Add the contents related to login authentication. Add the contents related to NE license sharing. Add the contents related to CDMA Pool management.
02(2008-01-08)
Second formal release. Compared with V200R006 01(2007-10-17), the following content is modified. Context NE Commissioning Configuration Management Data Management
2
Description Add the contents related to NodeB commissioning. Add the contents related to IMS, C02 and WiMAX. Add the contents related to IMS.
Issue 06 (2008-12-16)
About This Document
Context Fault Management Getting Started Integrated Network Monitoring Integrated Task Management Log Management Security Management Terms, Acronyms, and Abbreviations Topology Management Performance Management Software Management
Description Add the contents related to IMS. Add the contents related to IMS and WiMAX. Add the contents related to C02. Add the contents related to IMS. Add the contents related to IMS. Add the contents related to WiMAX. Add the contents related to WiMAX. Add the contents related to IMS, C02 and WiMAX. Add the contents related to IMS and C02. Add the contents related to IMS, C02 and WiMAX.
01(2007-10-17)
This is the first formal release.
Organization
1 Getting Started You can know the operation GUI of the M2000 client, how to log in to, log out of, lock, and unlock the client, how to set the broadcasting message, and how to modify the user password and customize the display style of the client. 2 Network Monitoring On the M2000 client, you can monitor the alarms on the network, real-time NE performances, the RAN network, and operational status of the NM system. In this way, you can detect network faults in time and then perform the related operations. 3 Topology Management Topology management offers the function of constructing and managing the topology structure of the whole network to display the networking situation and running status of the equipment. You can query and monitor the entire network operation in real time through the topology view. 4 Security Management This describes how to guarantee the security of the M2000. The M2000 security management manages the user and the user's rights. Through the security management, the security of the M2000 is guaranteed. 5 Log Management
Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3
About This Document
Log management involves the management of user logs, NE logs, and system logs. This function enables you to query logs and collect statistics of logs, thus helps monitoring and analyzing operational status of the system and troubleshooting. 6 Performance Management Through the performance measurement, you can measure and observe the security, the running status and the signaling connection status of the equipment, also you can measure and observe the utilization of the user and system resources. This function provides reliable data support for the measurement, designing and operation management of the communication network. The M2000 can measure the performance of multiple NEs. When an NE is successfully set up and communicates normally with the M2000, the NE automatically reports the measurement results of key performance counters to M2000 for data query and analysis based on a certain period. 7 Performance Report Management The M2000 provides the function of performance report management. You can set the query conditions of system reports and custom reports on the GUI. The M2000 can display the queried performance report on the report query interface. By analyzing the report data, you can obtain the information about the performance of each NE. You can also manage KPIs, such as create, modify, and delete KPIs on the KPI management interface. 8 Software Management By using the software management function, the M2000 performs integrated management of software , configuration data, and file information for NEs. The NEs that support this function are RNC, NodeB, MSC Server, MGW, GGSN, SGSN, BSC, BTS, and ASN-GW. 9 Configuration Management The M2000 provides the NE centralized management function. On the M2000 client, you can run the MML command or start the LMT of an NE to configure the NE. The NEs of class B and class C do not support the configuration of MML commands. 10 Data Management The M2000 manages both NE data and NM data. The management of NM data covers manually or periodically backing up NM data, and viewing NM backup files. The management of NE data covers manually or periodically backing up NE data, viewing NE backup files, restoring NE data, and collecting network optimization data. The M2000 also provides the function of collecting NM log files. 11 Dual-Homing and LN Domain Management This part describes the basic functions provided by dual-homing and local network domain management. 12 MSC Pool Management MSC Pool refers to a resource pool composed of MSC servers. The access network RNC/ BSC is connected to all the MSC servers in the pool. By using the MSC Pool, you can distribute the user service to the MSC servers in the pool according to the capacity ratio. In this way, the traffic peak in different districts and different time ranges can be balanced. The operator can make an investment based on the maximum traffic of the whole city rather than that of each district. Thus, the network capacity can be optimized and the investment is economized. Through the M2000 client, you can monitor and maintain the MSC Pool network and configure data. 13 CDMA Pool Management
4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
About This Document
This describes the CDMA pool, which is comprised of multiple MSCes. The CBSC of the access network connects to all MSCes in the pool. If the network is deployed as a CDMA pool, user services are distributed to MSCes on the basis of the capacity proportion of each MSCe. In this way, you can balance the traffic of MSCe in the pool in different regions on weekdays or weekends. Therefore, operators calculate the device investment on the basis of the maximum traffic of the city rather than that of each region. This helps operators to optimize network capacity and reduce the investment. You can configure data, monitor the performance, and maintain the CDMA pool network through the M2000 client. 14 Integrated Task Management The M2000 provides the function of integrated management of scheduled tasks. Thus, you can browse information such as the task status and the progress. You can also create, modify, and delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and save task result files to the client. 15 NE Commissioning The M2000 automatically commissions NEs. The commissioning items are as follows: the automatic detection and configuration of NEs, the automatic performance check of new NEs, and the automatic report generation. You can monitor the commissioning process, and collect and analyze the commissioning report on the M2000 client. Currently, the commissioning of NodeB can be performed. 16 NE Maintenance Enhanced Management The M2000 provides the enhanced maintenance management for some NEs to facilitate servicing these NEs. The NE enhanced maintenance management involves device management, trace management, monitoring management, and real-time performance monitoring. You can start this function only after the related components are upgraded on the client. 17 FAQ This part describes the typical faults of the M2000 client, analyzes the possible causes, and provides the solution. 18 Terms, Acronyms, and Abbreviations This part gives the M2000 glossary and abbreviations.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
Issue 06 (2008-12-16)
About This Document
Symbol
Description Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions
6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
About This Document
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder .
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 06 (2008-12-16)
1 Getting Started
1
About This Chapter
Getting Started
You can know the operation GUI of the M2000 client, how to log in to, log out of, lock, and unlock the client, how to set the broadcasting message, and how to modify the user password and customize the display style of the client. 1.1 Logging In to the M2000 This section describes how to log in to the M2000, and how to log out the current user or exit the M2000 client. 1.2 Changing Password This section describes how to modify the login password. 1.3 Shortcuts to Client GUI Controls This section describes the GUI controls on the M2000 client, such as the menu, button, and dropdown list. 1.4 Customizing Client GUI Style You can customize the GUI effect of the M2000 client. 1.5 Locking Client This section describes how to lock the M2000 client. 1.6 Unlocking the Client You can perform this task to unlock the locked M2000 client. 1.7 Setting the Running Mode of the System The running mode of the system can be the single-user mode or the multi-user mode. You can allow one user or multiple users to log in by setting the running mode of the system. 1.8 Setting the Alarm Sound When the Network Is Disconnected You can set the alarm sound when the network is disconnected on the M2000 client. When the M2000 client is disconnected from the network, the sound box plays the corresponding alarm sound. 1.9 Setting the LMT Proxy The local maintenance terminal (LMT) is the local O&M system of an NE. If the firewall is set on the NE, the LMT cannot be directly connected to the NE. You can set the M2000 server as
Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
1 Getting Started
the LMT proxy, through which you can connect the LMT to the NEs. This function is applicable when you start the LMT through the M2000 rather than starting the LMT manually. 1.10 Setting the LMT Prompt You can determine whether to display a dialog box, which prompts the M2000 user when NE user logs in or exits the NE LMT. 1.11 Sending Broadcasting Messages This section describes how to send broadcast messages from the client. 1.12 Viewing NM License Information You can view information about all function control items in the licence control items configured in the M2000 server. 1.13 Viewing NE Partitioning This topic descirbes how to view the NE partitioning. If the M2000 server applies the multiserver load-sharing system, different NEs can be managed by different service partitions. On the client, you can view different NE partitioning. 1.14 Downloading NE Mediation Data to the M2000 Client When the NE version on the client is inconsistent with that on the server, you can manually download the NE mediation file to the M2000 client to reach the consistency. The dynamic NE upgrade refers to upgrading dynamically the NE configuration files on the M2000 Client. When detecting that the NE version changes, the M2000 server obtains the new version configuration files from the NE. You can upgrade manually these files on the M2000 Client. 1.15 Managing the Exported Files in the Server In the File Browser window, you can view the information that are exported from the server according to the path to the exported file. 1.16 Managing User-Defined Object Groups You can group objects of the same type into an object group. In this way, you can perform the same operation on all the objects in this object group. The M2000 allows you to create, view, and modify the information about a user-defined object group. 1.17 Reference for M2000 Client Interfaces This describes the M2000 client interface and related parameters, which helps you perform the related operations on the client.
1-2
Issue 06 (2008-12-16)
1 Getting Started
1.1 Logging In to the M2000

This section describes how to log in to the M2000, and how to log out the current user or exit the M2000 client. 1.1.1 Logging In to theM2000 Server The M2000 uses the client/server mode. To perform an operation, you need to log in to the server through the M2000 client. 1.1.2 Logging Out the User Account To ensure security, when you do not need to perform any operations on the client, you can log out the user account. This operation does not end the client program. 1.1.3 Exiting the M2000 Client when you do not need to do any operations on the client, exit the M2000 client. And this operation will end the client program. 1.1.4 Checking Whether the Client Need Upgrade After the server is updated, the server and the client do not match. Therefore, the client has to be updated accordingly. The user can use the manual check function to check whether the client version and the server version match with each other. 1.1.5 Setting the Interval for Update Checking of M2000 Client After the server is updated, the server and the client do not match. Therefore, the client has to be updated accordingly. After the interval for update checking is set, the M2000 periodically checks whether the client needs to be updated. 1.1.6 Automatically Upgrading the Client Software After a minor upgrade of the server software, that is, the change of SP version in the software version: product name+VxxxRxxxCxxBxxy[SPxx], the M2000 can automatically upgrade the client software to ensure the consistency.
1.1.1 Logging In to theM2000 Server

The M2000 uses the client/server mode. To perform an operation, you need to log in to the server through the M2000 client.
Prerequisite
Before login, ensure that the M2000 client and server are connected normally, and the server works correctly.
Context
l
Except the Administrator, if you have not logged in to M2000 for more than 30 days, your user account becomes invalid automatically. Before you can use the account again, the account need be set to valid by a user who has the Administrator rights. If you do not log in during the preset period after the previous login, the M2000 disables or delete the user account. If a new user account has not logged in to the M2000 server, M2000 does not delete or invalidate it.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
Issue 06 (2008-12-16)
1 Getting Started
l
Different NEs support different management functions .Whether some functions are visible is associated with the license of the system and the rights of users.
Procedure
Step 1 Start the M2000 client from the start menu. Step 2 In the Login dialog box, click 1. 2. Click Add. In the Add Server Information dialog box, enter the host name and IP address of the server.
NOTE
on right of Server.
Step 3 In the Server List dialog box, configure the M2000 server.
l l l
The default port number is 9999. Do not change it. Click Modify to change the host name and IP address of the server. Click Delete to delete the server information.
3.
Click OK.
Step 4 In the Login dialog box, select a server, then enter the user name and password. Step 5 Click Login. Figure 1-1 shows the process of login authentication.
1-4
Issue 06 (2008-12-16)
1 Getting Started
Figure 1-1 Process of login authentication
Issue 06 (2008-12-16)
1-5
1 Getting Started
The process of login authentication is as follows: 1. 2. 3. 4. 5. 6. 7. 8. 9.

l
The current client checks whether another client is being upgraded. If a client is being upgraded, the login is not allowed. Initialize the communication connection between the client and the server. Check whether the daemon service is running properly. Obtain the copyright notice on the server and display the contents. Check whether the client version is consistent with the server version. It the two versions are inconsistent, display the inconsistent messages or prompt the user to upgrade. Invoke the login interface on the server. Check whether the user account and password are correct. Check whether the user password expires according to the security policy. If the password expires, it must be changed for a successful login. Check whether the login is within the allowable time period according to the security policy. After the user account passes the authentication, the client loads each software module. If the user name and the password are correct, the Loading dialog box is displayed, indicating the loading progress. If the user name or password is wrong, the Information dialog box is displayed, saying Login failed. Please enter the correct user name and password. If the password is to expire in the specified days, the system prompts you to change the password before the expiration date. If the license is to expire in the specified days, the system notifies you of the expiration date.
----End
Related References
1.17.3 Parameters for Logging In to the M2000 Server
1.1.2 Logging Out the User Account

To ensure security, when you do not need to perform any operations on the client, you can log out the user account. This operation does not end the client program.
Context
l
To ensure security, when you do not need to perform any operations on the client, you can log out the user account or exit the M2000 client. This operation does not end the client program. After logout, the Login dialog box is displayed. You can enter the proper information in the dialog box to log in to the M2000 again.
Procedure
Step 1 Choose System > Logout. Step 2 In the Confirmation dialog box, click OK. ----End
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
1 Getting Started
1.1.3 Exiting the M2000 Client

when you do not need to do any operations on the client, exit the M2000 client. And this operation will end the client program.
Context
l
To ensure security, when you do not need to do any operations on the client, exit the M2000 client or log out the user account. If you do not need to do any operations for a while, you can 1.5.2 Locking Client Manuallyor 1.5.1 Locking the Client Automatically. This operation will end the client program. If you want to do some operations on the client, restart the M2000 client.
Procedure
Step 1 Choose System > Exit. Step 2 In the Confirmation dialog box, click OK. ----End
1.1.4 Checking Whether the Client Need Upgrade

After the server is updated, the server and the client do not match. Therefore, the client has to be updated accordingly. The user can use the manual check function to check whether the client version and the server version match with each other.
Context
After the M2000 server is upgraded, you can perform this operation to check whether the version of the client match that of the server. If the versions do not match, you can upgrade the client.
Procedure
Step 1 Choose Help > Check For Upgrades to check whether the client version matches the server version. l l When the versions match, the system prompts that the client version matches the server version and the client does not need to be upgraded. Click OK. When the version do not match, the system prompts that the versions do not match and the client needs to be upgraded, and it asks you whether to start the upgrade immediately. Click OK to continue with the next step.
Step 2 In the Update Wizard: Update Applications window, click Continue. The upgrade progress is displayed. Step 3 In the Update Wizard: Update Applications window, click Finish. ----End
1.1.5 Setting the Interval for Update Checking of M2000 Client

After the server is updated, the server and the client do not match. Therefore, the client has to be updated accordingly. After the interval for update checking is set, the M2000 periodically checks whether the client needs to be updated.
1 Getting Started
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences dialog box, in the navigation tree on the left, select Upgrade. In the Time Interval drop-down list, select the interval for update checking. Step 3 Click OK. ----End
1.1.6 Automatically Upgrading the Client Software

After a minor upgrade of the server software, that is, the change of SP version in the software version: product name+VxxxRxxxCxxBxxy[SPxx], the M2000 can automatically upgrade the client software to ensure the consistency.
Context
NOTE
l l
You can check whether the versions on the client and the server are consistent. For details, refer to 1.1.4 Checking Whether the Client Need Upgrade. The client can be correctly upgraded only when the software version of the server has the same version sequence with and greater than that of the client. The same version sequence means that in the software versions, that is, product name+VxxxRxxxCxxBxxy[SPxx], the numbers after B are the same.
Only when the software version of the client is of the same version sequence as that of the server and the software version of the server is later than the client version, the client can be correctly updated. The software version is in the format of Name of the product + VxxxRxxxCxxBxxy [SPxx]. For instance, if the software version of the server is V200R005C01B066SP01, the software version of the client can be updated only when it is of the V200R005C01B066. According to the flag in the version response, the client determines whether the upgrade tool is required.
Procedure
Step 1 Start the client. Select the server and then click Login.
NOTE
The M2000 automatically compares the versions of the client and server. If the versions are not consistent, the system displays a dialog box, prompting you to upgrade the client.
Step 2 Click OK. The client exits and the Upgrade Wizard dialog box is displayed. Step 3 Click Continue. The client downloads the client programs from the corresponding directories on the server. Step 4 Click OK. ----End
1 Getting Started
1.2 Changing Password

This section describes how to modify the login password.
Context
l
When using the default password policy, the user password cannot be less than six characters. The password of Admin cannot be less than eight characters. To ensure the security of the M2000, you are recommended to change the user password periodically.
l l
Procedure
Step 1 Choose Security > Change Password. Step 2 In the Change Password dialog box, in the Old Password text box, enter the password of the login user. Step 3 In the Change Password dialog box, in the New Password text box, enter the new password. Step 4 In the Change Password dialog box, in the Confirm Password text box, enter the new password again. Step 5 Click OK. ----End
1.3 Shortcuts to Client GUI Controls

This section describes the GUI controls on the M2000 client, such as the menu, button, and dropdown list.
For Menu
For any menu followed by the asterisk * (* represents a letter or a number), you can press Alt +* to choose the root menu and press * to choose a sub-menu.
For Button
l
For any button followed by the asterisk * (* represents a letter or a number), you can press Alt+* instead of clicking the button. When a dialog box is open and a dot square is on a button, this button is the default button. If the dot square is not on any button, OK is the default button. If you click Apply in a window, the settings in the window take effect and the window is not closed. You can continue with other operations. If you click OK in a window, the settings in the window take effect and the window is closed. When a dot square is on a button, you can press Enter or space bar instead of clicking the button.
Issue 06 (2008-12-16)
1 Getting Started
l
When the button that gets the dot square does not support the Enter operation and you press Enter, the default button in that dialog box is clicked.
For Drop-Down List

l
When a dot square is on a drop-down list, you can press the down arrow key to expand the drop-down list. You can press the up arrow key and down arrow key to switch between options in a drop-down list, and press Enter to select the current option. For any drop-down list followed by the asterisk *(* represents a letter or a number) and when the drop-down list is expanded, you can press * instead of choosing an option.
For Option Button and Check box

l l
If a dot square is on an option button, you can press the space bar to select the option button. If a dot square is on a check box, you can press the space bar to select or clear the check box.
For Navigation Tree

When a dot square is on the navigation tree, you can press the down arrow key or up arrow key to switch between the nodes, and press the left or right arrow key to collapse or expand a node.
Other Combined Shortcut Keys

The client provides various combined shortcut keys. These shortcut keys help you perform operations faster. Operation Exit a dialog box or prompt Unlock a terminal Open the Help Close the current window Restore down (when the service window in the public window is maximized) Minimize the window (applied to the service window in the public window) Maximize the window (when the service window in the public window is restored) Shortcut keys Esc Ctrl+Alt+U F1 Ctrl+F4 Ctrl+F5 Ctrl+F9 Ctrl+F10
NOTE
The public window area refers to the area below the toolbar on the M2000 client.
1.4 Customizing Client GUI Style

You can customize the GUI effect of the M2000 client.
1-10
Issue 06 (2008-12-16)
1 Getting Started
1.4.1 Setting Output Information The output window is at the bottom of the M2000 client GUI. It displays the prompt messages and feedback information of the errors that affect the running of the M2000. You can manage the display of output messages and export the messages by setting the output window. 1.4.2 Setting the Display Effect of Alarm Status in the Topology View This section describes how to select the alarm state that needs to be displayed on the topology view, adjust the priority of the alarm state. So, on the topology view, the alarm state of the network element icon is displayed according to the priority. 1.4.3 Setting the Toolbar You can perform this task to set the shortcut buttons on the toolbar. 1.4.4 Custom Menu This describes how to trigger the execution files by setting the customizing menu. On the M2000 client, you can start programs outside the M2000 system. 1.4.5 Customizing Client Time Display Mode You can customize the time display mode as desired. 1.4.6 Customizing the Display Mode of Numbers Through this operation, customize the number display mode of the client, such as, the display mode of the system monitoring data. 1.4.7 Customizing the Mesurement You can set the metrology, namely, imperial (IMP) measurement system or metric measurement system (MET). The default setting is MET. 1.4.8 Setting Common Options for Performance Management The system can save the settings of some common options to execute the related functions according to the parameter settings.
1.4.1 Setting Output Information

The output window is at the bottom of the M2000 client GUI. It displays the prompt messages and feedback information of the errors that affect the running of the M2000. You can manage the display of output messages and export the messages by setting the output window.
Procedure
Step 1 Choose System > Preferences. Step 2 From the navigation tree on the left of the Preferences window, select Output Window, and then set relevant parameters.
NOTE
l l l l l l
Right-click in the output pane and choose Save As to save the output information as an *.txt file. Right-click in the output pane and choose Clear to clear all the displayed output information. Right-click in the output pane and choose Select All, and then right-click again and choose Copy to copy all the displayed output information to the clipboard. Right-click in the output window and choose Auto Scroll. The output information is set to scroll automatically. Right-click in the output window again and choose Auto Scroll, the auto scroll is cancelled. Right-click in the output window and choose Parameter Setting. The Output Window pane is displayed in the Preferences window. Right-click in the output window and choose Find. Enter the keywords in the Find what dialog box.
Issue 06 (2008-12-16)
1-11
1 Getting Started
Step 3 Click OK. ----End
Related References
1.17.5 Parameters for Output GUI Information
1.4.2 Setting the Display Effect of Alarm Status in the Topology View
This section describes how to select the alarm state that needs to be displayed on the topology view, adjust the priority of the alarm state. So, on the topology view, the alarm state of the network element icon is displayed according to the priority.
Context
l
The settings take effect only after you log in to the M2000 client again.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences window, select Topology Status Display. Step 3 In Alarm Status, select the alarm status you want to display. Step 4 Select the alarm status for which you want to adjust the display sequence. Click Up or Down to adjust the display sequence in the topology view. Step 5 Click OK. ----End
1.4.3 Setting the Toolbar

You can perform this task to set the shortcut buttons on the toolbar.
Procedure
Step 1 Choose System > Customize Toolbar. Step 2 In the Customize Toolbar dialog box, deselect the checkboxed under Toolbar Groups, for example, System or Fault as desired. Step 3 Click Advanced to display a new dialog box.
NOTE
The new dialog box consists of two sections: Usable Tools and Customize Tools. All the buttons in Customize Tools are displayed on the toolbar, and the buttons in Usable Tools are not displayed on the toolbar. Click Advanced again. The new dialog box is hidden. Click Reset to restore the toolbar so that you can reset it.
l l
Step 4 In the Toolbar Buttons dialog box, set the buttons you want to display on the toolbar.
1 Getting Started
l l
In the Usable Tools group box, select the buttons you want to display. Click move the buttons to Customize Tools. In the Customize Tools group box, select the buttons you do not want to display. Click to move the buttons to Usable Tools.
to
Related References
1.17.4 Tool Buttons
1.4.4 Custom Menu

This describes how to trigger the execution files by setting the customizing menu. On the M2000 client, you can start programs outside the M2000 system.
Prerequisite
You have logged in to the M2000 client.
Context
NOTE
l l
The executable file triggered by the customizing menu is a program outside the M2000 and this program is owned by the client. The length of character strings entered in the Menu Group Name and Menu Name fields is 1 to 20. Characters such as `!@#$%^&*+={}[]\\|;':\"<>,.?/ are not allowed.
Procedure
Step 1 Choose Custom Menu > Menu Setting. The Custom Menu Setting window is displayed. Step 2 Right-click the Custom Menu node and choose Add Menu Group from the shortcut menu. Step 3 In the displayed Menu Attribute Modifying dialog box, enter the name of the menu group.
NOTE
A maximum of 10 menu groups can be added.
Step 4 Right-click the menu group node, and then choose Add Menu from the shortcut menu. Step 5 In the displayed Menu Attribute Modifying dialog box, set the menu information. 1. 2. 3. Enter the menu name in the Menu Name field. In File Path, click be triggered. . In the displayed Open dialog box, select the executable file to
Optional: You can use the custom menu to start all the applications that can be started by DOS commands. The format of the start parameters varies based on the application. In Parameters, you can enter the parameters according to the program format. For example, according to the LMT client configuration, the startup parameter of the LMT client is -u "username" -p "password" -o "NE name" -pip "proxyip" -nip "neip" -closeall "true" -t "bamid". You can enter the startup parameters in the Parameters field.
Issue 06 (2008-12-16)
1 Getting Started
After you customize the menu, you can log in to the LMT of the NE through the custom menu.
NOTE
l l
A menu group supports a maximum of 10 menus. In the Parameters field, you can enter a maximum of 20 characters.
Step 6 Click OK. The added information about the custom menu, which includes the menu name and the path of the executable file, is displayed in the right of the Custom Menu Setting window. Step 7 Click OK. The Custom Menu Setting dialog box is closed. ----End
Postrequisite
Choose the corresponding menu under Custom Menu . Start up the executable file that is set on the M2000 client.
1.4.5 Customizing Client Time Display Mode

You can customize the time display mode as desired. 1.4.5.1 Setting the Time Format of the Client This section describes how to set the time format of the client. 1.4.5.2 Setting the Time Mode of the Client By setting the time mode of the client, set the default time mode while querying the alarm. Here, the time mode is divided into the server time and the network element time. 1.4.5.3 Setting the Date Format of the Client This section describes how to set the date format of the client.
Setting the Time Format of the Client

This section describes how to set the time format of the client.
Context
l
This setting is bound to users. That is, the setting is valid only to the user who performs this setting. The setting does not affect other users of the client. After you set the time format, you need to log in to the server again for the settings to take effect. You can preview the time format in Appearance Example.
Procedure
Step 1 Choose System > Preferences. Step 2 From the navigation tree on the left of the Preferences window, expand the Region Setting node and select Time. Step 3 In the Time Settings group box, set the time format.

NOTE
1 Getting Started
The time format is displayed in Appearance Example.
Related References
1.17.7 Parameters for Setting the Time Style
Setting the Time Mode of the Client

By setting the time mode of the client, set the default time mode while querying the alarm. Here, the time mode is divided into the server time and the network element time.
Context
The settings take effect after you log in to the client again.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences dialog box, select Time Mode.
NOTE
The time can be displayed in two modes:

l l
Server time mode: If you select this mode, the alarms are queried according to the server time. NE time mode: If you select this mode, the alarms are queried according to the NE time.
You are recommended to select the default value NE time mode.
Setting the Date Format of the Client

This section describes how to set the date format of the client.
Context
l
This setting is bound to users. That is, the setting is valid only to the user who performs this setting. The setting does not affect other users of the client. After you set the date format, you need to log in to the server again for the settings to take effect. You can preview the new date format in Appearance Example.
Procedure
Step 1 Choose System > Preferences. Step 2 In the navigation tree on the left of the Preferences window, expand the Region Setting node and select Date.
1 Getting Started
Step 3 In the Date Settings group box, set the date format.
NOTE
l l l
Date Separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and ".". The default is "-". Date Format: display format of the date. It can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/yyyy". The default is "yyyy/MM/dd". The date display effect that you set is displayed in Appearance Example.
1.4.6 Customizing the Display Mode of Numbers

Through this operation, customize the number display mode of the client, such as, the display mode of the system monitoring data.
Context
l l
The settings take effect after you log in to the client again. Modifications to the region number settings may adjust the number display and sequence effect. The display effect is displayed in the Positive number text box and Negative number text box.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Region Settings dialog box, click the Number tab, and set Digits of Decimal Fraction, Number Separator, and Start with 0.
NOTE
l l l
Digits of Decimal Fraction: digits of decimal fraction. The default is two digits, and the value ranges from 0 to 3, 2 by default. Number Separator: whether to use the comma (,) to group the integer part of numbers. The default is blank space. You can choose the blank space or comma ",". Start with 0: whether to add 0 before the decimal point. The default is to add a 0.
1.4.7 Customizing the Mesurement

You can set the metrology, namely, imperial (IMP) measurement system or metric measurement system (MET). The default setting is MET.
Context
The setting has effects on the display mode of performance measurement results. The performance measurement data is automatically displayed according to the defined metrology.
1 Getting Started
Procedure
Step 1 Choose System > Metrology Setting. The Metrology Setting dialog box is displayed. Step 2 Select IMP or MET. Step 3 Click OK to save the setting. Click Cancel to cancel the setting.
NOTE
After the modification, the setting takes effect on the client only.
----End
1.4.8 Setting Common Options for Performance Management

The system can save the settings of some common options to execute the related functions according to the parameter settings.
Context
Common option settings are bound to the client. In other words, the parameters set on the same client apply to all its users.
Procedure
Step 1 Choose Performance > Preference to view the System Setting dialog box. Step 2 Set the parameters. Step 3 Click Apply or OK. ----End
Related References
1.17.8 Parameters for Setting Common Options for Performance Management 1.17.2 Interface Description: Common Options for Performance Management
1.5 Locking Client

This section describes how to lock the M2000 client. 1.5.1 Locking the Client Automatically You can set the M2000 to lock the client automatically in case you forget to lock the client. After you set the auto lock and there is no operation performed on the client during the preset time period, the M2000 locks the client automatically. 1.5.2 Locking Client Manually When you do not need to perform any operations on the M2000 client, you can lock the client manually to prevent illegal operations.
1 Getting Started
1.5.1 Locking the Client Automatically

You can set the M2000 to lock the client automatically in case you forget to lock the client. After you set the auto lock and there is no operation performed on the client during the preset time period, the M2000 locks the client automatically.
Procedure
Step 1 Choose System > Preferences. Step 2 From the navigation tree on the left of the System Setting window, select Locking Interval. Step 3 Select Automatically locked check box. In the minutes later, this client will be automatically locked. text box, enter the lock time.
NOTE
l l
Clear Automatically locked check box. The function of auto lock is disabled. minutes later, this client will be automatically locked.: Set the time to start the auto lock. The value ranges from 1 minute to 35000 minutes. The default is 3 minutes.
1.5.2 Locking Client Manually

When you do not need to perform any operations on the M2000 client, you can lock the client manually to prevent illegal operations.
Procedure
You can lock the client in two ways: l l Choose System > Lock Terminal. Click on the toolbar.
The client is locked. The operations on the keyboard and the mouse cannot be performed. ----End
1.6 Unlocking the Client

You can perform this task to unlock the locked M2000 client.
Context
l l
If you unlock your own account, the M2000 becomes operable after it is unlocked. If your user account is in the Administrators user group and you unlock a user account of someone else, that account is logged out after it is unlocked.
Procedure
Step 1 When the client is locked, press Ctrl+Alt+U .
1 Getting Started
Step 2 In the Unlock dialog box, enter the user name and the password, and then click OK. ----End
1.7 Setting the Running Mode of the System

The running mode of the system can be the single-user mode or the multi-user mode. You can allow one user or multiple users to log in by setting the running mode of the system.
Prerequisite
l l
You are the admin user. No admin users have logged in to other clients.
Context
l
Single-user mode: applicable for maintenance. Only one user is allowed to log in and to establish the session. Mulit-user mode: applicable for normal operation. Multiple users are allowed to log in to the system at the same time.
Procedure
Step 1 Choose System > Preferences. The System Setting dialog box is displayed. Step 2 In the navigation tree, select the System Login Mode node. Choose the system running mode in the right pane. Running Mode Multi-user mode Single-user mode Step 3 Click OK. Step 4 Enter the delay time for mode switching. Enter the delay time for mode switching in the Set Switch Delay dialog box. Operation Go to Step 5. Go to Step 3.
CAUTION
The single-user mode allows only one user to log in and to establish the session. Therefore, after the change of the running mode, the current client is still active, while other online clients that are not authorized to change the mode are forced to exit. You need to set the switch delay time based on actual situations so that clients have time for preparations. Step 5 Click OK.
l
For the multi-user mode, the System Setting dialog box is closed.
Issue 06 (2008-12-16)
1 Getting Started
l
For the single-user mode, the system will count down the mode switching and inform other online clients. Then you can click Cancel to cancel the mode switching.
The system counts down the mode switching and informs other online clients. ----End
1.8 Setting the Alarm Sound When the Network Is Disconnected

You can set the alarm sound when the network is disconnected on the M2000 client. When the M2000 client is disconnected from the network, the sound box plays the corresponding alarm sound.
Context
l l
You can use the sound file of the M2000 or others. Only the sound files of the Wav type in the PCM format are supported. The Microsoft ADPCM type is not supported. You can set the delay time of the alarm sound in $iManagerM2000Client\style\defaultstyle \conf\sf\ConnectionConfig.properties on the M2000 client. The unit of the delay time is second. If the connection between the client and the network is not recovered within the preset delay time, the sound box plays the corresponding alarm sound.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences dialog box, from the navigation tree on the left, select Disconnection Sound. Step 3 In the Disconnection Sound group box, choose Enable, and then click box, select a sound file, and then click Open. Step 4 Optional: Click Step 5 Click OK. ----End to listen to the sound. . In the Open dialog
1.9 Setting the LMT Proxy

The local maintenance terminal (LMT) is the local O&M system of an NE. If the firewall is set on the NE, the LMT cannot be directly connected to the NE. You can set the M2000 server as the LMT proxy, through which you can connect the LMT to the NEs. This function is applicable when you start the LMT through the M2000 rather than starting the LMT manually.
Context
l
For NodeB, the M2000 automatically starts the LMT proxy. You are not allowed to change the LMT proxy setting. For other NEs that support the LMT proxy, the M2000 does not start the LMT proxy by default. You, however, can start or stop the LMT proxy.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2008-12-16)
1-20
1 Getting Started
CAUTION
You must use the M2000 as the proxy when you plan to log in to the NodeB because the NodeB has no BAM.
l
The parameters that you set are saved on the server in real time and overwrite the previous setting. When other users log in to the client, the client automatically reads and uses the setting saved on the server. If a user changes the setting, the changed setting is stored on the server. It takes effect to the clients that log in later rather than those who have logged in.
Procedure
Step 1 Choose System > Proxy Service Setting. Step 2 Select the types of NE maintenance stations on the Proxy Service Setting window. When these NE maintenance stations are started, the M2000 proxy enables them to connect to the NEs. Step 3 Click OK. ----End
1.10 Setting the LMT Prompt

You can determine whether to display a dialog box, which prompts the M2000 user when NE user logs in or exits the NE LMT.
Procedure
Step 1 Choose System > LMT Prompt Setting. The LMT Prompt Setting dialog box is displayed. Step 2 Select or deselect the check box Prompt when LMT user login or logout. Step 3 Click OK. ----End
1.11 Sending Broadcasting Messages

This section describes how to send broadcast messages from the client.
Context
l l
Broadcast messages are only sent to the clients that log in to the server normally. A client can receive the broadcast messages sent by itself. A prompt is given in the output window.
Procedure
Step 1 Choose System > Broadcast Message.
1 Getting Started
Step 2 In the Broadcast Message dialog box, in the Message entry box, enter the message content.
NOTE
l l
A broadcast message cannot be null, and cannot exceed 128 characters. The system automatically adds line feeds according to the length of broadcast messages.
Step 3 Click Send. Step 4 In the Prompt dialog box, click OK. ----End
1.12 Viewing NM License Information

You can view information about all function control items in the licence control items configured in the M2000 server.
Context
The license keys are divided into resource keys and function keys. For the resource keys, the system controls the number of the items, such as the frequency of the CBSC. For the function keys, the system controls if the function can be performed by the user. Only authorized users can use the function keys.
Procedure
Step 1 Choose Help > About. The About dialog box is displayed. Step 2 Click the License Information tab. ----End
Related References
1.17.6 Parameters for Viewing NM License Information
1.13 Viewing NE Partitioning

This topic descirbes how to view the NE partitioning. If the M2000 server applies the multiserver load-sharing system, different NEs can be managed by different service partitions. On the client, you can view different NE partitioning.
Prerequisite
Procedure
Step 1 Select Configuration > Query NE SubArea, the Query NE Subarea window is displayed. Step 2 Select the query condition, and then click Query. You can view the NEs based on either the NE partitions or the NE names.

l
1 Getting Started
Query based on the NE partitions: In the Query Result dialog box, the NE distribution conditions and the NE information such as the NE type, the NE name, the NE version of the selected partition will be displayed. In the Statistic dialog box, the partition information such as the host name, the IP address, and the instance name of the database will be displayed. Query based on the NE name: In the Query Result dialog box, the NE distribution conditions and the NE information such as the NE type, the NE name, the NE version of the selected partition will be displayed. In the Statistic dialog box, the partition information such as the host name, the IP address, and the instance name of the database will be displayed.
NOTE
Click Save, the query results are saved to the file.
For parameter related description, refer to 1.17.9 Parameters for the NE Partitioning Information. ----End
Related References
1.17.9 Parameters for the NE Partitioning Information
1.14 Downloading NE Mediation Data to the M2000 Client

When the NE version on the client is inconsistent with that on the server, you can manually download the NE mediation file to the M2000 client to reach the consistency. The dynamic NE upgrade refers to upgrading dynamically the NE configuration files on the M2000 Client. When detecting that the NE version changes, the M2000 server obtains the new version configuration files from the NE. You can upgrade manually these files on the M2000 Client.
Context
The macro file provides the collection of all commands defined by NEs. From this file, you can know what commands are supported by the version and the meaning of each parameter.
Procedure
Step 1 Choose Help > Online Update to view a progress bar through which the client queries the new version file from the server. Step 2 If new version files exist, the server displays the Update Available dialog box to show the NE type and version number of the files and prompts you to upgrade them.
NOTE
If new version files do not exist, the progress closes automatically.
Step 3 In Update Available, click Yes to upgrade the files. Click No to cancel the upgrade. A percentage is displayed in the upgrade progression bar to show the upgrade progression. Step 4 Click Ok. The displayed Update prompt box shows the update progress. Step 5 When you see 100%, click OK. The upgrade is complete. ----End
1 Getting Started
1.15 Managing the Exported Files in the Server

In the File Browser window, you can view the information that are exported from the server according to the path to the exported file.
Procedure
Step 1 Choose Maintenance > File Browser. The File Browser window is displayed. You can view the exported timing tasks in the server in the File Browser window. Step 2 In the File Browser window, view the exported results according to the name of the exported file. ----End
1.16 Managing User-Defined Object Groups

You can group objects of the same type into an object group. In this way, you can perform the same operation on all the objects in this object group. The M2000 allows you to create, view, and modify the information about a user-defined object group. 1.16.1 User-Defined Object Groups You can group objects of the same type into an object group, such as cell group, server group, and RNC group. In this way, you can perform the same operation on all the objects in an object group. This function applies to only commissioning cells. 1.16.2 Adding a User-Defined Object Group You can create a user-defined object group to perform the same operation on all the objects in this object group. This function applies to only commissioning cells. 1.16.3 Modifying a User-Defined Object Group This describes how to modify the name, remarks, and objects of a user-defined object group. 1.16.4 Viewing User-Defined Object Groups This describes how to view and modify the information about the user-defined object groups on the server.
1.16.1 User-Defined Object Groups

You can group objects of the same type into an object group, such as cell group, server group, and RNC group. In this way, you can perform the same operation on all the objects in an object group. This function applies to only commissioning cells. By default, the types of the NEs and object groups that support this function are: MSC Server (MSCServer NE Group, Office Group), and RNC (RNC NE Group, Cell Group). You can add or delete the types of NEs and object groups by modifying the configuration file on the server.
Related Tasks
1.16.2 Adding a User-Defined Object Group 1.16.3 Modifying a User-Defined Object Group 1.16.4 Viewing User-Defined Object Groups
1 Getting Started
Related References
1.17.10 Parameters for User-Defined Object Groups
1.16.2 Adding a User-Defined Object Group

You can create a user-defined object group to perform the same operation on all the objects in this object group. This function applies to only commissioning cells.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized with the relevant operation privileges.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is displayed. Step 2 Click New. Step 3 Select the type of the object group to be created, set the attributes, and then click Next. For detailed information about the parameters, refer to 1.17.10 Parameters for User-Defined Object Groups. Step 4 Select the object scope and create type, and then click Next.
NOTE
If the type of the object group is NE group, the corresponding scope of the object group can only be Network.
Step 5 Perform the related operations based on the selected type. Create Type Operation By Condition 1. Click Add and set the search condition. The logical operator of the search condition in the last line must be none. The logical operators used in other lines cannot be none. 2. Click Search. 3. In the displayed Objects In Scope dialog box, click OK. 4. Click Next and modify the name and remarks of the object group. By Manual 1. In Objects, select the objects to be added to the object group. Click to add them to Selected Objects. 2. Click Next and modify the name and remarks of the object group. AUTO Step 6 Click Finish. Step 7 In the displayed Successful dialog box, click OK. ----End
Select the attribute of the object group in the drop-down list.
1 Getting Started
Related Concepts
Related References
1.16.3 Modifying a User-Defined Object Group

This describes how to modify the name, remarks, and objects of a user-defined object group.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized with the relevant operation privileges. A user-defined object group is available.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is displayed. Step 2 In the navigation tree, select the node of the object group to be modified. In the right pane, select the object group to be modified. Step 3 Click Modify, or right-click the object group and choose Modify on the shortcut menu.
CAUTION
An object group whose create type is AUTO cannot be modified manually. Step 4 Perform the related operations based on the type of the user-defined object group. Create Type Operation By Condition 1. Modify the search conditions in Modify Object Group(Setting conditions) and then click Search. 2. In the displayed Objects In Scope dialog box, click OK. 3. Click Next and modify the name and remarks of the object group. By Manual 1. Select the objects in the object group again. 2. Click Next and modify the name and remarks of the object group.
For detailed information about the parameters, refer to 1.17.10 Parameters for User-Defined Object Groups. Step 5 Click Finish.
1 Getting Started
Step 6 In the displayed dialog box that shows the operation result, click OK. ----End
Related Concepts
Related References
1.16.4 Viewing User-Defined Object Groups

This describes how to view and modify the information about the user-defined object groups on the server.
Prerequisite
l l
You have logged in to the M2000 client. A user-defined object group is available.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is displayed. Step 2 In the navigation tree, select the Network node. In the right pane, view the information about the user-defined object group, such as name, NE type, object group type, scope, creator, and create type.
NOTE
l l
Select a user-defined object group in the right pane and click Information. Then you can view the details of its objects. Select a user-defined object group in the right pane and click Delete to delete it. Alternatively, you can right-click it and choose Delete on the shortcut menu.
----End
Related Concepts
Related References
1.17 Reference for M2000 Client Interfaces

This describes the M2000 client interface and related parameters, which helps you perform the related operations on the client. 1.17.1 Interface Description: M2000 Client Interface
1 Getting Started
This part describes the contents and functions of the M2000 client interface, such as the physical topology, system output window, menu bar, and status bar. Thus you can have a clear understanding of the client and perform corresponding operations. 1.17.2 Interface Description: Common Options for Performance Management The common options for performance management are organization tree, status table, time parameter, and others. 1.17.3 Parameters for Logging In to the M2000 Server This section describes the parameters in the Login dialog box. You can refer to these parameters when you log in to the M2000. 1.17.4 Tool Buttons Tool buttons are displayed as icons on the toolbar. You can perform operations faster through these buttons. 1.17.5 Parameters for Output GUI Information This section describes the parameters in the Output Window group box. You can refer to these parameters when you set output information. 1.17.6 Parameters for Viewing NM License Information This part gives the descriptions of the parameters for the License Information tab. You can view the NM license information by referring to the information below. 1.17.7 Parameters for Setting the Time Style This section describes the parameters in the Time dialog box. You can refer to these parameters when you set the client time style. 1.17.8 Parameters for Setting Common Options for Performance Management Setting common options for performance management involves setting the organization tree, status table, time parameter, and others. 1.17.9 Parameters for the NE Partitioning Information This topic describes the related parameters in the Query NE Subarea dialog box. You can refer to the these parameters when you check the NE partitioning information. 1.17.10 Parameters for User-Defined Object Groups This describes the parameters related to user-defined object groups. You can refer to this part when adding or modifying user-defined object groups.
1.17.1 Interface Description: M2000 Client Interface

This part describes the contents and functions of the M2000 client interface, such as the physical topology, system output window, menu bar, and status bar. Thus you can have a clear understanding of the client and perform corresponding operations.
Overview
Figure 1-2 shows the GUI after you log in to the system. For details of Figure 1-2, see Table 1-1.
1-28
Issue 06 (2008-12-16)
1 Getting Started
Figure 1-2 M2000 client interface
Table 1-1 Parameters Serial Number (1) Name System output window Description The system output window displays the information such as the system operation logs and the system alarms. The time displayed is the time of the client. The log, fault, and security information is provided by the server. Therefore, the displayed time is the time of the server. The menu bar shows the main menu of the system. The status bar displays the current status information of the system, such as the current user and the IP address of the connected server. The toolbar shows the shortcut icons for key operation tasks.
(2) (3)
Menu bar Status bar
(4)
Toolbar
Menu Bar
The menu bar shows the main menu of the system. It is designed according to the main functions of the M2000 to facilitate your operation. Table 1-2 describes the main menus on the interface and corresponding functions.
Issue 06 (2008-12-16)
1-29
1 Getting Started
Table 1-2 Menu bar Main Menu System Description System provides robust system configuration functions. The menu options are System > Customize Topology Tips , System > Proxy Service Setting , System > LMT Prompt Setting, System > Metrology Setting, System > Log Management, System > Preferences, System > Customize Toolbar, System > Broadcast Message, System > Lock Terminal, System > Logout, and System > Exit. You can customize shortcut operations and the operation style. You can also configure the system to your preference before the usage. Monitor provides the function of monitoring and integrated fault management on all NEs in the entire network. . The menu options are Monitor > Current Fault Alarms, Monitor > History Fault Alarms , Monitor > Event Alarms, Monitor > Masked Fault Alarms, Monitor > Masked Event Alarms, Monitor > Performance Monitor, Monitor > Object Groups Management , Monitor > RAN Network Monitor, Monitor > Browse Current Fault Alarms By Status , Monitor > Browse Event Alarms By Status, Monitor > Fault Alarm Statistics, Monitor > Event Alarm Statistics, Monitor > Display Alarm Board, Monitor > Stop Client Sounding, Monitor > Alarm Box Manager, Monitor > Alarm Real-time Monitor, Monitor > NE Alarm Synchronize, Monitor > Settings, and Monitor > System Monitor. Maintenance provides the function of maintaining the system and NEs. The menu options are Maintenance > Follow-up Reports Browser , Maintenance > MML Command, Maintenance > Trigged Script, Maintenance > Task Management, Maintenance > File Browser, Maintenance > Backup Management, Maintenance > Pool Management, Maintenance > Network Health Check, and Maintenance > iSStar. Performance provides the function of measuring and observing the security, running status, signal connection status, and status of users and system resources. The menu options are Performance > Query Result, Performance > Measure Management, Performance > Threshold Management, Performance > User-defined Counter Management, Performance > Monitor Threshold Management , Performance > Object Set Management , and Performance > Preference.
Monitor
Maintenance
Performance
1-30
Issue 06 (2008-12-16)
1 Getting Started
Main Menu Software
Description Software provides the function of integrated management of NE software, configuration data and file. The menu options are Software > Browser, Software > License Management, Software > File Server Setting, Software > File Transfer Wizard, Software > Plan Upgrade Task, Software > NE Upgrade Wizard, Software > FTP Setting, and Software > FTPS Parameters Setting . Configuration provides the function of integrated NE configuration management. The menu options are Configuration > MIT Browser, Configuration > Domain Management, Configuration > Dual Homing, Configuration > Link Browser, Configuration > State Management, Configuration > SNMP Template Management , Configuration > Device Map, Configuration > Query NE SubArea, Configuration > Export NE Attribute Template, Configuration > PCU Integrated Configuration , Configuration > Inventory Management, and Configuration > Core Basic Navigation Configuration. Security provides the function of user and user right management. The menu options are Security > Security Management , Security > NE User Management, Security > NE Login Management,Security > Local Users Setting, Security > User Monitor, Security > Access Control List, Security > Security Policy, and Security > Change Password. Topology provides the function of topology management. The menu options are Topology > Main Topology, Topology > New, Topology > Delete, Topology > Modify Custom View, Topology > Delete Custom View, Topology > Back to Parent, Topology > Back to Top, Topology > Refresh, Topology > Save Position, Topology > Lock View, Topology > Search, Topology > Show, Topology > Layout, Topology > Set Background, and Topology > Zoom. Report provides the functions related to NE reports and performance reports. The menu options are Report > NE Report, Report > NE Resource Report, Report > NE Statistic Report, Report > Link Report Wizard, and Report > Performance Report > Report Management. Custom Menu provides the function of customizing menus, which enables you to directly start the programs other than those for the M2000 on the client. The menu options are Custom Menu > Menu Setting.
Configuration
Security
Topology
Report
Custom Menu
Issue 06 (2008-12-16)
1-31
1 Getting Started
Main Menu Window
Description Window provides the function of setting display mode of the windows. The menu options are Window > Close, Window > Close All, Window > Minimize, Window > Minimize All, Window > Toggle Window Tabbed Bar, Window > Toggle Message Output Area, Window > Cascade, Window > Tile, Window > Tile Horizontally, and Window > Tile Vertically. Help provides the online help of the M2000 client. The menu options are Help > Help Topics, Help > Check For Upgrades, Help > About, and Help > Online Update. The menu is displayed after you install the resource management tool on the client. The M2000 resource management tool provides the function of allocating interprovincial circuit resources of softswitch tandem, thus satisfying the operation and maintenance requirements of carriers. The resource management tool includes Standard Data Management , Real Data Manager and Task Manager .
Help
Resource Management
Toolbar
The toolbar of the M2000 client provides access to some common operations. You can rapidly open the corresponding windows or perform the corresponding operations by clicking the icons. The M2000 also allows you to customize the buttons on the toolbar.
l
System management tool buttons Table 1-3 shows the icons and functions of system management tool buttons. Table 1-3 System management tool buttons Icon Meaning Exit Description You can terminate client programs and exit the current M2000 client. You can log out of the current M2000 client but not terminate client programs. If the client is locked, you are not allowed to perform operations on the client. You must enter the correct password to unlock the client.
Logout
Lock terminal
1-32
Issue 06 (2008-12-16)
1 Getting Started
Icon
Meaning Full screen
Description You can hide the menu bar, toolbar, system output window, and status bar, thus expanding the display area of the main window. You can press Esc to exit the display mode of full screen.
Buttons of the fault management tool Table 1-4 shows the buttons of the fault management tool. Table 1-4 Description of the fault management tool Icon Meaning Current fault alarm query Description Provides the access to the Current Fault Alarms dialog box. Provides the access to the Event Alarms dialog box. Provides the access to the Browse Current Fault Alarms By Status dialog box. Provides the access to the Fault Alarm Statistics dialog box.
Event alarm query
Browse current fault alarms by status
Fault alarm statistics
Buttons of the performance management tool Table 1-5 shows the buttons of performance management tool. Table 1-5 Buttons of the performance management tool Icon Meaning Query result Description Provides the access to the Query Result dialog box, where you can query all the reported measure results after the NE is created.
Issue 06 (2008-12-16)
1-33
1 Getting Started
Icon
Meaning Measure management
Description Provides the access to the Measure Management window, where you can query the measure results, measure status, measure transition status of a measure unit. Provides the access to the Threshold Setting dialog box. Provides the access to the Customer Counter Management window, where you can manage the system counters and user-defined counters.
Threshold setting
Customer counter management
Buttons of the software management tool Table 1-6 shows the buttons of software management tool. Table 1-6 Descriptions of software management tool buttons Icon Meaning Software browser Description Provides the access to the Software Browser pane, where you can centralize the software management, configuration data, and files of NEs.
Configuration management tool buttons Table 1-7 shows the icons and functions of configuration management tool buttons. Table 1-7 Descriptions of the configuration management tool buttons Icon Meaning MIT browser Description Provides the access to the MIT Browser, where you can browser the basic information of NEs.
1-34
Issue 06 (2008-12-16)
1 Getting Started
Icon
Meaning MML command
Description Provides the access to the MML Command window, where you can operate and maintain NEs through delivering MML commands to NEs. Provides the access to the Follow-up Reports Browser window, where you an view the reports returned from NEs.
Follow-up reports browser
Buttons of the integrated task management tool Table 1-8 shows the buttons of integrated task management tool. Table 1-8 Descriptions of integrated task management tool buttons Icon Meaning RAN Network Monitor Description Provides the access to the RAN Network Monitor pane, where you can monitor the RNC, the NodeB, and the cell in an integrated manner.
Status Bar
The status bar is located at the bottom of the interface. It displays the status information of the system, such as the current user and the IP address of the connected server. The status information is updated in real time. From left to right on the status bar are:
l l l l
Coordinates: displays the longitude and latitude of the current location. Login server: displays the IP address of the server that the client logs in to. Login user: displays the name of the current login user. Login mode: displays the login mode of the current user. Two modes are available: singleuser mode and multi-user mode. Connection status: displays the status of the connection to the server. When the server is disconnected, the indicator blinks and the system displays a prompt box showing that the server being connected. shows the indicator. Logo: the logo of Huawei Technologies Co., Ltd., that is, .
System Output Window

The system output window resides at the bottom of the client. It displays the prompts and messages that are associated with the operation of the M2000 or other clients.
1 Getting Started
The system output includes:

l l l l l
Prompt for the initialization of the system at the login Prompt for the start of log export Prompt for the end of log export Prompt for the start of alarm data export Prompt for the end of alarm data export
1.17.2 Interface Description: Common Options for Performance Management

The common options for performance management are organization tree, status table, time parameter, and others.
Organization Tree
Figure 1-3 shows the tab of organization tree. Figure 1-3 Organization tree
Status Table
Figure 1-4 shows the tab of status table.
1 Getting Started
Figure 1-4 Status table
Time Parameter
Figure 1-5 shows the tab of time parameter.
Issue 06 (2008-12-16)
1-37
1 Getting Started
Figure 1-5 Time parameter
Others
Figure 1-6 shows the tab of others.
1-38
Issue 06 (2008-12-16)
1 Getting Started
Figure 1-6 Others
Related Tasks
1.17.3 Parameters for Logging In to the M2000 Server

This section describes the parameters in the Login dialog box. You can refer to these parameters when you log in to the M2000.
Parameters
Name User Name Description Description: The valid user name registered in the M2000 server. Settings Value: Cannot be null.
Issue 06 (2008-12-16)
1-39
1 Getting Started
Name Password
Description Description: Used to log in to the M2000 server, displayed as *.
Settings Value:
l
When using the default password policy, the user password cannot be less than six characters. For the description of the password policy parameters, see 4.3.1.1 Setting the Password Policy. The password of admin cannot be less than eight characters.
Server
Description: Select the M2000 server you want to log in from the drop-down list. Click the small button on the right, and then the Server List dialog box is displayed.
Value: Cannot be null.
Related Tasks
1.1.1 Logging In to theM2000 Server
1.17.4 Tool Buttons

Tool buttons are displayed as icons on the toolbar. You can perform operations faster through these buttons.
System Tool Buttons

Icon Name Exit Description Description: To exit the M2000. Logout Description: To log out the current user. Lock Terminal Description: To lock the Terminal. When the client is locked, you cannot do any operations on the client, and you need to enter your password to unlock the client.
1-40
Issue 06 (2008-12-16)
1 Getting Started
Icon
Name Full Screen
Description Description: By using this icon, the menu bar, toolbar, output window, and status bar can be hidden, thus the main window can have more space. Press Esc to exit the full screen mode.
Topology Tool Buttons

Icon Name Zoom In Description Description: To zoom in on the topology objects. You can click this icon eight times effectively based on the default object size. Zoom Out Description: To zoom out on the topology objects. You can click this icon eight times effectively based on the default object size. Magnifier Description: To magnify the topology objects in the selected rectangle area to adjust the view to the perfect size. You can zoom in four times based on the default size. Reset Zoom Description: To restore the topology objects to the default size. You can zoom out four times based on the default size.
Issue 06 (2008-12-16)
1-41
1 Getting Started
Icon
Name Fit to Contents
Description Description: To display all the topology objects of the current topology view in the same topology window. When the button is clicked, the size of the topology elements may change, but their shapes and positions in the coordinates remain the same.
Print
Description: To set the print properties to print the topology view.
Preview
Description: To preview the print result of the topology view. You can also print by using this icon.
Overview
Description: To display the overview. You can have a full view of the topology structure through the overview.
Search
Description: To search topology objects. It supports the wildcard character *, and the characters entered for the search must be less than 65 characters, and cannot be less than 0.
Refresh
Description: To refresh the topology view, and obtain the latest data from the M2000 server.
Save Positions
Description: To save the icon position. When you open the view next time, the topology view displays this position.
Legend/Filter/Attribute
Description: The Legend/Filter/Attribute pane is displayed on the right.
1-42
Issue 06 (2008-12-16)
1 Getting Started
Fault Tool Buttons

Icon Name Current Fault Alarms Description Description: The shortcut icon to query current fault alarms. Event Alarms Description: The shortcut icon to query event alarms. Browse Current Fault Alarms By Status Description: The shortcut icon to display current fault alarms by status. Description: The shortcut icon to statistics fault alarms.
Statistics Fault
Related Tasks
1.4.3 Setting the Toolbar
1.17.5 Parameters for Output GUI Information

This section describes the parameters in the Output Window group box. You can refer to these parameters when you set output information.
Parameters
Name Maximum Output Lines Description Description: The maximum lines that can be displayed in the output window. If the lines of output information exceed the maximum lines, the earliest input lines are deleted automatically and the maximum lines are displayed. Description: If you select this option and there is new output information, the output window scrolls to the new information automatically. If you deselect this option, you can only scroll to the new information manually. Settings Value: Value range: 30-3000
Automatically scroll to the new message
Setting method: Check box
Issue 06 (2008-12-16)
1-43
1 Getting Started
Name Automatic dump
Description Description: If you select this option, the output information is dumped to a file according to the preset conditions. Description: Dump lines of output information. The value cannot exceed the value set in Maximum Output Lines. If the value exceeds the preset maximum value, the output information is dumped to the corresponding file automatically, and the dump lines are the same as that set in Dump Lines.
Settings Setting method: Check box
Dump Lines
Value: Value range: 20-300
Dump File Name
Description: The dump path and dump file name of output information. The files must be saved in TXT format.
Setting method: Cannot be null.
Related Tasks
1.4.1 Setting Output Information
1.17.6 Parameters for Viewing NM License Information

This part gives the descriptions of the parameters for the License Information tab. You can view the NM license information by referring to the information below.
Parameters
Parameter License key Message Description Name of the License key. For the resource keys, the number of the authorized resources are displayed. For the function keys, the function is authorized if the value true is displayed.
Related Tasks
1.12 Viewing NM License Information
1.17.7 Parameters for Setting the Time Style

This section describes the parameters in the Time dialog box. You can refer to these parameters when you set the client time style.
1-44
Issue 06 (2008-12-16)
1 Getting Started
Parameters
Name Morning Indicator Description Description: Morning indicator. Settings Setting method: The default is AM. Cannot be modified on the client. Afternoon Indicator Description: Afternoon indicator. Setting method: The default is PM. Cannot be modified on the client. Time Separator Description: The sign to separate the time. Setting method: The default is :. Cannot be modified on the client. Time Format Description: HH:mm:ss: HH means 24-hour format, and the morning and afternoon indicators are not displayed. hh:mm:ss tt: hh means 12-hour format. tt is the suffix of morning or afternoon indicator. Show time zone offset Description: If you select the check box, the time zone is displayed next to the time. Setting method: Check box. Example: For example, 15:10:20 +08:00. Show daylight saving time (DST) Description: If you select the check box, the DST is displayed next to the time. Setting method: Check box. Example: For example, 15:10:20 DST. Setting method: The default is HH:mm:ss.
NOTE
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC, and MRF do not support multi-zone management and the DST.
Related Tasks
1.4.5.1 Setting the Time Format of the Client
1.17.8 Parameters for Setting Common Options for Performance Management

Setting common options for performance management involves setting the organization tree, status table, time parameter, and others.
Issue 06 (2008-12-16)
1-45
1 Getting Started
Parameter Description
Parameter Orga nizat ion tree Organization Value Object type, Function subset Description In the organization style of the object type, right-click an object type in the organization tree and choose View the Function Subset. In this situation, the organization tree are organized by function subsets and only the function subsets of the object type are displayed. In the organization style of the function subset, right-click function subsets in the organization tree and choose Filter with Object Type,In this situation, only the function subsets that map the object type are displayed. After you deselect the options, all the function subsets are displayed. Default type of NE on which you will perform operations related to performance management. Measurement status table displays the measurement statuses you have selected. Display style of the measurement status table. Includes integrity query, specific query, missing result, and synchronize result. Defaults from 00:00 to 23:59. -
Switchable Expansion Default NE type Statu s table Default status
Yes, No Expand, Collapse -
All, Set, Measuring, Error, Suspended, Not set Expand, Collapse Integers from 1 to 336 5 minutes, 15 minutes, 30 minutes, 60 minutes, 24 hours All, Set
Default style Time para mete r Default time range Result segment Default measurement period Othe rs Background color Measurement export item
Background color of result table and monitoring chart. Select All to export all measurement settings of the selected nodes. Select Set to export the information of objects or counters you have set.
1-46
Issue 06 (2008-12-16)
1 Getting Started
Parameter Searching Item
Value Counter, NE&Object, Organization tree
Description Select the items to show search box for organization tree, NE and object, or counter in the correspond fields of the Measure Management window. Fuzzy search is supported.
Related Tasks
1.17.9 Parameters for the NE Partitioning Information

This topic describes the related parameters in the Query NE Subarea dialog box. You can refer to the these parameters when you check the NE partitioning information.
Parameter Query Condition NE Subarea Description Host Name of the NE Partitioning When you query the specific partitioning information, you can select names of all partitions or the name of a specific partition from the dropdown list. indicates the NE Name. indicates the serial number of the NE. indicates the NE Name. indicates the version of the NE. indicates the usable capacity available. indicates the partitioning information about the NE,including the host name, the IP address, and the instance name of the database.
Ne Name Query Result No. NE Name NE Version Capability Statistic
Related Tasks
1.13 Viewing NE Partitioning

This describes the parameters related to user-defined object groups. You can refer to this part when adding or modifying user-defined object groups.
Issue 06 (2008-12-16)
1-47
1 Getting Started
Parameter Object Group Type Description Type of an object group The default types are: Office Group and RNC NE Group for the MSC Server, Cell Group for the RNC, and MSCServer NE Group.
NOTE You can add or delete object group types by modifying the configuration file on the server.
Select Attribute
Attribute
Logical attribute of an object, such as commissioning cell and VIP cell. Logical attributes are defined by the configuration file on the server. You can add or delete attributes by modifying the configuration file. Logical attribute value of an object Logical attribute values are defined by the configuration file on the server. You can add or delete attribute values by modifying the configuration file. Indicates that the objects are selected from the entire network Indicates that the objects are selected among the specified NEs Indicates that objects are selected from the created object groups A method for adding objects to a group. You can set search conditions to group the objects that meet the conditions. A method for adding objects to an object group. You need to manually add objects to an object group. A method for adding objects to an object group. Based on the selected object attribute, the system groups the objects that have the same value into a group. Attribute of an object, such as office name and office ID. Object attributes are defined by the configuration file on the server. You can add or delete object attributes by modifying the configuration file.
Attribute Value
Object Group Scope
Network NE NE Group
Create Type
By Condition
By Manual
AUTO
Setting conditions
Attribute
1-48
Issue 06 (2008-12-16)
1 Getting Started
Parameter Operation
Description Used to compare object attribute values, such as =, >, <, >=, <=, and ! =. Value of an object attribute Object attribute values are defined by the configuration file on the server. You can add or delete object attribute values by modifying the configuration file. Used to set the relations between search conditions, such as and, or, and none.
NOTE The logical operator of the search condition in the last line must be none. The logical oprators used in the other lines cannot be none.
Expression
Logic
Objects Selected Objects Attribute for the Object Group
Objects that can be added to an object group Objects that are added to an object group Attribute of an object attribute, such as office ID Object attributes are defined by the configuration file on the server. You can add or delete object attributes by modifying the configuration file. Name of an object group A maximum of 250 characters are allowed. You enter English letters, numbers, and special characters excluding ` ! @ $ # % ^ & * | ' \ " / = . ?.
Object Group Name
Remark
Remark for an object group A maximum of 250 characters are allowed.
Related Concepts
Related Tasks
1.16.2 Adding a User-Defined Object Group 1.16.3 Modifying a User-Defined Object Group 1.16.4 Viewing User-Defined Object Groups
Issue 06 (2008-12-16)
1-49
2 Network Monitoring
2
About This Chapter
Network Monitoring
On the M2000 client, you can monitor the alarms on the network, real-time NE performances, the RAN network, and operational status of the NM system. In this way, you can detect network faults in time and then perform the related operations. 2.1 Basic Knowledge of Monitoring To monitor the alarms, you need to familiarize yourself with certain knowledge, such as alarm severity, alarm status, and alarm report procedure. This helps you to better monitor the alarms generated on the network. 2.2 Monitoring Network Alarms In the M2000, you can monitor the network alarm through topology diagram, alarm board, alarm query, alarm statistics and so on. 2.3 Setting Alarm Auto Processing You can set an auto processing rules, and then the M2000 processes the alarms that match the preset conditions. This helps to improve the work efficiency. 2.4 Setting NE Alarms The M2000 provides the function of alarm shielding and alarm severity redefinition. You can shield unwanted alarms to prevent NEs from reporting them to the M2000. You can also redefine the severity of alarms to make the severity correctly reflect the actual situation. 2.5 Monitoring NE Performance in Real Time You can monitor in real time the specified object types and instances. In addition, you can display the monitoring results in data tables and figures. You can set filter conditions and display effects for the results. Then you save the results and figures to a file. 2.6 Integrated Network Monitoring The M2000 provides integrated network monitoring of the RNC, NodeB, and cells. This function includes managing object groups, monitoring network services, and managing real-time monitoring. Among these three functions, real-time monitoring is the most important. 2.7 NM System Monitoring The M2000 network element management system is the uniform management platform of the Huawei mobile network. It uniformly manages the mobile network elements manufactured by Huawei. On the M2000 client, you can monitor the operational status of the NM system, such
as the status information about the memory, CPU, hard disks, database, processes, and services. In addition, you can set the alarm threshold of the server. 2.8 Reference for Network Monitoring Interfaces This describes the parameters used on the network monitoring interface, such as alarm monitoring, performance monitoring, RAN network monitoring, and NM system monitoring.
2-2
Issue 06 (2008-12-16)
2.1 Basic Knowledge of Monitoring

To monitor the alarms, you need to familiarize yourself with certain knowledge, such as alarm severity, alarm status, and alarm report procedure. This helps you to better monitor the alarms generated on the network. 2.1.1 Alarm Management Alarm management involves alarm display and statistics, audio and visual alarm notification, alarm acknowledgement and synchronization. 2.1.2 Alarm Levels The M2000 defines the alarm to be four levels according to the severity of the alarm. You can adopt corresponding processing strategy for different alarm levels and redefine the alarm levels. 2.1.3 Alarm Status The M2000 divides the alarm into different states according to whether the alarm is confirmed or cleared. You can adopt corresponding processing measures for alarms of different states. 2.1.4 Fault Alarms and Event Alarms In the M2000, the alarm is classified into the fault alarm and event alarm according to the effect of the alarm to the system. 2.1.5 Alarm Types Based on deferent alarms resources, alarms can be classified into 11 types such as power system alarm and environment system alarm. 2.1.6 Alarm Reporting Procedure It describes the process from generating the fault to receiving the alarm notification by the user. 2.1.7 Alarm Auto-Triggering Script The repeat operations of the daily routine maintenance can be defined as an alarm auto-triggering script, which enables the M2000 server to execute the triggered script when the alarm meets the requirements of the triggering setting. The alarm auto-triggering script also enables the automation of the daily routine maintenance and improves the work efficiency.
2.1.1 Alarm Management

Alarm management involves alarm display and statistics, audio and visual alarm notification, alarm acknowledgement and synchronization.
Alarm Display and Statistics

The M2000 receives the NEs alarms in real time. It provides various methods of alarm display and statistics.
l
Alarm display Alarm display involves alarm board output and alarm query.
Alarm board output The alarm board collects statistics on the alarms of the managed objects by alarm levels and states with templates. Working as the monitoring panel, it provides the fault status of the entire system. For the description of the alarm board, see 2.3.2.2 Introduction to the Alarm Board.
Issue 06 (2008-12-16)
2-3
Alarm query Alarm query is to query the current fault alarms, history fault alarms, event alarms, filtered fault alarms, and filtered event alarms. The M2000 can display fault alarms and event alarms in a window by different alarm status.
Alarm statistics The M2000 can collect statistics on fault alarms and event alarms according to the preset statistical conditions. The statistical conditions include alarm name, alarm level, alarm type, alarm raised time, and alarm status, and can be combinations of these items.
Audio and Visual Alarm Notification

The M2000 provides two means of alarm notification: the alarm box and the audio adapter.
l
Alarm Box The M2000 uses the general alarm box of Huawei Technologies Co., Ltd. to provide audio and visual alarm notification. You can set the filter conditions for the alarms that are sent to the alarm box.
Audio Adapter You can set different audio files for the alarms of different levels on the M2000 client. When an alarm is reported, the M2000 client where the audio adapter and sound box are installed plays corresponding sound to notify users. When the M2000 receives a new alarm, it notifies users of the alarm arrival by the speaker. You can set different audio files for different levels of alarms.
Alarm Acknowledgement
The M2000 supports manual and automatic acknowledgement of alarms.
Alarm Synchronization
The M2000 supports alarm synchronization with NEs. Through a client, you can manually synchronize the alarms between the M2000 and an NE.
Alarm Redefinition
You can change the alarm levels displayed on the client and highlight the required alarms by redefinition. The M2000 supports the level redefinition of the alarms on the NEs. You can reset an alarm level by alarm name.
Alarm Correlation Analysis

Alarm correlation analysis aims to set the correlation rules for the M2000 to analyze various alarms completely and automatically. The M2000 then shields the non-root alarms and finds the root alarms so that the maintenance personnel can locate and remove the faults efficiently. The M2000 supports alarm correlation analysis. It also supports correlation analysis between multiple NEs.
2-4
Issue 06 (2008-12-16)
Alarm Explanation and Maintenance Experience

The alarm explanation database introduces the alarm details. You cannot edit the information, and you can only query it. You can record the maintenance experience in the alarm experience database. When a similar fault occurs, you can refer to the experience to handle it.
Alarm Remote Notification

Remote notification provides methods to notify remote maintenance personnel of alarms. At present, the methods of email and short message service(SMS) are supported.
Alarm Auto-Triggering Script

After you specify the script to be triggered and set conditions for the triggering, and when the alarm meets the requirements of the triggering conditions, the server automatically triggers the execution of the shell script file set by the user. Partial automation for the daily routine maintenance work is realized. You can also set the repeated operations of the daily routine maintenance to an alarm auto-triggering script.
2.1.2 Alarm Levels

The M2000 defines the alarm to be four levels according to the severity of the alarm. You can adopt corresponding processing strategy for different alarm levels and redefine the alarm levels.
Alarm Levels
The alarm levels are described as follows:
l
Critical The device or resource may be no longer available. The fault must be removed immediately. Major The Quality of Service(QoS) of the device or resource decreases greatly. Proper measures must be taken to recover the service.
Minor The QoS of the device or resource decreases slightly. Proper measures must be taken or further observation need to be done to avoid more severe faults.
Warning The QoS of the device or resource may be affected. Proper measures must be taken.
Alarm Level Redefinition

Different handling policies apply to different levels of alarms. The M2000 supports alarm level redefinition. You can change the level of an alarm according to the actual requirements. For example, NE Z generates a lot of critical alarms M during upgrade. If it is determined that alarm M is not critical, you can change the alarm level of M to warning.
2.1.3 Alarm Status

The M2000 divides the alarm into different states according to whether the alarm is confirmed or cleared. You can adopt corresponding processing measures for alarms of different states.
1.
Alarm status
l l
The status of an event alarm involves: unacknowledged and acknowledged. The status of a fault alarm involves: unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared, and acknowledged and cleared.
2.
Condition for changing alarm status A certain condition triggers the change of the alarm status.
l
Clear an alarm When the condition that causes a fault alarm is removed, the device recovers to its normal state, the device reports a cleared alarm to the M2000. The source alarm are cleared. You can also clear an alarm manually.
Acknowledge an alarm If an alarm is acknowledged, it is processed. You can unacknowledge an acknowledged alarm.
3.
Alarm status conversion Figure 2-1 shows the model of the fault alarm status conversion. Figure 2-1 Model of the fault Alarm status conversion
NOTE
The acknowledged and cleared alarms are history alarms. The fault alarms in other status are current alarms. That is, the unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared fault alarms are current alarms.
2.1.4 Fault Alarms and Event Alarms

In the M2000, the alarm is classified into the fault alarm and event alarm according to the effect of the alarm to the system. Table 2-1 lists the differences between fault alarms and event alarms.
2-6
Issue 06 (2008-12-16)
Table 2-1 Differences between fault alarms and event alarms Alarm Category Fault alarm Definition A notification that the system provides when it detects a fault. Related Concept A fault is a physical or logical factor that causes the system to fail. For example, Central Processing Unit(CPU) busy, hard disk failure, or network cable disconnectio n. An event is a situation of the managed object. For example, succeeded in periodic export of operation logs. Events occur all the time. They have no negative impacts on the system. Cannot be cleared, but can be acknowledge d and unacknowle dged. You do not have to handle the event. Impact The system probably cannot work properly. Handling Can be cleared. Recommen dation Clear the alarm to restore the system to normal.
Event alarm
A notification that the system provides when it detects an event.
Table 2-2 gives two examples to help you understand the differences between fault alarms and event alarms. Table 2-2 Examples Alarm Name ALM-040 Device serial numbers mismatch Alarm Category Fault alarm Cause The system detects a fault: The MAC address (device serial number) of the network adapter does not match the device serial number of license. Impact Some functions are disabled. The system cannot work properly. Recommenda tion Handle the alarm. For example, apply for a new license file according to the MAC address of the new network adapter.
Issue 06 (2008-12-16)
2-7
Alarm Name ALM-016 Overflow export of operation logs succeeded
Alarm Category Event alarm
Cause The system detects an event: Exporting the overflowed operation logs succeeded.
Impact None.
Recommenda tion You do not have to handle the alarm.
2.1.5 Alarm Types

Based on deferent alarms resources, alarms can be classified into 11 types such as power system alarm and environment system alarm. Table 2-3 shows the 11 types of alarm. Table 2-3 Complete procedure for creating a user Name Power system alarm Environment system alarm Description A power system alarm is raised by the power supply. An environment system alarm is an alarm about the environment of the equipment room, such as the temperature, humidity, or gate. A signaling system alarm is an alarm about the signaling system, such as No. 7 signaling. A trunk system alarm is an alarm about the trunk system, such as E1, STM-1 optical or electrical relay. A hardware system alarm is an alarm about a board device, such as clock or CPU. A software system alarm is an alarm about the software. A running system alarm is an alarm about the M2000 running. A communication system alarm is an alarm about the communication system. A QoS alarm is an alarm about the QoS. Processing error alarms are alarms about other exceptions that are not described here. An internal alarm is raised by the M2000. Except such alarms, other types of alarms are all external alarms reported by the devices.
Signaling system alarm Trunk system alarm Hardware system alarm Software alarm Running system alarm Communication system alarm QoS alarm Processing error alarm Internal alarm
2-8
Issue 06 (2008-12-16)
2.1.6 Alarm Reporting Procedure

It describes the process from generating the fault to receiving the alarm notification by the user.
Flow Chart
Figure 2-2 shows the alarm reporting procedure. Figure 2-2 Alarm reporting procedure
Flow Description
The following is the description of the flow in Figure 2-2. 1. Reporting a alarm When a device raises an alarm, it sends the alarm to the M2000 by the Man-Machine Language(MML) protocol or Simple Network Management Protocol(SNMP). 2. Masking alarms The M2000 masks alarms based on the mask condition set by users. The alarms that match the condition are masked. 3. 4. Redefining the alarm level The M2000 redefines the alarm levels based on the redefinition conditions set by users. Analyzing alarm correlation The M2000 analyzes the alarm correlation based on the correlation rule and shield the repetitive or non-root alarms. 5. 6.
Issue 06 (2008-12-16)
Saving alarms After processing, the M2000 writes the alarms into the alarm database. Notifying the user of alarms
The M2000 sends the alarm notifications to users based on the alarm notification rules set by users.
2.1.7 Alarm Auto-Triggering Script

The repeat operations of the daily routine maintenance can be defined as an alarm auto-triggering script, which enables the M2000 server to execute the triggered script when the alarm meets the requirements of the triggering setting. The alarm auto-triggering script also enables the automation of the daily routine maintenance and improves the work efficiency. The alarm auto-triggering script is a kind of the shell script, and thus is provided by the user. Correct script files are also guaranteed by the user. The M2000 does not provide functions such as editing and proofreading for the script files.
NOTE
shell script: indicates the program that is edited using the programing language UNIX shell. The shell script can be used to execute the complicated tasks, which cannot be executed using the command of the UNIX system itself.
2.2 Monitoring Network Alarms

In the M2000, you can monitor the network alarm through topology diagram, alarm board, alarm query, alarm statistics and so on. 2.2.1 Setting Columns in an Alarm Interface You can modify the alarm information and show some necessary columns as required. In addition, you can decide the columns to be shown, and adjust the sequence of the shown columns. 2.2.2 Manually Synchronizing NE Alarms To ensure that the M2000 fault alarms are consistent with the device fault alarms, you can manually synchronize the NE alarms to reflect the current running status of the device. 2.2.3 Locating Alarms When you browse alarms in the topology view or browse/query alarms in the alarm browse window, you can use the alarm topology locating function to locate the NE that raises the alarm by the alarm record. 2.2.4 Manually Clearing an Alarm The M2000 helps to clear a certain fault alarm manually. You can manually clear the alarms that cannot be recovered automatically or that are confirmed to be cleared. After rectifying the faults, the system considers that the faulty function is recovered. 2.2.5 Monitoring Alarms Through the Topology View You can choose to display the alarm list area under the topology view to monitor the alarm situation of the NEs in real-time. 2.2.6 Setting Alarm Real-Time Monitoring You can set alarm monitoring conditions to monitor the alarms that meet the conditions in real time. 2.2.7 Querying Alarms In the M2000, you can set the frequently used query conditions as an alarm query template, so that you can query the alarms with the same conditions. You can also set query conditions to query the current fault alarms, history fault alarms, event alarms, and masked alarms. 2.2.8 Collecting Alarm Statistics
By collecting alarm statistics, you can know the fault status of the network and obtain relevant data to remove faults and improve the network. You can set a query template based on the frequently used statistical conditions for future use. 2.2.9 Saving Alarm Data When querying or collecting statistics of alarms, you can save the alarm data to files. 2.2.10 Printing Alarm Data This task is performed to print the results of alarm query or alarm statistics. 2.2.11 Handling Alarms When you find an alarm, you need to take actions to handle it. The procedure of handling an alarm consists of viewing alarm details, acknowledging, locating, and clearing the alarm. 2.2.12 Setting the Displaying Location for a New Alarm Through this operation, you can set the new fault/event alarm to display the front or back of the alarm list, in order to view the newly reported alarm.
2.2.1 Setting Columns in an Alarm Interface

You can modify the alarm information and show some necessary columns as required. In addition, you can decide the columns to be shown, and adjust the sequence of the shown columns.
Context
You can make this settings in the following windows:
l l l l l l l
Current Fault Alarms Event Alarms Masked Fault Alarms Masked Event Alarms History Fault Alarms Browse Current Fault Alarms by Status Browse Current Event Alarms by Status
Procedure
Step 1 Open the 2.2.7 Querying Alarms window. Step 2 Right-click one alarm and select Configure Columns. The Configure Columns dialog box is displayed. Available column and Selected column respectively list all the available and selected columns. Step 3 Click an icon and perform the corresponding operation as show in the table below. Icon Description Add the selected column Remove the selected column
Issue 06 (2008-12-16)
2-11
Icon
Description Add all selected columns Remove all selected columns
Step 4 In Selected column, select a column and then click Up or Down to adjust the display sequence. Step 5 Choose Effective for the current window and new window of the same type or Effective for the current pane only. Optional Box Effective for the current window and new windows of the same type Effective for the current pane only Step 6 Click OK. The settings take effect. ----End Description This setting is effective for the alarm windows of the same type. This setting is effective only for the current alarm window.
Related References
2.8.10 Parameters for Setting Columns in an Alarm Interface
2.2.2 Manually Synchronizing NE Alarms

To ensure that the M2000 fault alarms are consistent with the device fault alarms, you can manually synchronize the NE alarms to reflect the current running status of the device.
Prerequisite
l l
You have logged in to the M2000 client. Uncleared fault alarms exist.
Context
The M2000 supports automatic alarm synchronization.
Procedure
Step 1 In the result window after you open 2.2.7.1 Querying Current Fault Alarms or 2.2.7.6 Displaying Fault Alarms by Status, right-click the fault alarms to be synchronized. Step 2 From the shortcut menu, select Synchronize. ----End
Related References
2.8.15 Parameters for Selecting Alarm Objects
2.2.3 Locating Alarms

When you browse alarms in the topology view or browse/query alarms in the alarm browse window, you can use the alarm topology locating function to locate the NE that raises the alarm by the alarm record.
Context
The topology location is applicable to only one alarm. If multiple alarms are chosen, even if they are raised by the same network element, the Topology Location item is disabled.
Procedure
l In the window for browsing the alarm query or statistical result, right-click an alarm record and choose Topology Location. The cursor is located to the NE that raises the alarm. l In the lower window of the topology view, right-click an alarm and choose Topology Location . The cursor is located to the NE that raises the alarm. ----End
2.2.4 Manually Clearing an Alarm

The M2000 helps to clear a certain fault alarm manually. You can manually clear the alarms that cannot be recovered automatically or that are confirmed to be cleared. After rectifying the faults, the system considers that the faulty function is recovered.
Context
A cleared alarm exists with a fault alarm. When a device is faulty, a fault alarm is reported to the M2000 server. After the fault is rectified, the cleared alarm is sent to the M2000 server, notifying that the alarm is cleared. After a fault alarm is acknowledged and cleared, it becomes a history alarm. The system dumps the alarm in the history fault alarm database for future reference.
Procedure
Step 1 In the 2.2.7.1 Querying Current Fault Alarms or 2.2.7.6 Displaying Fault Alarms by Status window, right-click the alarm to be cleared. A cleared alarm cannot be cleared again. Step 2 Select Clear from the from the shortcut menu. Change the state of the alarm to cleared. ----End
2.2.5 Monitoring Alarms Through the Topology View

You can choose to display the alarm list area under the topology view to monitor the alarm situation of the NEs in real-time.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the Main Topology window, click
NOTE
on the toolbar.
Click
again, the alarm browse window is hidden.
All the NE alarms are displayed in the alarm browse window below the topology view. Step 3 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. ----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
2.2.6 Setting Alarm Real-Time Monitoring

You can set alarm monitoring conditions to monitor the alarms that meet the conditions in real time.
Context
The M2000 monitors all the alarms by default.
Procedure
Step 1 Choose Monitor > Alarm Real-time Monitor. Step 2 In the Alarm Real-time Monitor window, click Step 3 In the Filter dialog box, set alarm filtering conditions. 1. 2. Click the Base Setting tab. Set the Acknowledgement and Clearance. Click the Alarm Source tab. Set the alarm sources. .
Step 4 Click OK. Step 5 Optional: Click Refresh. Monitor the alarms that are newly reported in real time. ----End
Related References
2.8.11 Parameters for Monitoring Alarms in Real Time
2.2.7 Querying Alarms

In the M2000, you can set the frequently used query conditions as an alarm query template, so that you can query the alarms with the same conditions. You can also set query conditions to query the current fault alarms, history fault alarms, event alarms, and masked alarms.
2.2.7.1 Querying Current Fault Alarms You can find the specific fault alarms quickly by setting the fault alarm query conditions. 2.2.7.2 Querying History Fault Alarms You can find the specific history fault alarms quickly by setting the query conditions for history fault alarms. 2.2.7.3 Querying Event Alarms You can find the specific event alarms quickly by setting the event alarm query conditions. 2.2.7.4 Querying the Masked Fault Alarms You can find the masked fault alarms quickly by setting the query conditions for masked fault alarms. 2.2.7.5 Querying the Masked Event Alarms You can find the masked event alarms quickly by setting the query conditions for masked event alarms. 2.2.7.6 Displaying Fault Alarms by Status By this task, you can view the fault alarms of different status in a window. 2.2.7.7 Displaying Event Alarms by Status By this task, you can view the event alarms of different status in a window. 2.2.7.8 Setting an Alarm Query Template You can save the frequently used query conditions as templates for future use.
Related References
2.8.12 Parameters for Setting Alarm Query/Browse 2.8.14 Parameters for Selecting NE for Query
Querying Current Fault Alarms

You can find the specific fault alarms quickly by setting the fault alarm query conditions.
Procedure
Step 1 Choose Monitor > Current Fault Alarms, or click Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Click Save As to save the query result in a file.
NOTE
on the toolbar.
The format of the file can be *.txt, *.html, or *.csv. The default is *.csv.
Step 5 Optional: Click Print. In the Print dialog box, set the print parameters and then click Print. Step 6 Optional: Select Auto Refresh in the fault browse window. The alarms in the fault browse window are refreshed in real time. You can browse the latest alarms.
NOTE
After select Auto Refresh, the alarms are refreshed in real time, and the Refresh button is disabled. After you clear Auto Refresh, the Refresh button is enabled, and you can click Refresh to refresh alarms manually.
Step 7 Optional: Right-click an alarm in the browse window and choose Synchronize. The alarm data on the M2000 keep consistent with that on the NE. Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 9 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 10 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 11 Optional: Choose one or more alarms in the browse window, right-click and then choose Send Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail address or SMS number. Click OK.
NOTE
l l
You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled. In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000 server.
Step 12 Optional: Right-click an alarm in the browse window and choose Topology Location . The cursor is located to the NE that raises the alarm. Step 13 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. Step 14 Optional: Right-click an alarm in the browse window and choose Masked Alarm . l l In the displayed dialog box, you can click Previous to view the masked alarm of the previous alarm. In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm. ----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse 2.8.15 Parameters for Selecting Alarm Objects 2.8.16 Parameters for Selecting Alarm Name
2-16
Issue 06 (2008-12-16)
Querying History Fault Alarms

You can find the specific history fault alarms quickly by setting the query conditions for history fault alarms.
Procedure
Step 1 Choose Monitor > History Fault Alarms . Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 7 Optional: Right-click an alarm in the browse window and choose Topology Location . The cursor is located to the NE that raises the alarm. Step 8 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. Step 9 Optional: Right-click an alarm in the browse window and choose Masked Alarm . l l In the displayed dialog box, you can click Previous to view the masked alarm of the previous alarm. In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
Related References
Querying Event Alarms

You can find the specific event alarms quickly by setting the event alarm query conditions.
Procedure
Step 1 Choose Monitor > Event Alarms, or click on the toolbar.
Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Click Save As to save the query result in a file.
NOTE
NOTE
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 9 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 10 Optional: Choose one or more alarms in the browse window, right-click and then choose Send Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail address or SMS number. Click OK.
NOTE
l l
Step 11 Optional: Right-click an alarm in the browse window and choose Topology Location . The cursor is located to the NE that raises the alarm. Step 12 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. Step 13 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l l
In the displayed dialog box, you can click Previous to view the masked alarm of the previous alarm. In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
Related References
2.8.12 Parameters for Setting Alarm Query/Browse 2.8.15 Parameters for Selecting Alarm Objects
Querying the Masked Fault Alarms

You can find the masked fault alarms quickly by setting the query conditions for masked fault alarms.
Context
The masked alarm is the alarm that is masked by the alarm correlation rules. It includes masked fault alarms and masked event alarms.
Procedure
Step 1 Choose Monitor > Masked Fault Alarms. Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Click Save As to save the query result in a file.
NOTE
Step 5 Optional: Click Print. In the Print dialog box, set the print parameters and then click Print. Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 9 Optional: Right-click an alarm in the browse window and choose Topology Location . The cursor is located to the NE that raises the alarm.
Step 10 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. Step 11 Optional: Right-click an alarm in the browse window and choose Masked Alarm . l l In the displayed dialog box, you can click Previous to view the masked alarm of the previous alarm. In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
Related References
Querying the Masked Event Alarms

You can find the masked event alarms quickly by setting the query conditions for masked event alarms.
Context
The masked alarm is the alarm that is masked by the alarm correlation rules. It includes masked fault alarms and masked event alarms.
Procedure
Step 1 Choose Monitor > Masked Event Alarms. Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Click Save As to save the query result in a file.
NOTE
Step 5 Optional: Click Print. In the Print dialog box, set the print parameters and then click Print. Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set. Step 9 Optional: Right-click an alarm in the browse window and choose Topology Location . The cursor is located to the NE that raises the alarm. Step 10 Optional: Right-click an alarm in the browse window and choose Details , or double-click the alarm. In the displayed dialog box, you can view the name, location, and severity of the alarm. Step 11 Optional: Right-click an alarm in the browse window and choose Masked Alarm . l l In the displayed dialog box, you can click Previous to view the masked alarm of the previous alarm. In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
Related References
Displaying Fault Alarms by Status

By this task, you can view the fault alarms of different status in a window.
Context
NOTE
Up to 1000 fault alarms of each state can be displayed.
Procedure
Step 1 Choose Monitor > Browse Current Fault Alarms By Status , or click on the toolbar.
Step 2 In the Filter dialog box, set the parameters for the fault alarm display. Click OK. Step 3 Optional: Select Auto Refresh in the fault browse window. The alarms in the fault browse window are refreshed in real time. You can browse the latest alarms.
NOTE
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Send Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail address or SMS number. Click OK.
NOTE
l l
In the displayed dialog box, you can view the masked alarm of the alarm. Step 11 Optional: Click the number buttons 1, 2, 3, and 4 to open or close the panes corresponding to the numbers. ----End
Displaying Event Alarms by Status

By this task, you can view the event alarms of different status in a window.
Context
NOTE
Up to 1000 event alarms of each state can be displayed.
Procedure
Step 1 Choose Monitor > Browse Event Alarms By Status. Step 2 In the Filter dialog box, set the parameters for the event alarm display. Click OK. Step 3 Optional: Select Auto Refresh in the fault browse window. The alarms in the fault browse window are refreshed in real time. You can browse the latest alarms.
NOTE
2-22
Issue 06 (2008-12-16)
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Send Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail address or SMS number. Click OK.
NOTE
l l
Setting an Alarm Query Template

You can save the frequently used query conditions as templates for future use.
Context
l l
You can set a maximum of one default template and five autoloading templates. In the template navigation tree, the default icon of a template is template is , and the icon of an autoloading template is . and autoloading, the icon is , the icon of a default
. For the template that is default
Issue 06 (2008-12-16)
2-23
Procedure
Step 1 In the alarm query window, click Template, choose New. Step 2 In the Enter The Template Name dialog box, set the template name. Click Set default template or Set auto load template as required, and then click OK.
l
After you log in M2000 on the client, the M2000 automatically opens all autoloading templates and displays corresponding alarms of these templates. When you query alarms, the M2000 automatically opens the default template.
Step 3 In the Filter dialog box, set the alarm query conditions. Step 4 Click OK. Step 5 In the Confirmation dialog box, click Yes. ----End
2.2.8 Collecting Alarm Statistics

By collecting alarm statistics, you can know the fault status of the network and obtain relevant data to remove faults and improve the network. You can set a query template based on the frequently used statistical conditions for future use. 2.2.8.1 Collecting Statistics on Fault Alarms You can collect statistics on fault alarms by setting fault alarm statistical conditions. 2.2.8.2 Collecting Statistics on Event Alarms You can collect statistics on event alarms by setting event alarm statistical conditions. 2.2.8.3 Setting a Manual Alarm Statistics Template You can set a manual alarm statistics template based on the frequently used statistical conditions. When you want to collect statistics on the alarms with the same conditions, you can use the template and do not have to set the conditions. It is very convenient.
Related References
2.8.13 Parameters for Setting Alarm Statistics
Collecting Statistics on Fault Alarms

You can collect statistics on fault alarms by setting fault alarm statistical conditions.
Context
The M2000 supports up to 400,000 statistical results. Because the count of the statistical results is the permutation result of all the statistical items and the statistical results with 0 are not displayed on the client, the displayed statistical results are less than the total statistical results.
Procedure
Step 1 Choose Monitor > Fault Alarm Statistics. Step 2 In the Statistic Filter dialog box, set the fault alarm statistical conditions, and then click OK.

NOTE
The statistical results are displayed on the Table and Pie tabs.
l l
Table: The results are listed in a table. Pie: Different statistic items are displayed in different pie charts. Click the tab of an item name to view its pie chart.
Step 3 Optional: In the statistical result window, click Save As to save the result in a file.
NOTE
Click the Table tab. The file can be saved in the *.txt, *.html, or *.csv format.
NOTE
When a CSV file contains more than 256 lines, it cannot be opened by Excel. Use a text editing tool such as UltraEdit or notepad to open the file.
l
Click the Pie tab. The file is saved in the *.jpg format.
Step 4 Optional: In the statistical result window, click the Table tab. Click Print to print the statistical result. ----End
Related References
2.8.16 Parameters for Selecting Alarm Name
Collecting Statistics on Event Alarms

You can collect statistics on event alarms by setting event alarm statistical conditions.
Context
Procedure
Step 1 ChooseMonitor > Event Alarm Statistics. Step 2 In the Statistic Filter dialog box, set the event alarm statistical conditions, and then click OK.
NOTE
The statistical results are displayed on the Table and Pie tabs.
l l
Table: The results are listed in a table. Pie: Different statistic items are displayed in different pie charts. Click the tab of an item name to view its pie chart.
Step 3 Optional: In the statistical result window, click Save As to save the result in a file.
NOTE
Click the Table tab. The file can be saved in the *.txt, *.html, or *.csv format.
NOTE
When a CSV file contains more than 256 lines, it cannot be opened by Excel. Use a text editing tool such as UltraEdit or notepad to open the file.
l
Click the Pie tab. The file is saved in the *.jpg format.
Issue 06 (2008-12-16)
2-25
Step 4 Optional: In the statistical result window, click the Table tab. Click Print to print the statistical result. ----End
Setting a Manual Alarm Statistics Template

You can set a manual alarm statistics template based on the frequently used statistical conditions. When you want to collect statistics on the alarms with the same conditions, you can use the template and do not have to set the conditions. It is very convenient.
Context
l l
You can set a maximum of one default template and five autoloading templates. In the template navigation tree, the default icon of a template is template is , and the icon of an autoloading template is . and autoloading, the icon is , the icon of a default
. For the template that is default
Procedure
Step 1 Choose Monitor > Fault Alarm Statistics or Monitor > Event Alarm Statistics. Step 2 In the Statistic Filter window, click Cancel. Step 3 In the statistic window, click Template, and then select New. Step 4 In the Enter The Template Name dialog box, enter the template name. Select Set Default Template or Set auto load template as required, and then click OK.
l
After you log in M2000 on the client, the M2000 automatically opens all autoloading templates and displays corresponding alarms of these templates. When you statistic alarms, the M2000 automatically opens the default template.
Step 5 In the Statistic Filter dialog box, set the alarm statistical conditions, and then click OK. Step 6 In the Confirmation dialog box, click Yes. ----End
2.2.9 Saving Alarm Data

When querying or collecting statistics of alarms, you can save the alarm data to files.
Prerequisite
The Alarm Browse, Query and Statistics window is open and the results of the alarm query or statistics are displayed.
Context
l
You can save all or selected alarm information in the Current Fault Alarms tab, the Event Alarms tab, the History Fault Alarms, the Masked Fault Alarms tab, and the Masked Event Alarms tab. You can save only selected alarm information in the Browse Current Fault Alarms by Status tab and the Browse Current Event Alarms by Status tab. You can save the statistic results of all alarm records.
Procedure
Step 1 In the 2.2.7 Querying Alarms or 2.2.8 Collecting Alarm Statistics window, open the Save dialog box. Save Range All alarm records Operation Click Save As.
Selected alarm records Right-click the alarm information to be saved and choose Save Selected Record(s) on the shortcut menu.
NOTE You can press Ctrl or Shift to select multiple alarm records at the same time.
Step 2 Specify the file path. Step 3 Specify the file name. The name can comprise letters, numbers, and characters. The file name, however, cannot contain the following characters: * " ? / | < > Step 4 Specify the file type under File Type. Step 5 In the Save dialog box, click Save. The Saving ... dialog box is displayed. This dialog box indicates the saving progress. ----End
2.2.10 Printing Alarm Data

This task is performed to print the results of alarm query or alarm statistics.
Prerequisite
The alarm query or statistics interface is open and displays the required alarm information.
Context
l
You can print all or selected alarm information in the Current Fault Alarms tab, the Event Alarms tab, the History Fault Alarms tab, the Masked Fault Alarms tab, and the Masked Event Alarms tab. You can print the statistic results of all alarm records.
Issue 06 (2008-12-16)
Procedure
Step 1 In the 2.2.7 Querying Alarms or 2.2.8 Collecting Alarm Statistics window, open the Print dialog box. Print Range All alarm records Operation Click Print.
Selected alarm records Right-click the alarm information to be printed and choose Print Selected Record(s) on the shortcut menu.
NOTE You can press Ctrl or Shift to select multiple alarm records at the same time.
Step 2 On the General tab, specify the printing service, scope, and copies.
TIP
If you select Print To File on the General tab, the Print To File dialog box is displayed. Specify the file name and path in the dialog box, and then click OK to save the alarm information to a specific file.
Step 3 On the Page Setup tab, specify the paper attributes, such as the size, source, orientation, and margins. Step 4 On the Appearance tab, specify the printing attributes, such as the color appearance, quality, sides, and job attributes. Step 5 Click Print. The Printing... dialog box is displayed. This dialog box indicates the saving progress. ----End
2.2.11 Handling Alarms

When you find an alarm, you need to take actions to handle it. The procedure of handling an alarm consists of viewing alarm details, acknowledging, locating, and clearing the alarm. 2.2.11.1 Procedure for Handling Fault Alarms The procedure for fault handling consists of three phases: information collection, fault location, and fault removal. After receiving an alarm, you need to collect fault information, analyze fault causes, locate the fault, remove the fault, and restore the system. 2.2.7.1 Querying Current Fault Alarms You can find the specific fault alarms quickly by setting the fault alarm query conditions. 2.2.11.3 Viewing Alarm Details By querying alarm details, you can obtain the information such as the alarm name, alarm location, and alarm level. 2.2.11.4 Acknowledging Alarms Alarm acknowledgement allows you to check if an alarm has been handled. You can easily distinguish between the alarms you have handled and those you have not handled. You can then take proper measures to handle them. 2.2.11.5 Removing Alarm-Related Faults
To remove alarm-related faults, you find causes of the alarms and then clear the causes to ensure the proper operation of the system. To remove alarm-related faults, you many need relevant personnel to assist you. 2.2.11.6 Clearing Alarms You can manually clear the alarms that cannot be cleared automatically or the alarms that have been acknowledged. After a fault alarm is cleared, the M2000 considers that the fault that causes the alarm is removed. 2.2.11.7 Recording Alarm Handling Experience You can record the alarm handling experience in the knowledge base. When a similar alarm occurs, you can refer to the experience in the database to handle it. 2.2.11.8 Exporting Maintenance Experience When you record the alarm maintenance experience in a server, you can export the information from the alarm experience base to back up or synchronize the information to another server. 2.2.11.9 Importing Maintenance Experience You can import the alarm maintenance experience from a server to the alarm maintenance base, to back up or synchronize the information to another server. 2.2.11.10 Example: Alarm Handling This section provides an example on how to handle the issue of insufficient disk space. It describes the procedure and method for handling alarms. You can know the basic procedure and operation of alarm handling from this example.
Procedure for Handling Fault Alarms

The procedure for fault handling consists of three phases: information collection, fault location, and fault removal. After receiving an alarm, you need to collect fault information, analyze fault causes, locate the fault, remove the fault, and restore the system.
Flow Chart
Figure 2-3 shows the fault handling procedure.
Issue 06 (2008-12-16)
2-29
Figure 2-3 Fault handling procedure
Procedure
The fault handling procedure, as shown in Figure 2-3, is described inTable 2-4.
2-30
Issue 06 (2008-12-16)
Table 2-4 Fault handling procedure Step 1 Operation Receive an alarm Description After you receive an alarm, start the alarm handling procedure. To ensure that the operators can receive notifications in time when a fault occurs, you need to set alarm notification methods on the M2000. This is where you start. View the alarm details, including the alarm location information, alarm help, and alarm maintenance experience. To avoid others handling the same alarm, you need to acknowledge it. When you acknowledge an alarm, it indicates that the alarm is being processed. By locating an alarm, you can query the fault information and analyze the causes of the fault. Analyze the causes of the fault according to the fault information. Work out the fault handling scheme according to the alarm details, device manuals, network status, and maintenance experience. Carry out the fault handling scheme to remove the fault. When the fault is removed, the alarm is cleared, and the M2000 receives the cleared alarm. After the fault is removed, check the handling results. After you complete the fault handling, record the maintenance experience.
View the alarm details
Acknowledge the alarm Collect fault information Analyze the causes of the alarm Work out the fault handling scheme Carry out the fault handling scheme Clear the alarm Check the handling results Record the maintenance experience
4 5 6
7 8 9 10
Querying Current Fault Alarms

You can find the specific fault alarms quickly by setting the fault alarm query conditions.
Procedure
Step 1 Choose Monitor > Current Fault Alarms, or click Step 2 In the Filter dialog box, set the alarm query conditions. Step 3 Click OK. The query result is displayed in the browse window. Step 4 Optional: Click Save As to save the query result in a file. on the toolbar.
Issue 06 (2008-12-16)
2-31
NOTE
NOTE
Step 7 Optional: Right-click an alarm in the browse window and choose Synchronize. The alarm data on the M2000 keep consistent with that on the NE. Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Configure Columns. In the Configure Columns dialog box, select the columns to be displayed in the browse window and the area where the column settings take effect. Click OK. The alarms are displayed according to your settings. Step 9 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or Descending. Click OK. The alarms are displayed according to the keywords you set. Step 10 Optional: Choose one or more alarms in the browse window, right-click and then choose Display Time Mode > Server Time or Display Time Mode > NE Time. The alarms are displayed according to the time mode you set. Step 11 Optional: Choose one or more alarms in the browse window, right-click and then choose Send Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail address or SMS number. Click OK.
NOTE
l l
Related References
2.8.12 Parameters for Setting Alarm Query/Browse 2.8.15 Parameters for Selecting Alarm Objects 2.8.16 Parameters for Selecting Alarm Name
Viewing Alarm Details

By querying alarm details, you can obtain the information such as the alarm name, alarm location, and alarm level.
Procedure
Step 1 In the window for browsing alarm query result, double-click an alarm or right-click an alarm and choose Detail Information. Step 2 In the Detail Information window, click Modify below the Alarm Experience text box. Enter the alarm maintenance experience. Then Click Add or Modify below the Alarm Memo text box. Enter the remarks. Then click Close. ----End
Related References
2.8.20 Parameters for Viewing Alarm Details
Acknowledging Alarms
Alarm acknowledgement allows you to check if an alarm has been handled. You can easily distinguish between the alarms you have handled and those you have not handled. You can then take proper measures to handle them.
Procedure
Step 1 In the window for browsing the alarm query result, right-click an alarm and choose Acknowledge .
NOTE
If the alarm you click is acknowledged, Acknowledge in the shortcut menu is disabled, and Unacknowledge is enabled.
Step 2 In the Confirmation dialog box, click Yes.

NOTE
After an alarm is acknowledged, you can click Unacknowledge to recover the alarm state to unacknowledged.
----End
Removing Alarm-Related Faults

To remove alarm-related faults, you find causes of the alarms and then clear the causes to ensure the proper operation of the system. To remove alarm-related faults, you many need relevant personnel to assist you.
Prerequisite
You have obtained alarm-related information. For details, refer to 2.2.11.3 Viewing Alarm Details.
Context
l
For fault alarms, you need to remove related alarms based on the causes of the alarms. When multiple fault alarms exist at the same time, you need to determine the priority of these alarms according to the alarm severity and the operational status of the current network. For event alarms, you need only to inform the occurrence of the alarms and does not need to remove the faults.
Procedure
Step 1 Check the online help of an alarm to know alarm explanation and treatment suggestions. You can select the Alarm Details tab in the Alarm Details dialog box. Click More information to view the online help associated with the alarm. Step 2 Check the treatment experience of the alarm-related fault. You can choose the Knowledge and Explanation tab in the Alarm Details dialog box to view the information in the Knowledge frame. Step 3 Contact relevant personnel to remove alarm-related faults according to treatment suggestions and recorded fault treatment experience. ----End
Postrequisite
After fault alarms are removed, the system automatically sets the state of the alarm to be Cleared.
Clearing Alarms
You can manually clear the alarms that cannot be cleared automatically or the alarms that have been acknowledged. After a fault alarm is cleared, the M2000 considers that the fault that causes the alarm is removed.
Context
l
One cleared alarm corresponds to one fault alarm. When the device is faulty, the fault alarm is reported to the M2000. After the fault is removed, the device sends the notification to the M2000, and the fault alarm is cleared automatically. The acknowledged and cleared fault alarms are history fault alarms. They are saved in the database of the history fault alarm for further query.
Procedure
Step 1 In the window for browsing the alarm query result, right-click a fault alarm and select Clear .

NOTE
If you right-click the fault alarm that has been cleared, the Clear menu is disabled.
Step 2 In the Confirmation dialog box, click Yes. The alarm status changes to Cleared. ----End
Recording Alarm Handling Experience

You can record the alarm handling experience in the knowledge base. When a similar alarm occurs, you can refer to the experience in the database to handle it.
Context
The initial knowledge base is empty.
Procedure
Step 1 ChooseMonitor > Settings > Explain and Experience. Step 2 In the Search by name text box, enter the key word of an alarm name. In the Alarm names navigation tree, alarm names with the key word are listed. Step 3 In the Alarm names navigation tree, choose an alarm name, ClickModify.
NOTE
You can choose one or more options from Group by NE Type, Group by Alarm Type, Group by Alarm Level, and Group by Category. This helps you to locate an alarm name more quickly in the navigation tree.
Step 4 In the Modify Experience group box, enter the alarm handling experience. Step 5 Click OK. ----End
Related References
2.8.17 Parameters for the Alarm Explanation and Maintenance Experience
Exporting Maintenance Experience

When you record the alarm maintenance experience in a server, you can export the information from the alarm experience base to back up or synchronize the information to another server.
Context
Do not modify the experience base file on the disk manually.
Procedure
Step 1 Choose Monitor > Settings > Explain and Experience. Step 2 In the Explain and Experience window, in the Search by name text box, enter the keywords of the alarm name.
The Alarm names navigation tree displays the alarm names that contain the keywords. Step 3 From the Alarm names navigation tree, select the name of the alarm whose maintenance experience you want to export, and then click Import. You can also select one or more from the Group by NE type, Group by alarm type, Group by alarm severity, and Group by category to sort the alarms. In the Alarm names navigation tree, select the name of the alarm whose maintenance experience you want to export. Step 4 In the Export Experience dialog box, click .
Step 5 In the Export dialog box, set the path, file name and file type of the exported file, and then click OK.
NOTE
The maintenance experience can only be exported as XML or CSV file.
Step 6 In the Export Experience dialog box, select Export All or Export by NE Type, and then click Export. ----End
Importing Maintenance Experience

You can import the alarm maintenance experience from a server to the alarm maintenance base, to back up or synchronize the information to another server.
Context
Do not modify the maintenance base file on the disk manually.
Procedure
Step 1 Choose Monitor > Settings > Explain and Experience. Step 2 In the Explain and Experience window, in the Search by name text box, enter the keywords of the alarm name. The Alarm names navigation tree displays the alarm names that contain the keywords. Step 3 From the Alarm names navigation tree, select the names of the alarms to be imported to the explanation and experience database. Click Import. You can also select one or more of Group by NE type, Group by alarm type, Group by alarm severity, and Group by category to sort the alarms. From the Alarm names navigation tree, select the names of the alarms to be imported to the explanation and experience database. Step 4 In the Import Experience dialog box, click .
Step 5 In the Open dialog box, select the target file, and then click Open.
NOTE
Only the files in the XML format can be imported to the explanation and experience database.
Step 6 In the Import Experience dialog box, select Add or Update, and then click Import. Step 7 In the Confirmation dialog box, click Yes. ----End
Example: Alarm Handling

This section provides an example on how to handle the issue of insufficient disk space. It describes the procedure and method for handling alarms. You can know the basic procedure and operation of alarm handling from this example.
Background
Administrator A finds that the M2000 reports a new alarm.
Operation Guide
Based on the Alarm Handling Procedure, administrator A has taken the following actions: 1. Receive the alarm notification. On the client, choose Monitor > Current Fault Alarms to browse the alarm list. An uncleared alarm with Identity(ID) 34 is found. The M2000 server has insufficient disk space. 2. 3. View the alarm details. Double-click this alarm to view its details. Acknowledge the alarm. The results indicate that the fault is removed. Now, the alarm can be acknowledged. In the alarm list, right-click this alarm and choose Acknowledge . In the Configuration dialog box, click OK. 4. Work out the alarm handling method. According to the fault management tips, maintenance experience, and the running status of the M2000, administrator A decides to delete the redundant files and back up the exported data on other disks. 5. Remove the relevant fault. Delete the redundant files of the M2000. Back up the export files to other disks. Then delete the exported data from the source disk. The M2000 server then has more available disk space. 6. Check the handling results. On the client, choose Monitor > Current Fault Alarms to browse the alarm list. The status of the alarm is changed from uncleared to cleared. 7. Record the alarm handling experience. On the client, choose Monitor > Settings > Explain and Experience. In the Explain and Experience tab. Search for the alarm and edit its maintenance experience.
2.2.12 Setting the Displaying Location for a New Alarm

Through this operation, you can set the new fault/event alarm to display the front or back of the alarm list, in order to view the newly reported alarm.
Procedure
Step 1 Choose System > Preferences. Step 2 Expand Alarm Local Terminal Settings , and then select New Fault/Event Alarms.
Step 3 In the New Fault/Event Alarms group box, click Display on top or Display at the bottom. Step 4 Click OK. The new fault/event alarm is displayed at the beginning or end of the alarm list. ----End
2.3 Setting Alarm Auto Processing

You can set an auto processing rules, and then the M2000 processes the alarms that match the preset conditions. This helps to improve the work efficiency. 2.3.1 Alarm Auto Processing Policies Alarm auto processing policy involves alarm filter, alarm auto acknowledgement, and alarm level redefinition. By alarm auto processing, the M2000 processes the alarm that match certain conditions in different ways; thus it improves the efficiency of alarm processing. 2.3.2 Setting Alarm Notification The M2000 provides you with multiple alarm notification methods, such as alarm board, alarm box, email, and short message service (SMS). You can customize the methods to obtain the latest alarm information in time. 2.3.3 Setting Alarm Remote Notification When you set the remote notification for alarms, you need to set the parameters, including the parameters for the notification by email and SMS. 2.3.4 Setting Alarm Filter Rules You can set the alarm filter rules to filter fault alarms and event alarms. The filtered alarms are discarded and are not saved in the alarm database. 2.3.5 Setting Alarm Auto Acknowledgement For the purpose of maintenance, the M2000 provides the real-time auto acknowledgement for the unacknowledged and cleared fault alarms. 2.3.6 Setting Redefinition of Alarm Level In the M2000, you can redefine the alarm levels according to the actual requirements. You can set the levels of the alarms that are not concerned to lower ones, and set the levels of the alarms that are concerned to higher ones. 2.3.7 Setting Alarm Correlation Rules You can set an alarm correlation rule to enable the M2000 to filter unnecessary alarm information. This improves the efficiency of handling alarms.M2000The M2000 provides multiple analysis methods, such as intermittent fault alarm analysis, repeat event analysis, and custom correlation analysis. 2.3.8 Managing Auto-Triggering Script Tasks The alarm auto-triggering script task realizes partial automation of the routine maintenance work by automatically triggering and executing the shell script file that is set by the user. Through the M2000 client, you can add the auto-triggering tasks, check the task attributes,and check the specific task and the auto-triggering conditions.
2.3.1 Alarm Auto Processing Policies

Alarm auto processing policy involves alarm filter, alarm auto acknowledgement, and alarm level redefinition. By alarm auto processing, the M2000 processes the alarm that match certain conditions in different ways; thus it improves the efficiency of alarm processing.
The auto processing policies involve the following: 1. Alarm filter If you are not concerned about some alarms, you can set the M2000 to filter them. For example, when the equipment is under maintenance or test, mass alarms are raised. Such alarms can be filtered. 2. Alarm auto acknowledgement After the related faults are removed, you do not have to manually acknowledge the cleared alarms. You can set the auto acknowledgement condition so that the M2000 can acknowledge alarms based on the condition automatically. 3. Alarm level redefinition You can redefine the alarm levels on the M2000 according to the actual requirements.
2.3.2 Setting Alarm Notification

The M2000 provides you with multiple alarm notification methods, such as alarm board, alarm box, email, and short message service (SMS). You can customize the methods to obtain the latest alarm information in time. 2.3.2.1 Alarm Notification Methods The M2000 provides various notification methods, such as alarm browser notification, topology view icon notification, alarm sound box notification, alarm board notification, alarm box notification and remote notification. These notifications help you to obtain the alarm information. 2.3.2.2 Introduction to the Alarm Board The alarm board uses color indicators to identify different levels of alarms. You can customize the indicator colors and alarm sounds. 2.3.2.3 Setting the Alarm Board You can set the following on the alarm board: whether the alarm box pops up automatically and whether the alarm indicator blinks when an alarm is raised; and whether to bind the fault template or event template with the alarm board. 2.3.2.4 Setting the Alarm Box You can set filter conditions for the alarm box on the client. Alarms that match the conditions are sent to the alarm box and prompted in audio and visual mode. 2.3.2.5 Setting the Alarm Sound You can set the alarm sound for each alarm level. When an alarm is raised, the sound box plays the corresponding alarm sound. You can also disable or enable the alarm sound. 2.3.2.6 Setting the Alarm Color You can set a color for each alarm level. This helps you browse different alarms easily. 2.3.2.7 Setting Alarm Highlight After you set the alarm highlight, an alarm is highlighted in the alarm query result window when it is not handled in the preset period.
Alarm Notification Methods

The M2000 provides various notification methods, such as alarm browser notification, topology view icon notification, alarm sound box notification, alarm board notification, alarm box
notification and remote notification. These notifications help you to obtain the alarm information. The M2000 provides the following notification methods:
l
Alarm browser The alarm browser is a window on the client. You can browse alarms in real time by using the browser. The M2000 also enables you to query specified alarms, such as event alarms, history alarms, or current alarms.
Topology view The topology view is a view that shows the device distribution on the client. The device icons in the view show the alarm status through their colors and status. You can observe the icons to know whether an alarm occurs to a device and the severity and status of the alarm.
Alarm speaker The alarm speaker notifies users of the current alarm by playing a sound. To use the alarm speaker, connect it to the M2000 server or client and set the parameters. You can know new alarms and their severities by using the alarm speaker.
Alarm board The alarm board is a board on the client. It displays the alarm status through flashing indicators and statistics. You can monitor the alarms in the network through this board to know alarm severity and related statistics.
Alarm box An alarm box is a hardware that prompts alarms in audio and video mode. An alarm box consists of an amplifier and four indicators. It connects to the M2000 client by a serial port cable. When an alarm is raised, the corresponding indicator is lighted and an alarm sound is played.
Alarm remote notification You can set a mail server or wireless modem for remote notification. The M2000 notifies the maintenance personnel of alarms by email or SMS.
Introduction to the Alarm Board

The alarm board uses color indicators to identify different levels of alarms. You can customize the indicator colors and alarm sounds.
Alarm Board
The minimized icon of the alarm board is displayed on the right of the toolbar. See Figure 2-4. Figure 2-4 Alarm Board Icon
Choose Monitor > Display Alarm Board, or in the M2000 client GUI, click alarm board, as shown in Figure 2-5.
2-40 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
to open the
Issue 06 (2008-12-16)
Figure 2-5 Alarm Board
The four color indicators on the alarm board represent critical, major, monitor, and warning alarms. The numbers under the indicators are the counts of alarms. The alarm board is a window that runs on the client and displays the alarm statistics in real time. If a new alarm is raised, the relative indicator flashes and the alarm sound is played. The alarm statistics on the alarm board is refreshed in real time. Both the alarm box and alarm board notify users of new alarms in audio and visual mode. The alarm box is hardware. It cannot display the alarm statistics. You can set the condition to filter the alarms sent to the alarm box on the client. Compared with the alarm box, the alarm board is a window on the client. You can click Add at the bottom of the Alarm Board dialog box to bind the fault template and event template with the alarm board. You cannot set the filter conditions for it. It can display the alarm statistics based on the alarm status and severities according to templates in real time. shows that the data is being refreshed in the alarm board. and the template name is preceded by in the alarm board. show that the data is failed to be refreshed
l l
Setting the Alarm Board

You can set the following on the alarm board: whether the alarm box pops up automatically and whether the alarm indicator blinks when an alarm is raised; and whether to bind the fault template or event template with the alarm board.
Procedure
Step 1 ChooseMonitor > Display Alarm Board or click on the toolbar.
Step 2 In the Alarm Board dialog box, click Option. Set auto display for the alarm board or auto flash for the alarm lamp. Step 3 In the Alarm Board dialog box, click Add.
NOTE
You can select a template except the All objects in the Alarm Board dialog boxand then click Delete to delete the template.
Issue 06 (2008-12-16)
2-41
Step 4 In the Add dialog box, select the event template or the current fault template. Then click Add. The alarm information on the bound template is added on the alarm board.
NOTE
If no fault template or event template is created, click New Event Template or New Fault Template to create a template.
----End
Setting the Alarm Box

You can set filter conditions for the alarm box on the client. Alarms that match the conditions are sent to the alarm box and prompted in audio and visual mode.
Procedure
Step 1 Choose Monitor > Alarm Box Manager. Step 2 In the Alarm Box Manager dialog box, set Control Sound and Light by Severity or Control Sound and Light by Template, select Enableand then select Serial Port.
NOTE
When the alarm box generates an alarm sound, click Mute current alarm sound to stop the alarm sound.
Related References
2.8.31 Parameters for Setting the Alarm Box
Setting the Alarm Sound

You can set the alarm sound for each alarm level. When an alarm is raised, the sound box plays the corresponding alarm sound. You can also disable or enable the alarm sound.
Context
l l
You can use the sound file of the M2000 or others. Only the sound files of the Wav type in the PCM format are supported. The Microsoft ADPCM type is not supported. By default, the sound files of the four alarm severities are located in style/defaultstyle/ conf/alarmclient/ of the M2000 client installation folder. The file names are Critical.wav, Major.wav, Minor.wav and Warning.wav.
Procedure
Step 1 Perform different operations according to different customized requirement.
2-42
Issue 06 (2008-12-16)
If You Need to
Perform.
Enable or disable the client alarm sound Select or clear Monitor > Stop Client Sounding. Set the preference of alarm sound Step 2 Choose System > Preferences. Step 3 In the Preferences dialog box, from the navigation tree on the left, select Disconnection Sound. 1. 2. In the Sound group box, click the path of the sound file, and then Configuration dialog box, select a sound file, and then click OK. In Sound Time(S), enter the play duration of the sound. Click listen to the sound.
NOTE
Perform Step 2.
. In the Sound on the right to
l l
The play duration is from 0 to 600, and the unit is second. 0 indicates that the play time is unlimited. If the alarm indicator on the alarm board is set to flash when a new alarm is raised, when a new alarm is raised, the alarm indicator that corresponds to the severity of this alarm flashes for the preset duration. If alarms of different severities are raised, only the alarm indicator that corresponds to the highest alarm severity flashes. If the duration of the alarm sound of an alarm severity is set to 0, when an alarm of this severity is raised, the alarm indicator keeps flashing until the alarm is cleared.
3.
Optional: In the Sound group box, click Default to restore the alarm sound to the default.
Setting the Alarm Color

You can set a color for each alarm level. This helps you browse different alarms easily.
Context
l
After you complete the settings, the alarm icon in the topology view, the alarm record you query, and the alarm indicator on the alarm board are shown in the specified color. To recover the default color, click the Sound and Color tab and then click Default. Click Default in the Preferences dialog box to restore the alarm color to the default.
Procedure
Step 1 ChooseSystem > Preferences. Step 2 In the Preferences dialog box, from the navigation tree on the left, select Color. Step 3 In the Color group box, double-click the button next to an alarm level to select the alarm color. Step 4 Click OK. ----End
Setting Alarm Highlight

After you set the alarm highlight, an alarm is highlighted in the alarm query result window when it is not handled in the preset period.
Context
l
The unacknowledged event alarm is highlighted when the interval between the local time on the client and the alarm raised time exceeds the threshold of the alarm highlight. The unacknowledged and uncleared fault alarm is highlighted when the interval between the local time on the client and the alarm raised time exceeds the threshold of the alarm highlight. The time on the client should synchronize with the time on the server. Otherwise, the time an alarm is highlighted differs from the highlight time you set. For example, if the highlight time you set is 5 minutes. But the time on the client is 5 minutes ahead of the time on the server. Then, the alarm is highlighted on the client immediately when it is raised.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences dialog box, in the navigation tree on the left, expand the Alarm Local Terminal Settings node, and then select Highlight. Step 3 In the Highlight group box, set the time for the alarms of a level.
NOTE
Time range: 0-1000000, Unit: minute. 0 indicates that the alarm is not highlighted.
2.3.3 Setting Alarm Remote Notification

When you set the remote notification for alarms, you need to set the parameters, including the parameters for the notification by email and SMS. 2.3.3.1 Setting the Remote Notification Rules for Alarms Before setting parameters for notification by email or SMS, you need to set the remote notification rules for alarms. These rules include notification conditions, notification time, and notification modes. 2.3.3.2 Setting Alarm Remote Notification Parameters You can set the parameters for alarm remote notification to send alarm information to users by email or SMS so that the users can know the alarm information on the M2000 server.
Setting the Remote Notification Rules for Alarms

Before setting parameters for notification by email or SMS, you need to set the remote notification rules for alarms. These rules include notification conditions, notification time, and notification modes.
Context
l l
A user can set more than one remote notification mode. A user can add at most fifty remote notification rules for alarms. Attempts to add more than fifty cause error messages. In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000 server. The steps of setting event remote notification rule and fault remote notification rule are the same. The following example describes the steps by setting the latter rules.
Procedure
Step 1 Choose Monitor > Settings > Remote Notification . Step 2 In the Remote Notify tab click Add, and then choose Fault Notification . Step 3 In the Base Setting tab of the Add Remote Notify Rule dialog box, set the parameters such as Name and Severity. Step 4 Click the Alarm Source tab. On the Alarm Source tab, set the alarm source. Click Next. Step 5 In the Add Remote Notify Rule dialog box set the notification time. Click Next. Step 6 In the Add Remote Notify Rule dialog box set the email address or SMS number. Select Enable. Step 7 Click Finish. ----End
Related References
2.8.16 Parameters for Selecting Alarm Name 2.8.32 Parameters for Setting Alarm Remote Notification Rules
Setting Alarm Remote Notification Parameters

You can set the parameters for alarm remote notification to send alarm information to users by email or SMS so that the users can know the alarm information on the M2000 server.
Context
Only the users that have the right of Setting Remote notification parameters can perform this task.
Procedure
Step 1 Choose Monitor > Settings > Remote Notification . Step 2 On the lower left of the Remote Notify window, click Communication Settings. Step 3 In the Notify Device Communication Settings dialog box, click Add.
NOTE
In the Notify Device Communication Settings dialog box, select a row and click Modify. In the Modify Notify Device Communication Settings dialog box, modify the setting name and communication parameters. In the Notify Device Communication Settings dialog box, select a row and click Delete to delete the settings.
Step 4 In the Add Notify Device Communication Settings dialog box, enter the device name. Select the sending device. Click Next.
NOTE
There are four types of devices that can send alarm notification: Email, GSM Modem, CDMA Modem, and SMS Gateway(SMS Center). The method of email sends notifications by emails. The other methods send notifications by SMS. When you set GSM Modem or CDMA Modem, pay attention to the following points:
l l l l
If the sending address is the server, the modem must be correctly installed on the server. In this case, the clients that log in to the server can send short messages for alarm remote notification. If the sending address is the client, only the clients that are installed with the modem can send remote alarm notification. If the sending address is the client, the corresponding serial port of the client is always in use until the M2000 client is exited. If the sending address is the server, the corresponding serial port of the server is always in use until the M2000 server is exited.
Step 5 In the Add Notify Device Communication Settings dialog box, set the parameters. Select Enable.
NOTE
For details on the parameters, see 2.8.33 Parameters for Setting Notification by Email, 2.8.35 Parameters for Setting Notification by Modem or 2.8.37 Parameters for Setting Notification by SMS Gateway.
Step 6 Optional: Click Advanced. In the Notify Device Communication Settings dialog box, set the format of the sending content. Click OK.
NOTE
For details on the parameters, see 2.8.34 Parameters for Advanced Settings of Notification by Email, 2.8.36 Parameters for Advanced Settings of Notification by Modem or 2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway.
Step 7 In the Add Notify Device Communication Settings dialog box, click Finish. Step 8 In the Notify Device Communication Settings dialog box, click Close. ----End
Related References
2.8.33 Parameters for Setting Notification by Email 2.8.34 Parameters for Advanced Settings of Notification by Email 2.8.35 Parameters for Setting Notification by Modem 2.8.36 Parameters for Advanced Settings of Notification by Modem 2.8.37 Parameters for Setting Notification by SMS Gateway 2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway
2.3.4 Setting Alarm Filter Rules

You can set the alarm filter rules to filter fault alarms and event alarms. The filtered alarms are discarded and are not saved in the alarm database. 2.3.4.1 Adding Alarm Filter Rules This section describes how to add the alarm filter rules to filter the alarms that match the rules. 2.3.4.2 Modifying Alarm Filter Rules The modification on the alarm screening rule refers to modifying the screen condition, time mode, screening rule, validation date, expiration date, and remark based on the previous alarm screening rule. 2.3.4.3 Deleting Alarm Filter Rules If an alarm filter rule is no longer applicable, delete it.
Related References
2.8.19 Parameters for Setting Alarm Filter Conditions
Adding Alarm Filter Rules

This section describes how to add the alarm filter rules to filter the alarms that match the rules.
Context
l
If both alarm severity redefinition and alarm filter are set for an alarm, the alarm is filtered first and then redefined the severity. Therefore, alarm filter is based on the original attributes (the attributes before severity redefinition) of the alarms. The M2000 discards the alarms that are masked by the alarm mask rules and does not save the alarms to the alarm database.
Procedure
Step 1 Choose Monitor > Settings > Alarm Filter Rule . Step 2 On the Alarm Filter Rule tab, click Add. Choose New Alarm Filter Rule or New Event Filter Rule. Step 3 In the Add Alarm Filter Rule dialog box, set the filter parameters. Step 4 Click OK. ----End
Modifying Alarm Filter Rules

The modification on the alarm screening rule refers to modifying the screen condition, time mode, screening rule, validation date, expiration date, and remark based on the previous alarm screening rule.
Issue 06 (2008-12-16)
2-47
Context
l
If both alarm severity redefinition and alarm filter are set for an alarm, the alarm is filtered first and then redefined the severity. Therefore, alarm filter is based on the original attributes (the attributes before severity redefinition) of the alarms. The M2000 discards the alarms that are masked by the alarm mask rules and does not save the alarms to the alarm database.
Procedure
Step 1 ChooseMonitor > Settings > Alarm Filter Rule . Step 2 On the Alarm Filter Rule tab, change the alarm filter rules.
NOTE
The fields displayed in white can be changed. The fields displayed in displayed in are already changed but are not used.
cannot be changed. The fields
You can also select a relevant alarm filter rule, and then click Detail. In the Detail Information dialog box, change the alarm filter rules.
Step 3 Click Apply. ----End
Deleting Alarm Filter Rules

If an alarm filter rule is no longer applicable, delete it.
Procedure
Step 1 Choose Monitor > Settings > Alarm Filter Rule . Step 2 On the Alarm Filter Rule tab, select the alarm filter rule you want to delete. Click Delete. Step 3 In the Confirmation dialog box, click Yes. ----End
2.3.5 Setting Alarm Auto Acknowledgement

For the purpose of maintenance, the M2000 provides the real-time auto acknowledgement for the unacknowledged and cleared fault alarms.
Procedure
Step 1 ChooseMonitor > Settings > Auto Acknowledge Rule . Step 2 In the Auto Acknowledgement Rule dialog box, set the parameters of auto acknowledgement. Step 3 Click OK. After auto acknowledgement is enabled, the M2000 acknowledges the fault alarms that match the preset conditions. ----End
Related References
2.8.18 Parameters for Acknowledging Alarms Automatically
2.3.6 Setting Redefinition of Alarm Level

In the M2000, you can redefine the alarm levels according to the actual requirements. You can set the levels of the alarms that are not concerned to lower ones, and set the levels of the alarms that are concerned to higher ones. 2.3.6.1 Adding Alarm Level Redefinition Rules Add the alarm level redefinition rule to redefine the level of an alarm from an alarm source. 2.3.6.2 Modifying Rules for Alarm Severity Redefinition Modify the content of the alarm severity redefinition rule, including whether to enable the rule, alarm source, redefined severity, and memo. 2.3.6.3 Deleting Redefinition Records This section describes how to delete the alarm severity redefinition rules. You can recover the alarm severity redefinition rules redefined by the manufacturers through this operation.
Related References
2.8.23 Parameters for Redefining NMS Alarm Level 2.8.25 Parameters for Alarm Severity Redefinition
Adding Alarm Level Redefinition Rules

Add the alarm level redefinition rule to redefine the level of an alarm from an alarm source.
Context
l
The results of query, browse and statistics are displayed based on the alarm levels that are redefined. Redefinition is to change the alarm level on the M2000 server, rather than to change alarm explanations given by the device manufacturer.
Procedure
Step 1 Choose Monitor > Settings > Level Redefine . Step 2 Click Add. In the Add level Redefine Setting dialog box, set the parameters for the alarm level redefinition. 1. 2. 3. 4. 5. next to Alarm Name. In the Select Alarm Name dialog box, select the alarm Click whose level you want to redefine. Click OK. In the Redefine Level drop-down list, select the level for the alarm after redefinition. Optional: In the Memo text box, set the remarks as required. Select or clear the Enable check box as required. In the Alarm Source tab, click Select. In the Select object window , select the objects that raise alarms. By default, all the objects are selected.
Issue 06 (2008-12-16)
When the objects in Alarm Source report the alarms that are set in Alarm Name, the alarm level are redefined. Step 3 Click OK. ----End
Modifying Rules for Alarm Severity Redefinition

Modify the content of the alarm severity redefinition rule, including whether to enable the rule, alarm source, redefined severity, and memo.
Procedure
Step 1 Choose Monitor > Settings > Level Redefine . Step 2 On the Severity Redefine tab, select a rule and then modify the parameters.
NOTE
The fields displayed in white can be changed. The fields displayed in displayed in are already changed but are not used.
cannot be changed. The fields
You can also select a relevant alarm severity redefinition rule, and then click Detail. In the Detail Information dialog box, change the alarm severity redefinition rules.
Deleting Redefinition Records

This section describes how to delete the alarm severity redefinition rules. You can recover the alarm severity redefinition rules redefined by the manufacturers through this operation.
Procedure
Step 1 Choose Monitor > Settings > Level Redefine . Step 2 In the Severity Redefine window, select the alarm severity redefinition rules you want to delete.
NOTE
You can choose more than one record by Shift and Ctrl.
Step 3 Click Delete. Step 4 In the Confirmation dialog box, click YES. ----End
2.3.7 Setting Alarm Correlation Rules

You can set an alarm correlation rule to enable the M2000 to filter unnecessary alarm information. This improves the efficiency of handling alarms.M2000The M2000 provides multiple analysis methods, such as intermittent fault alarm analysis, repeat event analysis, and custom correlation analysis. 2.3.7.1 Principles of Correlation Analysis
In the network, physical or logical correlations exist between devices. A fault may cause repetitive and non-root alarms. In this case, the alarms are not important for reference. You may find it difficult to locate and remove faults. By alarm correction analysis, the M2000 can shield the repetitive or non-root alarms, and you can obtain useful alarm information. After you understand the principle of alarm correlation analysis, you can use the M2000 to set the correlation rules more accurately. 2.3.7.2 Priorities in Correlation Analysis During correlation analysis, the M2000 determines the priority of a correlation rule, and then takes a proper action. 2.3.7.3 Adding Simple Correlation Rules of Alarms To filter the intermittent alarms or repeat events and prevent the system running in unstable status, the M2000 provides simple correlation analysis for alarms. Take intermittent alarms as an example, when the alarms reach the preset limit, the M2000 filters or discards them based on the correlation rule. 2.3.7.4 Adding Advanced Correlation Rules of Alarms Through setting the advanced correlation rules of alarms, you can filter the alarms that match the rules or redefine the alarm levels. Therefore, you can reduce the unnecessary alarms or ignore the non-root alarms so that you can handle the major alarms and solve problems quickly. 2.3.7.5 Modifying Simple Correlation Rules for Alarms This section describes how to modify the existing simple correlation rules for alarms. 2.3.7.6 Modifying Advanced Correlation Rules for Alarms This section describes how to modify the existing advanced correlation rules for alarms. 2.3.7.7 Example of Using Simple Correlation Rules of Alarms This section gives an example of using the simple correlation rules of intermittent alarms to describe how to set a simple correlation rule for alarms. 2.3.7.8 Example of Using Advanced Correlation Rules of a Single Alarm This section describes how to set the advanced correlation rules for a single alarm by giving an example. 2.3.7.9 Example of Using Advanced Correlation Rules of Two Alarms This section describes how to set the advanced correlation rules for two alarms by giving an example.
Principles of Correlation Analysis

In the network, physical or logical correlations exist between devices. A fault may cause repetitive and non-root alarms. In this case, the alarms are not important for reference. You may find it difficult to locate and remove faults. By alarm correction analysis, the M2000 can shield the repetitive or non-root alarms, and you can obtain useful alarm information. After you understand the principle of alarm correlation analysis, you can use the M2000 to set the correlation rules more accurately.
Correlative Alarms
Correlative alarms are alarms that have correlations between one another. One is the root alarm that raises other alarms. A fault may result in multiple alarms. The non-root alarms do not help in the fault location or analysis. To solve this problem, you can set a condition based on the alarm features, such as the
alarm raised time or physical location to shield the alarms that do not match the condition or reduce the levels of insignificant alarms.
Intermittent Alarms/Repeat Events

If the interval between two clearance times of an alarm is less than the set period of the cleared alarm, the alarm is an intermittent alarm. If the reporting times of an event is more than the set times in the set period, the event is a repeat event. A fault, such as a physical device fault may result in multiple repetitive alarms or events. Such information is redundant. To avoid intermittent alarms or repeat events, you can set a condition. The alarms or events that match the condition are intermittent alarms or repeat events. You can then reduce the levels of such alarms or events. You can also shield them directly.
Simple/Advanced Correlation
In the M2000, the correlation of the intermittent alarms or repeat events is considered as simple correlation alarms, and the correlation of the other alarms is considered as advanced correlation alarms.
Priorities in Correlation Analysis

During correlation analysis, the M2000 determines the priority of a correlation rule, and then takes a proper action.
Example 1:
The priority of an alarm advanced correlation rule is 1000000000. The priority of another alarm advanced correlation rule is 1000000. When an alarm meets both rules, the system performs the first alarm correlation rule first, and then the second correlation rule.
Example 2:
The priority of an alarm advanced correlation rule is 1000000000. The priority of another alarm advanced correlation rule is also 1000000000. When an alarm meets both rules, the system takes the analysis actions based on the sequence in which the two rules are added to the correlation analysis module.
Adding Simple Correlation Rules of Alarms

To filter the intermittent alarms or repeat events and prevent the system running in unstable status, the M2000 provides simple correlation analysis for alarms. Take intermittent alarms as an example, when the alarms reach the preset limit, the M2000 filters or discards them based on the correlation rule.
Context
l
If the clearance interval of the same alarm is less than the preset interval, the alarm is intermittent. The simple correlation rule takes effects only when alarm intervals and intermittence/repeat times match the conditions that you set.
2-52

l
The M2000 discards or save the alarms that are shielded by the correlation rules to the shield database. You can query the shielded alarms in the shield database.
Procedure
Step 1 Choose Monitor > Settings > Simple Correlation . Step 2 In the Simple Correlation window, click Add. Step 3 In the Add Simple Correlation Rule dialog box, set the parameters for correlation rules. 1. 2. 3. 4. Click Choose. In the Select Alarm Name dialog box, select the alarms on which you want to analyze the correlation, and then click OK. Set Interval, Intermittence/Repeat Times and action. Optional: In the Memo text box, set the remarks. Select Enable.
Related References
2.8.39 Parameters for Setting Simple Correlation Rules
Adding Advanced Correlation Rules of Alarms

Through setting the advanced correlation rules of alarms, you can filter the alarms that match the rules or redefine the alarm levels. Therefore, you can reduce the unnecessary alarms or ignore the non-root alarms so that you can handle the major alarms and solve problems quickly.
Context
The M2000 redefine the alarm level or save the alarms that are shielded by the correlation rules to the shield database. You can query the shielded alarms in the shield database.
Procedure
Step 1 Choose Monitor > Settings > Advanced Correlation . Step 2 In the Advanced Correlation window, click New. Step 3 In the Add Advanced Correlation Rule dialog box, set the parameters for correlation rules. 1. 2. 3. Set the correlation conditions: Click Add next to the Correlation Condition group box. Set Alarm Instance A, Alarm Instance B, Property, Condition, and Value. Set the correlation action: Click New next to the Correlation Action group box. Set Alarm Instance, Action, and Value. Set Priority, Memo, and Enable.
Step 4 Click OK. When the correlation rules are enabled and the alarms match the rules, the M2000 executes the relevant correlation actions in sequence. ----End
Related References
2.8.40 Parameters for Setting Advanced Correlation Rules
Modifying Simple Correlation Rules for Alarms

This section describes how to modify the existing simple correlation rules for alarms.
Procedure
Step 1 ChooseMonitor > Settings > Simple Correlation . Step 2 In the Simple Correlation window, you can modify the correlation rules in the following ways: l Click the field of an alarm correlation rule, and then modify it. Then click Apply.
NOTE
The fields displayed in white can be changed. The fields displayed in fields displayed in are already changed but are not used.
cannot be changed. The
Select a relevant alarm correlation rule, and then click Detail. In the Detail Information dialog box, modify the correlation rule. Then click OK.
----End
Modifying Advanced Correlation Rules for Alarms

This section describes how to modify the existing advanced correlation rules for alarms.
Procedure
Step 1 ChooseMonitor > Settings > Advanced Correlation . Step 2 In the Advanced Correlation window, you can modify the correlation rules in the following ways: l Click the field of an alarm correlation rule, and then modify it. Then click Apply.
NOTE
l l
The correlation conditions and actions cannot be modified in this way. The fields displayed in white can be changed. The fields displayed in fields displayed in are already changed but are not used. You can use this method to modify the correlation rules for multiple alarms. cannot be changed. The
Select a relevant alarm correlation rule, and then click Detail. In the Detail Information dialog box, modify the correlation rule. Then click OK.
----End
Example of Using Simple Correlation Rules of Alarms

This section gives an example of using the simple correlation rules of intermittent alarms to describe how to set a simple correlation rule for alarms.
Background
The M2000 receive mass fault alarms that are raised and cleared periodically. These alarms are reduced after the intermittent alarm correlation rules are set.
Operation Guide
To set correlation rules for intermittent alarms, do as follows: 1. 2. 3. Choose Monitor > Settings > Simple Correlation . In the Simple Correlation window, click Add. In the Add Simple Correlation Properities dialog box, set the correlation rule parameters. (1) Click Choose. In the Select Alarm Name dialog box, select the alarms that need correlation analysis, and then click OK. (2) Set Interval to 3, which indicates that the interval between the clearance of two intermittent alarms is three seconds. (3) Set Intermittence / Repeat Times to 5. (4) Set Action to discarding. (5) Select Enable. 4. Click OK.
Example of Using Advanced Correlation Rules of a Single Alarm

This section describes how to set the advanced correlation rules for a single alarm by giving an example.
Background
During the period from 5:00 to 23:00 on September 5th, 2005, the NE Z raises mass critical alarms M during upgrade. These critical alarms do not need be concerned. Therefore, the administrator redefines all the critical alarms M raised during upgrade to warning alarms, so that the alarms M are not concerned. In this example, the administrator redefines the critical alarms M that are raised during the period from 5:00 to 23:00 on September 5th, 2005.
NOTE
This correlation analysis is to obtain the root alarms M, and it does not conflict with the correlation analysis of repeat event alarms or intermittent fault alarms. Therefore, the priority value of this correlation analysis can be lower than that (which is 1000000000) of repeat event alarms or intermittent fault alarms. In this example, the priority is set to 1000000. When you customize Correlation Condition, you can perform correlation analysis only when all the conditions are met. Therefore, do not add indeterminate correlation conditions to a custom correlation rule record. In addition, mass custom correlation analysis may increase the system load. Do not add too many conditions of custom correlation rule analysis.
Operation Guide
To set a single custom alarm instance, do as follows: 1. 2.
Issue 06 (2008-12-16)
Choose Monitor > Settings > Advanced Correlation . In the Advanced Correlation window, click Add.
3.
Set the condition for that the alarms M are generated by NE Z. (1) Click Add next to Correlation Condition. (2) Set the new correlation condition records. In the Alarm Instance A column, select Create Alarm Instance. In the displayed Select Alarm Name dialog box, select the alarm name M, and then click OK. In the Property column, select NE. In the Condition column, select Equal. Click Value. In the displayed Select Alarm Name dialog box, click NE Z, click OK.
4.
Set the raised time of the alarms M later than 5:00, on September 5th, 2005. (1) Click Add next to Correlation Condition. (2) Set the new correlation condition records. In the Alarm Instance A column, select the alarm name M. In the Property column, select Occurrence Time. In the Condition column, select Greater than. Click the Value column. In the Select time dialog box, set the time to 05-09-2005 05:00:00, click OK.
5.
Set the raised time of the alarms M earlier than 23:00, on September 5th, 2005. (1) Click Add next to Correlation Condition. (2) Set the new correlation condition records. In the Alarm Instance Acolumn, select the alarm name M. In the Propertycolumn, select Occurrence Time. IN the Condition column, select Less than. Double-click the Value column. In the Select time dialog box, set the time to 05-09-2005 23:00:00, click OK.
6.
Set the actions of redefining the alarms M. (1) Click Add next to Correlation Action. (2) Set the new correlation condition records. In the Alarm Instancecolumn, select the alarm name M. In the Action column, select Level Redefine. In the Value column, select Warring.
7. 8. 9.
Set Priority to 1000000. Select Enable. In the Add Advanced Correlation Rule dialog box, click OK.
Example of Using Advanced Correlation Rules of Two Alarms

This section describes how to set the advanced correlation rules for two alarms by giving an example.
Background
In the actual application, the link of an NE is faulty, and the NE reports the fault alarm M periodically. In addition, due to the faulty link, this NE or other NEs may raise mass link fault alarms N. The fault alarm M is the root alarm of the alarm N. Therefore, in the actual analysis, the administrator can analyze the alarm causes and handling methods by analyzing the alarm M, and you do not need to analyze the alarm N. The administrator can filter all the alarms N that are raised after the alarm M by adding correlation rule records. In this example, the alarm M must be raised before the alarm N. Therefore, the administrator only need to compare the raised times of the two alarms to determine whether the alarm N meets the filter conditions.
2-56
Issue 06 (2008-12-16)

NOTE
When you customize Correlation Condition, you can perform correlation analysis only when all the conditions are met. Therefore, do not add indeterminate correlation conditions to a custom correlation rule record. In addition, mass custom correlation analysis may increase the system load. Do not add too many conditions of custom correlation rule analysis.
Operation Guide
To set two custom alarm instances, do as follows: 1. 2. 3. Choose Monitor > Settings > Advanced Correlation . In the Advanced Correlation window, click Add. Set the comparison conditions for the alarm M and alarm N. In this instance, the alarm is raised before the alarm N, that is, the raised time of the alarm M is earlier than that of the alarm N. (1) Click Add next to Correlation Condition. (2) Set the new correlation condition records. In the Alarm Instance A column, select Create Alarm Instance. In the displayed Select Alarm Name dialog box, select the alarm name M, and then click OK. In the Alarm Instance B column, select Create Alarm Instance. In the displayed Select Alarm Name dialog box, select the alarm name N, and then click OK. In the Property column, select Occurrence Time. In the Condition column, select Less than. 4. Set the actions for filtering the alarm N. (1) Click Add next to Correlation Action. (2) In the Alarm Instance column, select the alarm name N. In the Action column, select Shielded. 5. 6. 7. Set Priority to 1000000. Select Enable. In the Add Advanced Correlation Rule dialog box, click OK.
2.3.8 Managing Auto-Triggering Script Tasks

The alarm auto-triggering script task realizes partial automation of the routine maintenance work by automatically triggering and executing the shell script file that is set by the user. Through the M2000 client, you can add the auto-triggering tasks, check the task attributes,and check the specific task and the auto-triggering conditions. 2.3.8.1 Creating Auto-Triggering Tasks This task describes how to create an auto-triggering task. Then the M2000 server automatically runs the defined script file to perform routine maintenance when the alarm that meets the requirements of the triggering conditions occurs. In this way, the work efficiency is improved. 2.3.8.2 Viewing the Attributes of Auto-Triggering Tasks This describes how to view the attribute of auto-triggering tasks. On the M2000 client, you can query the basic attributes and triggering conditions of the auto-triggering tasks. 2.3.8.3 Searching Auto-Triggering Tasks The M2000 provides the searching function for auto-triggering tasks. By setting multiple querying conditions, you can quickly locate the auto-triggering task you care about. 2.3.8.4 Searching Auto-Triggering Records
By searching the auto-triggering records, you may know the auto-triggering tasks that are already automatically executed by the server and their detailed information such as the triggering time and task name.
Creating Auto-Triggering Tasks

This task describes how to create an auto-triggering task. Then the M2000 server automatically runs the defined script file to perform routine maintenance when the alarm that meets the requirements of the triggering conditions occurs. In this way, the work efficiency is improved.
Prerequisite
Context
CAUTION
l l
You need to manually send the script files to be triggered to the M2000 server. You can create a maximum of 100 auto-triggering tasks.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed. Step 2 Click New, or right-click the task list and choose New from the shortcut menu.
TIP
You may also select an existing auto-triggering task, and by modifying the task information, you can create an auto-triggering task.
Step 3 In the displayed New Task dialog box, set the basic attributes of the task. 1. 2. In the Task Name field, enter the name of the task. Set the time range and Period. You may set the time using any of the following three ways:
l l l
Directly enter the time. Click Click the or to adjust the time. . In the displayed dialog box, choose the time.
CAUTION
The script to be executed is triggered by the server only when the alarm occurs in the specified time range, and in Period, the date is set to Tuesday. 3. 4. Choose the task running mode from the Run-time Type drop-down list. In the Script File dialog box, enter the absolute path and the name of the script file on the server.
2-58
For example, /export/home/trigger.sh.

NOTE
l l
Based on demands, in the Run-time Param field, you can reset some of the parameters in the script file. In the Remark field, you may enter task description related information.
For details about relevant parameters, see 2.8.41 Parameters for the Basic Attributes of AutoTriggering Tasks. Step 4 Click the Trigger Condition tab, and then click Add.
NOTE
A maximum of 250 triggering condition settings is allowed.
Step 5 Set the NE alarm of the auto-running script file triggered by the server. Step 6 Click OK. The added triggering conditions are displayed in the list of the Trigger Condition tab page. Step 7 Click OK. The added auto-triggering tasks are displayed in the task list of the Triggering Script dialog box. If the alarm set in this task occurs later on, the server will automatically run the script file based on the task running conditions that are already set in the task.
CAUTION
If the triggering conditions that are set are incorrect, for example, if the selected NE does not exist on the actual network, a dialog box indicating error is displayed. At the same time, on the Trigger Condition tab page, the Message field displays the message explaining the detailed reasons why the triggering conditions fail to be created. In this case, you need to click Delete to delete the triggering condition and perform Step 4 through Step 6 to set another triggering condition. ----End
Postrequisite
You may choose Query > Query Record in the Triggering Script window. Then, you can check the running results of the auto-triggering task, For example, the specific time for the triggering task.
Related References
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks 2.8.42 Parameters for Auto-Triggering Conditions 2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script
Viewing the Attributes of Auto-Triggering Tasks

This describes how to view the attribute of auto-triggering tasks. On the M2000 client, you can query the basic attributes and triggering conditions of the auto-triggering tasks.
Prerequisite
l l
You have logged in to the M2000 client. The auto-triggering task exists.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed. Step 2 In the task list, choose the task record whose attribute you need to query. You may either click Refresh or right-click the task list and choose <Refresh to obtain the latest information about the task. In usual cases, the client refreshes the displayed information about the task in real time. Step 3 Double-click the task record. Alternatively, right-click the it and choose Attribute from the shortcut menu or click Attribute. The system displays the Attribute dialog box. Step 4 You can check the detailed information about the auto-triggering task.
l
Basic Attribute tab page: displays the basic attribute of the auto-triggering task. For parameter-related description, refer to 2.8.41 Parameters for the Basic Attributes of AutoTriggering Tasks. Trigger Attribute tab page: displays the trigger attribute of the auto-triggering task. For parameter-related description, refer to 2.8.42 Parameters for Auto-Triggering Conditions.
NOTE
Based on demands, you can modify the auto-triggering task related information, click OK. he modified auto-triggering tasks are displayed in the task list of the Triggering Script dialog box.
----End
Related References
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks 2.8.42 Parameters for Auto-Triggering Conditions 2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script
Searching Auto-Triggering Tasks

The M2000 provides the searching function for auto-triggering tasks. By setting multiple querying conditions, you can quickly locate the auto-triggering task you care about.
Prerequisite
l l
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed. Step 2 Choose Query > Query Task, or right-click the task list and choose Query Task from the shortcut menu.
The Query Task dialog box is displayed. Step 3 Select the check boxes before the related parameters, and then set the querying conditions. By selecting multiple check boxes, you can set multiple querying conditions. For parameterrelated description, refer to 2.8.44 Parameters for Searching Auto-Triggering Tasks. Step 4 Click OK. The auto-triggering task that meets the requirements of the querying conditions is displayed in the task list of the Triggering Script dialog box. ----End
Related References
2.8.44 Parameters for Searching Auto-Triggering Tasks
Searching Auto-Triggering Records

By searching the auto-triggering records, you may know the auto-triggering tasks that are already automatically executed by the server and their detailed information such as the triggering time and task name.
Prerequisite
l l
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed. Step 2 ClickQuery > Query Record. Alternatively, right-click it and choose Query Record from the shortcut menu. The Query Record dialog box is displayed. Step 3 Select the check boxes before the related parameters, and then set the querying conditions. By selecting multiple check boxes, you can set multiple querying conditions. For parameterrelated description, refer to 2.8.45 Parameters for Searching Auto-Triggering Records. Step 4 Click Query. The triggering records are displayed in the Query Result list.
NOTE
You can click Save to save the triggering records to a file.
If the system has never executed auto-triggering tasks, a dialog box is displayed, showing that the querying result is null. ----End
Related References
2.8.45 Parameters for Searching Auto-Triggering Records
2.4 Setting NE Alarms

The M2000 provides the function of alarm shielding and alarm severity redefinition. You can shield unwanted alarms to prevent NEs from reporting them to the M2000. You can also redefine the severity of alarms to make the severity correctly reflect the actual situation. 2.4.1 Shielding an NE Alarm You can shield the alarms that you are not required. Thus, you can prevent the NE from reporting the alarms that must be shielded. In this case, invalid alarm information is reduced, the system stress is decreased, and the efficiency of the system is improved. 2.4.2 Querying the Shielding of an NE Alarm You can query the shielding of an NE alarm that has been sent to the NE. 2.4.3 Modifying the Shielding of an NE Alarm By using this function, you can modify the alarm shielding that is sent to but does not reach the NE. For the shielding of an NE alarm that does not reach the NE, you need to click Apply to make the setting take effect. For the setting that does not reach the NE, the modification has no effect on the NE. 2.4.4 Redefining the Level of an NE Alarm The M2000 enables you to redefine the severity level of an NE alarm. By using this function, you can downgrade the severity level of an alarm that has minimal impact on the system. You can also upgrade the severity level of a major fault alarm. 2.4.5 Querying the Redefinition of an NE Alarm Level You can query an applied alarm level redefinition record with this function. 2.4.6 Modifying the Setting of NE Alarm Level Redefinition This describes how to modify an alarm level redefinition record. 2.4.7 Defining an NE Alarm A newly defined alarm is identified by NE type and alarm ID. Its alarm name, alarm severity level, and alarm type can be different with that on the NE side. The M2000 supports the function of environment monitoring. You can define a new NE alarm, bind it to a port of a cabinet, frame, or slot of an NE, and then externally mount an environment monitoring device on the port. In this case, when the device detects environment exceptions, a real-time alarm is generated on the NE and reported to the M2000. In this way, it can quickly and automatically obtain the exception conditions and guarantee the normal operation. 2.4.8 Binding a User-Defined Alarm This describes how to define the corresponding relations between the user-defined alarms and the signal input ports. When a signal received through a port meets the alarm triggering conditions, the NE reports an alarm to the M2000, and the alarm is bound with a customized name and ID.
2.4.1 Shielding an NE Alarm

You can shield the alarms that you are not required. Thus, you can prevent the NE from reporting the alarms that must be shielded. In this case, invalid alarm information is reduced, the system stress is decreased, and the efficiency of the system is improved.
2-62
Issue 06 (2008-12-16)
Prerequisite
l l l
You have logged in to the M2000 client. You are familiar with the meaning of each alarm. You are authorized to perform the related operation.
Context
The following NEs do not support this function: IWF, SG7000, HLR36, PCU35, PCU33, PCU6000, tMSC, iMSC, MSC, BSC, GT800BSC, BTS, and AHR.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Perform the following operations based on the actual requirement. NEs for Shielding NEs managed by the BSC6000 Other NEs Step 3 Perform the following steps: 1. 2. Click the Object Alarm Shielding tab under Alarm Shielding. Click Add. The Add Object Alarm Shielding dialog box is displayed. 3. 4. Select an object whose alarm needs to be shielded in the Select Object tree. Select an alarm to be shielded from the Select Alarm tree. You can also type the keyword in Search by Name to search for the alarm. You can sort the alarms in the Select Alarm tree by selecting Group by Alarm Type, Group by Alarm Level, or Group by Alarm Category. 5. 6. Click OK. In the Messagedialog box, click OK.
l
Then... Perform Step 3. Perform Step 4.
The Message dialog box shows whether the alarm shielding is successful or failed. If the alarm shielding is failed, the reason is provided. The shielding requirements are directly issued to NEs and are not saved in the database of the NM side.
Step 4 Perform the following steps: 1. 2. Click the NE Alarm Shielding tab under Alarm Shielding. Click Add. The Add Alarm Shielding dialog box is displayed. 3. Select an NE from the Select NE tree. You can also type the keyword in Search by Name to search for the NE.
Issue 06 (2008-12-16)
4. 5.
Select an alarm from the Select Alarm tree. You can also type the keyword in Search by Name to search for the alarm. Click OK. The alarm shielding record to be added is listed on the Alarm Binding tab page. Each record is marked
NOTE
on the left.
The alarm shielding setting is saved on only the M2000. You must click Apply to apply it on the NE.
6.
Click Apply. The alarm shielding setting is applied on the NE. The symbol disappears. An information box is displayed, indicating whether the operation succeeds or fails.
The Shielded Flag in the Add Alarm Shielding dialog box is not configurable. The default setting is Yes. ----End
Related References
2.8.22 Parameters for Shielding an NE Alarm
2.4.2 Querying the Shielding of an NE Alarm

You can query the shielding of an NE alarm that has been sent to the NE.
Prerequisite
l l l
You have logged in to the M2000 client. You are familiar with the meaning of each alarm. You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Perform the following operations based on the actual requirement. Querying Object NEs managed by the BSC6000 Other NEs Step 3 Perform the following steps: 1. 2.
2-64
Then... Perform Step 3. Perform Step 4.
Click the Object Alarm Shielding tab under Alarm Shielding. Click Query.
3. 4.
In the displayed Confirm dialog box, click OK. The Query Object Alarm Shielding dialog box is displayed. In the Root tree, select an NE to query the alarm shielding information. You can also search the NE by entering key words in the Search by Name box. You can select Group by NE Types so that the NEs in the Root tree are displayed by NE types.
5.
Click OK. The queried alarm shielding record is displayed in list in the Object Alarm Shielding tab page. If you need to delete one or multiple alarm shielding records, you can select the corresponding record in the list, and then click Delete or right-click the record and select Delete from the shortcut menu. You can also delete the alarm shielding records in batches by using the Ctrl or the Shift key.
Step 4 Perform the following steps: 1. 2. Click the NE Alarm Shielding tab under Alarm Shielding. Click Query. The Query Alarm Shielding dialog box is displayed. 3. 4. 5. 6. 7. , and select the NE with this alarm filter in the displayed topology tree. Or you Click can also enter directly the NE name. Enter the start alarm ID and the end alarm ID to specify the query range. Enter the maximum number of returned records. Select the alarm level in the Alarm Level tree. Click OK. The queried alarm shielding record is displayed as a list on the Alarm Shielding tab page. ----End
Related References
2.8.14 Parameters for Selecting NE for Query 2.8.21 Parameters for Querying the Shielding of an NE Alarm
2.4.3 Modifying the Shielding of an NE Alarm

By using this function, you can modify the alarm shielding that is sent to but does not reach the NE. For the shielding of an NE alarm that does not reach the NE, you need to click Apply to make the setting take effect. For the setting that does not reach the NE, the modification has no effect on the NE.
Prerequisite
l l l l
You have logged in to the M2000 client. Relevant NEs are properly connected to the M2000. You are authorized to perform the related operation. The related NEs operate properly.
Issue 06 (2008-12-16)
l
At least one alarm shielding record exists.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 In the list of the NE Alarm Shielding tab under Alarm Shielding, select an alarm shielding record. Step 3 Click Modify, or right-click the object group and select Modify from the shortcut menu. The Modify Alarm Shielding dialog box is displayed. Step 4 Refer to 2.8.22 Parameters for Shielding an NE Alarm to reset the alarm shielding. You can modify the Shielded Flag only when modifying the applied alarm shielding. The default setting is Yes. Step 5 Click OK. The user-defined alarms to be modified are listed. The alarm record is marked with left. on the
CAUTION
l
After you modify an alarm shielding record, click Apply to submit this new record to the NE. To modify an applied record, ensure that this record exists. For details, see 2.4.2 Querying the Shielding of an NE Alarm.
Step 6 Click Apply. The modified user-defined alarms are applied to the NE. An information box is displayed, indicating whether the operation is successful. ----End
2.4.4 Redefining the Level of an NE Alarm

The M2000 enables you to redefine the severity level of an NE alarm. By using this function, you can downgrade the severity level of an alarm that has minimal impact on the system. You can also upgrade the severity level of a major fault alarm.
Prerequisite
l l l
You have logged in to the M2000 client. You are familiar with the meaning of each alarm severity level. You are authorized to perform the related operation.
Context
The following NEs do not support this function: SG7000, HLR36, PCU35, PCU33, PCU6000, tMSC, iMSC, MSC, BSC, GT800BSC, BTS, IP Clock Server, and AHR.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Severity Redefinition tab, and click Add. The Add Severity Redefinition dialog box is displayed. Step 3 Select an NE from the Select NE tree. You can also type the keyword in Search by Name to search for the NE. Step 4 Select an NE from the Select Alarm tree. You can also type the keyword in Search by Name to search for the NE. Step 5 Select an alarm severity level from the Redefined Level drop-down list. Step 6 Click OK. The alarm level redefinition record to be added is listed on the Alarm Binding tab page. Each record is marked
NOTE
on the left.
After that, you must click Apply to add the new record to the NE.
Step 7 Click Apply. symbol disappears. An information The alarm level redefinition is applied on the NE and the box is displayed, indicating whether the operation succeeds or fails. ----End
Related References
2.8.24 Parameters for Redefining/Modifying the Level of an NE Alarm
2.4.5 Querying the Redefinition of an NE Alarm Level

You can query an applied alarm level redefinition record with this function.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Severity Redefinition tab, and click Query. The Query Severity Redefinition dialog box is displayed. , and select the NE with this alarm level redefinition in the displayed topology tree. Step 3 Click Alternatively, you can also enter directly the NE name. Step 4 Enter the start alarm ID and the end alarm ID to specify the query range.
Step 5 Enter the maximum number of returned records. Step 6 Select the alarm level in the Alarm Level tree. Step 7 Click OK. The queried records are listed in Severity Redefinition. ----End
Related References
2.8.14 Parameters for Selecting NE for Query 2.8.26 Parameters for Querying the Redefinition of an NE Alarm Level
2.4.6 Modifying the Setting of NE Alarm Level Redefinition

This describes how to modify an alarm level redefinition record.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the related operation. At least one alarm level redefinition record exists.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 In the list on the Alarm Level Redefinition tab page, select an alarm redefinition record. Step 3 Click Modify. Alternatively, right-click and select Modify from the shortcut menu. The Add Alarm Level Redefinition dialog box is displayed. Step 4 Refer to 2.4.4 Redefining the Level of an NE Alarm to reset the alarm level redefinition. Step 5 Click OK. The record to be modified is listed and marked with on the left.
CAUTION
l
After you modify an alarm level redefinition record, click Apply to submit this new record to the NE. Before modifying an applied record, ensure that this record exists. For details, see 2.4.5 Querying the Redefinition of an NE Alarm Level.
Step 6 Click Apply. The modified alarm redefinition record is applied to the NE. An information box is displayed, indicating whether the operation is successful. ----End
Related References
2.4.7 Defining an NE Alarm

A newly defined alarm is identified by NE type and alarm ID. Its alarm name, alarm severity level, and alarm type can be different with that on the NE side. The M2000 supports the function of environment monitoring. You can define a new NE alarm, bind it to a port of a cabinet, frame, or slot of an NE, and then externally mount an environment monitoring device on the port. In this case, when the device detects environment exceptions, a real-time alarm is generated on the NE and reported to the M2000. In this way, it can quickly and automatically obtain the exception conditions and guarantee the normal operation.
Context
The NEs that support this function are NodeB, MSC Server, MGW, and BSC6000. 2.4.7.1 Querying a User-Defined Alarm This describes how to query a user-defined alarm. The attributes of user-defined alarms are stored in the M2000 database. You can query the related information in the database. The attributes of a user-defined alarm are NE type, alarm ID, alarm name, alarm severity level, and alarm type. 2.4.7.2 Adding a User-Defined Alarm This describes how to add a user-defined alarm as required. After a user-defined alarm is added, bind the alarm and the corresponding NE to make the alarm take effect. 2.4.7.3 Modifying a User-Defined Alarm This describes how to modify a user-defined alarm.
Related References
2.8.27 Parameters for User-Defined Alarms
Querying a User-Defined Alarm

This describes how to query a user-defined alarm. The attributes of user-defined alarms are stored in the M2000 database. You can query the related information in the database. The attributes of a user-defined alarm are NE type, alarm ID, alarm name, alarm severity level, and alarm type.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Alarm Definition tab in the User-Defined Alarm dialog box. Step 3 Click Query. The Query User-Defined Alarm dialog box is displayed.
Step 4 Enter the name and ID of the user-defined alarm to be queried. Step 5 Select the NE type and alarm severity level. Step 6 Click OK. The queried user-defined alarms are displayed in the list on the Alarm Definition tab page. ----End
Related References
2.8.14 Parameters for Selecting NE for Query 2.8.28 Parameters for Querying a User-Defined Alarm
Adding a User-Defined Alarm

This describes how to add a user-defined alarm as required. After a user-defined alarm is added, bind the alarm and the corresponding NE to make the alarm take effect.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform the relevant operations on NEs.
Context
The user-defined alarms of NEs can be used to monitor the physical environment of hardware. To make the alarms take effect, you must bind these alarms and specified subracks, slots, and ports. A user-defined alarm must be added on the M2000. Thus, you can bind the alarm and the NEs to be monitored. You can bind a user-defined alarm and NEs in the NE Alarm Setting window. Alternatively, you can bind the user-defined alarm and NEs by running the SET ALMPORT command to send the information such as Cabinet, Subrack, Slot, and Port to NEs. The process for adding a user-defined alarm is the process for defining Alarm Name and Alarm ID of an alarm. If you bind a user-defined alarm and NEs by running an MML command without adding the alarm, the following problems may occur:
l l
The user-defined alarm does not have an Alarm Name. If you repeat the binding operations to bind multiple user-defined alarms and a port by running MML commands, only the last binding operation takes effect.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Setting window is displayed. Step 2 Click the User Defined Alarm > Alarm Definition tab. Step 3 Click Add. The Add User Defined Alarm dialog box is displayed. Step 4 Set the parameters related to a user-defined alarm. 1. 2.
2-70
Select an NE type from the NE Type navigation tree. Set Alarm Name, Alarm ID, and Alarm Level.
Step 5 Click OK. The user-defined alarm to be added is listed on the Alarm Definition tab page. Each record is marked
NOTE
For a NodeB, the information about the user-defined alarm is not sent to the NodeB. For MSCe and MGW, if you select NEs when adding or modifying a user-defined alarm, the information about the modified user-defined alarm is sent to the selected NEs after you click Apply.
Step 6 Click Apply. The ----End icon disappears. A dialog box is displayed, informing you of operation result.
Postrequisite
For details about how to bind a user-defined alarm and an NE, see 2.4.8.2 Adding the Binding Relation of a User-Defined Alarm.
Related References
Modifying a User-Defined Alarm

This describes how to modify a user-defined alarm.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the related operation. At least one user-defined alarm record is available.
Context
CAUTION
The ID and NE type of a user-defined alarm cannot be modified.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Alarm Definition tab in the User-Defined Alarm dialog box. Step 3 Select a user-defined alarm that has been used. Step 4 Click Modify. Alternatively, right-click the object group and choose Modify from the shortcut menu.
The Modify User-Defined Alarm dialog box is displayed. Step 5 Rename the user-defined alarm in the Alarm Name field in the Modify User-Defined Alarm dialog box, if required. Step 6 Select the alarm severity level in the Alarm Level field, if required. Step 7 Click OK. The alarm bindings to be added are listed on the Alarm Definition tab page. Each record is marked
NOTE
After a user-defined alarm is modified, you need to click Apply to make the modification take effect.
Step 8 Click Apply. The modified user-defined alarms are applied to the NE. An information box is displayed, indicating whether the operation succeeds or fails. ----End
Related References
2.4.8 Binding a User-Defined Alarm

This describes how to define the corresponding relations between the user-defined alarms and the signal input ports. When a signal received through a port meets the alarm triggering conditions, the NE reports an alarm to the M2000, and the alarm is bound with a customized name and ID.
Context
The NEs that support this function are NodeB, MSC Server, MGW, and BSC6000. 2.4.8.1 Querying the Binding of a User-Defined Alarm This describes how to query the binding of a user-defined alarm. The binding of a user-defined alarm is stored on the related NE rather than in the M2000 database. You can query an existing binding of a user-defined alarm on an NE. 2.4.8.2 Adding the Binding Relation of a User-Defined Alarm This describes how to add the binding relation of a user-defined alarm as required. 2.4.8.3 Modifying the Binding of a User-Defined Alarm This describes how to modify the binding of a user-defined alarm. 2.4.8.4 Canceling the Binding of a User-Defined Alarm This describes how to cancel the binding of a user-defined alarm, that is, cancel the binding of a user-defined alarm set on the M2000 and not issued to the related NE. This operation does not affect the NE operation. 2.4.8.5 Exporting a User-Defined Alarm Binding Template This describes how to export a user-defined alarm binding template and edit it. After you import the edited alarm binding template, it is added to the list of the Alarm Binding tab page. 2.4.8.6 Importing a User-Defined Alarm Binding Relation
This describes how to import a user-defined alarm binding template to the Alarm Binding tab page. A user-defined alarm binding template can contain the user-defined alarm binding relation of multiple NEs of the same type. The import template enables you to add user-defined alarm binding relations in batches.
Related References
2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm
Querying the Binding of a User-Defined Alarm

This describes how to query the binding of a user-defined alarm. The binding of a user-defined alarm is stored on the related NE rather than in the M2000 database. You can query an existing binding of a user-defined alarm on an NE.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Alarm Binding tab on the User-Defined Alarm in the NE Alarm Settings window. Step 3 On the Alarm Binding tab page, click Query. The Query Alarm Binding dialog box is displayed. Step 4 In the Query Alarm Binding dialog box, click behind NE Name.
Step 5 In the displayed navigation tree, select the NE that the alarm binding to be queried belongs to. Step 6 Type a cabinet number in Cabinet, subrack number in Subrack, slot number in Slot, and port number in Port. Step 7 Click OK. The queried alarm binding is displayed on the Alarm Binding tab page in the NE Alarm Setting window. ----End
Related References
2.8.14 Parameters for Selecting NE for Query 2.8.29 Parameters for Querying the Binding of a User-Defined Alarm
Adding the Binding Relation of a User-Defined Alarm

This describes how to add the binding relation of a user-defined alarm as required.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the relevant operations on NEs. Certain user-defined alarms are already added. For details about how to add a user-defined alarm, see 2.4.7.2 Adding a User-Defined Alarm.
Context
The user-defined alarms of NEs can be used to monitor the physical environment of hardware. To make the alarms take effect, you must bind these alarms and specified subracks, slots, and ports. A user-defined alarm must be added on the M2000. Thus, you can bind the alarm and the NEs to be monitored. You can bind a user-defined alarm and NEs in the NE Alarm Setting window. Alternatively, you can bind the user-defined alarm and NEs by running the SET ALMPORT command to send the information such as Cabinet, Subrack, Slot, and Port to NEs. The process for adding a user-defined alarm is the process for defining Alarm Name and Alarm ID of an alarm. If you bind a user-defined alarm and NEs by running an MML command without adding the alarm, the following problems may occur:
l l
The user-defined alarm does not have an Alarm Name. If you repeat the binding operations to bind multiple user-defined alarms and a port by running MML commands, only the last binding operation takes effect.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Setting window is displayed. Step 2 Click the User Defined Alarm > Alarm Binding tab. Step 3 Click Add. The Add Alarm Binding dialog box is displayed. Step 4 In the Select NE navigation tree in the left pane, click an NE. Alternatively, enter the NE name in the Search by Name field. Select Group by NE Type. Then, the Select NE navigation tree displays the NEs by NE type. Step 5 In the Select Alarm navigation tree in the right pane, click an alarm. Alternatively, enter the alarm name in the Search by Name field. Select Group by Alarm Type, Group by Alarm Level, and Group by Category. Then, the Select Alarm tree displays the alarms by alarm type and alarm severity. Step 6 Set the binding parameters. Step 7 Click OK. The alarm binding relation to be added is listed on the Alarm Binding tab page. Each record is marked .
2-74
Issue 06 (2008-12-16)
CAUTION
After adding an alarm binding relation, you must click Apply to make the settings take effect on an NE. Step 8 Click Apply. The user-defined alarm and the NE are bound, and the icon before the related record disappears. A dialog box is displayed, informing you of the operation result. ----End
Related References
Modifying the Binding of a User-Defined Alarm

This describes how to modify the binding of a user-defined alarm.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the related operation. At least one user-defined alarm binding record is available.
Context
After the binding of an MSCe alarm is applied, it cannot be modified.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Alarm Binding tab in the User-Defined Alarm dialog box. Step 3 Select an alarm binding. Step 4 Click Modify. Alternatively, right-click the binding and choose Modify from the shortcut menu. The Modify Alarm Binding dialog box is displayed. Step 5 In the Modify Alarm Binding dialog box, modify the binding parameters. For detailed description of the parameters, refer to 2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm. Step 6 Click OK. The alarm bindings to be added are listed on the Alarm Binding tab page. Each record is marked .
CAUTION
After adding alarm bindings, you must click Apply to make the settings take effect on the NE. Step 7 Click Apply. The modified user-defined alarms are applied to the NE. An information box is displayed, indicating whether the operation succeeds or fails. ----End
Related References
Canceling the Binding of a User-Defined Alarm

This describes how to cancel the binding of a user-defined alarm, that is, cancel the binding of a user-defined alarm set on the M2000 and not issued to the related NE. This operation does not affect the NE operation.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the related operation. At least one user-defined alarm binding record is available.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is displayed. Step 2 Click the Alarm Binding tab in the User-Defined Alarm dialog box. Step 3 In the list on the Alarm Binding tab page, select one user-defined alarm binding record. Step 4 Click Undo. Alternatively, right-click the record and choose Undo from the shortcut menu. ----End
Exporting a User-Defined Alarm Binding Template

This describes how to export a user-defined alarm binding template and edit it. After you import the edited alarm binding template, it is added to the list of the Alarm Binding tab page.
Prerequisite
You are authorized to perform the associated operations.
Context
The user-defined alarm template varies with the NE type. You can export the template of one NE type at a time.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . Step 2 Click the Alarm Binding tab in the User-Defined Alarm dialog box. Step 3 Click Export Template. You can click Export to export by NE type the records on the Alarm Binding tab page. Step 4 Select the NE type in the Export Alarm Binding Template dialog box. Step 5 Set the save path and file name. Step 6 Click OK. Then, the template with the specified name is saved to the specified path. ----End
Postrequisite
You can edit the template based on your requirement by referring to the examples given in the user-defined alarm template file. After editing the template, you can import it to the Alarm Binding tab page. For details on how to import a user-defined alarm binding template, see 2.4.8.6 Importing a User-Defined Alarm Binding Relation.
Related Tasks
2.4.8.6 Importing a User-Defined Alarm Binding Relation
Importing a User-Defined Alarm Binding Relation

This describes how to import a user-defined alarm binding template to the Alarm Binding tab page. A user-defined alarm binding template can contain the user-defined alarm binding relation of multiple NEs of the same type. The import template enables you to add user-defined alarm binding relations in batches.
Prerequisite
l l
You are authorized to perform the associated operations. The user-defined alarm binding template is available on the local M2000 client.
Context
The user-defined alarm binding template varies with the NE type. You can import the template of one NE type at a time.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . Step 2 Click the Alarm Binding tab in the User-Defined Alarm dialog box. Step 3 Click Import.
You can export an existing user-defined alarm binding or user-defined alarm binding template to a specified directory and then edit it. For details on how to export a user-defined alarm binding template, see 2.4.8.5 Exporting a User-Defined Alarm Binding Template. Step 4 Select the NE type in the Import Alarm Binding Template dialog box. Step 5 Set the path for saving the template file. Step 6 Click OK. The user-defined alarm binding relation is displayed in the list of the Alarm Binding tab. You can click Apply to apply the selected binding to the NE. ----End
Related Tasks
2.4.8.5 Exporting a User-Defined Alarm Binding Template
2.5 Monitoring NE Performance in Real Time

You can monitor in real time the specified object types and instances. In addition, you can display the monitoring results in data tables and figures. You can set filter conditions and display effects for the results. Then you save the results and figures to a file.
Context
NOTE
You can monitor the performance of NEs only after purchasing the license of the monitoring function.
2.5.1 Real-Time Monitoring Performance Counters This part introduces some parameters during the real-time monitoring of NEs. 2.5.2 Starting Real-Time Performance Monitoring This describes how to start the real-time performance monitoring, which consists of creating, viewing, and starting a monitoring task, synchronizing the monitoring data, and setting the monitoring threshold. Currently, the system supports the performance monitoring of HLR, iMSC, MSC Server, BSC32, BSC6000, PCU, RNC, SGSN, GGSN80, and MSC Pool. 2.5.3 Displaying Monitoring Results You can set display parameters of monitoring results. For the convenience of checking the monitoring results, set the filter conditions, thresholds, colors, and backgrounds. 2.5.4 Handling Monitoring Data The handling monitoring data consists of the functions of analyzing trends, scanning data, saving, and printing.
Related References
2.8.5 Interface Description: Performance Monitor
2.5.1 Real-Time Monitoring Performance Counters

This part introduces some parameters during the real-time monitoring of NEs.
Real-Time Monitoring Performance Counters

The concepts pertaining to performance monitoring are as follows:
l
Function Set Includes multiple function subsets related to a certain function of the system. Function Subset Includes multiple monitoring counters related to a certain function of the system. Monitoring Counter Performance measurement counters. You can query the performance information on an NE by creating a monitoring task.
The NE performance monitoring counters are as follows:

l l l l l l l
MSC Server performance monitoring counters, as shown in Table 2-5. RNC performance monitoring counters, as shown in Table 2-6. BSC performance monitoring counters, as shown in Table 2-7. BSC6000 performance monitoring counters, as shown in Table 2-8. GGSN80 performance monitoring counters, as shown in Table 2-9. SGSN performance monitoring counter on the MML interface, as shown in Table 2-10. SGSN performance monitoring counter on the FTP MML interface, as shown in Table 2-11. HLR performance monitoring counters, as shown in Table 2-12. PCU performance monitoring counters, as shown in Table 2-13. iMSC performance monitoring counters, as shown in Table 2-14. MSC Pool performance monitoring counters, as shown in Table 2-15. CDMA Pool performance monitoring counters, as shown in Table 2-16.
l l l l l
For the detailed meaning and the calculation method of the performance counters, refer to Performance Counter Information in NE Reference Information of the online help. For details about how to download the NE reference information, refer to 1.14 Downloading NE Mediation Data to the M2000 Client. Table 2-5 MSC server performance monitoring counters Function Set Function Subset Monitoring Counter Mobile originated success rate Mobile originated answer rate MSC basic service monitoring 2G mobile originated call Seizure traffic Connection traffic Answer traffic 3G mobile originated call Mobile originated success rate Mobile originated answer rate
2-79
Issue 06 (2008-12-16)
Function Set
Function Subset
Monitoring Counter Seizure traffic Connection traffic Answer traffic Mobile terminated success rate Mobile terminated answer rate
2G mobile terminated call
Seizure traffic Connection traffic Answer traffic
3G mobile terminated call
Mobile terminated success rate Mobile terminated answer rate Seizure traffic Connection traffic Answer traffic
Short message service
Initiated short message sending success rate Terminated short message sending success rate Rate of intra MSC handover success
Handover MSC mobile counter monitoring
rate of successful MSC outgoing handover requests rate of successful MSC incoming handover requests
Assign Paging Location update
Rate of assigning success Ratio of paging responses Rate of location update success Originating and incoming times Terminating and outgoing times BHCA value Congestion times Congestion duration Overload times Overload duration Average usage rate
MSC Resource Monitor
CPU usage rate
2-80
Issue 06 (2008-12-16)
Function Set
Function Subset
Monitoring Counter Peak value usage rate Peak value duration
MSC office direction traffic monitoring
Incoming office traffic
Connected ratio Answered ratio Seizure traffic Connection traffic Answer traffic Trunk available ratio Average Traffic Per Line Seizure ratio Connected ratio Answered ratio
Outgoing office traffic
Seizure traffic Connection traffic Answer traffic Trunk available ratio Average Traffic Per Line
MSC trunk traffic monitoring
Trunk office traffic measurement
Connected ratio Answered ratio Seizure traffic Connection traffic Answer traffic Seizure ratio Connected ratio
Trunk outgoing traffic measurement
Answered ratio Seizure traffic Connection traffic Answer traffic
MSC link monitoring
BICC link monitoring
Number of sending messages
Issue 06 (2008-12-16)
2-81
Function Set
Function Subset
Monitoring Counter Number of receiving messages Number of sending bytes Number of receiving bytes Congestion times Congestion duration Unavailable times Unavailable duration Link traffic Average link load
H248 link monitoring
Number of sending messages Number of receiving messages Number of sending bytes Number of receiving bytes Congestion times Congestion duration Unavailable times Unavailable duration Link traffic Average link load
M3UA link monitoring
Number of sending messages Number of receiving messages Number of sending bytes Number of receiving bytes Congestion times Congestion duration Unavailable times Unavailable duration Link traffic Average link load
2-82
Issue 06 (2008-12-16)
Function Set MSC Traffic Monitor
Function Subset MSC Alert Rate
Monitoring Counter Call connected times Seizure times Alert Rate
MSC MTP Signaling Link
MSC MTP SL Load
SL Load
Table 2-6 RNC performance monitoring counters Function Set RNC Monitor Function Subset RNC key counter monitoring Monitoring Counter RRC Connection Setup Success Rate(service) AMR RAB Assignment Success Rate VP RAB Setup Success Rate PS RAB Assignment Success Rate AMR Call Drop Rate VP Call Drop Rate PS Service Drop Rate Soft Handover Success Rate CS Inter-RAT Handover Success Rate(from UTRAN to GSM) PS Inter-RAT Handover Success Rate(from UTRAN to GSM) Inter-Freq Hard Handover Success Rate RNC key counter monitoring RRC Connection Setup Success Rate(service) AMR RAB Assignment Success Rate VP RAB Setup Success Rate PS RAB Assignment Success Rate AMR Call Drop Rate VP Call Drop Rate PS Service Drop Rate CS Inter-RAT Handover Success Rate(from UTRAN to GSM)
Issue 06 (2008-12-16)
2-83
Function Set
Function Subset
Monitoring Counter PS Inter-RAT Handover Success Rate(from UTRAN to GSM) Inter-Freq Hard Handover Success Rate
Table 2-7 BSC performance monitoring counters Function Set NW Level Performance Monitor Function Subset BSC Performance Monitor Monitoring Counter TCH Call-Drop Rate SDCCH Call-Drop Rate TCH Assignment Failure Rate Ratio of paging responses Call Success Rate HO due to UL Quality HO due to DL Quality Network Availability Call Setup Success Rate Daily Total Traffic Maximum Total Traffic Maximum FR-Traffic Maximum HR-Traffic Handover Success Rate Attempted TCH seizures for call RF Assign Success Rate BSC Cell Performance Monitor TCH Congestion Rate TCH Blocking Rate SDCCH Congestion Rate SDCCH Access Success Rate Handover Success Rate Attempted TCH seizures for call SDCCH RF Loss Rate
2-84
Issue 06 (2008-12-16)
Function Set
Function Subset
Monitoring Counter TCH RF Loss Rate
Incoming HO Monitor Outgoing HO Monitor Resource Monitor Link Monitor CPU Resource Monitor SS7 Link Monitor
Incoming HO Success Rate Outgoing HO Success Rate CPU usage rate SS7 Signaling Link Receiving and Sending Rate
Table 2-8 BSC6000 performance monitoring counters Function Set BSC6000 real time monitor Function Subset BSC Monitoring Counter Handover Successfully Rate (Real-Time Monitor) Per BSC Traffic Volume on TCH (Real-Time Monitor) Per BSC Establish Call Successful Rate (Real-Time Monitor) Per BSC TCH Call Drop Rate (Contain Handover) (Real-Time Monitor) Per BSC TCH Congestion Rate (Overflow) (Real-Time Monitor) Per BSC CELL TCH Call Drop Rate (Contain Handover) (Real-Time Monitor) Traffic Volume on TCH (Real-Time Monitor) Per BSC Establish Call Successful Rate (Real-Time Monitor) Handover Successfully Rate (Real-Time Monitor) TCH Congestion Rate (Overflow) (Real-Time Monitor) Table 2-9 GGSN80 performance monitoring counters Function Set Session Service realtime monitor
Issue 06 (2008-12-16)
Function Subset Basic session service
Monitoring Counter PDP context act PDP context act success ratio
2-85
Function Set
Function Subset
Monitoring Counter PDP Context num
Apn session performance
GTPv1 MS activate session request GTPv1 MS act PDP context success ratio GTPv0 MS activate session request GTPv0 MS act PDP context success ratio Active PDP Context
AAA performance realtime monitor
AAA Performance
Authentication request Authentication successful ratio Accounting start request Accounting start successful ratio Accounting stop request Accounting stop successful ratio Real time accounting request Real time accounting ratio
APN AAA Performance
Authentication request Authentication successful ratio Accounting start request Accounting start successful ratio Accounting stop request Accounting stop successful ratio Real time accounting request Real time accounting ratio
Data transfer realtime monitor
Data transfer measurement
Gn Peak Throughput in MB Gi Peak Throughput in MB Gn Uplink in MB Gn Downlink in MB Gi Uplink in MB Gi Downlink in MB
System Resource
System Resource Measurement
Average CPU occupation ratio
2-86
Issue 06 (2008-12-16)
Function Set realtime monitor
Function Subset
Monitoring Counter Peak CPU occupation ratio
Table 2-10 SGSN performance monitoring counter on the MML interface Function Set 2G realtime monitor Function Subset 2G mobility management Monitoring Counter 2G GPRS attach request times 2G GPRS attach success ratio 2G intra-SGSN RAU request times 2G intra-SGSN RAU success ratio 2G inter-RAU request times 2G inter-RAU success ratio 2G session management 2G resource 2G MS init PDP context act 2G MS init PDP context act success ratio 2G average attached users 2G average act PDP context 2G paging 2G packet paging request times 2G packet paging success ratio 3G realtime monitor 3G mobility management 3G GPRS attach request times 3G GPRS attach success ratio 3G intra-SGSN RAU request times 3G intra-SGSN RAU success ratio 3G inter-RAU request times 3G inter-RAU success ratio 3G session management 3G resource 3G MS init PDP context act 3G MS init PDP context act success ratio 3G average attached users 3G average act PDP context 3G paging 3G packet paging request times 3G packet paging success ratio
Issue 06 (2008-12-16)
2-87
Function Set Common realtime monitor
Function Subset CPU resource
Monitoring Counter CPU overload times CPU overload duration CPU congestion times CPU congestion duration Average CPU occupation ratio
Link realtime monitor
MTP link
MTP link send load MTP link receive load MTP link congestion MTP link durations of congestion MTP link durations of unavailable
GTP kbytes sent to GGSN GTP kbytes received from GGSN Downlink data kbytes sent to SNDCP Uplink data kbytes received from SNDCP Downlink data kbytes sent to RNC Uplink data kbytes received from RNC
Table 2-11 SGSN performance monitoring counter on the FTP MML interface Function Set Gb mode realtime monitor Function Subset Gb mode mobility management Monitoring Counter Gb mode GPRS attach request times Gb mode GPRS attach success ratio Gb mode intra-SGSN RAU request times Gb mode intra-SGSN RAU success ratio Gb mode inter-SGSN RAU request times Gb mode inter-RAU success ratio Gb mode session management Gb mode resource Gb mode MS init PDP context act Gb mode MS init PDP context act success ratio Gb mode average attached users Gb mode average act PDP context
2-88
Issue 06 (2008-12-16)
Function Set
Function Subset Gb mode paging
Monitoring Counter Gb mode packet paging request times Gb mode packet paging success ratio
Iu mode realtime monitor
Iu mode mobility management
Iu mode GPRS attach request times Iu mode GPRS attach success ratio Iu mode intra-SGSN RAU request times Iu mode intra-SGSN RAU success ratio Iu mode inter-SGSN RAU request times Iu mode inter-RAU success ratio
Iu mode session management Iu mode resource Iu mode paging
Iu mode MS init PDP context act Iu mode MS init PDP context act success ratio Iu mode average attached users Iu mode average act PDP context Iu mode packet paging request times Iu mode packet paging success ratio
Common realtime monitor
CPU resource
CPU overload times CPU overload duration CPU congestion times CPU congestion duration Average CPU occupation ratio
Link realtime monitor
MTP3 link
MTP3 link send load MTP3 link receive load MTP3 link congestion MTP3 link durations of congestion MTP3 link durations of unavailable
GTP kbytes sent to GGSN GTP kbytes received from GGSN Downlink data kbytes sent to SNDCP Uplink data kbytes received from SNDCP Downlink data kbytes sent to RNC
Issue 06 (2008-12-16)
2-89
Function Set
Function Subset
Monitoring Counter Uplink data kbytes received from RNC
Table 2-12 HLR performance monitoring counters Function Set HLR Link Monitor HLR HDU Monitor Function Subset HLR MTP SL Measurement HLR CPU Measurement Monitoring Counter SL Load CPU usage rate
Table 2-13 PCU performance monitoring counters Function Set NW Level Performance Monitor Function Subset BSC Performance Monitor Monitoring Counter Uplink TBF establishment failure rate Downlink TBF establishment failure rate
Table 2-14 iMSC performance monitoring counters Function Set iMSC Basic Service Monitor Function Subset iMSC Traffic Measurement Monitoring Counter Number of Call Attempts Number of Connected Calls Alert rate iMSC Resource Monitor iMSC VLR Subscribers Number iMSC Mobilerelated Indicators Monitor iMSC Office Traffic Monitor iMSC CPU Load Measurement iMSC VLR Subscribers Number iMSC Traffic Channel Assignment CPU Occupation Ratio
VLR Subscribers Number
Number of Traffic Channel Assignment Successes Number of Traffic Channel Assignment Requests Rate of assigning success
iMSC Office Traffic Measurement
Bidirectional Trunk Incoming Call Seized Traffic Bidirectional Trunk Outgoing Call Seized Traffic
2-90
Issue 06 (2008-12-16)
Function Set
Function Subset
Monitoring Counter Seizure traffic
iMSC Link Monitor
iMSC MTP Signaling Link
Number of Sent Load Number of Received Load Number of All Load
iMSC Trunk Traffic Monitor
iMSC Trunk Traffic Measurement
Bidirectional Trunk Incoming Call Answered Traffic Bidirectional Trunk Outgoing Call Answered Traffic
Table 2-15 MSC Pool performance monitoring counters Function Set Bearer Traffic Function Subset Mobile office direction incoming office traffic Mobile Office Direction Outgoing Office Traffic Global Components MSC Basic Services Call Processing MSC Basic Functions Subscriber SMS Success Rate Ratio of paging responses Rate of location update success Monitoring Counter Seizure traffic Connected ratio Seizure traffic Connected ratio VLR Subscriber of Total SMMO SUCCESS RATE SMMT SUCCESS RATE Ratio of paging responses Success Rate of Location Update
Table 2-16 CDMA Pool performance monitoring counters Function Set Bearer Traffic Function Subset Mobile office direction incoming office traffic Mobile Office Direction Monitoring Counter Seizure traffic Connected ratio Seizure traffic
Issue 06 (2008-12-16)
2-91
Function Set
Function Subset Outgoing Office Traffic
Monitoring Counter Connected ratio LOCAL SUBSCRIBERS SMMO SUCCESS RATE SMMT SUCCESS RATE Ratio of paging responses
Global Components MSC Basic Services Call Processing MSC Basic Functions
Subscriber SMS Success Rate MTC Success Rate Paging Rate Success Rate of Location Update
Rate of location update success
2.5.2 Starting Real-Time Performance Monitoring

This describes how to start the real-time performance monitoring, which consists of creating, viewing, and starting a monitoring task, synchronizing the monitoring data, and setting the monitoring threshold. Currently, the system supports the performance monitoring of HLR, iMSC, MSC Server, BSC32, BSC6000, PCU, RNC, SGSN, GGSN80, and MSC Pool. 2.5.2.1 Viewing Monitoring Task Information This describes how to view monitoring task information. 2.5.2.2 Creating a Monitoring Task This describes how to create a monitoring task. The M2000 provides the monitoring function of performance counters in real time. You can set the monitoring parameters to monitor the changes in NE performance counters. 2.5.2.3 Starting a Monitoring Task This describes how to start a monitoring task to open the interface of the monitoring task and check the changes in the monitoring counters. 2.5.2.4 Synchronizing Monitoring Data After you execute a monitoring task, some monitoring data may be missing caused by some reasons, such as interrupted connection. You can collect back the missing data through this function. 2.5.2.5 Setting Real-Time Monitoring Thresholds This describes how to set the real-time monitoring thresholds. The thresholds can be added, modified, and deleted. 2.5.2.6 Setting Rules for Monitoring Thresholds You can set rules to filter all the threshold offsets that may trigger threshold alarms within the set period of time. Set the time to filter monitoring thresholds. Filtering rules include the date and time. 2.5.2.7 Introduction to Default Monitoring Tasks This describes the default M2000 monitoring tasks, including system tasks and Tip tasks.
2.5.2.8 Monitoring Multiple Counters on the Same Screen You can monitor comparison diagrams for multiple counters or of objects, and counter trend diagrams by setting the objects and object counters to be monitored. This task enables you to browse data analysis diagrams for multiple counters at the same time.
Viewing Monitoring Task Information

This describes how to view monitoring task information.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed. Step 2 Select the Monitor Task tab on the left of the window. If the monitored task is unavailable on the navigation tree, you can right-click System Task or User-Defined Task and choose Refresh to refresh the navigation tree. Step 3 Right-click the task in the navigation tree choose select View Task. The View Task dialog box is displayed. In the dialog box, you can view the detailed information of the task. ----End
Creating a Monitoring Task

This describes how to create a monitoring task. The M2000 provides the monitoring function of performance counters in real time. You can set the monitoring parameters to monitor the changes in NE performance counters.
Prerequisite
Context
l l
A monitoring task consists of system task, Tip task, and user-defined task. The naming rule for the monitoring task tab page is NE name-Monitoring type. For example, RNC32-RNC.
Procedure
Step 1 Choose Monitor > Performance Monitor. The Performance Monitor dialog box is displayed. Step 2 You can choose an NE from the NE View tab page or choose an object group from the Object Set tab page to create a monitoring task.
Issue 06 (2008-12-16)
2-93
Creating Method To... NE view 1. Click the NE view tab on the left part of the interface. 2. Select the NE in the navigation tree. You can press Ctrl or Shift to select multiple NEs or cells of the same NE type. 3. Perform Step 3. Object set 1. Click the ObjectGroup tab on the left part of the interface. 2. Select the object group in the navigation tree. For details, refer to 1.16 Managing User-Defined Object Groups. 3. Perform Step 3. Step 3 Open the Monitor Parameter Setting dialog box. You can perform either of the following operations to open the Monitor Parameter Setting dialog box.
l l
Press and hold the left mouse button to drag the selected NE to the right part of the interface. Right-click multiple objects and choose Start Monitor > User-defined.
If you need to use the default settings, choose Start Monitor > Default. Step 4 Set the monitoring parameters. Click Save as Default. The system automatically saves the current setting as the default one. The setting takes effect when you set the parameters for the same object next time. Step 5 Click OK. A tab page of this monitoring task is created on the right part of the interface to display the detailed information about the monitoring parameters. You can view the monitoring information through the Table Data or Monitor Chart. Step 6 Optional: Check any abnormal information that leads to the failure to create a performance monitoring task. When a performance monitoring task fails to be created, an icon task name on the task tab page. 1. 2. 3. is displayed before the
Right-click the task tab, and then choose Abnormal Information. In the displayed Abnormal Information dialog box, check the information about the NEs that leads to the failure to create a performance monitoring task and the detailed reason. Click Close.
----End
Starting a Monitoring Task

This describes how to start a monitoring task to open the interface of the monitoring task and check the changes in the monitoring counters.
Prerequisite
l

2-94

l
The monitoring task has been successfully created.
Context
l
You can simultaneously start a maximum of eight monitoring tasks on one client. If eight monitoring tasks that have been started exist, new task fails to be started. For each monitoring task, a maximum of 2000 monitoring result records can be displayed on the GUI. All the created tasks are displayed in the navigation tree.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed. Step 2 Select the Monitor Task tab on the left of the window. Step 3 Right-click it and choose Start Monitor.
l
By default, the Table Data tab page displays the historical data, that is, the result data of the monitoring task within four days, and for the BSC6000 monitoring task, the result data within two hours is displayed. If you do not require the historical monitoring data to be displayed, you can right-click the blank area of the tab page and clear the Show History Data from the shortcut menu. If you need to display the monitoring chart, right-click the blank area of the Table Data tab page and choose Display Monitoring Chart from the shortcut menu. In the displayed Set Monitoring Information dialog box, you can set Type of Monitoring Chart, Monitoring Object, and Monitoring Counter, then click OK. The system supports the compare display of multiple counters of the same object, or the compare display of the same counter of multiple objects.
If the monitoring interface is closed, the result is not reported to the client. The monitoring task, however, still runs on the server to ensure that the latest data is reported.
----End
Synchronizing Monitoring Data

After you execute a monitoring task, some monitoring data may be missing caused by some reasons, such as interrupted connection. You can collect back the missing data through this function.
Prerequisite
A monitoring task is started.
Context
If the time segment is longer, the data synchronization task lasts longer.
Procedure
Step 1 Right-click and select Show Monitor Chart in the Table Data tab. Step 2 In Monitor Information Setting, select the icon, monitoring object and monitoring counter.
Step 3 Click OK to view the Monitor Chart tab. Step 4 Right-click the compare chart and select Synchronize. The Select a Time Segment dialog box is displayed. Step 5 Set a time segment for synchronizing the monitoring data. Step 6 Click OK. The displayed dialog box shows whether the synchronization command is successfully delivered. Step 7 Click OK to close the dialog box. ----End
Setting Real-Time Monitoring Thresholds

This describes how to set the real-time monitoring thresholds. The thresholds can be added, modified, and deleted.
Procedure
Step 1 Choose Performance > Monitor Threshold Management . The Monitor Threshold Management window is displayed. Step 2 Select a monitoring task in the navigation tree. The Threshold List displays all thresholds set for the monitoring task. Step 3 Add, modify, or delete monitoring thresholds. Operation Add monitoring thresholds. Procedure 1. In the navigation tree in the Threshold Info, select an object to monitor. 2. Set monitoring threshold parameters for the object. 3. Click Add. The added monitoring thresholds are displayed in the Threshold List. The system refreshes the Threshold List area on all the other clients. Modify monitoring thresholds. 1. Select a set monitoring threshold. 2. In the Threshold Info, reset monitoring threshold parameters. 3. Click Modify. The modified monitoring thresholds are displayed in the Threshold List. The system refreshes the Threshold List area on all the other clients.
2-96
Issue 06 (2008-12-16)
Operation Delete monitoring thresholds.
Procedure 1. Select a set monitoring threshold. Press Shift or Ctrl to select multiple monitoring thresholds at a time. 2. Click Delete. 3. In the displayed Confirm dialog box, click Yes. After a monitoring threshold is deleted, the system automatically refreshes the Threshold List area on all the other clients.
----End
Related References
2.8.50 Parameters for Setting Real-Time Monitoring Thresholds
Setting Rules for Monitoring Thresholds

You can set rules to filter all the threshold offsets that may trigger threshold alarms within the set period of time. Set the time to filter monitoring thresholds. Filtering rules include the date and time.
Context
The set filtering rules apply only to the selected monitoring counters.
Procedure
Step 1 Select Performance > Monitor Threshold Management to view Monitor Threshold Management. Step 2 Select a monitoring task in the navigation tree. The Threshold List displays all thresholds set for the monitoring task. Step 3 Select a set monitoring threshold. Step 4 Click Filter Rules. The Set Rules for Monitoring Thresholds dialog box is displayed. Step 5 Set the date and time. Step 6 Click Set. The displayed dialog box shows the operation results. Step 7 Click OK to close the prompt box. ----End
Related References
2.8.51 Parameters for Setting Rules for Monitoring Thresholds
Introduction to Default Monitoring Tasks

This describes the default M2000 monitoring tasks, including system tasks and Tip tasks.
System Task
A system task is a task configured by the system when you install the M2000. You cannot modify or change the system task. Table 2-17 shows the detailed information about a system task. Table 2-17 System Task Task Name ALL-NET CPU SEIZURE RATIO ALL-NET BICC LINK ALL-NET H248 LINK ALL-NET M3UA LINK Description Performs the performance monitoring of the CPU usage ratio on the entire network. Performs the performance monitoring of the BICC link on the entire network. Performs the performance monitoring of the H248 link on the entire network. Performs the performance monitoring of the M3UA link on the entire network.
Tip Task
A Tip task is a monitoring task customized in Topology Prompt Customizing. It can monitor the specified NE, link, and area.
NOTE
After you customize a Tip task, you can:

l l
Place the cursor on the NE, link, or domain of the created Tip task on the topology view. Then, the monitoring results of the most recent measurement period are displayed. Place the cursor on the NE, link, or domain on the created Tip task again. Then, the monitoring results are refreshed.
Monitoring Multiple Counters on the Same Screen

You can monitor comparison diagrams for multiple counters or of objects, and counter trend diagrams by setting the objects and object counters to be monitored. This task enables you to browse data analysis diagrams for multiple counters at the same time.
Prerequisite
Procedure
Step 1 Choose Monitor > Performance Monitor. The Performance Monitor dialog box is displayed. Step 2 Click the NE view tab on the left part of the interface. Step 3 In the navigation tree, select one or more objects to be monitored. Then, right-click the node and choose Add task to Monitor Panel from the displayed shortcut menu. The Monitor Parameter Setting dialog box is displayed. You can press and hold the Ctrl key to select multiple object nodes of the same type.
Step 4 Set Monitor Object Layer, Detail Data Object Layer, Monitor Type, and Monitor Counter. Step 5 Click OK. The Dashboard Monitor tab page is displayed.
l
In this window, you can monitor the diagrams of multiple counter comparison or of object comparison. In addition, you can view on a real-time basis the performance data reported by NEs on the list under each diagram. You can click Set to set Monitor chart total, Total per page, and Cycle Period(second). After the Cycle is activated, the monitored tasks are displayed in turn based on the preset Cycle Period(second). The number of monitored tasks displayed on each screen is determined by Total per page. You can click Previous or Next to manually switch over between different monitoring pages.
l l
Step 6 Optional: Right-click the monitor window and choose Trend Analysis to set parameters for trend analysis diagrams. For details about parameter settings in the trend analysis, refer to 2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter. You can open a maximum of five trend analysis tab pages at the same time in the monitor window. ----End
2.5.3 Displaying Monitoring Results

You can set display parameters of monitoring results. For the convenience of checking the monitoring results, set the filter conditions, thresholds, colors, and backgrounds.
Context
The monitoring of entities can be displayed through charts and data tables. Charts include monitoring charts and tendency charts. Monitoring charts fall into the following three categories:
l l l
Counter compare charts: show changes of multiple counters of one monitored object. Object compare charts: show changes of one counter of multiple monitored objects. Detail charts: show changes of various counters and objects in multiple separate charts.
2.5.3.1 Setting Filtering Conditions for a Monitoring Table You can set filtering conditions for a monitoring table. Then only the monitoring data that meets the filtering conditions is displayed or hidden. 2.5.3.2 Setting Thresholds for Displaying Counters in a Monitoring Table This task is performed to set thresholds for the monitored counters to show the monitored objects whose counter values exceed the set threshold. 2.5.3.3 Zoom In/Out a Monitoring Chart You can zoom in or out a monitoring chart for better observation of the monitoring data. The detail chart does not support this function. 2.5.3.4 Setting Properties for a Monitoring Chart You can set chart attributes to obtain a satisfied object monitoring chart. 2.5.3.5 Setting Thresholds for Displaying Counters in a Monitoring Chart This task is performed to set the thresholds for the detail chart to show the monitored objects whose counter values exceed the predefined thresholds.
2.5.3.6 Setting a Background Picture for a Monitoring Chart You can set a background picture for a chart to enhance the visual effect of the chart. 2.5.3.7 Setting a Background Color for a Monitoring Chart You can set a background color for a chart to enhance the visual effect of the chart. 2.5.3.8 Setting a Color for a Curve of the Monitoring Chart You can set a color for a curve of the monitoring chart to enhance the visual effect of the chart. 2.5.3.9 Showing Scales in a Monitoring Chart The tick table is used to show the data of a time point in the active monitoring chart. Only the compare chart and tendency chart support this function.
Setting Filtering Conditions for a Monitoring Table

You can set filtering conditions for a monitoring table. Then only the monitoring data that meets the filtering conditions is displayed or hidden.
Context
l
The logical relationship between filtering conditions for object monitoring and filtering conditions for counter monitoring is "AND". You can set zero, one, or more filtering conditions. The relationship between multiple counter filtering conditions can be "OR" or "AND".
Procedure
Step 1 In Performance Monitor, select Table Data. Step 2 In Table Data, right-click and selectFilter Setting. The Filter Setting dialog box is displayed. Step 3 Set filtering parameters. Step 4 Click OK. Set filtering conditions for the counter monitoring in the tables directly. Add or delete counter filtering conditions by clicking the + or -. ----End
Related References
2.8.48 Parameters for Setting Filtering Conditions for a Monitoring Table
Setting Thresholds for Displaying Counters in a Monitoring Table

This task is performed to set thresholds for the monitored counters to show the monitored objects whose counter values exceed the set threshold.
Context
This task sets the data display in the table when the value of a counter is greater than the upper threshold or smaller than the lower threshold.
Procedure
Step 1 In Performance Monitor, select Table Data. Step 2 In Table Data, right-click and select Threshold Setting. The Threshold Setting dialog box is displayed. Step 3 Select a monitored counter, and set the display format of the upper and lower limit. Step 4 Click OK. Click Reset Default. You can cancel the settings through the restoring defaults function. The data in the table is displayed in the default format. ----End
Related References
2.8.53 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Table
Zoom In/Out a Monitoring Chart

You can zoom in or out a monitoring chart for better observation of the monitoring data. The detail chart does not support this function.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart. Step 2 Perform the following operations to zoom in or out the monitor chart or the tendency chart:
l l l
Click Click Click
to zoom in the chart. to zoom out the chart. to restore the original size of the chart.
----End
Setting Properties for a Monitoring Chart

You can set chart attributes to obtain a satisfied object monitoring chart.
Context
l
The curve in the counter compare chart indicates the names of the monitored counters. The curve in the object compare chart consists of names of the monitored objects. When you put the mouse on a sampling point, the system displays the time and value of the data for this point. When counters in multiple units are displayed in one compare chart, single x coordinate and multiple y coordinates are used.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart.
Step 2 Right-click and select Properties. The Property Setting dialog box is displayed. Step 3 Set the properties. Step 4 Click OK. ----End
Related References
2.8.49 Parameters for Setting Properties for a Monitoring Chart
Setting Thresholds for Displaying Counters in a Monitoring Chart

This task is performed to set the thresholds for the detail chart to show the monitored objects whose counter values exceed the predefined thresholds.
Procedure
Step 1 In Performance Monitor, select Monitor Chart. Step 2 Right-click the detail chart and select Threshold Setting. The Detail Chart Threshold Setting dialog box is displayed. Step 3 Select a counter and set thresholds for the counter. Step 4 Click OK. Two threshold lines are drawn in the detail chart according to the upper and lower thresholds. When the value of a monitored counter is greater than the upper threshold or smaller than the lower threshold, the column is regarded as a grained column. ----End
Related References
2.8.52 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Chart
Setting a Background Picture for a Monitoring Chart

You can set a background picture for a chart to enhance the visual effect of the chart.
Context
l l
The format of a background picture can only be GIF, JPG, or PNG. The background picture is displayed, by default, in the same size as that of the compare chart area. The background picture cannot be removed. You can set the background color or set a new background picture to cover the applied background picture.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart. Step 2 Right-click the chart and select Background > picture . The Open dialog box is displayed.
Step 3 Select a background picture. Step 4 Click Open to apply the selected background picture. ----End
Setting a Background Color for a Monitoring Chart

You can set a background color for a chart to enhance the visual effect of the chart.
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart. Step 2 Right-click the chart and choose Background > Color . The Background Setting dialog box is displayed. Step 3 Set the background color. Step 4 ClickOK to make the set background color effective. Click Reset to restore the default background color. ----End
Related References
2.8.47 Parameters for Setting a Background Color for a Monitoring Chart
Setting a Color for a Curve of the Monitoring Chart

You can set a color for a curve of the monitoring chart to enhance the visual effect of the chart.
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart. Step 2 Right-click the chart and choose Line color settings. The Line Color Settings dialog box is displayed. Step 3 Set the color. Step 4 ClickOK. ----End
Showing Scales in a Monitoring Chart

The tick table is used to show the data of a time point in the active monitoring chart. Only the compare chart and tendency chart support this function.
Procedure
Step 1 InPerformance Monitor, selectMonitor Chart or Trend Chart. Step 2 Right-click the chart and select Tick Table. The tick table is displayed in the monitoring chart.
If the displayed monitoring chart already includes the tick table, perform this operation to hide the tick table. ----End
2.5.4 Handling Monitoring Data

The handling monitoring data consists of the functions of analyzing trends, scanning data, saving, and printing. 2.5.4.1 Analyzing the Trend of a Monitoring Counter To analyze the counter trend, you must compare the current data of a monitored counter with the history data of the counter of the same period. 2.5.4.2 Scanning Values of Correlated Monitoring Counters Scan data to view the data about a correlated counter for counter correlation analysis. For example, the put-through rate of a monitored object is detected low for a time point. To analyze causes of the low put-through rate, you should know why the put-through rate is low, what are the counters related to the put-through rate, and what are the values of the related counters. 2.5.4.3 Saving a Monitoring Chart You can save the monitoring chart as a figure. You can also save exported data as a file. 2.5.4.4 Saving a Monitoring Table You can save the current monitoring data by exporting the data to a file. 2.5.4.5 Printing a Monitoring Chart You can print the currently active chart.
Analyzing the Trend of a Monitoring Counter

To analyze the counter trend, you must compare the current data of a monitored counter with the history data of the counter of the same period.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed. Step 2 Select the Monitor Task tab on the left of the window. Step 3 Starting a monitoring task. For details, refer to 2.5.2.3 Starting a Monitoring Task. Step 4 Right-click and select Show Monitor Chart in the Table Data tab. The Monitor Information Setting dialog box is displayed. Step 5 Select the icon, monitoring object, and monitoring counter. The system supports the compare display of multiple counters of the same object, or the compare display of the same counter of multiple objects. Step 6 Click OK. The Monitor Chart tab page is displayed. The compare chart and detail chart of the started monitoring task are displayed. Step 7 In the compare or detail chart, right-click and select Trend Analysis to view the Trend Chart Parameter Setting dialog box.
Step 8 Set parameters for the trend chart. Step 9 Click OK. In the Monitor Task tab, click the Trend Chart tab to see the trend chart. Click the Table Data tab. Right-click and select Show Trend Chart to see the trend chart. You can also see the trend chart through the Trend Chart tab. In the Trend Chart tab, right-click and select Exceptional Value Background for exceptional values. The exceptional values are displayed in background color. In other words, when the value for a time point is greater than the upper value or smaller than the lower value, the counter value is highlighted in a background color. In the Trend Chart tab, right-click and select Modify Diff Values to reset the upper and lower values. The trend chart is refreshed automatically after you modify the upper and lower values. ----End
Related References
2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter
Scanning Values of Correlated Monitoring Counters

Scan data to view the data about a correlated counter for counter correlation analysis. For example, the put-through rate of a monitored object is detected low for a time point. To analyze causes of the low put-through rate, you should know why the put-through rate is low, what are the counters related to the put-through rate, and what are the values of the related counters.
Context
Two types of counters currently support this function, that is , the connected rate and the answer rate.
Procedure
Step 1 Choose Monitor > Performance Monitor. The Performance Monitor window is displayed. Step 2 Click the Monitor Task tab on the left of the window. Step 3 Start a monitoring task. Step 4 Select a monitoring record in Table Data. Step 5 Right-click and select Show Monitor Chart to view the Monitor Information Setting. Step 6 Select the icon, monitoring object, and monitoring counter. Step 7 Click OK. The Monitor Chart tab is displayed. The compare chart and detail chart of the started monitoring task are displayed. Step 8 Perform the following operations to view the data analysis dialog box:
l l
Right-click on the compare chart. Select the counters to be scanned. Select a counter column in the detail counter chart. Right-click the counter and select Data Scanning.
Issue 06 (2008-12-16)
The list displays related counter records in the Analysis Table dialog box. Select a counter record in the Analysis Table tab. Right-click and select Analysis Chart. Data is displayed in pie or column charts in the Analysis Chart tab.
l
The pie chart displays the counter data in a prompt box. The pie chart displays a maximum of 20 counters. When the number of counters exceeds 20, the pie chart displays the first 20 counters sorted by counter value in the descending order. In the Analysis Chart tab, select Analysis Counter to set that the counter data is displayed in the chart. In the Analysis Chart tab, click the Color cell behind the Analysis Counter check box to set the color of the counter to be displayed in the chart. After you switch to another object, the relevant tables and charts are updated automatically.
----End
Saving a Monitoring Chart

You can save the monitoring chart as a figure. You can also save exported data as a file.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart. Step 2 Save the monitoring chart as a figure or a file. Saving Mode Operation
Save as a figure. 1. Right-click the chart and select Save as. The Save dialog box is displayed. 2. Save the chart as a photo. You can save charts only in .JPG format. 3. Click OK. Save as a file. 1. Right-click the chart and select Export Data. The Save dialog box is displayed. 2. Save the chart to a file. You can save the data exported from the chart to a file in .TXT, .XLS, .CSV, or HTML format. 3. Click OK. ----End
Saving a Monitoring Table

You can save the current monitoring data by exporting the data to a file.
Procedure
Step 1 In Performance Monitor, select Table Data. Step 2 Right-click and select Export Data. The Save dialog box is displayed.
Step 3 Save the monitoring data. You can save the data in the current data table into a file of either the HTML, TXT, CSV, or XLS format. Step 4 Click OK. ----End
Printing a Monitoring Chart

You can print the currently active chart.
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart. Step 2 Right-click the chart and select Print. Step 3 Print the chart. ----End
2.6 Integrated Network Monitoring

The M2000 provides integrated network monitoring of the RNC, NodeB, and cells. This function includes managing object groups, monitoring network services, and managing real-time monitoring. Among these three functions, real-time monitoring is the most important. 2.6.1 Basic Knowledge The RAN network monitor enables the M2000 to monitor the RNC, the NodeB, and the cell in a centralized manner. This function monitors the real-time alarms, configuration status, and typical KPIs of the monitored objects. 2.6.2 Managing Monitored Object Groups You add, delete, modify, and rename the object groups. 2.6.3 Monitoring Object Groups You can collect all the MOs that concern you most and form an object group. The object group helps you perform the RAN network monitoring and query of the information, such as configuration status, alarm, and exceeded KPI statistics of the MOs. 2.6.4 Checking Information of Monitored Objects You can view the information of monitoring objects, such as basic configuration, interfaces, and distribution. 2.6.5 Checking the Status of Monitored Objects This task is performed to check alarms and KPI counters of the ENC and the cell object group. 2.6.6 Summarizing Alarms of Monitored Objects The M2000 enables you to collect statistics on RNC and NodeB alarms. By using this function, you can summarize the current fault alarms of the RNC and NodeB.
Issue 06 (2008-12-16)
2-107
2.6.1 Basic Knowledge

The RAN network monitor enables the M2000 to monitor the RNC, the NodeB, and the cell in a centralized manner. This function monitors the real-time alarms, configuration status, and typical KPIs of the monitored objects. 2.6.1.1 Monitored Group You can group objects of the same type such as RNC, NodeB, and cell. An object group can be monitored in real time by the M2000 only after being activated. 2.6.1.2 WRAN Configured Object Model Currently, the objects supporting the function of RAN network monitoring are the RNC, NodeB, and cell. The three objects form a stringent logical structure. 2.6.1.3 Configuration Status of Monitored Objects By monitoring the configuration status of the three WRAN objects, that is, RNC, NodeB, and cell, you can view the status information of the monitored object group. This helps you find out and handle abnormal status. 2.6.1.4 RNC Monitoring Counters You can view the monitoring counters and superstandard classic counters of an RNC monitoring object. When creating an object group, you need set the upper and lower thresholds of monitoring counters. The superstandard classic counters indicate the counter values exceeding set upper and lower thresholds. 2.6.1.5 Cell Monitoring Counters You can view the monitoring counters and superstandard classic counters of a cell monitoring object. When creating an object group, you need set the upper and lower thresholds of monitoring counters. The superstandard classic counters indicate the counter values exceeding set upper and lower thresholds.
Monitored Group
You can group objects of the same type such as RNC, NodeB, and cell. An object group can be monitored in real time by the M2000 only after being activated. By using a monitored group, you can easily check the service information and monitor the monitored group in real time.
Related Tasks
2.6.2 Managing Monitored Object Groups
Related References
2.8.6 Interface Description: Management of Monitored Object Groups
WRAN Configured Object Model

Currently, the objects supporting the function of RAN network monitoring are the RNC, NodeB, and cell. The three objects form a stringent logical structure. The RAN network only monitors RNCs, NodeBs, and cells. Figure 2-6 shows the logical relationship between monitored objects.
Figure 2-6 Model of WRAN configured objects
To better monitor these three kinds of objects, you can group the objects of the same type together.
NOTE
Services depend on the monitored objects. You can view objects to check the monitored services, or locate objects by monitored services.
Configuration Status of Monitored Objects

By monitoring the configuration status of the three WRAN objects, that is, RNC, NodeB, and cell, you can view the status information of the monitored object group. This helps you find out and handle abnormal status.
l
The RNC configuration status is on or off. Whether the RNC is disconnected from the server is the key of M2000 monitoring. The NodeB configuration status is on or off. Whether the NodeB is disconnected from the server is the key of M2000 monitoring. The configuration status of a cell can be blocked, deactivated, and disabled. When a cell is in the inactive state, the cell cannot provide services. When a cell is in the blocked state, the users accessing to the cell are not affected. When a cell is in the disabled state, users cannot access the cell.
Related Tasks
2.6.3.4 Checking Detailed Information of Configuration Status
Related References
2.8.65 Parameters for Configuration Status
RNC Monitoring Counters

You can view the monitoring counters and superstandard classic counters of an RNC monitoring object. When creating an object group, you need set the upper and lower thresholds of monitoring counters. The superstandard classic counters indicate the counter values exceeding set upper and lower thresholds. Table 2-18 describes the RNC monitoring counters. You can view the superstandard classic counters of the RNC in the monitoring list. Table 2-18 RNC Monitoring Counters CounterName RRC Connection Setup Success Rate (service) Definition The number of successful RRC connections/ the number of RRC connection set up requests received by the RNC x 100%
NOTE The number of RRC setup requests refers to the number of requests for initiating services.
AMR RAB Assignment Success Rate
The number of 'AMR RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of AMR RAB assignment requests received by the RNC from the CN x 100% The number of 'VP RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of VP RAB assignment requests received by the RNC from the CN x 100% The number of 'PS RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of PS RAB assignment requests received by the RNC from the CN x 100% The number of AMR service releases initiated by the RNC/the number of AMR service setups x 100% The number of VP service releases initiated by the RNC/the number of VP service setups x 100%
Video Call RAB Assignment Success Rate
PS RAB Assignment Success Rate
AMR Call Drop Rate
VP Call Drop Rate
2-110
Issue 06 (2008-12-16)
CounterName PS Service Drop Rate
Definition The number of PS service releases initiated by the RNC/the number of PS service setups x 100% The number of Active Set Update Complete messages received by the RNC/the number of Active Set Update messages sent by the RNC The number of successful inter-system handovers in CS domain)/(the number of inter-system handovers attempt in CS domain
l
Soft Handover Success Rate
CS Inter-RAT Handover Success Rate(from UTRAN to GSM)
The number of inter-system handover attempts in CS domain is the number RELOCATION REQUIRED messages sent by the RNC to the CN. The number of successful inter-system handovers in CS domain is the number of IU RELEASE COMMAND messages received by the RNC. The value of the reason in the IU RELEASE COMMAND message must be Successful Relocation.
PS Inter-RAT Handover Success Rate(from UTRAN to GSM)
The number of successful inter-system handovers in PS domain)/(the number of inter-system handovers attempt in PS domain
l
The number of inter-system handover attempts in PS domain is the number of CELL CHANGE ORDER FROM UTRAN messages sent by the RNC to the UE. The number of the successful inter-system handovers in PS domain is the number of the received IU RELEASE COMMAND messages. The value of the reason in the IU RELEASE COMMAND message must be Normal Release.
Inter-Freq Hard Handover Success Rate
The number of physical link reconfiguration messages received by the RNC/the number of physical link reconfiguration messages sent by the RNC
Related Tasks
2.6.5.1 Checking Values of RNC Monitoring Counters
Cell Monitoring Counters

You can view the monitoring counters and superstandard classic counters of a cell monitoring object. When creating an object group, you need set the upper and lower thresholds of monitoring
counters. The superstandard classic counters indicate the counter values exceeding set upper and lower thresholds. Table 2-19 describes the monitoring counters of a cell monitoring object. You can view the superstandard classic counters of a cell object group in the monitoring list. Table 2-19 Cell Monitoring Counters CounterName RRC Connection Setup Success Rate (service) Definition The number of successful RRC connections/ the number of RRC connection set up requests received by the RNC x 100%
NOTE The number of RRC setup requests refers to the number of requests for initiating services.
AMR RAB Assignment Success Rate
The number of 'AMR RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of AMR RAB assignment requests received by the RNC from the CN x 100% The number of 'VP RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of VP RAB assignment requests received by the RNC from the CN x 100% The number of 'PS RB setup complete' messages received by the RNC from the UE and the RAB assignment responses sent by the RNC to the CN/the number of PS RAB assignment requests received by the RNC from the CN x 100% The number of AMR service releases initiated by the RNC/the number of AMR service setups x 100% The number of VP service releases initiated by the RNC/the number of VP service setups x 100% The number of PS service releases initiated by the RNC/the number of PS service setups x 100%
Video Call RAB Assignment Success Rate
PS RAB Assignment Success Rate
AMR Call Drop Rate
VP Call Drop Rate
PS Service Drop Rate
2-112
Issue 06 (2008-12-16)
CounterName CS Inter-RAT Handover Success Rate(from UTRAN to GSM)
Definition The number of successful inter-system handovers in CS domain)/(the number of inter-system handovers attempt in CS domain
l
The number of inter-system handover attempts in CS domain is the number RELOCATION REQUIRED messages sent by the RNC to the CN. The number of successful inter-system handovers in CS domain is the number of IU RELEASE COMMAND messages received by the RNC. The value of the reason in the IU RELEASE COMMAND message must be Successful Relocation.
PS Inter-RAT Handover Success Rate(from UTRAN to GSM)
The number of successful inter-system handovers in PS domain)/(the number of inter-system handovers attempt in PS domain
l
The number of inter-system handover attempts in PS domain is the number of CELL CHANGE ORDER FROM UTRAN messages sent by the RNC to the UE. The number of the successful inter-system handovers in PS domain is the number of the received IU RELEASE COMMAND messages. The value of the reason in the IU RELEASE COMMAND message must be Normal Release.
Inter-Freq Hard Handover Success Rate
The number of physical link reconfiguration messages received by the RNC/the number of physical link reconfiguration messages sent by the RNC
Related Tasks
2.6.5.5 Checking the Values of Cell Monitoring Counters

You add, delete, modify, and rename the object groups. 2.6.2.1 Adding Monitored Object Groups You can form an object group for one or more MOs of the same type and specify the monitoring services for the group. 2.6.2.2 Checking Monitoring Parameters of Object Groups You can view the monitoring services and objects of the created object group. 2.6.2.3 Modifying Monitoring Parameters of Object Groups
For a created object group, you can modify the name, monitoring objects, and monitoring services. 2.6.2.4 Modifying Names of Object Groups You can modify the names of the created object groups. 2.6.2.5 Copying Monitored Object Groups You can copy an object group to create another one with the same monitoring objects and services. 2.6.2.6 Suspending Monitored Object Groups This describes how to suspend monitored groups. You can suspend a monitored group that need not be monitored temporarily. The service status of a suspended object group is not monitored by the M2000. 2.6.2.7 Activating Monitored Object Groups This describes how to activate monitored object groups. You can activate a suspended object group so that the M2000 can monitor its service status. 2.6.2.8 Deleting Monitored Object Groups You can delete the unwanted monitored object groups to save the resources. 2.6.2.9 Checking Exceptions of Monitored Object Groups Stopping the configuration or performance service or deleting the object may cause that the system fails to monitor the monitored object groups. The M2000 can analyze the exceptions and you can view the causes on the client.
Related Concepts
2.6.1.1 Monitored Group
Related References
Adding Monitored Object Groups

You can form an object group for one or more MOs of the same type and specify the monitoring services for the group.
Prerequisite
You are authorized to monitor an object group.
Context
The objects in an object group should satisfy the following conditions:
l l
You can view an object. The object type can only be RNC, NodeB or cell. Different objects support different monitoring services. An object cannot belong to the object group that you have defined. In other words, two duplicate monitored objects can only exist in the object groups of different users.
2-114
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Click Add. The Object Group Type dialog box is displayed. Step 3 Enter the name of the object group and choose the type. Step 4 Click Next. The Service Type dialog box is displayed. Step 5 Select the services to be monitored, such as alarm, configuration status, performance KPI, and cell status. Step 6 Click Next. The Object List dialog box is displayed. Select the monitoring objects of the object group. Step 7 Click OK. ----End
Checking Monitoring Parameters of Object Groups

You can view the monitoring services and objects of the created object group.
Prerequisite
l l
You have operation authorities of a object group. At least one monitoring object group is available.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Select an object group.
l l
You can view the monitoring services of the object group in Service Type. You can view all the monitoring objects in Monitored Objects.
----End
Modifying Monitoring Parameters of Object Groups

For a created object group, you can modify the name, monitoring objects, and monitoring services.
Prerequisite
l l
Context
Users including the admin can modify only the object group created by themselves.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Select an object group. Click Modify or right-click it and choose Modify on the shortcut menu. The Object Group Type dialog box is displayed. Step 3 Modify the name of the object group. Step 4 Click Next. The Service Type dialog box is displayed. Step 5 Select the type of the service to be modified. Step 6 Click Next. The Object List dialog box is displayed. Step 7 Select the monitoring objects of the object group. Step 8 Click OK. ----End
Modifying Names of Object Groups

You can modify the names of the created object groups.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Select an object group. Click Rename or right-click it and choose Rename on the shortcut menu. The Rename Object Group dialog box is displayed. Step 3 Modify the name of the object group. Step 4 Click OK. ----End
Copying Monitored Object Groups

You can copy an object group to create another one with the same monitoring objects and services.
Prerequisite
l l
2-116
Context
You can copy the object group created by yourself or by other users. You can copy an object group successfully only when you have operation authorities of all objects in the object group.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Select an object group. Click Copy or right-click it and choose Copy on the shortcut menu. The Copy Object Group dialog box is displayed. Step 3 Name the object group. Step 4 Click OK. ----End
Suspending Monitored Object Groups

This describes how to suspend monitored groups. You can suspend a monitored group that need not be monitored temporarily. The service status of a suspended object group is not monitored by the M2000.
Prerequisite
l l
You have the right to operate the related object groups. At least one monitored object group exists.
Context
l l
A common user can suspend only the self-created object group. The user admin can suspend all the object groups in a system.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Group Management window is displayed. Step 2 Select one or more object groups and click Suspend. Alternatively, right-click the objects and choose Suspend from the shortcut menu. The Confirm dialog box is displayed. Step 3 Click Yes. ----End
Activating Monitored Object Groups

This describes how to activate monitored object groups. You can activate a suspended object group so that the M2000 can monitor its service status.
Prerequisite
l
You have the right to operate the related object groups.

Issue 06 (2008-12-16)
l
At least one monitored object group exists.
Context
NOTE
l l l
A common user can suspend only the self-created object group. The admin user can activate the object groups created by other users. The same user can activate a maximum of six object groups.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Group Management window is displayed. Step 2 Select one or more object groups and click Activate. Alternatively, right-click one or more object groups and choose Activate from the shortcut menu. ----End
Deleting Monitored Object Groups

You can delete the unwanted monitored object groups to save the resources.
Prerequisite
l l
Context
l l
Normal users can delete only the object groups that are created by themselves. The user admin can delete all the object groups.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 Select an object group. Click Delete or right-click it and choose Delete on the shortcut menu. The Confirm dialog box is displayed. Step 3 Click Yes. ----End
Checking Exceptions of Monitored Object Groups

Stopping the configuration or performance service or deleting the object may cause that the system fails to monitor the monitored object groups. The M2000 can analyze the exceptions and you can view the causes on the client.
Prerequisite
Exceptional object groups exist.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog box is displayed. Step 2 In the object list, select a monitoring object. Step 3 Click Exception Cause or right-click it and choose Exception Cause on the shortcut menu. The Exception Cause dialog box is displayed.
TIP
In the RAN Network Monitor window, you can also click current object group.
to query the abnormal information of the
2.6.3 Monitoring Object Groups

You can collect all the MOs that concern you most and form an object group. The object group helps you perform the RAN network monitoring and query of the information, such as configuration status, alarm, and exceeded KPI statistics of the MOs.
Context
NOTE
You can monitor object groups only after purchasing the license of the RAN network monitoring function.
2.6.3.1 Browsing Monitoring Panel You can view the monitoring services of the object group on the integrated monitoring panel. The service information monitored by the RNC and a cell consists of the unacknowledged alarm information, uncleared alarm information, configuration status information, and the information of superstandard classic performance indicators. The service information monitored by the NodeB consists of the unacknowledged alarm information, uncleared alarm information, and configuration status information. 2.6.3.2 Searching for Objects You can query monitoring objects through the quick search method. This method enables you to quickly locate a monitoring object. 2.6.3.3 Checking Detailed Alarm Information You can view the detailed alarm information of the monitored object group. 2.6.3.4 Checking Detailed Information of Configuration Status You can view the information such as the on-off status of the objects in RNC and NodeB monitored object group, and object status and configuration of the objects in cell monitored object group. 2.6.3.5 Checking Detailed Information of Exceptional Counters You can view the detailed information on the exceptional counters of RNC and cell object groups. 2.6.3.6 Checking the Charts of Monitoring Counters You can view the charts of monitoring counters. 2.6.3.7 Blocking/Unblocking Cells
blocking and unblocking are two states of a cell. A blocked cell can be unblocked while an unblocked cell can be blocked.
Browsing Monitoring Panel

You can view the monitoring services of the object group on the integrated monitoring panel. The service information monitored by the RNC and a cell consists of the unacknowledged alarm information, uncleared alarm information, configuration status information, and the information of superstandard classic performance indicators. The service information monitored by the NodeB consists of the unacknowledged alarm information, uncleared alarm information, and configuration status information.
Prerequisite
l l
You are authorized to perform the RAN network monitoring function. The activated monitoring object group is available.
Context
The object group supporting the RAN network monitoring function consists of the RNC, NodeB, and cell. The monitoring panel displays only the activated object groups.
Procedure
Choose Monitor > RAN Network Monitor. The RAN Network Monitor is displayed. You can view the service information of the activated object group in the browse area. ----End
Related References
2.8.8 Interface Description: Monitoring Panel
Searching for Objects

You can query monitoring objects through the quick search method. This method enables you to quickly locate a monitoring object.
Prerequisite
l l
You are authorized to perform RAN network monitoring. The monitoring object to be queried is already created.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Right-click a blank space of the monitoring panel and select Search from the displayed shortcut menu. Step 3 In the Search dialog box, enter the related information of an object to be searched.
The information to be entered includes the object name, object type, search scope, and search style.
TIP
You can press Ctrl+F to activate the dialog box.
Step 4 Click Search. The Search Result panel displays the result.
TIP
By double clicking a piece of result, you can find that it is associated with a specific monitoring object.
----End
Related References
2.8.69 Parameters for Searching for Objects
Checking Detailed Alarm Information

You can view the detailed alarm information of the monitored object group.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an object group. Step 3 Double-click the icon on the monitoring panel. You can view the detailed configuration information of the object group in the list at the bottom. For the descriptions of the parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/NodeB. ----End
Checking Detailed Information of Configuration Status

You can view the information such as the on-off status of the objects in RNC and NodeB monitored object group, and object status and configuration of the objects in cell monitored object group.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a monitored object group.
Step 3 Click the status icon on the monitoring panel. You can view the detailed configuration information of the object group in the detailed information area. ----End
Related Concepts
2.6.1.3 Configuration Status of Monitored Objects
Related References
Checking Detailed Information of Exceptional Counters

You can view the detailed information on the exceptional counters of RNC and cell object groups.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated RNC or cell object group is available, which has one or more exceptional performance counters.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC or Cell monitored object group. Step 3 From the object tree at the bottom left, select a monitored object. Step 4 Click KPI Counter. Then you can view the detailed information of the exceptional counter in the displayed list. For details about descriptions of parameters, refer to 2.8.55 Parameters for Checking Values of RNC Monitoring Counters. ----End
Checking the Charts of Monitoring Counters

You can view the charts of monitoring counters.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated RNC object group is available, which has one or more performance monitoring items.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 Click the monitoring icon. Step 4 In the list under the monitoring panel, right-click a performance monitoring counter and select KPI Curve from the shortcut menu. Then the chart of performance counters is displayed. ----End
Blocking/Unblocking Cells
blocking and unblocking are two states of a cell. A blocked cell can be unblocked while an unblocked cell can be blocked.
Prerequisite
l l
The current user is authorized to perform RAN network monitoring. The activated cell object group is available. The number of blocked or unblocked cells cannot be null.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a cell monitoring object group. Step 3 Click the configuration status pane. The icons of locking and unlocking are illustrated at the right side of the pane. Step 4 In the sell list, select a cell object. Step 5 Right-click and select Unblock or block. ----End
2.6.4 Checking Information of Monitored Objects

You can view the information of monitoring objects, such as basic configuration, interfaces, and distribution.
Context
NOTE
You can check the information of the monitored objects only after purchasing the license of the RAN network monitoring function.
2.6.4.1 Checking the Information on Basis RNC Configuration This task describes how to check the basic configuration information, such as object name, NE type, and IP address, on the monitored object. 2.6.4.2 Checking the Distribution of NodeB and Cells on the RNC You can view the distribution of NodeB and cells on the RNC, such as subrack No. of NodeB, serial number, and number of cells. 2.6.4.3 Checking the Information on the Iu/Iur of the RNC
You can view the basic configuration information on the Iu/Iur of the RNC. 2.6.4.4 Checking the Information on Specified Links of the Iu/Iur Interface You can view the alarm information on a specified link of the Iu/Iur interface of RNC. 2.6.4.5 Checking the Information on the Iub Interface of the RNC You can view the information such as the link and port on the Iub interface of the RNC. 2.6.4.6 Checking the Information on Specified Links of the Iub Interface You can view the alarm information on a specified link of the Iub interface of RNC. 2.6.4.7 Checking the Information on Basic NodeB Configuration You can view the basic configuration information of the NodeB, such as object name, NE type, and IP address. 2.6.4.8 Checking the Information on Basic Cell Configuration You can view the information on basic cell configuration, such as cell name, cell ID, and PSCH power. 2.6.4.9 Checking the Information on CCH Configuration This task is performed to check the basic information on the public channel configuration of cells, such as cell name, cell ID, and maximum transmit power. 2.6.4.10 Checking the Information on Neighbors The task is performed to check the information on the neighboring relation between cells.
Checking the Information on Basis RNC Configuration

This task describes how to check the basic configuration information, such as object name, NE type, and IP address, on the monitored object.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one RNC monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object . Step 4 View the basic configuration information on the Attribute tab page. For descriptions of the parameters for basic RNC configuration, refer to 2.8.63 Parameters for Checking the Information on Basic NodeB Configuration. ----End
Related References
2.8.56 Parameters for Checking the Information on Basic RNC Configuration
2-124
Issue 06 (2008-12-16)
Checking the Distribution of NodeB and Cells on the RNC

You can view the distribution of NodeB and cells on the RNC, such as subrack No. of NodeB, serial number, and number of cells.
Prerequisite
l l
You are authorized to perform the RAN network monitoring. At least one RNC monitored object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object. Step 4 Click Distributing NodeBs and Cells to view the related information. For descriptions of the distribution of NodeBs and Cells, refer to 2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC. ----End
Related References
2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC
Checking the Information on the Iu/Iur of the RNC

You can view the basic configuration information on the Iu/Iur of the RNC.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one RNC monitoring object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object group. Step 4 Click Iu/Iur Interface. Select a signaling point from Destination Signaling Point. Step 5 Click Attribute and view the basic configuration information on Iu/Iur. For details of Iu/Iur attribute parameters, refer to 2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC. ----End
Related References
2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC
Checking the Information on Specified Links of the Iu/Iur Interface

You can view the alarm information on a specified link of the Iu/Iur interface of RNC.
Prerequisite
l l
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object group. Step 4 Click Iu/Iur Interface, and select a signaling point from Destination Signaling Point. Step 5 View the link information. For descriptions of parameters, refer to 2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface. ----End
Related References
2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface
Checking the Information on the Iub Interface of the RNC

You can view the information such as the link and port on the Iub interface of the RNC.
Prerequisite
l l
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object group. Step 4 Click the Iub Interface tab to view the basic configuration information. ----End
Related References
2.8.59 Parameters for Checking the Information on the Iub Interface of the RNC
Checking the Information on Specified Links of the Iub Interface

You can view the alarm information on a specified link of the Iub interface of RNC.
Prerequisite
l l
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitored object group. Step 3 From the object tree at the bottom left, select an RNC monitored object group. Step 4 Click Iub Interface to view the information on the RNC object group. For descriptions of Iub Interface parameters, refer to 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface. ----End
Related References
2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface
Checking the Information on Basic NodeB Configuration

You can view the basic configuration information of the NodeB, such as object name, NE type, and IP address.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a NodeB monitored object group. Step 3 From the object tree at the bottom left, select a NodeB monitored object group. Step 4 Click the Attribute tab to view the information on basic NodeB configuration. For descriptions of the parameters for the NodeB, refer to 2.8.63 Parameters for Checking the Information on Basic NodeB Configuration. ----End
Related References
2.8.63 Parameters for Checking the Information on Basic NodeB Configuration
Checking the Information on Basic Cell Configuration

You can view the information on basic cell configuration, such as cell name, cell ID, and PSCH power.
Prerequisite
l l
You are authorized to perform the RAN network monitoring. At least one cell monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a cell monitored object group. Step 3 From the object tree at the bottom left, select a cell monitored object. Step 4 Click the Attribute tab to view the basic configuration information. For descriptions of parameters, refer to 2.8.64 Parameters for Checking the Information on Basic Cell Configuration. ----End
Related References
2.8.64 Parameters for Checking the Information on Basic Cell Configuration
Checking the Information on CCH Configuration

This task is performed to check the basic information on the public channel configuration of cells, such as cell name, cell ID, and maximum transmit power.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one active cell object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Select an active cell object group on the monitoring panel. Step 3 Select an active cell object in the object tree to the lower left. Step 4 Click the Public Channel Configuration tab to view the basic configuration information of the common channel of the cell object. For descriptions of parameters, refer to 2.8.66 Parameters for Checking the Information on CCH Configuration. ----End
Related References
2.8.66 Parameters for Checking the Information on CCH Configuration
Checking the Information on Neighbors

The task is performed to check the information on the neighboring relation between cells.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one active cell object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Select an active cell object group on the monitoring panel. Step 3 Select an active cell object in the object tree to the lower left. Step 4 Click Neighboring Relation to view the neighboring relation of the cell object. For details of parameters about the neighboring relation between cells, refer to 2.8.67 Parameters for Checking the Information on Neighbors. ----End
Related References
2.8.67 Parameters for Checking the Information on Neighbors
2.6.5 Checking the Status of Monitored Objects

This task is performed to check alarms and KPI counters of the ENC and the cell object group.
Context
NOTE
You can check the status of the monitored objects only after purchasing the license of the RAN network monitoring function.
2.6.5.1 Checking Values of RNC Monitoring Counters This task is performed to view the values of RNC monitoring counters. 2.6.5.2 Checking the E1/T1 Status of the RNC This task is performed to check the E1T1 status of the RNC object group. 2.6.5.3 Checking the Current Alarm Information on Specified Links of the Iu/Iur Interface This task is performed to check the current alarm information on specified links of the Iu/Iur interface. 2.6.5.4 Checking the Current Alarm Information on Specified Links of the Iub Interface This task is performed to check the current alarm information on specified links of the Iub interface. 2.6.5.5 Checking the Values of Cell Monitoring Counters You can view the monitoring the values of cell monitoring counters. 2.6.5.6 Checking the Current Alarms of the Cell You can view the current alarms of the cell.
Checking Values of RNC Monitoring Counters

This task is performed to view the values of RNC monitoring counters.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one active RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC object group . Step 3 From the object tree at the bottom left, select an RNC object . Step 4 Click KPI Counter to check the KPI of the RNC object group. For details of KPI Counter parameters, refer to 2.8.55 Parameters for Checking Values of RNC Monitoring Counters. ----End
Related References
2.8.55 Parameters for Checking Values of RNC Monitoring Counters 2.6.1.4 RNC Monitoring Counters
Checking the E1/T1 Status of the RNC

This task is performed to check the E1T1 status of the RNC object group.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Select an active RNC object group on the monitoring panel. Step 3 Select an active RNC object in the object tree to the lower left. Step 4 Click E1T1 Status to check the E1/T1 status of the RNC object group. For descriptions of parameters, refer to 2.8.61 Parameters for Checking the E1/T1 Status of the RNC. ----End
Related References
2.8.61 Parameters for Checking the E1/T1 Status of the RNC
Checking the Current Alarm Information on Specified Links of the Iu/Iur Interface
This task is performed to check the current alarm information on specified links of the Iu/Iur interface.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Select an active RNC object group on the monitoring panel. Step 3 Select an active RNC object in the object tree to the lower left. Step 4 Click Iu/Iur Interface and select a link. Step 5 Click Current Alarm to check the alarm information on the current link. For details of alarm parameters about the current links of the Iu/Iur interface, refer to 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface. ----End
Checking the Current Alarm Information on Specified Links of the Iub Interface
This task is performed to check the current alarm information on specified links of the Iub interface.
Prerequisite
l l
You are authorized to perform the RAN network monitoring. At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 Select an active RNC object group on the monitoring panel. Step 3 Select an active RNC object in the object tree to the lower left. Step 4 Click Iub Interface and select a link. Step 5 Click Current Alarm to check the alarm information on the current link. For details of alarm parameters about the current links of the Iub interface, refer to 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface. ----End
Checking the Values of Cell Monitoring Counters

You can view the monitoring the values of cell monitoring counters.
Prerequisite
l l
You are authorized to perform the RAN network monitoring. At least one cell monitored object is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a cell monitored object group. Step 3 From the object tree at the bottom left, select a cell monitoring object. Step 4 Click KPI Counter to view the detailed information of KPI counters. For descriptions of the parameters, refer to 2.8.68 Parameters for Checking the Values of Cell Monitoring Counters. ----End
Related References
2.8.68 Parameters for Checking the Values of Cell Monitoring Counters 2.6.1.5 Cell Monitoring Counters
Checking the Current Alarms of the Cell

You can view the current alarms of the cell.
Prerequisite
l l
You are authorized to perform the RAN network monitoring. At least one cell monitored object is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a cell monitored object group. Step 3 From the object tree at the bottom left, select a cell monitored object. Step 4 Click Current Alarm to view the alarm statistics of the cell. For descriptions of parameters, refer to 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface. ----End
2.6.6 Summarizing Alarms of Monitored Objects

The M2000 enables you to collect statistics on RNC and NodeB alarms. By using this function, you can summarize the current fault alarms of the RNC and NodeB.
Context
NOTE
You can summarize the alarms of monitored groups only after purchasing the license of the RAN network monitoring function.
2.6.6.1 Summarizing RNC Alarms by Alarm Severity You can measure all the current alarms of the RNC according to alarm levels. 2.6.6.2 Summarizing RNC Alarms by Alarm ID You can measure all the current alarms of the RNC according to alarm IDs. 2.6.6.3 Summarizing RNC Alarms by NodeB A part of RNC alarms come from the NodeBs managed by the RNC in the monitoring object group. By measuring the TopN alarms of the NodeBs under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of NodeBs according to generated alarms. The NodeB with most alarms is classified as Top1. 2.6.6.4 Summarizing RNC Alarms by Cell A part of RNC alarms come from the cells managed by the RNC in the monitoring object group. By measuring the TopN alarms of the cells under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of cells according to generated alarms. The cell with most alarms is classified as Top1. 2.6.6.5 Summarizing RNC Alarms by SAAL Link A part of RNC alarms come from the SAAL links managed by the RNC in the monitoring object group. By measuring the TopN alarms of the SAAL links under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of SAAL links according to generated alarms. The SAAL link with most alarms is classified as Top1. 2.6.6.6 Summarizing RNC Alarms by E1/T1 Link A part of RNC alarms come from the E1/T1 links managed by the RNC in the monitoring object group. By measuring the TopN alarms of the E1/T1 links under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of E1/T1 links according to generated alarms. The E1/T1 link with most alarms is classified as Top1. 2.6.6.7 Summarizing NodeB Alarms by Alarm Severity You can measure all the current alarms of the NodeB according to alarm levels. 2.6.6.8 Summarizing NodeB Alarms by Alarm ID You can measure all the current alarms of the NodeB according to alarm IDs.
Summarizing RNC Alarms by Alarm Severity

You can measure all the current alarms of the RNC according to alarm levels.
Prerequisite
l l
You are authorized to perform RAN network monitoring. At least one activated RNC monitoring object group are available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitoring object group.
Step 3 Select an RNC object from the object tree to the lower left. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by Level. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the current alarms of the RNC NE Time: is the actual time of the RNC and is used to measure the current alarms
Step 7 Set start time for the statistical calculation. By default, all the alarms in the database are measured. Step 8 Click Statistic. On the lower panel, you can view the alarms calculated according to alarm levels. ----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Summarizing RNC Alarms by Alarm ID

You can measure all the current alarms of the RNC according to alarm IDs.
Prerequisite
l l
You are authorized to perform RAN network monitoring. The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitoring object group. Step 3 Select an RNC object from the object tree to the lower left. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by ID. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure RNC alarms NE Time: is the actual time of the RNC and is used to measure RNC alarms
Step 7 Set start time for statistical calculation.

If you do not set start time, use the default system setting. Step 8 Click Statistic. On the lower panel, you can view the alarms calculated according to alarm IDs. ----End
Related References
Summarizing RNC Alarms by NodeB

A part of RNC alarms come from the NodeBs managed by the RNC in the monitoring object group. By measuring the TopN alarms of the NodeBs under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of NodeBs according to generated alarms. The NodeB with most alarms is classified as Top1.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitoring object group. Step 3 Select an RNC object from the object tree to the lower left. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by TopN of NodeB. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the first n alarms of the RNC NE Time: is the actual time of the RNC and is used to measure the first n alarms
Step 8 Set start time for statistical calculation. If you do not set start time, use the default setting. Step 9 Click Statistics. On the lower panel, you can view the alarms calculated according to according to the first n alarms of the NodeB. ----End
Related References
Summarizing RNC Alarms by Cell

A part of RNC alarms come from the cells managed by the RNC in the monitoring object group. By measuring the TopN alarms of the cells under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of cells according to generated alarms. The cell with most alarms is classified as Top1.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitoring object group. Step 3 Select an RNC object from the object tree to the lower left. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by TopN of Cell. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the first n alarms of the RNC NE Time: is the actual time of the RNC and is used to measure the first n alarms of the RNC
Step 8 Set start time for statistical calculation. If you do not set start time, use the default setting. Step 9 Click Statistic. On the lower panel, you can view the alarms calculated according to the first n alarms of a cell. ----End
Related References
Summarizing RNC Alarms by SAAL Link

A part of RNC alarms come from the SAAL links managed by the RNC in the monitoring object group. By measuring the TopN alarms of the SAAL links under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of SAAL links according to generated alarms. The SAAL link with most alarms is classified as Top1.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an RNC monitoring object group. Step 3 From the object tree in the left lower part, select an RNC object. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by TopN of SAAL. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the first n alarms of the RNC NE Time: is the actual time of the RNC and is used to measure the first n alarms of the RNC
Step 8 Set start time for the statistical calculation. If you do not set start time, use the default setting. Step 9 Click Statistics. On the lower panel, you can view the alarms calculated according to the first n alarms of the SAAL link. ----End
Related References
Summarizing RNC Alarms by E1/T1 Link

A part of RNC alarms come from the E1/T1 links managed by the RNC in the monitoring object group. By measuring the TopN alarms of the E1/T1 links under the RNC, you can collect the statistics of RNC alarms. TopN indicates the ordering of E1/T1 links according to generated alarms. The E1/T1 link with most alarms is classified as Top1.
Prerequisite
l l
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitoring object group. Step 3 From the object tree in the left lower part, select an RNC object. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by TopN of E1T1. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the first n alarms of an E1/T1 link NE Time: is the actual time of the RNC and is used to measure the first n alarms of the RNC
Step 8 Set start time for the statistical calculation. If you do not set start time, use the default setting. Step 9 Click Statistic. On the lower panel, you can view the alarms calculated according to the first n alarms of an E1/ T1 link. ----End
Related References
Summarizing NodeB Alarms by Alarm Severity

You can measure all the current alarms of the NodeB according to alarm levels.
Prerequisite
l l
You are authorized to perform RAN network monitoring. The activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select a NodeB monitoring object group. Step 3 From the object tree in the left lower part, select a NodeB object. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by Level. For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/ NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics.
Two time types are available. You can set one as required.
l l
Server Time: is used to measure the current alarms of the NodeB NE Time: is the actual time of the NodeB and is used to measure the current alarms
Step 8 Set start time for the statistical calculation. By default, only all the alarms in the database are measured. Step 9 Click Statistic. On the lower panel, you can view the alarms calculated according to alarm levels. ----End
Related References
Summarizing NodeB Alarms by Alarm ID

You can measure all the current alarms of the NodeB according to alarm IDs.
Prerequisite
l l
You are authorized to perform RAN network monitoring. The activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed. Step 2 On the monitoring panel, select an NodeB monitoring object group. Step 3 From the object tree in the left lower part, select an NodeB object. Step 4 Click Alarm Statistics. Step 5 In Statistic Style, select Statistic by ID. For detailed description of the parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/NodeB. Step 6 In TopN, set a number. Step 7 Set a time type for statistics. Two time types are available. You can set one as required.
l l
Server Time: is used to measure the first n alarms of the NodeB. NE Time: is the actual time of the NodeB and is used to measure the first n alarms of the NodeB.
Step 8 Set start time for the statistical calculation. Step 9 Click Statistic. On the lower panel, you can view the alarms calculated according to alarm IDs. ----End
Related References
2.7 NM System Monitoring

The M2000 network element management system is the uniform management platform of the Huawei mobile network. It uniformly manages the mobile network elements manufactured by Huawei. On the M2000 client, you can monitor the operational status of the NM system, such as the status information about the memory, CPU, hard disks, database, processes, and services. In addition, you can set the alarm threshold of the server. 2.7.1 Setting Monitoring Parameters You can set thresholds for the performance monitoring, hard disk monitoring, database monitoring, and service monitoring. When the threshold is reached, the M2000 raises an alarm. 2.7.2 Monitoring the M2000 Performance Status You can monitor the status of the M2000 server performance to view the information on the operating system, memory usage, and CPU usage, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000. 2.7.3 Monitoring the M2000 Hard Disk Status You can monitor the status of the M2000 server hard disk to view the information such as the total space and usage of the hard disk, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000. 2.7.4 Monitoring the M2000 Database Status You can monitor the status of the M2000 server database to view the information such as the database name, server name, and database status, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000. 2.7.5 Monitoring the M2000 Service Status You can monitor the status of the M2000 server services to view the information such as the service name and service status, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000. 2.7.6 Monitoring the M2000 Process Status You can monitor the status of the M2000 server processes to view the information such as the process name, process ID, and number of threads, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
2.7.1 Setting Monitoring Parameters

You can set thresholds for the performance monitoring, hard disk monitoring, database monitoring, and service monitoring. When the threshold is reached, the M2000 raises an alarm. 2.7.1.1 Relation Between Threshold and Alarm You can set alarm thresholds for the M2000. When the CPU usage, memory usage, hard disk usage, or database usage of the M2000 exceeds the preset alarm threshold, a relevant alarm is raised, and the corresponding icon of the alarm is displayed in red. After the alarm is sent, if the CPU usage, memory usage, hard disk usage, or database usage is less than the preset threshold, a corresponding cleared alarm is sent, and the corresponding icon of the alarm is displayed in green. 2.7.1.2 Setting the Parameters for the M2000 Performance Monitoring
You can set the parameters for the M2000 performance monitoring to specify the threshold of the CPU usage, memory usage, and refresh period of the performance monitoring. When the CPU usage and memory usage reach the thresholds, the M2000 raises corresponding alarms, and the corresponding icon on the Performance Monitor tab is displayed in red. 2.7.1.3 Setting the Parameters for the M2000 Hard Disk Monitoring You can set the parameters for the M2000 hard disk monitoring to specify the threshold of the hard disk usage and the refresh period of the hard disk monitoring. When the M2000 hard disk usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the Hard Disk Monitor tab is displayed in red. 2.7.1.4 Setting the Parameters for the M2000 Database Monitoring You can set the parameters for the M2000 database monitoring to specify the threshold of the database usage and the refresh period of the database monitoring. When the M2000 database usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the Database Monitor tab is displayed in red. 2.7.1.5 Setting the Parameters for the M2000 Service Monitoring By setting services, you can monitor parameters, specify the displayed prompts of the service monitoring, and refresh the interval. After the displayed monitoring information is set and when the service is changed, the corresponding prompts are displayed. At the same time, the service is updated according to the specified interval. You can set the parameters for the M2000 service monitoring to specify the service refresh interval. When the service refresh interval reaches the threshold, the M2000 refreshes the monitored services.
Related References
2.8.70 Parameters for Setting Thresholds of the M2000 Server
Relation Between Threshold and Alarm

You can set alarm thresholds for the M2000. When the CPU usage, memory usage, hard disk usage, or database usage of the M2000 exceeds the preset alarm threshold, a relevant alarm is raised, and the corresponding icon of the alarm is displayed in red. After the alarm is sent, if the CPU usage, memory usage, hard disk usage, or database usage is less than the preset threshold, a corresponding cleared alarm is sent, and the corresponding icon of the alarm is displayed in green.
Setting the Parameters for the M2000 Performance Monitoring

You can set the parameters for the M2000 performance monitoring to specify the threshold of the CPU usage, memory usage, and refresh period of the performance monitoring. When the CPU usage and memory usage reach the thresholds, the M2000 raises corresponding alarms, and the corresponding icon on the Performance Monitor tab is displayed in red.
Procedure
Step 1 Choose Monitor > System Monitor > Configuration . Step 2 In the System Monitor Settings window, click the Performance Monitor tab to set the property values. Step 3 Click OK. ----End
Related References
Setting the Parameters for the M2000 Hard Disk Monitoring

You can set the parameters for the M2000 hard disk monitoring to specify the threshold of the hard disk usage and the refresh period of the hard disk monitoring. When the M2000 hard disk usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the Hard Disk Monitor tab is displayed in red.
Procedure
Step 1 Choose Monitor > System Monitor > Configuration . Step 2 In the System Monitor Settings window, click the Hard Disk Monitor tab to set the property values. Step 3 Click OK. ----End
Related References
Setting the Parameters for the M2000 Database Monitoring

You can set the parameters for the M2000 database monitoring to specify the threshold of the database usage and the refresh period of the database monitoring. When the M2000 database usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the Database Monitor tab is displayed in red.
Procedure
Step 1 Choose Monitor > System Monitor > Configuration . Step 2 In the System Monitor Settings window, click the Database Monitor tab to set the property values. Step 3 Click OK. ----End
Related References
Setting the Parameters for the M2000 Service Monitoring

By setting services, you can monitor parameters, specify the displayed prompts of the service monitoring, and refresh the interval. After the displayed monitoring information is set and when the service is changed, the corresponding prompts are displayed. At the same time, the service is updated according to the specified interval. You can set the parameters for the M2000 service monitoring to specify the service refresh interval. When the service refresh interval reaches the threshold, the M2000 refreshes the monitored services.
Procedure
Step 1 Choose Monitor > System Monitor > Configuration . Step 2 In the System Monitor Settings window, click the Service Monitor tab to set the property values. Step 3 Click OK. ----End
2.7.2 Monitoring the M2000 Performance Status

You can monitor the status of the M2000 server performance to view the information on the operating system, memory usage, and CPU usage, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
Context
l
If you set a threshold of the performance and an item reaches the threshold, the icon of the item is displayed in red. Right-click in the System Monitor Browser window and choose Refresh to refresh the window.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the Performance Monitor tab to view the server performance. Step 3 Optional: Click Save As. The monitoring data is saved in the local disk. ----End
Related References
2.8.71 Parameters for Monitoring Performance of the M2000 Server
2.7.3 Monitoring the M2000 Hard Disk Status

You can monitor the status of the M2000 server hard disk to view the information such as the total space and usage of the hard disk, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
Context
l
If you set a threshold of the hard disk and an item reaches the threshold, the icon of the item is displayed in red. Right-click in the System Monitor Browser window and choose Refresh to refresh the window.
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the Hard Disk Monitor tab to view the status of the server hard disk. Step 3 Optional: Click Save As. The monitoring data is saved in the local disk. ----End
Related References
2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server
2.7.4 Monitoring the M2000 Database Status

You can monitor the status of the M2000 server database to view the information such as the database name, server name, and database status, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
Context
l
If you set a threshold of the database and then an item reaches the threshold, the icon of the item is displayed in red. Right-click in the System Monitor Browser window and choose Refresh to refresh the window. When the database space is insufficient, you can expand the space. The M2000, however, only supports the extension of the Sybase database at present.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the Database Monitor tab to view the status of the server database.
NOTE
The M2000 server runs in Solaris or SuSE Linux. Solaris uses Sybase, and SuSE Linux uses DB2. The status of the databases that you monitor varies with the database type.
Step 3 Optional: Click Save As. The monitoring data is saved in the local disk. ----End
Related References
2.8.73 Parameters for Monitoring Database of the M2000 Server
2.7.5 Monitoring the M2000 Service Status

You can monitor the status of the M2000 server services to view the information such as the service name and service status, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
Context
l l
If a service is abnormal, its icon is displayed in red. Right-click in the System Monitor Browser window and choose Refresh to refresh the window.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the Service Monitor tab to view the services on the server. Step 3 Optional: Click Save As. The monitoring data is saved in the local disk. ----End
Related References
2.8.74 Parameters for Monitoring Services of the M2000 Server
2.7.6 Monitoring the M2000 Process Status

You can monitor the status of the M2000 server processes to view the information such as the process name, process ID, and number of threads, to know the running status of the M2000; thus you can find and handle exceptions, and ensure the efficient running of the M2000.
Context
l l
Only the running processes are displayed in the monitoring content. Right-click in the System Monitor Browser window and choose Refresh to refresh the window.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the Process Monitor tab to view the server processes. Step 3 Optional: Click Save As. The monitoring data is saved in the local disk. ----End
Related References
2.8.75 Parameters for Monitoring Process of the M2000 Server
Issue 06 (2008-12-16)
2-145
2.8 Reference for Network Monitoring Interfaces

This describes the parameters used on the network monitoring interface, such as alarm monitoring, performance monitoring, RAN network monitoring, and NM system monitoring. 2.8.1 Interface Description: Local Terminal Settings This part describes the Local Terminal Settings interface, which helps you understand the function of each part of the interface. 2.8.2 Interface Description: Fault Service Settings This describes the Alarm Service Setting interface, which helps you understand the function of each part of the interface. 2.8.3 Interface Description: NE Alarm Settings This describes the NE Alarm Settings dialog box, which helps you understand the function of each part. 2.8.4 Interface Description: Alarm Browse, Query and Statistics This part describes the alarm browse, query and statistics interface, which helps you understand the function of each part. 2.8.5 Interface Description: Performance Monitor This describes the Performance Monitor interface. 2.8.6 Interface Description: Management of Monitored Object Groups The object group manager is divided into three parts: object group list, detailed information, and functional key. 2.8.7 Interface Description: RAN Network Monitoring The RAN network monitor interface is divided into RAN network monitoring area and detailed service information. 2.8.8 Interface Description: Monitoring Panel The monitoring panel represents a group of monitored objects. The monitored services of an object group depend on the type of the monitored object and the related settings. 2.8.9 Interface Description: System Monitor Browser This describes how to check the operational status of the system. The status consists of the disk status of the server, the database status, the progress status, and the service status. 2.8.10 Parameters for Setting Columns in an Alarm Interface You can adjust the information of alarms and show some columns as required. In addition, you can decide the columns to be shown and adjust the sequence of the shown columns. 2.8.11 Parameters for Monitoring Alarms in Real Time This section describes the parameters for monitoring alarms in real time. You can refer to this section when you set these parameters. 2.8.12 Parameters for Setting Alarm Query/Browse This describes the parameters for filtering alarms. You can refer to these parameters when you set alarm query and alarm browse. 2.8.13 Parameters for Setting Alarm Statistics This section describes the parameters for collecting alarm statistics. You can refer to these parameters when you set alarm statistics.
2.8.14 Parameters for Selecting NE for Query This part describes the parameters shown in the Select NE dialog box in the NE Alarm Settings window. You can perform the settings by referring to this part. 2.8.15 Parameters for Selecting Alarm Objects This section describes the parameters in the Select object dialog box. You can refer to this section when you select alarm objects. 2.8.16 Parameters for Selecting Alarm Name This section describes the parameters for selecting alarm names. You can refer to this section when you select alarm names. 2.8.17 Parameters for the Alarm Explanation and Maintenance Experience This section describes the parameters in the Explain and Experience window. You can refer to these parameters when you set the alarm explanation and maintenance experience. 2.8.18 Parameters for Acknowledging Alarms Automatically This section describes the parameters of automatically acknowledge alarms. You can refer to these parameters when you set the automatically acknowledge alarms. 2.8.19 Parameters for Setting Alarm Filter Conditions This section describes the parameters of the alarm filter rule. You can refer to these parameters when you set the alarm filter rule. 2.8.20 Parameters for Viewing Alarm Details This section describes the parameters of the query result displayed in the Detail Information dialog box. 2.8.21 Parameters for Querying the Shielding of an NE Alarm This part describes the parameters related to the Query Alarm Shielded and Querying Object Alarm Shielding dialog boxes. It provides a reference for future query. 2.8.22 Parameters for Shielding an NE Alarm This part describes the parameters related to the Add Alarm Shielding and Add Object Alarm Shielding dialog boxes. You can refer to this part when setting the parameters related with alarm shielding. 2.8.23 Parameters for Redefining NMS Alarm Level This section describes the parameters in the Add Level Redefine Rule dialog box. You can refer to these parameters when you add alarm level redefinition rules. 2.8.24 Parameters for Redefining/Modifying the Level of an NE Alarm This part describes the parameters available on the Add Severity Redefinition and Modify Severity Redefinition dialog boxes. When redefining or modifying NE alarm severities, you can refer to the parameter description in this part. 2.8.25 Parameters for Alarm Severity Redefinition This section describes the parameters of the query result displayed in the Severity Redefine window. 2.8.26 Parameters for Querying the Redefinition of an NE Alarm Level This part describes the parameters shown in Query Severity Redefinition dialog box, thus providing a reference for future query. 2.8.27 Parameters for User-Defined Alarms This describes the parameters for user-defined alarms. When adding or modifying user-defined alarms, you can perform the related settings by referring to the parameter descriptions. 2.8.28 Parameters for Querying a User-Defined Alarm
This describes the parameters in the Query User-Defined Alarm dialog box. It provides a reference for future query. 2.8.29 Parameters for Querying the Binding of a User-Defined Alarm This describes the parameters in the Query Alarm Binding dialog box. It provides a reference for future query. 2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm This describes the parameters binding a user-defined alarm. When adding or modifying the binding of a user-defined alarm, you can perform the related settings by referring to the parameter descriptions. 2.8.31 Parameters for Setting the Alarm Box This section describes the parameters in the Alarm Box Manager dialog box. You can refer to these parameters when you set the alarm box. 2.8.32 Parameters for Setting Alarm Remote Notification Rules This section describes the parameters for setting the remote notification rules. You can refer to this section when you set alarm remote notification rules. 2.8.33 Parameters for Setting Notification by Email This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the remote notification by Email. 2.8.34 Parameters for Advanced Settings of Notification by Email This section describes the parameters in the Communication Settings dialog box. You can refer to these parameters when you set advanced parameters of alarm notification by Email. 2.8.35 Parameters for Setting Notification by Modem This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the remote notification by modem. 2.8.36 Parameters for Advanced Settings of Notification by Modem This section describes the parameters in the Notify Device Communication Settings dialog box. You can refer to these parameters when you set the advanced parameters of notification by modem. 2.8.37 Parameters for Setting Notification by SMS Gateway This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the alarm notification by SMS gateway. 2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway This section describes the parameters in the Notify Device Communication Settings dialog box. You can refer to these parameters when you set the advance parameters for notification by SMS gateway. 2.8.39 Parameters for Setting Simple Correlation Rules This section describes the parameters in the Add Simple Correlation Rule dialog box. You can refer to these parameters when you set or modify the simple correlation rules of alarms. 2.8.40 Parameters for Setting Advanced Correlation Rules This section describes the parameters in the Add Advanced Correlation Rule dialog box. You can refer to these parameters when you set or modify the advanced correlation rules of alarms. 2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks This describes the related parameters on the Basic Attribute tab page in the Attribute dialog box. You can refer to these parameters when you set auto-triggering basic attributes.
2.8.42 Parameters for Auto-Triggering Conditions When you set the auto-triggering conditions, you may refer to the Trigger Condition tab page in the Attribute dialog box for the related parameter description. 2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script The Select NE Alarms dialog box lists the information about the parameters. You may refer to the information in this part when you add the alarm conditions of the auto-triggering script. 2.8.44 Parameters for Searching Auto-Triggering Tasks When you query the auto-triggering tasks, you may refer to the Query Task dialog box for the related parameter description. 2.8.45 Parameters for Searching Auto-Triggering Records This describes the related parameters in the Query Record dialog box. You can refer to these parameters when you search for auto-triggering tasks. 2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter This part lists the trend chart parameter settings. 2.8.47 Parameters for Setting a Background Color for a Monitoring Chart This topic describes parameters for setting the background color for monitor charts. 2.8.48 Parameters for Setting Filtering Conditions for a Monitoring Table This part introduces parameters of Table DataFilter Setting. 2.8.49 Parameters for Setting Properties for a Monitoring Chart This part introduces parameters about Property Setting of the monitor chart. 2.8.50 Parameters for Setting Real-Time Monitoring Thresholds This describes the parameters in the Monitor Threshold Management dialog box. 2.8.51 Parameters for Setting Rules for Monitoring Thresholds This part introduces parameters of Set Rules for Monitoring Thresholds. 2.8.52 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Chart This part introduces parameters for setting the thresholds for the monitor chart. 2.8.53 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Table This part introduces parameters of Table Threshold SettingShow style setting. 2.8.54 Parameters for Summarizing Alarms of RNC/NodeB You can select a method for alarm statistics. Alarms on the RNC support statistics by levels, by IDs, and by TopN. TopN indicates the sequence based on the quantity of alarms. The NodeB with most alarms is classified as Top1. Alarms on NodeBs support statistics by levels and IDs. 2.8.55 Parameters for Checking Values of RNC Monitoring Counters This part describes the parameters of KPI counters in the active RNC object group. 2.8.56 Parameters for Checking the Information on Basic RNC Configuration This part describes the basic attributes of the RNC object group and the meanings of basic configuration parameters in the object group. 2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC This part describes the parameters about the information on the Iu/Iur interface in the RNC. 2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface This part describes the parameters about the information on specified links of the Iu/Iur interface in the RNC. 2.8.59 Parameters for Checking the Information on the Iub Interface of the RNC
This part describes the parameters about the information on the Iub interface in the RNC object group. 2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface This part describes the basic parameters about the information on specified links of the Iub interface in the RNC object group. 2.8.61 Parameters for Checking the E1/T1 Status of the RNC This part describes the parameters about the E1T1 status of the RNC. 2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC This part describes the parameters about the distribution of NodeB and cells on the RNC. 2.8.63 Parameters for Checking the Information on Basic NodeB Configuration This part describes the parameters about the information on basic configuration of the NodeB object group. 2.8.64 Parameters for Checking the Information on Basic Cell Configuration This describes the parameters for checking the information on basic cell configuration. 2.8.65 Parameters for Configuration Status This part describes the parameters related with the configuration status of the RNC, NodeB and cell. 2.8.66 Parameters for Checking the Information on CCH Configuration This part describes the parameters related to the basic configuration of the common channel in a cell. 2.8.67 Parameters for Checking the Information on Neighbors This describes the parameters for checking the information on neighbors.Three types of neighboring cells are available: Intra-frequency neighboring cell, inter-frequency neighboring cell, and GSM neighboring cell. 2.8.68 Parameters for Checking the Values of Cell Monitoring Counters This part describes the parameters related to cell monitoring counters. 2.8.69 Parameters for Searching for Objects In case that many monitored objects exist, you can search the related monitored objects by using the fuzzy search method. Then you can locate the object quickly. 2.8.70 Parameters for Setting Thresholds of the M2000 Server This section describes the parameters of system monitor settings. You can refer to these parameters when you set the server thresholds. 2.8.71 Parameters for Monitoring Performance of the M2000 Server This section describes the parameters of the query result displayed in the Performance Monitor tab. 2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server This section describes the parameters of the query result displayed in the Hard Disk Monitor tab. 2.8.73 Parameters for Monitoring Database of the M2000 Server This section describes the parameters of the query result displayed in the Database Monitor tab. 2.8.74 Parameters for Monitoring Services of the M2000 Server This section describes the parameters of the query result displayed in the Service Monitor tab. 2.8.75 Parameters for Monitoring Process of the M2000 Server
This section describes the parameters of the query result displayed in the Process Monitor tab.
2.8.1 Interface Description: Local Terminal Settings

This part describes the Local Terminal Settings interface, which helps you understand the function of each part of the interface.
Highlighting Alarms
You can specify the time after which an alarm is regarded as a long-period alarm if it is not handled. A long-period alarm is highlighted on the interface, as shown in Figure 2-7. Figure 2-7 Highlighting Alarms
Customizing the Sound and Colors

You can customize the sound and colors for different levels of alarms, as shown in Figure 2-8 and Figure 2-9. Figure 2-8 Color settings
Issue 06 (2008-12-16)
2-151
Figure 2-9 Sound settings
Alarm Board
You can customize the settings of the alarm board, as shown in Figure 2-10. Figure 2-10 Alarm Board
Alarm Box
You can specify the filtering conditions of the alarm box. Thus, only those wanted alarms are sent to the alarm box and displayed through sounds or visions. Figure 2-11 shows the alarm box settings.
2-152
Issue 06 (2008-12-16)
Figure 2-11 Alarm Box
2.8.2 Interface Description: Fault Service Settings

This describes the Alarm Service Setting interface, which helps you understand the function of each part of the interface.
Remote Notification interface

Through the Remote Notification interface, you can specify the methods of remote notification. When an alarm is generated, the M2000 can deliver it to operators though E-mails or short messages. Figure 2-12 shows the interface.
Figure 2-12 Remote Notification interface
Correlation Analysis
l
After you set the alarm correlation rules, the M2000 abandons or shields the alarms that satisfy the conditions. Figure 2-13 shows the interface. After you set advanced alarm correlation rules, the system can shield the alarms that satisfy the conditions or re-define the alarm severity. In this case, you can focus on the main alarms to quickly locate and solve the problems. Figure 2-14 shows the interface.
2-154
Issue 06 (2008-12-16)
Figure 2-13 Simple correlation rule
Figure 2-14 Advanced alarm correlation rule
Issue 06 (2008-12-16)
2-155
Alarm Filtering interface

Through the Alarm Filtering interface, you can specify the settings for filtering those unwanted alarms. Figure 2-15 shows the interface. Figure 2-15 Alarm Filtering interface
Automatic Acknowledgement
The automatic acknowledgement interface provides the function of delaying and immediate auto acknowledging of unacknowledged fault alarms and event alarms. After you activate the auto acknowledge function, the system automatically acknowledge an event or fault alarm that meets the conditions. Figure 2-16 shows the interface.
2-156
Issue 06 (2008-12-16)
Figure 2-16 Automatic Acknowledgement
Knowledge and Explanation

The knowledge and explanation interface consists of query conditions, Explain, and Experience. After you select the alarm, click the alarm in Explain, then you can view the detailed information and suggested solution. You can also record your experiences in Experience to serve as reference when you encounter the same problem next time. Figure 2-17 shows the interface.
Issue 06 (2008-12-16)
2-157
Figure 2-17 Knowledge and Explanation
Alarm Level Redefinition

Through the alarm level redefinition interface, you can redefine the alarm severity, for example, degrade the severity level of relatively unimportant alarms or upgrade the severity of relatively important alarms. You can click Detail to view the information about the alarm level redefinition. Figure 2-18 shows the interface. Figure 2-18 Alarm Level Redefinition
2-158
Issue 06 (2008-12-16)
2.8.3 Interface Description: NE Alarm Settings

This describes the NE Alarm Settings dialog box, which helps you understand the function of each part. The NE Alarm Settings interface consists of the User-Defined Alarm tab, the Alarm Shielding tab, and the Severity Redefinition tab, as shown in Figure 2-19. After setting the conditions, you can view the alarm information in list in the related tab. Table 2-20 describes the function of each tab. Figure 2-19 NE Alarm Settings dialog box
Table 2-20 Description of the tabs i the NE Alarm Settings dialog box Tab User-Defined Alarm Description The User-Defined Alarm tab consists of Alarm Definition and Alarm Binding. You can self-define a new alarm and bind it to a port of a cabinet, subrack, or slot of an NE. You can also selfdefine the binding relationship. For details, refer toManaging User-Defined Tasks. In the Alarm Shielding tab, you can set shielding attribute for unwanted or wanted alarms to shield or release the shielding. Then you can forbid NEs reporting shielded alarms or allow NEs reporting alarms not shielded. In the Severity Redefinition tab, you can change the severity of alarms based on the actual effect on the system. For example, you can degrade the severity level of relatively unimportant alarms or upgrade the severity of relatively important alarms.
Alarm shielding
Severity Redefinition
2.8.4 Interface Description: Alarm Browse, Query and Statistics

This part describes the alarm browse, query and statistics interface, which helps you understand the function of each part.
Alarm Query
The alarm query interface consists of the event alarm query tab, the history fault alarm tab, the current fault alarm query, the shielded fault alarm query, the shielded event alarm query, the browse current fault alarms by status tab, and the browse event alarms by status tab. After setting the conditions, you can view the detailed information in the window. Figure 2-20 shows the interface. Figure 2-20 Alarm Query
Alarm statistics interface

Figure 2-21 shows the alarm statistics interface. After you set the conditions, the alarm statistics interface shows the detailed statistical information in tables and pie charts. Figure 2-21 Alarm statistics interface
2-160
Issue 06 (2008-12-16)
2.8.5 Interface Description: Performance Monitor

This describes the Performance Monitor interface. Figure 2-22, Figure 2-23, and Figure 2-24 show the Performance Monitor interface. Figure 2-22 Performance Monitor interface-1
(1) Navigation tree: shows the NEs, object sets, and monitoring tasks in a tree. (2) Table data: shows the result of performance monitoring in a table.
Issue 06 (2008-12-16)
2-161
Figure 2-23 Performance Monitor interface-2
(3) Counter result display area: displays the counter result of the selected time by counter or object. (4) Object name display area: displays the short names and full names of the objects. Short names are automatically assigned by the system, for example, SO1. Full names are the actual names of the objects, for example, RNC_64. (5) Monitoring chart: select multiple counters of an object or the same counter of multiple objects to compare the monitoring result. The compare result is shown in a line chart. (6) Counter results: displays the counter results in the compare chart separately in a bar chart. (7) Zooming button: to zoom in, zoom out, or restore the compare chart.
2-162
Issue 06 (2008-12-16)
Figure 2-24 Performance Monitor interface-3
(8) Trend figure: displays the performance monitoring results in a trend chart.
Related Tasks
2.5 Monitoring NE Performance in Real Time

The object group manager is divided into three parts: object group list, detailed information, and functional key. Figure 2-25 shows the object group manager interface. Figure 2-25 Object Group Manager interface
Issue 06 (2008-12-16)
2-163
(1) Object group list: lists all the object groups and their related information, such as creator, name, type, and status. (2) Detailed information: lists the detailed information of the object groups. The information are about function type and monitoring object.

Function Type shows the monitored services of object groups. Monitoring Object lists all of the monitored objects of the object group.
(3) Function key: includes Add, Modify, and Delete.
Related Concepts
2.6.1.1 Monitored Group
Related Tasks
2.8.7 Interface Description: RAN Network Monitoring

The RAN network monitor interface is divided into RAN network monitoring area and detailed service information. Figure 2-26 shows the network monitoring interface. Figure 2-26 RAN network monitoring
(1) RAN network monitoring area: shows all of the object groups that are activated. One panel represents an object group. For details about the implication of panel legend, refer to the description column on the right part of this window. (2) Detailed service information: shows the information of services. These services are depend on object type. The monitored services vary with types of the objects.
2-164
2.8.8 Interface Description: Monitoring Panel

The monitoring panel represents a group of monitored objects. The monitored services of an object group depend on the type of the monitored object and the related settings. Figure 2-27 shows a monitoring panel. Table 2-21 describes the panel elements. Figure 2-27 Monitoring panel
Table 2-21 Description of the monitoring panel Status Unack Description Indicates unacknowledged alarms. Alarm levels are as follows:
l l l l
: critical alarm : major alarm : minor alarm : warning
Unclr State PM
Indicates uncleared alarms. Indicates the status of NE connections. Indicates the performance status of superstandard KPI.
Related Tasks
2.6.3.1 Browsing Monitoring Panel
2.8.9 Interface Description: System Monitor Browser

This describes how to check the operational status of the system. The status consists of the disk status of the server, the database status, the progress status, and the service status. Figure 2-28 shows the System Monitor Browse interface. Table 2-22 describes each tab page.
Issue 06 (2008-12-16)
2-165
Figure 2-28 System Monitor Browser interface
Table 2-22 Functions of tabs on the system monitor browser interface Tab Performance Monitor Description You can check the basic information about current login server, such as Server Name, Server Status, OS, Free Physical Memory(KB), Total Physical Memory(KB), Free Swap Memory(KB), Total Swap Memory (KB), CPU Usage Rate(%) and Memory Usage(%). You can check the information about the hard disk of current login server, such as Server Name, Server Status, OS, Partition(Mounted Path), Total Size(KB), Used Size(KB), Free Size(KB), Used Rate(%), and Status. You can check the information about the database of current login server, such as DataBase Name, Server Name, OS, Total Data Space(KB), Used Space(KB), Free Space(KB), Used Rate(%), Total Log Space(KB), Free Log Space(KB), and Status. You can check the information about running services of current login server, such as Agent Name, Service, Service Description, Status, Auto Restart Count, Service Start Time, and Server Name. You can check the information about service proxy of current login server, such as Agent Name, Process ID, Handle Number, CPU Usage Rate (%), Memory Usage(KB), DB Connection Number, and Thread Number. You can check the information about all NEs, such as NE Name, NE Type, Alarm Status, and Connection Status.
Hard Disk Monitoring Database Monitor
Service Monitor Process Monitor
NE Monitor
2-166
Issue 06 (2008-12-16)
2.8.10 Parameters for Setting Columns in an Alarm Interface

You can adjust the information of alarms and show some columns as required. In addition, you can decide the columns to be shown and adjust the sequence of the shown columns.
Parameters for Setting Columns in an Alarm Interface

Parameter Serial Number Identifier Description The network serial number of an alarm. It is the keyword of an alarm record and uniquely identifies an alarm. Shows the alarm information using an icon:
l l l l l
Intermittent alarm
. .
High-frequency intermittent alarm Repeat event alarm .
High-frequency repeat event alarm Alarm with a comment .
Link Name Link Type
The name of a link in the network. The type of a link in the network. Each link type corresponds to a unique link. The following link types are available:
l l l l l l
BICCSCTPLINK DataLink H248Link M3UALink MTP3BLink MTP3Link
NE Type Equipment Alarm Serial Number Name
The type of an NE in the network. Each NE type corresponds to a unique NE. The serial number of an alarm device. In the same device, a unique alarm can be defined according to the serial number. The name of an alarm in the network, through which it is possible to quickly locate the basic information of the alarm. For example, if it is a database threshold alarm, users can know that the alarm is generated from the database by its name. The category available in the network, including fault alarms and event alarms. Both fault alarms and event alarms are used to notify users of exceptional situations. Fault alarms indicate that you need to take measures to handle the fault.
Category
Issue 06 (2008-12-16)
2-167
Parameter Type
Description The type of an alarm in the network, such as power system, trunk system, and OMC.The name of an alarm in the network, through which it is possible to quickly locate the basic information of the alarm. For example, if it is a database threshold alarm, users can know that the alarm is generated from the database by its name. The clearance category of an alarm, including automatic clearance and manual clearance. The clearance type of an alarm, such as, normal clearance, manual clearance, and configuration clearance. The source of an alarm. Shows whether an alarm is cleared.
l
Clearance Category Clearance Type Alarm Source Clearance
If the alarm is cleared, the name of the operator that cleared the alarm is displayed. If the alarm is not cleared, is displayed.
Acknowledgemen t
Shows whether an alarm is acknowledged.

l
If the alarm is acknowledged, the name of the operator that acknowledged the alarm is displayed. If the alarm is not cleared, is displayed.
Object Instance Type Operation Impact Flag Additional Information Level
The name of the object that generates an alarm. If the object is available on the topology view, the related object name is displayed. Otherwise, the NE name is displayed. Shows whether the alarm has impact on the services. The value can be Yes,No, or Unknown. The additional information about an alarm, for example, the alarm causes. Alarm levels. Four levels are available:
l
Critical The device or resource is absolutely faulty. An immediate solution is a must.
Major The quality of the device or resource is greatly degraded. Immediate solution is required.
Minor The quality of the device or resource is slightly degraded. Appropriate solution or further observation is needed to avoid a worse situation.
Warning The quality of the device or resource has potential trouble. Different measures are needed depending on the warning.
Alarm ID
The ID corresponding to an alarm.
2-168
Issue 06 (2008-12-16)
Parameter Occurrence Time (NT) Clearance Time (NT) Acknowledgemen t Time(ST) Location Information
Description The time when an alarm occurs. The time when a fault alarm is cleared. The time when an event alarm or a fault alarm is acknowledged. The information is used to quickly locate the reason why an alarm is generated, and analyze the way of handling alarms. When an alarm is reported, the system automatically fills in the location information which operators have configured for each NE. If operators do not configure the location information for an NE, the system replaces it with the information configured in Explanation and Knowledge Database.
Related Tasks
2.2.1 Setting Columns in an Alarm Interface
2.8.11 Parameters for Monitoring Alarms in Real Time

This section describes the parameters for monitoring alarms in real time. You can refer to this section when you set these parameters.
Base Settings
Name Acknowledgem ent Description Description: Acknowledgement status of the alarms that you want to monitor. Settings Value: The acknowledgement status includes: Acknowledged Unacknowledged Setting method: You can choose more than one items. If do not choose, all items are considered selected by default. Clearance Description: Clearance status of the alarms that you want to monitor. Value: The clearance status includes: Cleared Uncleared Setting method: You can choose more than one items. If do not choose, all items are considered selected by default.
Issue 06 (2008-12-16)
2-169
Alarm Source Object Types

Name By object Description Description: Select an alarm source according to the NE type. Settings Setting method: Click .
Related Tasks
2.2.6 Setting Alarm Real-Time Monitoring

This describes the parameters for filtering alarms. You can refer to these parameters when you set alarm query and alarm browse.
Base Setting
Name Name Description Description: Indicates the name of the alarm to be queried or browsed. Severity Description: Indicates the severity of the alarm to be queried or browsed. Setting Setting method: Select Name, and then click the parameter. Value: Alarm severity is as follows: Critical Major Minor Warning Setting method: Select one or multiple check boxes. By default, all the check boxes are selected. Acknowledgem ent Description: Indicates the acknowledgement status of the alarm to be queried or browsed. Value: Acknowledgement status are as follows: Acknowledged Unacknowledged Setting method: Select one or multiple check boxes. By default, all the check boxes are selected. to set
2-170
Issue 06 (2008-12-16)
Name Clearance
Description Description: Indicates the clearance status of the alarm to be queried or browsed.
Setting Value: Clearance status are as follows: Cleared Uncleared Setting method: Select one or multiple check boxes. By default, all the check boxes are selected.
Type
Description: Indicates the type of the alarm to be queried or browsed.
Value: Alarm types are as follows: Power System Environment System Signaling System Trunk System Hardware System Software System Running System Communication System QoS Processing Error Internal Setting method: Select one or multiple check boxes. By default, all the check boxes are selected. Click Click to select all the items. to clear all the items.
Start Time
Description: Indicates a start time. You can query or browse the alarms generated later than this time.
Setting method: Select Start Time, and then specify the time range of alarm generation between the start time and end time. Enter the time in dd/MM/yyyy HH:mm:ss format, or click the time panel. to choose a time from
Issue 06 (2008-12-16)
2-171
Name End Time
Description Description: Indicates an end time. You can query or browse the alarms generated earlier than this time.
Setting Setting method: Select End Time, and then specify the time range of alarm generation between the start time and end time. Enter the time in dd/MM/yyyy HH:mm:ss format, or click the time panel. to choose a time from
Latest
Description: Indicates the latest time. You can query or brows the alarms that are generated in the latest hours, days, weeks, or months.
Setting method: Select Latest, and then set the hour, day, week, and month.
Advanced
Description: Indicates the advanced parameters of the alarms to be queried or browsed.
Setting method: Click the button.
Import
Description: Imports the parameters template for alarm query, browse or statistics and uses the parameters configuration in this template as alarm filter conditions.
Setting method: Click Import. In the Import dialog box, select a template and then click Import.
Reset
Description: Restores the parameters for alarm query or browse to the default settings.
Advanced
Tab Maintenanc e Region Name Description Description: You can select the maintenance region as required. Setting Setting method: Check box
2-172
Issue 06 (2008-12-16)
Tab Browse Setting
Name -
Description Description: You can select the mode for browsing alarms as required.
Setting Value:
l l l
Browse all alarms Browse debug alarms Browse normal alarms
Debug alarms refer to the alarms generated by commissioning NEs. Setting method: Check box Default Location information contains: Description: You can set the content of the alarm location information. Description: You can set the network serial number contained in the alarm information. Description: You can set whether to filter alarms based on alarm identifiers or not. Setting method: Text box
Alarm serial Number (separated by ;):
Setting method: Text box
Identifier
Value: Event alarm identifiers are as follows: Alarm Memo Repeat Event High Frequency Repeat Event Fault alarm identifiers are as follows: Alarm Memo Flash Fault High Frequency Flash Fault Setting method: Check box
Issue 06 (2008-12-16)
2-173
Tab
Name Time Mode
Description Description: You can query or browse alarms based on the local server time or the local NE time.
NOTE If you select Latest in the filtering conditions, the M2000 queries or browses alarms based on the local server time no matter which time mode is selected.
Setting Value: Time modes are as follows: Server time NE time Setting method: Option button

Name By Object Description Description: You can select an alarm source according to the NE. By Type Description: You can select an alarm source according to the NE type. Setting Setting method: Click Setting method: If you select NE Type, all types of NEs in the network are selected by default. If you select an NE type under NE Type, all NEs of this type are selected. A specific NE cannot be selected if you use this arrangement mode. By Topo Description: You can select an alarm source according to the topology objects. Setting method: Select the alarm source from the Topology Root navigation tree. If you select Topology Root, all types of NEs in the network are selected by default. .
Related Tasks
2.2.5 Monitoring Alarms Through the Topology View 2.2.7 Querying Alarms 2.2.7.1 Querying Current Fault Alarms 2.2.7.3 Querying Event Alarms 2.2.7.2 Querying History Fault Alarms 2.2.7.4 Querying the Masked Fault Alarms 2.2.7.5 Querying the Masked Event Alarms
2-174
Issue 06 (2008-12-16)
2.8.13 Parameters for Setting Alarm Statistics

This section describes the parameters for collecting alarm statistics. You can refer to these parameters when you set alarm statistics.
Statistical Items
Name Alarm Log Description Description: Set the type of the alarms on which you want to collect statistics. Operation Value: Parameters for fault alarms: current fault alarm and history fault alarm. Parameter for event alarms: event alarm. Setting method: Click Statistic Row Description: Set the row heading of the statistical result table. for selection.
Setting method: You can select up to three statistical items. The statistical results are sorted according to the statistical items. Setting method: Value: The parameters include NE, NE type, link, link type, alarm name, alarm level, alarm type, alarm log, alarm status, by day, and by hour. Setting method: Drop-down list
Statistic Column
Description: Set the column heading of the statistical result table. Description: Set the row heading and column heading of the statistical result table.
Statistic Item
Preview
Description: Preview the style of the statistical result table.
Value: Setting method: Click the button. Setting method: Click the button.
Reset
Description: Set the statistical item to the default value.
Import
Description: Import the parameter template for alarm statistics.
Issue 06 (2008-12-16)
2-175
Basic Settings
Name Name Description Description: Name of the alarm on which you want to collect statistics. Level Description: Level of the alarm on which you want to collect statistics. Operation Setting method: Select Name, and then click the parameter. Value: Alarm levels include: Critical Major Minor Warning Setting method: You can choose more than one items. If no item is chosen, all items are considered selected by default. Acknowledgem ent Description: Acknowledgement status of the alarm on which you want to collect statistics. Value: Acknowledgement status includes: Acknowledged Unacknowledged Setting method: You can choose more than one items. If no item is chosen, all items are considered selected by default. Clearance Description: Clearance status of the alarm on which you want to collect statistics. Value: Clearance status includes: Cleared Uncleared Setting method: You can choose more than one items. If no item is chosen, all items are considered selected by default. to set
2-176
Issue 06 (2008-12-16)
Name Type
Description Description: Type of the alarm on which you want to collect statistics.
Operation Value: Alarm types include: Power System Environment System Signaling System Trunk System Hardware System Software System Running System Communication System QoS Processing Error Internal Setting method: You can choose more than one items. If no item is chosen, all items are considered selected by default.
Start Time
Description: Statistic the alarms raised later than this time.
Setting method: Select Start Time, and then specify the time range of alarm occurrence between the start time and end time. Enter the time in the format of YYYY-MMDD hh:mm:ss, or click from the time panel. to choose a time
End Time
Description: Statistic the alarms raised earlier than this time.
Setting method: Select End Time, and then specify the time range of alarm occurrence between the start time and end time. Enter the time in the format of YYYY-MMDD hh:mm:ss, or click from the time panel. to choose a time
Advanced
Description: Advanced parameters for alarm statistics.
Issue 06 (2008-12-16)
2-177
Name Import
Description Description: Import the parameters template for alarm query, browse or statistics and use the parameters configuration in this template as alarm filter conditions.
Operation Setting method: Click Import. In the Import dialog box, select a template and then click Import.
Reset
Description: Restore the parameters for alarm statistics to the default settings.
Advanced Settings
The Ne District tab in the Advanced dialog box displays the NEs based on districts. You can select the NEs on which you want to collect statistics. The Ne District information is added to the statistical result. The NEs on which the statistics is collected is the intersection of the NEs set on the Ne District and Alarm Source tab pages. You can set the query mode on the Browse Setting tab page of Advanced dialog box. You can select Browse all alarms, Browse debug alarms. or Browse normal alarms. The following is the description of the parameters on the Default tab page of the Advanced dialog box. Name Location information contains Identifier Description Description: Content of the alarm location information. Description: Whether to filter alarms based on alarm identifiers. Operation Setting method: Text box Value: Alarm identifiers include: Alarm Memo Flash Fault High Frequency Flash Fault Setting method: Check box Time Mode Description: Statistic alarms based on the local server time or the local NE time. Value: Time modes include: Server time NE time Setting method: Radio button

Name By Object Description Description: Select an alarm source according to the NE. By type Description: Select an alarm source according to the NE type. Operation Setting method: Click Setting method: If you select NE Type, all types of NEs in the network are selected by default. If you select an NE type under NE Type, all NEs of this type are selected. You cannot select a specific NE if using this arrangement mode. By topo Description: Select an alarm source according to the topology objects. Setting method: Select the alarm source from the Topology Root tree. If you select Topology Root, all types of NEs in the network are selected by default. .
Related Tasks
2.2.8 Collecting Alarm Statistics
2.8.14 Parameters for Selecting NE for Query

This part describes the parameters shown in the Select NE dialog box in the NE Alarm Settings window. You can perform the settings by referring to this part.
Parameter Search by Name Group by NE Type Description Searching NEs by the NE name. It supports fuzzy search. You can enter keyword of the NE name to search the NE. If you select the option, the NEs in the Select NE navigation tree are displayed by NE type.
Related Tasks
2.2.7 Querying Alarms 2.4.2 Querying the Shielding of an NE Alarm 2.4.5 Querying the Redefinition of an NE Alarm Level 2.4.7.1 Querying a User-Defined Alarm 2.4.8.1 Querying the Binding of a User-Defined Alarm
Issue 06 (2008-12-16)
2-179
2.8.15 Parameters for Selecting Alarm Objects

This section describes the parameters in the Select object dialog box. You can refer to this section when you select alarm objects.
Parameters
Name Search by name Description Description: Search for an alarm object by the keyword of the alarm object name. Fuzzy search is supported. Description: Whether to expand the navigation tree of alarm object names automatically. Description: Group alarms based on all the existing NE types, such as OMC. Description: Alarm objects that you can select. Settings Setting method: Text box.
Auto expand
Setting method: Check box.
Group by type
Setting method: Check box. Setting method:

l
Available objects
In the Available objects navigation tree, select an object. Click to add the object.
Click objects.
to add all the
Click to delete all the selected objects.
Selected objects
Description: Alarm objects that are selected.
Setting method:
l
In the Selected objects navigation tree, select an object. Click to delete the object.
Click objects.
to add all the
Click to delete all the selected objects.
Related Tasks
2.2.2 Manually Synchronizing NE Alarms 2.2.7.1 Querying Current Fault Alarms 2.2.7.3 Querying Event Alarms
2-180
Issue 06 (2008-12-16)
2.8.16 Parameters for Selecting Alarm Name

This section describes the parameters for selecting alarm names. You can refer to this section when you select alarm names.
Alarm Names
Name Available Alarm Description Description: Alarm names that you can select. Settings Setting method:
l
In the Available Alarm navigation tree, select an alarm. Click the alarm. to add
l l
Click Click alarms.
to add all the alarms. to delete all the selected
Selected Alarm
Description: Alarm names that are selected.
Setting method:
l
In the Selected Alarm navigation tree, select an alarm. Click the alarm. to delete
l l
Click Click alarms.
to add all the alarms. to delete all the selected
Search by name
Description: Search for alarms by alarm name. Fuzzy search is supported. Letters are case insensitive. Description: Whether to expand the navigation tree of alarm names automatically.
Setting method: Text box.
Auto expand
Group by NE type
Description: Group alarms based on all existing NE types in the network. Description: Group alarms by alarm type, such as power system, environmental system, or signaling system.
Group by alarm type
Issue 06 (2008-12-16)
2-181
Name Group by alarm level
Description Description: Group alarms by alarm level. Alarm levels include critical, major, minor, and warning.
Settings Setting method: Check box.
Group by categories
Description: Group alarms by alarm categories. Alarm categories include event alarm and fault alarm.
Related Tasks
2.2.8.1 Collecting Statistics on Fault Alarms 2.2.7.1 Querying Current Fault Alarms 2.3.3.1 Setting the Remote Notification Rules for Alarms
2.8.17 Parameters for the Alarm Explanation and Maintenance Experience

This section describes the parameters in the Explain and Experience window. You can refer to these parameters when you set the alarm explanation and maintenance experience.
Parameters
Name Search by name Description Description: Search for an alarm by the keyword of the alarm name. Auto expand Description: Whether to expand the navigation tree of alarm names automatically. Group by NE type Description: Group alarms based on all the existing NE types, such as OMC. Description: Group alarms based by alarm type, such as, Environmental System, Hardware System, Communication System. Settings Setting method: Text box. Setting method: Check box. Setting method: Check box. Setting method: Check box.
Group by alarm type
2-182
Issue 06 (2008-12-16)
Name Group by alarm level
Description Description: Group alarms by alarm level, such as critical, major, minor, and warning. Description: Group alarms by alarm category, such as event and fault. Description: Name of an alarm in the network.
Group by category
Setting method: Check box. Setting method: Setting method: Button. Setting method: Button. Setting method: -
Alarm name
Export
Description: Export the experience database and save it as a file.
Import
Description: Import the file to the experience database.
Explanation
Description: Display the alarm explanation information and the suggestions for clearing the alarm.
Experience
Description: Display the maintenance experience of an alarm.
Setting method: Setting method: Button.
Modify
Description: Record the fault maintenance experience in the experience database.
Related Tasks
2.2.11.7 Recording Alarm Handling Experience
2.8.18 Parameters for Acknowledging Alarms Automatically

This section describes the parameters of automatically acknowledge alarms. You can refer to these parameters when you set the automatically acknowledge alarms.
Parameters
Name Since alarm cleared Critical Major
Description Description:
Issue 06 (2008-12-16)
2-183
Name Minor Warning
Description Set the alarms that need be acknowledged immediately according to the levels. The alarms of a level are acknowledged immediately after they are cleared.
Settings
Related Tasks
2.3.5 Setting Alarm Auto Acknowledgement
2.8.19 Parameters for Setting Alarm Filter Conditions

This section describes the parameters of the alarm filter rule. You can refer to these parameters when you set the alarm filter rule.
Parameters for alarm filter rules

Name Filter Condition Description Description: Conditions for alarm filter. Description: Time mode used by the alarm filter rule. Server time: The start and end time the alarm filter rule takes effect are the server time. NE time: The start and end time the alarm filter rule takes effect are the NE time. Settings Setting method: Click next to Filter Condition. In the displayed Filter Condition dialog box, set the parameter. Setting method: -
Time mode
2-184
Issue 06 (2008-12-16)
Name Start time
Description Description: Time when the alarm filter rule starts to function.
Settings Setting method: next to Start time. In the displayed Date/Time Click Selection dialog box, set the parameter.
End time
Description: Time when the alarm filter rule stops to function.
Setting method: next to End time. In the displayed Date/Time Click Selection dialog box, set the parameter.
Memo
Description: Remarks of the alarm filter rule.
Enable
Description: Whether the alarm filter rule functions.
Parameters for alarm filter conditions

Name Name Description Description: Name of the filtered alarm. Level Description: Level of the filtered alarm. Type Description: Type of the filtered alarm. Alarm Source Description: Source of the filtered alarm. Settings Setting method: Select Name. Click next to Name. In the displayed Select Alarm Name dialog box, set the parameter. Setting method: Select the check box next to a proper alarm level. Setting method: Select the check box next to a proper alarm type. Setting method: You can set the parameter by object or type:
l
By object: Click Select, and then set the parameter in the By Object dialog box. By type: In the By Type navigation tree, select a proper NE type.
Issue 06 (2008-12-16)
2-185

Name By object Description Description: Select an alarm source according to the NE. By type Description: Select an alarm source according to the NE type. Settings Setting method: Click , and then set the parameter in the By Object dialog box. Setting method: If you select NE Type all types of NEs in the network are selected by default. If you select an NE type under NE Type, all NEs of this type are selected. You cannot selected a specific NE if using this arrangement mode.
Related Tasks
2.3.4 Setting Alarm Filter Rules
2.8.20 Parameters for Viewing Alarm Details

This section describes the parameters of the query result displayed in the Detail Information dialog box.
Parameters
Name Name Description Description: Name of an alarm in the network. The basic information of the alarm can be quickly located by alarm name. For example, if it is a database threshold alarm, you can know that the alarm is raised from the database based on its name. Location Information Description: You can use the information to quickly locate the causes of an alarm, and analyze the methods of handling the alarm. When an alarm is reported, the system automatically fills the location information you have configured for each NE. If you do not configure the location information on an NE, the system replaces the location information with the information configured in the explanation and experience database. Severity Description: Alarm severities, including critical, major, minor, and warning. Alarm Source Description: Device that raises the alarm.
2-186
Issue 06 (2008-12-16)
Name Occurrence Time
Description Description: Time when an alarm is raised.
Clearance Time
Description: Time when a fault alarm is cleared.
Clearance
Description: Clearance status of a fault alarm or event alarm, such as Unclear.
Acknowledgement
Description: Acknowledgement status of a fault alarm or event alarm, such as Unacknowledged.
Acknowledgement Time Serial Number
Description: Time when an event alarm or a fault alarm is acknowledged. Description: Network serial number of an alarm. It is the key word of an alarm record, by which a unique alarm can be defined.
Equipment Alarm Serial Number
Description: Serial number of an alarm device. In the same device, a unique alarm can be defined according to the serial number. Description: Identifies the status of alarm memo. If there is a memo of the alarm, the status is displayed as Have memo. Otherwise, the field is blank.
Identifier
Link Name
Description: Name of a link in the network.
Link Type
Description: Type of a link in the network. Each link type corresponds to a unique link.
NE Type
Description: Type of an NE in the network. Each NE type corresponds to a unique NE.
Category
Description: Categories of alarms in the network, including fault alarms and event alarms.
Type
Description: Source of an alarm in the network, such as Power System, Trunk System, or Internal.
Issue 06 (2008-12-16)
2-187
Name Clearance Category
Description Description: Whether the alarm is automatically cleared or manually cleared. The value can be ADAC or ADMC, indicating auto clearance or manual clearance.
Clearance Type
Description: Type of alarm clearance. The value can be Normal clearance, Manual clearance, Reset clearance, Configuration clearance, or Correlation clearance.
NOTE
l ADAC indicates that after the fault is removed, the M2000 reports the
corresponding cleared alarm.

l ADMC indicates that after the fault is removed, the M2000 does not report
the corresponding cleared alarm, and you need to clear the alarm manually.
Object Instance Type
Description: Type of the managed object that raises an alarm, such as the board, file directory, or port.
Operation Impact Flag
Description: Whether the service is affected. The value can be Yes, NO or Unknown. Description: Additional information on an alarm. Description: Handling experience on an alarm. Click Modify to record the alarm handling experience.
Additional Information Alarm Experience
Alarm Memo
Description: Memo on an alarm.

l l
Click Add to add a new memo. Click Modify to modify the existing memo.
MO Object
The managed object that raises an alarm, such as the board name.
Related Tasks
2.2.11.3 Viewing Alarm Details
2.8.21 Parameters for Querying the Shielding of an NE Alarm

This part describes the parameters related to the Query Alarm Shielded and Querying Object Alarm Shielding dialog boxes. It provides a reference for future query.
2-188
Issue 06 (2008-12-16)
Querying the Descriptions on Alarm Shielding Parameters of the NEs Managed by the BSC6000
Parameter Search by Name Value Range None Description Search the parameters according to the names of the alarms. The query supports case-insensitive search. Group by NE Type None If you select this item, in the Root tree, the NEs are displayed in groups based on NE types.
Querying the Descriptions on Alarm Mask Parameters of Other NEs

Parameter NE Name Value Range None Description Name of an NE. Click and select the NE in the displayed dialog box. The start alarm ID for the alarm filter.
Start Alarm ID
For NodeB NEs, the value ranges from 1 to 32000 and from 65334 to 65534. For non-NodeB NEs, the value ranges from 1 to 32000. For NodeB NEs, the value ranges from 1 to 32000 and from 65334 to 65534. For non-NodeB NEs, the value ranges from 1 to 32000.
End Alarm ID
The end alarm ID for the alarm filter.
Maximum Record Count Level
Numeric type. Ranges from 1 to 1000. The default value is 1000.

l l l l
The maximum count of the returned records. You can choose more than one items. If you do not select any alarm level, all alarms will be queried.
Critical Major Minor Warning
Related Tasks
2.4.2 Querying the Shielding of an NE Alarm
2.8.22 Parameters for Shielding an NE Alarm

This part describes the parameters related to the Add Alarm Shielding and Add Object Alarm Shielding dialog boxes. You can refer to this part when setting the parameters related with alarm shielding.
Alarm shielding parameters of the NEs managed by the BSC6000

Parameter Search by Name Value Range None Description Search the parameters according to the names of the alarms. Case insensitive search rather than wildcard search is supported. Group by Alarm Type None If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on NE types. The alarm types include power system, environment system, and signaling system. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm levels. Alarm severity levels are: Critical, Major, Minor, and Warning. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm types. The alarms can be classified into two types: fault alarm and event alarm.
Group by Alarm Level
None
Group by Alarm Category
None
Alarm shielding parameters of the NEs

Parameter Shielded flag Search by Name Value Range Enumeration, Value range: YES and No. None Description Indicates whether to enable the function of alarm shielding. Search by the name of an NE or alarm. The name is case insensitive. Wildcard search is not supported. Case insensitive search rather than wildcard search is supported. If you select this item, in the Select NE navigation tree, the NEs are displayed in groups based on NE types. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on NE types. The alarm types include power system, environment system, and signaling system.
Group by NE Type
None
Group by Alarm Type
None
2-190
Issue 06 (2008-12-16)
Parameter Group by Alarm Level
Value Range None
Description If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm levels. Alarm severity levels are: Critical, Major, Minor, and Warning. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm types. The alarms can be classified into two types: fault alarm and event alarm.
None
Related Tasks
2.4.1 Shielding an NE Alarm
2.8.23 Parameters for Redefining NMS Alarm Level

This section describes the parameters in the Add Level Redefine Rule dialog box. You can refer to these parameters when you add alarm level redefinition rules.
Parameters
Name Alarm Names Description Description: Name of the alarm whose level you want to redefine. Settings Setting method: Click next to the text box. In the Select Alarm Name dialog box, set the parameter. Setting method: Text box. Setting method: Drop down list box.
Default Level
Description: Level of the alarm before redefinition.
Redefine Level
Description: Level of the alarm after redefinition. The redefined level cannot be the same as the original level.
Memo
Description: Remarks of the alarm redefinition rule.
Setting method: Text box. Setting method: Check box.
Enable
Description: Whether the alarm redefinition rule functions.
Issue 06 (2008-12-16)
2-191
Name Alarm Source
Description Description: Source of an alarm, that is, the device that raises the alarm. After you select the alarm source, the M2000 redefines the level of the alarms that are raised by only the alarm source.
Settings Setting method: On the Alarm Source tab, click . In the Select object dialog box, select the alarm source.
Related Tasks

This part describes the parameters available on the Add Severity Redefinition and Modify Severity Redefinition dialog boxes. When redefining or modifying NE alarm severities, you can refer to the parameter description in this part.
Parameter Search by Name Description In Search by Name, enter the alarm name you want to query. Fuzzy search is supported. Browse Mode You can browse alarms by group. Browse mode combinations are supported. The modes include Group by NE Type, Group by Alarm Type, Group by Alarm Level, and Group by Category. Redefined Level You can choose a new alarm level from the drop-down list under this field. Original alarm severities are not included in the drop-down list.
Related Tasks
2.4.4 Redefining the Level of an NE Alarm 2.4.6 Modifying the Setting of NE Alarm Level Redefinition
2.8.25 Parameters for Alarm Severity Redefinition

This section describes the parameters of the query result displayed in the Severity Redefine window.
2-192
Issue 06 (2008-12-16)
Parameters
Name ID Description Description: Name of the redefined alarm. Enable Description: Whether to enable the alarm redefinition rules. Alarm Names Description: Name of the redefined alarm. Alarm Source Description: Source of an alarm, that is, the device that raises the alarm. Default Severity Description: Severity of the alarm before redefinition. Redefine Severity Description: Alarm Severity after redefinition. Category Description: Alarm category. Memo Description: Remarks of the alarm redefinition rule.
Related Tasks
2.8.26 Parameters for Querying the Redefinition of an NE Alarm Level

This part describes the parameters shown in Query Severity Redefinition dialog box, thus providing a reference for future query.
Parameters
Parameter NE Name Value Range None. Description Name of an NE. Click and select the NE in the displayed dialog box. The start alarm ID for the alarm level redefinition. The end alarm ID for the alarm level redefinition.
Start Alarm ID
Numeral. Value range: 1 to 32000.
End Alarm ID
Numeral. Value range: 1 to 32000.
Issue 06 (2008-12-16)
2-193
Parameter Maximum Record Count
Value Range Numeral. Value range: 1 to 100. Default value: 1000.
Description The maximum count of the returned records.
Alarm Level
l l l l
You can select more than one alarm levels. If you do not select any alarm, alarms of all these levels are queried.
Related Tasks
2.4.5 Querying the Redefinition of an NE Alarm Level

This describes the parameters for user-defined alarms. When adding or modifying user-defined alarms, you can perform the related settings by referring to the parameter descriptions.
Parameter NE Type Value Range NE type and NE Description For the NodeB, you can select only an NE type. For the MSCe and MGW, you can select either an NE type or an NE. Name of a user-defined alarm This parameter can be null. ID of a user-defined alarm
Alarm Name Alarm ID
String type
l
The value range of the NodeB: 65334-65534 The value range of the MSCe: Odd numbers in the range of 65334-65533 The value range of the MGW: 65334-65533 The value range of the MSC Server: 65335-65533 The value range of the DBS3800: 65334-65534 The value range of the OMC: 65400-65449 Only the iSStar can send user-defined alarms to the OMC.
2-194
Issue 06 (2008-12-16)
Parameter Level
Value Range The following four severity levels are listed in the dropdown list:
l l l l
Description You can select only one severity level.
Critical Major Minor Warning The parameter is set by default and the setting cannot be modified.
Types
Environment system or the OMC.

l
If NE Type is set to an NE type other than OMC, this option is Environment System. If NE Type is set to OMC, this option is OMC.
Related Tasks
2.4.7 Defining an NE Alarm 2.4.7.2 Adding a User-Defined Alarm 2.4.7.3 Modifying a User-Defined Alarm
2.8.28 Parameters for Querying a User-Defined Alarm

This describes the parameters in the Query User-Defined Alarm dialog box. It provides a reference for future query.
Parameter Alarm Name Alarm ID Value Range String type
l
Description Name of a user-defined alarm This parameter can be null. ID of a user-defined alarm This parameter can be null.
The value range of the NodeB: 65334-65534 The value range of the MSCe: Odd numbers in the range of 65334-65533 The value range of the MGW: 65334-65533
NE Type
Issue 06 (2008-12-16)
NE type and NE
Select a related NE type.

2-195
Parameter Level
Value Range
l l l l
Description You can choose more than one items. If you do not select any alarm level, all alarms will be queried.
Related Tasks
2.4.7.1 Querying a User-Defined Alarm
2.8.29 Parameters for Querying the Binding of a User-Defined Alarm

This describes the parameters in the Query Alarm Binding dialog box. It provides a reference for future query.
Parameter NE Name Value Range None Description Name of an NE. Click and select the NE in the displayed dialog box. This parameter is applicable to only MSC Server and MSCe. Type of the query. Three types, All, by Alarm ID, and by Position are available. The meanings are as follows:
l
Query Type
None
All: to query binding information of all alarms. by Alarm ID: to query binding information according to alarm ID. by Position: to query binding information according to subrack No. and port No. of the alarm to be bound.
Alarm ID
Numeric type. Ranges from 65335 to 65533.
ID of an alarm This parameter is applicable only when Query Type is by Alarm ID.
2-196
Issue 06 (2008-12-16)
Parameter Cabinet
Value Range Enumerated Type

l
Description Refers to the number of the cabinet to which the NE alarm is to be bound.
For NodeB, the value range is 0-1. For MSCe, the value range is 0-4. For DBS3800, the value range is 0-1. For MSC Server, the value range is 0-1.
Subrack
Numeric type. Ranges from 0 to 255. Numeric type. Ranges from 0 to 255. Numeric type.
l
Applicable to only NodeB, and DBS3800. Refers to the number of the subrack to which the NE alarm is to be bound. Applicable only to the NodeB and DBS3800. Refers to the number of the slot to which the NE alarm is to be bound. Refers to the number of the port to which the NE alarm is to be bound.
Slot
Port
Related Tasks
2.4.8.1 Querying the Binding of a User-Defined Alarm
2.8.30 Parameters for Adding/Modifying the Binding of a UserDefined Alarm

This describes the parameters binding a user-defined alarm. When adding or modifying the binding of a user-defined alarm, you can perform the related settings by referring to the parameter descriptions.
Issue 06 (2008-12-16)
2-197
Parameter Search by Name Value Range None Description Search by the name of an NE or alarm. The name is case insensitive. Wildcard search is not supported. Case insensitive search rather than wildcard search is supported. If you select this item, in the Select NE navigation tree, the NEs are displayed in groups based on NE types. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on NE types. The alarm types include power system, environment system, and signaling system. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm levels. Alarm severity levels are: Critical, Major, Minor, and Warning. If you select this item, in the Select Alarm navigation tree, the NEs are displayed in groups based on alarm types. The alarms can be classified into two types: fault alarm and event alarm. Refers to the number of the cabinet to which the NE alarm is to be bound.
Group by NE Type Group by Alarm Type
None
None
None
None
Cabinet
Enumerated Type
l
Subrack
Numeric type. Ranges from 0 to 255. Numeric type. Ranges from 0 to 255.
Applicable only to the NodeB. Refers to the number of the subrack to which the NE alarm is to be bound. Applicable only to the NodeB. Refers to the number of the slot to which the NE alarm is to be bound.
Slot
2-198
Issue 06 (2008-12-16)
Parameter Port
Value Range Numeric type.

l
Description Refers to the number of the port to which the NE alarm is to be bound.
Port Type
Select the value from the drop-down list. Select the value from the drop-down list. Numeric type. The value range depends on the NE.
Type of the signal received by the port which is to be bound to the NE alarm, such as Bool and Value. This parameter is applicable only when Port Type is Bool. Two types are available, that is,High and Low. This parameter is applicable only when Port Type is Value. It indicates the upper limit for generating alarms. An alarm is reported to the M2000 when signals received by the port reaches this value. This parameter is applicable only when Port Type is Value. An alarm is restored on the M2000 when signals received by the port are smaller than this value. The default setting is Open. After you delete an alarm binding, Port Switch is Close. Open indicates that user-defined alarm binding is takes effect. Close indicates that alarms are not bound.
Alarm Voltage
Upper Threshold
Lower Threshold
Numeric type. The value range depends on the NE. Default value, such as Open and Close.
Port Switch
Related Tasks
2.4.8 Binding a User-Defined Alarm 2.4.8.2 Adding the Binding Relation of a User-Defined Alarm 2.4.8.3 Modifying the Binding of a User-Defined Alarm
2.8.31 Parameters for Setting the Alarm Box

This section describes the parameters in the Alarm Box Manager dialog box. You can refer to these parameters when you set the alarm box.
Issue 06 (2008-12-16)
2-199
Parameters
Name Control Sound and Light by Severity Description Description: Set the severity of the alarms to be monitored by the alarm box. When an alarm at the specified severity is generated, the indictor corresponding to this severity generates an audible and visual alarm.
NOTE The alarm box has four alarm indicators corresponding to four alarm severities.
Settings Value: Alarm severities include:

l l l l
Value: Select option button and then select one or multiple options in the check box. Value: Select option button.
Control Sound and Light by Template
Description: Set the alarm box to generate audible and visual alarms according to the alarm template. Description: Select an alarm template. When an alarm complying with the alarm template is generated, the alarm box generates an audible and visual alarm.
Template
Value: Value range: All objects and current fault alarms templates. Default value: All objects, which refers to all current fault alarms. Setting method: Select option button and then . In the Select dialog click box, select the fault template.
NOTE If no fault template is created, click New Fault Template to create a template.
Mute current alarm sound
Description: Stops the current alarm sound.
Setting method: Click the button. Setting method: Check box.
Enable
Description: Start the alarm box.
2-200
Issue 06 (2008-12-16)
Name Serial Port
Description Description: Serial port through which the M2000 client is connected the alarm box.
Settings Value: Value range: COM1 and COM2. Default value: COM1. Setting method: Select Enable, and then select a serial port from the drop-down list.
Related Tasks
2.3.2.4 Setting the Alarm Box
2.8.32 Parameters for Setting Alarm Remote Notification Rules

This section describes the parameters for setting the remote notification rules. You can refer to this section when you set alarm remote notification rules.
Base Settings
Name Name Description Description: Name of the remote notification alarm. Level Description: Level of the remote notification alarm. Settings Setting method: Select Name, and then click Description: Alarm levels include: Critical Major Minor Warning Setting method: You can choose more than one items. If do not choose, all items are considered selected by default. .
Issue 06 (2008-12-16)
2-201
Name Type
Description Description: Type of the remote notification alarm.
Settings Description: Alarm Types include: Power System Environmental System Signaling System Trunk System Hardware System Software System Running System Communication System QoS Processing Error Internal Setting method: You can choose more than one items. If do not choose, all items are considered selected by default.
Alarm Names
Name Available Alarm Description Description: Alarm names that you can select. Description: Alarm names that are selected. Search by name Description: Search for alarms by alarm name. Fuzzy search is supported. Letters are case insensitive. Description: Whether to expand the navigation tree of alarm names automatically. Group by NE type Description: Group alarms based on all existing NE types in the network. Settings Setting method: Setting method: Setting method: Text box.
Selected Alarm
Auto expand
2-202
Issue 06 (2008-12-16)
Name Group by alarm type
Description Description: Group alarms by alarm type, such as power system, environmental system, or signaling system. Description: Group alarms by alarm level. Alarm levels include critical, major, minor, and warning.
Group by alarm level
Group by categories
Description: Group alarms by alarm categories. Alarm categories include event alarm and fault alarm.

Name By object Description Description: Select an alarm source according to the NE. By type Description: Select an alarm source according to the NE type. Settings Setting method: Click Setting method: If you select NE Type all types of NEs in the network are selected by default. If you select an NE type under NE Type, all NEs of this type are selected. You cannot selected a specific NE if using this arrangement mode. .
Notification Time
Name Week Description Description: Time in a week to send alarm remote notification. Settings Setting method: Check box.
NOTE Select at least one option.
Issue 06 (2008-12-16)
2-203
Name All week
Description Description: To send alarm remote notification every day in a week.
Sun
Description: To send alarm remote notification every Sunday.
Setting method: Check box. Setting method: Check box. Setting method: Check box. Setting method: Check box.
Mon
Description: To send alarm remote notification every Monday.
Tue
Description: To send alarm remote notification every Tuesday.
Wen
Description: To send alarm remote notification every Wednesday.
Thu
Description: To send alarm remote notification every Thursday.
Fri
Description: To send alarm remote notification every Friday.
Setting method: Check box. Setting method: Check box.
Sat
Description: To send alarm remote notification every Saturday.
Period of Time
Description: Period in a day to send alarm remote notification every.
Setting method: Select the check box, and then set the period in the drop-down list.
NOTE You can set up to three periods.
2-204
Issue 06 (2008-12-16)
Notification Methods
Name Email address (formatted as: username@hos tname) SMS number Description Description: Email address used to receive emails. Description: Number of the mobile phone used to receive short messages. Memo Description: Description. Enable Description: To enable the notification method. Settings Setting method: Text box. Addresses are separated by semicolons (;). Setting method: Text box. Numbers are separated by semicolons (;). Setting method: Text box. Setting method: Option button.
Related Tasks
2.3.3.1 Setting the Remote Notification Rules for Alarms
2.8.33 Parameters for Setting Notification by Email

This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the remote notification by Email.
Parameters
Name Host name or IP of SMTP Description Description: Host name or IP address of the Simple Mail Transfer Protocol(SMTP) email server.
NOTE To protect the connection with the SMTP server against a domain resolution failure, it is recommended to use the IP address of the email server.
Settings Setting method: Enter the valid SMTP server name or IP address.
Address of sender
Description: Email address of the sender. Description: This option determines whether to provide complete configuration of the email. If the SMTP server needs authentication, you should select this option.
Setting method: Use the email address of the sender. Setting method: Option button.
Enable check right
Issue 06 (2008-12-16)
2-205
Name User name of SMTP
Description Description: This name is used for authentication on the SMTP server. Set this field if you select Enable check right.
Settings Setting method: Text box.
Sender password
Description: This password is used for authentication on the SMTP server. The password must match the user account. Set this field if you select Enable check right.
Send by server
Description: The email is sent by the server.
Setting method: Option button. Setting method: Click the button. In the Email Notification Test dialog box, enter an email address for test. Click Test. The format of the email address is user name@host name.
NOTE If M2000 prompts the operation is successful, it indicates that the settings are correct.
Test on Server
Description: Test on the server whether the mail can be sent.
Send by current client Test on Client
Description: The email is sent by the client. Description: Test on the client whether the mail can be sent.
Setting method: Option button. Setting method: Click the button. In the Email Notification Test dialog box, enter an email address for test. Click Test. The format of the email address is user name@host name.
NOTE If M2000 prompts the operation is successful, it indicates that the settings are correct.
2-206
Issue 06 (2008-12-16)
Name Enable
Description Description: Start the notification device.
Settings Setting method: Option button.
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
2.8.34 Parameters for Advanced Settings of Notification by Email

This section describes the parameters in the Communication Settings dialog box. You can refer to these parameters when you set advanced parameters of alarm notification by Email.
Parameters
Name Email Subject Description Description: Title of the email. Settings Value: Default value: Alarm Notify. Setting method: Text box. Message head Description: Prefix of each alarm in the email. Value: Default value: +++. Setting method: Text box. Message head end Description: Suffix of each alarm in the email. Value: Default value: ---. Setting method: Text box. Content Setting Description: Set the alarm fields in the email content. Sender IP Description: View the IP address of the sender. Setting method: Click the button. In the Content Setting dialog box, select the alarm fields. Setting method: Click the button.
Related Tasks
2.8.35 Parameters for Setting Notification by Modem

This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the remote notification by modem.
Parameters for setting notification by modem

Name Send by server Serial Port Description Description: The SMS is sent by the server. Description: Port number between the SMS device and a computer. Baud rate Description: Baud rate of the modem. Settings Setting method: Option button. Setting method: Value range: COM1 and COM2. Default value: COM1. Setting method: Select the actual baud rate supported by the modem. Default value: 9600. Test on Server Description: After you enter the SMS number, test on server whether the short message can be sent. Setting method: Click the button. In the SMS Notification Test dialog box, enter a SMS code for test. Click Test.
NOTE
l Type the mobile phone number of a
maintenance person. The number must contain the county (region) code. For example, in +8613800755500, 86 is the county (region) code.
l If M2000 prompts the operation is
successful, it indicates that the settings are correct.
Send by current client
Description: The short message is sent by the local client. Description: After you enter the SMS number, test on client whether the short message can be sent.
Setting method: Option button. Setting method: Click the button. In the SMS Notification Test dialog box, enter a SMS code for test. Click Test.
NOTE
Test on Client
Enable
Description: Start the notification device.
Setting method: Option button.
2-208
Issue 06 (2008-12-16)
Related Tasks
2.8.36 Parameters for Advanced Settings of Notification by Modem

This section describes the parameters in the Notify Device Communication Settings dialog box. You can refer to these parameters when you set the advanced parameters of notification by modem.
Parameters
Name Message head Description Description: Prefix of each alarm in the email. Settings Value: Default value: +++. Setting method: Text box. Setting method: Message head end Description: Suffix of each alarm in the email. Value: Default value: ---. Setting method: Text box. Content Setting Description: Set the alarm fields in the email content. Sender IP Description: View the IP address of the sender. Setting method: Click the button. In the Content Setting dialog box, select the alarm fields. Setting method: Click the button.
Related Tasks
2.8.37 Parameters for Setting Notification by SMS Gateway

This section describes the parameters in the Add Notify Device Communication Settings dialog box. You can refer to these parameters when you set the alarm notification by SMS gateway.
Parameters for SMS gateway settings

Name Host Address Description Description: IP address of the SMS center. Settings Setting method: For details, contact the SMS center.
Issue 06 (2008-12-16)
2-209
Name Port
Description Description: Port number of the SMS center.
Settings Value: Value range: 1-65534. Setting method: For details, contact the SMS center. Setting method: For details, contact the SMS center. Setting method: For details, contact the SMS center. Setting method: Click the button. In the SMS Notification Test dialog box, enter a SMS code for test. Click Test.
NOTE
User name
Description: User name in the SMS center.
Password
Description: Valid user password in the SMS center.
Code protocol
Description: Coding protocol in the SMS center.
Test
Description: Test whether the SMS receiving number can be normally used after the SMS properties are set.
l In the external dual-band GSM
modem or CDMA modem, the test number cannot exceed 26 characters, including the plus sigh (+). In the SMS, the test number cannot exceed 20 characters, including the plus sigh (+).
Enable
Description: Enable the notification device.
Setting method: Option button.
Related Tasks
2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway

This section describes the parameters in the Notify Device Communication Settings dialog box. You can refer to these parameters when you set the advance parameters for notification by SMS gateway.
2-210
Issue 06 (2008-12-16)
Advance Parameters
Name Message head Description Description: Prefix of the short message body. Settings Value: Default value: +++. Setting method: Text box. Message head end Description: Suffix of the short message body. Value: Default value: ---. Setting method: Text box. Content Setting Description: Set the alarm fields of the content to be sent. Description: User number that initiates the call. Description: Type of the user number that initiates the call. Description: Type of the user number that is called. Description: Coding rule of the calling number. Setting method: Click the button. In the Content Setting dialog box, select the alarm fields. Setting method: Text box. Setting method: Text box. Value: Value range: 0-7. Default value: 1.
Calling number Calling number type
Called number type
Calling number numbering plan Called number numbering plan
Description: Coding rule of the called number.
Setting method: Text box. Value: Value range: 0-15. Default value: 1.
Parameters for Caller and Called Number Types

Code 0 Description Description: Unknown. 1 Description: International number.
Issue 06 (2008-12-16)
2-211
Code 2
Description Description: Home number. Area or special numbers cannot be contained.
Description: Network special number.
Description: Subscriber number.
Description: Letter or number.
Description: Abbreviated number.
Description: Reserved.
Parameters for Caller and Called Number Coding

Code 0 Description Description: Unknown. If TON is equal to 5, then NPI is equal to 0. 1 Description: Integrated Services Digital Network(ISDN) or telephone number coding scheme (E164 or E163). This code applies to any Service Center (SC), Mobile Switching Center(MSC), or Mobile Station(MS). 2 Description: Reserved. 3 Description: Data coding scheme (121). 4 Description: Telegraph coding scheme. 5-7 Description: Reserved. 8 Description: Home coding scheme. 9 Description: Private coding scheme.
2-212
Issue 06 (2008-12-16)
Code 10
Description Description: ERMES coding scheme (ETSI DE/PS 3 01-3).
11-15
Description: Reserved.
Related Tasks
2.8.39 Parameters for Setting Simple Correlation Rules

This section describes the parameters in the Add Simple Correlation Rule dialog box. You can refer to these parameters when you set or modify the simple correlation rules of alarms.
Parameters
Name Alarm names Description Description: Name of the alarm that need simple correlation analysis. Settings Setting method: Click . In the displayed Select Alarm Name dialog box, set the parameter. Value: Value range: 0-10. Unit: Second (abbreviated as s)
Interval
Description:
l
For fault alarms Interval between the clearance of two fault alarms. If the status of the alarms is switched between "uncleared" and "cleared" and the interval between the clearance of two adjacent fault alarms does not exceed the preset value, these alarms are called intermittent alarms. In this case, only the first alarm that is report for the first time is displayed, and other intermittent alarms that are report later are filtered.
For event alarms Interval between the clearance of two event alarms. If the same event alarm is reported by the NE continuously for twice or more times and the interval between any two adjacent event alarms does not exceed the preset value, this alarm is called repeat event alarm. In this case, only the first alarm is displayed, and the repeat event alarms are filtered.
Issue 06 (2008-12-16)
2-213
Name Intermittence/ Repeat Times
Description Description:
l
Settings Value: Value range: 2-6000.
For fault alarms If the frequency of the intermittent fault alarms exceeds the preset value, these alarms are called high frequent fault alarms. In this case, the M2000 filters the intermittent fault alarms, and reports an alarm of a higher level. If the level of the intermittent alarms is already highest, the M2000 reports an alarm of the same level.
For event alarms If the frequency of the repeat event alarms exceeds the preset value, these alarms are called high frequent event alarms. In this case, the M2000 displays the first event alarm, and reports an alarm of a higher level. If the level of the intermittent alarms is already highest, the M2000 reports an alarm of the same level.
Action
Description: When the M2000 detects intermittent fault alarms or repeat event alarms, it filters the report alarms. If you select Shield, the alarms are saved in the filter database. If you select Abandon, the alarms are deleted. You can view the filtered alarms by querying the filtered fault alarms and filtered event alarms.
Value: Value range: Abandon and Shield.
Memo
Description: Remarks of the alarm simple correlation filter rule.
Setting method: Text box. Value: Check box.
Enable
Description: Whether the current alarm correlation rule is enabled.
Related Tasks
2.3.7.3 Adding Simple Correlation Rules of Alarms
2.8.40 Parameters for Setting Advanced Correlation Rules

This section describes the parameters in the Add Advanced Correlation Rule dialog box. You can refer to these parameters when you set or modify the advanced correlation rules of alarms.
2-214
Issue 06 (2008-12-16)
Parameters
Name Correlati on Conditio n Alarm Instance A Description Description: An alarm instance set in the correlation condition. Settings Setting method: From the drop-down list, select Clear Alarm Instance (which indicates no configuration). Select Create Alarm Instance. In the displayed Select Alarm Name dialog box, specify the alarm instance. Setting method: From the drop-down list, select Clear Alarm Instance (which indicates no configuration). Select Create Alarm Instance. In the displayed Select Alarm Name dialog box, specify the alarm instance. Setting method: Select the priority from the drop-down list. Setting method: Select the condition from the drop-down list. Example: Example: If you select Less than for Occurrence Time, it indicates that the occurrence time of alarm instance A is earlier than that of alarm instance B, that is, alarm instance B is raised later than alarm instance A. Setting method: Select the value from the drop-down list. Example: Example: If you select Level for Property, the values include Critical and Major.
Alarm Instance B
Description: Another alarm instance set in the correlation condition.
Property
Description: Properties of the instance set in the correlation condition.
Condition
Description: Define the relation between the properties of Alarm Instance A and Alarm Instance B, or between the properties of Alarm Instance A or Alarm Instance B and Value.
Value
Description: Value of the alarm instance. It varies with the selected property. You can enter the alarm instance value when only one alarm instance exists.
Issue 06 (2008-12-16)
2-215
Name Correlati on Action Alarm Instance
Description Description: When the correlation condition is met, the alarm instance of the correlation action is used. Description: Correlation action executed for a specific alarm when the correlation condition is met.
Settings Setting method: Select the instance from the drop-down list. Setting method: Select the action from the drop-down list. Example: Example: If you select Level Redefine, and the correlation condition is met, the M2000 executes the preset correlation action. The redefined value is set in Value.
Action
Value
Description: Alarm level. This field is valid when the value of Action is Level Redefine.
Setting method: Select the value from the drop-down list. Setting method: Value range: Maximum: 1000000000 High: 1000000 Low: -1000000 Minimum: -1000000000 Value: Option button.
Priority
Description: During correlation analysis, the M2000 determines the priorities of correlation rules, and then executes the actions. The priority of the correlation analysis for intermittent fault alarms and repeat event alarms is highest, which is 1000000000.
Enable
Description: Whether the current correlation rule is enabled.
Related Tasks
2.3.7.4 Adding Advanced Correlation Rules of Alarms
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks

This describes the related parameters on the Basic Attribute tab page in the Attribute dialog box. You can refer to these parameters when you set auto-triggering basic attributes.
NOTE
The parameters with the asterisk cannot be null.
2-216
Issue 06 (2008-12-16)
Parameter Task Name
Value Range
l
Description The name of the task that is automatically triggered.
A maximum of 20 characters. The allowed characters include Chinese characters, English letters, numbers and special characters except ` ~ ! @ # $ % ^ & ; * ()+-={}[]\\|;':,.?/ <>\" The value must be unique and not empty. Case sensitive
Start Date Start Time End Date End Time Triggering Day
Year range: 1970 to 2038. 24 hours Year range: 1970 to 2038. 24 hours The following four severity levels are listed in the dropdown list:
l l l l l l l l
Indicates the time range when the script is triggered. Only when the alarm occurs in the defined time range, and in the defined Triggering Day, for example, Tuesday, the script to be executed is triggered by the server.
Everyday Mon Tuesday Wed Thursday Fri Sat Sun Run-time type refers to the way the server runs the script.
l
Run-time Type
Selected from the drop-down list.
bash represents Bourne Again shell. sh represents Bourne shell. csh represents C shell. zsh represents Z shell. ksh represents Korn shell. tcsh represents TC shell.
l l l l l
Issue 06 (2008-12-16)
2-217
Parameter Script file
Value Range A maximum of 255 characters.
Description Involves the absolute path and the name of the script file on the M2000 server. For example, / export/home/trigger.sh. You can assign the parameters in the script files using this function. or example, when you enter a b, the first parameter of this script file is assigned with a, and the second parameter is assigned with b. The system determines the number of a parameter based on the order in which the parameter occurs in the script file.
Run-time Param
A maximum of 9 parameters is allowed. The parameters are separated by spaces.
Remark
A maximum of 255 characters.
Involves the backup information about the auto-triggering task.
Related Tasks
2.3.8.1 Creating Auto-Triggering Tasks 2.3.8.2 Viewing the Attributes of Auto-Triggering Tasks
2.8.42 Parameters for Auto-Triggering Conditions

When you set the auto-triggering conditions, you may refer to the Trigger Condition tab page in the Attribute dialog box for the related parameter description.
Parameter No. Description The serial number of the auto-triggering conditions. The system distributes the serial numbers based on the time order in which you create the triggering conditions. The name of the NE whose alarm triggers the script execution. The alarm ID that triggers the script execution. The information about the failure to create the auto-triggering condition.
NOTE If the auto-triggering condition is successfully created, the Message field is null.
Ne Name Alarm ID Message
Related Tasks
2.8.43 Parameters for Adding the Alarm Conditions of the AutoTriggering Script
The Select NE Alarms dialog box lists the information about the parameters. You may refer to the information in this part when you add the alarm conditions of the auto-triggering script.
NOTE
l l
Each auto-triggering task supports a maximum of 250 alarm conditions settings. In the Select Alarm navigation tree, the items can be listed based on the alarm name or on the alarm ID. You can right-click the blank area in the Select Alarm pane, and then choose Sort by Alarm Name or Sort by Alarm ID.
Parameter Search by Name
Description This parameter is used to search for the NE or the NE alarm that triggers the script. The querying conditions support fuzzy search whatever case the name is. The querying conditions do not support wildcard. If you select this item, in the Select NE navigation tree, the NEs are displayed in groups based on NE types. If you select this item, In the Select Alarm navigation tree, the alarms are divided based on the alarm type. The alarm types include the power supply system, the environment system, and the signaling system. If you select this item, in the Select Alarm navigation tree, the alarms are displayed in groups based on the alarm levels. The alarm levels are critical, major, minor and warning. If you select this item, in the Select Alarm navigation tree, the alarms are displayed in groups based on the alarm categories. The alarms are categorized into fault alarms and event alarms.
Group by NE Type Group by Alarm Type
Group by Category
Related Tasks
2.8.44 Parameters for Searching Auto-Triggering Tasks

When you query the auto-triggering tasks, you may refer to the Query Task dialog box for the related parameter description.
Issue 06 (2008-12-16)
2-219
Parameter Task Name Value Range
l
Description The name of the task that is automatically triggered.
The task name has a maximum of 20 characters. The allowed characters include Chinese characters, English letters, numbers and any other special characters rather than ` ~ ! @#$%^&;*()+-={} []\\|;':,.?/<>\" The task name is unique and cannot be null. The task name is case sensitive.
Start Date End Date Start Time End Time Triggering Day
Year range: 1970 to 2038. Year range: 1970 to 2038. 24 hours. 24 hours. You may choose a period from the drop-down list that includes the following periods:
l l l l l l l l
The period that is set in the autotriggering task.
Everyday Monday Tuesday Wednesday Thursday Friday Saturday Sunday Run-time type refers to the way the server runs the script.
l
Run-time Type
You may choose a type from the drop-down list.
bash represents Bourne Again shell. sh represents Bourne shell. csh represents C shell. zsh represents Z shell. ksh represents Korn shell. tcsh represents TC shell.
l l l l l
2-220
Issue 06 (2008-12-16)
Parameter Ne Name
Value Range None.
Description Indicates the NE name whose alarm triggers the script execution. Click the NE name in the Select NE Alarms dialog box that is displayed after you click .
Alarm ID
None.
Indicates the ID of the alarm that triggers the script execution. Enter the alarm ID or choose from theSelect NE Alarms dialog box displayed after you click .
Related Tasks
2.3.8.3 Searching Auto-Triggering Tasks
2.8.45 Parameters for Searching Auto-Triggering Records

This describes the related parameters in the Query Record dialog box. You can refer to these parameters when you search for auto-triggering tasks.
Parameter Query Condition Task Name NE Name Query All Description The name of the task that is automatically triggered. The name of the NE whose alarm triggers the script execution. Select this item. The system queries all auto-triggering tasks run by the server. The name of the task that is automatically triggered. The name of the NE whose alarm triggers the script execution. Indicates the ID of the alarm that triggers the script execution. Run-time type refers to the way the server runs the script. Involves the absolute path and the name of the script file on the M2000 server. For example, / export/home/trigger.sh.
2-221
Query Result
Task Name NE Name Alarm ID Run-time Type Script file
Issue 06 (2008-12-16)
Parameter Triggered time
Description Indicates the specific time for triggering the server to run the script file.
Related Tasks
2.3.8.4 Searching Auto-Triggering Records
2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter

This part lists the trend chart parameter settings.
Parameters
Parameter Object Counter Value Range Options in the dropdown list Description Select object in navigation tree. Counter to be monitored. The counter to be monitored depends on the object class of the detail data specified during the setting of a monitoring task. Upper value set against the history value. Lower value set against the history value.
Upper Warp (%) Lower Warp (%)
0.000 - 100.000 0.000 - 100.000
Related Tasks
2.5.4.1 Analyzing the Trend of a Monitoring Counter
2.8.47 Parameters for Setting a Background Color for a Monitoring Chart

This topic describes parameters for setting the background color for monitor charts.
Parameters
Parameter Swatches HSB RGB Operation Select a sample color. Select a sample color or select a color by setting the HSB value. Select a color by setting the RGB value.
Related Tasks
2.5.3.7 Setting a Background Color for a Monitoring Chart
2.8.48 Parameters for Setting Filtering Conditions for a Monitoring Table

This part introduces parameters of Table DataFilter Setting.
Parameters
Parameter Hide the filtered data Show the filtered data Show All Object Condition Counter Condition Description To hide the data that satisfies the filtering conditions. To show the data that satisfies the filtering conditions. To show all the data. Name of the current monitored object. Name of the monitored counter of the current object monitored. You can select counter names, operators, and logical relationships. For the values, however, you must enter them manually.
Related Tasks
2.5.3.1 Setting Filtering Conditions for a Monitoring Table
2.8.49 Parameters for Setting Properties for a Monitoring Chart

This part introduces parameters about Property Setting of the monitor chart.
Parameters
Parameter Show/Hide Description You can select the counters or objects to be displayed in the monitoring chart.
l
Compare chart: The counter compare chart displays all the monitored counters; the object compare chart displays all the monitored objects. Detail chart: display all the monitored objects. Tendency chart: displays the real value, upper value, and lower value.
l l
Time range Part/Full Lost Data Status
Specifies the start and end time of the monitoring time segment for the monitoring chart.
l
Normal: Only time points in the normal monitoring status are shown in the curve in the chart. Part Lost: Time points with missing data are shown in the curve in a special color. Full Lost: Time points with lost data are shown in the curve in a special color.
2-223
Issue 06 (2008-12-16)
Related Tasks
2.5.3.4 Setting Properties for a Monitoring Chart
2.8.50 Parameters for Setting Real-Time Monitoring Thresholds

This describes the parameters in the Monitor Threshold Management dialog box.
Parameter Object Counter Upper Warp (%) Lower Warp (%) Triggering Times Value Range None. Monitoring counters. 0.000 - 100.000 0.000 - 100.000 1 - 10 Description Object to be monitored. Counter to be monitored. Upper value set against the history value. Lower value set against the history value. Triggering times for monitor threshold alarms. The default value is 3. When a counter of a monitored task exceeds the threshold range set by monitor threshold alarm for successive three times, the system reports the Pm Alarm Threshold of the corresponding level. Severity level of the threshold alarm
Level
l l l l
Related Tasks
2.5.2.5 Setting Real-Time Monitoring Thresholds
2.8.51 Parameters for Setting Rules for Monitoring Thresholds

This part introduces parameters of Set Rules for Monitoring Thresholds.
Parameters
Parameter Date Description Date for filtering alarms.
l l l
All By Week By Month
2-224
Issue 06 (2008-12-16)
Parameter Time
Description Time for filtering alarms.

l l
All Specific: a maximum of three time segments
Related Tasks
2.5.2.6 Setting Rules for Monitoring Thresholds
2.8.52 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Chart
This part introduces parameters for setting the thresholds for the monitor chart.
Parameters
Parameter Counter Upper Warp Lower Warp Value Range Options in the drop-down list From -999999999.998 to 999999999.998 From -999999999.998 to 999999999.998 Description Counter name. Upper threshold of a monitored counter. Lower threshold of a monitored counter.
Related Tasks
2.5.3.5 Setting Thresholds for Displaying Counters in a Monitoring Chart
2.8.53 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Table
This part introduces parameters of Table Threshold SettingShow style setting.
Parameters
Parameter Font Size Attributes Value range Enumeration. Enumeration.
l l
Description The text font. The font size. The font attributes.
Bold Italic
Foreground color
Swatches,HSB,RGB
The foreground color of the font.The default color is black.
Issue 06 (2008-12-16)
2-225
Parameter Background color
Value range Swatches,HSB,RGB
Description The background color of the font.The default color is white.
Related Tasks
2.5.3.2 Setting Thresholds for Displaying Counters in a Monitoring Table

You can select a method for alarm statistics. Alarms on the RNC support statistics by levels, by IDs, and by TopN. TopN indicates the sequence based on the quantity of alarms. The NodeB with most alarms is classified as Top1. Alarms on NodeBs support statistics by levels and IDs.
Settings for Alarm Statistics

Before you take alarm statistics in the system, refer to Table 2-23 to set the statistical conditions. Table 2-23 Parameters related to the settings of alarm statistics Parameter Statistic Method Description
l l l
Statistic by Level: Alarms are categorized by levels. Statistic by ID: Alarms are categorized by IDs. Statistic by TopN of NodeB: Collect the alarms of the current object group by collecting the alarms of the NodeBs under the object group. TopN indicates the sequence based on the quantity of alarms. The NodeB with most alarms is classified as Top1. Statistic by TopN of Cell: Collect the alarms of the current object group by collecting the alarms of the cells under the object group. TopN indicates the sequence based on the quantity of alarms. The cell with most alarms is classified as Top1. Statistic by TopN of SAAL: Collect the alarms of the current object group by collecting the alarms of the SAAL links under the object group. TopN indicates the sequence based on the quantity of alarms. The SAAL link with most alarms is classified as Top1. Statistic by TopN of E1T1: Collect the alarms of the current object group by collecting the alarms of the E1/T1 links under the object group. TopN indicates the sequence based on the quantity of alarms. The E1/T1 link with most alarms is classified as Top1. Server Time: Alarm statistics are made according the time on the server. NE Time: Alarm statistics are made according the time on a specific NE.
Time Style
2-226
Issue 06 (2008-12-16)
Parameter Statistic Time
Description Time range for alarm statistics

l l
Start time: start time of the alarm statistics End time: end time of the alarm statistics
Alarm Statistics by Levels

You can make alarm statistics by levels. For details of related parameters, refer to Table 2-24. Table 2-24 Parameters related to alarm statistics by levels Parameter Alarm Level Total Alarm Current Alarm History Alarm Cleared Alarm Uncleared Alarm Description Alarms are categorized into four levels: critical, major, minor and warning. Number of all alarms by levels Number of current alarms by levels Number of history alarms by levels Number of cleared alarms by levels Number of uncleared alarms by levels
Alarm Statistics by IDs

You can make alarm statistics by IDs. For details of related parameters, refer to Table 2-25. Table 2-25 Parameters related to alarm statistics by IDs Parameter Alarm ID Total Alarm Current Alarm History Alarm Cleared Alarm Uncleared Alarm Alarm Name Description ID of an alarm Number of all alarms by IDs Number of current alarms by IDs Number of history alarms by IDs Number of cleared alarms by IDs Number of uncleared alarms by IDs Name of the alarm specified by an ID
Alarm Statistics on a TopN Basis

You can make alarm statistics on a TopN basis. Three methods available are Statistic by TopN of Cell, Statistic by TopN of SAAL, and Statistic by TopN of E1T1. For details of related parameters, refer to Table 2-26.
Table 2-26 Parameters related to alarm statistics on a TopN basis Parameter Object ID Point Name Total Alarm Current Alarm History Alarm Cleared Alarm Uncleared Alarm Description ID of the object Name of the key point Number of all alarms on a TopN basis Number of current alarms on a TopN basis Number of history alarms on a TopN basis Number of cleared alarms on a TopN basis Number of uncleared alarms on a TopN basis
Related Tasks
2.6.6.1 Summarizing RNC Alarms by Alarm Severity 2.6.6.2 Summarizing RNC Alarms by Alarm ID 2.6.6.3 Summarizing RNC Alarms by NodeB 2.6.6.4 Summarizing RNC Alarms by Cell 2.6.6.5 Summarizing RNC Alarms by SAAL Link 2.6.6.6 Summarizing RNC Alarms by E1/T1 Link 2.6.6.7 Summarizing NodeB Alarms by Alarm Severity 2.6.6.8 Summarizing NodeB Alarms by Alarm ID
2.8.55 Parameters for Checking Values of RNC Monitoring Counters

This part describes the parameters of KPI counters in the active RNC object group. Table 2-27 lists the parameters of KPI counters in the active RNC object group. Table 2-27 Parameters about the information on basic configuration of the RNC object group Property Name Name CounterName CounterUnit CounterResult ResultReliable ResultTime Property Value Name of the affiliated NE Name of KPI counters Unit that KPI counters belong to Counter result Counter related to the result Report time of counter results
Related Tasks
2.6.5.1 Checking Values of RNC Monitoring Counters
2.8.56 Parameters for Checking the Information on Basic RNC Configuration

This part describes the basic attributes of the RNC object group and the meanings of basic configuration parameters in the object group. Table 2-28 lists the parameters about the information on basic configuration of the RNC object group. Table 2-28 Parameters about the information on basic configuration of object groups Parameter Name IP neVersion className RNCID MCC MNC Description Name of the object group. IP address of the object. The IP address varies with the object tree on the left. NE version of the object. The NE version varies with the object tree on the left. NE class name of the object. The NE class name varies with the object tree on the left. The RNC ID uniquely identifies an RNC node within the scope of the PLMN. Mobile country code that the RNC belongs to. Mobile network code that the RNC belongs to.
Related Tasks
2.6.4.1 Checking the Information on Basis RNC Configuration
2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC
This part describes the parameters about the information on the Iu/Iur interface in the RNC. Table 2-29 lists the parameters about the information on the Iu/Iur interface. Table 2-29 Parameters about the information on the Iu/Iur interface Parameter Index Name Type Property Name
Issue 06 (2008-12-16)
Description Index of the destination signalling point. The range of the index is from 0 to 37 and the step length is 1. Interface name of the DCP destination signalling point Interface type of the DCP destination signalling point Index name of the current destination signalling point
2-229
Parameter Property Value
Description Index value of the current destination signalling point
Related Tasks
2.6.4.3 Checking the Information on the Iu/Iur of the RNC
2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface
This part describes the parameters about the information on specified links of the Iu/Iur interface in the RNC. Table 2-30 lists the parameters about the information on specified links of the Iu/Iur interface in the RNC. Table 2-30 Parameters about the information on specified links of the Iu/Iur interface Parameter Index Name Type Property Name Property Value Description Index of the destination signalling point. The range of the index is from 0 to 37 and the step length is 1. Interface name of the DCP destination signalling point Interface type of the DCP destination signalling point Index name of the current destination signalling point Index value of the current destination signalling point
Related Tasks
2.6.4.4 Checking the Information on Specified Links of the Iu/Iur Interface
2.8.59 Parameters for Checking the Information on the Iub Interface of the RNC
This part describes the parameters about the information on the Iub interface in the RNC object group. Table 2-31 lists the parameters about the information on the Iub interface in the RNC object group. Table 2-31 Basic parameters of the Iub interface Property Name Name ID IP
2-230
Property Value Name of the current object ID of the current object IP address of the current object
Issue 06 (2008-12-16)
Property Name Frame No Sub System No Slot No Link No
Property Value Number of the frame that the board is located in Sub-system number that the current board bears Number of the current board is located in Link number that the IUB interface bears
Related Tasks
2.6.4.5 Checking the Information on the Iub Interface of the RNC
2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface
This part describes the basic parameters about the information on specified links of the Iub interface in the RNC object group. Table 2-32 lists the basic parameters about the information on specified links of the Iub interface in the RNC object group. Table 2-32 Basic parameters of the Iub interface Property Name Identifier Serial Number Property Value Location where the alarm occurs Serial number of the alarm. The serial number is the keyword of alarm records. Based on the serial number, you can determine a unique alarm. NE name in the network Alarm ID MO object name. When the object is a real NE, the MO object is consistent with the NE name. When the object is a virtual NE, the MO object is the NE type of the object. Alarm name that enables you to quickly locate the details about alarms. Take the alarm name Database Threshold Alarm as an example. Based on this name, you can locate the details about the alarm. Source of the alarms in the network such as Power System, Trunk System, and Inside Element Management. Alarm levels that consist of four levels: critical alarm, major alarm, minor alarm, and warning. Time when an alarm occurs. Occurrence time can be server time or network element time.
NE Name Alarm ID MO Object
Alarm Name
Type Level Occurrence Time
Issue 06 (2008-12-16)
2-231
Property Name Status
Property Value Indicates whether a fault alarm or an event alarm is acknowledged and cleared, such as Unacknowledged and uncleared.
Related Tasks
2.6.4.6 Checking the Information on Specified Links of the Iub Interface
2.8.61 Parameters for Checking the E1/T1 Status of the RNC

This part describes the parameters about the E1T1 status of the RNC. Table 2-33 lists the parameters about the E1T1 status of the RNC. Table 2-33 Parameters about E1T1 status Parameter Frame No Description Number of the frame in which the board with the E1T1 interface is located Valid range of the parameter: 1 or 3 to 17 Slot No Number of the slot that the board with the E1T1 interface is located in Valid range of the parameter: 0 or 15 Link No E1T1 link number that begins from bottom to up Valid range of the parameter: 0 or 62If the port type is WOSE/ WOSEb/WOSEc_OPORT, the range is from 0 to 62.If the port type is WOSE/WOSEb/WOSEc_EPORT, the range is from 0 to 7.If the port type is WBIE/WBIEb_EPORT, the range is from 0 to 31. Use Status NodeB Name N7DPC Name Use status that has two states: Unused and Used NodeB name that the link maps Name of the destination signalling point
Related Tasks
2.6.5.2 Checking the E1/T1 Status of the RNC
2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC
This part describes the parameters about the distribution of NodeB and cells on the RNC. Table 2-34 lists the details about the parameters.
2-232
Issue 06 (2008-12-16)
Table 2-34 Parameters about the distribution of NodeB and cells on the RNC Parameter Frame No Sub System No Number of NodeB Number of Cell Number of NodeB with Zero Cell Number of NodeB with One Cell Number of NodeB with Two Cells Number of NodeB with Three Cells Number of NodeB with More than Three Cells Description Number of the frame in which the board is located Sub-system number of a board Total NodeB number in the current object group Total cell number in the current object group Total number of NodeB with zero cell in the current object group Total number of NodeB with one cell in the current object group Total number of NodeB with two cells in the current object group Total number of NodeB with three cells in the current object group Total number of NodeB with more than three cells in the current object group
Related Tasks
2.6.4.2 Checking the Distribution of NodeB and Cells on the RNC
2.8.63 Parameters for Checking the Information on Basic NodeB Configuration

This part describes the parameters about the information on basic configuration of the NodeB object group. Table 2-35 lists the parameters about the information on basic configuration of the NodeB object group. Table 2-35 Parameters about the information on basic configuration of object groups Property Name Name IP neVersion className ID
Issue 06 (2008-12-16)
Property Value Name of the object group IP address of the object. The IP address varies with the object tree on the left. NE version of the object. The NE version varies with the object tree on the left. NE class name of the object. The NE class name varies with the object tree on the left. Uniquely identifies a NodeB.
2-233
Property Name Frame No Sub System No TNLBEARERTY PE NODEBPROTCL VER TRANSDELAY
Property Value Indicates the WRBS frame that manages NodeBs. Identifies the subsystem of the WSPUb where the NodeB is located. Identifies the transmission type used by Iub interfaces. Indicates the protocol version used by the NodeB. Indicates the round-trip delay of Iub interfaces.
Related Tasks
2.6.4.7 Checking the Information on Basic NodeB Configuration
2.8.64 Parameters for Checking the Information on Basic Cell Configuration

This describes the parameters for checking the information on basic cell configuration. Table 2-36 describes the parameters related to the basic configuration of a cell. Table 2-36 Parameters related to the basic configuration of a cell Parameter Name ID PSCRAMBCODE MAXTXPOWER Attribute Value Name used to uniquely identify a cell. Value range: It consists of 1 to 31 characters. ID used to uniquely identify a cell. Value range: 0 to 65535. Primary downlink scrambling code. Value range: 0 to 511. Maximum transmit power of a cell. This parameter indicates the sum of the maximum transmit power over the downlink channels in a cell. The value depends on network planning.
l l
Value range: 0 to 500. Physical value range: 0 to 50, with a step of 0.1.
UARFCNUPLINK UARFCNDOWNLI NK NodeB name LAC
Uplink frequency number. Its value range depends on the frequency selected. Downlink frequency number. Its value range depends on the frequency selected. Name a specific NodeB Location area code. Value range: H'0000 to H'FFFF (0 to 65535), excluding H'0000 and H'FFFE. This parameter defines a location area for a GSM-MAP PLMN. Its value is defined by the operator.
2-234
Issue 06 (2008-12-16)
Parameter SAC
Attribute Value Service area code. The value range is H'0000-H'FFFF (0-65535). Together with PLMN-Id and LAC, this parameter defines the service area indicator (SAI). The SAI identifies an area composed of one or more cells belonged to the same location area. This area identified is also called service area, and used to identify the position of a UE. The SAC is defined by the operator. Its value is defined by the operator. Band of the frequency band of the cell. Value range: Band1, Band2, Band3, Band4, Band5, Band6, BandIndNotUsed.
BANDIND
TCELL SUPSSDT TXDIVERSITYIN D DPCHTXDIVERSI TYMODE HSPDSCHTXDIVE RSITYMODE LOCELL CFGRACIND
Difference between the cell system frequency number (SFN) and the NodeB frequency number (BFN). Indicates whether the cell supports Site Selection Diversity TPC (SSDT). Indicates whether the transmission diversity mode of the common channel is activated. Indicates the transmission diversity mode of the dedicated channel. Indicates the transmission diversity mode of the HS-PDSCH. Identifier of the local cell, which maps to the logical cell. Indicates whether the RAC is configured.
l l
NOT_REQUIRE: RAC is not configured. REQUIRE: RAC is configured.
RAC CLOSEDLOOPTI MEADJUSTMODE
Identifies the routing area in the LAI, The fixed length is one byte. It is mainly used in PS services. Identifies whether the cell supports the closed loop timing adjustment mode.
Related Tasks
2.6.4.8 Checking the Information on Basic Cell Configuration

This part describes the parameters related with the configuration status of the RNC, NodeB and cell.
Parameter Related with the Configuration Status of Cells

Parameter Name
Issue 06 (2008-12-16)
Description Indicates the name of a cell.

Parameter Administrative Status
Description Indicates whether a cell is blocked by the operator on the administration console of the RNC. If a cell is blocked, the users accessing the cell are not affected while new users cannot access the cell. Value range: blocked and unblocked
Operational Status
Indicates whether a cell is available. This parameter indicates a general status. If all the required resources of a cell, such as common channels and ports, are available and the administrative status of the cell is unblocked, infer that the operational status of the cell is available. Value range:
l l
Available: indicates that a cell is normal and users can access the cell. Unavailable: indicates that users cannot access a cell.
Activate Status
Indicates whether a cell can provide services. value range: activated and deactivated
Parameters Related to the Configuration Status of the RNC and the NodeB
Parameter Name Connect State Description Indicates the name of a monitoring object. Indicates whether the monitoring object is disconnected with a server. Value range: connected and disconnected
Related Concepts
2.6.1.3 Configuration Status of Monitored Objects
Related Tasks
2.6.3.4 Checking Detailed Information of Configuration Status
2.8.66 Parameters for Checking the Information on CCH Configuration

This part describes the parameters related to the basic configuration of the common channel in a cell. For details of the parameters related to the basic configuration of the common channel in a cell, refer to Table 2-37. Table 2-37 Parameters related to the basic configuration of the common channel in a cell Parameter Name
2-236
Description Name of the cell

Parameter ID NodeB Name PSCHPower
Description ID used to uniquely identify a cell. Value range: 0 to 65535. Name of the NodeB managing the current cell. Indicates the offset of the PSCH transmit power from the PCPICH transmit power in a cell
l l
Value range (in dBs): -350 to 150 Physical value range: -35 to 15, with a step of 0.1.
SSCHPower
Indicates the offset of the SSCH transmit power from the PCPICH transmit power in a cell
l l
Value range (in dBs): -350 to 150 Physical value range: -35 to 15, with a step of 0.1
PCPICHPower
PCPICH transmit power. This parameter is set based on the actual system environment such as cell coverage (radius) and geographical environment. For the cells to be covered, the downlink coverage should be guaranteed as a premise. For the cells requiring soft handover area, this parameter should satisfy the proportion of soft handover areas stipulated in the network planning. If the maximum transmit power of the PCPICH is configured too great, the cell capacity will be decreased because a lot of system resources will be occupied and the interference with the downlink traffic channels will be increased.
l l
Value range (in dBs): -100 to 500 Physical value range: -10 to 50, with a step of 0.1
PRACH PHYCHID SCCPCH PHYCHID PCCPCH PHYCHID
Uniquely identifies a random access physical channel in the cell Uniquely identifies the primary common control physical channel in the cell Uniquely identifies the secondary common control physical channel in the cell
Related Tasks
2.6.4.9 Checking the Information on CCH Configuration
2.8.67 Parameters for Checking the Information on Neighbors

This describes the parameters for checking the information on neighbors.Three types of neighboring cells are available: Intra-frequency neighboring cell, inter-frequency neighboring cell, and GSM neighboring cell. The three types of cells have the following meanings:
l
Intra-frequency neighboring cell

Issue 06 (2008-12-16)
The intra-frequency neighboring cell covers an area that partly overlaps the current service cell. In addition, the carrier frequency used by the intra-frequency neighboring cell is the same as the current service area.
l
inter-frequency neighboring cell The intra-frequency neighboring cell covers an area that partly overlaps the current service cell. In addition, the carrier frequency used by the intra-frequency neighboring cell is different from the current service area.
GSM neighboring cell The GSM neighboring cell is close to the current service cell. The GSM neighboring cell, however, belongs to the GSM or GSM/GPRS system.
Table 2-38 describes the parameters related to intra-frequency neighboring cells. Table 2-38 Parameters related to intra-frequency neighboring cells Parameter CELLID RNC ID NCELLID READSFNIND Description ID of a cell, uniquely identifying a cell. Value range: 0 to 65535. ID of a neighboring cell's RNC , uniquely identifying an RNC. Value range: 0 to 4095. ID of a cell, uniquely identifying a cell. Value range: 0 to 65535. Indicate whether to read the System Frame Number (SFN) of the neighboring cell. The value range is as follows:
l l
NOT_READ: not read READ: read
CELLINDIVIDAL OFFSET
Indicates the offset of the cell CPICH measurement. This parameter is used in handover decisions and its value depends on network planning. It is used to move the cell edges in handover algorithm. Configure this parameter based on the actual situation in network planning. For 1A/ 1C/1D events, the triggering chance is in positive correlation with the value of this parameter. For 1B/1F events, the triggering chance is in negative correlation with the value of this parameter. The value range is as follows: -20 to 20, with the unit as dB.
CELLSFORBIDD EN1A
Indicates whether the addition of the cell into the active set affects the relative threshold of the event 1A.
l
NOT_AFFECT: The addition does not affect the relative threshold of the event 1A. AFFECT: The addition affects the relative threshold of the event 1A. NOT_AFFECT: not affect. AFFECT: affect.
The value range is as follows:

l l
2-238
Issue 06 (2008-12-16)
Parameter CELLSFORBIDD EN1B
Description Indicates whether the addition of the cell into the active set affects the relative threshold of the event 1B.
l
NOT_AFFECT: The addition does not affect the relative threshold of the event 1B. AFFECT: The addition affects the relative threshold of the event 1B. NOT_AFFECT: not affect. AFFECT: affect.
The value range is as follows:

l l
QOFFSET1SN
Indicates load level offset 1 between connection mode center and neighboring cells. This parameter is used for the cell offset of CPICH RSCP measurement value in cell selection and re-selection. This parameter is used for changing the cell border. In cell selection or reselection, this parameter is in negative correlation with the probability of selecting inter-RAT neighboring cells. The value range is as follows: Value range (in dBs): -50 to 50. The recommended value of this parameter is 0.
QOFFSET2SN
Indicates load level offset 2 between connection mode center and neighboring cells. This parameter is used for the cell offset of CPICH Ec/No measurement value in cell selection and re-selection. This parameter is used for changing the cell border. In cell selection or reselection, this parameter is in negative correlation with the probability of selecting inter-RAT neighboring cells. The value range is as follows: Value range (in dBs): -50 to 50. The recommended value of this parameter is 0.
TPENALTYHCSR ESELEC
Indicates the hierarchical cell re-selection penalty timer. The larger the parameter is, the smaller the probability of selecting neighboring cells.
l l
The value range is as follows: D0, D10, D20, D30, D40, 50, D60 Physical value range (in seconds): 0, 10, 20, 30, 40, 50, 60.
Table 2-39 describes the parameters related to inter-frequency neighboring cells. Table 2-39 Parameters related to inter-frequency neighboring cells Parameter CELLID RNC ID NCELLID Description ID of a cell, uniquely identifying a cell. Value range: 0 to 65535. ID of a neighboring cell's RNC , uniquely identifying an RNC. Value range: 0 to 4095. ID of a cell, uniquely identifying a cell. Value range: 0 to 65535.
Issue 06 (2008-12-16)
2-239
Parameter READSFNIND
Description Indicate whether to read the System Frame Number (SFN) of the neighboring cell The value range is as follows:
l l
NOT_READ: not read READ: read
CELLINDIVIDALOFFSET
Indicates the offset of the cell CPICH measurement. This parameter is used in handover decisions and its value depends on network planning. It is used to move the cell edges in handover algorithm. Configure this parameter based on the actual situation.
l
The value range is as follows: -20 to 20, with the unit as dB. The value range is as follows: Physical value range: -10 to 10, with a step length of 0.5
BLINDHOFLAG
Indicates whether to perform blind handover. The value 0 represents the highest priority. Priorities 0 through 15 are assigned to concentric neighboring cells, which can ensure successful handover. Priorities 16 through 30 are assigned to neighboring cells for blind handover, which cannot ensure successful handover. Value range: 0-30
QOFFSET1SN
Indicates the offset between inter-RAT neighboring cell and WCDMA cell. In cell selection or re-selection, this parameter is in negative correlation with the probability of selecting inter-RAT neighboring cells. The value range is as follows: -50 to 50, with the unit as dB.
QOFFSET2SN
Indicates the offset 2 between inter-RAT neighboring cell and WCDMA cell. In cell selection or re-selection, this parameter is in negative correlation with the probability of selecting inter-RAT neighboring cells. The value range is as follows: -50 to 50, with the unit as dB.
TPENALTYHCSRESELEC
Indicates the hierarchical cell re-selection penalty timer. The larger the parameter is, the smaller the probability of selecting neighboring cells.
l
Table 2-40 describes the parameters related to GSM neighboring cells.
2-240
Issue 06 (2008-12-16)
Table 2-40 Parameters related to GSM neighboring cells Parameter CELLID GSMCELLINDEX Description ID of a cell, uniquely identifying a cell. Value range: 0 to 65535. Index of a GSM cell, uniquely identifying a GSM cell. The GSM cell identified by this parameter is already configured in the ADD GSMCEL command. This cell becomes the neighboring cell of a WCDMA cell. The difference between GSMCELLINDEX and CID is that the previous one is unique to identify a GSM cell while the latter one is not. Value range: 0-4095 CELLINDIVIDALOFFSET It is set according to the topographic feature. This parameter is used in inter-RAT handover decision. The smaller the parameter, the lower the handover priority of the GSM cell. The value range is as follows: -50 to 50, with the unit as dB. BLINDHOFLAG Indicates whether to perform blind handover. FALSE means that the cell is not in candidate cells for blind handover, so blind handover to this cell cannot be triggered. True means that the cell is in candidate cells for blind handover, so blind handover to his cell might be triggered. Value range: FALSE and TRUE QOFFSET1SN Indicates the offset between inter-RAT neighboring cell and WCDMA cell. In cell selection or re-selection, this parameter is in negative correlation with the probability of selecting inter-RAT neighboring cells. The value range is as follows: -50 to 50, with the unit as dB. TPENALTYHCSRESELEC Indicates the hierarchical cell re-selection penalty timer. When the penalty mechanism works, the UE is not allowed to re-select between the two cells where the last reselection occurs. This mechanism avoids the frequent cell re-selections.
l
Related Tasks
2.6.4.10 Checking the Information on Neighbors
Issue 06 (2008-12-16)
2-241
2.8.68 Parameters for Checking the Values of Cell Monitoring Counters

This part describes the parameters related to cell monitoring counters. For details of the parameters, refer to Table 2-41. Table 2-41 Parameters related to NodeB and cell statistics Parameter Name CounterName CounterUnit CounterResult CounterTime Description Number of the subrack that houses the board Name of a counter Unit that a counter belongs to Result of a counter Report time of a counter
Related Tasks
2.6.5.5 Checking the Values of Cell Monitoring Counters
2.8.69 Parameters for Searching for Objects

In case that many monitored objects exist, you can search the related monitored objects by using the fuzzy search method. Then you can locate the object quickly. When setting the parameters to be found, refer to Table 2-42. Table 2-42 Parameters for searching for monitored objects Parameter Search Keyword Object Type Search Scope Case Sensitive Description Keywords of the object. It can include letter, number and underline. The value range is 1-256 characters. The value can be RNC, NodeB or CELL. You can search in all the object groups or in a specified object group. This parameter can be selected or deselected. If selected, it means case sensitive. If deselected, it means not case sensitive. The options are available. You can search by the object name. Research the result list. The node names and pathes are displayed.
Search Style Search Result
2-242
Issue 06 (2008-12-16)
Related Tasks
2.6.3.2 Searching for Objects

This section describes the parameters of system monitor settings. You can refer to these parameters when you set the server thresholds.
Performance
Name CPU sustained overload times(times)
NOTE When the database of the M2000 server is DB2, the M2000 client does not display this parameter.
Description Description: Times of continuously sampling the CPU usage. If the CPU usage that is sampled each time exceeds the sum of the preset value and offset value, the M2000 raises a CPU alarm. If the CPU usage that is sampled each time is less than the sum of the preset value and offset value, the M2000 raises a cleared alarm. Description: Interval of performance refreshing. Description: Threshold of the CPU usage.
Settings Value: Value range: 40-400 Default value: 40
Performance status refresh interval(sec.)
Value: Value range: 2-60 Default value: 3 Value: Value range: 1-99. Default value: 80. Offset value range: 0-10. Default value: 5.
CPU used rate(%)
Memory used rate(%)
Description: Threshold of the memory usage. When the memory usage exceeds the sum of the preset value and offset value, the M2000 raises a memory busy alarm. When the memory usage is less than the sum of the preset value and offset value, the M2000 raises a cleared alarm.
Value: Value range: 1-99. Default value: 87. Offset value range: 0-10. Default value: 3.
Issue 06 (2008-12-16)
2-243
Hard Disk
Name Hard disk refresh interval (sec.) Description Description: Interval of hard disk refreshing. Description: Default thresholds of all the hard disk usage on the M2000 server. When the hard disk usage of the alarms exceeds the sum of the preset value and offset value of a certain level, the M2000 raises a hard disk alarm. Settings Value: Value range: 60-3600 Default value: 60 Value:
l
Default value(%)
Value range: 1-100 Default value:

Warning: 60 Minor: 70 Major: 80 Critical: 90
Offset value range: 0-10 Offset default value:

Warning: 3 Minor: 3 Major: 3 Critical: 2
NOTE The threshold of a low-level alarm must be smaller than the threshold of a high-level alarm.
Used rate(%)
Description: Thresholds of all the hard disk usage on the M2000 server. When the hard disk usage exceeds the sum of the preset value and offset value, a hard disk alarm is raised. When you select Default value, the M2000 uses the thresholds defined in default value. When you select Customize value, the M2000 uses the thresholds that you define manually.
Value: Value range: 1-99 Offset value range: 0-10

NOTE The threshold of a low-level alarm must be smaller than the threshold of a high-level alarm.
2-244
Issue 06 (2008-12-16)
Database
Name Database used rate(%) Description Description: Settings Value: Default value: 90 Database status refresh interval(sec.) Description: Interval of database refreshing. Description: Select the database name and set whether to monitor the database. Value: Value range: 300-3600 Default value: 300 Setting method: In the left list, select the database name. In the dropdown list on the right, select enable or disable.
Threshold of database usage. Value range: 1-100
Database Monitor Settings
Services
Name Service refresh interval(sec.) Description Description: Interval of service refreshing. Settings Value: Value range: 60-3600 Default value: 60 Service Monitor Screen Tip Settings Description: Set whether to display the service status at the lower right corner of the M2000 client by or . If all the monitored services are is displayed; if a running, monitored service is stopped, is displayed. The Service Monitor tab is displayed when or is clicked. Setting method: In the left list, select the service name. In the dropdown list on the right, select enable or disable.
Related Tasks
2.7.1 Setting Monitoring Parameters 2.7.1.2 Setting the Parameters for the M2000 Performance Monitoring 2.7.1.3 Setting the Parameters for the M2000 Hard Disk Monitoring 2.7.1.4 Setting the Parameters for the M2000 Database Monitoring
2.8.71 Parameters for Monitoring Performance of the M2000 Server

This section describes the parameters of the query result displayed in the Performance Monitor tab.
Parameters
Name Server Name Description Description: Name of the M2000 server. Server Status Description: Status of the M2000 server, including status of the primary server and secondary server. OS Description: Operating system of the server. Free Physical Memory(KB) Description: Remaining physical memory space. Total Physical Memory(KB) Description: Total physical memory space. Free Swap Memory(KB) Description: Remaining virtual memory space. Total Swap Memory(KB) Description: Total virtual memory space. CPU Usage Rate(%) Description: CPU usage. Memory Usage(%) Description: The usage of the total memory space (including physical memory and virtual memory).
Related Tasks
2.7.2 Monitoring the M2000 Performance Status
2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server

This section describes the parameters of the query result displayed in the Hard Disk Monitor tab.
Parameters
Name Server Name Description Description: Name of the M2000 server. Server Status Description: Status of the M2000 server, including Active and Standby.
2-246
Issue 06 (2008-12-16)
Name OS
Description Description: Operating system of the server.
Partition(Mounted Path)
Description: Hard disk partitions and their mapping paths.
Total Size(KB)
Description: Total space of a specific partition, equals to the sum of Used Size and Free Size.
Used Size(KB)
Description: Used space of a specific partition.
Free Size(KB)
Description: Available space of a specific partition.
Used Rate(%)
Description: Current usage of a specific partition.
Status
Description: Current status of a specific partition, including normal and abnormal. If the usage exceeds the maximum, the system displays Abnormal.
Related Tasks
2.7.3 Monitoring the M2000 Hard Disk Status
2.8.73 Parameters for Monitoring Database of the M2000 Server

This section describes the parameters of the query result displayed in the Database Monitor tab.
Parameters
Name Database Name Description Description: Name of the database on the M2000 server. Server Name Description: Name of the M2000 server. OS Description: Operating system in the server. Total Data Space(KB) Description: Total data space.
Issue 06 (2008-12-16)
2-247
Name Used Space(KB)
Description Description: Used data space.
Free Space(KB)
Description: Remaining data space.
Used Rate(%)
Description: Usage rate of the used data space and total data space.
Log Space(KB) Total Log Space(KB) Free Log Space(KB)
Description: Total log space. Description: Remaining log space.
Status
Description: Database status, including normal and abnormal. If the database usage exceeds the threshold, the system displays Abnormal.
Related Tasks
2.7.4 Monitoring the M2000 Database Status
2.8.74 Parameters for Monitoring Services of the M2000 Server

This section describes the parameters of the query result displayed in the Service Monitor tab.
Parameters
Name Agent Name Description Description: The name of a process. Service Name Description: The name of a service. Service Description Description: The description information of functions and interfaces provided by a service. Status Description: The status of a service. Auto Restart Count Description: The times that the service is restarted automatically when it is stopped abnormally.
2-248
Issue 06 (2008-12-16)
Name Service Start Time
Description Description: The time that the service is started.
Server Name
Description: The name of the server.
Related Tasks
2.7.5 Monitoring the M2000 Service Status
2.8.75 Parameters for Monitoring Process of the M2000 Server

This section describes the parameters of the query result displayed in the Process Monitor tab.
Parameters
Name Agent Name Description Description: Name of a process. Process ID Description: ID of a process. Handle Number Description: Amount of handles used by a process. CPU Usage Rate(%) Description: CPU usage by a process. Memory Usage(KB) Description: Memory usage by a process. Unit: KB. DB Connection Number Description: Amount of connected databases. Thread Number Description: Amount of connected threads in a process.
NOTE
If the M2000 uses the DB2 database, the client does not display DB Connection Number.
Related Tasks
2.7.6 Monitoring the M2000 Process Status
Issue 06 (2008-12-16)
2-249
3 Topology Management
3
About This Chapter
Topology Management
Topology management offers the function of constructing and managing the topology structure of the whole network to display the networking situation and running status of the equipment. You can query and monitor the entire network operation in real time through the topology view. 3.1 Basic Knowledge of Topology Before performing topology management operations, you must be familiar with the basic knowledge of topology such as network topology type, topology object, and topology shortcut menu. The basic topology knowledge helps you understand the contents of topology management. 3.2 Constructing a Physical Subnet In the topology view, the physical subnet is used to show the hierarchical network structure. By designing physical subnets properly, you can improve the visibility of the telecommunication network and the operability of the network management system. 3.2.4 Creating Physical NEs A physical NE is the communication equipment that has the physical connection with the M2000 and can be managed by the M2000. Only when the related physical NE is created on the M2000, the M2000 can manage the communication equipment. 3.4 Managing SNMP Parameter Templates The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. The template types consist of SNMPV1, SNMPV2c, and SNMPV3. By managing SNMP parameter templates, you can browse the detailed information on the existing templates on the current server. In addition, you can add, modify, and delete the templates. 3.5 Monitoring NEs You can monitor the alarm status and connection status on the NEs. By monitoring NEs, you can detect and solve the abnormalities in real time. 3.6 Adjusting the Network Topology After creating a subnet, NE, or link, you can adjust the network topology as required. Adjusting the network topology involves modifying and deleting a subnet, NE, or link. 3.7 Adjusting the Topology View
You can adjust the topology view as required. For example, you can expand or hide the topology navigation tree, switch the current subnet, display the topology view in full screen, zoom in or out of the view, and customize the topology tips. 3.8 Printing a Topology View Using the print function, you can print the topology view to paper. 3.9 Reference for Topology Management Interfaces This part describers the topology management interfaces and relevant parameters, which helps you perform the operation related to topology management.
3-2
Issue 06 (2008-12-16)
3.1 Basic Knowledge of Topology

Before performing topology management operations, you must be familiar with the basic knowledge of topology such as network topology type, topology object, and topology shortcut menu. The basic topology knowledge helps you understand the contents of topology management. 3.1.1 Topology Management Function Topology management is used to construct and manage the entire network topology and helps you know the networking and operational status of the devices. You can browse the topology view to know and monitor the entire network status in real time. 3.1.2 Objects in a Topology View Topology objects refer to the elements in a network.
3.1.1 Topology Management Function

Topology management is used to construct and manage the entire network topology and helps you know the networking and operational status of the devices. You can browse the topology view to know and monitor the entire network status in real time. Topology management provides the following functions:
l
Three topology types: physical topology, electronic map, and custom view. You can define and categorize different topology views according to actual requirements. The topology views of the MSC Pool and CDMA Pool are custom views. To create an MSC pool, refer to 12.2 Creating MSC Pool Topology on the M2000. To create a CDMA pool, refer to 13.2 Creating CDMA Pool. Different icons are used to identify different topology object types. Small icons are used to identify the status of the topology objects, such as disconnected and synchronizing. You can add, delete, modify, and move the NEs, subnets, and links in the topology view. Status of each managed object is displayed, for example, whether there is a fault and whether the objects are connected with other NEs. You can query or browse the alarm information about the NEs through the topology view. You can customize the initial view, filter the topology objects by type, lay out the topology objects by legend, and lay out the topology objects by name or type. You can set the background for the topology view. You can know the position of a device node through the icon position in the background. You can zoom in or zoom out globally or partially on the topology view to view the network topology structure. The topology view supports global and local topology search and helps you locate a topology object quickly. The topology view provides auxiliary tools such as overview, print, and filter to help you implement topology management.
l l
l l
3.1.2 Objects in a Topology View

Topology objects refer to the elements in a network. Each element managed by the network management system is called an object.
l
Subnet In the M2000, a large network can be divided into several smaller networks based on a specific rule (for example, by region) for the convenience of network management. In topology, these smaller networks are called subnets. Subnets exist in the physical topology and logical topology.
NE NEs are used to identify concrete entity devices, such as switches and routers. NEs can be grouped into physical NEs and virtual NEs.
Group NE In a telecommunication network, some NEs are interdependent. A group NE is an NE that has the characteristics of both NE and subnet.
Links Links refer to the links between NEs that are mapped in the topology, including physical links and virtual links. A physical link indicates that there is physical connection between two physical NEs. Currently the M2000 supports six types of links: M3UA, H248, BICCSCTPLNK, DATALINK, MTP3, and MTP3B. M3UA, H248, and BICCSCTPLNK links are created by the system automatically. DATALINK, MTP3 and MTP3B links are created manually. Only physical links that are manually created can be deleted. A virtual link refers to the logic link between two NEs (including physical NEs and virtual NEs), and you can set up a virtual link manually.
3.2 Constructing a Physical Subnet

In the topology view, the physical subnet is used to show the hierarchical network structure. By designing physical subnets properly, you can improve the visibility of the telecommunication network and the operability of the network management system. 3.2.1 Designing the Physical Topology Before deploying NEs in the physical topology, you need to design the physical subnet. The physical topology presents the topology structure of the actual communication network, and you can operate and maintain the topology easily. 3.2.2 Setting the Topology Background You can set a proper background for the topology view according to the device layout; thus you can know the locations of the devices directly. 3.2.3 Creating a Physical Subnet You can create a physical subnet in the physical view or electronic view, and add NEs to the physical subnet. 3.2.4 Creating Physical NEs A physical NE is the communication equipment that has the physical connection with the M2000 and can be managed by the M2000. Only when the related physical NE is created on the M2000, the M2000 can manage the communication equipment. 3.2.5 Creating a Virtual NE Virtual NEs refer to the devices that cannot be managed by the M2000 in the entire communication network. You can have a better understanding of the entire communication network by adding the existing virtual NEs to the physical topology. 3.2.6 Creating IP Device An IP device refers to the IP networking device in the mobile network. After you create IP device on the M2000 topology, the communications between the M2000 and an IP device are
established. Thus, M2000 can perform centralized management and maintenance on multiple IP devices. 3.2.7 Creating a Physical Link A physical link indicates the actual physical connection between two physical NEs. By establishing a physical link, you can know the communication status of the connected NEs. You need to manually create MTP3 and MTP3B links, which cannot be automatically created by the system. 3.2.8 Creating a Virtual Link Virtual links are not the actual links in the network. They indicate the logical relation between NEs. By creating virtual links, you can understand the relations between NEs better. 3.2.9 Creating Links in Batches To reduce the maintenance workload, M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology at the same time. 3.2.10 Setting an NE as a Transfer Server The M2000 software management is based on the FTP. Therefore, you need to set the FTP server, that is, the relay server, to transfer files between the M2000 and NEs. Since firewall always exists between NEs and the M2000, many NEs cannot establish an FTP connection with the M2000. If an NE supports the FTP server mode, you can set the NE as an FTP Server. In this case, the NE acts as the FTP server, and the M2000 server acts as the FTP client. The NE acting as FTP server connects the M2000 to other NEs and improves network access efficiency for the purpose of file transfer.
3.2.1 Designing the Physical Topology

Before deploying NEs in the physical topology, you need to design the physical subnet. The physical topology presents the topology structure of the actual communication network, and you can operate and maintain the topology easily. The left of the logical topology is a navigation tree and the right is a topology view. The navigation tree displays the hierarchies between the topology objects, and the topology view displays the positions of the topology objects. You can divide the physical subnets as follows:
l l l l
By region: based on the regions where the NEs are located. By NE type: based on the types of the NEs. By IP address or network segment: based on the IP addresses of the NEs. By responsible person: based on the responsible persons of the NEs.
3.2.2 Setting the Topology Background

You can set a proper background for the topology view according to the device layout; thus you can know the locations of the devices directly.
Context
Only the image files in the formats of *.gif or *.jpg can be imported, and the file size cannot exceed 1MB.
Issue 06 (2008-12-16)
3-5
Procedure
Step 1 Choose Topology > Main Topology. Step 2 Right-click in the topology view and choose Set Background or select Topology > Set Background. Step 3 In the Set Background dialog box, select a subview (also known as subnet) in the table, then click Select Background. Step 4 In the Select Map File dialog box, select an image, then click Open.
NOTE
To remove the background, select empty.gif in the Select Map File dialog box and then click Open.
3.2.3 Creating a Physical Subnet

You can create a physical subnet in the physical view or electronic view, and add NEs to the physical subnet.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the Current Viewdrop-down list, select a view where you want to create a physical subnet, such asPhysical View. Step 3 Choose one of the following method to start to create the physical subnet: l l In navigation tree of the topology, choose New > Create Physical Subnet . Right-click in the topology view and choose New > Create Physical Subnet .
Step 4 Click the Basic Attribute tab. Set the name, coordinate, background, and memo. Step 5 Click the Objects Selection tab. In the Available Objects list, select a NE or a subnet, click to add the selected object to the Selected Objects list. Thus the object is added to the subnet being created.
NOTE
In the Selected Objects list, click to the Available Objects list.
. The object added to the subnet being created can be moved back
Step 6 Click OK. The physical subnet is created successfully in the current subnet or view. You can double-click the subnet to open it. ----End
Related References
3.9.3 Parameters for Setting a Physical Subnet
3.2.4 Creating Physical NEs

A physical NE is the communication equipment that has the physical connection with the M2000 and can be managed by the M2000. Only when the related physical NE is created on the M2000, the M2000 can manage the communication equipment. 3.3.1 NE Type The mobile network devices managed by the M2000 are categorized according to the home network, service function, and management functions supported by NEs. 3.3.2 Basic NE information This part describes the basic NE information. You are required to acquire the basic NE information before creating NEs, modifying NEs, and querying NE reports. 3.3.3 Creating a Physical NE This describes the procedure for creating a physical NE on the topology view. After the NE is created, the M2000 obtains the configuration data of the NE by synchronizing the NE. 3.3.4 Creating Multiple Physical NEs To reduce the maintenance workload, the M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology at the same time.
3.2.5 Creating a Virtual NE

Virtual NEs refer to the devices that cannot be managed by the M2000 in the entire communication network. You can have a better understanding of the entire communication network by adding the existing virtual NEs to the physical topology.
Procedure
Step 1 In the physical navigation tree or physical view, right-click the subnet where you want to create an NE, and then choose New > Create Topo Object . Step 2 Select a specified virtual NE from the navigation tree of the Create Topo Object dialog box. Step 3 In the right part of the Create Topo Object dialog box, enter the name, coordinates, and memo. Step 4 Click OK. ----End
3.2.6 Creating IP Device

An IP device refers to the IP networking device in the mobile network. After you create IP device on the M2000 topology, the communications between the M2000 and an IP device are established. Thus, M2000 can perform centralized management and maintenance on multiple IP devices.
Prerequisite
l l
The network communications between the M2000 and an IP device are functioning well. The parameters used for connecting the M2000 is set on the IP device.
Issue 06 (2008-12-16)
3-7
Context
IP device includes SNMP, routers, and switches. After the IP device is successfully created, the M2000 system automatically obtains related alarms from the IP device if the IP device incurs faults.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 In the physical topology navigation tree or on the physical view, right-click the subnet of the NE to be created and choose New > Create Topo Object on the shortcut menu. Step 3 Select a mapping NE node under the Single Create node from the navigation tree in the left part of the Create Topo Object dialog box. Step 4 For details of the parameters, refer to 3.9.4 Parameters for Creating an IP Device.
TIP
When the SNMP is created, you can right-click the parameter panel of the SNMP template and choose Save to save the modification performed in the parameter template, or click Save As to save the current parameter information about the SNMP as a template.
Step 5 Click OK. You can view the execution progress of creating the IP device in the displayed Create NE Progress dialog box. You can click Detail in the dialog box to view the detailed information about creating an IP device.
NOTE
A dialog box is displayed to show the progress of creating the IP device. If the communications between the M2000 and an IP device are not functioning well, the status icon is displayed at the top left corner of the created IP device on the topology. The icon indicates that the NE is located in the disconnected state.
Step 6 Click Close. Then, the Create NE Progress dialog box is closed. ----End
Related References
3.9.4 Parameters for Creating an IP Device
3.2.7 Creating a Physical Link

A physical link indicates the actual physical connection between two physical NEs. By establishing a physical link, you can know the communication status of the connected NEs. You need to manually create MTP3 and MTP3B links, which cannot be automatically created by the system.
Prerequisite
l l
You have logged in to the M2000 client. The topology view and network levels are already planned.
Context
l
Currently the M2000 supports six types of links: M3UA, H248, BICCSCTPLNK, DATALINK, MTP3, and MTP3B. M3UA, H248and BICCSCTPLNK links can be
3-8
automatically created by the system. DATALINK, MTP3 and MTP3B links must be manually created.
l l
Only physical links that are manually created can be deleted. The physical links are named automatically by the system. To change the name of a physical link, see 3.6.6 Viewing/Modifying a Physical Link. The supported NE type varies with the link type. For details, see 3.9.5 Parameters for Physical Link.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Right-click the subnet node in the physical topology navigation tree or the physical topology view, and select New > Create Topo Object. Step 3 Select a specific link type from the navigation tree of the Create topo objects dialog box. You can use either of the following methods:
l l
Select a specific link type from the Link node under the Single Create node. Select the Link node under the Bulk Create node. Click Add in the right part of the window.
Step 4 Configure link information. For details of parameters about link information, refer to 3.9.5 Parameters for Physical Link.
TIP
l l
If you want to create multiple links, repeat step1 to step3. If you need re-configure link information, click Reset.
Step 5 Click OK. The system displays the Create Link prompt box. The progress of creating the link is shown. After the link is created successfully, a link is displayed between two NEs.
NOTE
After a physical link is set up, you can only modify its name.
Step 6 Click OK to close the Create Link prompt box. ----End
Related References
3.9.5 Parameters for Physical Link
3.2.8 Creating a Virtual Link

Virtual links are not the actual links in the network. They indicate the logical relation between NEs. By creating virtual links, you can understand the relations between NEs better.
Context
l
The two NEs at the both ends of a virtual link are called left node and right node. You can only select an NE as the right or left node. If you select a subnet or a link as the right or left node, the selection is invalid, and you need to select the node again.
Issue 06 (2008-12-16)
l l
When there is more than one virtual link between two NEs, a virtual link set is set up. Double-click the link set. A table is displayed, listing the links in the set.
Procedure
Step 1 In the physical navigation tree or physical view, right-click the subnet where you want to create a link, and then choose New > Create Topo Object . Step 2 Select the Virtual Link node under the Single Create node from the navigation tree of the Create Topo Object dialog box. Step 3 In the right part of the Create Topo Object dialog box, enter the name, type, and left node and right node of the virtual link. Step 4 Click OK. ----End
Related References
3.9.6 Parameters for Setting a Virtual Link
3.2.9 Creating Links in Batches

To reduce the maintenance workload, M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology at the same time.
Prerequisite
l l
You have logged in to the M2000 client. The topology view and network levels are already planned.
Context
l
Some physical links can be set up automatically through a program. For the other physical links that cannot be set up through the program, you can set them up manually. The physical links are named automatically by the system. To change the name of a physical link, see 3.6.6 Viewing/Modifying a Physical Link. The MGW and MSC Server support this function.
Procedure
Step 1 Choose Topology > Main Topology, theMain Topologywindow is displayed. Step 2 Right-click the subnet node in the physical topology navigation tree or the physical topology view, and select New > Create Topo Object. Step 3 Select the Link node under Bulk Create from the navigation tree of the Create topo objects dialog box. Step 4 Click Add in the right pane. Step 5 To know how to configure link information in Add a link, refer to 3.9.5 Parameters for Physical Link.

TIP
If you need re-configure link information, click Reset.
Step 6 Click OK to close the Add a link dialog box. Step 7 Repeat step4 to step6 to create multiple links. Step 8 Click OK. The system displays the Create Link prompt box. The progress of creating the link is shown. After the link is created successfully, a link is displayed between two NEs.
NOTE
After a physical link is set up, you can only modify its name.
Step 9 Click OK to close the Create Link prompt box. ----End
3.2.10 Setting an NE as a Transfer Server

The M2000 software management is based on the FTP. Therefore, you need to set the FTP server, that is, the relay server, to transfer files between the M2000 and NEs. Since firewall always exists between NEs and the M2000, many NEs cannot establish an FTP connection with the M2000. If an NE supports the FTP server mode, you can set the NE as an FTP Server. In this case, the NE acts as the FTP server, and the M2000 server acts as the FTP client. The NE acting as FTP server connects the M2000 to other NEs and improves network access efficiency for the purpose of file transfer.
Context
l
The system sets the NEs that can serve as an FTP server for file transfer M2000 server and an NE. If an NE chooses another NE or the M2000 server as its transfer server, the file transfer process can be stopped. If the NE chooses itself as the transfer server, the file transfer process cannot be stopped. The M2000 provides the function of setting FTP servers in batches to save the maintenance effort. You set multiple NEs as FTP servers concurrently. The typical setting is to use the RNC as the relay server for transferring NodeB data.
Procedure
Step 1 Choose Software > File Server Setting. The File Server Setting dialog box is displayed. Step 2 Select the type of the target NE from the navigation tree of the dialog box. All the NEs of this type on M2000 are listed in the right pane.
NOTE
click Refresh to refresh the NE information in the list at the right of the File Server Setting dialog box.
Step 3 Select the destination NE from the NE Name list. You can use Shift or Ctrl to select multiple NEs. Then right-click them and choose Set to set NEs in batches. Step 4 Click the File Server Name column. The File Server IP box displays the IP address of the file server that you have set.
NOTE
If you click Refresh, the Confirm dialog box is displayed. Click No to cancel the previous setting for the file server.
Step 5 To activate the setting, click Apply. ----End
3.3 Creating Physical NEs

A physical NE is the communication equipment that has the physical connection with the M2000 and can be managed by the M2000. Only when the related physical NE is created on the M2000, the M2000 can manage the communication equipment. 3.3.1 NE Type The mobile network devices managed by the M2000 are categorized according to the home network, service function, and management functions supported by NEs. 3.3.2 Basic NE information This part describes the basic NE information. You are required to acquire the basic NE information before creating NEs, modifying NEs, and querying NE reports. 3.3.3 Creating a Physical NE This describes the procedure for creating a physical NE on the topology view. After the NE is created, the M2000 obtains the configuration data of the NE by synchronizing the NE. 3.3.4 Creating Multiple Physical NEs To reduce the maintenance workload, the M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology at the same time.
3.3.1 NE Type
The mobile network devices managed by the M2000 are categorized according to the home network, service function, and management functions supported by NEs.
Categorize According to Home Networks

According to the different home networks of NEs, the mobile network devices managed by the M2000 can be categorized into the devices of the four network types: GSM, WCDMA, CDMA, and WiMAX. IP devices do not belong to the three networks. Table 3-1 lists the network devices of each type of network.
3-12
Issue 06 (2008-12-16)
Table 3-1 Network devices categorized according to their home networks NE Type GSM Network Device
l l l l l l l
PCU/PCU33 BSC/GT800BSC iMSC tMSC HLR36 rMSCSvr MSC/MSC33 MGW SGSN RNC HLR SIWF CG MSCServer IMSOMU CSCF HSS ATS RM CCF DOPRA SBC MRF AG AHR ICS(IP Clock Server)
WCDMA
l l l l l l l l l l l l l l l l l l l
Issue 06 (2008-12-16)
3-13
NE Type CDMA
Network Device
l l l l l l l l l l l
AAA CHLR CBSC CBTS(3606&3612) RAC RAU CMSC MSCe POC CHLR9820 PDSN ASN-GW BWA MRFP MRFC MEDIAX IPCTRX CSE MediaX3600
WiMAX
l l l l l l l l
IP device
ROUTER. The specific models are as follows:

l l l l l l l l
AR28 Eudemon1000 Eudemon200 Eudemon500 NE08 NE16 NE40 NE80 S2000 S2000B S3000 S3500 S5500 S8500
SWITCH. The specific models are as follows:

l l l l l l
3-14
Issue 06 (2008-12-16)
NE Type Other networking devices
Network Device
l
IPsec Gateway
Categorize According to Service Functions

Based on the service function supported by the NEs, the mobile network devices that can be managed by the M2000 can be classified into CN, AN, and IP devices. Table 3-2 lists the NEs in each class. Table 3-2 Categorize According to Service Functions NE Type Access Network Network Device
l l l l l l l l l l
BSC PCU RNC CBSC CBTS(3606&3612) RAC RAU ASN-GW BWA ICS(IP Clock Server)
Issue 06 (2008-12-16)
3-15
NE Type Core Network
Network Device
l l l l l l l l l l l l l l l l l l l l l l l l l l l
CG GGSN80 HA HLR MGW MSC Server rMSCSvr SGSN tMSCSvr AAA CHLR CMSC MSCe POC CHLR9820 PDSN IMSOMU CSCF HSS ATS RM CCF DOPRA SBC MRF AG AHR
3-16
Issue 06 (2008-12-16)
NE Type IP device
Network Device ROUTER. The specific models are as follows:

l l l l l l l l
AR28 Eudemon1000 Eudemon200 Eudemon500 NE08 NE16 NE40 NE80 S2000 S2000B S3000 S3500 S5500 S8500 IPsec Gateway

l l l l l l
Other networking devices
Categorize According to the Functions Supported by NEs

According to the different functions supported by the NEs, the mobile network devices managed by the M2000 can be categorized into NEs in classes A, B, and C. Table 3-3 lists the NEs in each class.
Issue 06 (2008-12-16)
3-17
Table 3-3 NEs categorized according to the supported functions NE Type A NE Network Device
l l l l l l l l l l l l l l l l l l l l l l l l l
BSC HLR9820 NodeB SGSN GGSN CG MSC Server MGW RNC CHLR9820 MSCe IMSOMU CSCF HSS ATS RM CCF DOPRA SBC MRF ASN-GW BWA AG AHR ICS(IP Clock Server) BTS MSC PCU HLR36 GT800 BSC iMSC rMSC tMSC
B NE
l l l l l l l l
3-18
Issue 06 (2008-12-16)
NE Type C NE
Network Device
l l l l l l l l l l l l l l
CHLR9820 GLMS RAC TSC RAU POC CT800 GLMS CBTS CBSC SG7000 MSCe PDSN CMGW HA
IP device
ROUTER. The specific models are as follows:

l l l l l l l l
AR28 Eudemon1000 Eudemon200 Eudemon500 NE08 NE16 NE40 NE80 S2000 S2000B S3000 S3500 S5500 S8500 IPsec Gateway

l l l l l l
Other networking devices
3.3.2 Basic NE information

This part describes the basic NE information. You are required to acquire the basic NE information before creating NEs, modifying NEs, and querying NE reports.
Issue 06 (2008-12-16)
3-19
Table 3-4 describes the NE basic information. Except User name, Password, Confirm Password, and Coordinate, other NE information is displayed in the NE table. Table 3-4 Basic NE information Message NE Name NE Type Version Description Name of the NE, which must be entered when you create an NE. Type of an NE, which cannot be changed after the NE is created. NE version number obtained from the NE. Manual input or modification of class A NE version is not allowed. Manual input or modification of classes B and C NE versions are required. IP address of an NE, which serves for the NE to communicate with the M2000. You must enter an IP address when creating an NE. Location of an NE. Name of an NE vendor. Description of the NE. District of the NE. For the users outside China, import the files of their own district information. Indicates the maintenance region where NEs are located . The candidate maintenance regions are determined by the server side. Indicates the subareas where the NEs are located. The candidate NEs subareas are determined by the server side. Name of an NE user. This parameter is displayed only when the NE is an NE in classes B or C. For details of NEs in classes B and C, refer to 3.3.1 NE Type. Password Password for logging in to the NE. This parameter is displayed only when the NE is an NE in classes B or C. For details of NEs in classes B and C, refer to 3.3.1 NE Type. Confirm Password The confirm password for logging in to the NE. This parameter is displayed only when the NE is an NE in classes B or C. For details of NEs in classes B and C, refer to 3.3.1 NE Type. Coordinate The pointer changes to + after you click Axis. In the physical topological view, click where the NE is created to display the X and Y coordinates values of the NE.
IP address
Physical Location Vendor Description District Maintenance region
Subarea User
3-20
Issue 06 (2008-12-16)
3.3.3 Creating a Physical NE

This describes the procedure for creating a physical NE on the topology view. After the NE is created, the M2000 obtains the configuration data of the NE by synchronizing the NE.
Prerequisite
l l l
You have logged in to the M2000 client. The mediation applications of accessed NEs are successfully installed. You have obtained the basic information about NEs, such as NE name, IP address of NEs, NE version, and district of NEs. The physical NE communicates properly with the M2000 server.
Context
l
After the RNC is created, it serves as a subnet or an NE. You can use 3.3.4.1 Automatically Searching for NodeBs to view all the NodeBs belonging to the RNC on the physical topology view and the navigation tree. After the IMSOMU is created, it can be both a subnetwork and an NE. By referring to 3.3.4.2 Automatically Searching the Sub-NEs of the IMSOMU, you can display all the sub-NEs of the IMSOMU on the topology view and the navigation tree. After the ASN-GW is created, it serves as a subnet or an NE. You can create a BWA under the ASN-GW subnet. After the MGW is created, you can use 3.6.2.1 Moving an NE into a Group NE to add it to the MSC server. This addition does not change the user authority of the MGW. The M2000 individually manages the BAM servers of three CN NEs, that is, MSC Server, MSCe, and SG7000 servers. These NEs are called third-party servers. The third-party server can only be created manually under the MSC Server, MSCe, and SG7000. The sub-NEs of the IMSOMU are the CSCF, HSS, ATS, RM, CCF, and DOPRA. These sub-NEs cannot be created manually. After creating the IMSOMU, you can deliver the automatic search command. The searched NEs are displayed on the physical topology view.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 In the physical topology navigation tree or on the physical view, right-click the subnet of the NE to be created and choose New > Create Topo Object on the shortcut menu. Step 3 From the navigation tree in the Create topo objects dialog box, select a specific NE node under Single Create.
NOTE
l l
The RNC, MSC Server, ASN-GW, and BSC are also group objects. They can manage NodeBs, MGWs, BWAs, and BTSs in addition to subnets. The physical BTS cannot be manually created. If a BSC is controlled by a BTS, the BTS is automatically created when you synchronize the BSC.
Step 4 In the right part of the window, configure NE-related information.

NOTE
For RNCs, you need set the NE partitions where the NodeBs are located. The NE partitions that can be selected are determined by the M2000 server.
Issue 06 (2008-12-16)
3-21
For information about NEs that need configuring, refer to 3.9.9 Parameters for Creating an NE. Step 5 Click OK. The displayed Create NE Progress dialog box shows the NE creation progress. You can click Detail in the dialog box to view the detailed information about creating a physical NE. After an NE is created, the NE is displayed in the physical topology navigation tree and in the topology view. Step 6 Click Close. Then, the Create NE Progress dialog box is closed. ----End
Result
After the physical NE is created successfully, the system automatically synchronizes the configuration information on the NE.
Related References
3.9.9 Parameters for Creating an NE
3.3.4 Creating Multiple Physical NEs

To reduce the maintenance workload, the M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology at the same time. 3.3.4.1 Automatically Searching for NodeBs This describes how to automatically search for NodeBs. The automatic searching function helps you know information about the NodeBs under an RNC such as the total number of NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NEs whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated. 3.3.4.2 Automatically Searching the Sub-NEs of the IMSOMU This task is performed to automatically detect the sub-NEs of the specified IMSOMU on the physical topology view. 3.3.4.3 Exporting an NE Information Template (in .ini Format) When you create NEs in batches, you can apply the format of the .ini file to record information on multiple NEs. The system provides the template for exporting NE information to ensure that the file is in .ini format. You can configure attributes of these NEs according to the items in the template. 3.3.4.4 Exporting an NE Information Template (in .csv Format) When you create NEs in batches, you can apply the format of the .csv file to record information on multiple NEs. The system provides the NE information exporting template to ensure that the file is in .csv format. You can configure attributes of these NEs according to the items in the template. 3.3.4.5 Editing a Script for Creating NEs in Batches (in .ini Format) Before creating physical NEs in batches, you must configure the information about the physical NEs as an .ini file. You can configure the NE information in .ini files according to the value range applied when you create a single physical NEs. If the value is beyond the range, physical NEs cannot be created in batches. 3.3.4.6 Editing a Script for Creating NEs in Batches (in .csv Format)
To create physical NEs in batches, you need to add the information about all these physical NEs to a .csv file. You can configure the NE information in .csv files according to the value range applied when you create a single physical NE. If the value is beyond the range, physical NEs cannot be created in batches. 3.3.4.7 Creating Physical NEs in Batches To reduce the maintenance workload, M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology view at the same time. 3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script The M2000 provides a standard template for the script files for creating NEs in batches. You need only export the template, and then enter the information of the NEs to be created. Two formats of templates are available: INI and CSV. This part describes the template in .ini format to facilitate the creation of NEs in batches through script files. 3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script The M2000 provides a standard template for the script files for creating NEs in batches. You need only export the template, and then enter the information of the NEs to be created. Two formats of templates are available: INI and CSV. This part describes the template in .csv format to facilitate the creation of NEs in batches through script files.
Automatically Searching for NodeBs

This describes how to automatically search for NodeBs. The automatic searching function helps you know information about the NodeBs under an RNC such as the total number of NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NEs whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated.
Prerequisite
l l
You have logged in to the M2000 client. The RNCs are well connected to the M2000 server.
Context
NodeBs can be reparented. Therefore, the NodeBs that need to be deleted are not deleted automatically when they are found automatically. Instead, they are displayed as Disconnected. In this case, you need to determine whether the disconnected NodeBs need to be deleted. For information about how to delete NodeBs, refer to 3.6.9 Deleting a Virtual NE.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 From the topology navigation tree or the topology view, right-click an RNC and choose Search NodeB on the shortcut menu. If the RNCs are disconnected from the M2000 server, Search NodeB becomes dimmed.
NOTE
For the RNCs in the multi-server load-sharing system, you also need to select the NE partition of the NodeB.
----End
Issue 06 (2008-12-16)
3-23
Result
In the Main Topology window, the system automatically synchronizes the information about the NodeBs managed by a specific RNC, such as the total number of NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NEs whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated.
Automatically Searching the Sub-NEs of the IMSOMU

This task is performed to automatically detect the sub-NEs of the specified IMSOMU on the physical topology view.
Prerequisite
If an IMSOMU is connected, this task enables you to automatically detect the sub-NEs of the IMSOMU on the physical topology view or from the navigation tree. These sub-NEs are the CSCF, HSS, ATS, RM, CCF, and DOPRA.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 From the navigation tree or on the physical topology view, select an IMSOMU. Right-click the pane and choose Search IMSOMU NE from the shortcut menu. ----End
Result
The searched IMSOMU sub-NEs are displayed on the physical topology view.
Exporting an NE Information Template (in .ini Format)

When you create NEs in batches, you can apply the format of the .ini file to record information on multiple NEs. The system provides the template for exporting NE information to ensure that the file is in .ini format. You can configure attributes of these NEs according to the items in the template.
Context
l
To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrlbycondition.csv is located in \client\style\defaultstyle\conf\omccommon in the installation path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is installed in \client\style\defaultstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation. Two formats of templates are available for creating NEs in batches: .ini and .csv. To create NEs in batches successfully, you must configure the .ini or .csv file correctly. Group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS260 0,MEDIAX,IPCTRX) can only be created in batches through the INI template.
3-24
Procedure
Step 1 Choose Configuration > Export NE Attribute Template > INI File Format. Step 2 In the Export NE Info Template(.ini) dialog box, select an NE type. Step 3 click to select a path for saving the template.
Step 4 Enter a name for saving the .ini file, and then click Save to return to Export NE Information template(INI file format) dialog box. Step 5 Click Confirm to export the .ini file template for creating NEs in batches. The Message dialog box is displayed, showing that the template is exported successfully. Step 6 Click OK to close the Message dialog box. ----End
Related Tasks
3.3.4.5 Editing a Script for Creating NEs in Batches (in .ini Format)
Related References
3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script 3.9.8 Parameters for Exporting an NE Information Template (in .ini Format)
Exporting an NE Information Template (in .csv Format)

When you create NEs in batches, you can apply the format of the .csv file to record information on multiple NEs. The system provides the NE information exporting template to ensure that the file is in .csv format. You can configure attributes of these NEs according to the items in the template.
Context
l
To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrlbycondition.csv is located in \client\style\productstyle\conf\omccommon in the installation path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is installed in \client\style\productstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation. Two formats of templates are available for creating NEs in batches: .ini and .csv. To create NEs in batches successfully, you must configure the .ini or .csv file correctly. Group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS260 0,MEDIAX,IPCTRX) can only be created in batches through the INI template. The NodeB supports two IP addresses. Therefore, the NodeB template is different from those of other NEs.
Procedure
Step 1 Choose Configuration > Export NE Attribute Template > CSV File Format.
Step 2 In the Export NE Info template(CSV file format) dialog box, select Template Type. Step 3 Click to set the path for saving files.
Step 4 Enter a name for saving the .csv file, and then click Save to return to Export NE Information Template(.csv) dialog box. Step 5 Click Confirm to export the .csv file template for creating NEs in batch. The Message dialog box is displayed, showing that the template is exported successfully. Step 6 Click OK to close the Message dialog box. ----End
Related Tasks
3.3.4.6 Editing a Script for Creating NEs in Batches (in .csv Format)
Related References
3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script
Editing a Script for Creating NEs in Batches (in .ini Format)

Before creating physical NEs in batches, you must configure the information about the physical NEs as an .ini file. You can configure the NE information in .ini files according to the value range applied when you create a single physical NEs. If the value is beyond the range, physical NEs cannot be created in batches.
Prerequisite
l l
You have obtained the NE type, NE IP address, and district area. You have exported the NE information template through 3.3.4.3 Exporting an NE Information Template (in .ini Format).
Context
l l
This operation does not support virtual NEs. To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrlbycondition.csv is located in \client\style\productstyle\conf\omccommon in the installation path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is installed in \client\style\productstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation. Group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS260 0,MEDIAX,IPCTRX) can only be created in batches through the INI template. For information about the value range of each NE parameter when you create a physical NE, refer to 3.9.9 Parameters for Creating an NE and 3.9.4 Parameters for Creating an IP Device.
3-26
Procedure
Step 1 Use Notepad delivered with the operating system to open the NE information template. Step 2 Enter the NE name, NE version, and district. ----End
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format)
Related References
3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script
Editing a Script for Creating NEs in Batches (in .csv Format)

To create physical NEs in batches, you need to add the information about all these physical NEs to a .csv file. You can configure the NE information in .csv files according to the value range applied when you create a single physical NE. If the value is beyond the range, physical NEs cannot be created in batches.
Prerequisite
l l
You have obtained the NE type, NE IP address, and district area. You have exported the NE information template through 3.3.4.4 Exporting an NE Information Template (in .csv Format).
Context
l l
This operation does not support virtual NEs. To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrlbycondition.csv is located in \client\style\productstyle\conf\omccommon in the installation path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is installed in \client\style\productstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation. The script file in .csv format can be used to create physical NEs in batches. It cannot be used to create group NEs, such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS260 0,MEDIAX,IPCTRX). For information about the value range of each NE parameter when you singly create physical NEs, refer to 3.9.9 Parameters for Creating an NE. The NodeB supports two IP addresses. Therefore, the template for creating NodeBs is different from those of other NEs. You need to use the NodeB template when creating NodeBs. As the separator of columns, commas are not allowed in each cell of the .csv file.
TIP
It is recommended that you use the Microsoft Excel to edit .csv files.
Issue 06 (2008-12-16)
3-27
Procedure
Step 1 Open the exported NE information template.
NOTE
Use a NodeB template when creating NodeBs.
Step 2 Enter the NE information such as the NE type, NE name, NE version, and home administration region. ----End
Related Tasks
3.3.4.4 Exporting an NE Information Template (in .csv Format)
Related References
3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script
Creating Physical NEs in Batches

To reduce the maintenance workload, M2000 provides the function of creating physical NEs in batches. You can create multiple physical NEs on the topology view at the same time.
Prerequisite
l l l
You have logged in to the M2000 client. The mediation software of the NE to be created is successfully installed. The script in .csv or .ini format used for creating NEs in batches is available.
Context
l l
The M2000 does not support the batch creation of virtual NEs. To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrlbycondition.csv is located in \client\style\productstyle\conf\omccommon in the installation path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is installed in \client\style\productstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation. Two formats of templates are available for creating NEs in batches: .ini and .csv. The script files in .csv format do not support the bulk creation of group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS260 0,MEDIAX,IPCTRX).
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 In the physical topology navigation tree or on the physical view, right-click the subnet of the NE to be created and choose New > Create Topo Object on the shortcut menu.
CAUTION
If the type of the new NE is NodeB, a virtual or physical RNC is selected as the subnet where the new NE is located. If the type of the new NE is BWA, a virtual or physical ASN-GW is selected as the subnet where the new NE is located. Step 3 Select the NE node under the Bulk Create node from the navigation tree of the Create topo objects dialog box. Step 4 In the right part, click and select the NE configuration script file.
Step 5 Click Verify to check the configuration of the script file. For errors, modify them according to 3.3.4.6 Editing a Script for Creating NEs in Batches (in .csv Format) or 3.3.4.5 Editing a Script for Creating NEs in Batches (in .ini Format). Step 6 Click OK to start creating NEs. The Create NE Progress prompt box is displayed, showing the progress of NE creation and results. Step 7 Click Close. Then, the Create NE Progress dialog box is closed. ----End
Result
After creating a physical NE successfully, the system performs NE synchronization automatically to obtain configuration data from this NE. If synchronized successfully, the NE is displayed in the specified position on the topology view and is in the Being Synchronized . If the network connection between the M2000 and this physical state, as shown by the icon NE is abnormal, the NE can also be displayed in the designated position on the topology view, but the NE is in the disconnection state, as shown by the icon .
Related References
3.9.10 Parameters for Batch Creating Physical NEs
Description of the .ini Template Format Used by the Batch NE Creation Script
The M2000 provides a standard template for the script files for creating NEs in batches. You need only export the template, and then enter the information of the NEs to be created. Two formats of templates are available: INI and CSV. This part describes the template in .ini format to facilitate the creation of NEs in batches through script files.
Format Description
The templates in INI format apply to create all types of NEs in batches except virtual NEs. Use the notepad to edit the templates in the INI format. Different from the CSV templates, the INI templates apply to different parameter groups. You can configure the NE information in .ini files according to the value range applied when you create a single physical NEs. If the value is beyond the range, physical NEs cannot be created in batches. For details about the value range of parameters for each NE, refer to 3.9.9 Parameters for Creating an NE and 3.9.4 Parameters
for Creating an IP Device. For details about the basic configuration information of each NE, refer to 3.3.2 Basic NE information.
CAUTION
If several NEs of the same category are created, you need to provide the associated parameter groups. The ID of NE types should be duplicate. For instance, when several RNCs are created, the [RNC] at the beginning of the configuration information should be duplicate to identify the NE type for each RNC in the .ini template. Do not configure the information on several RNCs under one [RNC].
Instances of Creating NE Configuration Information in Batches

[RNC] Name = RNC_1 Vendor = Huawei Physical Location = A Zone District = Beijing City IP Address = 10.161.170.22 Description = NE of A Zone subarea = osssvr-1 nodebsubarea =osssvr-1 pos X = 153 pos Y = 141 longitude = latitude = [RNC] Name = RNC_2 Vendor = Huawei Physical Location = B Zone District = Beijing City IP Address = 10.71.36.40 Description = NE of B Zone subarea =osssvr-2 nodebsubarea =osssvr-2 pos X = 113 pos Y = 105 longitude = latitude = [MGW] Name = MGW_A Vendor = Huawei Physical Location = A Zone District = Beijing City IP Address = 10.161.118.23 Description = NE of A Zone subarea =osssvr-2 pos X = 407 pos Y = 220 longitude = latitude =
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format) 3.3.4.5 Editing a Script for Creating NEs in Batches (in .ini Format)
Description of the .csv Template Format Used by the Batch NE Creation Script
The M2000 provides a standard template for the script files for creating NEs in batches. You need only export the template, and then enter the information of the NEs to be created. Two formats of templates are available: INI and CSV. This part describes the template in .csv format to facilitate the creation of NEs in batches through script files.
Format Description
The script file in .csv format can be used to create physical NEs in batches. It cannot be used to create group NEs, such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS (IMSOMU,CSCF,HSS,ATS,RM,CCF,DOPRA,SBC,MRF,MRFC,MRFP,CSE,OMS2600,ME DIAX,IPCTRX). To determine whether an NE supports bulk creation, you can compare the NETYPE in the file entrancectrl-bycondition.csv and the file bulkCreateNe.txt.
l
The file entrancectrl-bycondition.csv is located in \client\style\productstyle\conf \omccommon in the installation path of the client. This file contains NENAME and NETYPE.
3-30

l
The file bulkCreateNe.txt is installed in \client\style\productstyle\conf\omccm in the installation path of the client. This file contains the NETYPE of the NEs that support batch creation.
The system can create NEs in batches only when you conform to the value range of parameters for each NE. For details about the value range of parameters for each NE, refer to 3.9.9 Parameters for Creating an NE. For details about the basic configuration information of each NE, refer to 3.3.2 Basic NE information.
Example of the CSV Template

Use the Microsoft Excel to edit the templates in the CSV format. All the NEs except NodeB use the common templates, as shown in Figure 3-1. Figure 3-1 An example of CSV templates
NOTE
NodeB templates have two IP addresses: ATM network IP address and IP bearer network IP address. Other parameters are the same as the common template.
Related Tasks
3.3.4.4 Exporting an NE Information Template (in .csv Format) 3.3.4.6 Editing a Script for Creating NEs in Batches (in .csv Format)
3.4 Managing SNMP Parameter Templates

The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. The template types consist of SNMPV1, SNMPV2c, and SNMPV3. By managing SNMP parameter templates, you can browse the detailed information on the existing templates on the current server. In addition, you can add, modify, and delete the templates. 3.4.1 Creating SNMP Parameter Templates The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. You can create the required templates. 3.4.2 Modifying SNMP Parameter Templates The SNMP parameter templates are used to save the parameters typed. Thus, the parameters are easy to import when the SNMPs are created. You can modify the SNMP parameter templates when the created SNMP parameter templates are outdated or incorrect. 3.4.3 Deleting SNMP Parameter Templates The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. For the created SNMP parameter templates, you can delete unneeded templates.
3.4.1 Creating SNMP Parameter Templates

The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. You can create the required templates.
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template Management dialog box. Step 2 Select the template type to be created from the Protocol Version navigation tree and click Add. Step 3 Configure parameters in the displayed Template Parameter. For details of configuring parameters, refer to 3.9.15 Parameters for SNMP Parameter Templates. Step 4 Click OK or Apply. The added parameter template is displayed in the right window of the Template Parameter Management dialog box. ----End
Related References
3.9.15 Parameters for SNMP Parameter Templates
3.4.2 Modifying SNMP Parameter Templates

The SNMP parameter templates are used to save the parameters typed. Thus, the parameters are easy to import when the SNMPs are created. You can modify the SNMP parameter templates when the created SNMP parameter templates are outdated or incorrect.
Prerequisite
The SNMP parameter templates are already created.
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template Management dialog box. Step 2 Select the template types to be modified from the Protocol Version navigation tree and select the parameter templates to be modified on the right of the window. Step 3 Double-click the parameter templates or click Modify to open the Template Parameter dialog box. Step 4 Modify parameters in Template Parameter. For details about modifying parameters, refer to 3.9.15 Parameters for SNMP Parameter Templates. Step 5 Click OK. The latest parameter template is displayed in the right window of the Template Parameter Management. ----End
Related References
3.4.3 Deleting SNMP Parameter Templates

The SNMP parameter templates are used to save the parameters typed by users. Thus, the parameters are easy to import when the SNMPs are created. For the created SNMP parameter templates, you can delete unneeded templates.
Prerequisite
The SNMP parameter templates are already created.
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template Management dialog box. Step 2 Select the template type to be deleted from the Protocol Version navigation tree and select the parameter templates to be deleted on the right of the window. Step 3 Click Delete. Step 4 Click OK in the displayed Confirmation prompt box. ----End
3.5 Monitoring NEs

You can monitor the alarm status and connection status on the NEs. By monitoring NEs, you can detect and solve the abnormalities in real time. 3.5.1 Monitoring NE Status You can monitor the NE status to view the name, type, and status of the NEs that are managed by the M2000 so that you can know the running status of the NEs and solve the abnormalities in time. 3.5.2 Allowing Reconnection to an NE When an NE is disconnected with the M2000 server, you can specify whether the M2000 server automatically connects the NE. There are two connection states: Enable Connection and Disable Connection. 3.5.3 Manually Reconnecting an NE You can reconnect an NE manually when the NE is disconnected from the M2000 server.
3.5.1 Monitoring NE Status

You can monitor the NE status to view the name, type, and status of the NEs that are managed by the M2000 so that you can know the running status of the NEs and solve the abnormalities in time.
Issue 06 (2008-12-16)
3-33
Context
l
You can right-click an NE in the system monitor and browse window, and then choose Topology Location to view the topology view of the NE. You can right-click in the system monitor and browse window, and then choose Refresh to refresh the current window.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 In the System Monitor Browser window, click the NE Monitor tab to view the NEs that are managed by the M2000. Step 3 Optional: Click Filter. Select NE Type and Alarm Status. Click OK. The information on the NEs that matches the filter conditions are displayed in the table. Step 4 Optional: Click Save As. The monitoring data is saved to the local disk. ----End
Related References
3.9.11 Parameters for Monitoring the Status of an NE
3.5.2 Allowing Reconnection to an NE

When an NE is disconnected with the M2000 server, you can specify whether the M2000 server automatically connects the NE. There are two connection states: Enable Connection and Disable Connection.
Context
There are two NE reconnection states:
l
Enable Connection: When the communication between an NE and the M2000 server is disconnected, the M2000 attempts to reconnect the NE. By default, the connection state of a newly added NE is Enable Connection. Disable Connection: When the communication between an NE and the M2000 is disconnected, the M2000 does not attempt to reconnect the NE.
The set connection state is maintained even after you restarts the system.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 In the navigation tree or on the topology view, select an NE and set a reconnection state.
3-34
Issue 06 (2008-12-16)
Menu Item
Result
Enable connect NE The connection is enabled between the M2000 server and an NE. When disconnected , the M2000 server automatically reconnect the NE. At the same time, the disabling connection icon disappears. If the connection succeeds, the disconnection icon disappears. Disable connect NE An NE is disconnected from the M2000 server. The reconnection function between the M2000 server and the NE is disabled. At the same time, the NE is labeled with the disconnection icon and the disabling connection icon .
NOTE
The menu displayed after you right-click an NE varies with the change of the reconnection status. If you right-click an NE in the Enable Connection state, the displayed menu shows the Disable connect NE option. If you right-click an NE in the Disable Connection state, the displayed menu shows the Enable connect NE option.
Step 3 Click Yes in the displayed Confirm dialog box. A dialog box is displayed, showing the operation results and progress. Step 4 Click Close. ----End
3.5.3 Manually Reconnecting an NE

You can reconnect an NE manually when the NE is disconnected from the M2000 server.
Context
NodeBs may be in the disconnected state because they are deleted or reparented. Therefore, you need to determine the reason why the NodeBs are disconnected before performing the related operation such as deleting, reconnecting, and waiting for the NodeBs to be reparented.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the physical topology view, select an NE with the Disconnected icon . Step 3 Right-click the NE, and select Reconnect. The disconnected icon is removed when the NE is reconnected to the server. ----End
3.6 Adjusting the Network Topology

After creating a subnet, NE, or link, you can adjust the network topology as required. Adjusting the network topology involves modifying and deleting a subnet, NE, or link. 3.6.1 Searching for Topology Objects
You can search for and identify the specific NEs, links, link sets, and subnets in the topology. 3.6.2 Adjusting the Position of an NE This task is performed to adjust the position of an NE. For example, you can move an NE to a group object or other subnets and adjust its position in the subnet. 3.6.3 Moving a NodeB To re-parent NodeBs, the RNC sends a command about deleting NodeBs and then a command about creating NodeBs to the M2000. Upon receiving the command of NodeB deletion, the M2000 closes the connection with the physical NodeBs rather than directly deleting the NodeBs. In this way, you can determine the binding relation between the NodeBs before and after the reparenting, thus avoiding the loss of alarm and performance data. 3.6.4 Viewing/Modifying the Basic Attributes of a Subnet After creating a physical subnet, you can view and modify the attributes of the physical subnet, such as the name, object, and background. 3.6.5 Viewing/Modifying NE Properties After creating a physical or virtual NE, you can view or modify the basic attributes as required. 3.6.6 Viewing/Modifying a Physical Link On the physical topology view, you can view the basic information on physical links. In addition, you can set conditions to view the details about a physical link. This function does not apply to virtual links. After a physical link is set up, you can modify only the name of the link. 3.6.7 Viewing/Modifying a Virtual Link After a virtual link is set up, you can view and modify the name and other information on the virtual link. 3.6.8 Deleting Subnets You can delete the physical subnets or logical subnets that are no longer needed. 3.6.9 Deleting a Virtual NE When the topology is adjusted and a virtual NE is removed from the topology, you need to delete the virtual NE from the topology view. 3.6.10 Deleting Physical NEs in Batches You can delete multiple physical NEs from the physical topology view at a time. 3.6.11 Deleting a Physical Link After a physical link is set up, you can remove it manually. At the same time, the network structure is refreshed. 3.6.12 Deleting a Virtual Link A virtual link indicates that two NEs (including physical NE and virtual NE) communicate with each other. You can delete the link. 3.6.13 Refreshing a Topology View You can perform this operation to refresh the status of an object such as an NE and a link in the topology view.
3.6.1 Searching for Topology Objects

You can search for and identify the specific NEs, links, link sets, and subnets in the topology.
3-36
Issue 06 (2008-12-16)
Context
l
In the Search Content text box, you can enter the key words containing the wildcard (*) to perform a fuzzy search. In the Search Results list, click a record. The object related to the record is located in the topology view.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 On the toolbar, click .
Step 3 In Search Type, select the type of the searched objects. Step 4 In Search Content, enter the keywords for search. Step 5 In Search Scope, set the range for search.
NOTE
l l l
Search sublayer: If you select this item, you can search the path and the subpath specified in Search Scope. Case sensitive: If this check box is selected, it is case sensitive in the search operation. Match whole word only: If this check box is selected, only the results that exactly meet the conditions are to be displayed.
Step 6 Click Search. The Search Results list displays all the found records. ----End
3.6.2 Adjusting the Position of an NE

This task is performed to adjust the position of an NE. For example, you can move an NE to a group object or other subnets and adjust its position in the subnet. 3.6.2.1 Moving an NE into a Group NE On the topology view, you can move one or multiple NEs to a group NE which is logically associated with the NE or NEs. For example, you can move a NodeB into the RNC that manages the NodeB. Group NEs refer to NEs which can also act as subnets, such as RNC, ASN-GW and MSC Server. 3.6.2.2 Moving an NE into Another Subnet On the topology view, you can move one or more NEs into another subnet to facilitate the management. 3.6.2.3 Moving an NE Within a Subnet On the topology view, you can move an NE to other locations within its subnet, thus locating the NE correctly and facilitating NE management. This operation changes only the physical location on the topology view and has no effect on the actual situation.
Moving an NE into a Group NE

On the topology view, you can move one or multiple NEs to a group NE which is logically associated with the NE or NEs. For example, you can move a NodeB into the RNC that manages
the NodeB. Group NEs refer to NEs which can also act as subnets, such as RNC, ASN-GW and MSC Server.
Prerequisite
l l
You have logged in to the M2000 client. The NE to be moved is located in the same subnet as the group NE.
Context
This operation supports the MGW, NodeB, BWA, ASN-GW, RNC and MSC Server. Moving an NE into a group NE changes only the dependency relationship on the topology view, and has no effect on the actual situation.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the topology view, select the group NE that the NE is to be moved into. Step 3 Right-click the group NE and select Property from the shortcut menu. The NE Property dialog box is displayed. Step 4 Click the Object Selection tab as shown in Figure 3-2. Figure 3-2 NE Property
3-38
Issue 06 (2008-12-16)
Step 5 Select the NE to be moved into the group NE in the Available Objects list. Click Then the NE is added to the Selected Objects list.
TIP
You can select multiple NEs at the same time.
Step 6 Click OK. The Message dialog box is displayed, showing the operation results. Step 7 Click OK to close the Message dialog box. ----End
Moving an NE into Another Subnet

On the topology view, you can move one or more NEs into another subnet to facilitate the management.
Prerequisite
Context
All network devices support this operation. Moving an NE into another subnet changes only the dependency relationship on the topology view and has no effect on the actual situation.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Determine the relationship between the NE and the subnet. Relationship Between NE and Subnet Then...
The NE and the subnet are located in different level of network hierarchy Go to Step 3. on the navigation tree. The NE and the subnet are located in the same level of network hierarchy Go to Step 4. on the navigation tree. Step 3 Move the NE to the network level of the subnet.
l
If the NE is located in the first network level under the Physical Root node while the subnet to be moved into is located in the first network level, perform the following steps: 1. 2. 3. In the topology view, select the subnet of the subnet to be moved into. Right-click the subnet and select Modify from the shortcut menu. the Modify Physical Subnet dialog box is displayed. Click the Object Selection tab.
Issue 06 (2008-12-16)
4. 5.
l
Select the NE to be moved into the group NE in the Available Objects list. Click . Then the NE is added to the Selected Objects list. If the subnet is located in the third or higher network level, repeat operation a to operation d till the NE is moved to the same network level with the subnet.
If the NE is located in the second network level under the Physical Root node while the subnet to be moved into is located in the first network level, perform the following steps: 1. 2. 3. 4. 5. In the topology view, select the subnet of the NE to be moved out. Right-click the subnet and select Modify from the shortcut menu. the Modify Physical Subnet dialog box is displayed. Click the Object Selection tab. Select the NE to be moved out of the NE group in the Selected Objects list. Click . Then the NE is added to the Available Objects list. If the subnet is located in the third or higher network level, repeat operation a to operation d till the NE is moved to the same network level with the subnet.
If both the NE and the subnet are located in the second or higher level of the Physical Root node, perform the previous steps till the NE is located in the same network level with the subnet to be moved into.
Step 4 Move the NE to the corresponding subnet. 1. 2. 3. 4. In the topology view, select the subnet to be moved into. Right-click the subnet and select Modify from the shortcut menu. the Modify Physical Subnet dialog box is displayed. Click the Object Selection tab. Select the NE to be moved into the group NE in the Available Objects list. Click . Then the NE is added to the Selected Objects list. You can select multiple NEs. Step 5 Click OK. ----End
Moving an NE Within a Subnet

On the topology view, you can move an NE to other locations within its subnet, thus locating the NE correctly and facilitating NE management. This operation changes only the physical location on the topology view and has no effect on the actual situation.
Prerequisite
l l
You have logged in to the M2000 client. The NE is created.
Context
All network devices support this operation.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Select an NE on the topology view. Step 3 Drag the NE to the target location. Step 4 Click the icon ----End on the toolbar to save the new location.
3.6.3 Moving a NodeB

To re-parent NodeBs, the RNC sends a command about deleting NodeBs and then a command about creating NodeBs to the M2000. Upon receiving the command of NodeB deletion, the M2000 closes the connection with the physical NodeBs rather than directly deleting the NodeBs. In this way, you can determine the binding relation between the NodeBs before and after the reparenting, thus avoiding the loss of alarm and performance data. 3.6.3.1 Moving a NodeB in the Same RNC This describes how to move a NodeB in the same RNC. The binding relation can be automatically identified or manually specified. 3.6.3.2 Moving a NodeB to Another RNC This describes how to manually specify the binding relation between the NodeBs before and after re-parenting so that the NodeB can be moved to another RNC.
Related References
3.9.16 Parameters for Moving a NodeB 3.9.2 Interface Description: Moving a NodeB
Moving a NodeB in the Same RNC

This describes how to move a NodeB in the same RNC. The binding relation can be automatically identified or manually specified.
Prerequisite
l l
You have logged in to the M2000 client. You have the right to operate the related NEs.
Context
Figure 3-3 shows the process for moving a NodeB in the same RNC.
Issue 06 (2008-12-16)
3-41
Figure 3-3 Process for moving a NodeB in the same RNC
The process for moving a NodeB to another RNC shown in Figure 3-3 is as follows: 1. 2. 3. 4. The RNC sends a command about deleting the NodeB to the M2000. The M2000 closes the connection with the NodeB (hereinafter referred to as A). After the NodeB is re-parented, the RNC sends a command about creating a NodeB to the M2000. The M2000 searches for the NE with the same NodeBID. If an NE with the same NodeBID is found, you can infer that the created NodeB is the reparented one. Then the system updates the information about the existing NodeB with the created NodeB. If no such a NodeB is found, the M2000 automatically searches for NodeBs and creates a new NodeB (hereinafter referred to as A'). Then you can specify the binding relation through the NodeB re-parenting tool. At the same time, the system deletes A'. 5. After the re-parenting, the state of A changes to connected.
Procedure
Step 1 Double-click omcNodebmove.bat under M2000 client installation directory\client\bin to view the Login dialog box.
By default, the M2000 client is installed in the path C:\iManagerM2000Client. Step 2 Enter the user name, password, and IP address of the M2000 server. Then, click OK. Step 3 Select the related NodeBs in the NodeB Re-parent navigation trees. Then, click Add Bind(s).
l l
After being bound, the NodeB turns blue in color and the node name is added binded. A binding record is added to the result table. You can select one or more binding records and click Remove Bind(s) to remove the binding relation. You can repeat Step 3 to specify multiple binding relations for bulk re-parenting.
Step 4 Click Confirm Move. The system automatically updates the information about A with the information about A', including NodeID and the relation with the RNC, and then deletes A'. After that, A is automatically connected to the system.
NOTE
A' is the logical representation of A. The IP address, belonged RNC, and sometimes the configuration information of A' are changed after the re-parenting. You need to synchronize the information about A with the information about A'. Then after the synchronization, the system deletes the logical NE A'.
Step 5 Click Close. Step 6 In the displayed Confirm dialog box, click OK. ----End
Result
After the NodeB is moved in the same RNC, the progress bar in the NodeB Re-parent dialog box displays 100%. You can view the result in Operation Result.
Related References
Moving a NodeB to Another RNC

This describes how to manually specify the binding relation between the NodeBs before and after re-parenting so that the NodeB can be moved to another RNC.
Prerequisite
l l
You have logged in to the M2000 client. You have the right to operate the related NEs.
Context
Figure 3-4 shows the process for moving a NodeB to another RNC.
Issue 06 (2008-12-16)
3-43
Figure 3-4 Process for moving a NodeB to another RNC
The process for moving a NodeB to another RNC shown in Figure 3-4 is as follows: 1. 2. 3. 4. The RNC sends a command about deleting the NodeB to the M2000. The M2000 closes the connection with the NodeB (hereinafter referred to as A). After the NodeB is re-parented, the RNC to which the NodeB is moved sends a command about creating a NodeB to the M2000. The M2000 automatically searches for the NodeB and then creates a new NodeB (hereinafter referred to as A'). After A is re-parented, it is displayed as A' and its state changes to disconnected. A' is automatically found by the M2000 and regarded as a new NE.
CAUTION
The IP addresses of NEs of the same type must be unique on the M2000. Therefore, the IP address of a NodeB must be changed after it is moved to another RNC. The conflict caused by identical IP addresses may result in the failure to create a new NodeB. The System Output Window may display error. In this case, you need to manually change the IP address of the NodeB and then enable the M2000 to automatically search for the NodeB. 5. The user specifies the binding relation between A and A' by using the NodeB re-parenting tool. The system automatically updates the information about A, that is, NodeBID and the relation with the RNC, with the information about A', and then deletes A'.

NOTE
A' is the logical representation of A. The IP address, belonged RNC, and sometimes the configuration information of A' are changed after the re-parenting. You need to synchronize the information about A with the information about A'. Then after the synchronization, the system deletes the logical NE A'.
6.
After the re-parenting, the state of A changes to connected.
Procedure
Step 1 Double-click omcNodebmove.bat under M2000 client installation directory\client\bin to view the Login dialog box. By default, the M2000 client is installed in the path C:\iManagerM2000Client. Step 2 Enter the user name, password, and IP address of the M2000 server. Then, click OK. Step 3 Select the related NodeBs in the NodeB Re-parent navigation trees. Then, click Add Bind(s).
l l
After being bound, the NodeB turns blue in color and the node name is added binded. A binding record is added to the result table. You can select one or more binding records and click Remove Bind(s) to remove the binding relation. You can repeat Step 3 to specify multiple binding relations for bulk re-parenting.
Step 4 Click Confirm Move. The system automatically updates the information about A with the information about A', including NodeID and the relation with the RNC, and then deletes A'. After that, A is automatically connected to the system. Step 5 Click Close. Step 6 In the displayed Confirm dialog box, click OK. ----End
Result
After the NodeB is moved to another RNC, the progress bar in the NodeB Re-parent dialog box displays 100%. You can view the result in Operation Result.
Related References
3.6.4 Viewing/Modifying the Basic Attributes of a Subnet

After creating a physical subnet, you can view and modify the attributes of the physical subnet, such as the name, object, and background.
Issue 06 (2008-12-16)
3-45
Context
CAUTION
l l
Do not modify the coordinate of the ROOT node in the physical topology. The size of the background picture must be less than 1 MB.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 In the physical topology navigation tree or on the physical topology view, select the subnet to be modified. Right-click the subnet and choose Modify to view the Modify Physical Subnet dialog box. Step 3 Select the corresponding tab and then view and modify the basic attributes of the subnet. Tab Basic Attribute Operation View and set the name, coordinate, background, and remarks.
Object Selection Deselected objects are listed in the left part of the tab and selected objects are listed in the right part of the tab. To set objects included in a subnet, click Step 4 Click OK. ----End or .
Related References
3.9.12 Parameters for Viewing/Modifying the Basic Attributes of a Subnet
3.6.5 Viewing/Modifying NE Properties

After creating a physical or virtual NE, you can view or modify the basic attributes as required.
Context
l
If you have modified the IP address of the NE, the system automatically reconnects the NE through the new IP address. To save the NE location information, drag the NE to the specified location and then click on the topology toolbar.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Right-click an NE on the navigation tree or topology view, and choose Property from the shortcut menu, then you can view or modify the information.
CAUTION
The information on a physical BTS cannot be modified. Step 3 Click OK. ----End
3.6.6 Viewing/Modifying a Physical Link

On the physical topology view, you can view the basic information on physical links. In addition, you can set conditions to view the details about a physical link. This function does not apply to virtual links. After a physical link is set up, you can modify only the name of the link.
Procedure
Step 1 Select a physical link. 1. Open the Link Browser window by using either of the following ways: Method Method 1 Operation a. Choose Topology > Main Topology. The Main Topology window is displayed. b. On the physical topology view, double-click a physical link or a physical link set. In the displayed information box, right-click a link and choose Query Link Information on the shortcut menu. c. Click Filter. Method 2 2. a. Choose Configuration > Link Browser.
Select one or more NEs in the End A NE and End Z NE fields respectively.
l
If you do not select NEs for either end, this function displays the information about all the available physical links. If you select NEs for only one end, this function displays the information about all the available physical links with the ends as the specified NEs.
3.
Click Query. The links that satisfy the conditions are shown in the list.
Step 2 Modify the physical link. 1. 2. 3. 4. Select a link from the displayed link list. Right-click the link, and then choose the Modify menu item or click Modify to view the Change Link Name dialog box. Type the name of the link, and then click OK. A prompt box is displayed, showing the operation results. Click OK to close the prompt box.
----End
Related References
3.6.7 Viewing/Modifying a Virtual Link

After a virtual link is set up, you can view and modify the name and other information on the virtual link.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the physical topology view, double-click a virtual link or a virtual link set. You can also right-click and choose Display on the shortcut menu. Step 3 Check the information about the virtual link in the displayed information box. Step 4 Right-click a virtual link and choose Modify on the shortcut-menu. The Modify Virtual Link dialog box is displayed.
NOTE
For a signal virtual link, you can right-click it directly on the topology view and choose Modify. The Modify Virtual Link dialog box is displayed.
Step 5 In the Modify Virtual Link table, modify the virtual link attributes.
CAUTION
l l
You can modify the name and remarks of a virtual link. After a virtual link is created, three attributes, that is type, End A NEs, and End Z NEs cannot be modified.
Related References
3.6.8 Deleting Subnets

You can delete the physical subnets or logical subnets that are no longer needed.
Context
l l
The root nodes in the navigation tree cannot be deleted. When a subnet is deleted, the elements in the subnet are not deleted. They are moved to the upper subnet. The IMSOMU is an exception. When deleting an IMSOMU, you must perform association deletion to delete all the subnets belonging to the IMSOMU. When a subnet is deleted, the elements in the subnet are not deleted. They are moved to the upper subnet.
3-48
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the navigation tree or topology view, right-click a subnet and choose Delete. Step 3 In the Confirm dialog box, click Yes. ----End
3.6.9 Deleting a Virtual NE

When the topology is adjusted and a virtual NE is removed from the topology, you need to delete the virtual NE from the topology view.
Context
You can delete the virtual NE in the physical view, or electronic view. You cannot delete the virtual NE in the custom view. This section describes how to delete the virtual NE in the physical view. In the custom topology, you cannot delete a virtual NE.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the navigation tree or the view, right-click a virtual NE and choose Delete. Step 3 Click Yes. ----End
3.6.10 Deleting Physical NEs in Batches

You can delete multiple physical NEs from the physical topology view at a time.
Context
The CSCF, HSS, ATS, RM, CCF and DOPRA do not support batch deletion.
NOTE
Do not perform the batch deletion when a subnet is selected.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Press Ctrl to select multiple physical NEs from the physical topology navigation tree or the physical topology view. Step 3 Right-click the selected NEs, and then choose Delete NEs in batch. Step 4 In the displayed Confirm dialog box, click Yes. The Delete NE prompt box is displayed, showing the deleting progress and operation results. Step 5 Click Close to close the Delete NE prompt box. ----End
Result
The system deletes the information related to the NEs in the database.
3.6.11 Deleting a Physical Link

After a physical link is set up, you can remove it manually. At the same time, the network structure is refreshed.
Context
CAUTION
Do not remove the physical links that the are automatically set up by the system. The physical links are automatically refreshed according to the connection status between NEs.
Procedure
Step 1 Choose Configuration > Link Browser to view the Link Browser window. Step 2 Set conditions for querying the links you want to remove. Step 3 In the displayed link list, select one or more links. Step 4 Right-click the Delete option or click Delete in the dialog box. Step 5 In the displayed dialog box, click Yes. The Operation Progress prompt box is displayed, showing the deletion progress and operation results. Step 6 Click Close to close the Operation Progress prompt box. ----End
Related References
3.6.12 Deleting a Virtual Link

A virtual link indicates that two NEs (including physical NE and virtual NE) communicate with each other. You can delete the link.
Context
l l
When a virtual link is deleted, the corresponding physical link is not deleted. You can delete the virtual link in the physical view, electronic view, or machine view. You cannot delete the virtual link in the custom view. This section describes how to delete the virtual link in the physical view.
3-50
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the physical view, right-click a virtual link and choose Delete. Step 3 In the Confirm dialog box, click Yes. ----End
Related References
3.6.13 Refreshing a Topology View

You can perform this operation to refresh the status of an object such as an NE and a link in the topology view.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 On the toolbar of the topology view, click .
The status of the objects in the topology view and navigation tree is refreshed. ----End
3.7 Adjusting the Topology View

You can adjust the topology view as required. For example, you can expand or hide the topology navigation tree, switch the current subnet, display the topology view in full screen, zoom in or out of the view, and customize the topology tips. 3.7.1 Showing/Hiding the Navigation Tree of a Topology View The topology view shows all the service windows. This task is performed to show or hide the navigation tree of a topology view. 3.7.2 Setting Alarm Display on the Topology View After you set alarm display on the topology view, when an alarm is raised on an NE, the color of the NE on the topology view is changed to the color indicating the highest alarm severity in the corresponding status, thus you can know the alarm information in time. 3.7.3 Switching the Current Subnet On the topology view, you can switch the current subnet view to the desired one. 3.7.4 Display the filtered topology view When there are excessive objects, the topology view may appear crowded. You can set the filter conditions to filter the objects in the view by type. 3.7.5 Zooming In/Out on a Topology View You can adjust the topology view as desired, including zooming in, zooming out, magnifying, resetting, and fitting the view to the contents. 3.7.6 View the topology aerial view
When the topology view is larger than 1024 x 768 pixels, only a part of the view is displayed in the topology window. You can use the aerial view to browse the entire view and locate the area to be displayed. 3.7.7 Laying Out Topology Objects Automatically If there are multiple objects in the topology view in disorder, you can lay out the objects automatically. 3.7.8 Expand or Collapse Child Objects You can expand or collapse the topology objects in the navigation tree so that you can view the objects conveniently. 3.7.9 Sorting Topology Objects You can sort the topology objects in the navigation tree in the ascending or descending order. 3.7.10 Displaying the Alarm Pop-Up Pane You can set the display of the alarm pop-up pane. When an alarm is raised, the number of the alarms of the highest severity is displayed in the pop-up pane on the upper right of the NE. 3.7.11 Customizing Topology Tips The topology tip refers to the information displayed when the cursor stays on an object for a few seconds on the topology view. You can select counters for setting the tips. The counters can be sorted in two ways: by NE, and by link. 3.7.12 Setting a Subnet Displayed When the Topology View is Started You can specify the default subnet view that is displayed when the topology view is started. If view is manually set, the default startup subnet view is the root subnet view. 3.7.13 Enabling the E-Map The electronic map supports the map files in .mif or .mid format. This view can directly display the actual locations of the NEs in all areas.
3.7.1 Showing/Hiding the Navigation Tree of a Topology View

The topology view shows all the service windows. This task is performed to show or hide the navigation tree of a topology view.
Context
or is located between the physical topology navigation tree and physical topology view.
If both the topology view and topology navigation tree are displayed, you can click to hide the topology navigation tree. Then the topology view extends to the area of the topology navigation tree.
If the topology navigation tree is not displayed, you can click to display the navigation tree.
3-52
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Hide or display the topology navigation tree.
Click to hide the topology navigation tree.
Click to display the topology navigation tree.
----End
3.7.2 Setting Alarm Display on the Topology View

After you set alarm display on the topology view, when an alarm is raised on an NE, the color of the NE on the topology view is changed to the color indicating the highest alarm severity in the corresponding status, thus you can know the alarm information in time.
Context
You can customize the display of the following alarm states:
l l l l l
Uncleared Fault Alarm Unacknowledged & Cleared Fault Alarm Unacknowledged & Uncleared Fault Alarm Unacknowledged Fault Alarm Acknowledged & Uncleared Fault Alarm
Uncleared fault alarms represent unacknowledged and uncleared fault alarms, and unacknowledged and uncleared fault alarms. Unacknowledged fault alarms represent unacknowledged and uncleared fault alarms, and unacknowledged and cleared fault alarms. To know the meaning of each alarm state, refer to 2.1.3 Alarm Status.
Procedure
Step 1 Choose System > Preferences. Step 2 In the Preferences dialog box, select the Topology Status Display node. Step 3 In Alarm status, select the status of the alarms that you want to display on the topology view. Click Up or Down to adjust the display priority. Step 4 Click OK. ----End
3.7.3 Switching the Current Subnet

On the topology view, you can switch the current subnet view to the desired one.
Context
You can switch the current subnet both on the navigation tree and the topology view. The procedures are the same.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the navigation tree or the topology view, click a desired subnet to switch a current subnet to the subnet. ----End
3.7.4 Display the filtered topology view

When there are excessive objects, the topology view may appear crowded. You can set the filter conditions to filter the objects in the view by type.
Context
l
When the M2000 is started, the default filter condition is null, that is, the topology objects in all types are displayed. When you filter the parent nodes in the navigation tree, indicates all selected. indicates partially selected, and
Procedure
Step 1 Choose Topology > Main Topology. Step 2 On the toolbar, click .
Step 3 In the displayed dialog box, click the Filter. Step 4 In the Filter tab, in the Topology Filter navigation tree, choose a node type. Only those topology objects in the chose types are displayed in the current topology view. ----End
Related References
3.9.13 Parameters for Setting Topology Filter Display
3.7.5 Zooming In/Out on a Topology View

You can adjust the topology view as desired, including zooming in, zooming out, magnifying, resetting, and fitting the view to the contents.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 Perform the following operations to zoom in and out topology objects:
l
On the topology toolbar, click
to zoom in on the topology view.

Issue 06 (2008-12-16)
3-54

l l
On the topology toolbar, click
to zoom out on the topology view.
On the topology toolbar, click . Click in the topology view and drag a rectangle. The objects in the rectangle are magnified. On the topology toolbar, click On the topology toolbar, click to reset the size of the topology view. to display all the objects in the topology window.
l l
When you click this button, the size of the topology objects may change, but the coordinates and shapes do not change. ----End
3.7.6 View the topology aerial view

When the topology view is larger than 1024 x 768 pixels, only a part of the view is displayed in the topology window. You can use the aerial view to browse the entire view and locate the area to be displayed.
Context
The resolution is determined by the screen size of the client, and is not always 1024 x 768 pixels.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 On the toolbar in the topology window, click . The Overview window is displayed. The rectangle area is visible in the current view. Step 3 In the Overview window, drag the rectangle area to modify the display area of the current view.
NOTE
When you switch to another topology view or window, the Overview window is closed.
----End
3.7.7 Laying Out Topology Objects Automatically

If there are multiple objects in the topology view in disorder, you can lay out the objects automatically.
Context
l
There are four layout modes: table, tree, star, and ring. You can select the mode according to the actual requirements. If you select part of the topology objects, only the selected objects are laid out. If you do not select any object, all the objects in the topology view are laid out. Layout of a link or a link set refers to the layout of the NEs at the both end of the link. When you lay out topology objects, the M2000 places the figure corresponding to each topology objects in the cell of a table. The row spacing and column spacing respectively correspond to the height and width of the cell. The display effects of the figures are the same.
l l l l
Issue 06 (2008-12-16)
3-55
Procedure
Step 1 Choose Topology > Main Topology. Step 2 In the topology view, select the topology objects for layout, and then click Step 3 In the Layout dialog box, select the layout mode. l l l l Select Table. In Column spacing and Row spacing, enter the length and height between nodes. Select Tree. Select Star. In Spacing, enter the spacing between nodes. Select Ring. In Spacing, enter the spacing between nodes. .
Step 4 Click OK. Step 5 In the Set Layout dialog box, click OK.
NOTE
Select Automatically save the coordinates of the node.
----End
3.7.8 Expand or Collapse Child Objects

You can expand or collapse the topology objects in the navigation tree so that you can view the objects conveniently.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 Perform the following operations to expand and collapse topology objects:
l l l
On the toolbar, click On the toolbar, click
to expand all the topology objects in the navigation tree. to collapse all the topology objects in the navigation tree. to expand the to collapse
In the navigation tree, select one or multiple subnets. On the toolbar, click selected subnets. In the navigation tree, select one or multiple subnets. On the toolbar, click the selected subnets.
----End
3.7.9 Sorting Topology Objects

You can sort the topology objects in the navigation tree in the ascending or descending order.
3-56
Issue 06 (2008-12-16)
Context
NOTE
Topology objects in the navigation tree are sorted according to the following rules:
l
No matter whether topology objects are sorted in ascending or descending order, the sequence of the types of topology objects is unchanged. It is local NMSs, subnets, NEs with subnodes, NEs without subnodes, links, and link sets. The local NMS is always displayed on the top. For each type, topology objects are sorted by name in alphabetical order. Object names are case insensitive.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 Perform the following operations to sort topology objects:
l
On the top of the navigation tree, click on the toolbar. The topology objects of the same typein the navigation tree are sorted in the ascending alphabetic order. on the toolbar. The topology objects of the same On the top of the navigation tree, click type in the navigation tree are sorted in the descending alphabetic order.
----End
3.7.10 Displaying the Alarm Pop-Up Pane

You can set the display of the alarm pop-up pane. When an alarm is raised, the number of the alarms of the highest severity is displayed in the pop-up pane on the upper right of the NE.
Procedure
Step 1 Choose Topology > Main Topology. Step 2 Right-click in the topology view and choose Show Alarm Balloon. When an alarm is raised, the number of the alarms of the highest severity is displayed in the pop-up pane on the upper right of the NE. ----End
3.7.11 Customizing Topology Tips

The topology tip refers to the information displayed when the cursor stays on an object for a few seconds on the topology view. You can select counters for setting the tips. The counters can be sorted in two ways: by NE, and by link.
Prerequisite
Procedure
Step 1 Choose System > Customize Topology Tips to view the Customize Topology Tips dialog box.
By default, the system displays the configurable and activated counters of the first NE in the navigation tree. Step 2 Under the ToolTip node of the navigation tree, select an object on which a topology tip is required. Then set the counter item in the right part of the dialog box. Step 3 Click OK or Apply.
l l
Click OK to save the settings and close the dialog box. Click Apply to save the settings without closing the dialog box. You can set other counters for tips.
----End
3.7.12 Setting a Subnet Displayed When the Topology View is Started

You can specify the default subnet view that is displayed when the topology view is started. If view is manually set, the default startup subnet view is the root subnet view.
Prerequisite
Context
CAUTION
The setting takes effect the client is restarted.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Right-click the subnet on the topology view and choose Set to My Topology on the displayed shortcut menu. A prompt box is displayed indicating that the operation is successful. Step 3 Click OK. ----End
3.7.13 Enabling the E-Map

The electronic map supports the map files in .mif or .mid format. This view can directly display the actual locations of the NEs in all areas.
Prerequisite
Context
l l
If you needs an electronic map, contact the technical support engineers. The electronic map can help you color the districts, thus showing or hiding the names of districts. Each district is marked with a unique color. You can double-click a province name to open the detailed map of the province.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the tool bar of the Main Topology window, select Electronic View from the Current View drop-down list. The electronic view is displayed. Step 3 You can right-click in the view and select Show District Name from the shortcut menu. The names of districts are displayed in the electronic map view. ----End
3.8 Printing a Topology View

Using the print function, you can print the topology view to paper.
Context
You can directly print the topology view by clicking Print in the Print Preview dialog box and setting print attributes.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 Click on the toolbar.
Step 3 Set the attributes, such as the printer, print range and copies, and then click Print to print. ----End
Related References
3.9.14 Parameters for Printing a Topology View
3.9 Reference for Topology Management Interfaces

This part describers the topology management interfaces and relevant parameters, which helps you perform the operation related to topology management. 3.9.1 Interface Description: Topology Management This part describes the Main Topology interface. You can know the function of each part of the interface and meanings of icons and shortcut menus on the topology view. 3.9.2 Interface Description: Moving a NodeB
This decries the NodeB Re-parent interface. You can move NodeBs through this interface. 3.9.3 Parameters for Setting a Physical Subnet This section describes the parameters of physical subnet. You can refer to these parameters when you create or modify a physical subnet. 3.9.4 Parameters for Creating an IP Device This part describes the parameters used for creating IP devices on the topology view. You can refer to this part when creating IP devices on the topology view. 3.9.5 Parameters for Physical Link This describes the parameters related with the physical links. You can refer to these parameters when you create, search for, or change a physical link. 3.9.6 Parameters for Setting a Virtual Link This section describes the parameters of virtual links. You can refer to these parameters when you create, modify, or view links. 3.9.7 Parameters for Setting the Topology View This section describes the parameters in the Create Custom View dialog box. You can refer to these parameters when you create or modify a custom view. 3.9.8 Parameters for Exporting an NE Information Template (in .ini Format) This part describes the parameters in the Export NE Attributs template (INI File Format) dialog box. You can refer to this part when exporting an NE information template. 3.9.9 Parameters for Creating an NE This part provides the parameter description about one physical NE or virtual NE. When you create a physical NE and a virtual NE, you can set parameters according to the information given below. 3.9.10 Parameters for Batch Creating Physical NEs This part describes the parameters in the Create Physical NEs in Batch dialog box. You can refer to this part when creating physical NEs in batches. 3.9.11 Parameters for Monitoring the Status of an NE This part describes the parameters related with NE status monitoring. You can refer to this part when setting the parameters related with NE status monitoring. 3.9.12 Parameters for Viewing/Modifying the Basic Attributes of a Subnet This part describes the parameters in the Modify Physical Subnet dialog box. You can refer to this part when modifying basic attributes of a physical subnet and selecting the background. 3.9.13 Parameters for Setting Topology Filter Display This section describes the parameters in the Filter tab. You can refer to these parameters when you set the topology filter display. 3.9.14 Parameters for Printing a Topology View This part describes the parameters shown in the Print dialog box. When printing the topology view, you can refer to this part to set parameters. 3.9.15 Parameters for SNMP Parameter Templates This part describes the parameters in the Template Parameter. When creating or modifying SNMP parameter templates, set the parameters by referring to the information described below. 3.9.16 Parameters for Moving a NodeB This describes the parameters displayed in the NodeB Re-parent dialog box. You can refer to these parameters when manually specifying the binding relations before and after the NodeB is re-parented.
3.9.1 Interface Description: Topology Management

This part describes the Main Topology interface. You can know the function of each part of the interface and meanings of icons and shortcut menus on the topology view. As shown in Figure 3-5, the Main Topology interface comprises three parts: physical topology navigator, topology bar, physical topology view. For details, see Table 3-5. Figure 3-5 Main Topology interface
Table 3-5 Description of the Physical Topology interface No. (1) Name Physical topology navigation Topology Tool Bar Description Displays the hierarchy of the objects on the topology view. You can locate the objects on the topology view through the navigation tree. The shortcut icon on the topology tool bar can be used to perform operations easily and quickly on the physical topology. For the description of the shortcut menu, refer to Shortcut Menu in the Topology View. Displays all the devices managed by the M2000 in a map.
(2)
(3)
Physical topology view
Topology Legend
On the topology view, the M2000 uses different icons to identify the objects such as subnet, NE, group NE, and link.
Table 3-6 lists the icons of topology objects. Table 3-6 Description of topology legends Icon Meaning Common subnet Root Custom view Logical view MSC Pool Logical View Core Network Access Network OMC
NOTE On the topology view, different icons are used to identify different NEs. To know the legend of each NE and its meaning, refer to the Legend tab page on the topology navigation tree.
BICCSCTPLINK BICCSCTPLINK set MTP3Link MTP3Link set Virtual link LinkSet
NE State
l
Connection State On the physical topology, the connection states of the NEs are indicated by the NE icon and the state icon. The state icon is located at the upper left of the NE icon. Multiple state icons can be combined to indicate that the NE is in multiple states at the same time. For details of NE connection states, refer to Table 3-7.
3-62
Issue 06 (2008-12-16)
Table 3-7 Description of NE connection states Icon Meaning Synchroni zing processing Connectio n down NE not match ForbidCon nect Unknown type FourStates Critical alarm on LinkSet Major alarm on LinkSet Minor alarm on LinkSet Warning alarm on LinkSet
l
Description The data of NE on the M2000 Server are synchronizing with that on the NE. The connection between the M2000 Server and the NE is interrupted. The NE is not configured. The M2000 server is forbidden to automatically reconnect the NE. Current system does not support the NE type. The NE state contains four or more states. Critical alarm on linkset.
Major alarm on linkset.
Minor alarm on linkset
Warning alarm on linkset
Alarm State If an physical NE raises an alarm, the color of the NE icon on the physical topology view changes to show the alarm status of the NE. If an NE raises multiple fault alarms at the same time, the color of the NE icon maps to the top alarm severity. In addition, an alarm balloon is generated beside the icon. The balloon displays the alarm severity identity and number of alarms. To know how to set the icon color of each alarm severity, refer to 2.3.2.6 Setting the Alarm Color. To set whether to display the alarm balloon on the topology view through the shortcut menu, refer to Shortcut Menu in the Topology View. Table 3-8 lists the samples of integrated alarm states.
Issue 06 (2008-12-16)
3-63
Table 3-8 Samples of alarm states Icon Meaning Indicates the OMC without any fault alarm Description None.
Indicates the OMC with 102 critical fault alarms
The meaning of 102C is as follows:

l l
C: indicates the alarm severity. indicates the number of fault alarms of this severity. C: indicates critical alarms M: indicates major alarms N: indicates minor alarms W: indicates warning
In an alarm balloon:
l l l l
Indicates that the OMC has major fault alarms
If an alarm balloon does not appear, the amount of fault alarms at the corresponding severity is not displayed.
In the physical topology view, the NEs are connected in a hierarchical way. When a fault alarm occurs on the sub-NE of an NE, the following icons are displayed to indicate the alarms. If there are several fault alarms occurring on a sub-NE at the same time, the NE icon indicating the severest alarm is displayed. To know how to set the icon color of each alarm severity, refer to 2.3.2.6 Setting the Alarm Color. Table 3-9lists the samples of alarm states. Table 3-9 Samples of alarm states Icon Meaning Contain critical alarm Contain major alarm Contain minor alarm Contain warning alarm Description A critical alarm occurs on the sub-NE of the NE. A major alarm occurs on the sub-NE of the NE. A minor alarm occurs on the sub-NE of the NE. A warning alarm occurs on the sub-NE of the NE.
3-64
Issue 06 (2008-12-16)

NOTE
When multiple alarms are reported to the server from the NEs, the alarm statistical result on the NE tip will be different from the real-time statistical result for a while.
Topology Tool Bar

The shortcut icons in the topology tool bar facilitate the operations on the topology view. Table 3-10 describes the function of each shortcut icon. Table 3-10 Description of the topology tool bar Icon Name Create Description You can click the drop-down button to create a physical subnet or topology object. To return to the subnet of the upper level. When you move the view, you click to select the objects in the view. Move Hand To move the entire view without changing the spacing between the topology objects. To create a virtual link in the topology view. To set the print attributes to print the content of topology view. To preview the print result of the topology view. You can also print by using this icon. To save current view as JPG picture. To browse the topology structure of the topology view. To find the topology subjects (supporting * wildcard, the length of the value: 0-64) in physical topology. Entering nothing indicates searching for all topology objects on the topology view.
Back to Parent Select
Create Link Print
Print Preview
Save Picture Overview
Find
Issue 06 (2008-12-16)
3-65
Icon
Name Refresh
Description To refresh the topology view, and obtain the latest data from the M2000 server. Show all the elements in the topology view in the topology window. When the button is clicked, the size of the topology elements may change, but their shapes and positions in the coordinates remain the same. Save the positions of the physical objects. When you view the physical topology next time, the objects are displayed in these positions. To filter the topology objects, display the legend, and display the NE properties. To display the alarm list at the bottom of the client. To lay out the objects in the preset layout mode in the topology view automatically. To zoom in on the topology view. To zoom out on the topology view
l
Save Positions
Filter & Legend
Display Alarm List layout
Zoom In Zoom Out
When you zoom in on the topology view, the system hides the topology status to guarantee the display effect. When you zoom out on the topology view to certain extent, the system hides the names of the topology objects to guarantee the display effect.
Magnifier
To magnify the topology objects in the specified rectangle area to achieve better display effect of the topology view.
3-66
Issue 06 (2008-12-16)
Icon
Name Reset Zoom Fit to Contents
Description To restore the topology view to the normal size. To display all the current subnets in the topology window. When the button is clicked, the size of the topology elements may change, but their shapes and positions in the coordinates remain the same.
Shortcut Menu in the Topology View

Table 3-11 describes the functions of the shortcut menu on the topology view. Table 3-11 Description of the shortcut menu Shortcut Menu Attribute Supported Topology Object
l l
function View and modify NE property.

l
physical NE Virtual NE
For information about a physical NE, refer to 3.6.5 Viewing/ Modifying NE Properties and 3.6.2.1 Moving an NE into a Group NE. For information about a virtual NE, refer to 3.6.5 Viewing/ Modifying NE Properties.
Delete
l l l l
physical NE Virtual NE Subnet Virtual link
Remove the current NE, subnet, or link from the topology view.
l
For information about a physical NE, refer to 3.6.9 Deleting a Virtual NE and 3.6.10 Deleting Physical NEs in Batches. For information about a subnet, refer to 3.6.8 Deleting Subnets.
Modify
l l
Subnet Virtual link
Modify the current subnet or link. For information about a subnet, refer to 3.6.4 Viewing/Modifying the Basic Attributes of a Subnet. Query the current fault alarm of the NE. For details, see 2.2.7.1 Querying Current Fault Alarms.
Current Fault Alarms
l l
physical NE physical link
Issue 06 (2008-12-16)
3-67
Shortcut Menu Event Alarms
Supported Topology Object

l l
function Query the event alarm of the NE. For details, see 2.2.7.3 Querying Event Alarms. Query the history fault alarm of the NE. For details, see 2.2.7.2 Querying History Fault Alarms. Query the masked fault alarms. For details, see 2.2.7.4 Querying the Masked Fault Alarms. Query the masked event alarms. For details, see 2.2.7.5 Querying the Masked Event Alarms. View the information such as server name, operating system, CPU occupation ratio. For details, see 2.8.5 Interface Description: Performance Monitor. Enable the MIT browser. Enable MML commands. View the dependence relation between the UMG and the MSC Server. For details, see 11 DualHoming and LN Domain Management. Enable or disable the M2000 server to automatically reconnect NEs. Reconnect a disconnected NE to the M2000 server. Synchronize the configuration data of NE. Start the panels service. The menu items are displayed only after the mediation software of the NE is installed on both the M2000 server and client.
l l l
physical NE physical link physical NE physical link physical NE physical link physical NE physical link physical NE physical link
Query History Fault Alarm Query Masked Fault Alarms Query Masked Event Alarms Performance Monitor
l l
l l
l l
l l
MIT browser MML command View DualHoming
physical NE physical NE physical NE
Disable Connect NE/Enable Connect NE Reconnect NE Synchronize CM data Panels Service Management
physical NE
physical NE physical NE physical NE
Device Panel Monitor Panel Trace Panel
3-68
Issue 06 (2008-12-16)
Shortcut Menu Maintenance Client Synchronize NE Operation & Security Logs Show State
Supported Topology Object physical NE
function Start the local maintenance terminal for the selected NE. For details, see 9.8 Starting the LMT of an NE. Synchronize NE Operation Logs and NE Security Logs. Browse the states of physical NEs. For details, refer to 3.5 Monitoring NEs. For details, see 6.3 Querying Performance Measurement Results. Create physical subnet under the current subnet. For details, see 3.2.3 Creating a Physical Subnet.
l
physical NE
physical NE
Query result
physical NE
Create Physical Subnet Create Topo Object
Subnet
Subnet
Create NE under the current subnet. For details, see3.3.3 Creating a Physical NE and 3.2.5 Creating a Virtual NE. Create a physical link under the current subnet. For details, see 3.2.7 Creating a Physical Link. Create a virtual link under the current subnet. For details, see 3.2.8 Creating a Virtual Link. Create physical NEs under the current subnet in batches. For details, see 3.3.4.7 Creating Physical NEs in Batches.
Set as Startup Subnet Query link Information
Subnet physical link
Set the subnet that is displayed when the client is started. View the link information. For details, see 3.6.6 Viewing/ Modifying a Physical Link.
3.9.2 Interface Description: Moving a NodeB

This decries the NodeB Re-parent interface. You can move NodeBs through this interface. The NodeB re-parenting tool is divided into five parts: left navigation pane, search box, NE attribute area, right navigation pane and re-parenting result table. For details, see Figure 3-6. Table 3-12 describes Figure 3-6.
Issue 06 (2008-12-16)
3-69
Figure 3-6 NodeB Re-Parent interface
Table 3-12 Description of the NodeB Re-Parent interface No. 1 2 Parameter Left navigation tree Search box Description Displays all the disconnected NodeBs after the M2000 receives the command about deleting NodeBs. The left and right search box are used to quickly locate the NodeBs before and after re-parenting respectively.
l
Full match of the name and IP address of NodeB is supported. The search condition is case sensitive.
NE attribute area
This area is divided into two parts, which display the attributes of the corresponding NEs in the left and right navigation tree. Displays the NEs that are newly created in the M2000 system. Displays the information about the bound NodeBs and the re-parenting result.
4 5
Right navigation tree Re-parenting result
Related Tasks
3.6.3 Moving a NodeB 3.6.3.1 Moving a NodeB in the Same RNC 3.6.3.2 Moving a NodeB to Another RNC
3.9.3 Parameters for Setting a Physical Subnet

This section describes the parameters of physical subnet. You can refer to these parameters when you create or modify a physical subnet.
Basic Attribute
Name Name Description Description: Name of physical subnet. Settings Value: Value range: 1-64 Unit: character It can not contain special characters, such as ` ~ ! @ # $ % ^ & * ( ) - = + [ { ] } \ | ; : " , < . > / ? and blank space. The name cannot be null. Coordinate Description: Coordinates of the physical subnet icon in the topology view. Setting method: Click , and then click in the topology view where you want to locate the object. The text box displays the coordinates of the new object.
NOTE If you place the cursor on the icon of an existing NE, subnet, or link, you cannot select the coordinates.
Background
Configuration Guidelines: To set the background of the physical subnet.
Setting method: Click . In the Select Map File dialog box, select an image file for the background of the physical subnet. Value: Value range: 0-127. Unit: character.
Memo
Description: Description of the physical subnet. It can be null.
Objects Selection
Name Available Objects Description Description: Objects that can be added to the subnet when you create or modify the physical subnet. Selected Objects Description: Objects that are already included in the physical subnet. Settings Setting method: In the Available Objects list, select an object. Then click to move the selected object to the Selected Objects list. Then the object is added to the physical subnet. In the Selected Objects list, select an NE or a subnet. Then to move the click object from the physical subnet to the Available Objects list.
Issue 06 (2008-12-16)
3-71
Related Tasks
3.2.3 Creating a Physical Subnet
3.9.4 Parameters for Creating an IP Device

This part describes the parameters used for creating IP devices on the topology view. You can refer to this part when creating IP devices on the topology view.
Parameter Description of SNMP

Parameter Name Value Range
l l
Description Name is unique and case sensitive. It is recommended to use a meaningful name. This parameter cannot be null. District indicates the district of the NE. For the users outside China, import the files of their own district information. District is unique and can not be null.
1-60 characters Numbers, English letters, and special characters excluding @#!%^&*.[]/'" and space are allowed.
District
Selected from the dropdown list
IP Address
Conform to the rules of IP address.
Indicates the IP address of the IP device. This parameter is unique and can not be null. Click the value behind Position, and the mouse changes to +. In the physical topological view, click where the NE is created to display the X and Y coordinates values of the NE. Indicates the subareas where the NEs are located. The candidate NE subareas are determined by the server side. Indicates the SNMP version. Indicates the parameter template of the SNMP to be loaded. Indicates the community name when the NMS sends the Get Community request. Only when the community name is the same as that recognized by the NE, the Get Community can be performed. The community name works as password. The supported SNMP versions are SNMPV1 and SNMPV2c.
Position
Integer
Subarea
Selected from the dropdown list Selected from the dropdown list Selected from the dropdown list String of characters Value range: 1-100 This parameter cannot be null.
Version Template Name Get Community
3-72
Issue 06 (2008-12-16)
Parameter Set Community
Value Range String of characters Value range: 1-100 This parameter cannot be null.
Description Indicates the community name when the NMS sends the Set Community request. Only when the community name is same as that recognized by the NE, the Set Community can be performed. The community name works as password. The supported SNMP versions are SNMPV1 and SNMPV2c.
Timeout
Value range: 1-5
Indicates the waiting period after the NMS sends operation requests to NEs. The supported SNMP versions are SNMPV1, SNMPV2c, and SNMPV3.
Retries
Value range: 0-5 This parameter cannot be null.
Indicates the maximum number of retries that the NMS can perform when the request times out. The NMS makes retries when the SNMP request sent by the NMS times out. The supported SNMP versions are SNMPV1, SNMPV2c, and SNMPV3.
Port
Value range: 1-65535 This parameter cannot be null.
Indicates the port number of NEs communicating based on SNMP protocol. The supported SNMP versions are SNMPV1, SNMPV2c, and SNMPV3.
Devise User Name
l l
Value range: 1-100 Numbers, English letters, and English underline _ are allowed.
Indicates the user name in the security model. The SNMPV3 provides the userbased security model. Each user has their own private keys and authorization keys. The supported SNMP version is SNMPV3.
Context Name
l l
Value range: 1-100 Numbers, English letters, and English underline _ are allowed.
Context Name is also called contextName. This parameter is an exclusive one that indicates the context information in the SNMP. You can skip this parameter. The supported SNMP version is SNMPV3.
Context ID
l l
Value range: 1-100. Numbers, English letters, and English underline _ are allowed.
Context ID can also be called contextEngineID. This parameter is used to label the SNMP entity exclusively. The supported SNMP version is SNMPV3.
Issue 06 (2008-12-16)
3-73
Parameter Authorization Protocol
Value Range Selected from drop-down list
Description Used to set authentication keys. Select NONE to conduct no authorization. The supported SNMP version is SNMPV3.
Authorization Protocol Password
1-100 characters
Authorization Protocol Password is used to set the password of the user authentication key. After you select specific authorization protocols, this option takes effect. The supported SNMP version is SNMPV3.
Confirm Password
1-100 characters
Confirm Password is used to confirm the configured password. The supported SNMP version is SNMPV3.
Encrypt Protocol
Select from drop-down list.
Used to set private keys for users. If encryption is not necessary, this parameter can be NONE. The supported SNMP version is SNMPV3.
Encrypt Protocol Password
1-100 characters
Encrypt Protocol Password is used to set the password for private keys of users. After you select specific data encryption protocol, this option takes effect. The supported SNMP version is SNMPV3.
Parameter description of routers and switches

l l
Description Name should be unique and case sensitive. This parameter cannot be null. It is recommended to use a meaningful name. Indicates the district of the NE. For users outside China, import the files of their own district information.
1-60 characters Numbers, English letters, and special characters excluding @ # ! % ^ & * . [ ] / ' " and space are allowed.
District
3-74
Issue 06 (2008-12-16)
Parameter IP Address
Value Range Conforms to the rules of IP address.
Description Indicates the IP address of the IP device. This parameter is unique and can not be null. Indicates the equipment type of the IP device. This parameter cannot be null.
Equipment type
Version
Selected from the dropdown list Integer
Indicates the version of the IP device. This parameter cannot be null. Click the value behind Position, and the mouse changes to +. In the physical topological view, click where the NE is created to display the X and Y coordinates values of the NE. Click the value after Coordinates, and the mouse changes to +. In the e-map, click where the NE is created to display the longitude and latitude values of the NE.
Position
Coordinates
None
Related Tasks
3.2.6 Creating IP Device

This describes the parameters related with the physical links. You can refer to these parameters when you create, search for, or change a physical link.
Issue 06 (2008-12-16)
3-75
Parameter Link Type Description Type of a physical link At present, the M2000 supports six types of physical links: MTP3, MTP3B, DATALINK, M3UA, H248, and BICCSCTP. DATALINK, MTP3 and MTP3B links can only be created manually. They support the following types of NEs:
l
If one end of a MTP3 or MTP3B link is a physical MGW, the other end of the link can be a physical MSC Server or MSCe, or a virtual RNC or MSC server. MTP3 and MTP3B links can be created between a physical and a physical MSCe. DATALINK links can only be created between a physical CG and a physical GGSN 80 or physical SGSN.
M3UA, H248, and BICCSCTP links are automatically created by the system. They support the following types of NEs:
l
One end of a H248 or M3UA link can only be a physical MGW, the other end of the link can be a physical MSC server or MSCe. BICCSCTP links can only be created between physical MSC Servers.
A NE A MO Z NE Z MO Name
NE at end A of a link. You cannot modify the NE after the link is set up. Configuration of end A NE of a physical link. NE at end Z of a link. You cannot modify the NE after the link is set up. Configuration of end Z NE of a physical link. Name of a physical link. The length of a name is less than 120 characters Numbers.
Type
Type of a physical link
Related Tasks
3.2.7 Creating a Physical Link 3.6.6 Viewing/Modifying a Physical Link 3.6.11 Deleting a Physical Link

This section describes the parameters of virtual links. You can refer to these parameters when you create, modify, or view links.
3-76
Issue 06 (2008-12-16)
Parameters
Name Name Description Configuration Guidelines: The name cannot be duplicate with the link names in the topology view, and cannot be null. Settings Value: Value range: 1-64 Unit: character It can not contain special characters, such as `~!@#$% ^&*()-=+[{]}\|;:",<.>/? and blank space. Value: Virtual link. Setting method: Choose from the drop-down list. Setting method: Choose from the drop-down list. Value: Value range: 0-127. Unit: character.
Type
Description: You cannot change it.
End A NE
Description: NE on one end of the virtual link.
End Z NE
Description: NE on the other end of the virtual link.
Memo
Description: Description of the virtual link.
Related Tasks
3.2.8 Creating a Virtual Link 3.6.7 Viewing/Modifying a Virtual Link 3.6.12 Deleting a Virtual Link
3.9.7 Parameters for Setting the Topology View

This section describes the parameters in the Create Custom View dialog box. You can refer to these parameters when you create or modify a custom view.
Parameters
Name Name Description Configuration Guidelines: The name cannot be the same as the name of other topology object, and it cannot be null. Settings Value: Value range: 1-64 Unit: character It can contain special characters, such as `~!@#$% ^&*()-=+[{]}\|;:",<.>/? and blank space.
Issue 06 (2008-12-16)
3-77
Name Background
Description Configuration Guidelines: Background of the custom view.
Settings Setting method: Click . In the Select Map File dialog box, set the background of the custom view. Value: Value range: 0-127. Unit: characters. Setting method: Click Select Object. In the topology view or navigation tree, right-click the object you want to add and choose Select, or right-click the object you want to delete and choose Cancel Selection. Click Finish. Setting method:
Memo
Description: Description of the custom view. It can be null.
Select Object
Description: To select the objects in the view.
Selected Nodes
Description:
NEs that are already selected Click Select Object. to the custom view. Selected Links Description: Links that are already selected to the custom view. Setting method: Click Select Object.
3.9.8 Parameters for Exporting an NE Information Template (in .ini Format)

This part describes the parameters in the Export NE Attributs template (INI File Format) dialog box. You can refer to this part when exporting an NE information template.
Parameters
Parameter All Ne Types Save file to Description NE types of the information export template, consisting of NEs in access network series and core network series. Path for saving .ini files. You can directly enter a path or click select a path in the displayed Save dialog box. and
Generate comment information
Select this option. You can enter information in the Comment Info pane. The entered information is recorded in the exported .ini file.
3-78
Issue 06 (2008-12-16)
Parameter Comment Info
Description You can enter information only when the option Generate comment information is selected.
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format)
3.9.9 Parameters for Creating an NE

This part provides the parameter description about one physical NE or virtual NE. When you create a physical NE and a virtual NE, you can set parameters according to the information given below.
l l
Description Name of the NE, which must be entered when you create an NE.
1-60 characters Numbers, English letters, and special characters : < > ! Special characters, such as @ # ? [ ] / | ' " and space, are not allowed,.
Vendor Physical Location District
1-30 characters 1-30 characters Select the value from the dropdown list. Select the value from the dropdown list.
Name of an NE vendor. Location of an NE. District of the NE. For the users outside China, import the files of their own district information. Indicates the maintenance region where NEs are located . The candidate maintenance regions are determined by the server side. IP address of an NE, which serves for the NE to communicate with the M2000. You must enter an IP address when creating an NE. Description of the NE. Indicates the subareas where the NEs are located. The candidate NEs subareas are determined by the server side. Indicates the subareas where the added NodeBs are located.
3-79
Maintenance region
IP address
Conform to the rules of IP address.
Description Subarea
1-63 characters Select the value from the dropdown list.
NodebSubare a
Issue 06 (2008-12-16)
Select the value from the dropdown list.
Parameter Coordinate
Value Range Integer
Description The pointer changes to + after you click Axis. In the physical topological view, click where the NE is created to display the X and Y coordinates values of the NE.
Related Tasks
3.3.3 Creating a Physical NE
3.9.10 Parameters for Batch Creating Physical NEs

This part describes the parameters in the Create Physical NEs in Batch dialog box. You can refer to this part when creating physical NEs in batches.
Parameters
Parameter Script file Stop creating in case of errors Description The script file saves the NE configuration information. The system creates NEs one by one according to the sequence of NE information in the CSV or INI file. If you select this option, the system stops creating the following NEs when it fails to create one. If not, the system displays a prompt when failed to create one NE and continues to create the following NEs. The script verify information such as verification progress and result is generated during the verification of the NE information in the script file.
Script verify information
Related Tasks
3.3.4.7 Creating Physical NEs in Batches
3.9.11 Parameters for Monitoring the Status of an NE

This part describes the parameters related with NE status monitoring. You can refer to this part when setting the parameters related with NE status monitoring.
Parameter NE Name NE Type Alarm State Description Name of a managed NE Type of an NE, which is defined by the system Severity of an NE alarm, as described in NE State.
3-80
Issue 06 (2008-12-16)
Parameter Connection Status
Description State of the connections between the M2000 and NEs, as described in NE State.
Related Tasks
3.5.1 Monitoring NE Status
3.9.12 Parameters for Viewing/Modifying the Basic Attributes of a Subnet

This part describes the parameters in the Modify Physical Subnet dialog box. You can refer to this part when modifying basic attributes of a physical subnet and selecting the background.
Parameters
Parameter Name Value range
l l l
Description Name of a physical subnet.
Unique, cannot be null. 1-64 characters Numbers, English letters, and English underlines _ are allowed.
Coordinate
Integer
The pointer changes to + after you click . Then you can view the coordinate values by clicking the position where you want to place the object in the physical topology.
Background
Files in .gif or .jpg formats
Background map of the subnet. You can click , and then set the background map of the subnet in the displayed Select Map File dialog box.
Memo
0-127 characters, string type.
Description of the subnet. Can be null.
Related Tasks
3.6.4 Viewing/Modifying the Basic Attributes of a Subnet
3.9.13 Parameters for Setting Topology Filter Display

This section describes the parameters in the Filter tab. You can refer to these parameters when you set the topology filter display.
Issue 06 (2008-12-16)
3-81
Parameters
Name Background Description Description: To filter the background. Set whether to display the backgrounds of the current view. Subnet Description: To filter the subnet. Set whether to display all the subnets in the current view. NE Description: To filter the NE. Set whether to display all the NEs in the current view. Link Description: To filter the link. Set whether to display all the links in the current view. Name of Link Description: To filter the name of link. Set whether to display all the names of the link in the current view. Icon of Link Description: To filter the icon of link. Set whether to display all the icons of the link in the current view.
Related Tasks
3.7.4 Display the filtered topology view
3.9.14 Parameters for Printing a Topology View

This part describes the parameters shown in the Print dialog box. When printing the topology view, you can refer to this part to set parameters.
Parameters
Tab General Parameter Print Service Description In this box, you can set the printer properties and select to print a document to file. Name, Status, Type and Info respectively refer to the name, status, type and the information of the selected printer. If it permits, you can click Properties to set the printer properties. Print To File shows that you can print a document to a file.
3-82
Issue 06 (2008-12-16)
Tab
Parameter Print Range
Description Range of pages to be printed. Value range:

l l
All: to print all pages. Pages: to print the specified pages.
Copies
Copies to be printed. Value range:

l
Number of copies: to print the specified copies. Collate: to print copies one by one. It is valid if you print more than one copy.
Page Setup
Media
Property of papers for print. Value range:

l l
Size: size of the papers for print. Source: source of the papers for print.
Orientation
Orientation in which pages are to be printed. Value range:

l l l
Portrait: print perpendicularly Landscape: print horizontally Reverse Portrait: print perpendicularly in reverse order Reverse Landscape: print horizontally in reverse order
Margins
Margins of pages to be printed. Value range:

l l l l
left(in): left margin of a page. right(in): right margin of a page. top(in): top margin of a page. bottom(in): bottom margin of a page.
Appearance
Color Appearance
Color of pages to be printed. Value range:

l l
Monochrome: to print in black and white. Color: to print in multiple colors other than black and white.
Issue 06 (2008-12-16)
3-83
Tab
Parameter Quality
Description Quality of pages to be printed. Value range:

l l l
Draft: to print with low quality. Normal: to print with generic quality. High: to print with high quality.
Sides
Set whether to print on one side or on both sides. Value range:

l
One Side: to print on one side of a paper and the shorter side turns during printing. The printed pages are like a notepad. Tumble: to print on both sides of each paper and the shorter side upturns during printing. The printed pages are like a notepad. Duplex: to print on both sides of each paper and the longer side upturns during printing. The printed pages are like a book.
Job Attributes
Property of a print job.

l
Banner Page: page that contains titles of the job. Priority: priority of the print job. Job Name: name of the print job. User Name: name of the user that starts the print job.
l l l
Related Tasks
3.8 Printing a Topology View

This part describes the parameters in the Template Parameter. When creating or modifying SNMP parameter templates, set the parameters by referring to the information described below.
3-84
Issue 06 (2008-12-16)
Parameter Value Range Description Supported Parameter Templates
l l l
Template Name
About 1 to 100 characters Numbers, English letters, and English underline _ are allowed. This parameter is exclusive and cannot be null. The characters are case sensitive.
Sets names for SNMP parameter templates.
SNMPV1 SNMPV2c SNMPV3
Get Community
String of characters. Value range: 1 to 100. Default value: public.
Indicates the community name when the NMS sends the Get Community request. Only when the community name is the same as that recognized by the NE, the Get Community can be performed. The community name functions as the password. Indicates the community name when the NMS sends the Set Community request. Only when the community name is same as that recognized by the NE, the Set Community can be performed. The community name functions as the password. Indicates the waiting period after the NMS sends operation requests to NEs.
l l
SNMPV1 SNMPV2c
Set Community
String of characters. Value range: 1 to 100. Default value: private.
l l
SNMPV1 SNMPV2c
Timeout
Value range: 1 to 5. This parameter cannot be null.
l l l
Issue 06 (2008-12-16)
3-85
Parameter
Value Range
Description
Supported Parameter Templates

l l l
Retries
Value range: 0 to 5. This parameter cannot be null.
Indicates the maximum number of retries that the NMS can perform when the request times out. The NMS makes retries when the SNMP request sent by the NMS times out. Indicates the port number of NEs communicating based on SNMP protocol. Indicates the user name in the security model. The SNMPV3 provides the user-based security model. Each user has their own private keys and authrization keys. Also called contextName. This parameter is an exclusive one that indicates the context information in the SNMP. You can skip this parameter. Also called contextEngineID. This parameter is used to label the SNMP entity exclusively.
Port
Value range: 0 to 99999. The value 161 is recommended.

l
l l l
Device User Name
Value range: 1 to 100 Numbers, English letters, and English underline _ are allowed. Value range: 1 to 100 Numbers, English letters, and English underline _ are allowed.
SNMPV3
Context Name
SNMPV3
Context ID
Value range: 1 to 100. Numbers, English letters, and English underline _ are allowed.
SNMPV3
Encrypt Protocol
Select from dropdown list.
Used to set private keys for users. If encryption is not necessary, this parameter can be NONE. Used to set authentication keys. Select NONE to conduct no authorization.
SNMPV3
Authorization Protocol
Select from dropdown list
SNMPV3
3-86
Issue 06 (2008-12-16)
Related Tasks
3.4.2 Modifying SNMP Parameter Templates 3.4.1 Creating SNMP Parameter Templates
3.9.16 Parameters for Moving a NodeB

This describes the parameters displayed in the NodeB Re-parent dialog box. You can refer to these parameters when manually specifying the binding relations before and after the NodeB is re-parented.
Parameter Name Description Attribute of the NE selected in the navigation tree, such as NE name, vendor, location, district, IP address, description, partition, and NodeB partition. For details, refer to 3.3.2 Basic NE information. Attribute value of the NE selected in the navigation tree. Name of the NodeB before being re-parented. RNC of the NodeB before being re-pareneted. Name of the NodeB after being re-parented. RNC of the NodeB after being re-pareneted. Result of the re-parenting operation. Description of the re-parenting operation, including succeeded and failed.
Value NodeB Before Moved RNC Before Moved NodeB After Moved RNC After Moved Operation Result Operation Description
Related Tasks
3.6.3 Moving a NodeB 3.6.3.1 Moving a NodeB in the Same RNC 3.6.3.2 Moving a NodeB to Another RNC
Issue 06 (2008-12-16)
3-87
4 Security Management
4
About This Chapter
Security Management
This describes how to guarantee the security of the M2000. The M2000 security management manages the user and the user's rights. Through the security management, the security of the M2000 is guaranteed. 4.1 Basic Knowledge of Security Management This describes the conceptual knowledge of security management, such as centralized user management, user authority, and NE users. Better understanding of the knowledge helps you to manage the authority of a user or a user group, and to guarantee the system safety. 4.2 Refreshing the Security Management Interface Because the security management interface cannot automatically refresh, other users cannot view the interface changes in real time when one user is operating on the interface. This describes how to display the latest information on the security management interface through the refreshing function. 4.3 Configuring the M2000 This describes how to configure the M2000 before you run it. After you install the M2000, configure it according to the actual situations. 4.4 Customizing MML Authority This describes the MML authority to NEs. The authority refers to the MML commands that you can run on the LMT and M2000 clients. According to the functions, NEs divide the MML commands into several command groups. You can customize command groups according to actual requirements. You can grant the authority to the MML commands of command groups to a specified user. In this way, the user can run all the commands in the command group. 4.5 Creating OM Users OM users operate and maintain the entire network or specified NEs through the M2000. You can manage OM users by creating OM user groups, assigning the authority to OM user groups, and creating OM user accounts. 4.6 Modifying an OM User This describes how to modify an existing OM user. For an existing OM user, you can modify the user's authority, basic information, and password. 4.7 Deleting an OM User Group
This describes how to delete an OM user group. You can delete an unwanted OM user group based on the requirements to save the system resource. The deletion of an OM user group indicates that only the authority of the OM user for the associated command groups is deleted. After the deletion, the OM user still exists without belonging to any user group. 4.8 Deleting an OM User This describes how to delete an OM user. Based on the requirements, you can delete an unneeded OM user to save the system resource. If an OM user already has the binding relationship with an NE, the user bound to the NE is also deleted when you delete an OM user. In this way, the information on the OM user is removed from the M2000. 4.9 Querying Authorization You can query the authorization of the NEs and the M2000 rights in the M2000. 4.10 Comparing the OM User Rights You can compare the rights of two users in the M2000. 4.11 Managing NE Users This describes NE users. NE users can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. 4.12 Monitoring OM Users This describes how to monitor an OM user. The M2000 offers the user-monitoring function to monitor users' login and operations. This prevents illegal users from attacking the system. 4.13 Reference for Security Management Interfaces This part describes the security management interface and the parameters, which can help you perform the related operations.
4-2
Issue 06 (2008-12-16)
4.1 Basic Knowledge of Security Management

This describes the conceptual knowledge of security management, such as centralized user management, user authority, and NE users. Better understanding of the knowledge helps you to manage the authority of a user or a user group, and to guarantee the system safety. 4.1.1 Centralized User Management This describes how to maintain users on centralized management networks. The user maintenance includes account management, authority assignment, and user monitoring. 4.1.2 User Authority A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. 4.1.3 NE User This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. The NE user can also troubleshoot NEs at the near end of NEs. 4.1.4 Introduction to the FTPS This describes the FTPS, which refers to the FTP transmission through encryption techniques on the basis of the SSL protocol.
4.1.1 Centralized User Management

This describes how to maintain users on centralized management networks. The user maintenance includes account management, authority assignment, and user monitoring.
User account
A user account is the identification for operation and maintenance. On M2000 networks, the user account consists of the OM user account and NE user account.
l l
NE users are the users who operate and maintain NEs at the LMT. OM users operate and maintain the entire network or specified NEs through the M2000.
Centralized Management Mode

The M2000 centralized user management consists of two modes:
l
For category A NEs, you can grant relevant rights to an OM user and the OM user becomes an NE user, In this way, you can perform uniform management of user accounts on the entire network. For category B/C NEs, you need to create an OM user on the M2000 and NE user on the NEs, and then manually establish and maintain the association between the OM user and NEs.
For details of category A/B/C NEs, refer to 3.3.1 NE Type.
Issue 06 (2008-12-16)
4-3
User monitoring and control

The function of user monitoring provided by the M2000 enables you to monitor the operation and session of a user, and to query the operation log. For category A NEs, you can monitor the operation and session of a user on the M2000 and at the LMT at the same time.
4.1.2 User Authority

A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. The user authority consists of the user, operation, and NE. That is, the user authority defines the operations that users perform. When you assign authority to OM users, consider that the operation is performed through the M2000 client or the MML commands.
Authority Item
According to whether NEs are involved in the operations, the M2000 authority is categorized into network management application authority and network device authority. The network management application authority does not involve the operations related to the devices on the M2000, such as creating a user and viewing user logs. The network device authority involves the operations related to the devices on the M2000, such as viewing NE operation logs and downloading NE software. According to the functions, NEs divide the MML commands into several command groups. You can customize command groups according to actual requirements. You can grant the authority of the MML command group to a specified user. In this way, the user can run all the commands in the command group.
Allocation Mechanism
To simplify the allocation of user authority, the M2000 provides the allocation mechanism at user group and user levels. The user authority contains the authority of the user group that the user belongs and the authority of the user. You can grant the authority of several MML command groups of specified NE types to an OM user or OM user group. In this way, you can create an authority rule. After the authority rule is created, you can distribute the rule to specific NEs. In this way, the OM user or OM user group have the authority to the MML commands of the NEs. If the authority rule is successfully created, the OM user or OM user group automatically have the authority to the MML commands of new NEs of this NE type.
Related Tasks
4.5.4 Assigning Operation Rights to an OM User Group 4.5.10 Assigning Operation Rights to an OM User 4.6.3.2 Modifying the Operation Rights of an OM User 4.6.2.2 Modifying the Operation Rights of an OM User Group
Related References
4.13.9 Parameters for the Operation Authority of an OM User or an OM User Group
4.1.3 NE User
This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. The NE user can also troubleshoot NEs at the near end of NEs.
Type of NE Users
NE users consist of local NE users and non-local NE users.
l
The account, password, and authority of a local NE user are managed by NEs. The creation and modification of a local NE user are performed at the LMT. NEs provide several default local users.
CAUTION
The NodeBs have only default local users because the NodeBs have no BAM and cannot create any local users.
l
The account, password, and authority of a non-local NE user are managed by the M2000. The creation and modification of a non-local NE user are performed through the M2000.
User Management of Category A NEs

Category A NEs support local and non-local NE users. If an OM user is granted with the MML authority of category A NEs, the OM user becomes a non-local user of the NEs. For details about NEs of category A, see 3.3.1 NE Type. The M2000 manages non-local users, which integrates the OM user account and NE user account. Thus, non-local NE users have higher priority than local NE users. You can set whether to enable NE local user to log in to and manage NEs on the M2000.
User Management of Category B/C NEs

NEs of category B/C support only local NE users. For details about the category B/C NE list, see 3.3.1 NE Type. To perform centralized management to category B/C NEs, you can create an NE User account in the M2000 NE User window. The user names and passwords of the accounts are the same with those of local NE users. Then you can associate the accounts to corresponding OM users.
NOTE
The user information are independent from each other. The system cannot synchronize the information about the two accounts. You need to manually synchronize the information about the NE user on the M2000 and the local user in the NEs.
4.1.4 Introduction to the FTPS

This describes the FTPS, which refers to the FTP transmission through encryption techniques on the basis of the SSL protocol. The FTPS function is implemented in the FTPS client and the FTPS server:
l
FTPS client: Based on the SSL library, the FTPS client extends FTP commands and configures security policies. The FTPS client is configured on the M2000. By using the FTPS client, the M2000 modules such as the software management module and the performance management module can interact with NEs. FTPS server: Based on the open source vsftpd codes, the FTPS server extends and processes part of FTP commands and configures security policies. The FTPS server mainly interacts with the RNC.
FTPS applies to the FTP that does not use encryption techniques. Through the addition of the SSL protocol, FTPS enables the FTP to transmit encrypted data. The purpose of FTPS is to improve the reliability of the file and data transmission through encryption.
4.2 Refreshing the Security Management Interface

Because the security management interface cannot automatically refresh, other users cannot view the interface changes in real time when one user is operating on the interface. This describes how to display the latest information on the security management interface through the refreshing function.
Prerequisite
l l
You have logged in to the M2000 client. You have the relevant operation authorization.
Procedure
Step 1 Choose Security and select an option to enter the related security management interface. Step 2 Click the shortcut icon ----End at the upper part of the navigation tree to obtain the latest information.
4.3 Configuring the M2000

This describes how to configure the M2000 before you run it. After you install the M2000, configure it according to the actual situations. 4.3.1 Setting the M2000 Security Policy This describes how to set the security policies such as the password policy, account policy, and system policy to ensure the security of the NM system. 4.3.2 Setting Single-User Mode The M2000 runs in the multiuser mode by default. When you perform maintenance on the M2000 server, for security purposes, you can set the M2000 to the single-user mode. 4.3.3 Setting the System ACL You can set the Access Control List(ACL) to allow the users to log in to the M2000through the clients of only the specific IP addresses or network segment. 4.3.4 Setting FTPS Parameters This describes how to set the FTPS parameters.
4.3.1 Setting the M2000 Security Policy

This describes how to set the security policies such as the password policy, account policy, and system policy to ensure the security of the NM system. 4.3.1.1 Setting the Password Policy You can set the password policy to set the parameters such as password valid days, length of a password and number of letters in a password. 4.3.1.2 Setting the Account Policy You can set the account policy to set the parameters such as maximum login attempts and auto unlock time. 4.3.1.3 Setting the System Policy The number of sessions is the number of the connections between the M2000 client and the M2000 server. You can set the system policy to set the maximum number of the sessions that are supported by the M2000.
Related References
4.13.15 Parameters for the System Security Policy
Setting the Password Policy

You can set the password policy to set the parameters such as password valid days, length of a password and number of letters in a password.
Context
l
The password dictionary is a password set of characters or strings. In the password dictionary file, each row contains only one character or string. The suffix of each password dictionary file is dic. The file is in $iManagerM2000Client/etc/conf/pwddic/ on the M2000 server. The number of the password dictionary files are not limited in the M2000, but the total rows in all the password dictionary files cannot exceed 5000.
Procedure
Step 1 Choose Security > Security Policy. Step 2 In the Security settings navigation tree, select Password Policy. Step 3 In the right pane, set the password policy. Step 4 Click Apply. ----End
Related References
Setting the Account Policy

You can set the account policy to set the parameters such as maximum login attempts and auto unlock time.
Context
l
When you log in to the M2000, if the failed login times exceed the value set in Max. Login Attempts, the account is locked to prevent attacks from illegal users to the M2000. When your account is locked, the user who has the right to unlock can unlock your account. You can also wait for the M2000 to unlock your account automatically. The unlock time is defined in the account policy.
Procedure
Step 1 Choose Security > Security Policy. Step 2 In the Security settings navigation tree, select Account Policy. Step 3 In the right pane, set the policies such as the maximum login attempts and auto unlock time. Step 4 Click Apply. ----End
Related References
Setting the System Policy

The number of sessions is the number of the connections between the M2000 client and the M2000 server. You can set the system policy to set the maximum number of the sessions that are supported by the M2000.
Context
The maximum number of sessions in the M2000 depends on the following three elements:
l
Login mode. In single-user login mode, only the admin user is allowed to log in to the M2000 through a client regardless of the value of Maximum Sessions.
Hardware condition. In some hardware conditions such as memory overflow, the user is not allowed to log in to the M2000.
ESN or license. Table 4-1 shows impact of ESN and license on Maximum Sessions. Table 4-1 Impact of ESN and license on Maximum Sessions Condition ESN is not matched or the license is invalid Maximum Session 3 Description If three users already log in through clients, no more user can log in. If the number of users who already log in is less than three, any other user can log in.
Issue 06 (2008-12-16)
4-8
Condition ESN is matched and the license is valid
Maximum Session The smaller number in the license and the specified value of Maximum Sessions.
Description If the number of current sessions exceeds the value set in Maximum Sessions but does not exceed the number in the license, the admin user can still log in to the M2000.
Procedure
Step 1 Choose Security > Security Policy. Step 2 In the Security settings navigation tree, select System Policy. Step 3 In the right pane, set the maximum number of the sessions that are supported by the M2000. Step 4 Click Apply. ----End
Related References
4.3.2 Setting Single-User Mode

The M2000 runs in the multiuser mode by default. When you perform maintenance on the M2000 server, for security purposes, you can set the M2000 to the single-user mode.
Context
CAUTION
l
Only the admin user and the members of the Administrators group can set the single-user mode. Only the admin can log in to the M2000 through a client and all the other users are forced to log out after the M2000 is switched from the multiuser mode to the single-user mode. Please switch to the multiuser mode after you complete the operations in the single-user mode.
Procedure
Step 1 Choose System > Preferences. Step 2 In the navigation tree on the left, select System Login Mode. Step 3 In the System Login Mode group box, select Single user mode.
4.3.3 Setting the System ACL

You can set the Access Control List(ACL) to allow the users to log in to the M2000through the clients of only the specific IP addresses or network segment.
Context
To set the system ACL, you must have the Edit Security Policy right.
Procedure
Step 1 Choose Security > Access Control List. Step 2 In the Access Control List window, specify the IP addresses of the clients that can log in to the M2000 server. l l Click Add. In the New System Access Control Item dialog box, enter the IP address or network segment and description. Click OK. Select the IP addresses or network segment that need to be modified, and then click Modify. In Modify System Access Control Item, modify relevant information, and then click OK. Select the IP addresses or network segment that need to be deleted, and then click Delete. In the Confirm dialog box, click Yes.
Step 3 In the Access Control List window, click Close. ----End
4.3.4 Setting FTPS Parameters

This describes how to set the FTPS parameters.
Prerequisite
l l l
The M2000 system is operational. NEs support the FTPS function. The FTPS client is connected to the FTPS server.
Procedure
Step 1 Choose Software > FTPS Parameters Setting . The FTPS Parameters Setting dialog box is displayed. Step 2 Set Encrypted Mode, Supported State, Transmission Mode, Firewall Traversal Supported, Progress Interval (seconds), Command Port, Data Port, Transmission Size (bytes), Min. Port, and Max. Port. For detailed parameter description, refer to 4.13.16 Parameters for FTPS Parameter.
CAUTION
The settings of the parameters except Command Port and Data Port are applicable to only the M2000 that serves as the FTPS client. Step 3 Click Apply or OK. If you click Apply, the system does not close the FTPS Parameters Setting dialog box. ----End
Related Concepts
Related References
4.13.16 Parameters for FTPS Parameter
4.4 Customizing MML Authority

This describes the MML authority to NEs. The authority refers to the MML commands that you can run on the LMT and M2000 clients. According to the functions, NEs divide the MML commands into several command groups. You can customize command groups according to actual requirements. You can grant the authority to the MML commands of command groups to a specified user. In this way, the user can run all the commands in the command group. 4.4.1 Customizing an NE Type Command Group This describes how to define a common command group according to actual requirements. New NEs of a certain type automatically have the authority to the custom command group. You can also issue the NE type command group to an existing NE, and then the NE obtains the authority to the custom command group. 4.4.2 Customizing an NE Command Group This describes how to customize an NE command group when the command group provided by NEs cannot meet the requirements for the authority set by users. You can combine several commands into a command group. By assigning the authority to the command group to a specified user, the user obtains the authority to the command group. 4.4.3 Setting Authority Rules for NE Types This describes how to set an authority rule by granting the authorization of the MML command group of a specified NE type to an OM user or a user group. Issue the authority rule to the specified NEs so that the OM user or user group owns the MML command authorization of the NEs. Once the authority rule is created successfully, the OM user or user group owns the MML command authorization of all the new NEs of the same NE type. 4.4.4 Issuing Authority Rules for NE Types This describes how to issue authority rules for NE types. After you apply the authority rules on the NEs that are of the corresponding types, the OM user obtains the MML authorities of the NEs. 4.4.5 Synchronizing NE Security Data
The describes how to synchronize the NE security data. The NE security data is the operationrelated data. The synchronization of NE security data synchronizes the user data on the M2000 with that of the NEs to ensure the data consistency between NEs and the M2000.
Related Tasks
4.5.6 Granting MML Authority to an OM User Group 4.5.13 Grant MML Authority to an OM user 4.6.3.4 Modifying the MML Authority to an OM User 4.6.2.4 Modifying the MML Authority to an OM User Group
4.4.1 Customizing an NE Type Command Group

This describes how to define a common command group according to actual requirements. New NEs of a certain type automatically have the authority to the custom command group. You can also issue the NE type command group to an existing NE, and then the NE obtains the authority to the custom command group.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed. Step 2 Select an NE type node from the navigation tree. Right-click and choose Customize Command Group. You can also click Customize Command Group in the right pane. Step 3 In the displayed Customize Command Group dialog box, click Add. Step 4 Set the information about the command group in the Add Command Group dialog box. 1. 2. 3. Choose the name of the new command group in the Name drop-down list. Value range: M_0 to M_14. Enter the description of the command group in Description. Choose the command to be added to the command group from the Command navigation tree.
Step 5 Click OK. The new command group is displayed in the Customize Command Group window. Step 6 Click Close to close the Customize Command Group dialog box. ----End
Result
New NEs of a certain type automatically have the authority to the custom command group.
Postrequisite
You can also issue the NE type command group to a specific NE, and then the NE obtains the authority to the custom command group. The detailed procedures are as follows: 1. Set the authority rules of NE type. For details, refer to 4.4.3 Setting Authority Rules for NE Types.
4-12
2.
Issue authority rules to a specific NE. For details, refer to 4.4.4 Issuing Authority Rules for NE Types.
4.4.2 Customizing an NE Command Group

This describes how to customize an NE command group when the command group provided by NEs cannot meet the requirements for the authority set by users. You can combine several commands into a command group. By assigning the authority to the command group to a specified user, the user obtains the authority to the command group.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed. Step 2 You can use either of the following two methods to customize an NE command group. Operation Procedure Procedure Method one 1. Select a specific NE node under the NE type node from the navigation tree. Right-click the node and choose Add Command Group. You can also click Add on the Command Group tab page in the right pane. 2. Choose the name of the new command group in Name. Enter the description of the command in Description. 3. Choose the command to be added to the command group from the Command navigation tree. 4. Click OK. Method two 1. For details about customizing an NE type command group, refer to 4.4.1 Customizing an NE Type Command Group. 2. For details about creating authority rules of NE type, refer to 4.4.3 Setting Authority Rules for NE Types. 3. Issue the authority rule to the specific NE so that the NE owns the customized command group authority of the NE type. For details, refer to 4.4.4 Issuing Authority Rules for NE Types. Step 3 You can issue the authority to the custom command group to a specific user. For details, refer to 4.5.13 Grant MML Authority to an OM user. ----End
Related References
4.13.14 Parameters for Customizing an NE Command Group
4.4.3 Setting Authority Rules for NE Types

This describes how to set an authority rule by granting the authorization of the MML command group of a specified NE type to an OM user or a user group. Issue the authority rule to the specified NEs so that the OM user or user group owns the MML command authorization of the NEs. Once the authority rule is created successfully, the OM user or user group owns the MML command authorization of all the new NEs of the same NE type.
Prerequisite
The NEs are available before the authority rule of the NE type is created.
Procedure
l Start the setting from the NE User Management window. 1. 2. 3. Choose Security > NE User Management. The NE User Management window is displayed. Select the NE type node on the navigation tree. Right-click the node and select Setting Rule , or click Setting Rule in the right window. In the displayed Setting Rule dialog box, select the user and the corresponding command group. Click OK. The change in the NE type does not affect the existing NEs. You can manually modify the authorization through 4.4.4 Issuing Authority Rules for NE Types. l Start the setting from the Security Management window. 1. 2. 3. Choose Security > Security Management . The Security Management window is displayed. Select the user or user group node on the navigation tree. Right-click the node and select Setting Rule, or click Setting Rule in the Rules tab at the right window. In the displayed Setting Rule dialog box, select the NE type, the corresponding command group, and the user or user group . Click OK. The change in the NE type does not affect the existing NEs. You can manually modify the authorization through 4.4.4 Issuing Authority Rules for NE Types. ----End
Related References
4.13.5 Interface Description: Authority Rules for NE Type
4.4.4 Issuing Authority Rules for NE Types

This describes how to issue authority rules for NE types. After you apply the authority rules on the NEs that are of the corresponding types, the OM user obtains the MML authorities of the NEs.
Prerequisite
l l
You have logged in to the M2000 client. The authority rules for NE types are already created.
Procedure
Step 1 Choose Security > NE User Management. The NE User Management window is displayed. Step 2 Issue the authority rules for NE types to specific NEs.
4-14
Issue 06 (2008-12-16)
Issuing mode Issue all the set authority rules for this type.
Procedure Mode one: 1. Select the NE type node whose authority rules are to be issued from the navigation tree. Right-click the node and choose Apply Rule or click Apply Rule in the right pane. 2. In the displayed Confirm dialog box, click Yes. 3. Choose the NEs whose authority rules are to be loaded in the Apply Rule dialog box and click Start. 4. Click Close to close the Apply Ruledialog box. Mode two: 1. Choose the NE types whose authority rules are to be loaded from the navigation tree. Right-click and choose Load Rule or click the Binded NE tab and choose Load Rule. 2. In the displayed Confirm dialog box, click Yes.
Issue some of the set authority rules for this type.
1. Choose the NE types whose authority rules are to be issued from the navigation tree. Choose the authority rules to be issued in the right pane. Click Apply Rule. 2. In the displayed Confirm dialog box, click Yes. 3. Choose the NEs whose authority rules are to be loaded in the Apply Rule dialog box and click Start. 4. Click Close to close the Apply Ruledialog box.
NOTE You can use Ctrl or Shift key to selectively issue the authority rules.
After the authority rules are applied to the selected NEs, the custom command groups set in the rules are added to the command groups preset for the NE. In addition, the added command groups are named in the same format as that of the command group parameters. After the authority rules are applied to an NE, you can modify the added command groups. The modification, however, does not affect the authority rules.
----End
Issue 06 (2008-12-16)
4-15
Result
After the NE type authority rule applies to the NEs created for this NE type, the original NE MML command authority of the OM user is invalid. In this case, the MML command authority of the user is the NE type authority rule.
4.4.5 Synchronizing NE Security Data

The describes how to synchronize the NE security data. The NE security data is the operationrelated data. The synchronization of NE security data synchronizes the user data on the M2000 with that of the NEs to ensure the data consistency between NEs and the M2000.
Context
The security data includes the following information: name, password, password policy, system mode, account policy, password validity period, login duration, binding IP address, system policy, inactive user policy (hibernate, delete), and user group information.
Procedure
Step 1 Choose Security > NE User Management. The NE User Management window is displayed. Step 2 Right-click the NE to be synchronized under the NE node in the navigation tree and choose Synchronize Security Data from the shortcut menu. Then the security data on the M2000 is synchronized with the NE. ----End
4.5 Creating OM Users

OM users operate and maintain the entire network or specified NEs through the M2000. You can manage OM users by creating OM user groups, assigning the authority to OM user groups, and creating OM user accounts. 4.5.1 Process for Creating OM Users This describes the process for creating OM users. The complete process for creating an OM user consists of the following tasks: creating an OM user group, setting the managed domain for an OM user group, setting operation rights for an OM user group, creating an OM user account, setting the managed domain for an OM user account. In actual operations however, you may need to perform only some of the tasks. 4.5.2 Creating an OM User Group By creating an OM user group, you can manage the OM user accounts in groups and grant related rights to the members of the group. 4.5.3 Setting the Managed Domain for an M2000 User Group You can set the managed domain for an M2000 user group to assign managed objects to the M2000 user group. 4.5.4 Assigning Operation Rights to an OM User Group This section describes how to assign operation rights to an OM user group. 4.5.5 Assigning Rights of New NEs to an OM User Group You can assign new device rights to an OM user group by NE type. When an NE is added, the user group has all the rights of the NE type to the NE.
4.5.6 Granting MML Authority to an OM User Group This describes how to assign the MML authority to an OM user group. This enables users in the same user group have the same MML authority. 4.5.7 Creating an OM User Account You can create the OM user accounts in the M2000 so that multiple OM users can operate and manage the M2000. 4.5.8 Synchronize OM User Data This describes how to synchronize the OM user data. The synchronization of OM user data synchronizes the data on the M2000 with that of the associated NE. If the M2000 is disconnected from the NE, the data cannot be synchronized with that of the NE when you set the NE authority on the M2000. When the M2000 is reconnected to the NE, synchronize the data on the M2000 with that of the NE. 4.5.9 Adding an OM User to a User Group You can add the OM users to user groups. These users can be managed in a centralized manner and, thus, you can assign rights to the users. 4.5.10 Assigning Operation Rights to an OM User This section describes how to assign operation rights to an OM user. 4.5.11 Setting the Managed Domain for an OM User You can set the managed domain for an OM user to allocate the managed objects to the user. 4.5.12 Setting the User ACL You can set the ACL to allow the users to log in to the M2000 only through the clients of the specific IP addresses or network segment. 4.5.13 Grant MML Authority to an OM user This describes how to grant the MML authority to a specified OM user. The user can run all the commands in the command group to NEs. After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs.
4.5.1 Process for Creating OM Users

This describes the process for creating OM users. The complete process for creating an OM user consists of the following tasks: creating an OM user group, setting the managed domain for an OM user group, setting operation rights for an OM user group, creating an OM user account, setting the managed domain for an OM user account. In actual operations however, you may need to perform only some of the tasks. Table 4-2 shows a simple process for creating OM users. Table 4-2 Simple process for creating OM users Process 1 Then... Creating an OM User Account Description Create an OM user account so that users can use the account to log in to the M2000 client. After a user is added to a user group, a user inherits the rights of the user group.
Adding an OM User to a User Group
A complete process for creating OM users is displayed, as shown in Table 4-3.

Table 4-3 Complete Process for Creating OM Users Process 1 2 Operation Create an OM user group Set the managed domain for an OM user group Description Grouping can reduce the complexity of user management. By setting the managed domain for a user group, you can set the objects that can be managed by a user group. By authorizing the user groups, you distribute the user groups with the corresponding rights. Distribute the rights for the new equipment to the user group to benefit the users by managing the new equipment. Before you operate the M2000, you should obtain the user account first. Synchronize the data of the M2000 with that of the NEs. Add a user to this user group. Then, the user automatically owns the rights of the user group. By setting the managed domain for the OM user, set the managed objects for the user. By authorizing the user, you assign the user with the corresponding rights. To ensure the security of the M2000, you can set the condition that the user can log in to the client only through a specific IP address. Assign OM users with the MML commands of the NEs. After the OM users have related operation rights, they can run the MML commands on the NEs.
Assign operation rights to an OM user group Assigning rights of new NEs to an OM user group
Create an OM user account
6 7
Synchronize OM user data Add an OM user to a user group
Set the managed domain for an OM user Assign operation rights to an OM user Set the user ACL
10
11
Grant MML authority to an OM user
4.5.2 Creating an OM User Group

By creating an OM user group, you can manage the OM user accounts in groups and grant related rights to the members of the group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, right-click the User Group node and select New User Group. Step 3 In the New User Group dialog box, on the Details tab, set Name and Description. You can also click Add to select the user you want to add to the user group, and then click Copy Rights From User Group to copy operation rights from other user groups. Step 4 Optional: If you want to set the managed domain for the user group in the New User Group dialog box, click the Domain tab. Set the objects that are managed by the user group. Step 5 Optional: If you want to set operation rights for the user group in the New User Group dialog box, click the Operation Rights tab. Set the operation rights for the user group. Step 6 Optional: If you want to set new NE rights for the user group in the New User Group dialog box, click the New Device Rights tab. Set new NE rights for the user group. Step 7 Click OK. ----End
Related References
4.13.8 Parameters for Adding an OM User Group
4.5.3 Setting the Managed Domain for an M2000 User Group

You can set the managed domain for an M2000 user group to assign managed objects to the M2000 user group.
Context
The nodes in the navigation tree are divided by NE type. If you select a node of an NE type, all the NEs of this type are selected. If you select the root node, all the NEs are selected.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User Group node, select the user group you want to set. Step 3 In the pane on the right, click the Domain tab. Step 4 On the Domain tab, click Add. Step 5 In the Add Domain dialog box in the Topology Root navigation tree, select the managed objects for the user group, and then click OK. ----End
4.5.4 Assigning Operation Rights to an OM User Group

This section describes how to assign operation rights to an OM user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators group has all the operation rights. You cannot change the rights of this group. You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User Group node, select the user group you want to set. Step 3 From the pane on the right, click the Operation Rights tab. Step 4 On the Operation Rights tab, click Add. Step 5 In the Add Operation Rights dialog box, select the type of operation rights and the corresponding rights. Click OK.
NOTE
If the type of the selected operation right is Network Device, you can do as follows:
l l l
Add the device to the managed domain of the user group before you set the operation rights to the device. Select the device in the left navigation tree, and select the operation rights to the device in the list on the right to add the operation rights. In the left navigation tree, right-click an NE or an object of an unknown type and select Copy Rights . Then in the right navigation tree, right-click another NE or another object of an unknown type and select Paste Rights to paste the rights of an NE or an object of an unknown type to another NE or another object of an unknown type. In the left navigation tree, right-click an NE and select Copy Rights to. In the Copy Rights to Devices of the Same Type dialog box, select the NE where you want to paste the rights, and then click OK. The rights of an NE are copied to another NE of the same type.
----End
Related Concepts
Related References
4.5.5 Assigning Rights of New NEs to an OM User Group

You can assign new device rights to an OM user group by NE type. When an NE is added, the user group has all the rights of the NE type to the NE.
Context
The Administrators user group has all the rights. You cannot modify new device rights of this group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User Group node, select the user group you want to set. Step 3 In the pane on the right, click the New Device Rights tab. Step 4 On the New Device Rights tab, click Add. Step 5 In the Add New Device Rights dialog box, select relevant rights, and then click OK. ----End
4.5.6 Granting MML Authority to an OM User Group

This describes how to assign the MML authority to an OM user group. This enables users in the same user group have the same MML authority.
Prerequisite
l l l l
You are authorized with the relevant privileges. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some MML commands of the specific NE types to an OM user or group. If the authority rule is successfully created, the OM user or OM user group automatically have the authority to the MML commands of all new NEs of this NE type.
NOTE
When you assign MML command authority to OM user groups, the M2000 does not display the defined rules of NE type authority. The MML command authority of a user group is the union of the NE MML command authority and NE type authority rule. After you assign NE MML command authority to an OM user group and then issue NE type authority rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority of the user group is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to 4.4.3 Setting Authority Rules for NE Types and 4.4.4 Issuing Authority Rules for NE Types.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group in the User Group node from the navigation tree. Click the Binded NE tab in the right pane. Step 3 Click Bind NE. Step 4 In the Bind NE dialog box, choose a user group, an NE type, and a command group. Click OK or Apply to assign the MML authority to an OM user group.
l l
Click OK to save the settings and close the dialog box. Click Apply to save the setting, but the dialog box is not closed. You can continue to assign the MML authority to other user groups.
----End
Related Concepts
Related Tasks
Related References
4.13.10 Parameters for the MML Authority to an OM User Group or an OM User 4.13.4 Interface Description: MML Authority Information of an OM User
4.5.7 Creating an OM User Account

You can create the OM user accounts in the M2000 so that multiple OM users can operate and manage the M2000.
Context
l l
When the default account policy is used, the user name must contain from 6 to 32 characters. You can modify the minimum length of the user name by setting the account policy.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, right-click the User node and select New User. Step 3 In the New User dialog box on the Details tab, set User Name, Description, and Password. Step 4 Optional: If you want to add the user to a user group in the New User dialog box, click the User Groups tab. Select the user group to which you want to add the user. Step 5 Optional: If you want to set the managed domain for the user in the New User dialog box, click the Domain tab. Set the objects that are managed by the user. Step 6 Optional: If you want to set operation rights for the user in the New User dialog box, click the Operation Rights tab. Set operation rights for the user. Step 7 Optional: If you want to set the ACL for the user in the New User dialog box, click the Access Control List tab. Set the ACL for the user. Step 8 Click OK. ----End
Related References
4.13.13 Parameters for Creating an M2000 User Account
4.5.8 Synchronize OM User Data

This describes how to synchronize the OM user data. The synchronization of OM user data synchronizes the data on the M2000 with that of the associated NE. If the M2000 is disconnected from the NE, the data cannot be synchronized with that of the NE when you set the NE authority on the M2000. When the M2000 is reconnected to the NE, synchronize the data on the M2000 with that of the NE.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select a user under the User node on the navigation tree. Right-click the node and select Synchronize User Data. Or click Synchronize User Data in the Binded NE tab.
NOTE
If the selected user is not bound to any NE, the data of the user cannot be synchronized.
Step 3 In the displayed Messagedialog box, clickOK.

NOTE
During data synchronization,M2000 removes user data on theLMT and creates new data. The online NE user is forcibly logged out of LMT .
Step 4 Select the NEs to be synchronized in the Synchronize User Data dialog box. Click Start to synchronize the OM user data with that of the NEs. The Synchronize User Data dialog box displays the progress of synchronizing OM user data to the NEs. Step 5 Click Close. The Synchronize User Data dialog box is closed. ----End
4.5.9 Adding an OM User to a User Group

You can add the OM users to user groups. These users can be managed in a centralized manner and, thus, you can assign rights to the users.
Context
You cannot add the user admin to a user group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the User Groups tab. Step 4 On the User Groups tab, click Add. Step 5 In the Add User Group dialog box, select the user group to which you want to add the user. Click OK. ----End
4.5.10 Assigning Operation Rights to an OM User

This section describes how to assign operation rights to an OM user.
Context
You cannot set the operation rights of the user admin.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Operation Rights tab. Step 4 On the Operation Rights tab, click Add.
NOTE
Select Show access from user group. The operation rights of the user group are displayed in gray in the operation rights list.
Step 5 In the Add Operation Rights dialog box, select the type of operation rights and the corresponding rights. Click OK.
NOTE
If the type of the selected operation right is Network Device, you can do as follows:
l l l
Add the device to the managed domain of the user before you set the operation rights to the device. Select the device in the left navigation tree, and select the operation rights to the device in the list on the right to add the operation rights. In the left navigation tree, right-click an NE or an object of an unknown type and select Copy Rights . Then in the right navigation tree, right-click another NE or another object of an unknown type and select Paste Rights to paste the rights of an NE or an object of an unknown type to another NE or another object of an unknown type. In the left navigation tree, right-click an NE and select Copy Rights to. In the Copy Rights to Devices of the Same Type dialog box, select the NE where you want to paste the rights, and then click OK. The rights of an NE are copied to another NE of the same type.
----End
Related Concepts
Related References
4.5.11 Setting the Managed Domain for an OM User

You can set the managed domain for an OM user to allocate the managed objects to the user.
Context
l
You cannot set the managed domain for the admin user.
4-24

l
When the user managed domain is set, M2000 does not display the managed domain of its user group. The final managed domain for the user is the union of the allocated user managed domain and its user group managed domain.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Domain tab. Step 4 On the Domain tab, click Add. Step 5 In the Add Domain dialog box in Topology Root navigation tree, select the managed objects, and then click OK. ----End
4.5.12 Setting the User ACL

You can set the ACL to allow the users to log in to the M2000 only through the clients of the specific IP addresses or network segment.
Context
l l
To set the user ACL, you must have the User Management right. The system ACL allows all the OM users to log in to the M2000 only through the clients of the specific IP addresses or network segment. The user ACL is a subset of the system ACL. The user ACL is effective only for the current user.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Access Control List tab. Step 4 On the Access Control List tab, do as follows: l l Select Use the system Access Control List. Select Use the current user Access Control List. Then select the IP addresses or network segment through which the users can log in to the server.
4.5.13 Grant MML Authority to an OM user

This describes how to grant the MML authority to a specified OM user. The user can run all the commands in the command group to NEs. After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs.
Prerequisite
l l
You have logged in to the M2000 client. Relevant NEs are properly connected to the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some MML commands of the specific NE types to an OM user or group. If the authority rule is successfully created, the OM user or OM user group automatically have the authority to the MML commands of all new NEs of this NE type.
NOTE
When you assign MML command authority to OM users, the M2000 does not display the defined rules of NE type authority. The MML command authority of a user is the union of the NE MML command authority and NE type authority rule. After you assign NE MML command authority to an OM user group and then issue NE type authority rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority of the user is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to 4.4.3 Setting Authority Rules for NE Types and 4.4.4 Issuing Authority Rules for NE Types.
Procedure
l Start the setting from the Security Management window. 1. 2. Choose Security > Security Management . The Security Management window is displayed. Choose a user in the User node from the navigation tree. Right-click the user and choose Bind NE. You can also click Bind NE on the Binded NE tab page in the right pane. In the displayed Bind NE dialog box, choose the command group to be assigned and NEs. Click OK to assign the MML authority to an OM user. Choose Security > NE User Management. The NE User Management window is displayed. Open the Bind Command Group window. You can choose either of the following two methods:
3. 4. l 1. 2.
Start the setting from the NE User Management window.
Select a specific NE node from the navigation tree. Right-click the node and choose Bind Command Group . You can also click Bind Command Group on the Binded NE tab page in the right pane. Select an NE user node from the navigation tree. Right-click the node and choose Bind Command Group . You can also click Bind Command Group on the Command Group tab page in the right pane.
3. 4. ----End
4-26
In the displayed Bind Command Group dialog box, choose the command group to be assigned and OM user. Click OK to assign the MML authority to an OM user.
Issue 06 (2008-12-16)
Postrequisite
After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs. You can choose Security > NE User Management and choose the NE user that maps to the OM user from the navigation tree. Click the Command Group tab to view the information about the assigned MML commands.
Related Concepts
Related Tasks
Related References
4.6 Modifying an OM User

This describes how to modify an existing OM user. For an existing OM user, you can modify the user's authority, basic information, and password. 4.6.1 Viewing the Details of an OM User This describes how to view the information about an OM user. In this way, you can familiarize yourself with the following items: the fundamental information about an OM user, the user group to which the OM user belongs, management domain, operation rights, access control list, MML command authorization of the managed NEs, and the authorization rule. 4.6.2 Modifying the Public Authority of an OM User This describes the public authority of an OM user. That is, the authority to the user group. Through the M2000 client, you can modify the management domain of the OM user group, operation authority, authority to new devices, and MML authority. The modification to the public authority to the OM user is applicable to all the OM users in the user group. 4.6.3 Modifying the Private Authority of an OM User This describes how to modify the private authority of an OM user. Through the M2000 client, you can modify the user group to which the OM user belongs, operation authority, access control list, and MML authority. The modification to the authority to the OM user is applicable only to the OM user. 4.6.4 Modifying the Information About an OM User This section describes how to change the information, such as user description, user validity, and login period, on the M2000. 4.6.5 Resetting the Password of an OM User This section describes how to reset the password of an OM user.
4.6.1 Viewing the Details of an OM User

This describes how to view the information about an OM user. In this way, you can familiarize yourself with the following items: the fundamental information about an OM user, the user group
to which the OM user belongs, management domain, operation rights, access control list, MML command authorization of the managed NEs, and the authorization rule.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select an OM user node under the User node on the navigation tree. Check the information about the OM user in each tab of the right window.
l
The Detail tab: displays the fundamental information about the OM user, such as user name, login time, and time for modifying the password. The User Groups tab: displays the user group to which the OM user belongs. The Domain tab: displays the managed objects of the OM user. The Operation Rights tab: displays the operation rights of the OM user. The Access Control List tab: displays the IP addresses on the client from which the OM user can log in to the M2000. The Binded NE tab: displays the MML command authorization that the OM user owns. The Rules tab: displays the authorization rule of the NE type set by the OM user.
l l l l
l l
----End
Related References
4.13.11 Parameters for the Information of an OM User
4.6.2 Modifying the Public Authority of an OM User

This describes the public authority of an OM user. That is, the authority to the user group. Through the M2000 client, you can modify the management domain of the OM user group, operation authority, authority to new devices, and MML authority. The modification to the public authority to the OM user is applicable to all the OM users in the user group. 4.6.2.1 Modifying the Management Domain of an OM User Group This describes how to assign and delete management objects by modifying management domain. 4.6.2.2 Modifying the Operation Rights of an OM User Group This describes how to distribute or delete the operation rights of an OM user group by adjusting the operation rights of the OM group. 4.6.2.3 Modifying the Authority to the New Devices in an OM User Group This describes the authority to new devices. The authority is granted according to the type of NE devices. After the authority is granted, the system automatically grants the authority to users if new devices of the defined types are added. 4.6.2.4 Modifying the MML Authority to an OM User Group This describes the MML authority to the users in the same user group. By modifying the MML authority to an OM user group, you can modify the MML authority to the users in the same user group.
Modifying the Management Domain of an OM User Group

This describes how to assign and delete management objects by modifying management domain.
Prerequisite
l l
You have logged in to the M2000 client. You have the management authorization of the user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators have all the authorities. You are not allowed to modify the management domain of this user. You can modify the management domain of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group whose management domain is to be modified under the User Group node from the navigation tree. Click Domain in the right pane. The objects managed by a user group are listed as a navigation tree on the Domain tab page. Step 3 Modify the management domain of an OM user. Modify the management domain of an OM user Add a management object Then...
1. Click Add or right-click and choose Add. 2. In the displayed Add Domain dialog box, choose a management object to be added. 3. Click OK.
Delete a management object
1. In the navigation tree on the Domain tab page, choose the management object to be deleted. 2. Click Delete or right-click and choose Delete. 3. In the displayed Confirm dialog box, click Yes.
----End
Modifying the Operation Rights of an OM User Group

This describes how to distribute or delete the operation rights of an OM user group by adjusting the operation rights of the OM group.
Prerequisite
l l
You have logged in to the M2000 client. You have the management authorization of the user group.
Issue 06 (2008-12-16)
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. Administrators have all the rights. You cannot modify the operation rights of this user group. You can, however, modify the operation rights of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select the user group for the adjustment under the User Group in the navigation tree. Click Operation Rights at the right window. In the Operation Rights tab, the operation rights owned by the user group are listed in table. Step 3 Adjust the operation rights of the OM user group. Adjust the operation rights of the OM Procedure user group. Add the operation rights. 1. Click Add or right-click and choose Add. 2. In the displayed Add Operation Rights window, select the type of the operation rights and the corresponding rights. 3. Click OK. Delete the operation rights. 1. In the list of the operation rights, select the unnecessary operation rights. Then, click Delete, or right-click the list and select Delete. 2. Click Yes in the displayed Confirm dialog box. ----End
Related Concepts
Related References
Modifying the Authority to the New Devices in an OM User Group

This describes the authority to new devices. The authority is granted according to the type of NE devices. After the authority is granted, the system automatically grants the authority to users if new devices of the defined types are added.
Prerequisite
l

4-30

l
You have the management authorization of the user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators group has all the operation rights. You cannot change the rights of this group. You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group to whom the authority to new devices is to be modified under the User Group node from the navigation tree. Click New Device Rights in the right pane. The authority to new devices in the user group is displayed in table format on the New Device Rights tab page. Step 3 Modify the authority to new devices in the user group Modify the authority to new devices in Procedure the user group Add authority to new devices 1. Click Add or right-click and choose Add. 2. In the displayed Add New Device Rights dialog box, choose the authority to be added. 3. Click OK. Delete authority to new devices 1. Choose the authority to be deleted from the New Device Rights list. 2. Click Delete or right-click and choose Delete. 3. In the displayed Confirm dialog box, click Yes. ----End
Modifying the MML Authority to an OM User Group

This describes the MML authority to the users in the same user group. By modifying the MML authority to an OM user group, you can modify the MML authority to the users in the same user group.
Prerequisite
l l l l
You have the management authorization of the user group. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user group to whom the MML authority is to be modified from the User Group node in the navigation tree, right-click the user group and choose Bind NE from the shortcut menu. You can also click Bind NE on the Binded NE tab page. Step 3 In the displayed Bind NE dialog box, choose the NE type and command group. Step 4 Click OK or Apply. ----End
Related Concepts
Related Tasks
Related References
4.6.3 Modifying the Private Authority of an OM User

This describes how to modify the private authority of an OM user. Through the M2000 client, you can modify the user group to which the OM user belongs, operation authority, access control list, and MML authority. The modification to the authority to the OM user is applicable only to the OM user. 4.6.3.1 Moving an OM User into Another User Group This describes how adjust the user group on which an OM user belongs to. In this way, the OM user has the authority to the user groups to which the OM user belongs. 4.6.3.2 Modifying the Operation Rights of an OM User This describes how to modify the operation rights of an OM user. You can assign or delete relevant authority to an OM user. 4.6.3.3 Modifying the OM Access Control List You can modify the OM access control list to modify the IP addresses of the clients through which the users can log in to the M2000 server. 4.6.3.4 Modifying the MML Authority to an OM User This describes the MML authority to an OM user. That is, the MML commands that the OM user runs on NEs. By modifying the MML authority to an OM user, you can modify the MML authority to the NEs of the user.
Moving an OM User into Another User Group

This describes how adjust the user group on which an OM user belongs to. In this way, the OM user has the authority to the user groups to which the OM user belongs.
Prerequisite
l l
You have logged in to the M2000 client. You have the authority to manager users.
Context
User admin has all the authority. You are not allowed to change the authority of this user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user in the User node from the navigation tree. Click the User Groups tab in the right pane. Step 3 Adjust the user group to which the OM user belongs according to actual requirements. Adjust the user group to which the OM user belongs. Procedure
Delete the OM user from a user group. 1. Choose a user group that needs not be bound to the OM user from the list, and click Delete. Alternatively, right-click it and choose Delete on the shortcut menu. 2. In the displayed Confirm dialog box, click Yes. Add the OM user to a user group. 1. Click Add or right-click and choose Add. 2. Choose a user group in the displayed Add User Group dialog box. 3. Click OK. ----End
Modifying the Operation Rights of an OM User

This describes how to modify the operation rights of an OM user. You can assign or delete relevant authority to an OM user.
Prerequisite
l l
You have logged in to the M2000 client. You have the authority to manager users.
Context
User admin have all the authority. You are not allowed to change the operation authority of this user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user under the User node from the navigation tree. Click the Operation Rights tab in the right pane.
l
The operation rights that an OM user directly obtains is listed on the Operation Rights tab page in table format. Select Show access from user group. The operation rights of the user group are displayed in the operation rights list.
Step 3 Adjust the operation rights of an OM user Adjust the operation rights of an OM Procedure user Add the operation rights. 1. Click Add or right-click and choose Add. 2. In the displayed Add Operation Rights window, select the type of the operation rights and the corresponding rights. 3. Click OK. Delete the operation rights. 1. In the list of the operation rights, select the unnecessary operation rights. Then, click Delete, or right-click the list and select Delete. 2. Click Yes in the displayed Confirm dialog box. ----End
Related Concepts
Related References
Modifying the OM Access Control List

You can modify the OM access control list to modify the IP addresses of the clients through which the users can log in to the M2000 server.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Access Control List tab.
Step 4 On the Access Control List tab, do as follows: l l Select Use the system Access Control List. Select Use the current user Access Control List. Then select the IP addresses or network segment through which the users can log in to the server.
Modifying the MML Authority to an OM User

This describes the MML authority to an OM user. That is, the MML commands that the OM user runs on NEs. By modifying the MML authority to an OM user, you can modify the MML authority to the NEs of the user.
Prerequisite
l l l l
You have the authority to manager users. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user to whom the MML authority is to be modified from the User node in the navigation tree, right-click the user and choose Bind NE from the shortcut menu. You can also click Bind NE on the Binded NE tab page. Step 3 In the displayed Bind NE dialog box, choose the NE type and command group. Step 4 Click OK to modify the command group of the OM user. Select the OM user node from the navigation tree, and then right-click the node and choose Refresh NE & Access from the shortcut menu. You can view the modified MML authority on the Binded NE tab page. ----End
Related Concepts
Related Tasks
Related References
4.6.4 Modifying the Information About an OM User

This section describes how to change the information, such as user description, user validity, and login period, on the M2000.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User node. Select the user whose information you want to modify. Click the Details tab from the pane on the right. Step 3 On the Details tab, modify the parameters in Description, Enable/Disable user account, and Valid time. Step 4 Click Apply. ----End
Related References
4.6.5 Resetting the Password of an OM User

This section describes how to reset the password of an OM user.
Context
l
The minimum length of the user password can be set in the password policy. For the description of setting password policy, see 4.3.1.1 Setting the Password Policy. By default, the length of the common user's password is 7. The value ranges from 7 to 16. The length of the admin's password ranges from 8 to 16. The user admin can reset the password of any user. The users in the Administrators group can reset the passwords of the users that are in other groups. If the users that are not in the Administrators group have the Reset Password right, they can reset the passwords of the users that are not in the Administrators group. If the users that are not in the Administrators group do not have the Reset Password right, they can reset only their own passwords.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window in the Security Management navigation tree, expand the User node. Right-click the user whose password you want to reset, and then select Reset Password.
NOTE
You can choose Security > Change Password to modify the password of the current login user.
Step 3 In the Reset Password dialog box, set New Password and Confirm Password, and then click OK. Step 4 In the Information dialog box, click OK. ----End
4.7 Deleting an OM User Group

This describes how to delete an OM user group. You can delete an unwanted OM user group based on the requirements to save the system resource. The deletion of an OM user group indicates that only the authority of the OM user for the associated command groups is deleted. After the deletion, the OM user still exists without belonging to any user group.
Context
NOTE
l l
The user groups Administrators, Guests, and Operators cannot be deleted. If an user in the OM user group has logged in to the server, the user group cannot be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Click the User Group node on the navigation tree. Delete a user group by using the following two methods:
l l
Right-click a user group under User Group and choose Delete. Choose the user group to be deleted in the right pane, and then click Delete or right-click the user group and choose Delete to delete the user group.
Step 3 In the displayed Confirm dialog box, click Yes. After the deletion, the users on the M2000 can be regrouped and granted with new authority. ----End
4.8 Deleting an OM User

This describes how to delete an OM user. Based on the requirements, you can delete an unneeded OM user to save the system resource. If an OM user already has the binding relationship with an NE, the user bound to the NE is also deleted when you delete an OM user. In this way, the information on the OM user is removed from the M2000.
Context
NOTE
The admin users and active users are not allowed to be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Remove an OM user You can choose either of the following two methods:
l
Click a specific user under the User node in the navigation tree, right-click the user, and then choose Delete.
Issue 06 (2008-12-16)
l
Choose the User node in the navigation tree. Choose the OM user to be deleted in the right pane and click Delete or right-click the user and choose Delete.
Step 3 In the displayed Confirmation dialog box, click Yes. ----End
4.9 Querying Authorization

You can query the authorization of the NEs and the M2000 rights in the M2000.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, click navigation tree. on the top of the Security Management
Step 3 In the Authorization Details dialog box, in the Topology Root navigation tree, select the name of a device . Then select rights from the rights navigation tree. The table on the right of the Authorization Details dialog box displays the users and user groups to which the right is assigned. ----End
4.10 Comparing the OM User Rights

You can compare the rights of two users in the M2000.
Procedure
Step 1 In the Security Management window, click navigation tree. on the top of the Security Management
Step 2 In the Select User for Compare dialog box, select two users. Step 3 Click OK. The comparison result is displayed in the Compare User Rights Result dialog box. ----End
4.11 Managing NE Users

This describes NE users. NE users can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users.
Context
For details about the difference between NE users of category A and NE users of category B/C, see 4.1.3 NE User. For details about the category A/B/C NE list, see 3.3.1 NE Type. 4.11.1 Creating an NE User
This describes how to operate and maintain NEs when they are not connected to the M2000 or they are disconnected from the M2000. You can create an NE user and then use this account to log in to the LMT to operate and maintain NEs. 4.11.2 Deleting an NE User This describes how to delete unwanted NE users. After you delete an NE user, the binding relationship between an OM user and NE is also deleted. 4.11.3 Changing the Password of an NE User This describes how to change the password of an NE user. 4.11.4 Associating OM User with NE User This describes how to associate an OM user with an NE user. In this way, the OM user is provided with the authority of the NE user. 4.11.5 Disassociating OM User with NE User This describes how to delete the association between an OM user and a category B/C NE user. In this way, the OM user does not have the authorities of the NE user.
4.11.1 Creating an NE User

This describes how to operate and maintain NEs when they are not connected to the M2000 or they are disconnected from the M2000. You can create an NE user and then use this account to log in to the LMT to operate and maintain NEs.
Prerequisite
Before you create a user of category B/C NEs, you need to create an NE local user on the NE side.
Context
For details about the difference between NE users of category A and NE users of category B/C, see 4.1.3 NE User. For details about the category A/B/C NE list, see 3.3.1 NE Type.
Procedure
Perform the following operations according to NE types. NE Type NEs of category A Creating an NE User 1. Create an OM user on the M2000 side. For details, see 4.5.7 Creating an OM User Account. 2. Assign the authority of the MML commands to an OM user For details, see 4.5.13 Grant MML Authority to an OM user.
Issue 06 (2008-12-16)
4-39
NE Type
Creating an NE User
NEs of category B/C 1. Choose Security > NE User Management. The NE User Management window is displayed. 2. Select a specific category B/C NE node from the navigation tree, and then right-click the node and choose New NE User from the shortcut menu. Or you can click New NE User on the right pane. You can also right-click on the right pane and choose New NE User. 3. Set user information in the displayed New NE User dialog box.
NOTE The information about the new NE user and NE local user is separate from each other. The system cannot synchronize the information about the two user accounts. You need to manually synchronize the information about the NE user on the M2000 and the local user in the NEs.
4. Click OK.
----End
Related Concepts
4.1.3 NE User
Related References
4.13.2 Interface Description: NE User Management Interface 4.13.12 Parameters for NE User
4.11.2 Deleting an NE User

This describes how to delete unwanted NE users. After you delete an NE user, the binding relationship between an OM user and NE is also deleted.
Context
NOTE
If you delete a category A NE user, the binding relationship between an OM user and NE is deleted. The OM user exists.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed. Step 2 Delete an NE user.
4-40
Issue 06 (2008-12-16)
Type of NE Users Category A NE user
Procedure Mode one: 1. Select the user node to be deleted from the navigation tree, and then right-click the node and choose Delete . 2. In the displayed Confirm dialog box, click Yes. Mode two: 1. Choose Security > Security Management . The Security Management window is displayed. 2. Select the node that maps to the OM user. Right-click the node and choose Bind NE. You can also click Bind NE on the Binded NE tab page in the right pane. 3. To cancel the binding relationship between the user and NE, and the relationship between the user and command group, click OK.
User of category B/C NEs Mode one: 1. Choose the user node to be deleted from the navigation tree, right-click and choose Delete NE User . 2. Click Yes in the displayed Confirm dialog box. Mode two: 1. Choose the NE node to which the NE user to be deleted belongs to from the navigation tree. Choose the NE user to be deleted in the right pane. Click Delete NE User or right-click and choose Delete NE User . 2. In the displayed Confirm dialog box, click Yes. ----End
4.11.3 Changing the Password of an NE User

This describes how to change the password of an NE user.
Context
Procedure
Perform the following operations according to NE types.
Issue 06 (2008-12-16)
4-41
NE Type NEs of category A
Changing the Password of an NE User For NEs of category A, the corresponding OM user becomes an NE user after you grant the related NE authority to the OM user. Therefore, you can modify an NE user of category A by changing the password of the corresponding OM user. For details, see 4.6.5 Resetting the Password of an OM User.
NEs of category B/C 1. Choose Security > NE User Management. 2. In the NE User Management window, in the NE User Management navigation tree, expand the NE type node. Click the NE user whose password you want to change in the NE User Management navigation tree, and then choose Change Password. 3. In the Change Password dialog box, select Effect Range. Enter the value of Old Password. Set New Password and Confirm Password.
NOTE
l When Modify the NMS password only is selected for Effect Range,
Old Password is entered by the system automatically.

l If you select Modify the NMS password only, only the password that
the NE user uses to log in to the M2000 will be modified.
4. Click OK. 5. In the Confirm dialog box, click OK.
----End
4.11.4 Associating OM User with NE User

This describes how to associate an OM user with an NE user. In this way, the OM user is provided with the authority of the NE user.
Context
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed. Step 2 Choose the OM user to be associated with the NE user from the navigation tree, right click the user and choose Associate NE User. Or you can click Associate NE User in the right pane. You can also right-click on the right pane and choose Associate NE User. Step 3 Choose the NEs to be associated with the OM user from the navigation tree. Choose the NE user to be associated in the table in the right pane. Click Set Association.
l
All category B/C NEs on the M2000 are displayed in the navigation tree in the dialog box. The selected NE users are displayed in the table in the right pane.
4-42

l l
For the same NE, one OM user can bind only one NE user. One OM user can be bound to a maximum of 255 NE users.
Related References
4.13.3 Interface Description: NE Login Management Interface
4.11.5 Disassociating OM User with NE User

This describes how to delete the association between an OM user and a category B/C NE user. In this way, the OM user does not have the authorities of the NE user.
Prerequisite
The OM user associates with the category B/C NE user.
Context
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed. Step 2 Choose the OM user whose association is to be deleted from the navigation tree. Choose one or more associated NE users in the right pane. Step 3 Click Delete Association, or right-click the menu and choose Delete Association . Step 4 In the displayed Confirm dialog box, click Yes. ----End
Related References
4.12 Monitoring OM Users

This describes how to monitor an OM user. The M2000 offers the user-monitoring function to monitor users' login and operations. This prevents illegal users from attacking the system. 4.12.1 User Operation Logs User operation logs records the operations of the users. By analyzing user operation logs, you get to know the operations performed by users and easily locate the users. 4.12.2 User Sessions A user session records the following information: login time, user group to which the user belongs, the terminal to which the user logs in, and the current status. You get to know what users have logged in to the system by monitoring the user session information. To ensure the
security of the system, you can also force some users to exit from the system. When a user logs in to the M2000 through the M2000 client or through the LMT of an NE, the M2000 or the NE establishes a user session to record the login information. 4.12.3 Monitoring Operation of OM Users on the M2000 You can monitor the OM user sessions and operations to prevent illegal user operations. 4.12.4 Viewing Operation of NE Users This describes how to monitor the sessions and operations of the NE users on the LMT. In this way, you can familiarize yourself with whether the local NE user logs in to the LMT. To prevent dangerous operations and to ensure the system security, you can force the user to exit the LMT. 4.12.5 Setting the Status of Special NE User This describes how to set the status of the special NE user. The status of the non-default NE user is categorized into two types: Manageable and Lock. By setting the status, you can restrict the non-default users on login to the LMT and operation of the MML commands on the LMT. The non-default users are the local NE users except user admin and guest. 4.12.6 Forcing an OM User to Exit from the M2000 You can force an OM user to exit if the user performs dangerous operations or initiates illegal sessions. 4.12.7 Forcing an NE User to Exit from the LMT This describes how to force an NE user to log out the LMT. When an NE user performs dangerous operations and illegal session, you can force the user to exit from the LMT. 4.12.8 Unlocking an OM User If the number of times that a user enters an incorrect password reaches the number of the preset login attempts, the user account is locked. This section describes how to unlock an OM user. 4.12.9 Setting OM User Auto-Locking When an OM user logs in to the M2000 client, the system locks the interface if the number of wrong passwords exceed the maximum attempts, thus protecting the system from authorized operations.
4.12.1 User Operation Logs

User operation logs records the operations of the users. By analyzing user operation logs, you get to know the operations performed by users and easily locate the users. User operation logs falls into two categories: NM user operation logs and NE user operation logs. NM user operation logs records the information on the operations performed on the M2000 by OM users. NE user operation logs records the information on the operations performed by NE users.
4.12.2 User Sessions

A user session records the following information: login time, user group to which the user belongs, the terminal to which the user logs in, and the current status. You get to know what users have logged in to the system by monitoring the user session information. To ensure the security of the system, you can also force some users to exit from the system. When a user logs in to the M2000 through the M2000 client or through the LMT of an NE, the M2000 or the NE establishes a user session to record the login information.
User Session Types

For the categories and common examples of user sessions, see Table 4-4. Table 4-4 Examples of user sessions Session Type M2000 session Description The sessions on the M2000 consist of the sessions of OM users and the sessions of nonlocal users of the NodeB. Example
l
A user logs in to the M2000 through the M2000 client. A non-local user of the NodeB logs in to the NE through the LMT. The device file tool is enabled.
NE session
When an NE user (except a non-local user of NodeB) logs in to an NE through the LMT, a user session is established on the NE.
An NE user (except a nonlocal user of NodeB) logs in to an NE.
CAUTION
The BAM is not available for the NodeB. Therefore, when a non-local user of the NodeB logs in to the NodeB through the LMT, the user session information is stored on the M2000.
Restriction on User Sessions

The maximum number of sessions in the M2000 depends on the following three elements:
l
Login mode. In single-user login mode, only the admin user is allowed to log in to the M2000 through a client regardless of the value of Maximum Sessions.
Hardware condition. In some hardware conditions such as memory overflow, the user is not allowed to log in to the M2000.
ESN or license. Table 4-5 shows impact of ESN and license on Maximum Sessions. Table 4-5 Impact of ESN and license on Maximum Sessions Condition ESN is not matched or the license is invalid Maximum Session 3 Description If three users already log in through clients, no more user can log in. If the number of users who already log in is less than three, any other user can log in.
4-45
Issue 06 (2008-12-16)
Condition ESN is matched and the license is valid
Maximum Session The smaller number in the license and the specified value of Maximum Sessions.
Description If the number of current sessions exceeds the value set in Maximum Sessions but does not exceed the number in the license, the admin user can still log in to the M2000.
Monitoring User Sessions

l
On the User Monitor tab page in the User Monitor window, you can view the user sessions on the M2000, including the user sessions of OM users and the user sessions of the nonlocal users of NodeBs. For details, see 4.12.3 Monitoring Operation of OM Users on the M2000. You can view the user sessions on the Local Maintenance Monitor tab page in the User Monitor window. For details, see 4.12.4 Viewing Operation of NE Users.
4.12.3 Monitoring Operation of OM Users on the M2000

You can monitor the OM user sessions and operations to prevent illegal user operations.
Context
l l
The session is the connection between the M2000 client and the M2000 server. If a monitored user performs operations, the information in the operation monitoring list is updated in real time. After the M2000 server is restarted or the network is recovered after interruption, you need to click Refresh to refresh the session monitoring list.
Procedure
Step 1 Choose Security > User Monitor. The session information of the user is displayed in the Session Monitor area box in the User Monitor window. The session information includes user name, session state, login time, login terminal, and user group to which the user belongs.
NOTE
When the computer where the client is present installs multiple network cards, the Terminal value can be randomly taken from available IPs.
Step 2 In the User Monitor window, select a user from the session monitoring list. Operations of the selected user are displayed in the operation monitoring list.
NOTE
In the operation monitoring list, only the user's operations after the User Monitor window is activated are displayed.
Step 3 Click Filter at the bottom of the operation monitoring list.

Step 4 In the Filter dialog box, set Operation and Operation Object, and then click OK. The user operations that match the preset conditions are displayed in the operation monitoring list.
NOTE
l l
Before this step, you must insure there is at least one operation record in the operation monitoring list. If there is none operation record in the operation monitoring list, then it is null in the operation monitoring list after you do this step.
----End
Related Concepts
4.12.1 User Operation Logs 4.12.2 User Sessions
Related References
4.13.6 Interface Description: Viewing Operations of OM Users on the M2000
4.12.4 Viewing Operation of NE Users

This describes how to monitor the sessions and operations of the NE users on the LMT. In this way, you can familiarize yourself with whether the local NE user logs in to the LMT. To prevent dangerous operations and to ensure the system security, you can force the user to exit the LMT.
Context
l l
This function supports only A NEs. B/C NEs are not supported. Only the users logging in to the LMTs (the LMT started through the M2000 and the independently started LMT) are monitored. For the virtual NEs, the maintenance and monitoring function is not provided. If a monitored user performs operations, the information in the operation monitoring list is updated in real time. After the M2000 server is restarted or the network is recovered after interruption, you need to click Refresh to refresh the session monitoring list.
Procedure
Step 1 Choose Security > User Monitor. The User Monitor window is displayed. Step 2 Select the Local Maintenance Monitor tab, and then click Subscribe. Step 3 In the displayed Subscribed NE List, select the NEs for the monitoring. Click OK.
NOTE
After you subscribe the NEs, the sessions and operations of the user on the LMT are displayed in the Local Maintenance Monitor tab.
Step 4 Select a session record in the user session list. The user operation list displays all the operations of the selected user.
Step 5 Click Filter to set the filtering conditions. Only the session information that meets the requirements are displayed in the user session list. ----End
Related Concepts
Related References
4.13.7 Interface Description: Viewing Operations of NE Users
4.12.5 Setting the Status of Special NE User

This describes how to set the status of the special NE user. The status of the non-default NE user is categorized into two types: Manageable and Lock. By setting the status, you can restrict the non-default users on login to the LMT and operation of the MML commands on the LMT. The non-default users are the local NE users except user admin and guest.
Prerequisite
l l
The user has the relevant operation rights. The M2000 is connected to the LMT normally.
Procedure
Step 1 Click Security > Local Users Setting. The Local Users Setting window is displayed. Step 2 Select an NE type under the NE Type node. All the NEs of this type are displayed at the right window. Step 3 Set the status of the non-default NE user.
l
If you select Manageable, it indicates that the NE can be managed. That is, you can create, modify, or delete non-default NE users on the NEs. By default, the system selects Manageable. If you select Lock, it indicates that the login is inhibited. That is, other local NE users except the admin and guest cannot log in to the LMT. By default, the system selects Lock.
NOTE
You can select multiple NEs in the list. Right-click the list, select an option in the shortcut menu, and then the NEs are processed in batches.
----End
4.12.6 Forcing an OM User to Exit from the M2000

You can force an OM user to exit if the user performs dangerous operations or initiates illegal sessions.
4-48
Issue 06 (2008-12-16)
Context
l
The M2000 forces a user to exit only from the specific client in the session monitoring table. If the user has logged in to the M2000 from multiple clients (if possible), you need to repeat the operation to force the user to exit from all the clients. You cannot force your own user account to exit.
Procedure
Step 1 Choose Security > User Monitor. Step 2 From the session monitoring table, select a user name, and then click Force User to Exit. Step 3 In the Confirm dialog box, click Yes. ----End
4.12.7 Forcing an NE User to Exit from the LMT

This describes how to force an NE user to log out the LMT. When an NE user performs dangerous operations and illegal session, you can force the user to exit from the LMT.
Procedure
Step 1 Choose Security > User Monitor, the User Monitor window is displayed. Step 2 Click the Local Maintenance Monitor tab, and then choose the NE user in the NE session list.
CAUTION
For NodeBs, the information about non-local users is displayed on the User Monitor tab page. Step 3 Click Force User to Exit or right-click and choose Force User to Exit from the shortcut menu. Step 4 In the displayed Confirm dialog box, click Yes. ----End
4.12.8 Unlocking an OM User

If the number of times that a user enters an incorrect password reaches the number of the preset login attempts, the user account is locked. This section describes how to unlock an OM user.
Prerequisite
Only the admin and the members of Administrators can perform this operation.
Context
You can set the maximum login attempts and auto unlock time in the account policy.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management dialog box, expand the User root node. Right-click the user you want to unlock, and then select Unlock User. ----End
4.12.9 Setting OM User Auto-Locking

When an OM user logs in to the M2000 client, the system locks the interface if the number of wrong passwords exceed the maximum attempts, thus protecting the system from authorized operations.
Procedure
Step 1 Choose Security > Security Policy. The Security Settings dialog box is displayed. Step 2 Click the Account Policy node in the navigation tree. Then, enter the number of attempts in the Max. Login Attempts field and the automatic unlocking time in the Auto Unlock Time (minutes) field. By default:
l l
the value of Max. Login Attempts is three. The value of Auto Unlock Time(minutes) is 30 minutes.
Step 3 Click Apply. The automatic locking of the OM user is set. ----End
4.13 Reference for Security Management Interfaces

This part describes the security management interface and the parameters, which can help you perform the related operations. 4.13.1 Interface Description: NM Security Management The NM Security Management interface mainly manages the rights of OM users and user groups. 4.13.2 Interface Description: NE User Management Interface This describes the NE User Management interface and how to manage the authority of an NE user. 4.13.3 Interface Description: NE Login Management Interface This describes the function of associating an OM user with an NE user provided by the NE Login Management interface. 4.13.4 Interface Description: MML Authority Information of an OM User This describes how to grant the MML authority to a specified OM user on the Binded NE tab page. In this way, the user can perform all the commands in the command group. 4.13.5 Interface Description: Authority Rules for NE Type This describes how to grant the authority of several MML command groups of specified NE types to an OM user on the Rules tab page. In this way, you can create an authority rule. After
the authority rule is created, you can issue the rule to specific NEs. In this way, the OM user obtains the authority to the MML commands of the NEs. If the authority rule is successfully created, the OM user automatically has the authority to the MML commands of new NEs of this NE type. 4.13.6 Interface Description: Viewing Operations of OM Users on the M2000 This describes how to monitor the session of an OM user and how to prevent illegal operations on the User Monitor tab page. 4.13.7 Interface Description: Viewing Operations of NE Users This describes the Local Maintenance Monitor tab. This tab monitors the session of NE users. To avoid dangerous operations and ensure system safety, you can force a user to log out of the LMT. 4.13.8 Parameters for Adding an OM User Group This section describes the parameters in the Details tab. You can refer to these parameters when you add an OM user group. 4.13.9 Parameters for the Operation Authority of an OM User or an OM User Group This describes the parameters on the Operation Rights tab page for an OM user group or an OM user. You can refer to this part when you view the operation authority to an OM user group or an OM user. 4.13.10 Parameters for the MML Authority to an OM User Group or an OM User This describes the parameters for the MML command of an OM user group or an OM user. You can refer to this part when you perform the settings of the MML authority to an OM user group or an OM user. 4.13.11 Parameters for the Information of an OM User This describes the parameters on the Detail tab page. You can refer to this part when you view the basic information about an OM user. 4.13.12 Parameters for NE User This describes the parameters of NE users. You can refer to this part when you create an NE user. 4.13.13 Parameters for Creating an M2000 User Account This section describes the parameters in the Details tab. You can refer to these parameters when you add an M2000 user. 4.13.14 Parameters for Customizing an NE Command Group This describes the parameters shown in the Add Command Group dialog box. You can refer to this part when you customize an NE command group. 4.13.15 Parameters for the System Security Policy This section describes the parameters in the Security Settings window. You can refer to these parameters when you set the M2000 security policy. 4.13.16 Parameters for FTPS Parameter This describes the parameters in the FTPS Parameters Setting dialog box. You can refer to these parameters when you perform the related operations.
4.13.1 Interface Description: NM Security Management

The NM Security Management interface mainly manages the rights of OM users and user groups. This describes how to manage the authority of an OM user or an OM user group in the Security Management interface. The Security Management interface provides functions for managing
an OM user or an OM user group, such as creating an OM user and an OM user group and setting the authority to an OM user and an OM user group. The M2000 consists of three default user groups and one default user. The default user groups are Administrators, Guests, and Operators. The default user is admin. The Administrators user group and user admin have all the authorities. Select User/User Group node from the navigation tree. The list of OM users or OM user groups is displayed in the right pane. Select the specific user or user group node. The relevant information such as the management domain and operation authority of a user or a user group is displayed in the right pane. For details, refer to Figure 4-1. Figure 4-1 Security Management Interface
4.13.2 Interface Description: NE User Management Interface

This describes the NE User Management interface and how to manage the authority of an NE user. The NE User Management interface performs the function of managing an NE user. You can grant the authority of the MML command to a specified NE user. In this way, the user can run all the commands in the command group and view the public information about the NE user, such as user name and login time. Figure 4-2 shows the interface. For details about the Figure 4-2, refer to Table 4-6.
4-52
Issue 06 (2008-12-16)
Figure 4-2 NE User Management Interface
Table 4-6 NE User Management Interface Description No. 1 2 Description Root node. If you select this node, the right window displays the list of NE types. Choose the node and view the NE type list in the right pane. NE type node
shows the node structure of NodeB NEs.

l
For category A NEs, choose the node and you can view the authority policy of the created category A NEs. For category B/C NEs, choose the node and you can view NE type list in the right pane. For NodeB NEs, choose the node and you can view the subnode list and RNC NEs in the right pane.
Issue 06 (2008-12-16)
4-53
No. 3
Description Specific NE node

l
For category A NEs, select the node and you can view the information about the NE user and the MML commands that the user runs. For category B/C NEs, choose the node and you can view the NE user list in the right pane.
NE user node
l
For category A NEs, choose the node and you can view the information about the NE user and the NEs on which the user can run the MML commands. For category B/C NEs, choose the node and you can view the basic information about the user, such as user name, NE type, description, and NE user type.
Related Concepts
4.1.3 NE User
Related Tasks

This describes the function of associating an OM user with an NE user provided by the NE Login Management interface. You can perform the following operations in the NE Login Management interface: Associating an OM user with an NE user to obtain the authority to the NE user; deleting the association relationship to cancel the authority of the OM user. Select the NMS User node from the navigation tree. The names of created OM users are displayed in the right pane. Select the specific OM user node, the user information about associated NEs are displayed in the right pane. For details, refer to Figure 4-3. Figure 4-3 NE Login Management Interface
4-54
Issue 06 (2008-12-16)
Related Tasks
4.11.4 Associating OM User with NE User 4.11.5 Disassociating OM User with NE User
4.13.4 Interface Description: MML Authority Information of an OM User

This describes how to grant the MML authority to a specified OM user on the Binded NE tab page. In this way, the user can perform all the commands in the command group. As shown in Figure 4-4, after you select the OM user node from the navigation tree, the NE list on the Binded NE tab page displays the NEs on which the user can run the MML commands. After you choose an NE record in NE, the Associate Command Group displays the information about the associated command group. Figure 4-4 OM User Binded NE Tab
Related Concepts
Related Tasks
4.5.6 Granting MML Authority to an OM User Group 4.5.13 Grant MML Authority to an OM user 4.6.3.4 Modifying the MML Authority to an OM User 4.6.2.4 Modifying the MML Authority to an OM User Group
4.13.5 Interface Description: Authority Rules for NE Type

This describes how to grant the authority of several MML command groups of specified NE types to an OM user on the Rules tab page. In this way, you can create an authority rule. After the authority rule is created, you can issue the rule to specific NEs. In this way, the OM user
obtains the authority to the MML commands of the NEs. If the authority rule is successfully created, the OM user automatically has the authority to the MML commands of new NEs of this NE type. As shown in Figure 4-5, after you select an NE type node from the navigation tree, the information about the user who sets the authority rule of this NE type is displayed in the User dialog box. After you choose a user record in the User dialog box, the Command Group dialog box displays the information about the command group associated with the user. Figure 4-5 NE Type Rules Tab
Related Tasks
4.4.3 Setting Authority Rules for NE Types
4.13.6 Interface Description: Viewing Operations of OM Users on the M2000

This describes how to monitor the session of an OM user and how to prevent illegal operations on the User Monitor tab page. As shown in Figure 4-6, the session information about the user who have logged in to the M2000 is display in the Session Monitor dialog box. After you choose a session record in the Session Monitor dialog box, the operation information about the user is display in the Operation Monitor dialog box.
4-56
Issue 06 (2008-12-16)
Figure 4-6 OM User Monitor Tab
Related Concepts
Related Tasks
4.12.3 Monitoring Operation of OM Users on the M2000
4.13.7 Interface Description: Viewing Operations of NE Users

This describes the Local Maintenance Monitor tab. This tab monitors the session of NE users. To avoid dangerous operations and ensure system safety, you can force a user to log out of the LMT. As shown in Figure 4-7, the session information about the user who have logged in to the LMT is displayed in the User Session dialog box. After you choose a session record in User Session, the operation information about the user is display in Operation List.
Issue 06 (2008-12-16)
4-57
Figure 4-7 Local Maintenance MonitorTab
Related Concepts
Related Tasks
4.12.4 Viewing Operation of NE Users
4.13.8 Parameters for Adding an OM User Group

This section describes the parameters in the Details tab. You can refer to these parameters when you add an OM user group.
Parameters
Name Name Description Description: Name of the new user group. Settings Value: Value range: 1-20 characters. The name must be unique and cannot be null. In special characters, only underline can be contained in the name. The name cannot start with _private.
4-58
Issue 06 (2008-12-16)
Name Description
Description Description: A brief description of the user. It is used to distinguish user groups.
Settings Value: Value range: 0-100 characters. Setting method: Click Add to select users.
Member of User Group
Description: Users that are added to the user group.
Related Tasks
4.5.2 Creating an OM User Group

This describes the parameters on the Operation Rights tab page for an OM user group or an OM user. You can refer to this part when you view the operation authority to an OM user group or an OM user.
Parameter Operation Object Description The operation object on the M2000 comprises Network Management Application and Network Device.
l
Network Management Application: The authority of network management application mapping the M2000 does not involve specific network devices, such as creating a user and viewing network management logs. Network Device: The authority of network device mapping the M2000 involves specific NEs, such as viewing NE operation logs and downloading NE software.
Operation Description
Operations on the M2000 Description of the operations
Related Concepts
Related Tasks
4.5.4 Assigning Operation Rights to an OM User Group 4.5.10 Assigning Operation Rights to an OM User 4.6.3.2 Modifying the Operation Rights of an OM User 4.6.2.2 Modifying the Operation Rights of an OM User Group
4.13.10 Parameters for the MML Authority to an OM User Group or an OM User

This describes the parameters for the MML command of an OM user group or an OM user. You can refer to this part when you perform the settings of the MML authority to an OM user group or an OM user.
Parameter NE NE Type NE Description NE Type The NE name refers to the NEs on which an OM user group or an OM user can run the MML commands. IP address of an NE. Refers to the name of the group. Refers to the description information about a command group. Refers to the attribute of a command group. Indicates whether the group is a default command group or a custom command group.
l
NE IP Command Group Name Description Attribute
Based on the functions the MML commands, NEs divide a default command group into several command groups. The name of a default command group is in G_digit format.You are not allowed to modify the information about a default command group. You can customize a custom command group, for details, refer to 4.4.2 Customizing an NE Command Group. The name of a custom command group is in M_digit format.You can modify the information about a custom command group.
Related Concepts
Related Tasks
4.5.6 Granting MML Authority to an OM User Group 4.5.13 Grant MML Authority to an OM user
4.6.3.4 Modifying the MML Authority to an OM User 4.6.2.4 Modifying the MML Authority to an OM User Group

This describes the parameters on the Detail tab page. You can refer to this part when you view the basic information about an OM user.
Parameter User name Description Description Name of the OM user The description information about the OM user is used to distinguish different OM users. Value range: 0 to 100 characters Enable/Disable user account Enable or disable a user account
l
Enable a user account: You can use this account to log in to the M2000 client. Disable a user account: You are forced to log out the M2000 when you use this user account.
Valid From Valid To Valid Time
Start time that the user can log in to End time that the user can log in to Time that the user can log in to. For example, 00:00:00-23:59:59 Thursday, Friday, Sunday indicates that user login is permitted from 00:00:00 to 23:59:59 on each Thursday, Friday, and Saturday. Click and then set login time in the Login Duration dialog box.
Time Authorized to Change Password Password Expiry Time Locked Status User must change password next login
Time within which you can modify the user account and password. Time when the user account and password expires. Indicates that the user account is locked
l
No: Do not change the password when the user logs in next time. Yes: Change the password when the user logs in next time. Yes: User cannot change the password through the M2000 client. No: User can change the password through the M2000 client.
4-61
User can not change password
Issue 06 (2008-12-16)
Parameter Maximum password valid days
Description Valid day for password: The system password is valid within 180 days. You can click and change the maximum days for saving the password in the Maximum Valid Days dialog box.
Recent Successful Login Time Recent Date for Changing Password Login Status
The latest time when the user successfully logs in to the M2000 The recent date when the user changes the password The M2000 login status comprises Not Login and Login.
Related Tasks
4.6.4 Modifying the Information About an OM User 4.6.1 Viewing the Details of an OM User
4.13.12 Parameters for NE User

This describes the parameters of NE users. You can refer to this part when you create an NE user.
Parameters for Users of Category A NEs

For category A NEs, the NE user is the mapping OM user. For parameter description of this type, refer to 4.13.13 Parameters for Creating an M2000 User Account.
Parameters for Users of Category B/C NEs

Parameter NE Operation Click and choose the NEs whose users are to be added in the Select NE dialog box. The value range is as follows:
l
Description Name of the NEs whose users are to be added
NE User Name
Name of the NE user to be added
The value must be unique and cannot be null. A maximum of 100 characters. The user name can contain ".", capital letters, small letters, numbers , underscores and special characters other than `~!@#$%^&*()\":;?/\\,| {}[]<> \'+=-\t
Issue 06 (2008-12-16)
4-62
Parameter NE User Description
Operation The value range is as follows:

l l
Description The description information about the NE user is used to distinguish different NE users.
The value can be empty. A maximum of 100 characters.
Type of NE Users
Select an NE user type from a drop-down list box. Currently, only the Real NE User type is available. The value range is as follows:
l l
Type of NE users
Password
Password of new NE users
Case sensitive Not restricted by system password policy A maximum of 16 characters.
Empty password is not recommended. Confirm Password The value range is as follows:
l l
Case sensitive Not restricted by system password policy A maximum of 16 characters.
Enter a parameter again to ensure that the previously entered password is correct.
Related Concepts
4.1.3 NE User
Related Tasks
4.13.13 Parameters for Creating an M2000 User Account

This section describes the parameters in the Details tab. You can refer to these parameters when you add an M2000 user.
Issue 06 (2008-12-16)
4-63
Parameters
Name User Name Description Description: Name of the new user. Settings Value: The length of the user name can be neither less than Min. Length preset in the account policy nor greater than 32 characters. The user name can contain ".", capital letters, small letters, numbers and underscores. The name must be unique and cannot be left blank. The initial character cannot be a number or an underline. Description Description: A brief description of the user. It is used to distinguish users. Password Description: Password of the new user. The password must follow the system password policy. To view the policy, choose Security > Security Policy. Value: The description can contain 0-100 characters. Value: The length of the password of the admini user cannot be less than 8 characters. The length of the password of the non-admin user cannot be less than Min. Length preset in the password policy. The password is a character string and is case sensitive. Confirm Password Description: Enter the password again to ensure that the one you enter in is correct. Description: If this option is selected, you need to change the user password when you log in to the M2000 next time. Description: If this option is selected, you cannot change your password through the M2000 client. Description: If this option is selected, the user account is disabled. You are forced to log out when you use this account to log in to the M2000. Value: The value range is the same as the Password field. Setting method: Select or clear the check box.
User must change password next login User can not change password
Setting method: Select or clear the check box.
User account is disabled
4-64
Issue 06 (2008-12-16)
Name Use system maximum password valid days
Description Description: If this option is selected, you can set the validity period of the password.
Settings Setting method: Select or clear the check box. Value: Value: Default value: system password valid period (The system sets the value automatically based on the time set in Max.validity(days): in security settings.
Maximum password valid days
Description: The expiration date of a new password. If you have never changed the password, the count date starts from the creation date. If you selectUse system maximum password valid days, this parameter is disabled.
Value: Value range: 0-999, 0 for valid permanently. Default value: system password valid period (The system sets the value automatically based on the time set in Max.validity(days): in security settings.
Enable Period limit
Description: If the option is selected, the following options are all enabled. you can set the login duration.
Setting method: In the New User dialog box, clickLogin Duration. In the Login Duration dialog box, select Enable period limit check box. Value: Default value: creation date of the user. You can enter the value (DD/MM/ YYYY) or choose it from the time panel.
Start Date
Description: Start date when you can use this account to log in.
End date
Description: End date when you can use this account to log in.
Value: Default value: 31/12/2037 You can enter the value (DD/MM/ YYYY) or choose it from the time panel. Value: Default value: 00:00:00. Enter the time in the format of hh:mm:ss.
Daily Start Time
Description: The time works every day.
Issue 06 (2008-12-16)
4-65
Name Daily End Time
Description Description: The time works every day. It must be later than the daily start time.
Settings Value: Default value: 23:59:59. Enter the time in the format of hh:mm:ss. Setting method: Select or clear the check box.
Sun
Description: If the option is selected, you can log in from Start Date to End Date every Sunday.
Mon
Description: If the option is selected, you can log in from Start Date to End Date every Monday.
Tue
Description: If the option is selected, you can log in from Start Date to End Date every Tuesday.
Wed
Description: If the option is selected, you can log in from Start Date to End Date every Wednesday.
Thur
Description: If the option is selected, you can log in from Start Date to End Date every Thursday.
Fri
Description: If the option is selected, you can log in from Start Date to End Date every Friday.
Sat
Description: If the option is selected, you can log in from Start Date to End Date every Saturday.
Related Tasks
4.5.7 Creating an OM User Account
4.13.14 Parameters for Customizing an NE Command Group

This describes the parameters shown in the Add Command Group dialog box. You can refer to this part when you customize an NE command group.
4-66
Issue 06 (2008-12-16)
Parameter Name Value Range Select the name from the dropdown list.
l l
Description Refers to the name of the group. The name of a custom command group is in M_digit format.. Describes the function of a command group
Description
Not allowed to be null A string of less than 32 characters Letters, numbers, Chinese characters and underlines are acceptable.
Search by Name
None.
Used to search for the command words to be added to a command group. The query condition supports a non-case-sensitive fuzzy search. The query condition does not support wildcard. MML command.
Command
None.
Related Tasks
4.4.2 Customizing an NE Command Group

This section describes the parameters in the Security Settings window. You can refer to these parameters when you set the M2000 security policy.
Parameters
Name Password policy Max. password valid days Description Description: Validity period of the new password. If the password is not modified, the validity period starts from when the user is created. Description: Minimum days that a new password can be used after it is set. Settings Value: Value range: 0-999. Default value: 180. 0: No limit.
Min. password valid days
Value: Value range: 0-999. Default value: 10. 0: No limit.
Issue 06 (2008-12-16)
4-67
Name Min. Length
Description Description: Minimum length of the password. The password for admin cannot be less than eight characters. Min. Uppercase Description: Minimum uppercase letters in a password.
Settings Value: Value range: 7-16. Default value: 7.
Min. Lowercase
Description: Minimum lowercase letters in a password.
Min. Numbers
Description: Minimum numbers in a password.
Min. Special Characters
Description: Minimum special characters in a password. Special characters contain ~! @#$%^&*()_+-={}|\\:\";'?,./` and blank space.
4-68
Issue 06 (2008-12-16)
Name History Record (s)
Description Description: Number of history passwords kept in the M2000. The history passwords are kept from the latest. The new password cannot be the same as the history password.
Settings Value: Value range: 0-24. Default value: 24. 0: No limit. Example: For example, suppose the passwords you use from the latest are 111, 222, and 333.
l
When this parameter is set to 0, it means not to keep history passwords, and you can set the new password to be the same as the history password. When this parameter is set to 1, the system keeps the password 111, and you cannot set the new password to 111. When this parameter is set to 2, the system keeps the password 111 and 222, and you cannot set the new password to 111 or 222.
Advance reminder of password expiry (days) Cannot contain the same and consecutive character sequences Cannot contain ascending or descending character sequences
Description: Lead time for prompting password expiry. Description: A password cannot contain two same and consecutive character sequences. Description: A password cannot contain at least two ascending or descending characters sequence.
Value: Value range: 1-30. Default value: 10. Value: Value range: Enabled or Disabled. Default value: Disabled. Value: Value range: Enabled or Disabled. Default value: Disabled.
Issue 06 (2008-12-16)
4-69
Name Cannot contain part of the user name or the whole user name
Description Description: The password cannot contain part of or all of the user name characters.
Settings Value: Value range: All, Disabled, or 1-32. Default value: Disabled. The number indicates the minimum number of characters of a user name that cannot be contained in the related password.
Cannot contain a word in the password dictionary
Description: The password cannot be a word from the dictionary. The value Enabled indicates that the password cannot contain characters or strings in the password dictionary. The value Disabled indicates that the password can contain characters or strings in the password dictionary. Description: If the attempts to log in to the M2000 by a wrong password exceed this value, the account is locked. If you enter the correct password before the incorrect login attempts exceed the maximum, the M2000 clears the incorrect login records. Description:
Value: Value range: Enabled or Disabled. Default value: Disabled.
Account policy
Max. Login Attempts
Value: Value range: 1-99. Default value: 3.
Auto Unlock Time (minutes)
Value:
When a user account is locked Value range: 1-999. due to the login attempts Default value: 30. exceeding the Max.Login Attempts, it is unlocked after this time. Description: Minimum length of an M2000 user. Description: When the user does not log in for a specified period of time, the user account is deleted or hibernate. Value: Value range: 1-32. Default value: 6. Value: Value range: Hibernate or Delete. Default value: Hibernate.
Min. Length of User Name
Inactive User Policy
4-70
Issue 06 (2008-12-16)
Name System policy Maximum Sessions
Description Description: The total clients that can log in to the M2000. The maximum sessions are controlled by the M2000 licenses. If this parameter is set to more than the value controlled by the license, the total clients allowed to log in is the value controlled by the license.
Settings Value: Value range: 0-32767. Default value: 30. 0: No limit.
Related Tasks
4.3.1 Setting the M2000 Security Policy 4.3.1.1 Setting the Password Policy 4.3.1.2 Setting the Account Policy 4.3.1.3 Setting the System Policy
4.13.16 Parameters for FTPS Parameter

This describes the parameters in the FTPS Parameters Setting dialog box. You can refer to these parameters when you perform the related operations.
CAUTION
The settings of Command Port and Data Port modify only the FTP port number when the M2000 acts as the FTP client. The settings of the parameters for FTP transfer strategy, except Command Port and Data Port, are applicable only when the M2000 serves as the FTP client and the NE acts as the relay server. Parameter Value Range Description Encryption mode of the FTPS In the drop-down list, you can select the following modes:
l
Encrypted Mode
Select from the drop-down list.
Adapter Mode: automatically determines whether to use the encryption mode or the nonencryption mode of the SSL protocol. Plain Mode: uses the nonencryption mode.
4-71
Issue 06 (2008-12-16)
Parameter
Value Range
Description The mode to establish the FTPS connection. The mode can be active mode or passive mode.
l
Supported State

l
Active Mode: The FTP server launches an active connection request to the FTP client. The FTP client detects and determines whether the connection is set up. Passive Mode: The FTP client launches a passive connection request to the FTP server. The FTP server detects and determines whether the connection is set up.
In the drop-down list, you can select the following modes: Transmission Mode Select from the drop-down list.
l
Binary File: transferring files in binary mode ASCII File: transferring text files
Firewall Traversal Supported
Select from the drop-down list
You select whether to support firewall transversal or not. This parameter indicates the time intervals for FTPS transmission, that is, how long the system calculates the scheduling of file transmission. This value cannot be empty. The default value is the interval that the user sets previously. Indicates the number of the port that handles FTPS commands. This value cannot be empty. The default value is 21.
NOTE Port numbers smaller than 1024 are resources reserved by the system. Among the port numbers, only 21 can be set as the number of the command port.
Progress Interval (seconds)
0-90
Command Port
21, or 1024 to 65535
If you change the default port number, you must change the port number of the corresponding NE to maintain consistency.
4-72
Issue 06 (2008-12-16)
Parameter
Value Range
Description Indicates the number of the port that This value cannot be empty. The default value is 20.
NOTE Port numbers smaller than 1024 are resources reserved by the system. Among the port numbers, only 20 can be set as the number of the data port.
Data Port
20, or 1024 to 65535
If you change the default port number, you must change the port number of the corresponding NE to maintain consistency. Indicates the bytes of the transmission size. This value cannot be empty. The default value is the data transmission unit set last time. Indicates the minimum number of the port that allows listening. This value cannot be empty. Min. Port 10000-65535 This setting takes effect when Supported State is set to Active Mode. The default value is the minimum port number set last time. Indicates the maximum number of the port that allows listening. This value cannot be empty. Max. Port 10000-65535 This setting takes effect when Supported State is set to Active Mode. The default value is the maximum port number set last time.
Transmission Size (bytes)
1-32765
Related Concepts
Related Tasks
4.3.4 Setting FTPS Parameters
Issue 06 (2008-12-16)
4-73
5 Log Management
5
About This Chapter
Log Management
Log management involves the management of user logs, NE logs, and system logs. This function enables you to query logs and collect statistics of logs, thus helps monitoring and analyzing operational status of the system and troubleshooting. 5.1 Basic Knowledge of Log Management Before performing the operations related to log management, you need to be familiar with the basic information of logs, such as log types, log templates, and procedure for reporting NE logs. The basic log knowledge helps you understand the contents of log management. 5.2 Synchronizing NE Logs To obtain the latest logs, you need to synchronize the logs on the M2000 with those on NEs. The logs involved are NE operation logs and NE security logs. 5.3 Querying Logs You can use your authority to set query conditions. Then you can query log contents. You can sort log query results, print or save the results to files. 5.4 Taking Statistics of Logs You can quickly identify system operation status using this function. For example, you can identify which period contains most of users operations and what are the most commonly performed operations. 5.5 Managing Log Templates To simplify the query and log statistics operations, the M2000 provides the log template function. You can save the commonly used query and statistics conditions as a template. In this situation, you can directly load the template when you query or collect statistical information about logs. Using the function of log template management, you can create, modify, and delete a log template. 5.6 References for Log Management Interfaces This part describes reference information and the interface of log management. The contents in this part consist of the log management interface and parameters involved in the process of querying and taking statistics of NE logs, system logs, operation logs, and security logs. This helps you perform the operations related to log management.
Issue 06 (2008-12-16)
5-1
5 Log Management
5.1 Basic Knowledge of Log Management

Before performing the operations related to log management, you need to be familiar with the basic information of logs, such as log types, log templates, and procedure for reporting NE logs. The basic log knowledge helps you understand the contents of log management. 5.1.1 Log Types Logs can be categorized into operation logs, security logs, system logs, NE operation logs, and NE security logs. 5.1.2 Log Templates To facilitate log query and log statistics, the M2000 system provides the template management function. That means that you can save commonly used querying or statistical items to a template for future use. 5.1.3 Procedure for Reporting NE Logs NE logs must be uniformly reported to the M2000 client to achieve the synchronization. The procedure for reporting NE logs can be classified into two modes: using the FTP server and not using FTP server.
5.1.1 Log Types

Logs can be categorized into operation logs, security logs, system logs, NE operation logs, and NE security logs.
l
Operation logs record important operations performed, thus providing information for future reference. Security logs record those events related to system security, such as logging in to the M2000, modifying NM user authority, and adding NM users, thus helping monitor the operational status of the system. System logs record important events, such as running errors, network failures, and attacks against the system, thus facilitating troubleshooting. NE operation logs record those important operations performed on NEs, thus providing information for future reference. NE security logs record those events related to NE security, thus helping monitor the operational status of NEs.
5.1.2 Log Templates

To facilitate log query and log statistics, the M2000 system provides the template management function. That means that you can save commonly used querying or statistical items to a template for future use. Log templates are categorized into querying templates and statistical templates.
l
You can save all the querying or statistical settings of a specific type of logs into a template. Click Template Filter and choose Open. Then, you can view the query or statistics template you have set. The template contents is saved in the server and associated with the user. The contents of the templates are saved in the database of the server, and they are available only to their creators.
5-2

l l
5 Log Management
Each type of log template created by a user must have a unique name. The name contains a maximum of 40 characters and does not contain the following characters: ` ~ ! @ # $ % ^ & * ( ) \ " : ; ? | { } [ ] < > The system does not support automatic template refreshing. This means that if a user logs in to client A and modifies/deletes template A, template A remains unaltered when the user logs in to client B. You can close the template first, then open it again, and the system refreshes the information of the template.
5.1.3 Procedure for Reporting NE Logs

NE logs must be uniformly reported to the M2000 client to achieve the synchronization. The procedure for reporting NE logs can be classified into two modes: using the FTP server and not using FTP server. NE logs record important events happened on each NE. After filtering conditions are set, the required log information is recorded and reported to the relevant software management server. The NE log information is uniformly reported to the GUI. In this situation, the NE logs are synchronized. In this case, the NE acts as the FTP Server and the M2000 server acts as the FTP Client. The M2000 is always isolated from NEs by a firewall for sake of security, and only the basic maintenance channel is kept on the firewall. With the port defined by the company, the firewall is unlikely to be attacked. But for the port used by FTP service, the possibility is stronger. In this case, you can set a relay server and on the firewall, open only the FTP port of the relay server. Then the possibility of being attacked is reduced. Check whether the FTP server is used during the reporting of NE logs and divide the NE logs into the following two kinds:
l
Figure 5-1 shows the process for reporting NE logs through the FTP server.
Issue 06 (2008-12-16)
5-3
5 Log Management
Figure 5-1 Process for reporting NE logs through the FTP server
The process shown in Figure 5-1 is illustrated as follows: 1. The software management server obtains the information about synchronizing time. Then the server stores the information in the database and sends the generated log file command to NEs. The NEs report progress of the generated log file to the software management server.
2.
5-4
5 Log Management
3. 4.
The software management server reports the whole progress to the GUI for the first time. The software management server reports the whole progress to the GUI for the first time. The software management server obtains the user name and password through the FTP server and create a path for saving the created log files on the FTP server. The software management server sends the uploading commands of log files to NEs. After the NEs receive the commands, the NEs upload the log files to the FTP server and report the uploading progress of the log files to the software management server. The software management server reports the whole progress to the GUI for the second time. The software management server downloads the log files from the FTP server and then reports the whole progress to the GUI for the third time. The software management server resolves the log files to records and save the records to the database. The software management server reports the whole progress to the GUI for the fourth time.
5.
6. 7. 8. 9.
l
Figure 5-2 shows the process for reporting NE logs rather other through the FTP server.
Issue 06 (2008-12-16)
5-5
5 Log Management
Figure 5-2 Process for reporting NE logs rather than through the FTP server
The process shown in Figure 5-2 is illustrated as follows: 1. The software management server obtains the information about synchronizing time. Then the server stores the information in the database and sends the generated log file command to NEs. The NEs report progress of the generated log file to the software management server. The software management server reports the whole progress to the GUI for the first time. The software management server sends the uploading commands of log files to NEs. After the NEs receive the commands, the NEs upload the NE log files to the software management server and report the uploading progress of the log files. The software management server reports the whole progress to the GUI for the second time.
2. 3. 4.
5.
5-6
5 Log Management
6. 7.
The software management server resolves the log files to records and save the records to the database. The software management server reports the whole progress to the GUI for the third time.
5.2 Synchronizing NE Logs

To obtain the latest logs, you need to synchronize the logs on the M2000 with those on NEs. The logs involved are NE operation logs and NE security logs.
Prerequisite
l l
You have logged in to the M2000 client. The NEs must not be virtual NEs and they must be connected to the M2000.
Context
Class B and class C NEs do not support NE log synchronization.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 On the topology view of the system, right-click the NE and select Synchronize NE Operation and Security Logs on the shortcut menu. The Software Browser window displays the information on the synchronizing task. ----End
5.3 Querying Logs

You can use your authority to set query conditions. Then you can query log contents. You can sort log query results, print or save the results to files. 5.3.1 Creating a Log Query Template You can create a log query template to set query conditions. 5.3.2 Querying Operation Logs You can query operation logs to know the operation records of the M2000. 5.3.3 Querying System Logs You can query system logs to know the important events that occur when the M2000 is running. 5.3.4 Querying Security Logs You can query security logs to know the security operations of the M2000. 5.3.5 Querying NE Operation Logs NE operation logs record the operations performed by NE users. You can define the filtering conditions and query the desired logs. 5.3.6 Saving Log Query Results The task is performed to set conditions for querying required operation logs, security logs, NE logs, or system logs, and to save query results as files.
5 Log Management
5.3.7 Printing Log Query Results The task is performed to print query results of operation logs, security logs, NE logs, or system logs.
5.3.1 Creating a Log Query Template

You can create a log query template to set query conditions.
Context
The log query templates consist of operation log query template, system log query template, and security log query template. The procedures for creating these templates are similar. This section takes how to create an operation log query template as an example.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs . Step 2 In the Filter Condition window, click Cancel. Step 3 In the Query Operation Log window, click Template Filter and select New. Step 4 In the Enter The Template Name dialog box, define the name of the template, and then click OK. Step 5 In the Filter Condition window, set query conditions, and then click OK.
NOTE
If you want to modify the current query template, you can click Filter in the Query Operation Log window. In the Filter Condition window, modify the query conditions in the template, and then click OK. Click Template Filter, and then select Save to save the modified template, or select Save As to save the modified template as a new one.
----End
5.3.2 Querying Operation Logs

You can query operation logs to know the operation records of the M2000.
Context
l l l l
If the query conditions are not set, all operation logs are queried. If you have no right to query operation logs, you can only query your own operation logs. If you want to print the query result, you need to install a printer. The displayed query results are not updated in real time. In this case, you need click Refresh. The query result is based on the existing data of the database. If the database is empty, the query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs . Step 2 In the Filter Condition window, set the filter conditions, and then click OK.

NOTE
5 Log Management
You can also click Cancel, and then query logs in the Query Operation Log window in the following ways:
l l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. Click Filter. Set the query conditions and click OK to query logs.
In the Query Operation Log window, the query result is displayed. Step 3 Optional: Perform the following operations as required. l l l l In the Query Operation Log window, click Refresh to refresh the query result. In the Query Operation Log window, click Print to print the query result. In the Query Operation Log window, click Save As to save the query result. In the Query Operation Log window, select one record. Right-click to select Details. In the displayed Log Details dialog box, query the information about the log. Select Previous or Next, you can query the previous or the next log information. If you select multiple records, the Details menu turns grey.
----End
Related References
5.6.2 Parameters for Operation Log Details 5.6.12 Parameters for Querying Operation Logs
5.3.3 Querying System Logs

You can query system logs to know the important events that occur when the M2000 is running.
Context
l l l
If the query conditions are not set, all system logs are queried. If you want to print the query result, you need to install a printer. The displayed query results are not updated in real time. In this case, you need click Refresh. The query result is based on the existing data of the database. If the database is empty, the query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query System Logs . Step 2 In the Filter Condition window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query System Log window in the following ways:
l l
In the Query System Log window, the query result is displayed. Step 3 Optional: Perform the following operations as required. l
Issue 06 (2008-12-16)
In the Query System Log window, click Refresh to refresh the query result.
5 Log Management
l l l
In the Query System Log window, click Print to print the query result. In the Query System Log window, click Save As to save the query result. In the Query System Log window, select one record. Right-click to select Details. In the displayed Log Details dialog box, query the information about the log. Select Previous or Next, you can query the previous or the next log information. If you select multiple records, the Details menu turns grey.
----End
Related References
5.6.3 Parameters for System Log Details 5.6.13 Parameters for Querying System Logs
5.3.4 Querying Security Logs

You can query security logs to know the security operations of the M2000.
Context
l l l l
If the query conditions are not set, all security logs are queried. If you have no right to query security logs, you can only query your own security logs. If you want to print the query result, you need to install a printer. The displayed query results are not updated in real time. In this case, you need click Refresh. The query result is based on the existing data of the database. If the database is empty, the query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query Security Logs . Step 2 In the Filter Condition window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query Security Log window in the following ways:
l l
In the Query Security Log window, the query result is displayed. Step 3 Optional: Perform the following operations as required. l l l l In the Query Security Log window, click Refresh to refresh the query result. In the Query Security Log window, click Print to print the query result. In the Query Security Log window, click Save As to save the query result. In the Query Security Log window, select one record. Right-click to select Details. In the displayed Log Details dialog box, query the information about the log. Select Previous or Next, you can query the previous or the next log information. If you select multiple records, the Details menu turns grey.
----End
5 Log Management
Related References
5.6.4 Parameters for Security Log Details 5.6.14 Parameters for Querying Security Logs
5.3.5 Querying NE Operation Logs

NE operation logs record the operations performed by NE users. You can define the filtering conditions and query the desired logs.
Context
l l
If no query condition is specified, all operation logs are queried by default. If you have no authority to query operation logs of other NEs, you can query only your own operation logs. If you need print the query results, install the printer first. The displayed query results are not updated in real time. In this case, you need click Refresh Filter. The query results are based on the existing data in the database. If no data is generated or exported, no related information is displayed.
l l
Procedure
Step 1 Choose System > Log Management > Query NE Operation Log. Step 2 In the Filter Condition dialog box, set the filtering conditions.
NOTE
You can click Cancel and use either of the following methods to filter the query in NE operation log query.
l l
Click Template. Choose Open. Select a template in the list and click Open to use the existing template to filter the query. Click Filter. Set the query conditions and click OK.
For descriptions of the related parameters, refer to 5.6.15 Parameters for Querying NE Operation Logs. Step 3 Click OK. You can view the query results in NE operation log query. For descriptions of the parameters related to operation logs, refer to 5.6.5 Parameters for NE Operation Log Information.
NOTE
In the NE operation log query dialog box, you can perform the following operations:
l l l
Click Refresh to refresh the query results. Click Print to print the query results. Click Save As to save the query results to the local computer.
----End
Related References
5.6.5 Parameters for NE Operation Log Information 5.6.15 Parameters for Querying NE Operation Logs
5 Log Management
5.6.6 Parameters for NE Security Log Information 5.6.16 Parameters for Querying NE Security Logs 5.6.15 Parameters for Querying NE Operation Logs
5.3.6 Saving Log Query Results

The task is performed to set conditions for querying required operation logs, security logs, NE logs, or system logs, and to save query results as files.
Prerequisite
The required NE log, operation log, security log, or system log is queried.
Context
l
By default, the files are saved in the M2000 client installation directory. The first log record in the log file corresponds to the first record of the queried result, and the last log record corresponds to the last result record. Enter the filename, with .txt, .html, .xls, or .csv as the file format.
Procedure
Step 1 In the log query window, click Save As. Step 2 In the displayed Save dialog box, enter the name of the log file and select the file type. Step 3 Click Save. The displayed Save dialog box shows the saving progress. You can click Cancel to cancel the operation. ----End
5.3.7 Printing Log Query Results

The task is performed to print query results of operation logs, security logs, NE logs, or system logs.
Prerequisite
The required NE log, operation log, security log, or system log is queried.
Procedure
Step 1 In the log query window, click Print. Step 2 In the displayed Print dialog box, set the related parameters and then click Print. For descriptions of related parameters, refer to 3.9.14 Parameters for Printing a Topology View. ----End
5 Log Management
5.4 Taking Statistics of Logs

You can quickly identify system operation status using this function. For example, you can identify which period contains most of users operations and what are the most commonly performed operations. 5.4.1 Creating a Log Statistical Template You can create a log statistical template to set statistical conditions. The log statistical templates consist of operation log statistical template, system log statistical template, and security log statistical template. The procedures for creating these templates are similar. This section takes how to create an operation log statistical template an example. 5.4.2 Collecting Statistics on Operation Logs You can know the operation status by statisticing and analyzing the operation log. For example, at which period most operations are performed, and which operations are performed most frequently. 5.4.3 Collecting Statistics on System Logs You can know the system status by collecting statistics and analyzing the system log. For example, you can know which type of services raises the most alarms. 5.4.4 Collecting Statistics on Security Logs You can know the security operations by statisticing and analyzing the security log. For example, at which period most security operations are performed, and which operations are performed most frequently. 5.4.5 Taking Statistics of an NE Log This describes how to set conditions for making statistics on NE logs. You can quickly identify system operation status using this function. For example, you can identify which period contains most of users operations and what are the most commonly performed operations.
5.4.1 Creating a Log Statistical Template

You can create a log statistical template to set statistical conditions. The log statistical templates consist of operation log statistical template, system log statistical template, and security log statistical template. The procedures for creating these templates are similar. This section takes how to create an operation log statistical template an example.
Context
When you collect statistics on logs, you need to set statistical conditions. Statistical conditions can be set by creating a statistical template or setting statistical conditions in real time.
Procedure
Step 1 Choose System > Log Management > Statistic Operation Logs. Step 2 In the Filter Condition window, click Cancel. Step 3 In the Statistic Operation Log window, click Template Filter and select New. Step 4 In the Enter The Template Name dialog box, define the name of the template, and then click OK.
5 Log Management
Step 5 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
If you want to modify the current statistics template, you can click Statistic Filter in the Statistic Operation Log window. In the Filter Condition window, modify the statistical conditions in the template, and then click OK. Click Template Filter, and then select Save to save the modifications, or select Save As to save the modified template as a new one.
----End
5.4.2 Collecting Statistics on Operation Logs

You can know the operation status by statisticing and analyzing the operation log. For example, at which period most operations are performed, and which operations are performed most frequently.
Context
l l l
If a statistical item has no options, this statistical item is invalid. If you want to print the statistical result, you need to install a printer. The statistical result is based on the existing data of the database. If the database is empty, the statistical result is also empty.
Procedure
Step 1 Choose System > Log Management > Statistic Operation Logs. Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Statistic Operation Log window in the following ways:
l l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on operation logs. Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on operation logs.
In the Statistic Operation Log window, the statistical result is displayed. Step 3 Optional: Perform the following operations as required. l l In the Statistic Operation Log window, click Print to print the statistical result. In the Statistic Operation Log window, click Save As to save the statistical result.
----End
Related References
5.6.7 Parameters for Operation Log Statistics
5.4.3 Collecting Statistics on System Logs

You can know the system status by collecting statistics and analyzing the system log. For example, you can know which type of services raises the most alarms.
5 Log Management
Context
l l l
Procedure
Step 1 Choose System > Log Management > Statistic System Logs . Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Statistic System Log window in the following ways:
l l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on system logs. Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on system logs.
In the Statistic System Log window, the statistical result is displayed. Step 3 Optional: Perform the following operations as required. l l In the Statistic System Log window, click Print to print the statistical result. In the Statistic System Log window, click Save As to save the statistical result.
----End
Related References
5.6.9 Parameters for System Log Statistics
5.4.4 Collecting Statistics on Security Logs

You can know the security operations by statisticing and analyzing the security log. For example, at which period most security operations are performed, and which operations are performed most frequently.
Context
l l l
Procedure
Step 1 Choose System > Log Management > Statistic Security Logs. Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
Issue 06 (2008-12-16)
5-15
5 Log Management
NOTE
You can also click Cancel, and then collect statistics in the Statistic Security Log window in the following ways:
l l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on security logs. Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on security logs.
In the Statistic Security Log window, the statistical result is displayed. Step 3 Optional: Perform the following operations as required. l l In the Statistic Security Log window, click Print to print the statistical result. In the Statistic Security Log window, click Save As to save the statistical result.
----End
Related References
5.6.8 Parameters for Security Log Statistics
5.4.5 Taking Statistics of an NE Log

This describes how to set conditions for making statistics on NE logs. You can quickly identify system operation status using this function. For example, you can identify which period contains most of users operations and what are the most commonly performed operations.
Context
l l l
If a statistical item has no options, this statistical item is invalid. If you need print the query results, install the printer first. The statistical result is based on the existing data of the database. If no data is generated or exported, no related information is displayed.
Procedure
Step 1 Choose System > Log Management and select the logs to collect the statistics. Step 2 In the Filter Condition dialog box, set Statistical Items and Filter Condition.
NOTE
You can click Cancel and use either of the following methods to filter the statistics of NE logs.
l l
Click Template. Choose Open. Select a template in the list and click Open to use the existing template to collect statistics of NE logs.. Click Statistic Filter. Set Statistical Items and Filter Condition, and then click OK to collect statistics of NE logs.
For information about statistical items of NE operation logs and security logs, refer to 5.6.10 Parameters for Statistics of an NE Operation Log and 5.6.11 Parameters for Statistics of an NE Security Log respectively. For descriptions of filtering conditions, refer to Parameters for Filter Condition of NE Operation Log Statistics and Parameters for Filter Condition of NE Security Log Statistics. Step 3 Click OK. Then you can view the statistical results in the log statistics window.

NOTE
5 Log Management
In the log statistics dialog box, you can perform the following operations:
l l
Click Print to print the statistical results. Click Save As to save the statistical results to the local computer.
----End
Related References
5.6.10 Parameters for Statistics of an NE Operation Log 5.6.11 Parameters for Statistics of an NE Security Log
5.5 Managing Log Templates

To simplify the query and log statistics operations, the M2000 provides the log template function. You can save the commonly used query and statistics conditions as a template. In this situation, you can directly load the template when you query or collect statistical information about logs. Using the function of log template management, you can create, modify, and delete a log template. 5.5.1 Creating Log Templates You can set conditions for log query and statistics by creating log templates. The log templates are used to simplify the process for querying logs and of collecting log statistics. 5.5.2 Modifying Log Template Condition After a log template is created, you can modify query or statistical conditions of the template. 5.5.3 Deleting Log Template You can delete an unneeded log template.
Related Concepts
5.1.2 Log Templates
5.5.1 Creating Log Templates

You can set conditions for log query and statistics by creating log templates. The log templates are used to simplify the process for querying logs and of collecting log statistics.
Prerequisite
l l
You have logged in to the M2000 client. You have the privilege for log management.
Context
You need to set conditions for log query and log statistics collect before you perform these operations. Two ways are available for setting conditions for log query or log statistics collection. They are creating query or statistics template, and setting query or statistics conditions in real time. The templates of the following logs are created in the same way:
5 Log Management
l l l l l
operation logs system logs security logs NE operation logs NE security logs
Procedure
Step 1 Choose System > Log Management and select the log whose template is to be added. Step 2 In the displayed Filter Condition dialog box, click Cancel. Step 3 Click Template Filter, and then select New from the drop-down list. Step 4 Enter the name of the template. Click OK.
l
The name contains a maximum of 40 characters and does not contain the following characters: ` ~ ! @ # $ % ^ & * ( ) \ " : ; ? | { } [ ] < > For each user, the template name for the same type of logs is unique.
Step 5 In the displayed Filter Condition condition, set filter conditions for log query or log statistics collection. Different type of logs have different filter conditions. You can set filter conditions based on actual requirements. Step 6 Click OK. ----End
Result
The results of log query or log statistics collection are displayed in the log window. The system displays the new log templates in the following ways:
l
Click Template Filter in the log window. The list displays the name of the new log template. Click Template Filter in the log window. Select Open from the drop-down list. The name of the new log template is displayed in the list.
Related Concepts
5.1.2 Log Templates
5.5.2 Modifying Log Template Condition

After a log template is created, you can modify query or statistical conditions of the template.
Prerequisite
l l
Context
You have the privilege for log management.

l l l l l
5 Log Management
Procedure
Step 1 Choose System > Log Management and select the log whose template is to be modified. Step 2 In the displayed Filter Condition dialog box, click Cancel. Step 3 Click Template Filter, and then select Open from the drop-down list. Step 4 In the displayed Open dialog box, select the log template to be modified. Click Open. The results of log query or log statistics collection are displayed in the log window. Step 5 Click Filter. Step 6 In the displayed Filter Condition dialog box, modify the filter conditions of log query or log statistics collection. Then, click OK. Step 7 Click Template Filter, and then select Save As from the drop-down list. ----End
5.5.3 Deleting Log Template

You can delete an unneeded log template.
Prerequisite
l l
Context
You can delete the following logs by using the same method:
l l l l l
Procedure
Step 1 Choose System > Log Management and select the log whose template is to be deleted. Step 2 In the displayed Filter Condition dialog box, click Cancel. Step 3 Click Template Filter, and then select Delete from the drop-down list.
5 Log Management
Step 4 In the displayed Delete dialog box, select the log template to be deleted. Click Delete. Step 5 In the Confirm dialog box, click Yes. The template deleted is also removed from the template list in the Delete dialog box. Step 6 Click Cancel. The Delete dialog box is closed. ----End
5.6 References for Log Management Interfaces

This part describes reference information and the interface of log management. The contents in this part consist of the log management interface and parameters involved in the process of querying and taking statistics of NE logs, system logs, operation logs, and security logs. This helps you perform the operations related to log management. 5.6.1 Interface Description: Log Management This part describes the log management interface. You can have an understanding of each part on the log management interface and their functions. 5.6.2 Parameters for Operation Log Details This section describes the parameters of the query result displayed in the Query Operation Log window. 5.6.3 Parameters for System Log Details This section describes the parameters of query result displayed in the Query System Log window. 5.6.4 Parameters for Security Log Details This section describes the parameters of query result displayed in the Query Security Logs window. 5.6.5 Parameters for NE Operation Log Information This part provides a detailed explanation of the parameters related to NE operation logs, thus providing a reference for checking the query results. 5.6.6 Parameters for NE Security Log Information This part provides a detailed explanation of the parameters related to NE security logs, thus providing a reference for checking the query results. 5.6.7 Parameters for Operation Log Statistics This section describes the parameters of statistic condition. You can refer to these parameters when you collect statistics on operation logs. 5.6.8 Parameters for Security Log Statistics This section describes the parameters of statistic condition. You can refer to this section when you collect statistics on security logs. 5.6.9 Parameters for System Log Statistics This section describes the parameters of statistic condition. You can refer to these parameters when you collect statistics on system logs. 5.6.10 Parameters for Statistics of an NE Operation Log This part describes the items set in the Filter Condition dialog box. Refer to this part when you set items for collecting statistics on NE operation logs. 5.6.11 Parameters for Statistics of an NE Security Log
5 Log Management
This part describes the items set in the Filter Condition dialog box. Refer to this part when you set items for collecting statistics on NE security logs. 5.6.12 Parameters for Querying Operation Logs This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query operation logs. 5.6.13 Parameters for Querying System Logs This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query system logs. 5.6.14 Parameters for Querying Security Logs This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query security logs. 5.6.15 Parameters for Querying NE Operation Logs This part describes the parameters in the Filter Condition dialog box. Refer to this part when you query or collect statistics on NE operation logs. 5.6.16 Parameters for Querying NE Security Logs This part provides a detailed explanation of the parameters related to querying NE security logs, thus providing a reference for future query.
5.6.1 Interface Description: Log Management

This part describes the log management interface. You can have an understanding of each part on the log management interface and their functions. For details about the interfaces for log query or log statistics collection, refer to Figure 5-3. After the filter conditions are set, the results of log query or log statistics collection are displayed in the log window. You can save or print the results by clicking the buttons on the interface. Figure 5-3 Log management interface
Issue 06 (2008-12-16)
5-21
5 Log Management
5.6.2 Parameters for Operation Log Details

This section describes the parameters of the query result displayed in the Query Operation Log window.
Parameters
Name Operation Description Description: Name of user operations, such as add, delete, and browse. User Description: Name of the user who performs the operation. User Type Description: Type of the user who performs the operation. Start Time Description: Start time of the operation. The format is consistent with that in region settings, such as YYYY-MM-DD hh:mm:ss. End Time Description: End time of the operation. The format is consistent with that in region settings, such as YYYY-MM-DD hh:mm:ss. Category Description: To identify different types of operations, such as log, topology, and remote notification. Terminal Description: To identify clients in IP addresses. Operation Object Description: Operation objects, such as the M2000. Result Description: To indicate whether the operation is successful, including Succeeded, Failed, Canceled, Partly succeeded, and Uncompleted. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned. Details Description: Details of operation logs.
Related Tasks
5-22
Issue 06 (2008-12-16)
5 Log Management
5.6.3 Parameters for System Log Details

This section describes the parameters of query result displayed in the Query System Log window.
Parameters
Name Level Description Description: There are three levels for system logs: Error, Warning, and Info. Source Description: The log IDs of the subsystems of the M2000 are alarm management, system management, and security management. Time Description: The date and time when the system log is recorded. The format is consistent with that in region settings, such as YYYY-MM-DD hh:mm:ss. Basic Information Details Description: The basic information of system logs. For example: start service. Description: Details of system logs.
Related Tasks
5.6.4 Parameters for Security Log Details

This section describes the parameters of query result displayed in the Query Security Logs window.
Parameters
Name Security Event Description Description: To query by security events. Event Level Description: To query by event levels. User Description: Name of the user who performs the operation. User Type Description: Type of the user who performs the operation.
5 Log Management
Name Start Time
Description Description: Start time of the operation. The format is consistent with that in region settings, such as YYYY-MM-DD hh:mm:ss.
End Time
Description: End time of the operation. The format is consistent with that in region settings, such as YYYY-MM-DD hh:mm:ss.
Event Type
Description: Type of the event.
Terminal
Description: To identify clients in IP addresses.

NOTE During the initialization of the M2000 server installation, the terminal IP address corresponding to the operations performed by using scripts or commands is 1.1.1.1 displayed in security logs.
Operation Object
Description: Operation objects, such as the M2000
Result
Description: To indicate whether the operation is successful, including Succeeded, Failed, Canceled, Partly succeeded, and Ongoing. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned.
Details
Description: Details of security logs.
Related Tasks
5.6.5 Parameters for NE Operation Log Information

This part provides a detailed explanation of the parameters related to NE operation logs, thus providing a reference for checking the query results. For details of the parameters related to NE operation logs, refer to Table 5-1. Table 5-1 Parameters related to NE operation logs Parameter User User Type Terminal
5-24
Description Name of the NE user that carries out a specific operation Domain attribute of the user, such as EMS, Local, and EMSOP IP address of the terminal on which the operation is performed
5 Log Management
Parameter Start Time
Description Start time of the operation The format complies with 1.4.5.1 Setting the Time Format of the Client and1.4.5.3 Setting the Date Format of the Client in the region settings, such as YYYY-MM-DD HH:MM:SS.
End Time
End time of the operation The format complies with 1.4.5.1 Setting the Time Format of the Client and 1.4.5.3 Setting the Date Format of the Client in the region settings, such as YYYY-MM-DD HH:MM:SS.
Result
Result of the operation The result is Succeeded or Failed.
MML Message NE Type NE Name
MML commands for performing operations on an NE Details of the operation Type of the NE Name of the NE
Related Tasks
5.6.6 Parameters for NE Security Log Information

This part provides a detailed explanation of the parameters related to NE security logs, thus providing a reference for checking the query results. For details of the parameters related to NE security logs, refer to Table 5-2. Table 5-2 Parameters Related to NE security logs Parameter User User Type Terminal Security Level Created Time Result Security Event Message NE Type
Issue 06 (2008-12-16)
Description Name of the NE user that carries out a specific operation Domain attribute of the user, such as EMS, Local, and EMSOP. IP address of the terminal on which the operation is performed Class of a security event to be queried, such as urgent, important, and subordinate. Time when the security event occurs Whether the operation is successful or fails Details of the security event Details of the operation Type of the NE
5 Log Management
Parameter NE Name
Description Name of the NE
Related Tasks
5.6.7 Parameters for Operation Log Statistics

This section describes the parameters of statistic condition. You can refer to these parameters when you collect statistics on operation logs.
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Settings Setting method: You can select up to two statistical items. The statistical results are sorted according to the statistical items. Setting method: Value: The parameters include None, User, User Type, Operation, Category, Terminal, Result, and Operation Object. Setting method: Drop-down list Example Description: Preview the style of the statistical result table. Value: -
Statistic Column
Description: Set the column heading of the statistical result table.
Statistic Item
Description: Set the row heading and column heading of the statistical result table.
Filter condition
Name User Description Description: To collect statistics by user. Settings Setting method: Click . From the User Select dialog box, select one or more items.
5-26
Issue 06 (2008-12-16)
5 Log Management
Name Terminal
Description Description: To collect statistics by terminal.
Settings Setting method: Click . From the Terminal Select dialog box, select one or more items. Setting method: From Results, select one or more items.
Result
Description: To collect statistics by operation result. The operation result involves:

l
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned. Canceled means the operation is canceled. Setting method: Select From and To to enter the date and time directly, or and set the time in click the Date/Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Time Range
Description: To collect statistics by time range. From means the start time, and To means the end time.
Operation
Description: To collect statistics by operation.
Setting method: Click corresponding to Operation. From the Operation Select dialog box, select one or more items.
Issue 06 (2008-12-16)
5-27
5 Log Management
Name Operation Object
Description Description: To collect statistics by operation object.
Settings Setting method: Click corresponding to Operation Object. From the Operation Object Select dialog box, select one or more items.
Related Tasks
5.4.2 Collecting Statistics on Operation Logs
5.6.8 Parameters for Security Log Statistics

This section describes the parameters of statistic condition. You can refer to this section when you collect statistics on security logs.
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Settings Setting method: You can select up to two statistical items. The statistical results are sorted according to the statistical items. Setting method: Value: The parameters include None, User, User Type, Security Event, Event Type, Terminal, Result, Operation Object, and Event Level. Setting method: Drop-down list Example Description: Preview the style of the statistical result table. Value: -
Statistic Column
Description: Set the column heading of the statistical result table.
Statistic Item
Description: Set the row heading and column heading of the statistical result table.
5-28
Issue 06 (2008-12-16)
5 Log Management
Filter condition
Name User Description Description: To collect statistics by user. Settings Setting method: Click . From the User Select dialog box, select one or more items. Setting method: Click . From the Terminal Select dialog box, select one or more items. Setting method: From Result, select one or more items. All the options are selected by default.
Terminal
Description: To collect statistics by terminals.
Result
Description: To collect statistics by operation result. The operation result involves:

l
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned. Canceled means the operation is canceled. Setting method: From the Event Level group box, select one or more items. All the options are selected by default.
Event Level
Description: To collect statistics by event levels.
Issue 06 (2008-12-16)
5-29
5 Log Management
Name Time Range
Description Description: To collect statistics by time range. From means the start time, and To means the end time.
Settings Setting method: Select From and To to enter the date and time directly, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Security Event
Description: To collect statistics by security events.
Setting method: Click corresponding to Security Event Select. From the Security Event dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Operation Object Select dialog box, select one or more items.
Operation Object
Description: To collect statistics by operation object.
Related Tasks
5.4.4 Collecting Statistics on Security Logs
5.6.9 Parameters for System Log Statistics

This section describes the parameters of statistic condition. You can refer to these parameters when you collect statistics on system logs.
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Statistic Column Description: Set the column heading of the statistical result table. Settings Setting method: Setting method: -
5-30
Issue 06 (2008-12-16)
5 Log Management
Name Statistic Item
Description Description: Set the row heading and column heading of the statistical result table.
Settings Value: The parameters include None, Level, and Source. Setting method: Drop-down list
Example
Description: Preview the style of the statistical result table.
Value: -
Filter condition
Name Sources Description Description: To collect statistics by log source. Settings Setting method: Click . From the Sources Select dialog box, select one or more items. Setting method: From the Level group box, select one or more items. Setting method: Select From and To to enter the date and time directly, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Level
Description: To collect statistics by log level.
Time Range
Description: To collect statistics by time range. From means the start time, and To means the end time.
Related Tasks
5.4.3 Collecting Statistics on System Logs
5.6.10 Parameters for Statistics of an NE Operation Log

This part describes the items set in the Filter Condition dialog box. Refer to this part when you set items for collecting statistics on NE operation logs.
Issue 06 (2008-12-16)
5-31
5 Log Management
Parameter User Result NE NE Type Terminal User Type Description Name of the user that performs the operation. Result of the operation. There are two types: succeeded and failed. Name of the operated NE. Type of the operated NE. Identified by IP address. Identifies the domain attribute of the user in the NE operation log, including EMS, Local and SMSOP.
Related Tasks
5.6.11 Parameters for Statistics of an NE Security Log

This part describes the items set in the Filter Condition dialog box. Refer to this part when you set items for collecting statistics on NE security logs.
Parameter User Result NE NE Type Terminal User Type Security Level Description Name of the user that performs the operation. Result of the operation. There are two types: succeeded and failed. Name of the operated NE. Type of the operated NE. Identified by IP address. Identifies the domain attribute of the user in the NE security log, including EMS, Local and EMSOP. Specifies the level of security events to query. There are three types: critical, major, and minor.
Related Tasks
5.6.12 Parameters for Querying Operation Logs

This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query operation logs.
5-32
Issue 06 (2008-12-16)
5 Log Management
Parameters
Name User Description Description: To query by user. Settings Setting method: Click . From the User Select dialog box, select one or more items. Setting method: Click . From the Terminal Select dialog box, select one or more items. Setting method: From the Result group box, select one or more items.
Terminal
Description: To query by terminal.
Result
Description: To query by operation result. The operation result involves:

l
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned. Canceled means the operation is canceled. Setting method: Select From and To, and then enter the date and time in the text box, or click and set the time in the Date/ Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Time Range
Description: To query by time range. From means the start time, and To means the end time.
Issue 06 (2008-12-16)
5-33
5 Log Management
Name Operation
Description Description: To query by operation.
Settings Setting method: Click corresponding to Operation. From the Operation Select dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Operation Object Select dialog box, select one or more items.
Operation Object
Description: To query by operation objects.
Related Tasks
5.6.13 Parameters for Querying System Logs

This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query system logs.
Parameters
Name Source Description Description: To query by log source. Settings Setting method: Click . From the Source Select dialog box, select one or more items. Setting method: From the Level group box, select one or more items. Setting method: Select From and To to enter the date and time directly, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Level
Description: To query by log level.
Time Range
Description: To query by time range. From means the start time, and To means the end time.
5-34
Issue 06 (2008-12-16)
5 Log Management
Related Tasks
5.6.14 Parameters for Querying Security Logs

This section describes the parameters in the Filter Condition dialog box. You can refer to these parameters when you query security logs.
Parameters
Name User Description Description: To query by user. Settings Setting method: Click . From the User Select dialog box, select one or more items. Setting method: Click . From the Terminal Select dialog box, select one or more items. Setting method: From Result, select one or more items.
Terminal
Description: To query by terminals.
Result
Description: To query by operation result. The operation result involves:

l
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned. Uncompleted means the operation is being carried out, the result is not returned. Canceled means the operation is canceled. Setting method: From the Event Level group box, select one or more items.
Event Level
Description: To query by event levels.
Issue 06 (2008-12-16)
5-35
5 Log Management
Name Time Range
Description Description: To query by time range. From means the start time, and To means the end time.
Settings Setting method: Select From and To to enter the date and time directly, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to "2002-02-09 00:00:00 2003-02-09 00:00:00".
Security Event
Description: To query by security events.
Setting method: Click corresponding to Security Event. From the Security Event Select dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Operation Object Select dialog box, select one or more items.
Operation Object
Description: To query by operation objects.
Related Tasks
5.6.15 Parameters for Querying NE Operation Logs

This part describes the parameters in the Filter Condition dialog box. Refer to this part when you query or collect statistics on NE operation logs. For details of the parameters related to querying NE operation logs, refer to Table 5-3. Table 5-3 Parameters for querying NE operation logs Query Condition User Terminal Description Queries by user. Queries by terminal. Setting Click . Select one or more items from the User Select dialog box. Click . Select one or more items from the Terminal Select dialog box.
5-36
Issue 06 (2008-12-16)
5 Log Management
Query Condition User Types
Description Queries by user type The user type falls into the Local, the EMS, and the EMSOP categories.
Setting Select one or more items from the User Types group box.
Result
Queries by operation results. The results are either Succeeded or Failed.
Select one or more items from the Result group box.
Time Range
Queries by time range From indicates the start time, while To indicates the end time.
Select From and To, and enter the date and time in the text box. Alternatively, click . In the Date/ Time Selection dialog box, set the date and the time. For instance, set the time range to 2002-02-09 00:00:00 2003-02-09 00:00:00.
NE Name
Queries by NE
Click Choose located at the lower part of NE Name. Select one or more items from the NE Name: Select dialog box.
Related Tasks
5.3.5 Querying NE Operation Logs 5.3.5 Querying NE Operation Logs
5.6.16 Parameters for Querying NE Security Logs

This part provides a detailed explanation of the parameters related to querying NE security logs, thus providing a reference for future query. For details of the parameters related to querying NE security logs, refer to Table 5-4. Table 5-4 Parameters for querying NE security logs Query Condition User Terminal User Types Description Queries by user. Queries by terminal. Queries by user type The user type falls into the Local, the EMS, and the EMSOP categories. Setting Click . Select one or more items from the User Select dialog box. Click . Select one or more items from the Terminal Select dialog box. Select one or more items from the User Types group box.
Issue 06 (2008-12-16)
5-37
5 Log Management
Query Condition Result
Description Queries by operation results. The results are either Succeeded or Failed.
Setting Select one or more items from the Result group box.
Security Levels
Collects statistics by security level The security levels are Urgent, Important, and Subordinate. Collecting statistics by time range From indicates the start time, while To indicates the end time.
Select one or more items from the Security Levels group box.
Time Range
Select From and To, and enter the date and time in the text box. Alternatively, click . In the Date/ Time Selection dialog box, set the date and the time. For instance, set the time range to 2002-02-09 00:00:00 2003-02-09 00:00:00.
NEs
Collecting statistics by NE
Click Choose located at the lower part of NE Name. Select one or more items from the NE Name: Select dialog box.
Related Tasks
5-38
Issue 06 (2008-12-16)
6 Performance Management
6
About This Chapter
Performance Management
Through the performance measurement, you can measure and observe the security, the running status and the signaling connection status of the equipment, also you can measure and observe the utilization of the user and system resources. This function provides reliable data support for the measurement, designing and operation management of the communication network. The M2000 can measure the performance of multiple NEs. When an NE is successfully set up and communicates normally with the M2000, the NE automatically reports the measurement results of key performance counters to M2000 for data query and analysis based on a certain period. 6.1 Basic Knowledge of Performance Management This topic describes the basic knowledge of performance management. Before you perform the related operations, you need know some basic knowledge about the performance, such as measurement counters, measurement objects, function sets and function subsets, measurement periods, counter thresholds, measurement status and measurement processes. 6.2 Monitoring NE Performances You can set NE performance measurement range and query performance measurement results. In addition, you can synchronize and subscribe to NE measurement results, query missing measurement results, and manage NE measurement states. 6.3 Querying Performance Measurement Results This task is performed to query performance measurement results. Two query modes, that is, by template and by new conditions, are available. 6.4 Managing Measurement Objects Through measurement object management, you can search for counters and objects. You can also export and import measurement settings information. 6.5 Managing User-Defined Counters The user-defined counter management involves two types of counters: system counters and userdefined counters. The system counter is obtained when the system performs the arithmetic operation on the original counters in the system by default. It is attached to the system. When the M2000 is running, you can perform a arithmetic operation on the original system counters to obtain a new measurement counter. The counter generated in this way is called the userdefined counter. The user-defined counters apply only to the periodic measurement results. A user-defined counter is measured only when all the original counters contained in the formula
are measured. If an original counter is not measured, the user-defined counter cannot be measured. 6.6 Managing Counter Thresholds During different periodic measurement, the M2000 provides the counter value threshold alarm to automatically monitor key performance counters and currently measured extension counters. You can set the alarm threshold of every periodic measurement based on actual situations including setting the simple alarm threshold for a single counter and for the combined counters after logic or arithmetic operations. 6.7 Reference for Performance Management Interfaces This part describes the following interfaces of performance management: query result interface, measure management interface, threshold management interface, customer counter interface, and Performance Monitor interface.
6-2
Issue 06 (2008-12-16)
6.1 Basic Knowledge of Performance Management

This topic describes the basic knowledge of performance management. Before you perform the related operations, you need know some basic knowledge about the performance, such as measurement counters, measurement objects, function sets and function subsets, measurement periods, counter thresholds, measurement status and measurement processes. 6.1.1 Performance Measurement Counters Performance measurement counter is a basic unit for the performance measurement. It defines what to measure. 6.1.2 Performance Measurement Objects This describes the performance measurement objects. A measurement object can be the physical concept of boards or subracks, or the logical concepts of cells. A certain corresponding relation exists between the measurement objects and the measurement counters. Each measurement object corresponds to some measurement counters. That is, the measured object has some specified measurement items. The measurement counters depend on the measurement objects. 6.1.3 Measurement Function Sets and Subsets The M2000 system involves large quantities of measurement counters. For better management, the measurement counters are categorized. 6.1.4 Performance Measurement Periods This describes the concepts pertaining to performance measurement periods. 6.1.5 Performance Measurement Results This describes the concept of performance measurement results. 6.1.6 Performance Counter Thresholds This topic describes the concept of performance counter thresholds. The performance threshold is used to monitor the actual measurement result of the performance counter. When the value of the measurement result exceeds that set by the user, the system generates an alarm. The threshold value of the performance counter can be the threshold value of a specific performance counter or the threshold value of the combined performance counters. 6.1.7 Performance Measurement States This describes the concept of performance measurement states. 6.1.8 Performance Measurement Procedure This describes the M2000 performance measurement procedure, which consists of reporting, saving, and viewing performance data.
6.1.1 Performance Measurement Counters

Performance measurement counter is a basic unit for the performance measurement. It defines what to measure.
Category
Based on the source, measurement counters fall into the following two categories:
l
The default counters, also called system counters, are defined by NEs. The NE periodically reports the measurement results of all default performance counters to the M2000. The default performance counters consist of common counters and extended counters.
Issue 06 (2008-12-16)
l
Counters defined on the M2000 client, that is, user-defined counters.
Operations are designed separately for these two categories of counters.
Common Counter
Common counters refer to the key counters defined for an NE. The NE periodically reports the measurement results of all these counters to the M2000, and the M2000 saves the results to the performance database for future queries. You can clear common counters.
Extended Counter
Extended counters are also counters defined for an NE. The NE reports the results of the selected extended counters to the M2000.The M2000 determines whether to save the result to the M2000 performance database based on the user selection. During the operation of the M2000, you can select or deselet the extended counters.
l
When you select an extended counter, the measurement results of the extended counter are saved to the M2000 performance database for future queries. When you clear an extended counter, the M2000 does not save the measurement results of the extended counter to the performance database.
User-Defined Counter
User-defined counters refer to those defined on the M2000 client. The system defines the user defined counters by adding, subtracting, multiplying, and dividing the system default counters (both common counters and extended counters). You can add, modify, or delete the user-defined counter during the M2000 operation. User-defined counters can be measured and can also be nested to create other user-defined counters.
6.1.2 Performance Measurement Objects

This describes the performance measurement objects. A measurement object can be the physical concept of boards or subracks, or the logical concepts of cells. A certain corresponding relation exists between the measurement objects and the measurement counters. Each measurement object corresponds to some measurement counters. That is, the measured object has some specified measurement items. The measurement counters depend on the measurement objects. Performance measurement objects of an NE can be classified into three types. Operations on measurement objects depend on the object class.
l
For the first type, you do not need to specify manually the measurement object. The system measures all objects of a certain type by default. The NE reports all the obtained measurement results of all objects of this type to the M2000. Therefore, you do not need to add these objects manually to the measurement range. You can choose not to measure them. For the second type, you need to specify the measurement object. After you add this type of measurement objects manually to the measurement range, the NE notifies the M2000 of
6-4
the addition, and the M2000 displays these objects in the Measurement Object Management window.
l
For the third type, you need to enter the specific characteristics of the object, because the measurement is based on these characteristics.M2000The M2000 adds this type of objects and notifies the NE, and the NE reports the corresponding measurement results to the M2000. The object of the third type is displayed by icon on the M2000 client interface.
6.1.3 Measurement Function Sets and Subsets

The M2000 system involves large quantities of measurement counters. For better management, the measurement counters are categorized. These counters are divided into three levels, as shown in Figure 6-1.
l
Level 1 is the function set. A function set consists of function subsets related to a certain system function. Function sets are also called measurement sets. Level 2 is the function subset. A function subset consists of measurement counters related to a certain system function. Function subsets are also called measurement units. Level 3 is the measurement counter.
Figure 6-1 Levels of measurement counters
There is a certain correspondence between the measurement object and the measurement counter. To make it more specific, different measurement objects have different measurement counters. One measurement counter applies only to one type of measurement object. Measurement counters are classified into different measurement function sets. One measurement function set is divided into multiple measurement units. One measurement unit corresponds to one type of measurement objects. One measure object can correspond to multiple measurement units. These measurement units can belong to different measurement function sets.
6.1.4 Performance Measurement Periods

This describes the concepts pertaining to performance measurement periods. A measurement period refers to the interval for NEs to report performance measurement results. NEs report measurement results to the M2000 periodically. The M2000 analyzes the results and then saves the results to the database for future queries. The measurement periods vary according to the measurement objects. The following measurement periods are available: 5 minutes, 15 minutes, 30 minutes, 60 minutes, or 24 hours.
6.1.5 Performance Measurement Results

This describes the concept of performance measurement results. Performance measurement results refer to the values of measurement counters of NE measurement objects. Once set up successfully on the M2000, the NE reports automatically values of key performance counters of Class 1 objects periodically. On the M2000 client, you can add extended counters and Class 2 and Class 3 measurement objects into the measurement range. Accordingly, the NE reports measurement results of these measurement objects and counters automatically.
6.1.6 Performance Counter Thresholds

This topic describes the concept of performance counter thresholds. The performance threshold is used to monitor the actual measurement result of the performance counter. When the value of the measurement result exceeds that set by the user, the system generates an alarm. The threshold value of the performance counter can be the threshold value of a specific performance counter or the threshold value of the combined performance counters. You can set the thresholds in both the Threshold Management window and the Performance Monitor window.
l
In the Threshold Management window, the threshold value is the allowable offset of the counter compared to the normal value. This threshold value is used to monitor the status of the measurement counters. In the Performance Monitor window, the threshold value is the offset of the actual measurement value against the historical average value. This threshold value is used to monitor the dynamic status of the counters.
Setting Thresholds in Threshold Management

For one counter, you can set alarm thresholds for various time periods, or an alarm threshold for all time periods in every periodic measurement. These thresholds can be set for all objects of a measurement type, or for one or more objects. In the Threshold Management window, two types of threshold are available: simple threshold and combined threshold.
l
Simple Threshold: indicates setting the threshold value for a single counter. When the counter value exceeds the threshold value set by the user, the system generates the corresponding threshold alarm; when the range of the counter value resumes the threshold value within the normal threshold value, the system also resumes the corresponding value. Combined Threshold: indicates setting the threshold value for the counters after logic or arithmetic operations. When the counter value meets the requirements of the set threshold alarm triggering conditions after several periods, the system triggers the corresponding threshold alarm. When the counter value meets the requirements of the set threshold alarm resuming conditions, the system resumes the corresponding threshold alarm.
By default, the threshold type is Simple Threshold.
Setting Thresholds in Performance Monitor

The history average value, also called empirical value, of the counter is calculated by averaging the result value at the current time point and the result values at the corresponding time in the last 10 days. Here the last 10 days must share the same empirical value calculation sequence. For instance, if you set one sequence respectively from Monday to Sunday, then the last 10 days
from this Monday should be the 10 Mondays in the last 10 weeks. Currently the workday and non-workday sequence is adopted, that is, the empirical value is calculated from the result values of the same time point in the last 10 workdays. To monitor performance counters, you can set thresholds for counters to monitor changes of the counters. A relevant threshold alarm is generated when the offset of a counter value exceeds the threshold for three times consecutively. The generated threshold alarm is cleared when the offset of the counter value remains below the threshold for three consecutive times. You can monitor in real time counter thresholds. Then you can set counters, threshold sizes, and triggered threshold alarm levels during the threshold management.
6.1.7 Performance Measurement States

This describes the concept of performance measurement states. You can set the measurement object, measurement function subset, or counter threshold of an NE to the suspended or activated state. Suspended NEs generate no results. After being activated, the suspended NEs can generate results and report the results to the M2000.
6.1.8 Performance Measurement Procedure

This describes the M2000 performance measurement procedure, which consists of reporting, saving, and viewing performance data.
Procedure of performance measurement

Figure 6-2 shows the procedure of performance measurement of the M2000 system. When a measurement period ends, the counters of an NE, both common counters and specified extended counters, start to be reported to M2000. The NE collects the measurement results, that is, the performance data, and reports the results to the M2000. After the mediation layer in the M2000 server analyzes the received results, the performance server saves the results to the performance database. An alarm is generated when the M2000 detects that more than the specified number of results are received.
Issue 06 (2008-12-16)
6-7
Figure 6-2 Procedure of performance measurement
Reporting Performance Data

NEs report the collected performance results to the M2000 through various interfaces, which falls into two categories: the file interface and task interface.
l
File interface: The NE saves the measurement results of all the KPIs and extended counters into a file. When a measurement period ends, the NE uploads the file generated for this period to the M2000. The M2000 mediation layer analyzes the file and collects the results for each counter. For the extended counter that is not selected, the M2000 discards the results instead of saving them into the performance database. Task mode: The M2000 delivers the information required by the performance measurement, such as the measurement object, counter, and period, to the NE. Then, based on the information, the NE creates a performance measurement task and collects statistics on each measurement counter. During each measurement period, the NE reports the measurement results to the M2000. Then, the M2000 parses the results and delivers them to the performance database.
Operations involved in the performance management are the same for these two different interfaces.
Saving Performance Data into the Database

After receiving M2000 performance data from an NE, the M2000 analyzes the performance data and then saves the data to the performance database. For user-defined counters, the M2000 does not save the collected results in the performance database. When the results of user-defined counters are queried, the M2000 calculates the results through a preset formula and displays them through the client.
Displaying Performance Data

Through the M2000 client, you can easily query all the data stored in the performance database. The data is displayed on the client. You can save the data to a file.
6.2 Monitoring NE Performances

You can set NE performance measurement range and query performance measurement results. In addition, you can synchronize and subscribe to NE measurement results, query missing measurement results, and manage NE measurement states. 6.2.1 Setting a Performance Measurement Range for an NE This describes how to set measurement objects and counters and add the measurement range. In this way, the NEs can report the measurement results to the M2000 in each period. 6.2.2 Managing Class 3 Object For the type 3 object, you must select objects and enter required parameters for the client to collect the counter information. You can add type 3 objects, import objects in batches from files, and export object editing template. On the editing interface, you can also edit the remarks directly. 6.2.3 Synchronizing NE Measurement Results You can obtain the missing measurement results by synchronizing measurement results. 6.2.4 Subscribing to NE Measurement Results To help query measurement results, you can subscribe to measurement results by object and counter. After that, the new reported performance measurement results are displayed automatically in the Subscribe Result window. 6.2.5 Querying the Reliability of Measurement Results When the NE reports measurement results to the M2000, the reliability information of these results is contained to describe whether the data is reliable or suspect. A result is suspect if one or more items of data contained in this result record is described suspect. The result reliability refers to the ratio of reliable results to all the reported results. In the M2000 system, this ratio is expressed as a percentage. 6.2.6 Querying Missing Measurement Results During the M2000 running, measurement results may be missing due to many reasons, such as the disconnection of NEs from the M2000 within a period of time.M2000The missing result query and recollection function is supported. You can query missing measurement results by customizing query conditions or using the template. If measurement results are lost, you can synchronize the measurement results to obtain the missing results. 6.2.7 Checking the Integrity of NE Results You can check the integrity of NE result. This task consists of two sub-tasks: querying the integrity of current results and querying the integrity of historical results.
6.2.8 Managing NE Measurement States You can view the measurement states of measurement units of each NE and export the status table to an excel file.
6.2.1 Setting a Performance Measurement Range for an NE

This describes how to set measurement objects and counters and add the measurement range. In this way, the NEs can report the measurement results to the M2000 in each period.
Context
l
When you set to measure user-defined counters, the related original counters instead of nested user-defined counters are set to be measured. When you cancel the measurement of user-defined counters, the measurement of the userdefined counter instead of the related original counters are canceled. If a user-defined counter is being measured, the invoked original counter cannot be canceled.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure Management window, or click , and choose Measurement Settings tab.
Step 2 Select an object type or function subset on the navigation tree.

l
For the convenience of setting, you can organize the navigation tree by function subset when setting measurement counters, and organize the navigation tree by object type when setting measurement objects. In the organization style of the object type, right-click an object type in the navigation tree and choose View the Function Subset, In this situation, the navigation tree are organized by function subsets and only the function subsets of the object type are displayed. In the organization style of the function subset, right-click function subsets in the organization tree and choose Filter with Object Type,In this situation, only the function subsets that map the object type are displayed. After you deselect the options, all the function subsets are displayed.
Step 3 Select a function set and subset in the Measurement Settings tab. Check the objects and counters to be measured.
NOTE
When you set measurement objects, All Measurement Object and Selected Ne Measurement Object dynamically collect the statistics of objects that are set to measure. Fuzzy search is supported. You can enter a character, letter, or number in the Filter Search text box. Then, the system filters out the object types and function subsets that do not contain the typed string. In this way, you can easily located the object type or function subset. If you select All when setting measurement objects, then all the objects of the NE are selected. If the NE has no object, then the system automatically issues measurement tasks when adding performance objects. In this way, new performance objects can be measured automatically.

Related Concepts
6.1.1 Performance Measurement Counters 6.1.2 Performance Measurement Objects
6.2.2 Managing Class 3 Object

For the type 3 object, you must select objects and enter required parameters for the client to collect the counter information. You can add type 3 objects, import objects in batches from files, and export object editing template. On the editing interface, you can also edit the remarks directly. 6.2.2.1 Adding a Class 3 Object Only class 3 objects allows you to add measurement objects and obtain results from NEs. 6.2.2.2 Exporting Templates for Class 3 Objects You can export the edit template for type 3 objects to an .xls file. Then you can edit the object information to import objects in batch mode from the file. 6.2.2.3 Importing Class 3 Object You edit the object information file to import objects in batches from the file.
Adding a Class 3 Object

Only class 3 objects allows you to add measurement objects and obtain results from NEs.
Procedure
Step 2 Select Object Type for Organization Style. Step 3 Select a class 3 object on the navigation tree. Class 3 objects are identified by .
Step 4 Right-click in the measurement object list and choose Edit Object on the shortcut menu. The Object Editing dialog box is displayed. Step 5 You can add the class 3 objects either individually or in batches. If... You add class 3 objects individually You add class 3 objects in batches Then... Perform Step 6. Perform Step 7.
Step 6 To add the class 3 objects individually, perform the following steps: 1. 2.
Issue 06 (2008-12-16)
Click Add to add a blank row. Alternatively, right-click the list and choose Add on the shortcut menu. Select or enter the object attribute in the blank row.
3. 4. 1. 2.
Click Apply to add the object to the system. In the Information dialog box, click OK. Click Batch Add. The Batch Add dialog box is displayed. Select the attributes required in the four attribute panes. Then, click OK. The Batch Add dialog box is closed. All the attribute combinations are displayed in the Object Editing dialog box. Click Apply to add the object to the system. In the Information dialog box, click OK.
Step 7 To add the class 3 objects in batches, perform the following steps:
3. 4.
----End
Exporting Templates for Class 3 Objects

You can export the edit template for type 3 objects to an .xls file. Then you can edit the object information to import objects in batch mode from the file.
Procedure
Step 2 Select Object Type for Organization Style. Step 3 Select a type 3 object type on the navigation tree. Type 3 objects are identified by .
Step 4 Right-click in the measurement object list and choose Edit Object on the shortcut menu. The Object Editing dialog box is displayed. Step 5 Click Export Editing Template or right-click the list and choose Export Editing Template on the shortcut menu. The Save dialog box is displayed. Step 6 Select the save path and enter the file name. By default, the file name is the name of the current type 3 object. Step 7 Click Save. The displayed Message dialog box shows whether the operation is successful. Step 8 Click OK to close the Message dialog box. ----End
Importing Class 3 Object

You edit the object information file to import objects in batches from the file.
Context
The file must conform to a certain format. You can edit the template by using the exported objects.
Procedure
Step 2 Select Object Type for Organization Style. Step 3 Select a type 3 object type on the navigation tree. Type 3 objects are identified by .
Step 4 Right-click in the measurement object list and choose Edit Object on the shortcut menu. The Object Editing dialog box is displayed. Step 5 Click Import Objects or right-click the list and choose Import Objects to open the Open dialog box. Step 6 Select the file to be imported. Step 7 Click Open. Step 8 Click OK in the displayed success dialog box. ----End
6.2.3 Synchronizing NE Measurement Results

You can obtain the missing measurement results by synchronizing measurement results.
Context
CSCF, HSS, ATS, RM and DOPRA do not support this function.
Procedure
Step 1 Choose Performance > Measure Management > Status Browser , or click Measure Management window. to view the
Step 2 Right-click a node on the navigation tree and choose Synchronize Result, or click the icon to view the Synchronize Result window. Step 3 Set the parameters.
l
The default end time is the current time. The default start time is result of subtracting the synchronization time range in the preference from the current time. You can synchronize the performance measurement results of multiple NEs, multiple periods, and multiple function subsets of the same NE type at a time.
Step 4 Click OK to start the synchronization. Step 5 Click OK in the displayed Prompt dialog box. After the synchronization command is sent to the NE, the NE needs some time to report the performance measurement data. After the data is reported, you can query missing measurement results by querying performance measurement results. ----End
Related References
6.7.11 Parameters for Synchronizing NE Measurement Results
6.2.4 Subscribing to NE Measurement Results

To help query measurement results, you can subscribe to measurement results by object and counter. After that, the new reported performance measurement results are displayed automatically in the Subscribe Result window.
Context
Each GUI can open one result subscription window. You can subscribe to the measurement results of only one NE and one function subsets in each subscription window.
Procedure
Step 2 On the navigation tree, right-click a node and choose Subscribe Result from the shortcut menu, or click the icon to view the Subscribe Result window.
Step 3 Set the parameters in the Measurement Period and Range areas.
NOTE
You can set the performance measurement results of multiple NEs, multiple periods, and one function subset of the same NE type at a time.
Step 4 Click OK. After the subscription is complete, each measurement period is displayed in one window. Each function subset is displayed in one tab. ----End
6.2.5 Querying the Reliability of Measurement Results

When the NE reports measurement results to the M2000, the reliability information of these results is contained to describe whether the data is reliable or suspect. A result is suspect if one or more items of data contained in this result record is described suspect. The result reliability refers to the ratio of reliable results to all the reported results. In the M2000 system, this ratio is expressed as a percentage.
Procedure
Step 1 Choose Performance > Query Result, or click to view the Query Result window.
Step 2 Right-click the measurement result table and choose Reliability on the shortcut menu. Then you can view the reliability in the displayed dialog box. Click Yes to the view the detailed information. ----End
Related References
6.7.8 Parameters for Querying the Reliability of Measurement Results
6.2.6 Querying Missing Measurement Results

During the M2000 running, measurement results may be missing due to many reasons, such as the disconnection of NEs from the M2000 within a period of time.M2000The missing result query and recollection function is supported. You can query missing measurement results by customizing query conditions or using the template. If measurement results are lost, you can synchronize the measurement results to obtain the missing results.
Procedure
l Customize query conditions to query missing measurement results. 1. 2. Choose Performance > Measure Management > Status Browser , or click view the Measure Management window. to
Right-click a node on the navigation tree and choose Query Missing Result on the shortcut menu. Or you can click the icon dialog box. to open the Query Missing Result
3.
Set the parameters. The default end time is the current time. The default start time is the result of subtracting the missing result time range in the preference setting from the current time.
4.
Click OK. If missing measurement result exists in the time segment, the missing results are listed in the displayed dialog box. The first column displays the object information, and the second displays the time segment.
Query missing measurement results based on the template. 1. 2. 3. 4. Choose Performance > Query Result, or click displayed. Double-click a template in the navigation tree. Click Lost Result. Alternatively, right-click in the right pane and choose Lost Result from the shortcut menu. The Query Missing Result dialog box is displayed. You can query the missing measurement results by using any of the following methods:
. The Query Result window is
Query the missing results by using one of the following methods: In function subset list, select the function subset to be queried and then press the enter key. In function subset list, double-click the function subset to be queried. In function subset list, select the function subset to be queried and click Query. Alternatively, right-click the function subset and choose Query from the shortcut menu.
If the measurement results of this function subset are missing, the right pane in the Query Missing Result dialog box displayed the object information and related time segment.
Issue 06 (2008-12-16)
If the measurement results of this function subset are not missing, the system displays a dialog box showing that the results are not missing.
----End
Related References
6.7.7 Parameters for Querying Missing Measurement Results
6.2.7 Checking the Integrity of NE Results

You can check the integrity of NE result. This task consists of two sub-tasks: querying the integrity of current results and querying the integrity of historical results. 6.2.7.1 Monitoring the Integrity of Current Measurement Results for NEs Monitoring the integrity of measurement results refers to checking the integrity of measurement results in a measurement period before the current time. 6.2.7.2 Querying the Integrity of Historical Measurement Results for NEs You can query the integrity of historical measurement results.
Monitoring the Integrity of Current Measurement Results for NEs

Monitoring the integrity of measurement results refers to checking the integrity of measurement results in a measurement period before the current time.
Context
Integrity of measurement results is associated with the number of results to be reported, number of results reported, and the ratio of the two numbers. The number of results to be reported refers to the number of valid measurement objects in a measurement period. Valid measurement objects refer to the NE objects that are to be measured and not suspended.
Procedure
Step 2 Click , and select Integrity Monitor to view the Condition setting for integrity monitor dialog box. Step 3 Select the measurement period, NE, and function subset. A maximum of 5 measurement periods, 10 NEs, and 10 function subsets are allowed. Step 4 Click OK.
l
The Integrity Monitor dialog box is displayed. Each tab shows the result of monitoring the integrity of one period. The tab is named in the format: Measurement period (start time of the period). For example, if the current time is 15:24, the tab name is 5 Minutes (15:15-15:20), 15 Minutes (15:00-15:15). The monitoring results are updated dynamically with the time. The tab for period of 5 minutes changes its name to 5 Minutes (15:20-15:25) when the current time is 15:30.
----End
Postrequisite
In the monitoring results, the intersecting cell of the NE column and function subset row is an available cell. Other cells are sum cells. You can click the available cell to activate the dimmed button, where
l
Each available cell records the number of performance results that are actually reported, the number of performance results that should be reported, and the ratio of the previous two numbers for the corresponding function subset. The sum cell under each NE records the number of performance results that are actually reported, the number of performance results that should be reported, and the ratio of the previous two numbers for all the corresponding function subset. The sum cell of each function subset records the number of performance results that are actually reported, the number of performance results that should be reported, and the ratio of the previous two numbers for all the NEs of the corresponding function subset. The sum cell at the right corner records the total number of sum cells of all NEs, that is, the sum of the sum cells of all function subsets.
You can select a cell in the Integrity Monitor window and perform Synchronize Result and Query Result.
Querying the Integrity of Historical Measurement Results for NEs

You can query the integrity of historical measurement results.
Context
Integrity of measurement results is associated with the number of results to be reported, number of results reported, and the ratio of the two numbers. The number of results to be reported refers to the number of valid measurement objects in a measurement period. Valid measurement objects refer to the NE objects that you have set to measure and are not suspended.
Procedure
, and select Integrity Query to view the Condition setting for Integrity Query Step 2 Click dialog box. Step 3 Select the measurement period, NE, and function subset. The maximum of 5 periods, 10 NEs, and 10 function subsets are allowed. Step 4 Click OK.
l
The Integrity Query dialog box is displayed. Each tab shows the result of querying integrity of one period. The tab is named in the format: Measurement period (start time of the query). For example, 5 Minutes (2006-12-05 15:00-2006-12-06 15:00).
----End
Postrequisite
You can select a cell in the Integrity Query window and perform Synchronize Result , Query Result, and Query Missing Result.
6.2.8 Managing NE Measurement States

You can view the measurement states of measurement units of each NE and export the status table to an excel file. 6.2.8.1 Viewing NE Measurement State You can view the measurement state and the corresponding quantity of all NE measurement units of a certain NE type. 6.2.8.2 Exporting NE Measurement State This task is performed to export the measurement state table to files.
Related Concepts
6.1.7 Performance Measurement States
Viewing NE Measurement State

You can view the measurement state and the corresponding quantity of all NE measurement units of a certain NE type.
Procedure
Step 2 Choose an NE type on the navigation tree. Then you can view the measurement states in Measurement Status in the right pane. ----End
Exporting NE Measurement State

This task is performed to export the measurement state table to files.
Procedure
Step 1 Choose Performance > Measure Management > Status Browser , or click Measure Management window. Step 2 Select an NE type on the navigation tree. Step 3 Right-click the measurement status table and choose Export Status on the shortcut menu. The Save dialog box is displayed. Step 4 Select the save path and file type. Enter the file name. The file can be in TXT, HTML, CSV, or XLS format.
to view the
Step 5 Click Save. Step 6 Click OK in the displayed prompt box. ----End
6.3 Querying Performance Measurement Results

This task is performed to query performance measurement results. Two query modes, that is, by template and by new conditions, are available. 6.3.1 Querying Results by Templates This describes how to query results by template. You can use the default query template or a created user-defined template to query measurement results, thus improving query efficiency. 6.3.2 Querying Results by New Conditions You can query on the M2000 client all the measurement results reported after the NE is created. Before querying the results, set the query conditions, including the concerned counters and objects and the time segment. 6.3.3 Query Results by Busy Hour The M2000 enables you to query performance measurement results by busy hour. 6.3.4 Re-querying Results After you re-query or query in real time the results, you can reset query conditions and then requery results. 6.3.5 Setting Result Query Conditions You can set result query conditions to query measurement results. The conditions include the measurement function set/subset, object range, counter range, time range, measurement period, query range, sequence mode, and filter condition. 6.3.6 Displaying Performance Measurement Results Measurement results can be displayed in a table or a line or bar chart. You can set the counter color and the background color for performance result charts to enhance the visual effect. 6.3.7 Saving Performance Measurement Results You save the performance measurement results to a file. 6.3.8 Printing Performance Measurement Results You can print the queried measurement results. 6.3.9 Managing Result Query Templates The condition template provides a group of condition parameters used for querying measurement results. It saves the common used data. The templates comprises the system default template and user-defined template. You cannot modify the query conditions set on the system template. You also cannot delete the system template. You can create, modify, query, and copy the defined template. In addition, you can set a directory for the defined template.
Related Concepts
Related References
6.7.1 Interface Description: Query Result
6.3.1 Querying Results by Templates

This describes how to query results by template. You can use the default query template or a created user-defined template to query measurement results, thus improving query efficiency.
Procedure
Step 1 Choose Performance > Query Result, or click The Query Result window is displayed. Step 2 In the template tree on the left part of Query Result, select a template. Step 3 Right-click the template and choose Query Result > Default from the shortcut menu. Alternatively, double-click the selected template. The query results are displayed on a new tab page. The tabs are name in the format of Template Name(Current Time). For example, all(25/12/2007 17:16). Select Default . Then the selected Date range when you create the template is the date range for querying the measurement results. You can change the date range for querying measurement results as required. For details, refer to Table 6-1. Table 6-1 Description of the options under Query Result Menu Today Yesterday This week Last week All time Description To query the measurement results of today for some counters under the selected objects based on the query template. To query the measurement results of yesterday for some counters under the selected objects based on the query template. To query the measurement results of this week for some counters under the selected objects based on the query template. To query the measurement results of last week for some counters under the selected objects based on the query template. To query all the measurement results for some counters under the selected objects based on the query template. For example, the measurement results of some counters under an object can be stored in the database for 30 days. After you select this option, you can view all the measurement results for the selected counter in the 30 days. Specific After you set Start Time and End Time, the system queries the measurement results for some counters under the selected object at the specific time based on the query template. .
----End
Postrequisite
You can modify the name of the sheet to be queried according to actual requirements. To modify the name, perform as follows:
1. 2.
Right-click a tab and choose Modify from the shortcut menu. Enter the new name in the Please put in new name dialog box, and then click OK.
6.3.2 Querying Results by New Conditions

You can query on the M2000 client all the measurement results reported after the NE is created. Before querying the results, set the query conditions, including the concerned counters and objects and the time segment.
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to select New Query to display Query Result window. Step 3 On the Object Settings, Counter Settings, and Other Settings tab pages, set the query conditions for the measurement results. Step 4 Optional: The Filter by Counter to set the filtering conditions. Step 5 Click Query. The queried measurement results are displayed in Query Result in tables, line charts, or bar charts. ----End
Postrequisite
You can modify the name of the sheet to be queried according to actual requirements. To modify the name, perform as follows: 1. 2. Right-click a tab and choose Modify from the shortcut menu. Enter the new name in the Please put in new name dialog box, and then click OK.
6.3.3 Query Results by Busy Hour

The M2000 enables you to query performance measurement results by busy hour.
Context
l l
The busy hour refers to the hour when the counter value is the greatest. The period for collecting statistics of busy hour is set to 60 minutes. If the NE does not support 60-minute period, the results are summarized every 30 minutes. If the NE support neither 60-minute period nor 30-minute period, the 15-minute period is adopted. If the 15minute period is not supported, the statistics are not collected. You can not perform busy hour query of the day. You can perform busy hour query only when busy hour counters of the select NE type exist. Busy hour counters are defined by NEs. You cannot query the missing results by this query mode.
l l
Issue 06 (2008-12-16)
Procedure
Step 2 Click New Query. Alternatively, right-click a directory in the navigation tree and choose New Query from the shortcut menu. The New Query dialog box is displayed. Step 3 Select a function subset on the navigation tree in the left pane. Step 4 Select the measurement object on the Object Settings tab and measurement counters in the Counter Settings tab. Step 5 On the Other Settings tab, select Busy Time under Time Mode. When multiple busy hour counters exist in the same function subset, you can select only one busy hour counter to query results. Step 6 Click Query. The queried measurement results are displayed in the Query Result window in the form of tables, line charts, and histograms. ----End
Postrequisite
6.3.4 Re-querying Results

After you re-query or query in real time the results, you can reset query conditions and then requery results.
Prerequisite
You have queried the results for once.
Procedure
Step 1 In Query Result, click Condition. The Condition Information window is displayed. Step 2 Set conditions to query results. In the displayed Condition Information window, objects and counters are already set in the previous time. You need not reset the objects and counters. You need reset query conditions in Other Setting. The objects and counters can be reset. Step 3 Click Query. ----End
Postrequisite
6.3.5 Setting Result Query Conditions

You can set result query conditions to query measurement results. The conditions include the measurement function set/subset, object range, counter range, time range, measurement period, query range, sequence mode, and filter condition. 6.3.5.1 Specifying the Measurement Function Set or Function Subset of Results When you set the measurement result query, you can specify a measurement function subset. 6.3.5.2 Specifying the Objects to Be Queried When you set result query conditions, you can specify the objects to be queried. 6.3.5.3 Specifying the Counters to Be Queried When you set the query conditions, you can specify the counters to be queried. 6.3.5.4 Specifying the Time Range of Results Set the query conditions for measurement results. You can specify the time range and mode of the query. 6.3.5.5 Specifying the Measurement Period of Results When you set result query conditions, you can specify the measurement period of results. 6.3.5.6 Setting the Mode of Sorting Displayed Results You can sort the queried measurement results by objects, time, or selected counters. 6.3.5.7 Setting the Conditions for Filtering Result Counters When setting conditions for querying performance measurement results, you can set filter conditions for each measurement counter. The M2000 displays only the measurement results that meet the filter conditions.
Specifying the Measurement Function Set or Function Subset of Results

When you set the measurement result query, you can specify a measurement function subset.
Procedure
Step 1 Choose Performance > Query Result, or click The Query Result window is displayed. Step 2 Click New Query. Alternatively, right-click a directory on the navigation tree and choose New Query to open the Query Result dialog box. Step 3 Select a measurement function subset on the navigation tree in the left part of the window. ----End
Related Concepts
6.1.3 Measurement Function Sets and Subsets
Specifying the Objects to Be Queried

When you set result query conditions, you can specify the objects to be queried.
Procedure
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to select New Query to display the Query Result. Step 3 Select a node in the navigation tree in the left of the window. Step 4 Select measurement objects in Object Settings.
l l l
The system prompts users of the number of selected objects. You can select specific objects, all the objects of an NE, objects of all the NEs. Provide the function of querying by name. You can type the name of an object to be queried. The system displays the mapping object. Provide the function of filtering by state. The system can display the objects of All, Set, and No Set, Now Object, and History Object. icon indicates a history object.
On the navigation tree in the Available Objects group box, the ----End
Specifying the Counters to Be Queried

When you set the query conditions, you can specify the counters to be queried.
Procedure
Step 2 Click New Query. Alternatively, right-click a directory in the navigation tree and choose New Query from the shortcut menu. The New Query dialog box is displayed. Step 3 Select a node in the navigation tree in the left part of the window. Step 4 Select measurement counters in Counter Settings.
6-24
Issue 06 (2008-12-16)

NOTE
M2000Note that the counter selection for different function subsets has restrictions. You can select counters for a maximum of N function subsets, where N is smaller than 10, you can change the value of N according to the specifications of EMS devices and the number of NEs connected to the system. The number of selected counters that are already set to be measured cannot exceed 150. The system prompts users of the number of selected counters. On the M2000, the number of user-defined counters that can be selected is limited. The number of user-defined counters that can be selected is smaller than 50. The counters that are not set to be measured display in grey. The system will not respond to the query of these counters. You can query measurement results of user-defined counters. Provide the function of querying by name. You can type the name of a counter to be queried. The system displays the mapping counter. The system displays the mapping object. The system can display the counters of All, Set, and No Set.
l l l l l l
----End
Related Concepts
Specifying the Time Range of Results

Set the query conditions for measurement results. You can specify the time range and mode of the query.
Procedure
Step 2 Click New Query, or select theCustom node or a template under this node and right-click to select New Query to display Query Result. Step 3 Select a node in the navigation tree in the left part of the window. Step 4 Set the time range and mode of the query in Other Settings. ----End
Related References
6.7.15 Parameters for Specifying the Time Range of Results
Specifying the Measurement Period of Results

When you set result query conditions, you can specify the measurement period of results.
Procedure
Step 1 Choose Performance > Query Result, or click
Issue 06 (2008-12-16)
. The Query Result window is displayed.

6-25
Step 2 Click New Query, or select theCustom node or a template under this node and right-click to select New Query to display the Query Result. Step 3 Select a node in the navigation tree in the left part of the window. Step 4 Set a measurement period in Other Settings. ----End
Setting the Mode of Sorting Displayed Results

You can sort the queried measurement results by objects, time, or selected counters.
Procedure
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to select New Query to display Query Result. Step 3 Select a node in the navigation tree in the left part of the window. Step 4 Set the sequence mode in the Sort box in Other Settings.
l
The sorting has five priorities. They are the major, minor, third, fourth and fifth respectively from high to low. The sequence can be organized in an ascending order or a descending order. When you set different keywords for various sorting priorities, the M2000 sorts and displays the queried measurement results according to the keyword priority. You are not allowed to set two or more same key words for sequencing. The key words used for sequencing must have precedence over those not for sequencing.
l l
l l
----End
Related References
6.7.9 Parameters for Setting the Mode of Sorting Displayed Results
Setting the Conditions for Filtering Result Counters

When setting conditions for querying performance measurement results, you can set filter conditions for each measurement counter. The M2000 displays only the measurement results that meet the filter conditions.
Context
l l
You can set a maximum of 200 filter conditions. The logical operators between multiple filter conditions define the logical relationship. If the counter value of a is greater than 3 and the counter value of b is greater than 2, or counter value of c is smaller than 1, the results are displayed. Therefore, the logical relation is a > 3 and b > 2 or c < 1 none.
6-26

NOTE
The logical operator of the filter conditions must be none. The parameters before the logical operator is allowed to be none.
Procedure
Step 1 Choose Performance > Query Result, or click The Query Result window is displayed. Step 2 Click New Query, or select theCustom node or a template under this node and right-click to choose New Query to display Query Result. Step 3 Select a node in the navigation tree in the left part of the window. Step 4 In Other Settings, click Filter by Counter to display the Set Counter Filter Conditions dialog box. Step 5 The setting of filter conditions involves the following three operations: Operation Add an filter condition. Procedure Select the counter filter condition and click Add. .
Modify an filter condition. 1. Select an existing filter condition in the list and click Modify. 2. Click Yes in the displayed Confirm dialog box. Delete a filter condition. 1. Select an existing filter condition in the list and click Delete. 2. Click Yes in the displayed Confirm dialog box. ----End
Related References
6.7.6 Parameters for Setting the Conditions for Filtering Result
6.3.6 Displaying Performance Measurement Results

Measurement results can be displayed in a table or a line or bar chart. You can set the counter color and the background color for performance result charts to enhance the visual effect. 6.3.6.1 Displaying Measurement Results in Table This task is performed to display measurement results in tables. 6.3.6.2 Displaying Measurement Results in Line Chart This task is performed to display the measurement results in line charts. 6.3.6.3 Displaying Measurement Results in Bar Chart This task is performed to display measurement results in the bar chart. 6.3.6.4 Setting the Background Color of a Chart
When the M2000 displays the performance results in a line chart or bar chart, you can set the background color of the chart.
Displaying Measurement Results in Table

This task is performed to display measurement results in tables.
Prerequisite
The existing measurement results are displayed on the Query Result tab of the Query Result window.
Context
l
Measurement results can be displayed in a table, a line chart, or a bar chart. The system takes the table form by default. When the results are displayed in a table, you can print measurement results and save job results into a file. You can right-click the table heading and choose More to open the Customize dialog box, where you can customize the column.
Procedure
Under View Type, click Table. ----End
Postrequisite
l l
Click Measure, you can query the measurement status of the objects and the counters. Click Lost Result, you can query the missing measurement results.
Displaying Measurement Results in Line Chart

This task is performed to display the measurement results in line charts.
Prerequisite
The existing measurement results are displayed in the Query Result window.
Context
l
Measurement results can be displayed in a table, a line chart, or a bar chart. The system takes the table form by default. In a line chart, the vertical coordinate represents the measurement counter values, and the horizontal coordinates represents the measurement time. You can choose to display the line chart according to By Object or By Counter.
Select By Object, and the line chart displays the value change of multiple counters of one object. Select By Counter, and the line chart displays the value change of the same counter of multiple objects.
6-28
Procedure
Step 1 Under View Type, click Line Chart. You can print measurement result and save job results into a file. Step 2 You can choose to display the line chart according to By Object or By Counter. Click to zoom out the chart, and click Procedure 1. Select a measurement object from Select Object. 2. Select measurement counters from Select Counter. By Counter 1. Select a measurement counter from Select Counter. 2. Select measurement objects from Select Object. ----End to zoom in the chart.
Display Mode By Object
Displaying Measurement Results in Bar Chart

This task is performed to display measurement results in the bar chart.
Prerequisite
The existing measurement results are displayed in the Query Result window.
Context
l
Measurement results can be displayed in a table, a line, or bar chart. The system takes the table form by default. In a bar chart, the vertical coordinate represents the measurement value, and the horizontal coordinate represents the measurement object or measurement counter. You can choose to display the chart by object or by counter. The measurement counters are displayed in different colors and icons.
Procedure
Step 1 Under View Type, click Bar Chart. You can print measurement results and save job results into a file. Step 2 You can choose to display the bar chart according to By Object or By Counter. Display Mode Procedure By Object 1. In the Select Object drop list, select one or multiple measurement objects. 2. In the Select Counter drop list, select one or multiple measurement counters.
Issue 06 (2008-12-16)
6-29
Display Mode Procedure By Counter 1. In the Select Counter drop list, select one or multiple measurement counters. 2. In the Select Object drop list, select one or multiple measurement objects. Step 3 Select the time under Select Time. ----End
Setting the Background Color of a Chart

When the M2000 displays the performance results in a line chart or bar chart, you can set the background color of the chart.
Procedure
Step 1 Right-click Background Color in result tab to display the Background Setting dialog box. Step 2 Select a color. Step 3 Click OK. ----End
Related References
6.7.10 Parameters for Setting a Background Color for a Measurement Results Chart
6.3.7 Saving Performance Measurement Results

You save the performance measurement results to a file.
Prerequisite
The performance measurement results are found.
Procedure
In the Query Result window, save the results through the shortcut menu or by clicking Save.
l l
The performance query results in tables can be saved as an .xls, .csv., .html., or .txt file. The performance query result in line charts or bar charts can be saved as a .jpg file. When the results are displayed in tables, right-click and choose Export Selected Rows or Export All from the shortcut menu. When the results are displayed in line charts or bar charts, right-click and choose Save.
To save the measurement results through the shortcut menu, perform the following steps:
l
----End
6.3.8 Printing Performance Measurement Results

You can print the queried measurement results.
Procedure
Step 1 Choose Performance > Query Result, or click The Query Result window is displayed. Step 2 Query a result and then open the tab indicating the queried result. Step 3 Right-click and choose Print to open the Print dialog box. Step 4 Set the print parameters. Step 5 Click Print. ----End .
6.3.9 Managing Result Query Templates

The condition template provides a group of condition parameters used for querying measurement results. It saves the common used data. The templates comprises the system default template and user-defined template. You cannot modify the query conditions set on the system template. You also cannot delete the system template. You can create, modify, query, and copy the defined template. In addition, you can set a directory for the defined template. 6.3.9.1 Adding a Result Query Template When querying the measurement results, you can set the query conditions and save them as a template. 6.3.9.2 Modifying a Result Query Template For the added query template, you can modify the query conditions set on the template. 6.3.9.3 Viewing the Conditions in a Template For the added query template, you can view the conditions in it. 6.3.9.4 Copying a Result Query Template To simplify the operation, the M2000 provides the function of copying and cutting the query template. 6.3.9.5 Managing the Directory of Result Query Templates For the convenience of managing the user-defined query template, the system can create, delete, and rename the sub-directory.
Adding a Result Query Template

When querying the measurement results, you can set the query conditions and save them as a template.
Procedure
Step 1 Choose Performance > Query Result, or click Step 2 From the template tree, select a template. Step 3 Right-click and select New Query to view the Query Result dialog box. Set conditions for querying measurement results.
. The Query Result window is displayed.
Step 4 Click Save Template to view the Save As dialog box. Step 5 Enter a name for this new template.
NOTE
The template name is composed of up to 64 characters, including numerals, spaces, English letters, Chinese characters and some special characters such as ! { } [ ] ( ) , . ; _
Step 6 Select a sub-directory in the directory tree in Save As to store this new template.
NOTE
The added template can only be stored under directories of the custom directory (including the custom directory).
Step 7 Click OK to save this template. Click Cancel to cancel the added query template. ----End
Modifying a Result Query Template

For the added query template, you can modify the query conditions set on the template.
Procedure
Step 2 In the template tree, select the template you want to modify. Step 3 Right-click and select Attribute to display the Template Attributedialog box. Step 4 Reset result query conditions. Step 5 Click Save to save the modification made on the template. Click Save As to save the modified template as another template. ----End
Viewing the Conditions in a Template

For the added query template, you can view the conditions in it.
Procedure
Step 2 In the template tree, select the template to be queried. For the default template, you can copy it, find it in from the user-defined templates, and view the properties. Step 3 Right-click and select Attribute to display the Template Attribute dialog box. Step 4 View the related information.
l l
Select Object Settings to view the selected objects on the template. Select Counter Settings to view the selected counters on the template.
6-32

l
Select Other Settings to view information about the time mode, date range, period, query range, and sort on the template.
----End
Copying a Result Query Template

To simplify the operation, the M2000 provides the function of copying and cutting the query template.
Context
The default template can be copied to the Custom directory as a custom template. The custom template can only be copied/pasted under the Custom directory.
Procedure
Step 1 Choose Performance > Query Result, or click Step 2 In the template tree, select a template. Step 3 Right-click and select Copy. Step 4 Select a destination directory. Right-click and select Paste. ----End . The Query Result window is displayed.
Managing the Directory of Result Query Templates

For the convenience of managing the user-defined query template, the system can create, delete, and rename the sub-directory.
Procedure
Step 1 Choose Performance > Query Result, or click The Query Result window is displayed. Step 2 Outspread the navigation tree, and select a directory node under the Template > Custom node. Step 3 Right-click the object and select the corresponding menu option. You can create, delete, and rename the sub-directory. Operation Create a sub-directory Procedure 1. Right-click and select Create directory, Enter a name for the sub-directory. 2. Right-click and select Enter, or click the button. Delete a sub-directory 1. Right-click and selectDelete. 2. Click Yes in Confirm. .
Issue 06 (2008-12-16)
6-33
Operation
Procedure
Rename a sub-directory 1. Right-click and select Rename, Enter a name for the subdirectory. 2. Press or click Enter.
NOTE
l l
The template name is composed of up to 64 characters, including numerals, spaces, English letters, and some special characters " ! { } [ ] ( ) , . ; _ " If this sub-directory contains query templates, the templates are deleted together with this sub-directory.
----End
6.4 Managing Measurement Objects

Through measurement object management, you can search for counters and objects. You can also export and import measurement settings information. 6.4.1 Querying Measurement Objects This describes how to query the measurement objects in the Measure Management window. 6.4.2 Querying Measurement Counters This task is performed to query the measurement counters in the Measure Management window. 6.4.3 Importing Measurement Object Data You can import all the measurement objects of a certain object type of a certain NE. 6.4.4 Exporting Measurement Object Data You can export all the measurement objects of a certain object type of a certain NE. 6.4.5 Importing Setting of Measurement This describes how to import M2000 measurement object data. 6.4.6 Exporting Setting of Measurement This task is performed to export measurement object data by object type or function subset. 6.4.7 Modifying Remarks of a Measurement Object You can modify the memo of any type of measurement object. Object remark is used to describe the functions of the measurement object. 6.4.8 Activating/Deactivating a Measurement Task This describes how to activate a suspended measurement task and suspend an activated task.
6.4.1 Querying Measurement Objects

This describes how to query the measurement objects in the Measure Management window.
6-34
Issue 06 (2008-12-16)
Procedure
Step 2 Select Object Type for Organization Style. Step 3 Select an object type on the navigation tree. The lower right pane displays all the measurement objects under this object type. All Measurement Object and Selected Ne Measurement Object collect the statistics of objects that are set to be measured.
NOTE
You can enter the keyword of the object name in the Filter Search field to quickly find the object type.
----End
Related Concepts
6.1.4 Performance Measurement Periods 6.1.2 Performance Measurement Objects 6.1.2 Performance Measurement Objects
Related References
6.7.16 Parameters for Measurement States of Measurement Objects and Counters
6.4.2 Querying Measurement Counters

This task is performed to query the measurement counters in the Measure Management window.
Procedure
Step 2 Select Object Type for Organization Style. Step 3 Select an object type on the navigation tree. Step 4 Select the function set and function subset. Step 5 In the Measurement Counter area, all the measurement counters under the function subset are listed by the measurement period.
NOTE
You can enter the keyword of the function subset name in the Filter Search field to quickly find the function subset.
----End
Related Concepts
Related References
6.4.3 Importing Measurement Object Data

You can import all the measurement objects of a certain object type of a certain NE.
Context
You can edit the exported xml files, and then import them.
Procedure
Step 2 Select an object type on the navigation tree.

NOTE
The type of the imported object must be the same with the one selected on the navigation tree. Otherwise, the import fails.
Step 3 Right-click the table on the right of the Measurement Object field and choose Import to view the Open dialog box. Step 4 Select the .xml file to be imported. Step 5 Click Open. The displayed prompt box indicates whether the import succeeds. Step 6 Click OK to close the prompt box. ----End
6.4.4 Exporting Measurement Object Data

You can export all the measurement objects of a certain object type of a certain NE.
Procedure
Step 2 Select an object type on the navigation tree. Step 3 Select an NE on the left of the Measurement Object field. The table on right lists all the measurement objects that are of the selected object type. Step 4 Right-click the table and choose Export to open the Save dialog box. Step 5 Set the save path and enter the file name. Step 6 Click Save to save the file to an .xml file. The displayed prompt box indicates whether the export succeeds.
Step 7 Click OK to close the prompt box. ----End
6.4.5 Importing Setting of Measurement

This describes how to import M2000 measurement object data.
Context
l
You can import the measurement settings of counters and the objects named All. If you set the All object to be measured, the system measures all the measurement objects of the object type. For the import of user-defined counters, the system create the counters automatically if no such counter exists. The imported file is in XML format.
Procedure
Step 1 Choose Performance > Measure Management > Status Browser , or click Measure Management window. Step 2 Click to view the Open dialog box. to view the
Step 3 Select the file to be imported. Step 4 Click Open. The displayed Operation Result prompt box shows the imported result information. Step 5 Click OK to close the Operation Result dialog box. ----End
6.4.6 Exporting Setting of Measurement

This task is performed to export measurement object data by object type or function subset.
Context
l l
Exported information includes measurement setting information of objects and counters. When exporting user-defined counters, you need to export the user-defined counter, formula nesting the user-defined counter, and other information. Information of the original counter is not exported. The exported file is in XML format. You can click All or Set in the Others tab of the Preference dialog box. Select All to export all the measurement settings of the selected node. Select Set to export the information of the set objects or counters.
l l
Issue 06 (2008-12-16)
6-37
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure Management window, or click Step 2 Select a node on the navigation tree. You can select NE type, object type, function set, and function subset. The exported measurement settings are associated with the selected node. Step 3 Click to open the Save dialog box. , and choose the Measurement Settings tab.
Step 4 Set the save path and file name. Step 5 Click Save. After the exporting is complete, a success prompt box is displayed. Step 6 Click OK to close the prompt box. ----End
6.4.7 Modifying Remarks of a Measurement Object

You can modify the memo of any type of measurement object. Object remark is used to describe the functions of the measurement object.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure Management window, or click Step 2 Select a node on the navigation tree. Step 3 Select a measurement object in the right table. Double-click the Memo column. Step 4 Add or modify the memo of the measurement object. Step 5 Click Apply. The displayed dialog box shows the operation results. Step 6 Click OK to close the prompt box. ----End , and choose Measurement Settings tab.
6.4.8 Activating/Deactivating a Measurement Task

This describes how to activate a suspended measurement task and suspend an activated task.
Procedure
Step 1 Choose Performance > Measure Management > Status Browser or click Management window is displayed. Step 2 Perform the related operations based on the actual requirement.
. The Measure
To... Suspend a measurement task
Perform
l l
For a single measurement task, performStep 3. For multiple measurement tasks, perform Step 4. For a single measurement task, performStep 5. For multiple measurement tasks, perform Step 6.
Activate a measurement task
l l
Step 3 Perform the following steps: 1. 2. 3. On the Measurement Status tab page, select an object whose measurement task needs suspending. Right-click the object and choose Suspend Measurement on the shortcut menu. In the Prompt dialog box, click OK.
Step 4 Perform the following steps: 1. 2. 3. 4. In the navigation tree, select a function subset or its counter object. Right-click it and choose Suspend Measurement on the shortcut menu. The Suspend dialog box is displayed. In the Period field, set the period for executing the measurement task. In the Range field, set the NEs and counter objects of the measurement task. Click OK.
Step 5 Perform the following steps: 1. 2. 3. On the Management Status tab page, select an object whose measurement task needs activating. Right-click the object and choose Active Measurement on the shortcut menu. In the Prompt dialog box, click OK.
Step 6 Perform the following steps: 1. 2. 3. 4. In the navigation tree, select a function subset or its counter object. Right-click it and choose Active Measurement . The Active dialog box is displayed. In the Period filed, set the period for executing the measurement task. In the Range field, set the NEs and counter objects of the measurement task. Click OK.
----End
6.5 Managing User-Defined Counters

The user-defined counter management involves two types of counters: system counters and userdefined counters. The system counter is obtained when the system performs the arithmetic operation on the original counters in the system by default. It is attached to the system. When the M2000 is running, you can perform a arithmetic operation on the original system counters to obtain a new measurement counter. The counter generated in this way is called the userdefined counter. The user-defined counters apply only to the periodic measurement results. A user-defined counter is measured only when all the original counters contained in the formula
are measured. If an original counter is not measured, the user-defined counter cannot be measured. 6.5.1 Adding a User-Defined Counter According to the existing measurement counters, this describes how to define a user-required measurement counter by using the arithmetic. 6.5.2 Modifying a User-Defined Counter This describes how to modify a user-defined counter. The items counter name, unit, and formula can be modified. 6.5.3 Importing a User-Defined Counter This describes how to create a user-defined counter easily by importing the corresponding information from an .XML file. 6.5.4 Exporting a User-Defined Counter In the M2000, you can export the latest user defined counter information into an .XML file. Accordingly, you can import the user-defined counter information from the .XML file if required.
Related References
6.7.4 Interface Description: User-defined Counter Management
6.5.1 Adding a User-Defined Counter

According to the existing measurement counters, this describes how to define a user-required measurement counter by using the arithmetic.
Prerequisite
Context
l
You can set user-defined counters for different measurement function sets instead of object types. User-defined counters supports nested setting. That means that a user-defined counter formula can contain user-defined counters. A maximum of three layers are allowed. Recursive setting is not supported. The location function helps you locate the counter by searching for keyword of the counter name. After the creation of a user defined counter, this counter is displayed in the table in the User-defined Counter Management window. You can create user defined counters in batch by 6.5.3 Importing a User-Defined Counter. This window does not close after you create a user defined counter successfully. When creation failed, the system displays a corresponding prompt.
6-40
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click Defined Counter Management window. Step 2 Expand the navigation tree. Select a node. Step 3 Click ADD. The ADD User-Defined Counter dialog box is displayed. Step 4 Enter the name of user-defined counter in Counter Name. Step 5 Select the function set and function subset of the user-defined counter in Function Set and Function Subset drop-down list.
NOTE
to view the User-
The function set and function subset of the user-defined counter depends on the selected values in the dropdown list rather than the function set and function subset of the selected counter format.
Step 6 Edit the calculation formula in Formula Information. The specific operations are as follows: Double-click a counter in Available Counter List. You can add the counter to Formula Information. Click an operation symbol in the right part of the table. You can also add the operation symbol to Formula Information. To compile a calculation formula, combine the counter with the operation symbol by using an operation rule. Step 7 Select the unit for the user-defined counter in the Unit drop-down box. Step 8 Click OK or Apply. ----End
Related References
6.7.5 Parameters for Adding/Modifying a User-Defined Counter
6.5.2 Modifying a User-Defined Counter

This describes how to modify a user-defined counter. The items counter name, unit, and formula can be modified.
Prerequisite
Context
l
The user-defined counters and all the related original counters must belong to the same measurement function set. You can open the Modify User-Defined Counter dialog box by double-clicking the userdefined counter you want to modify.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click Defined Counter Management window.
Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
to view the User-
6-41
Step 2 Select the user-defined counter to be modified.

NOTE
To switch to the Measurement Settings tab in the Measure Management window, right-click the counter information and choose Measurement Settings on the shortcut menu.
Step 3 Right-click the counter and choose Modify on the shortcut menu, or click Modify, to view the Modify User-Defined Counter dialog box. Step 4 Set the counter parameters. Step 5 Click OK or Apply. ----End
Related References
6.5.3 Importing a User-Defined Counter

This describes how to create a user-defined counter easily by importing the corresponding information from an .XML file.
Context
l
The .XML file to be imported is obtained through the export of user-defined counters to an .XML File. By importing and exporting user-defined counter information, you can copy the userdefined counter easily among multiple M2000 systems.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click Defined Counter Management window. Step 2 Click Import. In the displayed Open dialog box, select an XML file. Step 3 Click Open to import the user defined counter information. An .XML file may contain information about multiple user defined counters. If the user-defined counter in the file has the same name and belongs to the same measurement object with an existing counter in the system, the system does not import this file and displays a corresponding prompt at the same time. ----End to view the User-
6.5.4 Exporting a User-Defined Counter

In the M2000, you can export the latest user defined counter information into an .XML file. Accordingly, you can import the user-defined counter information from the .XML file if required.
6-42
Issue 06 (2008-12-16)
Context
l
The information about multiple user defined counters under different measurement units can be saved in the same file. Press Shift or Ctrl to select multiple user-defined counters. The user-defined counter information can only be saved as the XML file. By importing and exporting user-defined counter information, you can copy the userdefined counter easily among multiple M2000 systems.
l l l
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click Defined Counter Management window. to view the User-
Step 2 Select the user-defined counters for which you want to export the information. Step 3 Click Export or right-click the counter and choose Export on the shortcut menu. The Save dialog box is displayed. Step 4 Select the save path. Enter the file name. Step 5 Click Save. The displayed Message dialog box displays whether the export is successful. Step 6 Click OK to close the Message dialog box. ----End
6.6 Managing Counter Thresholds

During different periodic measurement, the M2000 provides the counter value threshold alarm to automatically monitor key performance counters and currently measured extension counters. You can set the alarm threshold of every periodic measurement based on actual situations including setting the simple alarm threshold for a single counter and for the combined counters after logic or arithmetic operations.
Context
For customized counters, the function of alarm threshold settings is not provided. 6.6.1 Setting a Simple Counter Threshold Simple threshold is a threshold defined for a single counter. You can set a simple threshold for all the objects under a measurement unit. You can also set a simple threshold for some objects of a specific NE under a certain measurement unit. When the measurement counter value exceeds the threshold, a threshold alarm is generated. 6.6.2 Setting a Combined Counter Threshold Combined threshold indicates setting the threshold value for the counters after logic or arithmetic operations. You can set a combined threshold for all the objects under a measurement unit. You can also set a combined threshold for some objects of a specific NE under a certain measurement unit. When the measurement counter values meet the alarm triggering condition for successive periods, a threshold alarm is generated. When the measurement counter values meet the alarm clearance condition for successive periods, the threshold alarm is cleared automatically. 6.6.3 Modifying a Counter Threshold
After adding a threshold, you can modify the set simple threshold based on the actual situation. When modifying a threshold, you are not allowed to modify the threshold type. 6.6.4 Modifying a Combined Counter Threshold This topic describes how to modify the threshold for a combined counter. You can modify the threshold for a combined counter based on demands. The system, however, does not allow the modification of the threshold type. 6.6.5 Activating/Deactivating a Counter Threshold You can suspend a threshold when it is not used temporarily, and then activate it if required.
Related Concepts
Related References
6.7.3 Interface Description: Threshold Management
6.6.1 Setting a Simple Counter Threshold

Simple threshold is a threshold defined for a single counter. You can set a simple threshold for all the objects under a measurement unit. You can also set a simple threshold for some objects of a specific NE under a certain measurement unit. When the measurement counter value exceeds the threshold, a threshold alarm is generated.
Context
l
According to the four alarm levels, you can set four levels of simple thresholds for one counter. If the triggered alarm is not cleared, the same alarm will not be generated again for the same counter . When the system generates an higher level alarm, the lower level alarm will be cleared automatically. On the M2000, the number of simple thresholds and combined thresholds that can be created is limited. The sum of simple thresholds and combined thresholds must be equal to or smaller than 30.
Procedure
Step 1 Choose Performance > Threshold Management, or click Management window is displayed. Step 2 Select a node on the navigation tree. Step 3 Click Add. The Add Threshold dialog box is displayed. Step 4 Modify the threshold parameters. Step 5 Click OK. Step 6 In Threshold Management, confirm the threshold setting information. Step 7 Repeat Step 3 toStep 6 to set other thresholds. Step 8 Click Close to close Threshold Management. ----End
. The Threshold
Related Concepts
6.1.6 Performance Counter Thresholds 6.1.6 Performance Counter Thresholds 6.1.6 Performance Counter Thresholds
Related References
6.7.12 Parameters for Setting a Simple Counter Threshold 6.7.12 Parameters for Setting a Simple Counter Threshold 6.7.12 Parameters for Setting a Simple Counter Threshold
6.6.2 Setting a Combined Counter Threshold

Combined threshold indicates setting the threshold value for the counters after logic or arithmetic operations. You can set a combined threshold for all the objects under a measurement unit. You can also set a combined threshold for some objects of a specific NE under a certain measurement unit. When the measurement counter values meet the alarm triggering condition for successive periods, a threshold alarm is generated. When the measurement counter values meet the alarm clearance condition for successive periods, the threshold alarm is cleared automatically.
Context
On the M2000, the number of simple thresholds and combined thresholds that can be created is limited. The sum of simple thresholds and combined thresholds must be equal to or smaller than 30.
Procedure
Step 1 Choose Performance > Threshold Management, or click Management window is displayed. Step 2 Select a node on the navigation tree. Step 3 Click Add. The Add Threshold dialog box is displayed. Step 4 In the Add Threshold dialog box, select Combined under Threshold Type. Step 5 Under Combined Condition, set Alarm Level, Triggering, and Recovering. Step 6 Under Advanced Setting, set the times of the conditions for triggering alarms and recovering alarms, that is, if the times for which triggering or recovering conditions are fulfilled reach this value, alarms are triggered or cleared. By default, the times of the conditions for triggering alarms and recovering alarms are both one. Step 7 Optional: Under Advanced Setting, you can set whether to raise the alarm severity if the times for which alarms of the same severity are generated reach the specified value. Step 8 Click OK. Step 9 In Threshold Management, confirm the threshold setting information. Step 10 Repeat Step 3 toStep 9 to set other combined thresholds.
. The Threshold
Step 11 Click Close to close Threshold Management. ----End
6.6.3 Modifying a Counter Threshold

After adding a threshold, you can modify the set simple threshold based on the actual situation. When modifying a threshold, you are not allowed to modify the threshold type.
Context
l
According to the four alarm levels, you can set four levels of simple thresholds for one counter. If the triggered alarm is not cleared, the same alarm will not be generated again for the same counter . When the system generates an higher level alarm, the lower level alarm will be cleared automatically.
Procedure
Step 1 Choose Performance > Threshold Management, or click Management window is displayed. Step 2 Select a node on the navigation tree.
NOTE
. The Threshold
If Show all Threshold information is selected, all the thresholds are listed. If this option is not selected, only those of selected nodes are listed.
Step 3 Choose the simple threshold you want to modify. Step 4 Click Modify or right-click and choose Modify to display the Modify Threshold dialog box. Step 5 Modify the threshold parameters. Step 6 Click OK. Step 7 In Threshold Management, confirm the threshold setting information. Step 8 Repeat Step 4 toStep 7 to modify other thresholds. Step 9 Click Close to close Threshold Management. ----End
Related Concepts
Related References
6.7.12 Parameters for Setting a Simple Counter Threshold 6.7.12 Parameters for Setting a Simple Counter Threshold 6.7.12 Parameters for Setting a Simple Counter Threshold
6.6.4 Modifying a Combined Counter Threshold

This topic describes how to modify the threshold for a combined counter. You can modify the threshold for a combined counter based on demands. The system, however, does not allow the modification of the threshold type.
Procedure
Step 1 Select Performance > Threshold Management or click Management window is displayed. Step 2 Select a node on the navigation tree.
NOTE
, and then the Threshold
If you select Show all Threshold Information, all threshold records will be listed in the table. If this option is not selected, the threshold record of the selected node is listed.
Step 3 Select the combined threshold setting to be modified. Step 4 Click Modify or right-click Modify. The Modify Threshold window is displayed. Step 5 In the Modify Threshold window, modify the threshold parameters. Step 6 Click OK to finish the modification of the combined threshold. Step 7 In the Threshold Management window, confirm the modification information of the threshold. Step 8 If you need modify other combined thresholds, repeat Step 3 till Step 7. Step 9 Click Close to close the Threshold Management. ----End
6.6.5 Activating/Deactivating a Counter Threshold

You can suspend a threshold when it is not used temporarily, and then activate it if required.
Procedure
Step 1 Choose Performance > Threshold Management, or click The Threshold Management window is displayed. Step 2 Select a node on the navigation tree.
NOTE
If Show all threshold information are selected, all the thresholds are listed in the table. If this option is not selected, only the thresholds of selected nodes are listed.
Step 3 Choose the threshold that you want to suspend or resume. Step 4 Click Suspend or Resume, or right-click and choose Suspend or Resume. ----End
6.7 Reference for Performance Management Interfaces

This part describes the following interfaces of performance management: query result interface, measure management interface, threshold management interface, customer counter interface, and Performance Monitor interface. 6.7.1 Interface Description: Query Result This part introduces the Query Result interface of performance management. 6.7.2 Interface Description: Measure Management This describes the Measure Management interface of performance management. 6.7.3 Interface Description: Threshold Management This part introduces the Threshold Management interface of performance management. 6.7.4 Interface Description: User-defined Counter Management This topic describes the User-defined Counter Management interface of performance management. 6.7.5 Parameters for Adding/Modifying a User-Defined Counter This describes the parameters on the ADD User-Defined Counter or Modify User Defined Counter window. 6.7.6 Parameters for Setting the Conditions for Filtering Result This part introduces the parameters in Set Counter Filter Condition. 6.7.7 Parameters for Querying Missing Measurement Results This part introduces parameters for querying measurement result of missing NEs. 6.7.8 Parameters for Querying the Reliability of Measurement Results This part introduces parameters for querying measurement result reliability. 6.7.9 Parameters for Setting the Mode of Sorting Displayed Results This part introduces parameters for setting the sequence of the result display. 6.7.10 Parameters for Setting a Background Color for a Measurement Results Chart This describes the parameters for setting the background color of a line chart or bar chart in the Query Result window. 6.7.11 Parameters for Synchronizing NE Measurement Results This part introduces parameters for synchronizing NE measurement results. 6.7.12 Parameters for Setting a Simple Counter Threshold This topic describes related parameters for setting simple counter thresholds. You can refer to these parameters when you set the simple counter threshold. 6.7.13 Parameters for Setting a Combined Counter Threshold This topic describes parameters for setting a combined threshold for a counter. You can refer to these parameters when you set a combined threshold for a counter. 6.7.14 Parameters for Setting Threshold Alarm Triggering or Restoration This part describes the parameters in the Set Triggering Conditions dialog box and the Set Recovering Conditions dialog box. 6.7.15 Parameters for Specifying the Time Range of Results This part introduces parameters for setting the time range of specified results.
6.7.16 Parameters for Measurement States of Measurement Objects and Counters This part introduces parameters of setting measurement objects and measurement counters.
6.7.1 Interface Description: Query Result

This part introduces the Query Result interface of performance management. The Query Result interface is shown in Figure 6-3, Figure 6-4, Figure 6-5. Figure 6-3 Query result interface - 1
Figure 6-4 Query result interface - 2
Issue 06 (2008-12-16)
6-49
Figure 6-5 Query result interface - 3
Table 6-2 describes each part on the interface. Table 6-2 Interface description No. (1) (2) (3) (4) (5) Name Navigation tree Table Operation bar Line Chart Bar Chart Description Refers to the navigation tree. Display measurement results in table. Provides some operation buttons, such as New Query, Condition. Display measurement results in line chart. Display measurement results in bar chart.
Related Concepts
Related Tasks
6.3 Querying Performance Measurement Results
6.7.2 Interface Description: Measure Management

This describes the Measure Management interface of performance management. The Measure Management interface is shown in Figure 6-6 and Figure 6-7.
Figure 6-6 Measure management interface - 1
Figure 6-7 Measure management interface - 2
Table 6-3 describes each part on the interface.

Table 6-3 Interface description No. (1) (2) (3) Name Navigation tree Measurement Status tab Measurement Settings tab Description Refers to the navigation tree. Displays measurement status. You can modify measurement settings.
6.7.3 Interface Description: Threshold Management

This part introduces the Threshold Management interface of performance management. The Threshold Management interface is shown in Figure 6-8. Figure 6-8 Threshold management interface
Table 6-4 describes each part on the interface. Table 6-4 Interface description No. (1) (2) (3) Name Navigation tree Content window Operation bar Description Refers to the navigation tree. Displays operation results. Provides the following operations: Add, Modify, Delete, and Suspend.
Issue 06 (2008-12-16)
6-52
Related Concepts
Related Tasks
6.6 Managing Counter Thresholds
6.7.4 Interface Description: User-defined Counter Management

This topic describes the User-defined Counter Management interface of performance management. The User-defined Counter Management interface is shown in Figure 6-9. Figure 6-9 User-defined counter management interface
Table 6-5 describes each part on the interface. Table 6-5 Interface description No. (1) (2) (3) Name Navigation tree Content window Operation bar Description Refers to the navigation tree. Displays operation results. Provides the following operations: Add, Modify, Delete, Meas Settings, Import, Export, and Close
Related Tasks
6.5 Managing User-Defined Counters

This describes the parameters on the ADD User-Defined Counter or Modify User Defined Counter window.
parameter CounterName Value Range 100 characters at most. Cannot be null. Enumeration. Default value is %. Description The name of a user defined counter is used to defined this counter. A meaningful name is recommended. Units of the existing counters are available. You can select a unit from the drop-down list. You need to select a unit according to the meaning of the user defined counter. For example, if a user defined counter measures the times of the occurrence, the unit can be times. The unit specified for a user defined counter is for referenced purpose only. It does not affect the calculation of the counter. Formula for the user defined counter.
Unit
Triggering/ Recovering Conditions
255 characters at most. Cannot be null.
Related Tasks
6.5.1 Adding a User-Defined Counter 6.5.2 Modifying a User-Defined Counter
6.7.6 Parameters for Setting the Conditions for Filtering Result

This part introduces the parameters in Set Counter Filter Condition.
Parameters
Parameter Counter name Value range All measurement counters of the selected measurement object ">",">=","=","<" and "<=" Description Select in the drop-down list the name of the counter for which the filter condition is to be set. For comparing the actual value and the compare value of the measurement counter. Compare Value -999999999.99 to 999999999.99 The measurement counter value set as the filter condition.
Issue 06 (2008-12-16)
Compare operator
Compare value
-999999999.99 to 999999999.99
6-54
Parameter Logical operator
Value range AND, OR and None
Description The logical relationship between the set filter conditions. none indicates that the filter condition is the last logical condition.
Related Tasks
6.3.5.7 Setting the Conditions for Filtering Result Counters
6.7.7 Parameters for Querying Missing Measurement Results

This part introduces parameters for querying measurement result of missing NEs.
Parameters
Parameter Start Date Time Value range 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time-12hours End Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time The end time for querying the missing results. Description The start time for querying the missing results.
Related Tasks
6.2.6 Querying Missing Measurement Results
6.7.8 Parameters for Querying the Reliability of Measurement Results

This part introduces parameters for querying measurement result reliability.
Parameters
Parameter Start Date Time Value range 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time-12hours End Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time Description The start time for querying the measurement result reliability. The end time for querying the measurement result reliability.
Related Tasks
6.2.5 Querying the Reliability of Measurement Results
6.7.9 Parameters for Setting the Mode of Sorting Displayed Results

This part introduces parameters for setting the sequence of the result display.
Parameters
Parameter Primary Key Second Key Third Key Fourth Key Fifth Key Value range
l l l
Description To sort the queried measurement results according to the priority. l Object: The measurement results are sorted and displayed by the names of the measurement objects. l Time: The queried results are sorted and displayed by time. l If you select "None", the queried results are sorted and displayed by time in an ascending order.
Object Time None
Related Tasks
6.3.5.6 Setting the Mode of Sorting Displayed Results
6.7.10 Parameters for Setting a Background Color for a Measurement Results Chart
This describes the parameters for setting the background color of a line chart or bar chart in the Query Result window.
Parameters
Related Tasks
6.3.6.4 Setting the Background Color of a Chart
6.7.11 Parameters for Synchronizing NE Measurement Results

This part introduces parameters for synchronizing NE measurement results.
6-56
Issue 06 (2008-12-16)
Parameters
Parameter Start Date Time Value range 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time-1hours End Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 (yyyy=current year+10) Default value: current time Description The start time for synchronizing NE measurement results. The end time for synchronizing NE measurement results.
Related Tasks
6.2.3 Synchronizing NE Measurement Results
6.7.12 Parameters for Setting a Simple Counter Threshold

This topic describes related parameters for setting simple counter thresholds. You can refer to these parameters when you set the simple counter threshold. Table 6-6 Simple Threshold Parameters Parameter Object List Value Range Enumeration. Including all the measurement objects under this measurement unit. Description You can set a simple threshold for all objects and for one or more objects. On the M2000, the number of objects in the threshold setting is limited. The number of objects that can be selected is smaller than 800. Name of the simple counter with the threshold to be set. After you select the Function Subset, click the drop-down list afterCounter Name, and then select the counter to set the threshold.
CounterName
Enumeration. Including key performance counters and currently measured extension performance counters in the measurement unit.
Direction
Enumeration. IncludingIncreasing and Decreasing.
Value,Hysteresis and Direction together determine the threshold value of a simple counter. Assume the Threshold as 50, the Offset as 5, the Direction as Increasing, when the value of the real measurement result reaches 55, that is 50 +5, the system deems this counter exceeds the value range.
Issue 06 (2008-12-16)
6-57
Parameter Status
Value Range Enumeration. IncludingActivate and Inactive.
Description This parameter determines whether to activate the threshold alarm when the counter value exceeds the value range.
l l
Active means "to activate the alarm". Inactive means "not to activate the alarm".
Time
00:00 to 23:59
Both the start time and the end time, indicating in which time segment of a day this performance threshold setting is valid. This means to set the threshold for which of the 5-Minute, 15-Minute, 30-minute, 60-minute and 24-hour periodic measurements. This means on which day of a week the threshold setting is valid.
Measure Period
5 Minutes,15 Minutes,30 Minutes,60 Minutesand24 Hours. Monday,Tuesday,Wednesda y,Thursday,Friday,Saturday ,Sunday,All. That is, all days are valid. Number
Day
Threshold
Counter Value,Hysteresis and Direction together determine the threshold value of a simple counter. Assume the Threshold as 50, the Offset as 5, the Direction as Increasing, when the value of the real measurement result reaches 55, that is 50 +5, the system deems this counter exceeds the value range.
Offset
Number
Offset of a counter value Value,Hysteresis and Direction together determine the threshold value of a counter. Assume the Threshold as 50, the Offset as 5, the Direction as Increasing, when the value of the real measurement result reaches 55, that is 50 +5, the system deems this counter exceeds the value range.
Level
Enumeration. The alarm level includesCritical,Major,Mino r, andWarning.
Level of the threshold alarm.
6-58
Issue 06 (2008-12-16)
Parameter Threshold Name
Value Range Including numbers, 26 English letters and any other special characters besides ! Name of the Combined Threshold
Description Name of this simple threshold. The name does not conflict with the existing threshold name. The maximum length is 255 bytes.
Related Concepts
Related Tasks
6.6.1 Setting a Simple Counter Threshold 6.6.3 Modifying a Counter Threshold 6.6.1 Setting a Simple Counter Threshold 6.6.3 Modifying a Counter Threshold 6.6.1 Setting a Simple Counter Threshold 6.6.3 Modifying a Counter Threshold
6.7.13 Parameters for Setting a Combined Counter Threshold

This topic describes parameters for setting a combined threshold for a counter. You can refer to these parameters when you set a combined threshold for a counter.
Parameter Object List Value Range Enumeration. indicates all the measurement objects under this measurement unit. Description The combined threshold can be set for all objects. You can also set the combined threshold for one or multiple objects. On the M2000, the number of objects in the threshold setting is limited. The number of objects that can be selected is smaller than 800. This parameter determines whether to activate the threshold alarm when the counter value exceeds the value range.
l l
Status
Enumeration. IncludingActivate and Inactive.
Active means "to activate the alarm". Inactive means "not to activate the alarm".
Issue 06 (2008-12-16)
6-59
Parameter Time
Value Range 00:00 to 23:59
Description Both the start time and the end time, indicating in which time segment of a day this performance threshold setting is valid. This parameter indicates for which period measurement this threshold setting is applied. This means on which day of a week the threshold setting is valid.
Measure Period
5 Minutes,15 Minutes,30 Minutes,60 Minutesand24 Hours. Monday,Tuesday,Wednesda y,Thursday,Friday,Saturday ,Sunday,All(indicating that all days are valid). Click Set Triggering conditions, and then set the conditions in the Modify Triggering Conditions dialog box. Click Set Recovering conditions, and then set conditions in the Set Recovering conditions dialog box. Number
l
Day
Triggering Conditions
Indicates the triggering conditions of this threshold alarm. For detailed parameter description, refer to 6.7.14 Parameters for Setting Threshold Alarm Triggering or Restoration. Indicates the recovering conditions of this threshold alarm. For detailed parameter description, refer to 6.7.14 Parameters for Setting Threshold Alarm Triggering or Restoration. You can set the times for which the triggering conditions or the recovering conditions are fulfilled. You can also raise the alarm severity when the times for which alarms of the same severity are generated reach a certain value.
Recovering Conditions
Advanced Setting
Indicates the times for which the triggering conditions are fulfilled, and the value ranges from 1 to 10 inclusive. Indicates the times for which the recovering conditions are fulfilled, and the value ranges from 1 to 10 inclusive. Indicates the times for which alarms of the same severity are generated, and the value ranges from 2 to 10 inclusive. When multiple threshold alarms of the same severity are generated, the alarm severity will be raised.
Level
Enumeration. The alarm level includesCritical,Major,Mino r, andWarning.
Level of the threshold alarm.
6-60
Issue 06 (2008-12-16)
Parameter Threshold Name
Value Range Including numbers, 26 English letters and any other special characters besides ! Name of the Combined Threshold
Description Name of this combined threshold. The name does not conflict with the existing threshold name. The maximum length is 255 bytes.
6.7.14 Parameters for Setting Threshold Alarm Triggering or Restoration

This part describes the parameters in the Set Triggering Conditions dialog box and the Set Recovering Conditions dialog box.
Parameter Triggering/ Recovering Conditions Value Range A maximum of 255 bytes are allowed. Description This parameter is an expression for the arithmetic and logical operation of the selected user-defined counters or original counters. The value must be of Boolean type. You can double-click a counter in Optional counter list. or enter the counter name to edit the formula. Note that you must add [] around the counter name.
NOTE In the counter list, you can select the counters of a maximum of N function subsets to perform the algorithm, where N is smaller than 3. This algorithm is the condition for restoring a threshold alarm.
Filter by Counter Name Filter by Counter Type
None.
Search for the counters by counter name and list the counters in Optional counter list. Search for the counters by counter type and list the counters in Optional counter list.
You can select All, Default Counter, Extended Counter, or User-defined Counter.
6.7.15 Parameters for Specifying the Time Range of Results

This part introduces parameters for setting the time range of specified results.
Issue 06 (2008-12-16)
6-61
Parameters
Parameter Time Mode Value range
l l l
Description
l
Continuous Time Section Time Busy Time
Continuous Time: To query the measurement results within a consecutive time period. For example, to query the measurement results within the period from 2005-03-05 10:10 to 2005-03-10 11:15. Section Time: To query the measurement results for separate time segments. This time mode applies to querying results for the period with high traffic. For example, to query the measurement results for the period from 10:10 to 11:15 every day from 2005-03-05 to 2005-03-10. Busy Time: To query the measurement results by busy time.
Date Range
All, Specific, Today, Yesterday, This Week and Last Week
The time range for querying the measurement results.

l
All: To query all the measurement results. Specific: To query the measurement results for the specified time segment. You can set the Start Time and the End Time.
Related Tasks
6.3.5.4 Specifying the Time Range of Results

This part introduces parameters of setting measurement objects and measurement counters.
6-62
Issue 06 (2008-12-16)
Table 6-7 Counter Measurement Status Parameter CounterName Measurement status Status description Description All the counters under a measurement unit of an NE that are currently measured. The measurement status of the counters. The detailed description of the measurement status of the counters.
Table 6-8 Object measurement status Parameter Object name Measurement status Status description Description All the objects under a measurement unit of an NE that are currently measured. The measurement status of the objects. The detailed description of the measurement status of the objects.
NOTE
l l
If you select All, then all the added measurement objects will be measured automatically. On a 3G network the number of neighbor objects must be equal to or smaller than 900, and the number of cell objects must be equal to or smaller than 900. On a 2G network the total number of neighbor objects and cell objects must be equal to or smaller than 700.
Related Tasks
6.4.1 Querying Measurement Objects 6.4.2 Querying Measurement Counters
Issue 06 (2008-12-16)
6-63
7 Performance Report Management
Performance Report Management
About This Chapter

The M2000 provides the function of performance report management. You can set the query conditions of system reports and custom reports on the GUI. The M2000 can display the queried performance report on the report query interface. By analyzing the report data, you can obtain the information about the performance of each NE. You can also manage KPIs, such as create, modify, and delete KPIs on the KPI management interface. 7.1 Basic Knowledge of Performance Report Management The M2000 can summarize the performance counter data of single NEs and generate performance reports. 7.2 Managing Performance Reports The performance report template can be a system performance report template or a custom performance report template. In the performance management window on the GUI, you can select a performance report template, set the query conditions to generate the required performance report, and then save the required query settings to a new report template. This facilitates later queries. In addition, you can set report relations, filter, save, and print reports, and set the display mode. 7.3 Managing KPIs Key performance indicators (KPIs) are categorized into system KPIs and custom KPIs. The M2000 enables you to manage KPIs, such as browse and filter KPIs, and set display conditions. You can also set custom KPIs based on your requirement. Custom KPIs are defined on the basis of system KPIs and the defined KPIs. They are used for setting custom reports. 7.4 MSC Server Performance Reports The MSC Server performance report group is used to query the traffic and some services of the MSC Server. This report group includes MSC basic traffic report, MSC Mobility management report, CPU load report, office direction traffic report, signaling link report, and trunk group report in a specified period. 7.5 MSC POOL Report Group Pool report group summarizes the measurement results of the counters on each MSC server within an MSC Pool in a specified period. After the measurement range is specified on the M2000, the NEs report the measurement results to M2000 with the interval of 30 minutes. By querying a Pool report, you can obtain the traffic, number of users, and services, which can serve as reference for routine maintenance.
7.6 MSCe Pool Report Group This describes the MSCe Pool report. The pool report group summarizes the measurement results of the counters of each MSCe within a MSCe Pool in a specified period. After the measurement range is specified through the M2000, the NEs report the measurement results with the interval of 60 minutes. By querying the pool report, you can obtain the traffic, number of users, and services, which can serve as reference for routine maintenance and network adjustment. 7.7 RNC Performance Reports The RNC performance report group is used to query RNC traffic and some services in a specified period. This report group includes RNC report and cell report group. The RNC report includes coverage Report, accessibility report, retainability report, mobility report, service integrity report, availability report, and traffic report. The RNC report includes coverage report, accessibility report, retainability report, mobility report, service integrity report, availability report, and traffic report. 7.8 PCU Performance Reports The PCU performance reports consist of data throughput report, transmission report, accessibility report, availability report, and retainability report. 7.9 Reference for Performance Report Management Interfaces This describes the performance report management interfaces and the related parameters. You can obtain the information about the functions and thus perform the related operations.
7-2
Issue 06 (2008-12-16)
7.1 Basic Knowledge of Performance Report Management

The M2000 can summarize the performance counter data of single NEs and generate performance reports. The system sets the performance counters to be extracted and the related rules. Then, the system periodically extracts and summarizes the counters based on the defined period and then saves the result in the database. The M2000 extracts and summarizes the data of the performance counter of an NE and then generates a performance report. The M2000 summarizes the key performance data of all NEs, such as time dimension and object dimension. You can set the duration for storing the performance data related to each service. You can query the performance data within the duration range in the report database. You can set the busy hour rule of performance data, such as the time range, expression, and calculation rule of the busy hour data. You can query the busy hour data according to the busy hour rule. In the rule: Where,
l l l
Specified indicates that you can define any hour as the busy hour. Daily indicates that the busy hour is the busiest hour in the specified Period. Weekly and Monthly relate to the average busy hour. To get the value, the system equally divides the specified Period each day in a week or month into segments with the duration as one hour, and summarizes the data of the same segment. The busiest time segment becomes the weekly busy hour or monthly busy hour.
Key performance indicators (KPIs) are categorized into system KPIs and custom KPIs. The custom KPI is defined according to the system KPI and defined KPIs. When system KPIs cannot meet your requirement, you can create custom KPIs. When predefined reports cannot meet your requirement, M2000 allows you to create performance reports as required. In addition, you can define sub-reports and the style of each data table of the sub-reports. The system can generate performance reports in tables and figures, which can be printed or saved to files. You can re-configure the time for saving data as required.
7.2 Managing Performance Reports

The performance report template can be a system performance report template or a custom performance report template. In the performance management window on the GUI, you can select a performance report template, set the query conditions to generate the required performance report, and then save the required query settings to a new report template. This facilitates later queries. In addition, you can set report relations, filter, save, and print reports, and set the display mode. 7.2.1 Generating a Performance Report This describes how to generate a performance report. Based on a condition template or the query conditions set in real time, the M2000 can generate a performance report for the data queried in the report database. 7.2.2 Setting a Template for Querying Performance Reports
This describes how to set a condition template for querying performance reports. You can save the related query rules as a query condition template. This facilitates future queries. 7.2.3 Filtering the Contents of a Performance Report This describes how to set filter conditions during the report data check. The report data that meets the filter conditions is displayed. And the report data that does not meet the filter conditions is shielded. 7.2.4 Setting the Display of a Performance Report Based on Conditions This describes how to set the display of a performance report based on conditions. The counter data that meets the condition is highlighted in the foreground color and background color. 7.2.5 Displaying a Performance Report in a Sequence Chart This describes how to display a performance report in a sequence chart. You can choose to display the counters of one object or the same counter of different objects in a sequence chart. This facilitates query and comparison. 7.2.6 Displaying a Performance Report in a Comparison Chart This describes how to display a performance report in a comparison chart. The system can display multiple objects and counters at one time point in the same comparison chart. This facilitates query and comparison. 7.2.7 Setting a Related Report This describes how to set a related report. The M2000 enables you to set related reports for performance reports of the same object type. In this way, when you query the related reports, the query conditions are consistent with those of the original reports. You can also modify the settings. 7.2.8 Viewing the Attributes of a Performance Report Template This describes how to view the attributes of a performance report template to obtain the information about the report, such as report name, report type, object type, creator, creation time, and modification time. The M2000 provides the function of viewing the attributes of a performance report. 7.2.9 Saving a Performance Report This describes how to save a performance report. The M2000 client enables you to save required information in a certain format when you are querying the report data. This facilitates query and browsing. 7.2.10 Printing a Performance Report This describes how to print a performance report. The M2000 client enables you to print required information in a certain format when you are querying the report data. 7.2.11 Managing a Custom Performance Report Template This describes how to manage the M2000 custom performance report template. This function is used in case that the provided performance report templates cannot meet your requirement. On the M2000 client, you can save a performance report as a report template so that it can be repeatedly used to query performance data. This function allows you to create custom, modify, and delete performance report templates and set the sub-reports of a custom performance.
7.2.1 Generating a Performance Report

This describes how to generate a performance report. Based on a condition template or the query conditions set in real time, the M2000 can generate a performance report for the data queried in the report database.
7-4
Issue 06 (2008-12-16)
Prerequisite
l l l l
You have logged in to the M2000 client. The DS and the RS run properly. The performance data of a certain time period exists in the database. You are authorized to browse reports.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 In the navigation tree, double-click a report template. Alternatively, right-click the report template and choose Query from the shortcut menu. The Report Condition Setting dialog box is displayed. Step 3 Set Time Dimension, Data Selection, Time Segment Selection, Object Dimension, and Object Range.
NOTE
l l
If condition templates are available, you can select one from the Select Template drop-down list. For information on saving the query conditions that are set this time as the template, see 7.2.2 Setting a Template for Querying Performance Reports.
Step 4 Click Query. The system displays the performance data that meets query conditions in the detailed lists to the right of the navigation tree. The number of results is displayed in the right corner of the window. The results can be displayed on multiple pages. You can click previous page, or
NOTE
to view the data on the
to view the data on the next page.
The query results are displayed on multiple tab pages. The names of level 1 tabs are consistent with those of the report templates, that is, the nodes in the navigation tree. The names of level 2 tabs are consistent with those of the sub-reports. If a report has only one sub-report, only the tab of this report is displayed. A maximum of five reports can be displayed at the same time. Select a tab, right-click it and select Close to close a primary tab.
----End
Postrequisite
You can filter, display based on conditions, correlation query, save, and print the generated performance reports.
Related References
7.9.2 Parameters for Setting Conditions for Querying Performance Reports
7.2.2 Setting a Template for Querying Performance Reports

This describes how to set a condition template for querying performance reports. You can save the related query rules as a query condition template. This facilitates future queries.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to manage reports.
Context
You can create a new query template in the Set report conditions window, modify the existing template, or delete the template that is no longer used.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 In the navigation tree, double-click the report template to be operated. Alternatively, right-click the report template and choose Query from the shortcut menu. The Report Condition Setting dialog box is displayed. Step 3 You can create a condition template, modify the properties of a condition template, or delete a condition template.
l
To create a condition template, perform the following steps: 1. Set each parameter in the dialog box. See 7.9.2 Parameters for Setting Conditions for Querying Performance Reports for details. 2. 3. Click Save Template. The Please enter a template name dialog box is displayed. Enter a template name that is different from existing names. Click OK. In the Select template drop list of the Set report conditions dialog box, select a template name. After re-setting each property value, click Save template. Click OK. The properties of the template are modified. In the Select template drop list of the Set report conditions dialog box, select a template name. Click Delete template. In the displayed Confirm dialog box, click Ok. The template is deleted.
To modify the attributes of a condition template, perform the following steps: 1. 2. 3.
To delete a condition template, perform the following steps: 1. 2. 3.
----End
Related References
7.2.3 Filtering the Contents of a Performance Report

This describes how to set filter conditions during the report data check. The report data that meets the filter conditions is displayed. And the report data that does not meet the filter conditions is shielded.
Prerequisite
l l l
You have logged in to the M2000 client. The required performance report has been generated. You are authorized to browse reports.
Context
The configuration of filtering conditions has two levels:
l
The first level relates to the configuration of query conditions. For details, refer to 7.2.1 Generating a Performance Report. The second level relates to the configuration of filtering conditions for generated performance reports.
Procedure
Step 1 In the Performance Report window, select a tab. Step 2 Right-click the report data or the blank area and choose Filter from the shortcut menu. The Filter Condition dialog box is displayed. If you need to set TopN or BottomN reports, click TopN to view the TopN dialog box.
NOTE
You can set filtering conditions only for a report that uses the common style.
Step 3 Set Comparison Column, Comparison Symbol, Value, and Relation.

l
For detailed parameter description, refer to 7.9.3 Parameters for Setting Filter Conditions for Performance Reports. When setting TopN or BottomN reports, you can define the value of N. TopN report is used to query the conditions of N counters which have top counter values. BottomN report is used to query the conditions of N counters which have bottom counter values. TopN (%) report is used to query the conditions of N% counters which have top counter values. BottomN (%) report is used to query the conditions of N% counters which have bottom counter values. If you need to add a format condition, click Add, and then set parameters in theComparison Column, Comparison Symbol, Value, and Relation. If you need to delete a filter condition, click Delete after selecting a condition. Click Yes in the Confirm dialog box.
l l
Step 4 Click OK. The performance data that meets the filter conditions is displayed in the detailed list. The data that does not meet the filter conditions is shielded. ----End
Postrequisite
For the performance report whose filtering conditions are already set, you can right-click the list area, and then select Cancel Filter from the shortcut menu to cancel the set filtering conditions.
Related References
7.9.3 Parameters for Setting Filter Conditions for Performance Reports
7.2.4 Setting the Display of a Performance Report Based on Conditions

This describes how to set the display of a performance report based on conditions. The counter data that meets the condition is highlighted in the foreground color and background color.
Prerequisite
l l l
Context
You can set the display format of one or multiple counters in a report. The settings do not take effect after the report is closed. You can also set the display format through KPI management. The settings in this way apply to all reports. That is, when you use the report template that contains the defined KPIs to generate reports, the counters are displayed in the format that you have configured. For details, refer to 7.3 Managing KPIs.
Procedure
Step 1 In the Performance Report window, select a tab. Step 2 Right-click the report data or the blank area and choose Format Setting from the shortcut menu. The Format Setting dialog box is displayed. Step 3 Set Counter, Condition, Foreground, and Background. If the selected KPI meets the conditions, the corresponding values are displayed in the defined foreground and background colors. For detailed parameter description, refer to 7.9.4 Parameters for Setting the Condition Display of the KPIs.
l
If you need to add a format setting, click Add, and then set parameters in Counter, Condition, Foreground, and Background.
NOTE
l l l
You can set a maximum of three display modes for one report. For the counter data that meets multiple conditions, the format of the first numbered condition applies.
If you need to delete a format setting, select a condition in the Delete format setting dialog box after clicking Delete. Click OK to delete it. To modify a condition format, you can modify the parameters in the drop-down lists of Counter, Condition, Foreground, and Background.
Step 4 Click OK or Apply.

l l l
If you click OK, the Format setting dialog box is closed and the settings take effect. If you click Apply, the Format setting dialog box is not closed and the settings take effect. If you click Cancel, the settings are not saved.
----End
Result
In the counter field, the counter values are displayed in the defined foreground and background colors. After the report is closed, the setting expires.
Related Tasks
7.3.3 Setting the Display of a KPI Based on Conditions
Related References
7.9.4 Parameters for Setting the Condition Display of the KPIs
7.2.5 Displaying a Performance Report in a Sequence Chart

This describes how to display a performance report in a sequence chart. You can choose to display the counters of one object or the same counter of different objects in a sequence chart. This facilitates query and comparison.
Prerequisite
l l l
Context
l
The series chart by object is used to compare the change tendency in a certain time period of different counters of the same object when they are querying report data. The horizontal coordinate of the generated series chart displays the time of each query. The vertical coordinate displays the counter values. The legend differentiates counters in different colors. The series chart by counter is used to compare the change tendency in a certain time period of the same counters of different objects when they are querying report data. The horizontal coordinate of the generated series chart displays the time of each query. The vertical coordinate displays the counter values. The legend differentiates objects in different colors.
Procedure
Step 1 In the Performance Report window, select a tab. Step 2 Click Show chart. Step 3 Select the Series chart tab. Step 4 Select the series chart by object or by counter according to your requirements. If... Display a sequence chart by object Operation 1. In the Select Object drop list, select an object. 2. In the Select Counter drop list, select one or multiple counters.
Issue 06 (2008-12-16)
7-9
If...
Operation
Display a sequence chart by counter 1. In the Select Counter drop list, select a counter. 2. In the Select Object drop list, select one or multiple objects.
The legend of the series chart is displayed by default. Right-click the series chart and select Legend to hide it. The default background color is white. If you want to set the background color, right-click the series chart and select Background Color. After setting the background color, click OK and the setting completes. To modify the value range of the y-axis, you can right-click in the sequence chart and choose Axis Value Range Setting from the shortcut menu. Then, you can set the value range in the displayed Axis Value Range Setting dialog box. If you select Auto Axis, the value range of the y-axis is automatically adjusted on the basis of all selected counters. If you clear Auto Axis, you can set the value range of the y-axis.
In the Series Charttab, the same counter of different objects or different counters of the same object are displayed in different colors. You can save or print the comparison chart. ----End
Related References
7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance Reports 7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports
7.2.6 Displaying a Performance Report in a Comparison Chart

This describes how to display a performance report in a comparison chart. The system can display multiple objects and counters at one time point in the same comparison chart. This facilitates query and comparison.
Prerequisite
l l l
Context
The comparison chart by object and the one by counter are both used to compare the differences of one or multiple counters of multiple objects at a certain time period when the counters are querying the counter data. The differences of the two comparison charts are as follows:
l
The comparison chart by objects: Objects are used as the reference points to compare counters. For comparison charts by object, objects are used as the reference points to compare counters. The horizontal coordinate of the generated comparison chart displays
7-10
the names of the selected objects. The vertical coordinate displays the selected counter values. The legend differentiates counters in different colors.
l
The comparison chart by counters: Counters are used as the reference points to compare objects. For comparison chart by counter, counters are used as the reference points to compare objects. The horizontal coordinate of the generated comparison chart displays the names of the selected counters. The vertical coordinate displays the selected counter values. The legend differentiates objects in different colors.
Procedure
Step 1 The legend differentiates the selected objects in color. In the Performance Report window, choose a report tab. Step 2 Click Show chart. Step 3 Select the Comparison chart tab. Step 4 Set Select Time. You can select the time from the drop-down list, or click time point relative to the current time. or to select previous or next
Step 5 Choose an object-oriented or index-oriented comparison chart according to your requirements. If... Display a comparison chart by object Then... 1. In the Select Object list box, select one or multiple objects. 2. In the Select Counter list box, select one or multiple counters. Display a comparison chart by counter 1. In the Select Counter list box, select one or multiple counters. 2. In the Select Object list box, select one or multiple objects.
The legend of the comparison chart is displayed by default. Right-click the series chart and select Legend to hide the legend. The default background color is white. If you want to set the background color, right-click the comparison chart and select Background Color. After setting the background color, click OK and the setting completes. To display the value of each counter on the comparison chart, you can right-click in the comparison chart and choose Value Label from the shortcut menu. If you need to display results in a pie chart, you can right-click the comparison chart and choose Pie Chart from the shortcut menu. If you need to display the results in the bar chart, you can right-click the comparison chart and choose Bar Chart By default, the results are displayed in a bar chart.
On the Comparison Chart tab page, relevant counters of different objects are displayed in different colors. You can save or print the comparison chart. ----End
Related References
7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance Reports 7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports
7.2.7 Setting a Related Report

This describes how to set a related report. The M2000 enables you to set related reports for performance reports of the same object type. In this way, when you query the related reports, the query conditions are consistent with those of the original reports. You can also modify the settings.
Prerequisite
l l l
You have logged in to the M2000 client. The required performance report has been generated. You are authorized to manage reports.
Context
For performance reports of the same object type, you can set relation for them if they are associated in the service. This facilitates the query of related reports and improves the query efficiency.
Procedure
Step 1 In the Performance Report window, select a report in the navigation tree. Step 2 Right-click the report and choose Relate Report from the shortcut menu. The Relate Report dialog box is displayed. Step 3 Create or delete a relation as required.
l
To set the relation, perform the following steps: 1. 2. Select the reports that need to be related to this report. Click OK. Clear the report that is related to this report. Click OK.
To delete the relation, perform the following steps: 1. 2.
----End
Postrequisite
After you create a report relation, you can view the relation by performing the following steps: 1. In the report tab, right-click the data or the blank area, and then choose Relation Query > *** from the shortcut menu. *** stands for the report that is related to this report. 2. In the displayed Report Condition Setting dialog box, set Object Rangeand then click Query.
7-12
If the query condition is different from that of the original one, you can modify the query condition and then query. When setting query conditions for related reports, you can modify the level of the summarized objects. You can also upgrade the level of Object Dimension, for example, from Cell to Cell Group. You can also downgrade the level of Object Dimension, for example, from Cell Group to Cell.
7.2.8 Viewing the Attributes of a Performance Report Template

This describes how to view the attributes of a performance report template to obtain the information about the report, such as report name, report type, object type, creator, creation time, and modification time. The M2000 provides the function of viewing the attributes of a performance report.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to browse reports.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 In the navigation tree, right-click the report template of which you plan to view the attributes and choose View Property from the shortcut menu. The Report Property dialog box is displayed. The report attributes consist of basic information and other information. Basic information refers to report name, report type, and object type. Other information refers to creator, creation time, and modification time. ----End
7.2.9 Saving a Performance Report

This describes how to save a performance report. The M2000 client enables you to save required information in a certain format when you are querying the report data. This facilitates query and browsing.
Prerequisite
l l l
Context
The performance report data can be saved in the format of data chart or image.
l
Save a report in the format of data chart. The .xls, .csv, .html, .txt formats are allowed.
Issue 06 (2008-12-16)
7-13

NOTE
If a report has multiple sub-reports, for the .xls format, only one file is generated with each sub-report corresponds to a tab. By default, the file is named after the report. For the .txt, .csv, or .html format, one file is generated for each sub-report. By default, the files are named after the sub-reports. If the data table is displayed on the basis of conditions, the file in .xls format saves the display format. That is, the counter data is displayed in the background color and foreground color that you have set.
l
Save a report in the format of image. That is, save the report displayed in the series chart or comparison chart. The .jpg file format is allowed.
Procedure
l Print the performance report data in the format of data chart. 1. 2. In the Performance Report window, select a tab. Right-click in the table area, and then select Save from the shortcut menu.

You can click Save > Save Table to save the table. You can choose Save > Save All to save the table and the figure.
3. 4. l 1. 2. 3. 4.
In the Save dialog box, set the path, name, and type of the file. Click Save. In the Performance Report window, select a tab. Click Show chart. Select an image format, namely, the Series chart tab or the Comparison chart tab. Right-click the chart area, and then select Save.

Save the performance report data in the format of image.
You can click Save > Save Chart to save the chart. You can choose Save > Save All to save the table and the figure.
5. 6. ----End
In the Save dialog box, set the path, name, and type of the file. Click Save.
7.2.10 Printing a Performance Report

This describes how to print a performance report. The M2000 client enables you to print required information in a certain format when you are querying the report data.
Prerequisite
l l l
Context
You can print a performance report as a data table or an image.
l
To print a performance report in the format of data table, you need to print it when it is displayed in tabular format.
7-14

NOTE
If a report has multiple sub-reports, the data of only one sub-report can be reported each time. The printed file is named in the format of report name-sub-report name.
l
To print a performance report as an image, you need to print it when it is displayed in a series chart or comparison chart. The .jpg file format is allowed.
Procedure
l Print the performance report data in the format of data chart. 1. 2. 3. In the Performance Report window, select a tab. Right-click the chart area, and then select Print. In the Print dialog box, click Print after setting the properties.
You can save the report data as files in different formats and then print it. The format can be .xls, .csv, .html, or .txt. For details, refer to 7.2.9 Saving a Performance Report. If the data table is displayed on the basis of conditions, the file in .xls format saves the display format. That is, the counter data is displayed in the background color and foreground color that you have set. If you print an .xls file, the data in the printed report is displayed as shown in the .xls file. l Print the performance report data in the format of image. 1. 2. 3. 4. 5. ----End In the Performance Report window, select a tab. Click Show chart. Select an image format, namely, the Series chart tab or the Comparison chart tab. Right-click the chart area, and then select Print. In the Print dialog box, click Print after setting the properties.
7.2.11 Managing a Custom Performance Report Template

This describes how to manage the M2000 custom performance report template. This function is used in case that the provided performance report templates cannot meet your requirement. On the M2000 client, you can save a performance report as a report template so that it can be repeatedly used to query performance data. This function allows you to create custom, modify, and delete performance report templates and set the sub-reports of a custom performance. 7.2.11.1 Creating a Custom Performance Report Template This describes how to create a custom performance report template. You can create a report template directly or duplicate a report template and then modify the attributes. 7.2.11.2 Setting Sub-Reports of a Custom Performance Report Template This describes how to set sub-reports of a custom performance report template. You can add, modify, or delete the sub-reports when creating or modifying a custom performance report template. 7.2.11.3 Modifying a Custom Performance Report Template This describes how to modify a custom performance report template. A custom performance report template is used to save the query settings to facilitate the query of related performance data. You can modify the configurations of a custom performance report as required. 7.2.11.4 Deleting a Custom Performance Report Template
This describes how to delete a custom performance report template to release more system resources.
Creating a Custom Performance Report Template

This describes how to create a custom performance report template. You can create a report template directly or duplicate a report template and then modify the attributes.
Prerequisite
l l l
You have logged in to the M2000 client. The DS and the RS run properly. You are authorized to manage reports.
Context
l
A report consists of one to five sub-reports. A custom report enables you to customize the attributes of the sub-reports. If a sub-report of a report is a comparison report, then the other sub-reports must be comparison reports. Four styles are available for a sub-report. These four styles can be classified into common report style, cross report style, and comparison report style. In the cross report style, the counters are fixed and the values are determined by both time and object. In the comparison report style, the values of a specified counter of the same object are compared by time. The sub-reports of a report can use different styles. A sub-report, however, can use only one style. For a sub-report using the common style, a maximum of 150 counters are allowed. You can customize TopN and BottomN reports. The value of N is configurable. For details, refer to 7.2.3 Filtering the Contents of a Performance Report. You can select KPIs and custom KPIs.
l l
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 Perform the following operations according to your requirements. Creation Mode Creating a template directly Duplicating an existing template and modifying the attributes Step 3 To create a report template directly, perform the following steps: 1. 2.
7-16
Operation Perform Step 3. Perform Step 4.
In the navigation tree, right-click a report type and choose New Report from the shortcut menu. The Add Report Template dialog box is displayed. Set Report Name and Object Type.
3.
Click Add Sub-report and then create a sub-reports for this report. For details, refer to 7.2.11.2 Setting Sub-Reports of a Custom Performance Report Template. Select the counters to be added to the sub-report in Available Counter List, and drag them to the corresponding sub-report areas.
l l
4.
You can press Ctrl or Shift to select multiple counters. You can double-click a counter to add it to the sub-report list on right. Alternatively, you can right-click the counter and choose Add to Table from the shortcut menu. You can enter a keyword in Filter Search to quickly find the required counter. For a selected counter in a sub-report, you can right-click the column of the counter and choose Delete Counter from the shortcut menu. For a cross report, you can select only one counter. If more than one counter is selected in the navigation tree, only the first counter can be dragged to the corresponding area. When one counter is available in the sub-report, the added counter replaces the existing one. For a common report, you can select the function subset and drag it to the corresponding sub-report area. Then, all the counters under the function subset are added to the area. If no sub-report is defined in Add Report Template, the Define Sub-report dialog box is displayed when you double-click a counter or drag a counter to the sub-report area. This dialog box prompts you to create a sub-report. If no counter is selected in a new sub-report, the system prompts you to select counters when you perform Step 3.5. In the sub-report area, you can right-click the area and choose Filter Condition from the shortcut menu to set the filtering conditions for the sub-report. In the sub-report area, you can right-click the area and choose TopN from the shortcut menu. In the displayed Filter Condition dialog box, you can set the TopN or BottomN filtering conditions for the sub-report. If you click OK, the Create Report Template dialog box is closed and the settings take effect. If you click OK, the Create Report Template dialog box is not closed and the settings take effect. If you click Cancel, the settings are not saved.
l l
5.
Click OK or Apply.
l
Step 4 Create a report template by duplicating an existing template and then modifying the attributes. 1. In the navigation tree, right-click a report type and choose Copy Report from the shortcut menu. You can duplicate system report templates and custom report templates. Locate the duplicated report template, right-click it , and then choose Modify Report from the shortcut menu. For details, refer to 7.2.11.3 Modifying a Custom Performance Report Template.
2.
----End
Issue 06 (2008-12-16)
7-17
Setting Sub-Reports of a Custom Performance Report Template

This describes how to set sub-reports of a custom performance report template. You can add, modify, or delete the sub-reports when creating or modifying a custom performance report template.
Prerequisite
l l l l
You have logged in to the M2000 client. The DS and the RS run properly. The Add Report Template or Modify Report Template dialog box is active. You are authorized to manage reports.
Context
l l
You can set one to five sub-reports for a report. If a sub-report of a report is a comparison report, then the other sub-reports must be comparison reports. Four styles are available for a sub-report. These four styles can be classified into common report style, cross report style, and comparison report style. In the cross report style, the counters are fixed and the values are determined by both time and object. In the comparison report style, the values of a specified counter of the same object are compared by time. The sub-reports of a report can use different styles. A sub-report, however, can use only one style. For a sub-report using the common style, a maximum of 15 counters are allowed. You can customize TopN and BottomN reports. The value of N is configurable. For details, refer to 7.2.3 Filtering the Contents of a Performance Report.
l l
Procedure
Step 1 Perform the following operations based on the actual requirement. If... Add a sub-report Modify a sub-report Delete a sub-report Then... Perform Step 2. Perform Step 3. Perform Step 4.
Step 2 To add a sub-report for a custom performance report, perform the following steps: 1. In the Add Report Template or Modify Report Template window, click Add Subreport. The Define Sub-report dialog box is displayed. Alternatively, you can right-click in the counter list and choose Add Sub-report from the shortcut menu. Set Sub-report Name and select the style for the sub-report.
l
2.
If no sub-report exists, four styles can be selected in Choose Sub-report Type. They are one comparison report style and three non-comparison report styles.
7-18

l
If a comparison report is created, then only the comparison report style is available in Choose Sub-report Type. If a non-comparison report is created, then the three non-comparison report style are available in Choose Sub-report Type. You can view the detailed description of the selected report style in Description.
3.
Click OK to close the Define Sub-report dialog box.
Step 3 To modify a sub-report for a custom performance report, perform the following steps: 1. 2. In the Add Report Template or Modify Report Template dialog box, select the tab of the sub-report that you plan to modify. Click Modify Sub-report. The Define Sub-report dialog box is displayed. Alternatively, you can right-click in the counter list and choose Modify Sub-report from the shortcut menu. 3. 4. Set the related parameters again. Click OK to close the Define Sub-report dialog box.
Step 4 To delete a sub-report for a custom performance report, perform the following steps: 1. 2. In the Add Report Template or Modify Report Template dialog box, select the tab of the sub-report that you plan to delete. Click Delete Sub-report. Alternatively, you can right-click the counter list and choose Delete Sub-report from the shortcut menu. ----End
Modifying a Custom Performance Report Template

This describes how to modify a custom performance report template. A custom performance report template is used to save the query settings to facilitate the query of related performance data. You can modify the configurations of a custom performance report as required.
Prerequisite
l l l
Context
The Object Type parameter of a custom report cannot be modified.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 In the navigation tree, right-click a custom report template and choose Modify Report from the shortcut menu. The Modify Report Template dialog box is displayed. Step 3 Set the related parameters again.

l l l
The Object Type parameter cannot be modified. You can modify the report name. To modify the attributes of a sub-report, refer to 7.2.11.2 Setting Sub-Reports of a Custom Performance Report Template. To add a counter in the sub-report, select the counter in Available Counter List and drag it to the sub-report tab. To remove a counter from the sub-report, right-click the blank area under the counter and choose Delete Counter from the shortcut menu. If you click OK, the Modify Report Template dialog box is closed and the settings take effect. If you click OK, the Modify Report Template dialog box is not closed and the settings take effect. If you click Cancel, the settings are not saved.

l
----End
Deleting a Custom Performance Report Template

This describes how to delete a custom performance report template to release more system resources.
Prerequisite
l l l
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance Report dialog box. Step 2 In the navigation tree, right-click a report type and choose Delete Report from the shortcut menu. Step 3 In the displayed Confirm dialog box, click Yes. ----End
7.3 Managing KPIs

Key performance indicators (KPIs) are categorized into system KPIs and custom KPIs. The M2000 enables you to manage KPIs, such as browse and filter KPIs, and set display conditions. You can also set custom KPIs based on your requirement. Custom KPIs are defined on the basis of system KPIs and the defined KPIs. They are used for setting custom reports. 7.3.1 Viewing KPIs This describes how to view the information about KPIs. The M2000 provides the function of viewing the KPI information.
7.3.2 Filtering KPIs This describes how to filter KPIs. You can set the keywords of counter names to display only the matching KPIs. In this way, the KPIs that are not required are shielded. This facilitates future queries. 7.3.3 Setting the Display of a KPI Based on Conditions This describes how to set the display of a KPI based on conditions. Then the system can display the KPIs in the generated report by using the defined foreground and background colors. 7.3.4 Managing Custom KPIs The M2000 enables you to manage custom KPIs so that you can create, modify, or delete KPIs.
7.3.1 Viewing KPIs

This describes how to view the information about KPIs. The M2000 provides the function of viewing the KPI information.
Prerequisite
l l l
You have logged in to the M2000 client. The DS and the RS run properly. You are authorized to browse KPIs.
Context
For system KPIs, you can only view the related information. For custom KPIs, you can modify or delete them by choosing Modify or Delete from the shortcut menu.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management dialog box. Step 2 In the navigation tree, select the NE type or object type of which you plan to view the KPIs.
l
If you select an NE type, you can view all the KPIs of this NE type in the counter list, including system KPIs and custom KPIs. If you select an object type, you can view all the KPIs of this object type in the counter list, including system KPIs and custom KPIs. In the counter list, select a KPI, and then you can view the corresponding counter formula in Counter Formula. The formulas of only medium counters and custom KPIs rather than original KPIs can be displayed. For description of medium counters, refer to 7.3.4 Managing Custom KPIs.
----End
7.3.2 Filtering KPIs

This describes how to filter KPIs. You can set the keywords of counter names to display only the matching KPIs. In this way, the KPIs that are not required are shielded. This facilitates future queries.
Issue 06 (2008-12-16)
7-21
Prerequisite
l l l l
You have logged in to the M2000 client. The DS and the RS run properly. You have performed 7.3.1 Viewing KPIs. You are authorized to browse KPIs.
Procedure
In the KPI Management window, enter the keywords of the counter names in Filter Counters by Name.

The keywords are case insensitive. All the counter names that contain the keywords are displayed in the counter list area.
----End
7.3.3 Setting the Display of a KPI Based on Conditions

This describes how to set the display of a KPI based on conditions. Then the system can display the KPIs in the generated report by using the defined foreground and background colors.
Prerequisite
l l l l
You have logged in to the M2000 client. The DS and the RS run properly. You have performed 7.3.1 Viewing KPIs. You are authorized to browse KPIs.
Context
After you set the display mode for a KPI in the KPI Managementwindow, the counter is displayed in the defined mode if the performance report contains this counter. You can also modify the conditions in the Performance Report window. For details, refer to 7.2.4 Setting the Display of a Performance Report Based on Conditions.
Procedure
Step 1 In the counter list in the KPI Management window, select a KPI. Step 2 Right-click the counter and choose Format Setting from the shortcut menu. The Format Setting dialog box is displayed. Step 3 Set Condition, Foreground, and Background. If the selected KPI meets the conditions, the corresponding values are displayed in the defined foreground and background colors. For detailed parameter description, refer to 7.9.4 Parameters for Setting the Condition Display of the KPIs.
l
If you need to add a format setting, click Add, and then set parameters in Condition, Foreground, and Background.
NOTE
You can set a maximum of three display modes for one KPI.
7-22
Issue 06 (2008-12-16)

l
If you need to delete a format setting, select a condition in the Delete format setting dialog box after clicking Delete. Click OK to delete it. To modify a condition format, you can modify the parameters in the drop-down lists of Condition, Foreground, and Background.

l l l
If you click OK, the Format setting dialog box is closed and the settings take effect. If you click Apply, the Format setting dialog box is not closed and the settings take effect. If you click Cancel, the settings are not saved.
----End
Related Tasks
7.2.4 Setting the Display of a Performance Report Based on Conditions
Related References
7.3.4 Managing Custom KPIs

The M2000 enables you to manage custom KPIs so that you can create, modify, or delete KPIs. 7.3.4.1 Adding a Custom KPI This describes how to add a custom KPI. Custom KPIs are defined according to the system KPIs and defined KPIs. They help implement the related functions of the report. You can create KPIs as required. 7.3.4.2 Modifying a Custom KPI This describes how to modify the parameter settings of a custom KPI as required.
Adding a Custom KPI

This describes how to add a custom KPI. Custom KPIs are defined according to the system KPIs and defined KPIs. They help implement the related functions of the report. You can create KPIs as required.
Prerequisite
l l l
You have logged in to the M2000 client. The DS and the RS run properly. You are authorized to manage KPIs.
Context
For the KPIs that can be defined for multiple objects, the data is summarized and calculated on the basis of one object type. For example, the counter data of RNCs and cells can be calculated on the basis of RNC. The counter data of different function subsets can be calculated on the basis of the same object type. For example, the data of in-office and out-office counters belong to different function subsets, but they are both office direction objects.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management dialog box. Step 2 Create custom KPIs by NE type or object type. If... Create custom KPIs by NE type Create custom KPIs by object type Step 3 To create custom KPIs by NE type, perform the following steps: 1. 2. In the left navigation tree, select the node of the NE type for which you plan to add custom KPIs. Click Add. The Add Counter dialog box is displayed. Alternatively, you can right-click in the counter list and choose Add from the shortcut menu. 3. Set Counter Name, Counter Unit, Data Type, Object Type, Function Subset, and Formula Information.
l l
Operation Perform Step 3. Perform Step 4.
For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs. When setting formula Information, you can manually enter a counter name or doubleclick a counter in the counter list. In Filter Counters by Name, you can enter the keyword of the counter. Then, the system displays only the KPIs that match the keywords. You can select Counter Type to distinguish system counters and custom counters. If you click OK, the Add Counter dialog box is closed and the settings take effect. If you click Apply, the Add Counter dialog box is not closed and the settings take effect. If you click OK, the Add Counter dialog box is closed and the settings do not take effect.
4.
Click OK or Apply.
l l
Step 4 To create custom KPIs by object type, perform the following steps: 1. 2. In the navigation tree, select the object type or function subset to which you plan to add custom KPIs. Click Add. The Add Counter dialog box is displayed. Alternatively, you can right-click in the counter list and choose Add from the shortcut menu. 3. Set Counter Name, Counter Unit, Data Type, Function Subset,and Formula Information.
l l l
Object Type cannot be modified. For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs. When setting formula Information, you can manually enter a counter name or doubleclick a counter in the counter list.
7-24

l
In Filter Counters by Name, you can enter the keyword of the counter. Then, the system displays only the KPIs that match the keywords. You can select Counter Type to distinguish system counters and custom counters. If you click OK, the Add Counter dialog box is closed and the settings take effect. If you click Apply, the Add Counter dialog box is not closed and the settings take effect. If you click OK, the Add Counter dialog box is closed and the settings do not take effect.
4.
Click OK or Apply.
l l
----End
Modifying a Custom KPI

This describes how to modify the parameter settings of a custom KPI as required.
Prerequisite
l l l l
You have logged in to the M2000 client. The DS and the RS run properly. A custom KPI is available. You are authorized to manage KPIs.
Context
You are not allowed to modify the object type and function subset.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management dialog box. Step 2 In the navigation tree, select the NE type or object type of which you plan to modify the custom KPIs. Step 3 In the counter list, select the custom KPI and click Modify. Alternatively, right-click the counter and choose Modify from the shortcut menu. The Modify Counter dialog box is displayed. Step 4 Set Counter Name, Counter Unit, Data Type, and Formula Information. For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs. Step 5 Click OK or Apply.
l l l
If you click OK, the Modify Counter dialog box is closed and the settings take effect. If you click Apply, the Modify Counter dialog box is not closed and the settings take effect. If you click OK, the Modify Counter dialog box is closed and the settings do not take effect.
----End
Postrequisite
You can delete a custom KPI that is not required.
1. 2. 3.
In the navigation tree of the KPI Management window, select the NE type or object type of which you plan to delete the custom KPIs. In the counter list, select the KPI and click Delete. Alternatively, right-click the counter and choose Delete from the shortcut menu. In the displayed Confirm dialog box, click Yes.
7.4 MSC Server Performance Reports

The MSC Server performance report group is used to query the traffic and some services of the MSC Server. This report group includes MSC basic traffic report, MSC Mobility management report, CPU load report, office direction traffic report, signaling link report, and trunk group report in a specified period. 7.4.1 MSC Basic Service Report The MSC basic service report is used to collect statistics on basic traffic of the MSC Server in a specified period. 7.4.2 Mobility Management Report The MSC mobility management report is used to query the handovers, assignments, paging, location registrations, and authentication encryption of the MSC Server in a specified period. 7.4.3 CPU Load Report The CPU seizure ratio report is used to query CPU seizure ratios of the MSC Server in a specified time. 7.4.4 Office Direction Traffic Report The office traffic report is used to query incoming and outgoing traffic, total office direction traffic, signaling links, trunk groups, and location of the MSC Server in a specified time. 7.4.5 Trunk Group Report The trunk group report is used to query the incoming and outing trunk traffic and total trunk traffic of the MSC Server in a specified period. 7.4.6 Signaling Link Report The link report is used to query the MSC signaling links of the MSC Server in a specified period. This report includes BICC link report, H248 link report, M3UA link report, M2UA link report, MTP3 link report, and MTP3B link report.
7.4.1 MSC Basic Service Report

The MSC basic service report is used to collect statistics on basic traffic of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter Device capability Report
7-26
Meaning Number of VLR Registered Subscriber Number of VLR register subscribers
Issue 06 (2008-12-16)
Counter VLR Subscriber of Local VLR Subscriber of Roaming Number of VLR Power-on Subscriber 2G MO Call MO Connected Rate MO Answer Rate 2G MO SEIZE USAGE 2G MO ALERT USAGE 2G MO ANSWER USAGE 2G ORG CALL ATTEMPT TIMES 2G MO ALERT 2G MO ANSWER 2G MT Call MT Connected Rate MT Answer Rate 2G TERMINATED SEIZE USAGE 2G TERMINATED ALERT USAGE 2G TERMINATED ANSWER USAGE 2G TERMINATED CALL ATTEMPT 2G TERMINATED ALERT 2G TERMINATED ANSWER 3G MO Call MO Connected Rate MO Answer Rate 3G MO SEIZE TRAFFIC 3G MO ALERT TRAFFIC 3G MO ANSWER TRAFFIC
Meaning Number of VLR local subscribers Number of VLR roaming subscribers Number of VLR power-on subscribers Mobile originated connected rate Mobile originated answer rate Mobile originated seizure traffic Mobile originated connected traffic Mobile originated answer traffic Times of mobile originated call attempts Times of mobile originated connected call attempts Times of mobile originated answer rate Mobile terminated connected rate Mobile terminated answer rate Mobile terminated seizure traffic Mobile terminated connected traffic Mobile terminated answer traffic Times of mobile terminated call attempts Times of mobile terminated connected call attempts Times of mobile terminated answers Mobile originated connected rate Mobile originated answer rate Mobile originated seizure traffic Mobile originated connected traffic Mobile originated answer traffic
Issue 06 (2008-12-16)
7-27
Counter 3G MO CALL ATTEMPTS 3G MO ALERT 3G MO ANSWER 3G MT Call MT Connected Rate MT Answer Rate 3G TERMINATED SEIZE USAGE 3G TERMINATED ALERT USAGE 3G TERMINATED ANSWER USAGE 3G TERMINATED CALL_ATTEMPT 3G TERMINATED ALERT 3G TERMINATED ANSWER Call Incoming Connected Ratio ALERTING TRAFFIC SEIZURE TIMES Outgoing Connected Ratio ALERTING TRAFFIC BID TIMES Internal Connected Ratio MOBILE TO MOBILE ALERT USAGE MOBILE TO MOBILE CALL ATTEMPT Transfer Connected Ratio ALERTING TRAFFIC OUTTK BID TIMES
Meaning Times of mobile originated call attempts Times of mobile originated connected call attempts Times of mobile originated answer rate Mobile terminated connected rate Mobile terminated answer rate Mobile terminated seizure traffic Mobile terminated connected traffic Mobile terminated answer traffic Times of mobile terminated call attempts Times of mobile terminated connected call attempts Times of mobile terminated answers Incoming connected ratio Traffic of completed incoming calls Times of incoming call attempts Internal connected ratio Traffic of internal completed incoming calls Number of internal call attempts Outgoing connected ratio Traffic of completed outgoing calls Times of outgoing call attempts Transfer connected ratio Traffic of transfer completed call attempts Times of transfer call attempts
7-28
Issue 06 (2008-12-16)
Counter SMS MO SMS Success Ratio MT SMS Success Ratio BASIC TABLE MO SMS BASIC TABLE MT SMS
Meaning Mobile originated SMS success ratio Mobile terminated SMS success ratio Mobile originated SMS attempts Mobile terminated SMS attempts
NOTE
To obtain the information about the previous counters, use the following methods:
l l
For system counters, refer to NE Reference Information in Online Help. For custom counters, you can find the corresponding expressions in the KPI Management window, and then read the description of each system counter in NE Reference Information in Online Help.
7.4.2 Mobility Management Report

The MSC mobility management report is used to query the handovers, assignments, paging, location registrations, and authentication encryption of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter Handover Intra MSC HO Success Rate Inter MSC Basic HO out Success Rate Inter MSC Basic HO in Success Rate request intra MSC HO request inter MSC Basic HO out request inter MSC Basic HO in Assign Assign Success Rate Assign Request Times Paging Paging Success Ratio BASIC TABLE PAGING Meaning Rate of intra MSC handover success Rate of inter MSC handover success Rate of inter MSC incoming handover success Times of intra MSC handover requests Times of inter MSC outgoing handover requests Times of inter MSC incoming handover requests Rate of assigning success Times of assigning request Paging success ratio Paging times
Issue 06 (2008-12-16)
7-29
Counter Location Subscriber Location Update Success Rate Number of Location Update request Authentication Success Rate AUTHENTICATION REQUEST TIMES Cipher Success Rate BASIC TABLE SET CIPHER MODE
Meaning Rate of location update success Number of location registration requests Rate of authentication success Times of authentication request Rate of ciphering success Times of ciphering request
Authentication and Cipher
NOTE
l l
7.4.3 CPU Load Report

The CPU seizure ratio report is used to query CPU seizure ratios of the MSC Server in a specified time.
Objects
MSCs.
Counters
Counter CPU Load ORIGINATING CALL ATTEMPT TIMES TERMINAL CALL TIMES CONGESTION TIMES CONGESTION DURATION OVERLOAD TIMES OVERLOAD DURATION AVERAGE SEIZURE RATIO PEAK SEIZURE RATIO Meaning Number of originating call attempts. Times of terminal call attempts. Congestion counts Duration of congestion. Times of overloads. Duration of congestion. The unit is second. Average seizure ratio (%). Peak seizure ratio (%).
7-30
Issue 06 (2008-12-16)
Counter PEAK SEIZURE DURATION BHCA
Meaning The duration of peak seizure. The unit is second. Busy hour call attempts.
NOTE
l l
7.4.4 Office Direction Traffic Report

The office traffic report is used to query incoming and outgoing traffic, total office direction traffic, signaling links, trunk groups, and location of the MSC Server in a specified time.
Objects
MSCs.
Counters
Counter Incoming INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM SEIZURE TRAFFIC CONNECTED TRAFFIC ANSWER TRAFFIC Connected Ratio Answer Ratio SEIZURE TIMES TK Avail Ratio Average Traffic Per Line Outgoing INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM SEIZURE TRAFFIC CONNECTED TRAFFIC ANSWER TRAFFIC
Issue 06 (2008-12-16)
Meaning Number of trunk circuits Number of available circuits Seizure traffic Traffic of completed call attempts Answer traffic Call completion ratio Answer ratio Seizure times Trunk available ratio Average traffic per line Number of trunk circuits Number of available circuits Seizure traffic Traffic of completed call attempts Answer traffic
7-31
Counter Seizure Ratio Connected Ratio Answer Ratio BID TIMES TK Avail Ratio Average Traffic Per Line Total Total Traffic Total Traffic Per Line
Meaning Seizure ratio Call completion ratio Answer ratio. Bid times Trunk available ratio Average traffic per line Total traffic Average traffic per line
NOTE
l l
7.4.5 Trunk Group Report

The trunk group report is used to query the incoming and outing trunk traffic and total trunk traffic of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter Incoming INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM SEIZURE TRAFFIC CONNECTED TRAFFIC ANSWER TRAFFIC CALL CONNECTED TIMES ANSWER TIMES SEIZURE TIMES Circuit Avail Ratio
7-32
Meaning Number of trunk circuits Number of available circuits Seizure traffic Traffic of completed call attempts Answer traffic Call completion times Answer times Seizure times Trunk available ratio
Issue 06 (2008-12-16)
Counter Average Traffic Per Line Outgoing INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM SEIZURE TRAFFIC CONNECTED TRAFFIC ANSWER TRAFFIC SEIZURE TIMES CALL CONNECTED TIMES ANSWER TIMES Circuit Avail Ratio BID TIMES DUAL SEIZURE TIMES Average Traffic Per Line Total Total Traffic Total Traffic Per Line
Meaning Average traffic per line Number of trunk circuits Number of available circuits Seizure traffic Traffic of completed call attempts Answer traffic Seizure times Call completion times Answer times Trunk available ratio Bid times Times of dual seizures. Average traffic per line Total traffic Average traffic per line
NOTE
l l
7.4.6 Signaling Link Report

The link report is used to query the MSC signaling links of the MSC Server in a specified period. This report includes BICC link report, H248 link report, M3UA link report, M2UA link report, MTP3 link report, and MTP3B link report. 7.4.6.1 BICC SCTP Link Report The BICC link report is used to query the number of sending and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the BICC link of the MSC Server. 7.4.6.2 H248 Link Report The H248 link report is used to query number of receiving and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the H248 link of the MSC Server. 7.4.6.3 M3UA Link Report
The M3UA link report is used to query the number of sending and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the M3UA link of the MSC Server in a specified period. 7.4.6.4 M2UA Link Report The M2UA link report is used to query number of receiving and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the M2UA link of the MSC Server in a specified period. 7.4.6.5 MTP3 Link Report The MTP3 link report is used to query the number of sending and receiving message signaling message units, number of sending and receiving octets, congestion counts and congestion duration, unavailable duration, and sending and receiving ratio of the MTP3 link of the MSC Server in a specified period. 7.4.6.6 MTP3B Link Report The MTP3B link report is used to query the number of sending and receiving message signaling message units, number of sending and receiving SIF and SIO octets, congestion counts and congestion duration, unavailable duration, and sending and receiving ratio of the MTP3B link of the MSC Server in a specified period.
BICC SCTP Link Report

The BICC link report is used to query the number of sending and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the BICC link of the MSC Server.
Objects
MSCs.
Counters
Counter BICC SCTP Link Number of message send Number of Message Received Bytes of Message Sent(MB) Bytes of Message Received (MB) Number of congestion Duration of congestion Number of disconnected Duration of disconnected Flow of Link(MB) Average Load of Link(kbps) Meaning Number of sent message packages Number of received message packages Bytes of sent messages Bytes of receiving messages Congestion counts Duration of congestion Number of link disconnections Duration of the link disconnection Flow of the BICC link Average load of links
7-34
Issue 06 (2008-12-16)

NOTE
l l
H248 Link Report

The H248 link report is used to query number of receiving and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the H248 link of the MSC Server.
Objects
MSCs.
Counters
Counter H248 SCTP Link Number of Message Sent Number of Message Received Bytes of Message Sent(MB) Bytes of Message Received (MB) Congestion Times of H248 SCTP link Congestion Duration of H248 SCTP link Unavailable Times of H248 SCTP link Unavailable Duration of H248 SCTP link Flow of Link(MB) Average Load of Link(kbps) Meaning Number of sent message packages Number of received message packages Bytes of sent messages Bytes of receiving messages Congestion counts Duration of congestion Number of link disconnections Duration of the link disconnection Flow of the BICC link Average load of links
NOTE
l l
Issue 06 (2008-12-16)
7-35
M3UA Link Report

The M3UA link report is used to query the number of sending and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the M3UA link of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter M3UA Link Number of Message Transmitted Number of Message Received Bytes of Message Sent(MB) Bytes of Message Received (MB) Congestion Times Congestion Duration Unavailable Times Unavailable Duration Flow of Link(MB) Average Load of Link(kbps) Meaning Number of receiving message packages Number of receiving message packages Bytes of sent messages Bytes of receiving messages Congestion counts Duration of congestion Number of link disconnections Duration of the link disconnection Flow of M3UA link Average load of links
NOTE
l l
M2UA Link Report

The M2UA link report is used to query number of receiving and receiving packages, number of sending and receiving bytes, congestion counts and duration, disconnection counts and duration, and flow and average load of the M2UA link of the MSC Server in a specified period.
Objects
MSCs.
7-36
Issue 06 (2008-12-16)
Counters
Counter M2UA Link number of MAUP message sent number of MAUP message received Bytes of Message Sent(MB) Bytes of Message Received (MB) times of the link congestion Congestion Duration times of the link unavailable Unavail Duration Average Load of Link(kbps) Meaning Number of sent message packages Number of received message packages Bytes of sent messages Bytes of receiving messages Congestion counts Duration of congestion Number of link disconnections Duration of the link disconnection Average load of links
NOTE
l l
MTP3 Link Report

The MTP3 link report is used to query the number of sending and receiving message signaling message units, number of sending and receiving octets, congestion counts and congestion duration, unavailable duration, and sending and receiving ratio of the MTP3 link of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter MTP Link MSU SND NUM OCTETS SND NUM MSU RCV NUM OCTETS RCV NUM
Issue 06 (2008-12-16)
Meaning Number of sent MSUs Number of sent octets Number of received MSUs Number of received octets
7-37
Counter CONGESTION TIMES CONGESTION DURATION UNAVAIL DURATION SND SEIZURE RATIO RCV SEIZURE RATIO
Meaning Congestion counts Duration of congestion Duration of the link disconnection Sent seizure ratio Received seizure ratio
NOTE
l l
MTP3B Link Report

The MTP3B link report is used to query the number of sending and receiving message signaling message units, number of sending and receiving SIF and SIO octets, congestion counts and congestion duration, unavailable duration, and sending and receiving ratio of the MTP3B link of the MSC Server in a specified period.
Objects
MSCs.
Counters
Counter MTP3B Link Link Sent MSUs Link Sent SIFSIO Octets Link Received MSUs Link Received SIFSIO Octets Link Congestion Times Link Congestion Duration Link Failed Duration Link Sending Used Rate Link Receiving Used Rate Meaning Number of sent MSUs Number of sent SIP and SIO octets Number of received MSUs Number of received SIP and SIO octets Congestion counts Duration of congestion Duration of the link disconnection Sent seizure ratio Received seizure ratio
7-38
Issue 06 (2008-12-16)

NOTE
l l
7.5 MSC POOL Report Group

Pool report group summarizes the measurement results of the counters on each MSC server within an MSC Pool in a specified period. After the measurement range is specified on the M2000, the NEs report the measurement results to M2000 with the interval of 30 minutes. By querying a Pool report, you can obtain the traffic, number of users, and services, which can serve as reference for routine maintenance. For details about how to specify the measurement range of NEs, refer to 6.2.1 Setting a Performance Measurement Range for an NE. This report group includes the following reports:
l l l l l l l l l l l l l l l l l
Global Traffic of a POOL Report Local Traffic of a POOL Report POOL incoming traffic report POOL outgoing traffic report Mobile office incoming traffic report Mobile office outgoing traffic report VLR subscribers MeasurementForSMS Report MTC connection measurement report Location management measurement report Pool Cell Handover Report Traffic Measurement For LAI Report GSM call drop report UMTS Call Drop Report Traffic Measurement of BSCOFI Assignment Report Traffic Measurement of RNCOFI Assignment Report Destcode traffic report
7.5.1 Global Traffic of a Pool Report The global traffic of a Pool report is used to query the traffic of the whole Pool in a specified period. 7.5.2 Local Traffic of a Pool Report The local traffic of a Pool report is used to query the local traffic of the whole Pool in a specified period. 7.5.3 Incoming Traffic of a Pool Report
The incoming traffic of Pool report is used to query the Pool incoming traffic in a specified period. 7.5.4 PoolOutTerCall Report The PoolOutTerCall report is used to query the Pool outgoing traffic in a specified period. 7.5.5 MobileOfficeInTfc Report The MobileOfficeInTfc report is used to query the mobile incoming traffic in a specified period. 7.5.6 MobileOfficeOutTfc Report The MobileOfficeOutTfc report is used to query the mobile outgoing traffic in a specified period. 7.5.7 VLRSubscriber Report The VLRSubscriber report is used to query the number of VLR subscribers in a specified period. 7.5.8 MeasurementForSMS Report The MeasurementForSMS report is used to query the SMS services in a Pool in a specified period. 7.5.9 MeasurementForMTC Report The MeasurementForMTC report is used to query the MTC connections in a specified period. 7.5.10 MeasurementForLOCUp Report The MeasurementForLOCUp report is used to query the location updates in a POOL in a specified period. 7.5.11 Pool Cell Handover Report The MSC Pool cell handover report is used to query the handovers in MSCs in a period of time. 7.5.12 Traffic Measurement For LAI Report The traffic measurement for LAI report is used to query the traffics of the specified location area in a period of time. 7.5.13 GSM Call Drop Report The GSM call drop report is used to query the GSM call drops in an MSC Pool in a period of time. 7.5.14 UMTS Call Drop Report The WCDMA call drop report is used to query the WCDMA call drops in an MSC Pool in a period of time. 7.5.15 Traffic Measurement of BSCOFI Assignment Report The traffic measurement of BSC office assignment report is used to query the assignments of specified BSC offices in an MSC Pool in a period of time. 7.5.16 Traffic Measurement of RNCOFI Assignment Report The traffic measurement of RNC office assignment report is used to query the assignments of specified RNC offices in an MSC Pool in a period of time.
7.5.1 Global Traffic of a Pool Report

The global traffic of a Pool report is used to query the traffic of the whole Pool in a specified period.
Objects
MSC Servers.
Counters
Counter Global Traffic of a Pool Report ANSWER TIMES CALL ATTEMPT TIMES ALERTING TIMES ANSWER TRAFFIC SEIZURE TRAFFIC ALERTING TRAFFIC ANSWER RATIO CONNECTED RATIO
l
Function Set and Function Subset

l
Function set: Total Traffic of the Office Function subset: Incoming Office Traffic, BSS Originate Call, UTRAN Originate Call Function set: Bearer Traffic Function subset: Trunk Office Direction Incoming Office Traffic
NOTE
l l
7.5.2 Local Traffic of a Pool Report

The local traffic of a Pool report is used to query the local traffic of the whole Pool in a specified period.
Objects
MSC Servers.
Counters
Counter Local Traffic of a Pool Report CALL ATTEMPT TIMES ALERTING TIMES ANSWER TIMES SEIZURE TRAFFIC ANSWER TRAFFIC ANSWER RATIO CONNECTED RATIO
l

l
Function set: Total Traffic of the Office Function subset: Internal Call Function set: Bearer Traffic Function subset: Trunk Office Direction Incoming Office Traffic
Issue 06 (2008-12-16)
7-41

NOTE
l l
7.5.3 Incoming Traffic of a Pool Report

The incoming traffic of Pool report is used to query the Pool incoming traffic in a specified period.
Objects
MSC Servers.
Counters
Counter Incoming Traffic of a Pool Report SEIZURE TIMES ALERTING TIMES ANSWER TIMES SEIZURE TRAFFIC ALERTING TRAFFIC ANSWER TRAFFIC CONNECTED RATIO ANSWER RATIO
l

l
Function set: Total Traffic of the Office Function subset: Incoming Office Traffic Function set: Bearer Traffic Function subset: Trunk Office Direction Incoming Office Traffic
NOTE
l l
7.5.4 PoolOutTerCall Report

The PoolOutTerCall report is used to query the Pool outgoing traffic in a specified period.
Objects
MSC Servers.
7-42
Issue 06 (2008-12-16)
Counters
Counter PoolOutTerCall Report CALL ATTEMPT TIMES ALERTING TIMES ANSWER TIMES SEIZURE TRAFFIC ALERTING TRAFFIC ANSWER TRAFFIC CONNECTED RATIO ANSWER RATIO
l

l
Function set: Total Traffic of the Office Function subset: Outgoing Office Traffic Function set: Bearer Traffic Function subset: Trunk Office Direction Incoming Office Traffic
NOTE
l l
7.5.5 MobileOfficeInTfc Report

The MobileOfficeInTfc report is used to query the mobile incoming traffic in a specified period.
Objects
MSC Servers.
Counters
Counter Mobile Office Direction Incoming Office Traffic Report SEIZURE TIMES ALERTING TIMES ANSWER TIMES SEIZURE TRAFFIC ALERTING TRAFFIC ANSWER TRAFFIC INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM
Function Set and Function Subset Function set: Bearer Traffic Function subset: Moble Office Direction Incoming Office Traffic
Counter BLOCKED CIRCUIT NUM CONNECTED RATIO ANSWER RATIO AVERAGE SEIZURE TRAFFIC PER LINE
NOTE
l l
7.5.6 MobileOfficeOutTfc Report

The MobileOfficeOutTfc report is used to query the mobile outgoing traffic in a specified period.
Objects
MSC Servers.
Counters
Counter Mobile Office Direction Outgoing Office Traffic Report SEIZURE TIMES ALERTING TIMES ANSWER TIMES SEIZURE TRAFFIC ALERTING TRAFFIC ANSWER TRAFFIC INSTALLED CIRCUIT NUM AVAIL CIRCUIT NUM BLOCKED CIRCUIT NUM CONNECTED RATIO ANSWER RATIO SEIZURE RATIO
Function Set and Function Subset Function set: Bearer Traffic Function subset: Mobile Office Direction Outgoing Office Traffic
Counter AVERAGE SEIZURE TRAFFIC PER LINE
NOTE
l l
7.5.7 VLRSubscriber Report

The VLRSubscriber report is used to query the number of VLR subscribers in a specified period.
Objects
MSC Servers.
Counters
Counter VLR Subscriber Report VLR SUBSCRIBER OF TOTAL VLR SUBSCRIBER OF IMSI_DETACH VLR SUBSCRIBER OF IMSI_ATTACH VLR SUBSCRIBER OF LOCAL VLR SUBSCRIBER OF ROAMING Function Set and Function Subset Function set: Global Components Function subset: Traffic Measurement For VLR Subscriber
NOTE
l l
7.5.8 MeasurementForSMS Report

The MeasurementForSMS report is used to query the SMS services in a Pool in a specified period.
Objects
MSC Servers.
Counters
Counter Measurement For SMS Report SMMO TIMES SMMO SUCCESS TIMES SMMT TIMES SMMT SUCCESS TIMES SMMO SUCCESS RATE SMMT SUCCESS RATE Function Set and Function Subset Function set: MSC Basic Services Function subset: Traffic Measurement For SMS
NOTE
l l
7.5.9 MeasurementForMTC Report

The MeasurementForMTC report is used to query the MTC connections in a specified period.
Objects
MSC Servers.
Counters
Counter Measurement For MTC Report MTC SUCC RATE PAGING MTC SUCC RATE PAGING RESP MTC SUCC RATE ALERT MTC SUCC RATE MO ALERT MTC SUCC RATE LAND ALERT MTC SUCC RATE ALERT RATE
Function Set and Function Subset Function set: Call Processing Function subset: Traffic Measurement For MTC SUCC Rate
Counter MTC SUCC RATE SUCCESS PAGING RATE
NOTE
l l
7.5.10 MeasurementForLOCUp Report

The MeasurementForLOCUp report is used to query the location updates in a POOL in a specified period.
Objects
MSC Servers.
Counters
Counter Measurement For LOCUp Report NUMBER OF LOCATION UPDATE REQUEST NUMBER OF LOCATION UPDATE REJECT NUMBER OF IMSI DETACH NUMBER OF IMSI ATTACH NUMBER OF LOCATION UPDATE INTRA_VLR REQUIRE SUCCESS NO OF LOCATION UPDATE INTRA_VLR REQUIRE NUMBER OF LOCATION UPDATE INTER_VLR REQUIRE SUCCESS NO OF LOCATION UPDATE INTER_VLR REQUIRE
Function Set and Function Subset Function set: MSC Basic Functions Function subset: Traffic Measurement For AUTH
Counter SUCCESS NO OF NATIONAL ROAMING USER REGISTRATION SUCCESS NO OF INTERNATIONAL ROAMING USER REGISTRATION SUCCESS RATE OF LOCATION UPDATE REQUEST
NOTE
l l
7.5.11 Pool Cell Handover Report

The MSC Pool cell handover report is used to query the handovers in MSCs in a period of time.
Objects
MSC Servers.
Counters
Counter Pool Cell Handover Report REQUEST INTER MSC BASIC HO IN REQUEST INTER MSC BASIC HO OUT SUCCESSFULLY INTER MSC BASIC HO IN SUCCESSFULLY INTER MSC BASIC HO OUT SUCCESSFULLY INTER MSC BASIC HO IN RATE SUCCESSFULLY INTER MSC BASIC HO OUT RATE
Function Set and Function Subset Function set: MSC Basic Services Function subset: Measurement For MSC HO

NOTE
l l
7.5.12 Traffic Measurement For LAI Report

The traffic measurement for LAI report is used to query the traffics of the specified location area in a period of time.
Objects
MSC Servers.
Counters
Counter Traffic Measurement For LAI Report TOTAL USER NUMBER(LAI) LOCAL USER NUMBER (LAI) ROAMING USER NUMBER (LAI) SWITCH ON USER NUMBER (LAI) SWITCH OFF USER NUMBER (LAI) UPDATE LOCATION REQUEST TIMES (LAI) LAI PAGING TIMES (LAI) PAGING RESPONSE TIMES (LAI) MO CONNECT TRAFFIC (LAI) MO RESPONSE TRAFFIC (LAI) MT CONNECT TRAFFIC (LAI) MT RESPONSE TRAFFIC (LAI)
Function Set and Function Subset Function set: Global Components Function subset: Traffic Measurement For LAI
Counter PAGING RESPONSE RATE
NOTE
l l
7.5.13 GSM Call Drop Report

The GSM call drop report is used to query the GSM call drops in an MSC Pool in a period of time.
Objects
MSC Servers.
Counters
Counter GSM Call Drop Report 2G CALL DROP RATE CONNECT 2G CALL DROP RATE MO CONNECT 2G CALL DROP RATE MT CONNECT 2G CALL DROP RATE CALL DROP 2G CALL DROP RATE MO CALL DROP 2G CALL DROP RATE MT CALL DROP 2G CALL DROP RATE HO CALL DROP 2G CALL DROP RATE Function Set and Function Subset Function set: Call Processing Function subset: GSM Call Drop
7-50
Issue 06 (2008-12-16)

NOTE
l l
7.5.14 UMTS Call Drop Report

The WCDMA call drop report is used to query the WCDMA call drops in an MSC Pool in a period of time.
Objects
MSC Servers.
Counters
Counter UMTS Call Drop Report 3G CALL DROP RATE CONNECT 3G CALL DROP RATE MO CONNECT 3G CALL DROP RATE MT CONNECT 3G CALL DROP RATE CALL DROP 3G CALL DROP RATE MO CALL DROP 3G CALL DROP RATE MT CALL DROP 3G CALL DROP RATE HO CALL DROP 3G CALL DROP RATE Function Set and Function Subset Function set: Call Processing Function subset: UMTS Call Drop
NOTE
l l
Issue 06 (2008-12-16)
7-51
7.5.15 Traffic Measurement of BSCOFI Assignment Report

The traffic measurement of BSC office assignment report is used to query the assignments of specified BSC offices in an MSC Pool in a period of time.
Objects
MSC Servers.
Counters
Counter Traffic Measurement Of BSCOFI Assignment Report TRAFFIC ASSIGN REQUEST TIMES TRAFFIC ASSIGN SUCCESS TIMES HALF RATE TRAFFIC ASSIGN REQUEST TIMES HALF RATE TRAFFIC ASSIGN SUCCESS TIMES TRAFFIC ASSIGN SUCCESS RATE
NOTE
Function Set and Function Subset Function set: MSC Basic Services Function subset: Traffic Measurement Of GSM Assignment
l l
7.5.16 Traffic Measurement of RNCOFI Assignment Report

The traffic measurement of RNC office assignment report is used to query the assignments of specified RNC offices in an MSC Pool in a period of time.
Objects
MSC Servers.
Counters
Counter Traffic Measurement Of RNCOFI Assignment Report
7-52
Function Set and Function Subset TRAFFIC ASSIGN REQUEST TIMES Function set: MSC Basic Services
Issue 06 (2008-12-16)
Counter TRAFFIC ASSIGN SUCCESS TIMES TRAFFIC ASSIGN SUCCESS RATE
Function Set and Function Subset Function subset: Traffic Measurement Of WCDMA Assignment
NOTE
l l
7.6 MSCe Pool Report Group

This describes the MSCe Pool report. The pool report group summarizes the measurement results of the counters of each MSCe within a MSCe Pool in a specified period. After the measurement range is specified through the M2000, the NEs report the measurement results with the interval of 60 minutes. By querying the pool report, you can obtain the traffic, number of users, and services, which can serve as reference for routine maintenance and network adjustment. For details about how to specify the measurement range of NEs, refer to 6.2.1 Setting a Performance Measurement Range for an NE. This report group includes the following reports:
l l l l l l l l l l l
Global Traffic of a Pool Report Local Traffic of a Pool Report Pool Incoming Traffic Report Pool Outgoing Traffic Report VLR Subscriber Report Pool Cell Handover Report LAI Traffic Measurement Report SMS Measurement Report Paging Measurement Report Location Update Measurement Report Assignment Measurement Report
7.6.1 Global Traffic of a Pool Report This describes the global traffic of a pool report, which is used to query the traffic of the whole MSCe Pool in a specified period. 7.6.2 Local Traffic of a Pool Report This describes the local traffic within pool report. The local traffic of a pool report is used to query the local traffic of a MSCe Pool in a specified period. 7.6.3 Pool Incoming Traffic Report
This describes the pool incoming traffic report. The incoming traffic of pool report is used to query the pool incoming traffic in a MSCe Pool in a specified period. 7.6.4 Pool Outgoing Traffic Report This describes the pool outgoing traffic report. The outgoing traffic of pool report is used to query the pool outgoing traffic in a MSCe Pool in a specified period. 7.6.5 VLR Subscriber Report This describes the VLR subscriber report, which is used to query the number of VLR subscribers in a MSCe Pool in a specified period. 7.6.6 Pool Cell Handover Report This describes the pool cell handover report. The pool cell handover report is used to query the handovers among all the MSCes in a MSCe Pool in a period. 7.6.7 LAI Traffic Measurement Report This describes the traffic measurement for LAI report, which is used to query the traffics of the specified location area in a period of time. 7.6.8 SMS Measurement Report This describes the measurement of short message report. The measurement for SMS report is used to query the SMS services in a MSCe Pool in a specified period. 7.6.9 Paging Measurement Report This describes the measurement of paging report. The paging measurement report is used to query successful paging in a MSCe Pool in a specified period. 7.6.10 Location Update Measurement Report This describes the measurement of location update report. The location update measurement report is used to query the location updates in a MSCe Pool in a specified period. 7.6.11 Assignment Measurement Report This describes the traffic measurement of assignment report, which is used to query the assignments of specified offices in a MSCe Pool in a period.
7.6.1 Global Traffic of a Pool Report

This describes the global traffic of a pool report, which is used to query the traffic of the whole MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Global Traffic of a Pool Report Pool All Answer Times Pool All Call Attempt Times Pool All Alerting Times
7-54 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

l
Function set: Global Traffic Measurement Function subset: Incoming Traffic Measurement, Originating Traffic Measurement
Issue 06 (2008-12-16)
Counter Pool All Answer Traffic Pool All Seizure Traffic Pool All Alerting Traffic Pool All Answer Ratio Pool All Connected Ratio

l
Function set: Bearer Traffic Measurement Function subset: Outgoing Office Measurement Based on Office Direction
NOTE
l l
7.6.2 Local Traffic of a Pool Report

This describes the local traffic within pool report. The local traffic of a pool report is used to query the local traffic of a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Local Traffic of a Pool Report Pool Local Call Attempt Times Pool Local Alerting Times Pool Local Answer Times Pool Local Seizure Traffic Pool Local Alerting Traffic Function Set and Function Subset
l
Function set: Global Traffic Measurement Function subset: Intra-office Traffic Measurement Function set: Bearer Traffic Measurement Function subset: Outgoing Office Measurement Based on Office Direction
Issue 06 (2008-12-16)
7-55
Counter Pool Local Answer Traffic Pool Local Answer Ratio Pool Local Connected Ratio
NOTE
l l
7.6.3 Pool Incoming Traffic Report

This describes the pool incoming traffic report. The incoming traffic of pool report is used to query the pool incoming traffic in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Pool Incoming Traffic Report Pool Incoming Seizure Times Pool Incoming Alerting Times Pool Incoming Answer Times Pool Incoming Seizure Pool Incoming Alerting Pool Incoming Answer Pool Incoming Connected Ratio Pool Incoming Answer Ratio

l
Function set: Global Traffic Measurement Function subset: Incoming Traffic Measurement Function set: Bearer Traffic Measurement Function subset: Outgoing Office Measurement Based on Office Direction

NOTE
l l
7.6.4 Pool Outgoing Traffic Report

This describes the pool outgoing traffic report. The outgoing traffic of pool report is used to query the pool outgoing traffic in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Pool Outgoing Traffic Report Pool Outgoing Seizure Times Pool Outgoing Alerting Times Pool Outgoing Answer Times Pool Outgoing Seizure Pool Outgoing Alerting Pool Outgoing Answer Pool Outgoing Connected Ratio Pool Outgoing Answer Ratio Function Set and Function Subset
l
Function set: Global Traffic Measurement Function subset: Outgoing Traffic Measurement Function set: Bearer Traffic Measurement Function subset: Outgoing Office Measurement Based on Office Direction
NOTE
l l
7.6.5 VLR Subscriber Report

This describes the VLR subscriber report, which is used to query the number of VLR subscribers in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter VLR Subscriber Report Local Subscribers Roaming Subscribers Function Set and Function Subset Function set: Global Traffic Measurement Function subset: VLR Subscriber Measurement
NOTE
l l
7.6.6 Pool Cell Handover Report

This describes the pool cell handover report. The pool cell handover report is used to query the handovers among all the MSCes in a MSCe Pool in a period.
Objects
MSCe NE
Counters
Counter Pool Cell Handover Report Request Inter MSC Basic HO In Request Inter MSC Basic HO Out Successfully Inter MSC Basic HO In Successfully Inter MSC Basic HO Out Successfully Inter MSC Basic HO In Rate Successfully Inter MSC Basic HO Out Rate
Function Set and Function Subset Function set: MSC Basic Service Traffic Measurement Function subset: Inter-office Handoff Measurement

NOTE
l l
7.6.7 LAI Traffic Measurement Report

This describes the traffic measurement for LAI report, which is used to query the traffics of the specified location area in a period of time.
Objects
MSCe NE
Counters
Counter LAI Traffic Measurement Report First Pagings Paging Response Times (LAI) MOC Attempted MOCs Connected MOC Answered MOC Connected Traffic MOC Answered Traffic MTCs Attempted MTCs Connected MTCs Answered MTC Connected Traffic MTC Answered Traffic Paging Response Rate Function Set and Function Subset Function set: BSMAP Measurement Function subset: Location Area Traffic Measurement
Issue 06 (2008-12-16)
7-59

NOTE
l l
7.6.8 SMS Measurement Report

This describes the measurement of short message report. The measurement for SMS report is used to query the SMS services in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter SMS Measurement Report MO Short Message Submission Attempts Successful MO Short Message Submissions MT Short Message Submission Attempts Successful MT Short Message Submissions SMMO Success Rate SMMT Success Rate Function Set and Function Subset Function set: MSC Special Service Traffic Measurement Function subset: Short Message Service Measurement
NOTE
l l
7.6.9 Paging Measurement Report

This describes the measurement of paging report. The paging measurement report is used to query successful paging in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Paging Measurement Report Pagings Paging Responses Completed Calls MTC Success Rate Alert Rate MTC Success Rate Success Paging Rate Function Set and Function Subset Function set: Call Connection Procedure Measurement Function subset: MTC Completion Measurement
NOTE
l l
7.6.10 Location Update Measurement Report

This describes the measurement of location update report. The location update measurement report is used to query the location updates in a MSCe Pool in a specified period.
Objects
MSCe NE
Counters
Counter Location Update Measurement Report Location Update Requests Successful Location Updates Location Update Failures Success Rate Of Location Update Request Function Set and Function Subset Function set: MSC Basic Service Traffic Measurement Function subset: Location Management Service Measurement
NOTE
l l
Issue 06 (2008-12-16)
7-61
7.6.11 Assignment Measurement Report

This describes the traffic measurement of assignment report, which is used to query the assignments of specified offices in a MSCe Pool in a period.
Objects
MSCe NE
Counters
Counter Assignment Measurement Report MOC TCH Assignment Requests Successful MOC TCH Assignments MOC TCH Assignment Retries MTC TCH Assignment Requests Successful MTC TCH Assignments MTC TCH Assignment Retries Function Set and Function Subset Function set: MSC Basic Service Traffic Measurement Function subset: Assignment Procedure Measurement
NOTE
l l
7.7 RNC Performance Reports

The RNC performance report group is used to query RNC traffic and some services in a specified period. This report group includes RNC report and cell report group. The RNC report includes coverage Report, accessibility report, retainability report, mobility report, service integrity report, availability report, and traffic report. The RNC report includes coverage report, accessibility report, retainability report, mobility report, service integrity report, availability report, and traffic report. When the denominator is 0 or a counter is Null, the result is Null. 7.7.1 RNC Reports
The RNC reports is used to query the traffics of the RNC in a specified period. This report group includes coverage report, accessibility report, retainability report, mobility report, service integrity report, availability Report, and traffic report. 7.7.2 Cell Reports The cell reports is used to query the traffics of each cell in a specified period. This report group includes Accessibility Report, Retainability Report, Mobility Report, Service Integrity Report, Availability Report, and Traffic Report. 7.7.3 Troubleshooting Reports The troubleshooting report is used to record the statistics on top 10 cells with communication failures in a specified period. This report group includes RRC FAIL Report, CS Call Drop Cells Report, PS Call Drop Cells Report, CS RAB Fail Report, and PS RAB Fail Report.
7.7.1 RNC Reports

The RNC reports is used to query the traffics of the RNC in a specified period. This report group includes coverage report, accessibility report, retainability report, mobility report, service integrity report, availability Report, and traffic report. 7.7.1.1 Coverage Report The coverage report is used to evaluate the consumption of network resources due to soft handover in one RNC. 7.7.1.2 Accessibility Report The accessibility report is used to evaluate the ability of a user to obtain the requested service from the system. 7.7.1.3 Retainability Report The retainability report is used to evaluate the ability of a user to retain its requested service for the desired duration once connected. 7.7.1.4 Mobility Report The mobility report is used to evaluate the handover service success ratio in one RNC. 7.7.1.5 Traffic Report The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC, the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in each cell.
Coverage Report
The coverage report is used to evaluate the consumption of network resources due to soft handover in one RNC.
Objects
RNCs.
Issue 06 (2008-12-16)
7-63
Counters
Counter Soft Handover Ratio RNC Counter/Formula {[VS.SHO.AS.1+(VS.SHO.AS.2Softer +VS.SHO.AS.2Soft)*2+(VS.SHO.AS. 3Soft2Softer+VS.SHO.AS.3Soft +VS.SHO.AS.3Softer)*3]/(VS.SHO.AS.1 +VS.SHO.AS.2Softer+VS.SHO.AS.2Soft +VS.SHO.AS.3Soft2Softer+VS.SHO.AS. 3Soft+VS.SHO.AS.3Softer)-1}*100%
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online Help.
Accessibility Report
The accessibility report is used to evaluate the ability of a user to obtain the requested service from the system.
Objects
RNCs.
Counters
Counter IU Paging Success Ratio Radio Access Success Ratio Formula (VS.RANAP.Paging.Succ.IdleUE/ VS.RANAP.Paging.Att.IdleUE)*100% RRCS_SRservice*{[(VS.RAB.SuccEstabCS.Conv +VS.RAB.SuccEstabCS.Str)+ (VS.RAB.SuccEstabPS.Conv +VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Inter +VS.RAB.SuccEstabPS.Bkg)]/ [(VS.RAB.AttEstabCS.Conv +VS.RAB.AttEstabCS.Str)+ (VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Inter +VS.RAB.AttEstabPS.Bkg]}*100% [(RRC.SuccConnEstab.IRATCelRes +RRC.SuccConnEstab.IRATCCO +RRC.SuccConnEstab.Reg +RRC.SuccConnEstab.Detach)/ (RRC.AttConnEstab.IRATCelRes +RRC.AttConnEstab.IRATCCO +RRC.AttConnEstab.Reg +RRC.AttConnEstab.Detach)]*100%
Issue 06 (2008-12-16)
RRC Setup Success Ratio (other)
7-64
Counter RRC Setup Success Ratio (service)
Formula 100%*[(RRC.SuccConnEstab.OgConvCall +RRC.SuccConnEstab.OrgStrCall +RRC.SuccConnEstab.OrgItrCall +RRC.SuccConnEstab.OrgBkgCall +RRC.SuccConnEstab.OrgSubCall +RRC.SuccConnEstab.TmConvCall +RRC.SuccConnEstab.TmStrCall +RRC.SuccConnEstab.TmItrCall +RRC.SuccConnEstab.TmBkgCall +RRC.SuccConnEstab.EmgCall +RRC.SuccConnEstab.Unkown +RRC.SuccConnEstab.OgHhPrSig +RRC.SuccConnEstab.OgLwPrSig +RRC.SuccConnEstab.CallReEst +RRC.SuccConnEstab.TmHhPrSig +RRC.SuccConnEstab.TmLwPrSig)/ (RRC.AttConnEstab.OrgConvCall +RRC.AttConnEstab.OrgStrCall +RRC.AttConnEstab.OrgInterCall +RRC.AttConnEstab.OrgBkgCall +RRC.AttConnEstab.OgSubCall +RRC.AttConnEstab.TmConvCall +RRC.AttConnEstab.TmStrCall +RRC.AttConnEstab.TmInterCall +RRC.AttConnEstab.TmBkgCall +RRC.AttConnEstab.EmgCall +RRC.AttConnEstab.Unknown +RRC.AttConnEstab.OgHhPrSig +RRC.AttConnEstab.OgLwPrSig +RRC.AttConnEstab.CallReEst +RRC.AttConnEstab.TmHhPrSig +RRC.AttConnEstab.TmLwPrSig)] (VS.RAB.SuccEstab.AMR/VS.RAB.AttEstab.AMR) *100% (VS.RAB.SuccEstCS.Conv.64/ VS.RAB.AttEstCS.Conv.64)*100% [(VS.RAB.SuccEstabPS.Conv +VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Inter +VS.RAB.SuccEstabPS.Bkg)/ (VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Inter +VS.RAB.AttEstabPS.Bkg)]*100% (VS.HSDPA.RAB.SuccEstab/ VS.HSDPA.RAB.AttEstab)*100% (VS.HSUPA.RAB.SuccEstab/ VS.HSUPA.RAB.AttEstab)*100%
AMR RAB Setup Success Ratio VP RAB Setup Success Ratio PS RAB Setup Success Ratio
HSDPA RAB Setup Success Ratio HSUPA RAB Setup Success Ratio
Issue 06 (2008-12-16)
7-65

NOTE
Retainability Report
The retainability report is used to evaluate the ability of a user to retain its requested service for the desired duration once connected.
Objects
RNCs.
Counters
Counter AMR Call Drop Ratio VP Call Drop Ratio Formula [VS.RAB.Loss.CS.AMR/(VS.RAB.Loss.CS.AMR +VS.RAB.Loss.CS.Norm.AMR)]*100% [VS.RAB.Loss.CS.Conv64K/ (VS.RAB.Loss.CS.Conv64K+VS.Norm.Rel.CS.Conv.RB. 64)]*100% [(VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm)/ (VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm + VS.RAB.Loss.PS.Norm)]*100% [(VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF)/ (VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF+VS.HSDPA.RAB.Loss.Norm + VS.HSDPA.RAB.Loss.InActivity)]*100% [VS.HSUPA.RAB.Loss.Abnorm/ (VS.HSUPA.RAB.Loss.Abnorm +VS.HSUPA.RAB.Loss.Norm)]*100%
PS Service Drop Ratio
HSDPA Service Drop Ratio
HSUPA Service Drop Ratio
NOTE
Mobility Report
The mobility report is used to evaluate the handover service success ratio in one RNC.
Objects
RNCs.
7-66
Issue 06 (2008-12-16)
Counters
Counter Soft Handover Success Ratio HS-DSCH Service Cell Change Success Ratio with SHO (HSDPA to HSDPA) Inter-frequency Hard Handover Success Ratio Inter-frequency Hard Handover Success Ratio (HSDPA to HSDPA) CS Inter-RAT Handover Success Ratio (WCDMA to GSM)(RNC) PS Inter-RAT Handover Success Ratio (WCDMA to GPRS) HSDPA Inter-RAT Handover Success Rate (WCDMA to GPRS) SRNC Relocation Success Ratio Formula (VS.SHO.Succ/VS.SHO.Att.RNC)*100% (VS.HSDPA.CellChg.SuccOutIntraRNC/ VS.HSDPA.CellChg.AttOutIntraRNC)*100% (VS.HHO.InterFreq.Succ.RNC/ VS.HHO.InterFreq.Att.RNC)*100% (VS.HSDPA.HHO.SuccOutIntraRNCInterFreq/ VS.HSDPA.HHO.AttOutIntraRNCInterFreq)*100% (VS.IRATHO.SuccCSOut.RNC/ VS.IRATHO.AttCSOut.RNC)*100% (VS.IRATHO.SuccPSOutUTRAN.RNC/ VS.IRATHO.AttPSOutUTRAN.RNC)*100% (VS.IRATHO.HSDPA.SuccOutPSUTRAN/ VS.IRATHO.HSDPA.AttOutPSUTRAN)*100% [(RELOC.SuccCS+RELOC.SuccPS)/ (RELOC.AttPrepUEInvolCS +RELOC.AttPrepUENotInvolCS +RELOC.AttPrepUEInvolPS +RELOC.AttPrepUENotInvolPS)]*100% [(VS.TRELOC.SuccExec.UEInv +VS.TRELOC.SuccExec.UENotInv)/ (VS.TRELOC.AttPrep.UEInv +VS.TRELOC.AttPrep.UENonInv)]*100% (VS.HSUPA.EDCH.SHO.Succ/ VS.HSUPA.EDCH.SHO.Att)*100% (VS.HSUPA.SHO.ServCellChg.Succ/ VS.HSUPA.SHO.ServCellChg.Att)*100% (VS.HSUPA.HHO.InterFreq.NoChR.Succ/ VS.HSUPA.HHO.InterFreq.NoChR.Att)*100% (VS.HSUPA.ChR.InterFreq.EDCHtoDCH.Succ/ VS.HSUPA.ChR.InterFreq.EDCHtoDCH.Att)*100%
TRNC Relocation Success Ratio
E-DCH Soft Handover Success Ratio E-DCH Service Cell Change Success Ratio with SHO (HSUPA to HSUPA) E-DCH Service Cell Change Success Ratio with InterHHO (HSUPA to HSUPA) E-DCH to DCH Handover Success Ratio (with Inter HHO)
Issue 06 (2008-12-16)
7-67
Counter HSUPA Inter-RAT Handover Success Ratio (UTRAN to GPRS)
Formula (VS.HSUPA.IRATHO.SuccOutPSUTRAN/ VS.HSUPA.IRATHO.AttOutPSUTRAN)*100%
NOTE
Traffic Report
The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC, the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in each cell.
Objects
RNCs.
Counters
Counter CS Equivalent Erlang PS UL Throughput PS DL Throughput HSDPA Mean UE Number HSDPA RLC Traffic Volume HSUPA Mean UE Number HSUPA RLC Traffic Volume Formula VS.CSLoad.Erlang.Equiv.RNC + VS.CSLoad.MaxErlang.Equiv.RNC VS.PSLoad.ULThruput.RNC + VS.PSLoad.MaxULThruput.RNC VS.PSLoad.DLThruput.RNC + VS.PSLoad.MaxDLThruput.RNC VS.HSDPA.UE.Mean.Cell VS.HSDPA.MeanChThroughput.TotalBytes VS.HSUPA.UE.Mean.Cell VS.HSUPA.MeanChThroughput.TotalBytes
NOTE
7.7.2 Cell Reports

The cell reports is used to query the traffics of each cell in a specified period. This report group includes Accessibility Report, Retainability Report, Mobility Report, Service Integrity Report, Availability Report, and Traffic Report.
7-68
Issue 06 (2008-12-16)
7.7.2.1 Accessibility Report The accessibility report is used to evaluate the ability of a user to obtain the requested service from the system. 7.7.2.2 Retainability Report The retainability report is used to evaluate the ability of a user to retain its requested service for the desired duration once connected. 7.7.2.3 Mobility Report The mobility report is used to evaluate the handover service success ratio in each cell. 7.7.2.4 Traffic Report The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC, the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in each cell.
Accessibility Report
The accessibility report is used to evaluate the ability of a user to obtain the requested service from the system.
Objects
Cells.
Counters
Counter IU Paging Success Ratio Radio Access Success Ratio Formula (VS.RANAP.Paging.Succ.IdleUE/ VS.RANAP.Paging.Att.IdleUE)*100% RRCS_SRservice*{[(VS.RAB.SuccEstabCS.Conv +VS.RAB.SuccEstabCS.Str)+ (VS.RAB.SuccEstabPS.Conv +VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Inter +VS.RAB.SuccEstabPS.Bkg)]/ [(VS.RAB.AttEstabCS.Conv +VS.RAB.AttEstabCS.Str)+ (VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Inter +VS.RAB.AttEstabPS.Bkg]}*100% [(RRC.SuccConnEstab.IRATCelRes +RRC.SuccConnEstab.IRATCCO +RRC.SuccConnEstab.Reg +RRC.SuccConnEstab.Detach)/ (RRC.AttConnEstab.IRATCelRes +RRC.AttConnEstab.IRATCCO +RRC.AttConnEstab.Reg +RRC.AttConnEstab.Detach)]*100%
7-69
RRC Setup Success Ratio (other)
Issue 06 (2008-12-16)
Counter RRC Setup Success Ratio (service)
Formula 100%*[(RRC.SuccConnEstab.OgConvCall +RRC.SuccConnEstab.OrgStrCall +RRC.SuccConnEstab.OrgItrCall +RRC.SuccConnEstab.OrgBkgCall +RRC.SuccConnEstab.OrgSubCall +RRC.SuccConnEstab.TmConvCall +RRC.SuccConnEstab.TmStrCall +RRC.SuccConnEstab.TmItrCall +RRC.SuccConnEstab.TmBkgCall +RRC.SuccConnEstab.EmgCall +RRC.SuccConnEstab.Unkown +RRC.SuccConnEstab.OgHhPrSig +RRC.SuccConnEstab.OgLwPrSig +RRC.SuccConnEstab.CallReEst +RRC.SuccConnEstab.TmHhPrSig +RRC.SuccConnEstab.TmLwPrSig)/ (RRC.AttConnEstab.OrgConvCall +RRC.AttConnEstab.OrgStrCall +RRC.AttConnEstab.OrgInterCall +RRC.AttConnEstab.OrgBkgCall +RRC.AttConnEstab.OgSubCall +RRC.AttConnEstab.TmConvCall +RRC.AttConnEstab.TmStrCall +RRC.AttConnEstab.TmInterCall +RRC.AttConnEstab.TmBkgCall +RRC.AttConnEstab.EmgCall +RRC.AttConnEstab.Unknown +RRC.AttConnEstab.OgHhPrSig +RRC.AttConnEstab.OgLwPrSig +RRC.AttConnEstab.CallReEst +RRC.AttConnEstab.TmHhPrSig +RRC.AttConnEstab.TmLwPrSig)] (VS.RAB.SuccEstab.AMR/VS.RAB.AttEstab.AMR) *100% (VS.RAB.SuccEstCS.Conv.64/ VS.RAB.AttEstCS.Conv.64)*100% [(VS.RAB.SuccEstabPS.Conv +VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Inter +VS.RAB.SuccEstabPS.Bkg)/ (VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Inter +VS.RAB.AttEstabPS.Bkg)]*100% (VS.HSDPA.RAB.SuccEstab/ VS.HSDPA.RAB.AttEstab)*100% (VS.HSUPA.RAB.SuccEstab/ VS.HSUPA.RAB.AttEstab)*100%
AMR RAB Setup Success Ratio VP RAB Setup Success Ratio PS RAB Setup Success Ratio
HSDPA RAB Setup Success Ratio HSUPA RAB Setup Success Ratio
7-70
Issue 06 (2008-12-16)

NOTE
Retainability Report
The retainability report is used to evaluate the ability of a user to retain its requested service for the desired duration once connected.
Objects
Cells.
Counters
Counter AMR Call Drop Ratio VP Call Drop Ratio Formula [VS.RAB.Loss.CS.AMR/(VS.RAB.Loss.CS.AMR +VS.RAB.Loss.CS.Norm.AMR)]*100% [VS.RAB.Loss.CS.Conv64K/ (VS.RAB.Loss.CS.Conv64K+VS.Norm.Rel.CS.Conv.RB. 64)]*100% [(VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm)/ (VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm + VS.RAB.Loss.PS.Norm)]*100% [(VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF)/ (VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF+VS.HSDPA.RAB.Loss.Norm + VS.HSDPA.RAB.Loss.InActivity)]*100% [VS.HSUPA.RAB.Loss.Abnorm/ (VS.HSUPA.RAB.Loss.Abnorm +VS.HSUPA.RAB.Loss.Norm)]*100%
PS Service Drop Ratio
HSDPA Service Drop Ratio
HSUPA Service Drop Ratio
NOTE
Mobility Report
The mobility report is used to evaluate the handover service success ratio in each cell.
Objects
Cells.
Issue 06 (2008-12-16)
7-71
Counters
Counter Soft Handover Success Ratio HS-DSCH Service Cell Change Success Ratio with SHO (HSDPA to HSDPA) Intra-frequency Hard Handover Success Ratio Inter-frequency Hard Handover Success Ratio Inter-frequency Hard Handover Success Ratio (HSDPA to HSDPA) CS Inter-RAT Handover Success Ratio (WCDMA to GSM)(Cell) PS Inter-RAT Handover Success Ratio (WCDMA to GPRS) HSDPA Inter-RAT Handover Success Rate (WCDMA to GPRS) SRNC Relocation Success Ratio Formula [(SHO.SuccRLAddUESide+SHO.SuccRLDelUESide)/ (SHO.AttRLAddUESide+SHO.AttRLDelUESide)]*100% (VS.HSDPA.CellChg.SuccOutIntraRNC/ VS.HSDPA.CellChg.AttOutIntraRNC)*100% [(VS.HHO.Succ.RNC-VS.HHO.InterFreq.Succ.RNC)/ (VS.HHO.Att.RNC-VS.HHO.InterFreq.Att.RNC)]*100% (VS.HHO.InterFreq.Succ.RNC/ VS.HHO.InterFreq.Att.RNC)*100% (VS.HSDPA.HHO.SuccOutIntraRNCInterFreq/ VS.HSDPA.HHO.AttOutIntraRNCInterFreq)*100% (IRATHO.SuccOutCS/IRATHO.AttOutCS)*100%
(IRATHO.SuccOutPSUTRAN/IRATHO.AttOutPSUTRAN) *100% (VS.IRATHO.HSDPA.SuccOutPSUTRAN/ VS.IRATHO.HSDPA.AttOutPSUTRAN)*100% [(RELOC.SuccCS+RELOC.SuccPS)/ (RELOC.AttPrepUEInvolCS +RELOC.AttPrepUENotInvolCS +RELOC.AttPrepUEInvolPS +RELOC.AttPrepUENotInvolPS)]*100% [(VS.TRELOC.SuccExec.UEInv +VS.TRELOC.SuccExec.UENotInv)/ (VS.TRELOC.AttPrep.UEInv +VS.TRELOC.AttPrep.UENonInv)]*100% (VS.HSUPA.EDCH.SHO.Succ/ VS.HSUPA.EDCH.SHO.Att)*100% (VS.HSUPA.SHO.ServCellChg.Succ/ VS.HSUPA.SHO.ServCellChg.Att)*100% (VS.HSUPA.HHO.InterFreq.NoChR.Succ/ VS.HSUPA.HHO.InterFreq.NoChR.Att)*100%
TRNC Relocation Success Ratio
E-DCH Soft Handover Success Ratio E-DCH Service Cell Change Success Ratio with SHO (HSUPA to HSUPA) E-DCH Service Cell Change Success Ratio with InterHHO (HSUPA to HSUPA)
7-72
Issue 06 (2008-12-16)
Counter E-DCH to DCH Handover Success Ratio (with Inter HHO) HSUPA Inter-RAT Handover Success Ratio (UTRAN to GPRS)
Formula (VS.HSUPA.ChR.InterFreq.EDCHtoDCH.Succ/ VS.HSUPA.ChR.InterFreq.EDCHtoDCH.Att)*100% (VS.HSUPA.IRATHO.SuccOutPSUTRAN/ VS.HSUPA.IRATHO.AttOutPSUTRAN)*100%
NOTE
Traffic Report
The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC, the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in each cell.
Objects
Cells.
Counters
Counter CS Equivalent Erlang PS UL Throughput PS DL Throughput HSDPA Mean UE Number HSDPA RLC Traffic Volume HSUPA Mean UE Number HSUPA RLC Traffic Volume Formula VS.CSLoad.Erlang.Equiv.RNC + VS.CSLoad.MaxErlang.Equiv.RNC VS.PSLoad.ULThruput.RNC + VS.PSLoad.MaxULThruput.RNC VS.PSLoad.DLThruput.RNC + VS.PSLoad.MaxDLThruput.RNC VS.HSDPA.UE.Mean.Cell VS.HSDPA.MeanChThroughput.TotalBytes VS.HSUPA.UE.Mean.Cell VS.HSUPA.MeanChThroughput.TotalBytes
NOTE
Issue 06 (2008-12-16)
7-73
7.7.3 Troubleshooting Reports

The troubleshooting report is used to record the statistics on top 10 cells with communication failures in a specified period. This report group includes RRC FAIL Report, CS Call Drop Cells Report, PS Call Drop Cells Report, CS RAB Fail Report, and PS RAB Fail Report. 7.7.3.1 RRC Fail Report The RRC fail report is used to record the statistics on top 10 cells with RRC failures in a specified period. 7.7.3.2 CS Call Drop Cells Report The CS call drop cells report is used to collect statistics on top 10 cells with CS call drops in a specified period. 7.7.3.3 PS Call Drop Cells Report The PS call drop cells report is used to 7.7.3.4 CS RAB Fail Report The CS RAB fail report is used to collect statistics on top 10 cells with CS RAB failures in a specified period. 7.7.3.5 PS RAB Fail Report The PS RAB fail report is used to collect statistics on top 10 cells with PS RAB failures in a specified period.
RRC Fail Report

The RRC fail report is used to record the statistics on top 10 cells with RRC failures in a specified period.
Objects
RNCs and cells
Counters
Counter VS.RRC.FailConnEstab.Cell VS.RRC.AttConnEstab.Cell VS.RRC.Rej.RL.Fail VS.RRC.Rej.AAL2.Fail VS.RRC.Rej.Power.Cong VS.RRC.Rej.UL.CE.Cong VS.RRC.Rej.DL.CE.Cong VS.RRC.Rej.Code.Cong Formula [VS.RRC.AttConnEstab.Cell][RRC.SuccConnEstab.sum] VS.RRC.AttConnEstab.Cell VS.RRC.Rej.RL.Fail VS.RRC.Rej.AAL2.Fail VS.RRC.Rej.Power.Cong VS.RRC.Rej.UL.CE.Cong VS.RRC.Rej.DL.CE.Cong VS.RRC.Rej.Code.Cong
7-74
Issue 06 (2008-12-16)
Counter VS.RRC.Rej.Other.Cong
Formula [RRC.FailConnEstab.Cong][VS.RRC.Rej.Power.Cong][VS.RRC.Rej.Code.Cong][VS.RRC.Rej.UL.CE.Cong][VS.RRC.Rej.DL.CE.Cong] RRC.FailConnEstab.NoReply
RRC.FailConnEstab.NoReply
NOTE
CS Call Drop Cells Report

The CS call drop cells report is used to collect statistics on top 10 cells with CS call drops in a specified period.
Objects
RNCs and cells.
Counters
Counter VS.CS.Call.Drop.Cell VS.RAB.Loss.CS VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.UTRANgen VS.RAB.Loss.CS.RF.RLCRst VS.RAB.Loss.CS.RF.ULSync VS.RAB.Loss.CS.RF.UuNoReply VS.RAB.Loss.CS.RF.Oth VS.RAB.Loss.CS.Aal2Loss VS.Call.Drop.CS.Other Formula [VS.RAB.Loss.CS.RF]+[VS.RAB.Loss.CS.Abnorm] [VS.RAB.Loss.CS.RF]+[VS.RAB.Loss.CS.Abnorm] +[VS.RAB.Loss.CS.Norm] VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.UTRANgen VS.RAB.Loss.CS.RF.RLCRst VS.RAB.Loss.CS.RF.ULSync VS.RAB.Loss.CS.RF.UuNoReply VS.RAB.Loss.CS.RF.Oth VS.RAB.Loss.CS.Aal2Loss [VS.RAB.Loss.CS.Abnorm][VS.RAB.RelReqCS.OM][VS.RAB.RelReqCS.UTRANgen][VS.RAB.RelReqCS.RABPreempt][VS.RAB.Loss.CS.Aal2Loss]
Issue 06 (2008-12-16)
7-75

NOTE
PS Call Drop Cells Report

The PS call drop cells report is used to
Objects
RNCs and cells.
Counters
Counter VS.PS.Call.Drop.Cell VS.RAB.Loss.PS VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.RABPreempt VS.RAB.RelReqPS.UTRANgen VS.RAB.Loss.PS.RF.RLCRst VS.RAB.Loss.PS.RF.ULSync VS.RAB.Loss.PS.RF.UuNoReply VS.RAB.Loss.PS.RF.Oth VS.RAB.Loss.PS.GTPULoss VS.Call.Drop.PS.Other Formula [VS.RAB.Loss.PS.RF]+[VS.RAB.Loss.PS.Abnorm] [VS.RAB.Loss.PS.RF]+[VS.RAB.Loss.PS.Abnorm] +[VS.RAB.Loss.PS.Norm] VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.RABPreempt VS.RAB.RelReqPS.UTRANgen VS.RAB.Loss.PS.RF.RLCRst VS.RAB.Loss.PS.RF.ULSync VS.RAB.Loss.PS.RF.UuNoReply VS.RAB.Loss.PS.RF.Oth VS.RAB.Loss.PS.GTPULoss [VS.RAB.Loss.PS.Abnorm][VS.RAB.RelReqPS.OM][VS.RAB.RelReqPS.UTRANgen][VS.RAB.RelReqPS.RABPreempt][VS.RAB.Loss.PS.GTPULoss]
NOTE
CS RAB Fail Report

The CS RAB fail report is used to collect statistics on top 10 cells with CS RAB failures in a specified period.
Objects
RNCs and cells.
Counters
Counter VS.RAB.FailEstabCS.Cell Formula [VS.RAB.AttEstabCS.Conv]+ [VS.RAB.AttEstabCS.Str][VS.RAB.SuccEstabCS.Conv][VS.RAB.SuccEstabCS.Str] [VS.RAB.AttEstabCS.Conv]+ [VS.RAB.AttEstabCS.Str] VS.RAB.FailEstabCS.TNL VS.RAB.FailEstCS.Relo VS.RAB.FailEstCS.RIPFail VS.RAB.FailEstCs.Power.Cong VS.RAB.FailEstCs.ULCE.Cong VS.RAB.FailEstCs.DLCE.Cong VS.RAB.FailEstCs.Code.Cong VS.RAB.FailEstCs.IUB.Band [VS.RAB.FailEstCS.Unsp][VS.RAB.FailEstCs.Power.Cong][VS.RAB.FailEstCs.Code.Cong][VS.RAB.FailEstCs.ULCE.Cong][VS.RAB.FailEstCs.DLCE.Cong][VS.RAB.FailEstCs.IUB.Band] [VS.RAB.FailEstabCS.RNL][VS.RAB.FailEstCS.Relo][VS.RAB.FailEstCS.RIPFail][VS.RAB.FailEstCS.Unsp] ([VS.RAB.AttEstabCS.Conv]+ [VS.RAB.AttEstabCS.Str][VS.RAB.SuccEstabCS.Conv][VS.RAB.SuccEstabCS.Str])[VS.RAB.FailEstabCS.RNL][VS.RAB.FailEstabCS.TNL]
VS.RAB.AttEstabCS.Cell VS.RAB.FailEstabCS.TNL VS.RAB.FailEstCS.Relo VS.RAB.FailEstCS.RIPFail VS.RAB.FailEstCs.Power.Cong VS.RAB.FailEstCs.ULCE.Cong VS.RAB.FailEstCs.DLCE.Cong VS.RAB.FailEstCs.Code.Cong VS.RAB.FailEstCs.IUB.Band VS.RAB.FailEstabCS.Unsp.Other
VS.RAB.FailEstabCS.RNL.Other
VS.RAB.FailEstabCS.Other.Cell
NOTE
PS RAB Fail Report

The PS RAB fail report is used to collect statistics on top 10 cells with PS RAB failures in a specified period.
Issue 06 (2008-12-16)
7-77
Objects
RNCs and cells.
Counters
Counter VS.RAB.FailEstabPS.Cell Formula ([VS.RAB.AttEstabPS.Conv]+ [VS.RAB.AttEstabPS.Str]+ [VS.RAB.AttEstabPS.Inter]+ [VS.RAB.AttEstabPS.Bkg])([VS.RAB.SuccEstabPS.Conv]+ [VS.RAB.SuccEstabPS.Str]+ [VS.RAB.SuccEstabPS.Inter]+ [VS.RAB.SuccEstabPS.Bkg]) [VS.RAB.AttEstabPS.Conv]+ [VS.RAB.AttEstabPS.Str]+ [VS.RAB.AttEstabPS.Inter]+ [VS.RAB.AttEstabPS.Bkg] VS.RAB.FailEstPS.TNL VS.RAB.FailEstPS.RIPFail VS.RAB.FailEstPS.Par VS.RAB.FailEstPS.Relo VS.RAB.FailEstPs.Power.Cong VS.RAB.FailEstPs.Code.Cong VS.RAB.FailEstPs.ULCE.Cong VS.RAB.FailEstPs.DLCE.Cong VS.RAB.FailEstPs.IUB.Band [VS.RAB.FailEstPS.Unsp][VS.RAB.FailEstPs.Power.Cong][VS.RAB.FailEstPs.Code.Cong][VS.RAB.FailEstPs.ULCE.Cong][VS.RAB.FailEstPs.DLCE.Cong][VS.RAB.FailEstPs.IUB.Band] [VS.RAB.FailEstPS.RNL][VS.RAB.FailEstPS.RIPFail][VS.RAB.FailEstPS.Par]-[VS.RAB.FailEstPS.Relo][VS.RAB.FailEstPS.Unsp]
VS.RAB.AttEstabPS.Cell
VS.RAB.FailEstPS.TNL VS.RAB.FailEstPS.RIPFail VS.RAB.FailEstPS.Par VS.RAB.FailEstPS.Relo VS.RAB.FailEstPs.Power.Cong VS.RAB.FailEstPs.Code.Cong VS.RAB.FailEstPs.ULCE.Cong VS.RAB.FailEstPs.DLCE.Cong VS.RAB.FailEstPs.IUB.Band VS.RAB.FailEstabPS.Unsp.Other
VS.RAB.FlEstPS.RNL.Other
7-78
Issue 06 (2008-12-16)
Counter VS.RAB.FailEstabPS.Other.Cell
Formula (([VS.RAB.AttEstabPS.Conv]+ [VS.RAB.AttEstabPS.Str]+ [VS.RAB.AttEstabPS.Inter]+ [VS.RAB.AttEstabPS.Bkg])([VS.RAB.SuccEstabPS.Conv]+ [VS.RAB.SuccEstabPS.Str]+ [VS.RAB.SuccEstabPS.Inter]+ [VS.RAB.SuccEstabPS.Bkg]))[VS.RAB.FailEstPS.TNL][VS.RAB.FailEstPS.RNL]
NOTE
7.8 PCU Performance Reports

The PCU performance reports consist of data throughput report, transmission report, accessibility report, availability report, and retainability report. 7.8.1 Data Throughput Report The data throughput report is used to collect statistics on the data throughput of the PCU in a period of time. 7.8.2 Transmission Report The transmission report is used to collect statistics on the transmission performance of the PCU in a period of time. 7.8.3 Accessibility Report The accessibility report is used to collect statistics on the accessibility of the PCU in a period of time. 7.8.4 Availability Report The availability report is used to collect statistics on the resource utilization of the PCU in a period of time. 7.8.5 Retainability Report The retainability report is used to collect statistics on the retainability of the PCU in a period of time.
7.8.1 Data Throughput Report

The data throughput report is used to collect statistics on the data throughput of the PCU in a period of time.
Objects
PCUs.
Issue 06 (2008-12-16)
7-79
Counters
Counter Uplink RLC Payload (kbits) Meaning (Number of uplink RLC data blocks using CS1*23+Number of uplink RLC data blocks using CS2*34+Number of uplink RLC data blocks using CS3*40+Number of uplink RLC data blocks using CS4*54)*8/1024 (Number of downlink RLC data blocks using CS1*23 +Number of downlink RLC data blocks using CS2*34 +Number of downlink RLC data blocks using CS3*40 +Number of downlink RLC data blocks using CS4*54) *8/1024 (Number of uplink EGPRS RLC data blocks using MCS1*22+Number of uplink EGPRS RLC data blocks using MCS2*28+Number of uplink EGPRS RLC data blocks using MCS3*37+Number of uplink EGPRS RLC data blocks using MCS4*44+Number of uplink EGPRS RLC data blocks using MCS5*56+Number of uplink EGPRS RLC data blocks using MCS6*74+Number of uplink EGPRS RLC data blocks using MCS7*56+Number of uplink EGPRS RLC data blocks using MCS8*68 +Number of uplink EGPRS RLC data blocks using MCS9*74)*8/1024 (Number of downlink EGPRS RLC data blocks using MCS1*22+Number of downlink EGPRS RLC data blocks using MCS2*28+Number of downlink EGPRS RLC data blocks using MCS3*37+Number of downlink EGPRS RLC data blocks using MCS4*44+Number of downlink EGPRS RLC data blocks using MCS5*56+Number of downlink EGPRS RLC data blocks using MCS6*74+Number of downlink EGPRS RLC data blocks using MCS7*56 +Number of downlink EGPRS RLC data blocks using MCS8*68+Number of downlink EGPRS RLC data blocks using MCS9*74)*8/1024 Total bytes of uplink LLC_PDUs sent*8/1024
Downlink RLC Payload (kbits)
Uplink EDGPRS RLC Payload (kbits)
Downlink EDGPRS RLC Payload (kbits)
Mean Payload (kbytes) of the Downlink Data at the LLC Layer Mean Payload (kbytes) of the Uplink Data at the LLC Layer Mean Downlink NS_PDUs Throughput (kbits/s) Packet Data Rate on Air Interface (UL/DL)
Total bytes of LLC_PDUs sent*8/1024 Total bytes of NS PDUs sent by NS sublayer*8/ (1024*Measure period*60) ((Uplink RLC payload (kbits)+Uplink EDGPRS RLC payload (kbits)) /(Downlink RLC payload (kbits) +Downlink EDGPRS RLC payload (kbits)))*100
7-80
Issue 06 (2008-12-16)

NOTE
l l
7.8.2 Transmission Report

The transmission report is used to collect statistics on the transmission performance of the PCU in a period of time.
Objects
PCUs.
Counters
Counter Retransmission Rate of RLC Uplink Data Block (%) Meaning (1-(Retransmission rate of RLC uplink data block using CS1 (%)+Retransmission rate of RLC uplink data block using CS2 (%)+Retransmission rate of RLC uplink data block using CS3 (%) +Retransmission rate of RLC uplink data block using CS4 (%))/Total number of uplink RLC data blocks)*100 (1-(Retransmission rate of RLC downlink data block using CS1 (%)+Retransmission rate of RLC downlink data block using CS2 (%)+Retransmission rate of RLC downlink data block using CS3 (%)+Retransmission rate of RLC downlink data block using CS4 (%))/Total number of downlink RLC data blocks)*100 (1-(Retransmission rate of uplink EGPRS RLC data block using MCS1 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS2 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS3 (%) +Retransmission rate of uplink EGPRS RLC data block using MCS4 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS5 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS6 (%) +Retransmission rate of uplink EGPRS RLC data block using MCS7 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS8 (%)+Retransmission rate of uplink EGPRS RLC data block using MCS9 (%))/Total number of uplink EGPRS RLC data blocks)*100
Retransmission Rate of RLC Downlink Data Block (%)
Retransmission Rate of Uplink EGPRS RLC Data Block (%)
Issue 06 (2008-12-16)
7-81
Counter Retransmission Rate of Downlink EGPRS RLC Data Block (%)
Meaning (1-(Retransmission rate of downlink EGPRS RLC data block using MCS1 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS2 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS3 (%) +Retransmission rate of downlink EGPRS RLC data block using MCS4 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS5 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS6 (%) +Retransmission rate of downlink EGPRS RLC data block using MCS7 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS8 (%)+Retransmission rate of downlink EGPRS RLC data block using MCS9 (%))/Total number of downlink EGPRS RLC data blocks)*100
NOTE
l l
7.8.3 Accessibility Report

The accessibility report is used to collect statistics on the accessibility of the PCU in a period of time.
Objects
PCUs.
Counters
Counter Uplink Assignment Success Rate (%) Downlink Assignment Success Rate (%) Mean Inter-arrival Time of Packet Access Requests on CCCH (s) Uplink GPRS TBF Congestion Rate (%) Downlink GPRS TBF Congestion Rate (%) Meaning (Number of uplink TBF establishment attempts/Number of successful uplink TBF establishment)*100 (Number of successful downlink TBF establishment/ Number of downlink TBF establishment attempts)*100 Measure period*60/Number of packet channel requests received on CCCH (Number of uplink TBF establishment failures due to no channel)/Number of uplink TBF establishment attempts*100 (Number of downlink TBF establishment failures due to no channel)/Number of downlink TBF establishment attempts*100
Issue 06 (2008-12-16)
7-82
Counter Uplink GPRS TBF Congestion Rate (%) Downlink GPRS TBF Congestion Rate (%)
Meaning (Number of uplink EGPRS TBF establishment failures due to no channel )/Number of uplink EGPRS TBF establishment attempts*100 (Number of downlink EGPRS TBF establishment failures due to no channel)/Number of downlink EGPRS TBF establishment attempts*100
NOTE
l l
7.8.4 Availability Report

The availability report is used to collect statistics on the resource utilization of the PCU in a period of time.
Objects
PCUs.
Counters
Counter Uplink PDTCH/PACCH Utilization Rate (%) Downlink PDTCH/PACCH Utilization Rate (%) PDCH Occupation Rate (%) Pre-empted Dynamic PDCH Carrying Packet Traffic Reclaimed Success Rate (%) PDCH Allocation Success Rate (%) Meaning Number of RLC data blocks received on uplink PDTCH/ PACCH*100/Uplink PDTCH/PACCH utilization rate (%) Number of RLC data blocks received on downlink PDTCH/ PACCH*100/Downlink PDTCH/PACCH utilization rate (%) Mean number of occupied PDCHs*100/Mean number of available PDCHs Number of pre-empted PDCHs carrying packet traffic*100/ Number of dynamic PDCHs reclaimed by BSC (1-(Number of uplink TBF establishment failures due to MS no response +Number of downlink TBF establishment failures due to MS no response)/(Number of uplink TBF establishment attempts+Number of downlink TBF establishment attempts)) Number of PDCHs occupied by downlink TBF/(Measure period*12)
Downlink RLC Data Throughput per PDCH
Issue 06 (2008-12-16)
7-83
Counter Uplink RLC Data Throughput per PDCH
Meaning Number of PDCHs occupied by uplink TBF/(Measure period*12)
NOTE
l l
7.8.5 Retainability Report

The retainability report is used to collect statistics on the retainability of the PCU in a period of time.
Objects
PCUs.
Counters
Counter Uplink GPRS TBF Drop Rate (%) Meaning (Number of uplink TBF abnormal release due to N3101 overflow (MS no response)+Number of uplink TBF abnormal release due to N3103 overflow (MS no response))/ Number of successful uplink TBF establishment*100 Number of downlink TBF abnormal release due to N3105 overflow/Number of successful downlink TBF establishment*100 (Number of uplink EGPRS TBF abnormal release due to N3101 overflow (MS no response)+Number of uplink EGPRS TBF abnormal release due to N3103 overflow (MS no response))/Number of successful uplink EGPRS TBF establishment*100 Number of downlink EGPRS TBF abnormal release due to N3105 overflow/Number of successful downlink EGPRS TBF establishment*100
Downlink GPRS TBF Drop Rate (%) Uplink EGPRS TBF Drop Rate (%)
Downlink EGPRS TBF Drop Rate (%)
NOTE
l l
7-84
Issue 06 (2008-12-16)
7.9 Reference for Performance Report Management Interfaces

This describes the performance report management interfaces and the related parameters. You can obtain the information about the functions and thus perform the related operations. 7.9.1 Interface Description: KPI List This describes the KPI list. The information about the counters of a specified NE type or object type helps you perform the related operation. 7.9.2 Parameters for Setting Conditions for Querying Performance Reports This part describes the parameters in the Report Condition Setting dialog box. 7.9.3 Parameters for Setting Filter Conditions for Performance Reports This part describes the parameters in the Filter conditions dialog box. 7.9.4 Parameters for Setting the Condition Display of the KPIs This part describes the parameters in the Format Setting dialog box. 7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance Reports This part describes the parameters on the Series Chart tab page and the Comparison Chart tab page. 7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports This describes the parameters for setting the background color of the sequence chart and the comparison chart of performance reports. 7.9.7 Parameters for Creating or Modifying a Custom Performance Report Template This describes the parameters in the Add Report Template and Modify Report Template dialog boxes. 7.9.8 Parameters for Creating or Modifying a Sub-Report This describes the parameters in the Define Sub-report dialog box. 7.9.9 Parameters for KPIs This describes the parameters in the Add Counter and Modify Counter dialog boxes.
7.9.1 Interface Description: KPI List

This describes the KPI list. The information about the counters of a specified NE type or object type helps you perform the related operation. Figure 7-1 shows the KPI list.
Issue 06 (2008-12-16)
7-85
Figure 7-1 KPI list
(1) Navigation tree: You can select the NE type or object type of a KPI. (2) Counter list area. This area displays the information about all the KPIs of the selected NE type or object type. For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs. (3) Counter formula area. This area displays the information about the formula of the selected custom KPI. No information is displayed if the selected counters are original counters. (4) Buttons. You can add, modify, or delete custom KPIs, and close the active window by using the buttons. (5) Keyword input area. After you enter a keyword in this area, all the counters containing the keyword are displayed in the counter list area.

This part describes the parameters in the Report Condition Setting dialog box.
Parameter Select Template Time Dimension Value Range The created condition templates Hour, Day, Week, Month Description Names of the available condition templates on the M2000. Summary granularity on the time dimension.
7-86
Issue 06 (2008-12-16)
Parameter Object Dimension
Value Range Cell Reports Whole Network, RNC NE, Cell, and Cell Group
Description Summary granularity on the object dimension.
Issue 06 (2008-12-16)
7-87
Parameter
Value Range MSC Server Performance Report

l
Description MSC Basic Service Report/ Mobility Management Report: Whole Network, and MSCServer NE CPU Load Report: Whole Network, Module, and MSCServer NE Office Direction Traffic Report: Whole Network, MSCServer NE, Office, and Office Group BICC SCTP Link Report: Whole Network, MSCServer NE, and BICC Link H248 Link Report: Whole Network, MSCServer NE, MGW, and H248 Link M3UA Link Report: Whole Network, MSCServer NE, and M3UA Link M2UA Link Report: Whole Network, MSCServer NE, and M2UA Link MTP3 Link Report: Whole Network, MSCServer NE, and MTP3 Link MTP3B Link Report: Whole Network,
7-88
Issue 06 (2008-12-16)
Parameter
Value Range MSCServer NE, and MTP3B Link

l
Description
Trunk Group Report: Whole Network, MSCServer NE, Office, and Trunk Group
RNC Reports Data Selection Absolute Date:

l
Whole Network, RNC NE Set an absolute date as the query date.

NOTE The duration varies with the type of performance data. Therefore, the query time is determined by the duration. The data duration that exceeds the preset value cannot be queried.
Non-comparison report: Start and End Comparison report: Date 1 and Date 2
Default value: current date The Start/Date 1 date must be earlier than or the same as the End/Date 2 date. Relative Date (Offset from a previous date to now):
l
Set a relative date as the query date.

NOTE The duration varies with the type of performance data. Therefore, the query time is determined by the duration. The data duration that exceeds the preset value cannot be queried.
Non-comparison report: Start, End, and Unit Comparison report: Date 1, Date 2, and Unit
The Start/Date 1 date and End/Date 2 date are the offsets compared with the date of the day. For example, if Date 1 is set to 2, Date 2 is set to 1, you can infer that the query time is from two days before to one day before. Start/Date 1 must be greater or the same as End/Date 2. Unit can be Day, Week, or Month. Today
Query the report data of the day. The time consists with the server time.
Time Segment Selection
All Time Segment
Time segment for querying the report data.
Issue 06 (2008-12-16)
7-89
Parameter
Value Range Special Time Segment You can choose one to three time segments: Time Segment 1, Time Segment 2, and Time Segment 3.
Description Specify the time segment for querying report data. The time segments cannot be overlapped. The end time of each time segment must be later than or the same as the start time. The start time of the next time segment must be later than or the same as the end time of the previous time segment. Specify the busy time for querying report data. This option is available when Time Dimension is set to Day, Week, or Month and unavailable when Time Dimension is set to Hour. The available busy rules refer to the rules that meet the requirements of both Time Dimension and Object Dimension. For example, if Time Dimension is set to Day and Object Dimension is set to Cell, then the available busy rules are all the day busy rules of the cell type. The busy rule of an object is applicable to all the object groups of this object. For example, the busy rule for a Cell is appliable when the Object Dimension is set to Cell Group. You can select the busy rule name from the drop-down list. Alternatively, you can click and view the related information in the displayed Busy Rule Information dialog box. You can select one or more objects in Object Dimension and click to view the busy segment information about the selected objects.
Busy Time
7-90
Issue 06 (2008-12-16)
Parameter Object Range
Value Range All objects on the entire network. In Display Mode, you can select by Lever or by Group to view the objects. You can also enter the keywords in Filter Search and then view the matched objects in the navigation tree.
Description Query objects of the report data.
For example, if Time Dimension is set to Hour, Data Selection is set to Today, and Time Segment Selection is set to All Time Segment, then the sum data of each object and each hour of the day is displayed in a row in the report.
Related Tasks
7.2.2 Setting a Template for Querying Performance Reports 7.2.1 Generating a Performance Report
7.9.3 Parameters for Setting Filter Conditions for Performance Reports

This part describes the parameters in the Filter conditions dialog box.
Parameter Comparison Column Comparison Symbol Value Range Select from the drop-down list Select from the drop-down list The values vary based on the Comparison Column. Description This parameter is used to set filtering conditions. This parameter is used to compare Comparison Column and Value.
NOTE This parameter cannot be configured before you set Comparison Column.
Value
Defined by the users
The value used to compare with Comparison Column according to Comparison Symbol.
NOTE This parameter cannot be configured before you set Comparison Column.
Issue 06 (2008-12-16)
7-91
Parameter Relation
Value Range Select from the drop-down list. The value can be or, and, and none.
Description This parameter is used to set the relations between filtering conditions. If no filtering condition is added, the Relation in the filtering condition is unavailable.
NOTE
Yo can select a counter in Comparison Column, select TopN or BottomN in Comparison Symbol to set the TopN or BottomN report. The value of N is configurable. If the TopN or BottomN filtering conditions is defined, other filtering conditions cannot be added. If filtering conditions excluding TopN and BottomN conditions are set, then you are informed that the defined filtering conditions are cleared after you select the TopN or BottomN filtering conditions.
Related Tasks
7.2.3 Filtering the Contents of a Performance Report

This part describes the parameters in the Format Setting dialog box.
Parameter Counter Value Range You can select a counter from the drop-down list in the performance report. In KPI management, this parameter stands for the name of the selected counter. It cannot be re-selected. Condition Comparison relation between the The value can be >, >, , !=, counter and counter value in the condition setting. <, <, or between.
NOTE The counter value must be a numerical value or null.
Description Name of the counter for which you plan to set the display mode based on conditions.
Foreground
Set the color mode, sample, HSB, or RGB. You can select a color from the drop-down list. Alternatively, you can click and select a color in the displayed Color dialog box.
Color of the font. The default setting is black.
7-92
Issue 06 (2008-12-16)
Parameter Background
Value Range Set the color mode, sample, HSB, or RGB. You can select a color from the drop-down list. Alternatively, you and select a color can click in the displayed Color dialog box.
Description Color of the background. The default setting is white.
Related Tasks
7.2.4 Setting the Display of a Performance Report Based on Conditions 7.3.3 Setting the Display of a KPI Based on Conditions
7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance Reports
This part describes the parameters on the Series Chart tab page and the Comparison Chart tab page.
Parameter Series Chart By object By counter Select object Description View the chart of one NE View the chart of one counter Name of the object for viewing the series chart A maximum of ten objects is allowed. Select counter Name of the counter for viewing the series chart A maximum of ten counters is allowed. Comparison Chart By object By counter Select object View the chart of one NE View the chart of one counter Name of the object for viewing the report data comparison chart A maximum of ten objects is allowed. Select counter Name of the counter for viewing the report data comparison chart A maximum of ten counters is allowed.
Parameter Select time
Description Time for viewing the report data comparison chart
NOTE
To know how to set the background color, refer to 7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports.
Related Tasks
7.2.5 Displaying a Performance Report in a Sequence Chart 7.2.6 Displaying a Performance Report in a Comparison Chart
7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison Chart of Performance Reports
This describes the parameters for setting the background color of the sequence chart and the comparison chart of performance reports.
Parameters
Related Tasks
7.2.5 Displaying a Performance Report in a Sequence Chart 7.2.6 Displaying a Performance Report in a Comparison Chart
7.9.7 Parameters for Creating or Modifying a Custom Performance Report Template

This describes the parameters in the Add Report Template and Modify Report Template dialog boxes.
Parameter Report Name Description Name of the custom report template to be added or modified.
7-94
Issue 06 (2008-12-16)
Parameter Object Type
Description Object type of the performance counter to be added or modified. This parameter cannot be modified when you modify a custom report template.
Available Counter List Filter Search
All available counters for a sub-report. Set the keyword for the filtering search. The keyword is case insensitive. All counters that contain the keyword are displayed in the navigation tree below the keyword field.
To create or modify the attributes of a sub-report, refer to 7.9.8 Parameters for Creating or Modifying a Sub-Report.
7.9.8 Parameters for Creating or Modifying a Sub-Report

This describes the parameters in the Define Sub-report dialog box.
Parameter Sub-report Name Description Name of the sub-report to be created or modified. The system assigns values from 1 in sequence to the names of the sub-reports. Choose Sub-report Type All available report styles. You can choose common report style, cross report style, or comparison report style. By default, the style of the sub-report is common report style. Description Description of the selected report style. You can view the description by placing the mouse pointer on a report type in Choose Sub-report Type.
7.9.9 Parameters for KPIs

This describes the parameters in the Add Counter and Modify Counter dialog boxes.
Issue 06 (2008-12-16)
7-95
Parameter Counter Name Description Name of the counter to be added or modified. The value range is as follows::
l l
The maximum length is 250 bytes. The allowable characters are English letters, Chinese characters, numbers, and special characters excluding \ / : * ? " < > | ' ~ @ # $ % ^ & + - =. The value must be unique and cannot be null.
Counter Unit Data Type
Unit of counter data. Save type of counter data. The type can be Integer or Float.
Object Type Function Subset Formula Information Filter Counters by Name Counter Type
Object type of the counter. Function subset of the counter. Calculation formula of the counter. Indicates that the counter list displays only the counters containing the keyword. Counter type. The value range is as follows::
l l l
Custom Counter System Counter All Counter
7-96
Issue 06 (2008-12-16)
8 Software Management
8
About This Chapter
Context
Software Management
By using the software management function, the M2000 performs integrated management of software , configuration data, and file information for NEs. The NEs that support this function are RNC, NodeB, MSC Server, MGW, GGSN, SGSN, BSC, BTS, and ASN-GW.
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support software management. 8.1 Basic Knowledge of Software Management This part describes the basic knowledge about software management, including NE software, patches, file types for software management, directory structure of the software on the server, and the processes for managing NodeB licenses and NE software. 8.2 Managing Software and Files The management of software and files realizes the integrated management of software , configuration data, and file information for NEs. 8.3 Upgrading NE Software and Patches This describes how to upgrade NE software and patches. The related operations are downloading, synchronizing, loading, activating, confirming, deactivating, and deleting. The NEs supporting this function are RNC, NodeB, MSC server, MGW, SGSN, GGSN,BSC, BTS, and ASN-GW. 8.4 Managing NE Licenses This describes how to manage NE licenses by delivering the license files or license control information from the M2000 to NEs. The function of NE license management consists of the upload, download, activation, or assignment of the RAN system license and the license sharing management between the NEs. 8.5 Querying Version Information on Software Installed on the Server This describes how to query the version information about the OMC, adaptation layer, ENM, and northbound Corba interface installed on the server through the M2000 client. 8.6 Reference for Software Management Interfaces This part describes the software management interface and the related parameters.
Issue 06 (2008-12-16)
8-1
8.1 Basic Knowledge of Software Management

This part describes the basic knowledge about software management, including NE software, patches, file types for software management, directory structure of the software on the server, and the processes for managing NodeB licenses and NE software. 8.1.1 NE Software NE software refers to the current software versions of an NE. 8.1.2 Software Patch This part describes software patches. 8.1.3 Patch States This describes the states and state transition between software patches. 8.1.4 Software Management File Types The M2000 manages different files for NEs, such as software version package, patches, configuration data, license, and voice files. The managed files vary with the NE type. 8.1.5 RAN License A license is provided by the supplier to the operator for the use of a product. It defines the usability range and the validity period of the product. Through license authorization and the purchase of the specific license, the operator can flexibly select phase-specific network functions and capacity. A RAN system, consisting an RNC and all its managed NodeBs, can have multiple license files. At a particular point in time, only one license file can be in the active state. The M2000 distributes the values of the license. 8.1.6 Software Management Procedure This part describes the flow chart and networking system of software management.
8.1.1 NE Software
NE software refers to the current software versions of an NE. Some NEs provide the main/backup software storage areas, such as MGW, NodeB, and SGSN. Thus it can store at least two software versions at the same time. The main area stores a software version and a hot patch of this version, namely, the activated and running software and patch of the NE. The backup area stores the deactivated software.
8.1.2 Software Patch

This part describes software patches. There are two kinds of NE software patches: hot patches and cold patches. In the M2000 system, cold patches are managed as special software version with the NE software. Hot patches are not located under the software version node. Instead, they are located on the Tab page with the same software and the same level. For details, see 8.1.4 Software Management File Types. Software hot patches are identified with patch IDs, which are numbered from 1. IDs of the patches for the same software release reflect their release time, that is, the larger the value of an ID is, the later it is released. A released patch must contain contents of all patches released previously. For example, if the patch ID is 5, it must be compatible with patches from patch 1 to patch 4.
Software hot patch upgrading includes the following operations:

l l l l l
Loading NE software patches Activating NE software patches Confirming NE software patches Deactivating NE software patches Unloading NE software patches
8.1.3 Patch States

This describes the states and state transition between software patches. The software upgrade procedure includes loading, activating, and synchronizing the software. No state transition occurs during an upgrade process. The state of a software patch can be:
l l l l
Idle Active Inactive Running
Figure 8-1 shows the state transition of a patch. Figure 8-1 State transition of a patch
A software patch changes its state as follows:

l
After the loading, an idle patch becomes inactive, and becomes idle again after the system resetting. After being deleted, an inactive patch becomes idle. If activated, the patch becomes active and becomes inactive again after the system resetting. If deactivated, an active patch becomes inactive. After being deleted, it becomes idle, and then becomes running after acknowledged. After the system resetting, it becomes inactive again.
Issue 06 (2008-12-16)
l
After being deleted, a running patch becomes idle, and becomes running again after the system resetting.
8.1.4 Software Management File Types

The M2000 manages different files for NEs, such as software version package, patches, configuration data, license, and voice files. The managed files vary with the NE type. The file types involved in software management are as follows:
l
Software patches including cold patches For details, refer to 8.1.1 NE Software and 8.1.2 Software Patch. Patches Patches refer to hot patches. Licenses Licenses refer to license files of NEs. Data Data refers to configuration files of NEs. Others Others refer to log files of NEs. Voice Voice files of MGW. Backup voice Backup of a voice file when it is deleted. Upgrade software package The software package used to upgrade the RNCs. Software package refers to the programming files in binary format that are required during the board running.
Upgrade patch package The patch package used to upgrade the RNCs. Patch package refers to the hot patch files in .pat format that can be loaded after the board running.
Different NE types map different managed files. For details, refer to Table 8-1. Table 8-1 Mapping relationship between NEs and files NE Type RNC NodeB MSC Server MGW SGSN GGSN ASN-GW
8-4
Managed Files Versions, patches, licenses, upgrade software package, upgrade patch package Versions, patches, data, and others Versions Versions, patches, licenses, data, voices, and backup voices Versions, patches, data Versions, patches, data Versions, patches, data
NE Type BWA BSC BTS IP Clock Server AG
Managed Files Versions Versions, patches, licenses, data Versions Software version, others Software version, patch, data
The server saves the files of each NE. The NEs save their own files. The software management can manage the files on both the server and the NEs at the same time. The Software Management window of the Client provides the file structure tree. The Server tab displays the files on the server. The tree is consistent with the structure of the /export/home/sysm/ftproot folder on the server. The file structure of NodeB is different from other NEs, as shown in Figure 8-2 and Figure 8-3 Figure 8-2 Server tab File Structure of NodeB
Figure 8-3 Server tab File Structure of Other NEs
Issue 06 (2008-12-16)
8-5
The NE tab displays the files on each physical NE. The file structure of NodeB is different from other NEs, see Figure 8-4 and Figure 8-5. Figure 8-4 NE tab File Structure of NodeB
Figure 8-5 NE tab File Structure of Other NEs
8.1.5 RAN License

A license is provided by the supplier to the operator for the use of a product. It defines the usability range and the validity period of the product. Through license authorization and the purchase of the specific license, the operator can flexibly select phase-specific network functions and capacity. A RAN system, consisting an RNC and all its managed NodeBs, can have multiple license files. At a particular point in time, only one license file can be in the active state. The M2000 distributes the values of the license.
NOTE
For an independent NodeB, that is, a NodeB not managed by any RNC, cannot be managed by the license.
The RAN license information has the following features:


l
The license is allocated by the M2000 and controlled by the NodeB. The assignment result is sent by M2000 to the NodeB. Users can adjust the allocation of licenses among the NodeBs managed by the same RAN, but the total number of licenses is limited. The ESN encrypted through MCC+MNC+RNCID is bound to a RAN system. By default, the NodeB does not enable the control items to limit the system resources. License management is enabled only after the M2000 is installed with the license file and the NodeBs are provided with license configurations.
l l
License synchronization between the M2000 and the NodeBs is performed on time. Thus, the result of NodeB license assignment is sent to the M2000 on time. The allocation of licenses is encrypted and checked through the CRC. Then it is stored in the M2000 database. When the database is damaged or faulty, the M2000 stops license synchronization to avoid the spread of the wrong data.
NodeBs automatically saves the license configuration from the M2000. When the NodeBs are disconnected from the M2000, the M2000 still provides services according to the licenses.
8.1.6 Software Management Procedure

This part describes the flow chart and networking system of software management. For the flow chart of software management, refer to Figure 8-6. Figure 8-6 Flow chart of software management
In the whole process, the M2000 server is the default file server, refer to 3.2.10 Setting an NE as a Transfer Server. Through the GUI, operation and management commands are sent to the file server and then sent to NEs. Upon receiving the commands, the NEs determine whether to execute the commands and give a feedback to the file server. Then, the file server sends the received information to the client and the information is displayed through the GUI. The networking structure of software management is shown in Figure 8-7.
Issue 06 (2008-12-16)
8-7
Figure 8-7 Software management networking
In Figure 8-7, M2000 server performs centralized management on the software, configuration data and other files of each NE. The server is connected with M2000 client and NEs. Files can be transferred between the server and the clients or NEs. The FTP protocol is used for transferring files.
8.2 Managing Software and Files

The management of software and files realizes the integrated management of software , configuration data, and file information for NEs. 8.2.1 Viewing File Information on the Server This describes how to view file information on the M2000 server. 8.2.2 Viewing File Information on an NE This task describes how to view file information on an NE. 8.2.3 Transferring Files from the Server to the Client This task describes how to transfer files from the server to the client. 8.2.4 Transferring Files from the Server to an NE This task describes how to transfer files from the server to an NE. 8.2.5 Transferring Files from the Client to the Server This describes how to transfer files from the client to the server. 8.2.6 Transferring Files from an NE to the Server This task describes how to transfer data packets, other files or license files of an NE to the server. 8.2.7 Managing Task List A task list contains the immediate task list, file transfer task list, and license task list. You can right-click a task and choose corresponding menu items to perform related operations on the task.
8.2.8 Setting Parameters of File Transferring You can set the file transfer mode to FTP or SFTP. You can also set whether the transfer needs resumable download or compression. 8.2.9 Managing Voice Files The function of managing voice files enables you to load, check, and synchronize the voice files of the NEs. Only the MGW supports this function.
8.2.1 Viewing File Information on the Server

This describes how to view file information on the M2000 server.
Procedure
Step 1 Choose Software > Browser or click .
The Software Browser window is displayed. Step 2 Select an NE type to be viewed on the navigation tree on the NM Server tab page. Step 3 In the right pane, click the related tab to view the file information. The system supports different file types for different NEs. For details, refer to 8.1.4 Software Management File Types. ----End
8.2.2 Viewing File Information on an NE

This task describes how to view file information on an NE.
Procedure
The Software Browser window is displayed. Step 2 Select an NE to be viewed under the navigation tree on the NE tab page. Step 3 In the right pane, click the related tab to view the file information. The system supports different file types for different NEs. For details, refer to 8.1.4 Software Management File Types. ----End
8.2.3 Transferring Files from the Server to the Client

This task describes how to transfer files from the server to the client.
Procedure
Step 1 Choose Software > File Transfer Wizard. The Select General Parameters dialog box is displayed. Step 2 Select From NM to Client under Direction.
Step 3 Select the file to be transferred under Server path. The system supports different file types for different NEs.For details,refer to8.1.4 Software Management File Types. Step 4 Perform the related operation according to the type of the file to be transferred. File Type License, data, voice, and others Version, patch, upgrade software package, upgrade patch package, and backup voice Procedure Click Finish. 1. Click Finish. The NE Selection dialog box is displayed. 2. Select an NE. 3. Click OK.
NOTE The NodeB downloads the relevant files according the configuration file.
In the Software Management window, you can view the progress information in the list of FTP Task. ----End
8.2.4 Transferring Files from the Server to an NE

This task describes how to transfer files from the server to an NE.
Prerequisite
l l
The related files are available on the server. The NEs and the server are properly connected.
Context
Please refer to 8.1.4 Software Management File Types.
Procedure
Step 1 Choose Software > File Transfer Wizard. The Select General Parameters dialog box is displayed. Step 2 Select From NM to NE under Direction. Step 3 Select the file to be transferred under Server path. Step 4 Click Finish to open the NE Select dialog box.
NOTE
If the transferred file type is license, data, voices, or others, the operation is complete. The NE Select dialog box is not displayed. The reason is that the three file types are already specified a destination NE on the server.
8-10
Issue 06 (2008-12-16)
Step 5 Select a destination NE.

NOTE
The NodeB supports bulk configuration.
8.2.5 Transferring Files from the Client to the Server

This describes how to transfer files from the client to the server.
Prerequisite
The client and the M2000 server are properly connected.
Procedure
l If the files to be transferred are not voice resource files, perform the following operations: 1. 2. 3. Choose Software > File Transfer Wizard. The Select General Parameters dialog box is displayed. In Direction, select From Client to NM. Select the file to be transferred under NE Path. The system supports different file types for different NEs. For details, refer to 8.1.4 Software Management File Types. 4. 5. 6. Click Next. The Select dialog box is displayed. Select the files to be transferred. You can select multiple files. Click Finished. In the Software Browser window, you can view the progress information in the FTP Task list. l If the files to be transferred are not voice resource files, perform the following operations: 1. 2. 3. 4. 5. Choose Software > Browser or click .
The Software Browser window is displayed. Click the NE Server tab. Select the required MGW in the navigation tree. In the right pane of the Software Management window, click the Tone tab. Click Select an NE.
NOTE
and select From Client to NM .
The Tone Upload Wizard-NE Selection dialog box is displayed.
You can select multiple NEs.
6. 7.
Click Next. The Tone Upload Wizard-Tone File Check dialog box is displayed. Select the NEs in the left pane. Click Add files. The Open dialog box is displayed.
NOTE
You can press Ctrl to select multiple NEs and NE types.
Issue 06 (2008-12-16)
8-11
8.
In the Open dialog box, select a file and click Open.

NOTE
l l l
You can press Ctrl to select multiple voice files. You can upload multiple voice files to the same NE. The same voice file can be uploaded to multiple NEs. You can press Ctrl and select multiple NE types, NEs, and voice files in the Tone Upload Wizard-Tone File Check. Click Remove files to delete the voice files in batches.
9.
Click Start Check. Check whether the name of the voice file to uploaded exists on the server.
10. Perform different operations based on whether a voice file with the same name exists.
If a voice file with the same name exists, set Operation Mode. If no voice file with the same name exists, In the Messagedialog box, click OK.
NOTE
You can press Ctrl to select multiple voice files and set Operation Mode to set the operation modes in batches. You can choose to overwrite, back up, or forgive the file.
l l l
Over Write: overwrites the same file. Back Up: saves the file on the server and backs up the voice file that is transferred. Backs up the voice file that is newly transferred. Forgive: saves the file on the server and does not transfer the new file.
11. Click Finish. In the Software Browser window, you can view the progress information in the FTP Task list. ----End
8.2.6 Transferring Files from an NE to the Server

This task describes how to transfer data packets, other files or license files of an NE to the server.
Prerequisite
l l
The related files exist on the NE. The NEs and the server are properly connected.
Procedure
l If the file to be transferred is not a voice resource file, perform the following steps: 1. 2. 3. Choose Software > File Transfer Wizard. The Select General Parameters dialog box is displayed. In Direction, select From NE To NM. In NE Path, select the file to be transferred. The supported file types vary based on the NEs. For details, refer to 8.1.4 Software Management File Types. 4.
8-12
Click Finish.
In the Software Browser window, you can view the progress information in the Immediate Task list. l If the file to be transferred is a voice resource file, perform the following steps: 1. 2. 3. 4. 5. 6. 7. Choose Software > Browser or click . The Software Browser window is displayed. Click the NM Server tab. Select the MGW to be operated in the navigation tree. Click the Tone tab in the right pane. and select From NE To NM . Click The Tone File Check Upload dialog box is displayed. Select the voice files in the left pane of the Tone File Check Upload dialog box. Click Check. Check whether the name of the voice file to uploaded exists on the server. Perform the operations based on whether the same voice file exists.
If the same voice file exists Set Operation Mode. If the same voice file does not exist In the displayed Message dialog box, click OK.
NOTE
You can press Ctrl to select multiple voice files and click Operation Mode to set the operation modes in batches.You can choose to overwrite, back up, or forgive the file.
l l l
Over Write: overwrites the same file. Back Up: saves the file on the server and backs up the voice file that is transferred. Forgive: saves the file on the server and does not transfer the new file.
NOTE
To view the backup voice files on the server, perform the following steps: 1. In the left pane of the Software Browser window, select the MGW under NM Server. 2. Select Bak Tone
8.
Click OK. In the Software Browser window, you can view the progress in the Immediate Task list.
----End
8.2.7 Managing Task List

A task list contains the immediate task list, file transfer task list, and license task list. You can right-click a task and choose corresponding menu items to perform related operations on the task.
Prerequisite
The task list is not null.
Context
The Software Browser window contains the immediate task list and the file transfer task list. The License Management window contains the license task list and the file transfer task list.
The task lists on different interfaces display the tasks to be run after the corresponding interface is displayed. The following part describes the tasks recorded by each task list:
l
The immediate task list records the task of upgrading NEs and the task of transferring files between the NEs and the server. The file transfer task list records all the tasks of transferring files between the M2000 client and the server. In the Software Browser window, the file transfer tasks consist of the tasks of uploading and downloading NE software versions, patches, and data. In the License Browse window, the file transfer tasks consist of the tasks of uploading and downloading license lists. The list of license tasks mainly records the tasks related to the license, for example, synchronizing the network license and setting the NE sharing mode.
Procedure
Step 1 Choose the corresponding menu based on the task type to be managed.
l
Immediate task: Choose Software > Browser or click Software Browser window.
on the toolbar to open the
File transfer task: Choose Software > Browser, or click the shortcut icon Software > License Management. License task: Choose Software > License Management to open the License Management window.
, or choose
Step 2 Manage the task list. Task Type Procedure
List of immediate tasks Click the Immediate Task tab, right-click a task on the tab page, and then choose the following menu items to perform related operations the task:
l
Setting: filters and displays the tasks according to the status or the NEs. Stop Task: stops the selected tasks that are being run. Restart: runs the selected tasks again. Show Detail: displays the detailed information about the selected tasks. Refresh: refreshes the task list.
l l l
File transfer task list
Click the FTP Task tab, right-click a task on the tab page, and then choose the following menu items to perform related operations on the task:
l l l
Stop Task: stops the selected tasks that are being run. Restart: runs the selected tasks again. Show Detail: displays the detailed information about the selected tasks. Delete Task: deletes the selected tasks.
8-14
Issue 06 (2008-12-16)
Task Type License task list
Procedure Click the License Task tab, right-click a task on the tab page, and then choose the following menu items to perform related operations on the task:
l
Job Setting: filters and displays the tasks according to the task status or the NEs. Show Detail: displays the detailed information about the selected tasks. Refresh: refreshes the task list.
----End
8.2.8 Setting Parameters of File Transferring

You can set the file transfer mode to FTP or SFTP. You can also set whether the transfer needs resumable download or compression.
Procedure
Step 1 Choose Software > FTP Setting. The FTP Setting dialog box is displayed. Step 2 Select the transfer mode, optional functions, and expire time.
l l
The transfer mode can be FTP or SFTP The optional functions include breakpoint, compress, and passive mode.If passive mode is not selected, active mode is selected by default. The expire time ranges from 5 to 3600 seconds.
For detailed description of the parameters, refer to 8.6.8 Parameters for Setting Parameters of Files Transferring. Step 3 Click OK. ----End
Related References
8.6.8 Parameters for Setting Parameters of Files Transferring
8.2.9 Managing Voice Files

The function of managing voice files enables you to load, check, and synchronize the voice files of the NEs. Only the MGW supports this function. 8.2.9.1 Loading a Voice File After a voice file is downloaded to the MGW and saved on the OMU, it does not take effect immediately. To play the voice, you must load the file to the VPU board. 8.2.9.2 Checking a Voice File The information about the MGW voice files is stored on the related MSC server and M2000 server. After a voice file is downloaded to the MGW and saved on the OMU board, it does not
take effect immediately. To play the voice, you must load the file to the VPU board. This function enables you to check whether all the voice files are consistent and whether the voice files on the MGW OMU board match to those on each VPU board. 8.2.9.3 Synchronizing a Voice File This describes how to synchronize a voice file on the active OMU to the standby OMU. In this way, the voice file on the standby OMU can be complete. Thus, in case that the active OMU is faulty, you can start the standby OMU to ensure the normal operation of the MGW.
Loading a Voice File

After a voice file is downloaded to the MGW and saved on the OMU, it does not take effect immediately. To play the voice, you must load the file to the VPU board.
Prerequisite
l l l
You have logged in to the M2000 client. The MGW is properly connected to the M2000 server. The required voice file is available on the active OMU of the MGW.
Context
l l
Voice files can be classified into voice package files and dynamic voice files. Voice package files are categorized into broadband voice package files and narrowband voice package files. A broadband voice package files can be named only tonefile_wb.arj and a narrowband voice package file can be named only tonefile.arj. A single MGW can have only one broadband voice package file and one narrowband voice package file. Dynamic voice files are categorized into broadband dynamic voice files and narrowband dynamic voice files. The extension of a broadband dynamic voice files is .wbv and the extension of a narrowband voice file is .spf. A single MGW can have multiple dynamic voice files.
Procedure
Step 1 Determine the type of the voice file to be loaded. File Type Voice package file Dynamic voice file Step 2 Load the voice package file. Refer to... See Step 2. See Step 3.
CAUTION
During the operation, the asynchronous voice is deleted. Therefore, you must ensure that the loading process is not interrupted. Otherwise, the asynchronous voice is lost.
8-16
Issue 06 (2008-12-16)
1. 2. 3. 4. 5.
Choose Software > Browser or click is displayed.
on the toolbar. The Software Browser window
In the NE tab, select an MGW in the file structure tree. In the Tone tab, click Load. The Tone files Loading Wizard-Boards Separating dialog box is displayed. Select an active board. Click Query ATone. Delete the asynchronous announcement.
NOTE
The board cannot be isolated if the asynchronous voice is not deleted.
6. 7. 8. 9.
In the Tone files Loading Wizard-Tone Files Loading dialog box, click the Tone File Load Information tab. Select the voice package file to be loaded in the file structure tree. Click Load. Then you can view the loading progress and status in the Tone File Load Information tab. After the loading is complete, click Next. The Tone files Loading Wizard-Boards Activating dialog box is displayed. Click Active to activate the isolated board. The deleted asynchronous voice is loaded to the board again when the board is being activated.
10. Click Finish. Then the voice file is completely loaded. Step 3 Load the dynamic voice file. 1. 2. 3. 4. 5. 6. 7. 8. Choose Software > Browser or click is displayed. on the toolbar. The Software Browser window
In the NE tab, select an MGW in the file structure tree. In the Tone tab, click Load. The Tone files Loading Wizard-Boards Separating dialog box is displayed. Select an active board. Click Next. The Tone files Loading Wizard-Tone Files Loading dialog box is displayed. In the Tone files Loading Wizard-Tone Files Loading dialog box, click the Tone File Load Information tab. Select the dynamic voice file to be loaded in the file structure tree. Click Load. Then you can view the loading progress and status in the Tone File Load Information tab. After the loading is complete, click Next. The Tone files Loading Wizard-Boards Activating dialog box is displayed. Click Finished. Then the voice file is completely loaded.
----End
Checking a Voice File

The information about the MGW voice files is stored on the related MSC server and M2000 server. After a voice file is downloaded to the MGW and saved on the OMU board, it does not take effect immediately. To play the voice, you must load the file to the VPU board. This function enables you to check whether all the voice files are consistent and whether the voice files on the MGW OMU board match to those on each VPU board.
Prerequisite
l l
You have logged in to the M2000 client. The MGW and its active MSC server are properly connected to the M2000 server.
Context
l
Each voice file contains the voice ID, though which the MSC server identifies the voice file. You can check whether the voice IDs stored on the MSC server match to those contained in the voice files on the MGW. The MGW centrally manages the voice files through the M2000. You can check whether the voice files on the M2000 server match to those stored on the MSG OMU board. On the MGW, you must load the voice files from the OMU board to the VPU board to make the files effective. You can check whether the voice files on each VPU board match.
Procedure
Step 1 Choose Software > Browser or click displayed. on the toolbar. The Software Browser window is
Step 2 In the NE tab, select an MGW in the file structure tree. Step 3 In the Tone tab, click Check. The Confirm dialog box is displayed. Step 4 Click Yes. The Tone File Check dialog box is displayed. Step 5 Check the results.
l
In the Compared with MSC Server tab, you can view the result of comparing the voice ID on the MSC server with those contained in each voice file. In the Compared with OMC tab, you can view the result of comparing the voice files on the M2000 server with those on the MGW OMU board. In the Compared with MGW tab, you can view the result of comparing the voice files on the MGW OMU board with those on each VPU board.
----End
Synchronizing a Voice File

This describes how to synchronize a voice file on the active OMU to the standby OMU. In this way, the voice file on the standby OMU can be complete. Thus, in case that the active OMU is faulty, you can start the standby OMU to ensure the normal operation of the MGW.
Prerequisite
l l
You have logged in to the M2000 client. The MGW is properly connected to the M2000 server.
Context
l
After you load a voice file to the MGW, it is loaded to only the active OMU. Therefore, you must perform this operation to synchronize the voice file to the standby OMU.
8-18

l
After you delete a voice file, the voice files on both the active OMU and the standby OMU are deleted. Therefore, you do not need to perform the synchronization.
Procedure
Step 2 In the NE tab, select an MGW in the file structure tree. Step 3 In the Tone tab, click Synchronize. You can check the synchronization progress in the Immediate Task tab. ----End
8.3 Upgrading NE Software and Patches

This describes how to upgrade NE software and patches. The related operations are downloading, synchronizing, loading, activating, confirming, deactivating, and deleting. The NEs supporting this function are RNC, NodeB, MSC server, MGW, SGSN, GGSN,BSC, BTS, and ASN-GW.
Context
l
You can upgrade the M2000 NE software and patches only after purchasing the license of the software management function. The system displays the dialog box that needs confirming with an audible alert when you upload or activate the NE software and patches.
8.3.1 Managing a Scheduled Upgrade To upgrade software of the NodeB, BSC and BTS. The M2000 provides the function of plan upgrade tasks. You can check, import, or export plan upgrade tasks. 8.3.2 Upgrading the RNC Software and Patch This task describes how to upgrade the RNC software and patches. 8.3.3 Upgrading the SGSN Software and Patch This task describes how to upgrade the SGSN software and patches. 8.3.4 Upgrading the GGSN Software and Patch This task describes how to upgrade the GGSN software and patches. 8.3.5 Upgrading the MSC Server Software Patch This task describes how to upgrade the patches of the MSC Server. 8.3.6 Upgrading the MGW Software and Patch By creating an upgrade task, you can easily upgrade the software of one or multiple MGWs or patches. 8.3.7 Upgrading the AG Software and Patch This task describes how to upgrade the AG software and patches. 8.3.8 Upgrading the ICS Software The M2000 provides the NodeB upgrade wizard. You can easily upgrade the software of one or multiple ICSs. 8.3.9 Upgrading NodeB NE Software and Patch
By creating an upgrade task, you can easily upgrade the software and patches of one or multiple NodeBs. 8.3.10 Upgrading the BSC Software and Patch This task describes how to upgrade the BSC software and patches. 8.3.11 Upgrading the BTS Software This describes how to upgrade the BTS software. 8.3.12 Upgrading the ASN-GW Software and Patch This task describes how to upgrade the ASN-GW software and patches. 8.3.13 Monitoring the Procedure of Software Upgrade Monitor the NE upgrade process, which includes loading, activating, and synchronizing the NE software, and loading, activating, deactivating, confirming, and uninstalling the NE patches.
8.3.1 Managing a Scheduled Upgrade

To upgrade software of the NodeB, BSC and BTS. The M2000 provides the function of plan upgrade tasks. You can check, import, or export plan upgrade tasks. 8.3.1.1 Browsing a Scheduled Upgrade This task describes how to browse a plan upgrade task about NodeB, BSC and BTS. 8.3.1.2 Importing a Scheduled Upgrade This task describes how to import files of plan upgrade tasks that are created according to upgrade task templates. You can create plan upgrade tasks in batch by the imported files. 8.3.1.3 Exporting a Scheduled Upgrade This task describes how to export plan upgrade tasks. You can edit the exported files, and then import them. 8.3.1.4 File Format of a Scheduled Upgrade By reading NodeB, BSC, and BTS scheduled upgrade templates, you can add scheduled upgrade tasks. A NodeB scheduled upgrade template is an Excel file with a fixed format.
Browsing a Scheduled Upgrade

This task describes how to browse a plan upgrade task about NodeB, BSC and BTS.
Procedure
Choose Software > Plan Upgrade Task. The Plan Upgrade Task window is displayed. The task list displays all the scheduled upgrade tasks. ----End
Importing a Scheduled Upgrade

This task describes how to import files of plan upgrade tasks that are created according to upgrade task templates. You can create plan upgrade tasks in batch by the imported files.
Context
l
The current import data overwrites the previously imported data.

8-20

l l
Please refer to 8.3.1.4 File Format of a Scheduled Upgrade. Click Template, you can obtain the template of plan upgrade task.
Procedure
Step 1 Choose Software > Plan Upgrade Task. The Plan Upgrade Tasks window is displayed. Step 2 Click Import to view the Open dialog box. Step 3 Select the excel files to be imported, or type the name and path of the excel files to be imported. Step 4 Click Open. Step 5 Click OK. ----End
Exporting a Scheduled Upgrade

This task describes how to export plan upgrade tasks. You can edit the exported files, and then import them.
Prerequisite
Data exists in the table in Plan Upgrade Tasks.
Context
The format of a plan upgrade task can be the Excel or the CSV format.
Procedure
Step 1 Choose Software > Plan Upgrade Task. The Plan Upgrade Tasks window is displayed. Step 2 Click Export to view the Save dialog box.
NOTE
You can only export a table that has data.
Step 3 Type a file name and a path. Step 4 Click Save. ----End
File Format of a Scheduled Upgrade

By reading NodeB, BSC, and BTS scheduled upgrade templates, you can add scheduled upgrade tasks. A NodeB scheduled upgrade template is an Excel file with a fixed format.
Scheduled Download
The NodeB, MGW , BSC, and BTS supports two kinds of scheduled upgrade tasks, that is, scheduled download and scheduled activation.
To know the format of a scheduled download template, refer to Table 8-2. Table 8-2 Scheduled download template Item Download time Content For example 2006-08-30 02:00:30
NOTE The format of digits in the cell should be Text.
Name of an NE type Software version to be downloaded on the server Whether download by configuration BootRom version to be downloaded on the server Cold patch version to be downloaded on the server. Hot patch version to be download on the server. NE Name
For example NodeB3802C For example BTS3802CV100R003C02B090 Y or N For example BTS3802CV100R003C02B090 For example: BTS3802CV100R003C02B090SP01 For example: BTS3802CV100R003C02B090SP01 Name of an NE that need be upgraded
Scheduled Activation
To know the format of a scheduled activation template, refer to Table 8-3. Table 8-3 Scheduled activation template Item Activation time Whether activate Bootrom Whether activate software Whether activate Bootrom of RRU Whether activate software of RRU Whether activate cold patches Whether activate cold patches of RRU Whether activate hot patches NE Name Content For example 2006-08-30 02:00:30 Y or N Y or N Y or N Y or N Y or N Y or N Y or N Name of an NE that need be upgraded
NOTE
The NE to be upgraded must be the NodeB and exist on the topology view.
8-22
Issue 06 (2008-12-16)
8.3.2 Upgrading the RNC Software and Patch

This task describes how to upgrade the RNC software and patches. 8.3.2.1 RNC NE Software and Patch This part describes the software versions of the RNC, naming rules for its patches, and precautions of software loading. 8.3.2.2 Loading the RNC Software This task describes how to load software versions to each board of the RNC. 8.3.2.3 Activating the RNC Software After being loaded to the RNC, the RNC software is changed to the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated. 8.3.2.4 Loading the RNC Software Patch On the M2000, you can use the software management function to load the RNC patches to each board of the RNC. 8.3.2.5 Activating the RNC Software Patch After being loaded to the RNC, the RNC software patch is changed to the deactivated state. After the activation command is issued, the RNC automatically restarts. After the RNC runs the loaded patch, the patch is activated. 8.3.2.6 Confirming the RNC Software Patch You can confirm software patch of the software version designated by the RNC through software management. After the mandatory confirmation, the software patch automatically takes effect upon the restart of the RNC. 8.3.2.7 Deactivating the RNC Software Patch You can use the software management function to deactivate the RNC patches that are activated but not confirmed. 8.3.2.8 Removing the RNC Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the RNC.
RNC NE Software and Patch

This part describes the software versions of the RNC, naming rules for its patches, and precautions of software loading.
Introduction to Software and Patch Versions

The software version of the RNC is named in the format of product name + VxxxRxxxCxxBxxy [SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version.
Issue 06 (2008-12-16)
l l
Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.
Precautions of Software Loading

If no patch is available for the RNC, you can download the patch from the file server.
Loading the RNC Software

This task describes how to load software versions to each board of the RNC.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the RNC is already set. The RNC communicates properly with the M2000. The software versions of the RNC are downloaded to the RNC successfully.
Procedure
Step 2 Select an RNC under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. If no software version under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Perform the related operation according to the type of the loading. Loading Type Initial loading Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial loading, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads the configuration files and NE online help to the M2000 client. In this way, you can confirm the parameters that need be set. Non-initial loading Perform Step 5. Step 5 Set parameters in Load Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the RNC Software

After being loaded to the RNC, the RNC software is changed to the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the RNC is already set. The NE is properly connected to the M2000. The applications of the RNC are downloaded to the RNC successfully.
Context
l
Each NE can activate only one software version. After a software version is activated successfully, the original version is automatically set to be deactivate. If the selected software version is already activated, the system informs that the activate operation fails.
Procedure
Step 2 Select an RNC under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. Step 4 Click Activate. Perform the related operation according to the type of the activation. Activation Type Initial activation Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial activation, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the M2000 client to confirm the parameters that need to be set by users. Non-initial activation Perform Step 5. Step 5 Select parameters in Activate Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Loading the RNC Software Patch

On the M2000, you can use the software management function to load the RNC patches to each board of the RNC.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the RNC is already set. The NE is properly connected to the M2000. The software patches of the RNC are downloaded to the RNC successfully.
Procedure
Step 2 Select an RNC under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Step 5 Set parameters in Load Patch Parameters Selection. Step 6 Click OK in the displayed Confirm dialog box. You can view the execution status of the task in Immediate Task. ----End
Activating the RNC Software Patch

After being loaded to the RNC, the RNC software patch is changed to the deactivated state. After the activation command is issued, the RNC automatically restarts. After the RNC runs the loaded patch, the patch is activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the RNC is already set. The NE is properly connected to the M2000. The applications of the RNC are downloaded to the RNC successfully.
Procedure
Step 1 Choose Software > Browser or click . The Software Browser window is displayed.
Step 2 Select an RNC under the navigation tree on the NE tab.

Step 3 Select a software patch on the Patch tab. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 In the Confirm dialog box, click Yes. You can view the execution status of the task in Immediate Task. ----End
Confirming the RNC Software Patch

You can confirm software patch of the software version designated by the RNC through software management. After the mandatory confirmation, the software patch automatically takes effect upon the restart of the RNC.
Context
Before you activate patches, confirm the patches.
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab page, select a RNC from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm. Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End .
Related References
8.6.3 Parameters for RNC Patch
Deactivating the RNC Software Patch

You can use the software management function to deactivate the RNC patches that are activated but not confirmed.
Context
NOTE
Only the patches that are activated but not confirmed can be deactivated. Confirmed patches can be deleted only by deleting patches.
Procedure
The Software Browser window is displayed. Step 2 Select a RNC under the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Removing the RNC Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the RNC.
Procedure
Step 2 Select an RNC under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload. Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
8.3.3 Upgrading the SGSN Software and Patch

This task describes how to upgrade the SGSN software and patches. 8.3.3.1 SGSN Software and Patch This part describes the software versions for the SGSN, naming rules for its patches, and precautions of software loading.
8.3.3.2 Loading the SGSN Software This describes how to load software versions to each board of the SGSN. 8.3.3.3 Activating the SGSN Software After being loaded to the SGSN, the SGSN software is changed to the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated. 8.3.3.4 Synchronizing the SGSN Software This task describes how to synchronize the software in the active area to the standby area. In this situation, the software version in the active area is consistent with that in the standby area. 8.3.3.5 Loading the SGSN Software Patch On the M2000, you can use the software management function to load the SGSN patches to each board of the SGSN. 8.3.3.6 Activating the SGSN Software Patch After being loaded to the SGSN, the SGSN software is changed to the deactivated state. Upon receipt of the activation command, the SGSN automatically reboots. After the SGSN runs the loaded patches, the patches are activated. 8.3.3.7 Confirming the SGSN Software Patch You can confirm software patch of the software version designated by the SGSN through software management. After the mandatory confirmation, the software patch automatically takes effect upon the restart of the SGSN. 8.3.3.8 Deactivating the SGSN Software Patch You can use the software management function to deactivate the SGSN patches that are activated but not acknowledged. 8.3.3.9 Removing the SGSN Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the SGSN.
Related References
8.6.4 Parameters for Other NE Software and Patch
SGSN Software and Patch

This part describes the software versions for the SGSN, naming rules for its patches, and precautions of software loading.

The software version of the SGSN is named in the format of product name + VxxxRxxxCxxBxxy [SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version.
Issue 06 (2008-12-16)
l l
Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.

If no patch is available for the SGSN, you can download the patch from the file server.
Loading the SGSN Software

This describes how to load software versions to each board of the SGSN.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the SGSN is already set. The SGSN communicates properly with the M2000. The software versions of the SGSN are downloaded to the SGSN successfully.
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. If no software version under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Perform the related operation according to the type of the loading. Loading Type Initial loading Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial loading, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads the configuration files and NE online help to the M2000 client. In this way, you can confirm the parameters that need be set. Non-initial loading Perform Step 5. Step 5 Set parameters in Load Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the SGSN Software

After being loaded to the SGSN, the SGSN software is changed to the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the SGSN is already set. The SGSN communicates properly with the M2000. The applications of the SGSN are downloaded to the SGSN successfully.
Context
l
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. Step 4 Click Activate. Perform the related operation according to the type of the activation. Activation Type Initial activation Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial activation, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the M2000 client to confirm the parameters that need to be set by users. Non-initial activation Perform Step 5. Step 5 Select parameters in Activate Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Synchronizing the SGSN Software

This task describes how to synchronize the software in the active area to the standby area. In this situation, the software version in the active area is consistent with that in the standby area.
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Click Synchronize in Version. You can query the progress of the task in Immediately Task. ----End
Loading the SGSN Software Patch

On the M2000, you can use the software management function to load the SGSN patches to each board of the SGSN.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the SGSN is already set. The SGSN communicates properly with the M2000. The software patches of the SGSN are downloaded to the SGSN successfully.
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Step 5 Set parameters in Load Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the SGSN Software Patch

After being loaded to the SGSN, the SGSN software is changed to the deactivated state. Upon receipt of the activation command, the SGSN automatically reboots. After the SGSN runs the loaded patches, the patches are activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the SGSN is already set. The SGSN communicates properly with the M2000. The applications of the SGSN are downloaded to the SGSN successfully.
Procedure
. Step 1 Choose Software > Browser or click The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 In the Confirm dialog box, click Yes. You can view the execution status of the task in Immediate Task. ----End
Confirming the SGSN Software Patch

You can confirm software patch of the software version designated by the SGSN through software management. After the mandatory confirmation, the software patch automatically takes effect upon the restart of the SGSN.
Context
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab, select an SGSN from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm.
Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Deactivating the SGSN Software Patch

You can use the software management function to deactivate the SGSN patches that are activated but not acknowledged.
Context
NOTE
Only the patches that are activated but not acknowledged can be deactivated. You can delete acknowledged patches only by deleting patches.
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Removing the SGSN Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the SGSN.
Procedure
The Software Browser window is displayed. Step 2 Select an SGSN under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload.
Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
8.3.4 Upgrading the GGSN Software and Patch

This task describes how to upgrade the GGSN software and patches. 8.3.4.1 GGSN NE Software and Patch This part describes the software versions for the GGSN, naming rules for its patches, and precautions of software loading. 8.3.4.2 Loading the GGSN Software This describes how to load software versions to each board of the GGSN. 8.3.4.3 Activating the GGSN Software After being loaded to the GGSN, the software is in the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated. 8.3.4.4 Loading the GGSN Software Patch On the M2000, you can use the function of software management to load the GGSN patches to each board of the GGSN. 8.3.4.5 Activating the GGSN Software Patch After being loaded to the GGSN, the GGSN software patch is changed to the deactivated state. After the activate command is issued, the GGSN automatically restarts. After the GGSN runs the loaded patches, the patches are activated. 8.3.4.6 Confirming the GGSN Software Patch This task is performed to confirm software patch of the software version designated by the GGSN NE through software management. After the mandatory confirmation, the software patch automatically take effect upon the restart of the GGSN. 8.3.4.7 Deactivating the GGSN Software Patch You can use the software management function to deactivate the GGSN patches that are activated but not acknowledged. 8.3.4.8 Removing the GGSN Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the GGSN.
Related References
GGSN NE Software and Patch

This part describes the software versions for the GGSN, naming rules for its patches, and precautions of software loading.
Issue 06 (2008-12-16)
8-35

The software version of the GGSN is named in the format of product name + VxxxRxxxCxxBxxy[SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.
l l l

If no patch is available for the GGSN, you can download the patch through the file server.
Loading the GGSN Software

This describes how to load software versions to each board of the GGSN.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the GGSN is already set. The GGSN communicates properly with the M2000. The software versions of the GGSN are downloaded to the GGSN successfully.
Procedure
. Step 1 Choose Software > Browser or click The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab page. Step 3 Select a software version on the Version tab page. If no software version under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Perform the related operation according to the type of the loading.
8-36
Issue 06 (2008-12-16)
Loading Type Initial loading
Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial loading, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads the configuration files and NE online help to the M2000 client. In this way, you can confirm the parameters that need be set.
Non-initial loading Perform Step 5. Step 5 Set parameters in Load Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the GGSN Software

After being loaded to the GGSN, the software is in the deactivated state. After the activation command is issued, the SGSN automatically restarts. After the SGSN runs the loaded software, the software is activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the GGSN is already set. The GGSN communicates properly with the M2000. The applications of the GGSN are downloaded to the GGSN successfully.
Context
l
Procedure
The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. Step 4 Click Activate. Perform the related operation according to the type of the activation.
Activation Type Initial activation
Procedure In the displayed Upgrade dialog box, click OK and then perform Step 5. For initial activation, the Upgrade dialog box is displayed, showing the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the M2000 client to confirm the parameters that need to be set by users.
Non-initial activation Perform Step 5. Step 5 Select parameters in Activate Software. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Loading the GGSN Software Patch

On the M2000, you can use the function of software management to load the GGSN patches to each board of the GGSN.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the GGSN is already set. The GGSN communicates properly with the M2000. The software patches of the GGSN are downloaded to the GGSN.
Procedure
The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Step 5 Set parameters in Load Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the GGSN Software Patch

After being loaded to the GGSN, the GGSN software patch is changed to the deactivated state. After the activate command is issued, the GGSN automatically restarts. After the GGSN runs the loaded patches, the patches are activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the GGSN is already set. The GGSN communicates properly with the M2000. The applications of the GGSN are downloaded to the GGSN successfully.
Procedure
Step 1 Choose Software > Browser or click . The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 In the Confirm dialog box, click Yes. You can view the execution status of the task in Immediate Task. ----End
Confirming the GGSN Software Patch

This task is performed to confirm software patch of the software version designated by the GGSN NE through software management. After the mandatory confirmation, the software patch automatically take effect upon the restart of the GGSN.
Context
Confirm the patches before you activate them.
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab, select a GGSN from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm.
Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Deactivating the GGSN Software Patch

You can use the software management function to deactivate the GGSN patches that are activated but not acknowledged.
Context
NOTE
Procedure
The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Removing the GGSN Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the GGSN.
Procedure
The Software Browser window is displayed. Step 2 Select a GGSN under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload.
Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
8.3.5 Upgrading the MSC Server Software Patch

This task describes how to upgrade the patches of the MSC Server.
Context
l l
Before you perform the patch operation, take care to read the Patch Operation Guide. Select a module for each type of boards to perform a patch operation. After the patch operation is sucessful, perform the same operation for all other modules.
8.3.5.1 MSC Server NE Software and Patch This part describes the software versions for the MSC server, naming rules for its patches, and precautions of software loading. 8.3.5.2 Loading the MSC Server Software Patch On the M2000, you can use the function of software management function to load the MSC server patches to each board of the MSC server. 8.3.5.3 Activating the MSC Server Software Patch After being loaded to the MSC server, the software patch is changed to the deactivated state. After the activate command is sent, the MSC server automatically restarts. After the MSC server runs the loaded patches, the patches are activated. 8.3.5.4 Confirming the MSC Server Software Patch You can confirm software patch of the software version designated by the MSC server through the software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the MSC Server. 8.3.5.5 Deactivating the MSC Server Software Patch You can use the software management function to deactivate the MSC Server patches that are activated but not acknowledged. After deactivation, an active patch becomes inactive. 8.3.5.6 Removing the MSC Server Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the MSC server.
Related References
MSC Server NE Software and Patch

This part describes the software versions for the MSC server, naming rules for its patches, and precautions of software loading.

The software version of the MSC server is named in the format of product name + VxxxRxxxCxxBxxy[SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.
l l l

If no patch is available for the MSC server, you can download the patch through the file server.
Loading the MSC Server Software Patch

On the M2000, you can use the function of software management function to load the MSC server patches to each board of the MSC server.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the MSC server is already set. The MSC server communicates properly with the M2000. The software patches of the MSC server are downloaded to the MSC Server successfully.
Context
Load patches when the traffic volume is low.
Procedure
The Software Browser window is displayed. Step 2 Select an MSC server under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Step 5 Set parameters in Load Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
Activating the MSC Server Software Patch

After being loaded to the MSC server, the software patch is changed to the deactivated state. After the activate command is sent, the MSC server automatically restarts. After the MSC server runs the loaded patches, the patches are activated.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the MSC server is already set. The MSC server communicates properly with the M2000. The applications of the MSC server are downloaded to the MSC server successfully.
Context
l l
The board type is patch specific. Boards of the same type are distinguished by module ID. To ensure the correctness, first activate the patch of a module, and then activate patches of all the modules.
Procedure
The Software Browser window is displayed. Step 2 Select an MSC server under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 In the Confirm dialog box, click Yes. You can view the execution status of the task in Immediate Task. ----End
Confirming the MSC Server Software Patch

You can confirm software patch of the software version designated by the MSC server through the software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the MSC Server.
Context
l l
Before you activate patches, confirm the patches. The active and standby boards need be confirmed separately.
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab page, select a MSC Server from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm. Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End .
Deactivating the MSC Server Software Patch

You can use the software management function to deactivate the MSC Server patches that are activated but not acknowledged. After deactivation, an active patch becomes inactive.
Context
l
Only the patches that are activated but not acknowledged can be deactivated. Acknowledged patches can only be deleted rather than deactivated. 8.1.3 Patch States describes the state transition of a patch.
Procedure
The Software Browser window is displayed. Step 2 Select an MSC Server from the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Removing the MSC Server Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the MSC server.
Procedure
The Software Browser window is displayed. Step 2 Select an MSC server under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload. Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can view the execution status of the task in Immediate Task. ----End
8.3.6 Upgrading the MGW Software and Patch

By creating an upgrade task, you can easily upgrade the software of one or multiple MGWs or patches.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the MGW is configured. The connection between the MGW and the M2000 server is normal. The software or patch to be upgraded is available on the M2000 server.
Introduction to Software and Patch Versions Upgrade Procedure

The software version of the MGW is named in the format of product name + VxxxRxxxCxxBxxy [SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch. You can also upgrade the MGW software and patch through a one-step operation. For details, refer to 8.3.3 Upgrading the SGSN Software and Patch. For you deactivate or delete the patch. For details of the patch state transition, refer to 8.1.3 Patch States.
l l l l
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade MGW . The NE Upgrade Wizard window is displayed. Step 2 Select an upgrade type under Upgrade Type.
l l
To upgrade the software, select Upgrade BootRom and software. To upgrade the patch, select Upgrade patch.
TIP
To deactivate or delete the patch, select Remove patch.
Step 3 Select one or more MGWs under the All NE navigation tree. You can select Version to categorize the NEs in the navigation tree. Step 4 Click Click Step 5 Click Next. Step 6 Select a software or patch version under Parameter Setting. Step 7 Select one or multiple operations in Operation Setting. Step 8 Click Finish to view the Message prompt box. Step 9 Click OK. You can view the execution status of the task in the Immediate Task window. ----End or or to shift the selected NEs to the list in the right part of the window. to move the previous NEs back.
Related References
8.3.7 Upgrading the AG Software and Patch

This task describes how to upgrade the AG software and patches. 8.3.7.1 AG Software and Patch This describes the software versions for the AG, naming rules for its patches, and precautions for loading the software. 8.3.7.2 loading the AG Software This task describes how to load software versions to each board of the AG. 8.3.7.3 Activating the AG Software After software is loaded to the AG, the software is in the deactivated state. Upon receipt of the activation command, the AG automatically reboots. After the AG runs the loaded software, the software is activated. 8.3.7.4 Synchronizing the AG Software This task describes how to synchronize the software in the active area to the standby area. In this situation, the software version in the active area is consistent with that in the standby area. 8.3.7.5 Loading the AG Software Patch
On the M2000, you can use the software management function to load the AG patches to each board of the AG. 8.3.7.6 Activating the AG Software Patch After patches are loaded to the AG, the patches are in the deactivated state. Upon receipt of the activation command, the AG automatically reboots. After the AG runs the loaded patches, the patches are activated. 8.3.7.7 Confirming the AG Software Patch You can confirm software patch of the software version designated by the AG through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the AG. 8.3.7.8 Deactivating the AG Software Patch You can use the software management function to deactivate the AG patches that are activated but not acknowledged. 8.3.7.9 Deleting the AG Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the AG.
AG Software and Patch

This describes the software versions for the AG, naming rules for its patches, and precautions for loading the software.
Introduction to Software Versions

The software version of the AG is named in the format of product name + VxxxRxxxCxxBxxy [SPxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a specific sub-version of features delivered to customers. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.
l l l
Naming Rules for Patches

The patches of the AG are named in the format of version + board name (short name) + identifier.
Precautions for Software Loading

If a patch is not available for the AG, you can download the patch from the file server.
loading the AG Software

This task describes how to load software versions to each board of the AG.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the AG is already set. The AG communicates properly with the M2000. The software versions of the AG are downloaded to the AG successfully.
Procedure
The Software Browser window is displayed. Step 2 Select a AG under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. If no software version under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load.
NOTE
If you load the AG software versions for the first time, the Upgrade dialog box is displayed. You can browse the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the client to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view Load Software Parameters Selection.
Step 5 Set parameters in Load Software Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Activating the AG Software

After software is loaded to the AG, the software is in the deactivated state. Upon receipt of the activation command, the AG automatically reboots. After the AG runs the loaded software, the software is activated.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the AG is already set. The AG communicates properly with the M2000. The applications of the AG are downloaded to the AG successfully.
Context
l
Each NE can active only one software version. After a software version is activated successfully, the original version is automatically set to be deactivate.
8-48

l
If the selected software version is already activated, the system prompts that the activate operation fails.
Procedure
The Software Browser window is displayed. Step 2 Select an AG from the navigation tree on the NE tab. Step 3 Select a software version under Software. Step 4 Click Activate.
NOTE
If you activate the AG for the first time, the Software dialog box is displayed. You can browse the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the client to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view Activate Software Parameters Selection.
Step 5 Select parameters in Activate Software Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Synchronizing the AG Software

This task describes how to synchronize the software in the active area to the standby area. In this situation, the software version in the active area is consistent with that in the standby area.
Procedure
The Software Browser window is displayed. Step 2 Select an AG under the navigation tree on the NE tab. Step 3 Click Synchronize in Version. You can query the progress of the task in Immediately Task. ----End
Loading the AG Software Patch

On the M2000, you can use the software management function to load the AG patches to each board of the AG.
Prerequisite
l l l l
You have successfully logged in to the M2000 client. The relay server of the AG is configured. The AG communicates properly with the M2000. The software patches of the AG are successfully downloaded to the AG.
Procedure
The Software Browser window is displayed. Step 2 Select a AG under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab. If a software patch under the corresponding NE cannot be loaded, you can download the files to the NE by using the server. Step 4 Click Load. Step 5 Set the parameters in Load Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Activating the AG Software Patch

After patches are loaded to the AG, the patches are in the deactivated state. Upon receipt of the activation command, the AG automatically reboots. After the AG runs the loaded patches, the patches are activated.
Prerequisite
l l l l
You have successfully logged in to the M2000 client. The relay server of the AG is configured. The AG communicates properly with the M2000. The applications of the AG are successfully downloaded to the AG.
Procedure
The Software Browser window is displayed. Step 2 Select an AG from the navigation tree on the NE tab. Step 3 Select a software patch under Patch. Step 4 Click Activate.
Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Confirming the AG Software Patch

You can confirm software patch of the software version designated by the AG through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the AG.
Context
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab, select an AG from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm. Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End .
Deactivating the AG Software Patch

You can use the software management function to deactivate the AG patches that are activated but not acknowledged.
Context
NOTE
Procedure
Step 1 Choose Software > Browser or
Issue 06 (2008-12-16)
.
8-51
The Software Browser window is displayed. Step 2 Select a AG under the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Deleting the AG Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the AG.
Procedure
The Software Browser window is displayed. Step 2 Select a AG under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload. Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
8.3.8 Upgrading the ICS Software

The M2000 provides the NodeB upgrade wizard. You can easily upgrade the software of one or multiple ICSs.
Prerequisite
l l l
The ICS is properly connected to the server. You can conveniently upgrade one or more NodeBs. The relay server of the ICS is already set.
Context
The software version of the ICS is named in the format of product name + VxxxRxxxCxxBxxy [SPxx].

l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R-version delivered to customers. Bxxy (Build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.
l l l
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade ICS . The NE Upgrade Wizard window is displayed. Step 2 Select an upgrade type under Upgrade Type. Step 3 Select one or more ICSs under the All NE navigation tree. You can select Version to organize the NEs in the navigation tree. Step 4 Click Click Step 5 Click Next. Step 6 Select necessary operations under Operation Setting.
NOTE
or or
to shift the selected NEs to the list in the right part of the window. to restore the NEs to the original position.
You can select multiple operations and implement the one-step upgrade.
Step 7 Click Finish to view the Message prompt box. Step 8 Click OK. You can query the progress of the task in Immediately Task. ----End
8.3.9 Upgrading NodeB NE Software and Patch

By creating an upgrade task, you can easily upgrade the software and patches of one or multiple NodeBs.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the NodeB is configured. The connection between the M2000 and the NodeB is normal. The software or patch to be upgraded is available on the M2000 server.
Issue 06 (2008-12-16)
8-53
Introduction to Software and Patch Versions Upgrade Procedure

The software version of the NodeB is named in the format of product name + VxxxRxxxCxxBxxy[SPxxx].
l
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a feature version under the R version. Bxxy (build) indicates the build versions during the developing process. SPxxx (Service Pack) indicates the version of a patch. SPCxxx indicates a cold patch. SPHxxx indicates a hot patch. Usually, an RNC hosts tens or hundreds of NodeBs. You can upgrade the software of one NodeB first. After verifying the software upgrade, install and verify the patches, and then upgrade other NodeBs in batches. When upgrading all the NodeBs in batches, you can divide them into groups and then upgrade the NodeBs in each group in batches. You can also upgrade the NodeB software and patch through a one-step operation. For details of the operation, refer to 8.3.3 Upgrading the SGSN Software and Patch. Note that the NodeB need not be loaded during upgrade. For you deactivate or delete the patch. For details of the patch state transition, refer to 8.1.3 Patch States.
l l l
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade NodeB . The NE Upgrade Wizard window is displayed. Step 2 Select an upgrade type under Upgrade Type.
l l
To upgrade the software, select Upgrade BootRom and software. To upgrade the patch, select Upgrade Hot Patch.
TIP
To deactivate or delete the patch, select Remove patch.
Step 3 Select one or more NodeBs under the All NE navigation tree. You can select RNC, NodeB Type, or Version to categorize the NEs in the navigation tree. Step 4 Click Click Step 5 Click Next. Step 6 Select a software or patch version under Parameter Setting. Step 7 Select one or multiple operations in Operation Setting.
or or
to shift the selected NEs to the list in the right part of the window. to move the previous NEs back.

NOTE
The upgrade operations vary according to the software types. For details, refer to Parameters for Upgrading the NodeB Software.
Step 8 Click Finish to view the Message prompt box. Step 9 Click OK. You can view the execution status of the task in the Immediate Task window. ----End
Related References
8.6.4 Parameters for Other NE Software and Patch 8.6.6 Parameters for Upgrading the NodeB Software
8.3.10 Upgrading the BSC Software and Patch

This task describes how to upgrade the BSC software and patches. 8.3.10.1 BSC Software and Patch This describes the software versions for the BSC, naming rules for its patches, and precautions for software loading. 8.3.10.2 Downloading the BSC Software You can download software on the M2000 server to the disk of the BSC. 8.3.10.3 Upgrading the BSC Software You can upgrade the BSCs in BSC6000 Upgrade Wizard. If exceptions occur during the process of upgrade, the system can roll back to the previous version. 8.3.10.4 Loading the BSC Software Patch This task describe how to load software patches to each board of the BSC. 8.3.10.5 Activating the BSC Software Patch After patches are loaded to the BSC, the patches are in the deactivated state. Upon receipt of the activation command, the BSC automatically reboots. After the BSC runs the loaded patches, the patches are activated. 8.3.10.6 Confirming the BSC Software Patch You can confirm software patch of the software version designated by the BSC through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the BSC. 8.3.10.7 Deactivating the BSC Software Patch You can use the software management function to deactivate the BSC patches that are activated but not confirmed. 8.3.10.8 Deleting the BSC Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the BSC. 8.3.10.9 Rollbacking the BSC Software Patch This describes how to roll back the current patch version to the status before the upload according to your requirements.
BSC Software and Patch

This describes the software versions for the BSC, naming rules for its patches, and precautions for software loading.

The software version of the BSC is named in the format of product name + VxxxRxxxCxxBxxy [SPxx]. Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a specific sub-version of features delivered to customers. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.

The patches of the BSC are named in the format of version + board name (short name) + identifier.

If no patch is available for the BSC, you can download the patch through the file server.
Downloading the BSC Software

You can download software on the M2000 server to the disk of the BSC.
Procedure
The Software Browser window is displayed. Step 2 Select a BSC under the navigation tree on the NE tab page. Step 3 Select a software version under Software. Step 4 Click Download From NM. The Version Selection window is displayed. Step 5 Select a version that needs to download in Name. Select SOFTWARE in the Software Type pull-down box. Step 6 Click OK. ----End
Upgrading the BSC Software

You can upgrade the BSCs in BSC6000 Upgrade Wizard. If exceptions occur during the process of upgrade, the system can roll back to the previous version.
Prerequisite
l l l
You have logged in to the M2000 client. The relay server of the BSC is already set. The BSCs communicate properly with the M2000.
Context
If exceptions occur during the upgrade of the BSCs, the system prompts you to exit the upgrade and allows the rollback to the previous state.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade BSC6000 . The NE Selection is displayed. Step 2 In the navigation tree of NEs, choose one or more BSCs to be upgraded. Step 3 ClickOK. The BSC6000 Upgrade Wizard is displayed. Step 4 Choose the software version to be upgraded in Upgrade Version, clickNext. The system displays the progress of downloading the upgrade packet to the GBAM/GOMU. Step 5 When the progress bar displays 100%, click Next. The system displays the progress of downloading the new version data from the network management server to the GBAM/GOMU. Step 6 When the progress bar displays 100%, click Next to check the progress before the upgrade. You can click Fetch Report to obtain a upgrade report. You can also view and store relevant system information and operation records. Step 7 When the progress bar displays 100%, click Next to load software and BIOS. You can click Fetch Report to obtain a upgrade report. You can also view and store relevant system information and operation records. Step 8 When the progress bar displays 100%, click Next to perform the upgrade. You can click Fetch Report to obtain a upgrade report. You can also view and store relevant system information and operation records. Step 9 When the progress bar displays 100%, click Next to perform check before the upgrade. You can click Fetch Report to obtain a upgrade report. You can also view and store relevant system information and operation records. Step 10 When the progress bar displays 100%, click Next to submit the upgrade. The system prompts that when the upgrade is submitted, performing rollback is not allowed. When the upgrade submission is finished, the system prompts that the user upgrade is finished. ----End
Loading the BSC Software Patch

This task describe how to load software patches to each board of the BSC.
Prerequisite
l l l
You have logged in to the M2000 client successfully. The BSC communicates properly with the M2000. The software is downloaded from the M2000 server to the disk of the BSC.
Procedure
The Software Browser window is displayed. Step 2 Select a BSC under the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab page. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load. Step 5 Set parameters in Load Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Activating the BSC Software Patch

After patches are loaded to the BSC, the patches are in the deactivated state. Upon receipt of the activation command, the BSC automatically reboots. After the BSC runs the loaded patches, the patches are activated.
Prerequisite
l l l
You have logged in to the M2000 client successfully. The BSC communicates properly with the M2000. The applications of the BSC are downloaded to the BSC successfully.
Procedure
The Software Browser window is displayed. Step 2 Select a BSC under the navigation tree on the NE tab page. Step 3 Select a software patch under Patch. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection.
Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Confirming the BSC Software Patch

You can confirm software patch of the software version designated by the BSC through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the BSC.
Context
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab page, select a BSC from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm. Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End .
Deactivating the BSC Software Patch

You can use the software management function to deactivate the BSC patches that are activated but not confirmed.
Context
NOTE
Only the patches that are activated but not confirmed can be deactivated. Confirmed patches can be deleted only by deleting patches.
Procedure
The Software Browser window is displayed.

Step 2 Select a BSC under the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Deleting the BSC Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the BSC.
Procedure
The Software Browser window is displayed. Step 2 Select a BSC under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload. Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Rollbacking the BSC Software Patch

This describes how to roll back the current patch version to the status before the upload according to your requirements.
Procedure
The Software Browser window is displayed. Step 2 Select a BSC under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Rollback. You can query the progress of the task in Immediately Task. ----End
8.3.11 Upgrading the BTS Software

This describes how to upgrade the BTS software. 8.3.11.1 BTS Software This describes the software versions for the BTS, and precautions for software loading. 8.3.11.2 Loading the BTS Software This describes how to upload the software of the BTSs. 8.3.11.3 Activating the BTS Software After being loaded to each BTS, the version file is in non-activation status. After the activation command is delivered, the software version file is delivered from the TMU board to other boards. The software on each board is activated. 8.3.11.4 Upgrading the BTS Software by One Push This describes how to upgrade the BTS software by one push. In BTS Upgrade of the M2000 client, you can select the software version and its mapping BTS. Select the uploading and activation operations simultaneously and issue the commands to the NEs. The M2000 client displays the progress of task performance. The results are reported to the M2000 after all the operations are completed by the NEs. 8.3.11.5 Querying the BTS NE Information This describes how to query the BTS information to familiarize yourself with the name and type of the BTS that is connected with the M2000. In addition, you can find the BSC to which the BTS belongs. 8.3.11.6 Querying the Version of BTS Board This describes how to query the version of the BTS board to learn the version information about the running BTS boards.
BTS Software
This describes the software versions for the BTS, and precautions for software loading.
Software Version Number Description

The software version of the BTS server is named in the format of product name + VxxxRxxxCxxBxxy. Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a specific sub-version of features delivered to customers. Bxxy (build) indicates the build versions during the developing process.
Precautions for Uploading

If the upload software does not exist in relevant BTS, you can download the version file from the server to the relevant BTS. The upload sequence is as follows: upload the TMU board, and then upload other boards.
Issue 06 (2008-12-16)
8-61
Loading the BTS Software

This describes how to upload the software of the BTSs.
Prerequisite
l l l
You have logged in to the M2000 client successfully. The BTS communicates properly with the M2000. The software of the BTS is downloaded to the BSC6000 successfully.
Procedure
The Software Browser window is displayed. Step 2 In the navigation tree under the NE tab, select a BTS. Step 3 Select a software version under Available Loading Software. If no software version is available for the NE, you can download the related file from the server. Step 4 Select a file to be loaded in the file list. You can load only one file each time. Step 5 Click Load. You can view the execution status in Immediately Task. ----End
Activating the BTS Software

After being loaded to each BTS, the version file is in non-activation status. After the activation command is delivered, the software version file is delivered from the TMU board to other boards. The software on each board is activated.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the BTS is already set. The BTS communicates properly with the M2000. The applications of the BTS are downloaded to the BTS successfully.
Context
You need to activate the TMU board before activating other boards.
Procedure
The Software Browser window is displayed.

Step 2 Select a BTS from the navigation tree on the NE tab. Step 3 Choose a software type in Software Type field under the Available Activating Software. Step 4 In the Version NO. field, choose the version number according to the software type. Step 5 Click Activate. Step 6 In Select Board Parameter, choose one or more board numbers of the software versions to be activated. Step 7 Click OK. You can query the progress of the task in Immediately Task. ----End
Upgrading the BTS Software by One Push

This describes how to upgrade the BTS software by one push. In BTS Upgrade of the M2000 client, you can select the software version and its mapping BTS. Select the uploading and activation operations simultaneously and issue the commands to the NEs. The M2000 client displays the progress of task performance. The results are reported to the M2000 after all the operations are completed by the NEs.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the BTS is already set. The BTS communicates properly with the M2000. The applications of the BTS are downloaded to the BSC6000 successfully.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade GBTS . The BTS Upgrade is displayed. Step 2 In the Select NE tree, select one or multiple BTSs. You can search the BTS by entering key words in the Search box. You can select BSC6000 or select one or all BTSs in GBTS Type. Sort the BTSs according to the site types or the BSCs they belong to. Step 3 Click
l l l
to add the selected BTS to the valid domain at the right side. to add all the BTSs to the valid domain at the right side. to clear one or multiple BTSs in the valid domain.
Click Click
Click to clear up the valid domain if you need to clear all the BTSs in the valid domain and reselect them. Click Export to export the information in the valid domain to the Excel table. Set the saving path and file name, and then click OK. The system prompts whether this operation succeeds or not. You can find the Excel table in the path and query relevant information. The table records the software name, NE name, and NE type of each BTS in the valid domain.
Issue 06 (2008-12-16)
l
Click Import if you need to directly import the information from the Excel table to the valid domain. Find the edited Excel table in the corresponding directory, and then click OK. The BTS in the Excel table is displayed in the valid domain.
Step 4 In Selection Operation, select the operation. You can select either of Load or Activate. You also can select both of the operations at a time. Step 5 Click OK. In the Immediately Task tab under Software Browser, you can query the upgrading progress. When Percent displays 100%, you can infer that the upgrade completes. ----End
Querying the BTS NE Information

This describes how to query the BTS information to familiarize yourself with the name and type of the BTS that is connected with the M2000. In addition, you can find the BSC to which the BTS belongs.
Prerequisite
l l l l
Procedure
The Software Browser window is displayed. Step 2 In the navigation tree of the NEtab page, choose BTS node. The information about the names, types, and belonged BSCs of all the BTSs are displayed at the right side of the list. You can click Refresh to manually refresh the information list of BTSs. ----End
Querying the Version of BTS Board

This describes how to query the version of the BTS board to learn the version information about the running BTS boards.
Prerequisite
l l l l
8-64
Procedure
The Software Browser window is displayed. Step 2 You can perform the following operations: Query the Version Information About the Running BTSs Query the version information about the running board of one BTS. Operation
1. In the navigation tree of the NE tab page, choose one BTS. 2. Choose the Query Running Version tab page. Before you enter the tab page, the system automatically queries the version information about the running board of the chosen BTS. The query information is displayed as a list. 3. Click Query. You can manually refresh the displayed version information.
Query the version information about the running board of all BTSs under a BSC.
1. In the navigation tree of the NE tab page, choose a BSC node in the NE > BTS node. 2. Choose Query Running Version tab page. 3. In NE navigation tree, choose one or more BTSs whose version information about the running board is to be queried. 4. In Board Type navigation tree, choose one or more board types. 5. Click Query. The query result is displayed as a list.
----End
8.3.12 Upgrading the ASN-GW Software and Patch

This task describes how to upgrade the ASN-GW software and patches. 8.3.12.1 ASN-GW Software and Patch This describes the software versions for the ASN-GW, naming rules for its patches, and precautions for software loading. 8.3.12.2 Loading the ASN-GW Software This task describes how to load software versions to each board of the ASN-GW. 8.3.12.3 Activating the ASN-GW Software
After software is loaded to the ASN-GW, the software is in the deactivated state. After the activate command is sent, the ASN-GW automatically reboots. After the ASN-GW runs the loaded software, the software is activated. 8.3.12.4 Loading the ASN-GW Software Patch On the M2000, you can use the software management function to load the ASN-GW patches to each board of the ASN-GW. 8.3.12.5 Activating the ASN-GW Software Patch After patches are loaded to the ASN-GW, the patches are in the deactivated state. After the activate command is sent, the ASN-GW automatically reboots. After the ASN-GW runs the loaded patches, the patches are activated. 8.3.12.6 Confirming the ASN-GW Software Patch This task is performed to confirm software patch of the software version designated by the ASNGW NE through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the ASN-GW. 8.3.12.7 Deactivating the ASN-GW Software Patch You can use the software management function to deactivate the ASN-GW patches that are activated but not acknowledged. 8.3.12.8 Deleting the ASN-GW Software Patch On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the ASN-GW.
ASN-GW Software and Patch

This describes the software versions for the ASN-GW, naming rules for its patches, and precautions for software loading.

The software version of the ASN-GW is named in the format of product name + VxxxRxxxCxxBxxy[SPxx]. Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple versions. Each version has a general development plan and can be further categorized into multiple releases. Rxxx (release) indicates a feature version that provides a series of product features. A series of feature products may have its own feature version or may be indicated through special letters or numbers added to a feature version. Cxx indicates a specific sub-version of features delivered to customers. Bxxy (build) indicates the build versions during the developing process. SPxx (Service Pack) indicates the version of a patch.

The patches of the ASN-GW are named in the format of version + board name (short name) + identifier.

If no patch is available for the ASN-GW, you can download the patch through the file server.
Loading the ASN-GW Software

This task describes how to load software versions to each board of the ASN-GW.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the ASN-GW is already set. The ASN-GW communicates properly with the M2000. The software versions of the ASN-GW are downloaded to the ASN-GW successfully.
Procedure
The Software Browser window is displayed. Step 2 Select a ASN-GW under the navigation tree on the NE tab. Step 3 Select a software version on the Version tab page. If no software version under the corresponding NE can be loaded, you can download files to the NE by using the server. Step 4 Click Load.
NOTE
If you load the ASN-GW software versions for the first time, the Upgrade dialog box is displayed. You can browse the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the client to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view Load Software Parameters Selection.
Step 5 Set parameters in Load Software Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Activating the ASN-GW Software

After software is loaded to the ASN-GW, the software is in the deactivated state. After the activate command is sent, the ASN-GW automatically reboots. After the ASN-GW runs the loaded software, the software is activated.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the ASN-GW is already set. The ASN-GW communicates properly with the M2000. The applications of the ASN-GW are downloaded to the ASN-GW successfully.
Context
l
Each NE can active only one software version. After a software version is activated successfully, the original version is automatically set to be deactivate.
Issue 06 (2008-12-16)
l
If the selected software version is already activated, the system prompts that the activate operation fails.
Procedure
The Software Browser window is displayed. Step 2 Select a ASN-GW under the navigation tree on the NE tab. Step 3 Select a software version under Software. Step 4 Click Activate.
NOTE
If you activate the ASN-GW for the first time, the Software dialog box is displayed. You can browse the upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the client to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view Activate Software Parameters Selection.
Step 5 Select parameters in Activate Software Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Loading the ASN-GW Software Patch

On the M2000, you can use the software management function to load the ASN-GW patches to each board of the ASN-GW.
Prerequisite
l l l l
You have logged in to the M2000 client. The relay server of the ASN-GW is set. The ASN-GW communicates properly with the M2000. The software patches of the ASN-GW are downloaded to the ASN-GW.
Procedure
The Software Browser window is displayed. Step 2 Select a ASN-GW from the navigation tree on the NE tab. Step 3 Select a software patch on the Patch tab page. If no software patch under the corresponding NE can be loaded, you can download files to the NE by using the server.
Step 4 Click Load. Step 5 Set the parameters in the Load Patch Parameters Selection dialog box. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Activating the ASN-GW Software Patch

After patches are loaded to the ASN-GW, the patches are in the deactivated state. After the activate command is sent, the ASN-GW automatically reboots. After the ASN-GW runs the loaded patches, the patches are activated.
Prerequisite
l l l l
You have logged in to the M2000 client successfully. The relay server of the ASN-GW is already set. The ASN-GW communicates properly with the M2000. The applications of the ASN-GW are downloaded to the ASN-GW successfully.
Procedure
The Software Browser window is displayed. Step 2 Select a ASN-GW under the navigation tree on the NE tab page. Step 3 Select a software patch under Patch. Step 4 Click Activate. Step 5 Set parameters in Activate Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End
Confirming the ASN-GW Software Patch

This task is performed to confirm software patch of the software version designated by the ASNGW NE through software management. Only after the confirmation, could the software patch automatically take effect upon the restart of the ASN-GW.
Context
Procedure
Step 1 Choose Software > Browser or click the shortcut icon The Software Browser window is displayed. Step 2 On the NE tab, select a ASN-GW from the navigation tree. Step 3 Select a software patch under Patch. Step 4 Click Confirm. Step 5 Set parameters in Confirm Patch Parameters Selection. Step 6 Click OK. Step 7 Click Yes in the Confirm dialog box. You can query the progress of the task in Immediately Task. ----End .
Deactivating the ASN-GW Software Patch

You can use the software management function to deactivate the ASN-GW patches that are activated but not acknowledged.
Context
NOTE
Procedure
Step 1 Choose Software > Browser or .
The Software Browser window is displayed. Step 2 Select a ASN-GW from the navigation tree on the NE tab. Step 3 Select a software patch to be deactivated under Patch. Step 4 Click Deactivate. Step 5 Set parameters in Deactivate Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
Deleting the ASN-GW Software Patch

On the M2000, you can use the software management function to uninstall a software patch of a specified software version of the ASN-GW.
Procedure
The Software Browser window is displayed. Step 2 Select a ASN-GW under the navigation tree on the NE tab. Step 3 Select a software patch version on the Patch tab page. Step 4 Click Unload. Step 5 Set parameters in Unload Patch Parameters Selection. Step 6 Click OK. You can query the progress of the task in Immediately Task. ----End
8.3.13 Monitoring the Procedure of Software Upgrade

Monitor the NE upgrade process, which includes loading, activating, and synchronizing the NE software, and loading, activating, deactivating, confirming, and uninstalling the NE patches.
Prerequisite
l l l
You have logged in to the M2000 client. The file server of the NE is configured. The NE is properly connected to the M2000.
Procedure
Step 1 Choose Software > Browser or the corresponding shortcut icon Management window is displayed. . The Software
The progress percentages of various tasks are listed in a table in the lower part of the Software Browser window. Step 2 Right-click and select Setting to filter the information displayed in the window. To view the details of a particular line, right-click and select Show Detail. ----End
8.4 Managing NE Licenses

This describes how to manage NE licenses by delivering the license files or license control information from the M2000 to NEs. The function of NE license management consists of the upload, download, activation, or assignment of the RAN system license and the license sharing management between the NEs.
Issue 06 (2008-12-16)
8-71
Context
CAUTION
You can perform the operations of Manage NE Licenses only after you purchase the license of the M2000 License Management function. The M2000 manages the NE licenses by using the following methods:
l
Management of the NE local license The license file is delivered to the NEs through the M2000 client. Then, the license file is activated by the M2000 client or the LMT so that the NEs obtain the function of license authorization. The M2000 uses this method to manage the license of the RAN system. For details, refer to 8.4.1 Managing RAN Licenses.
Management of the network license The license control information is directly delivered to the NEs through the M2000 client so that the NEs obtain the function of license authorization. Currently, the M2000 uses this method to manage the licenses of the BSC6000 and the BSC32. For details, refer to 8.4.2 Managing Licenses Between NEs. The license sharing between the NEs is implemented through the management of the network licenses. You can combine multiple NE groups into a license sharing group. When the traffic flow on an NE reaches the upper limit and the required value of the license control items exceeds the applied value, you can deliver the license control information through an M2000 client to the NEs. In this way, the license utilization of the NEs in the entire sharing group is improved and the investment is reduced.
8.4.1 Managing RAN Licenses This task is performed to manage RAN licenses, for example, to query, upload, download, activate, delete, and assign RAN licenses and to query the ESN of an RAN system. 8.4.2 Managing Licenses Between NEs This describes how to implement license sharing between the NEs in the entire group by classifying multiple NEs into one group and directly issuing the license control information from the M2000 client. In this way, the license utilization between the NEs in the entire group is improved and the investment is reduced.
8.4.1 Managing RAN Licenses

This task is performed to manage RAN licenses, for example, to query, upload, download, activate, delete, and assign RAN licenses and to query the ESN of an RAN system.
Context
NOTE
You can manage the RAN licenses only after purchasing the license of the license management function.
8.4.1.1 Uploading a RAN License to a Server This describes how to upload the RAN license file to the M2000 server through the M2000 client. This enables the SWMService of RAN license management to manage the license file. 8.4.1.2 Downloading an RNC License from a Server
This task is performed on the M2000 client to download the RNC license that is already uploaded to the M2000 server to an RNC. 8.4.1.3 Activating a RAN License This task is performed to activate RAN licenses. RAN licenses can be used only after being activated. RAN licenses are categorized into RNC licenses and licenses assigned on the NodeBs. The modes for activating two types of licenses are different. 8.4.1.4 Deleting a RAN License This describes how to delete the inactivated licenses of the RAN. 8.4.1.5 Querying the License Information about the RAN This describes how to view all the license information on the RAN system through the M2000 client. The RAN license consists of the license of one RNC and the licenses distributed on NodeBs. 8.4.1.6 Querying the ESN of the RAN System The mobile country code (MCC), mobile network code (MNC), and RNC ID are sequenced and encrypted to form the ESN of an RAN system. The mobile network code is associated with an operator. When an RAN system is shared by multiple operators, the RAN system may have multiple ESNs. This describes how to query the ESN of an RAN system. 8.4.1.7 Distributing RAN Licenses This describes how to assign the RAN licenses uploaded to the M2000 server to each operator and set usable licenses for each operator.
Related Concepts
8.1.5 RAN License
Related References
8.6.2 Interface Description: NE Licenses Management
Uploading a RAN License to a Server

This describes how to upload the RAN license file to the M2000 server through the M2000 client. This enables the SWMService of RAN license management to manage the license file.
Prerequisite
l l l l
You have logged in to the M2000 client. The M2000 service is running properly. The valid license file is available. You have successfully obtained the ESN from the RAN.
Context
l
Each RAN system can upload one RNC license and multiple NodeB license resources. At a time point, the license distributed to only one NodeB can be activated. If the RAN system is shared, the RNC can have multiple ESNs because the operator information is varies. If a license ID matches any ESN of an RNC when you match the license ID with ESNs of the RNC, you can infer that the license matches the RNC.
Issue 06 (2008-12-16)
Procedure
Based on the user requirements, determine the process of uploading the licenses.
To upload the RNC licenses, perform the following steps: 1. 2. 3. 4. 5. 6. 7. Choose Software > Browser. The Software Browser window is displayed. Click the Server tab. Under the Server node, select the RNC node. In the right part of the window, click the License tab. Click From Client to Server. In the displayed Select NE-----1/2 dialog box, select an RNC. Click Next. In the Select Uploading File-----2/2 dialog box, click Add and select the license file to be uploaded. Click Select to add the license file to the Select Uploading File-----2/2 dialog box. Click Finished. The progress of uploading the license file is displayed in the FTP Task tab page at the lower part of the Software Browser window. Choose Software > License Management to display the License Browser window. In the left part, select an RNC node from the structure tree in the License Browser window. Right-click the node and choose Upload > From Client. The Select Uploading File-----1/1dialog box is displayed. Click Add. The Select dialog box is displayed. Select one or multiple license resources to be uploaded, and then click Select.
TIP
To upload licenses distributed to the NodeBs, perform the following steps: 1. 2. 3. 4. 5.
Hold Shift or Ctrl and select multiple license resources at the same time.
6.
In the Select Uploading File-----1/1 dialog box, click Finish. The upload progress is displayed in the FTP Task tab page at the lower part of the License Browser window. When the progress bar reaches 100%, you can infer that the license file is uploaded completely.
NOTE
If you need to stop or delete this task when uploading the licenses, select this FTP task, rightclick it, and then choose Stop or Delete from the shortcut menu.
----End
Downloading an RNC License from a Server

This task is performed on the M2000 client to download the RNC license that is already uploaded to the M2000 server to an RNC.
Prerequisite
l l l l
You have logged in to the M2000 client. The M2000 service is running properly. You have successfully obtained the ESN from the RAN. The RNC license is already uploaded to the M2000 server.
8-74
Procedure
Step 1 Choose Software > Browser. The Software Browser window is displayed. Step 2 Click the NE tab. Choose NE > RNC and select an RNC node. Step 3 In the right part of the window, click the License tab, and then click Download From Server. The progress of downloading the license file is displayed in the Immediately Task tab page at the lower part of the Software Browser window. When Percent shows 100%, you can infer that the task is successfully downloaded. ----End
Activating a RAN License

This task is performed to activate RAN licenses. RAN licenses can be used only after being activated. RAN licenses are categorized into RNC licenses and licenses assigned on the NodeBs. The modes for activating two types of licenses are different.
Prerequisite
l l l l
You have logged in to the M2000 client. The M2000 service is running properly. You have successfully obtained the ESN from the RAN. RAN licenses are assigned to the operators.
Context
An RAN system can have multiple license files. At a particular point in time, only one license file can be in the active state. The M2000 distributes the values of the license.
Procedure
Based on user requirements, determine the process to activate a license.
l
To activate an RNC license, perform the following steps: 1. 2. 3. 4. 5. Choose Software > Browser. The Software Browser window is displayed. Click the NE tab. Choose NE > RNC and select an RNC node. In the right part of the window, click the License tab. The license information on the RNC node is displayed in the list. Select a license and click Activate. The Activate License window is displayed. Select an operator and set the related parameters, and then click OK. Choose Software > License Management to display the License Browser. From the file navigation tree on the left part of the License Browser window, select an RNC node. The detailed license list on the right part of the window displays all the licenses of the RNC node. Select a license whose Activated is set to False, and then right-click the license and choose Distribute All from the shortcut menu.
To activate a NodeB license, perform the following steps: 1. 2.
3.
Issue 06 (2008-12-16)
NOTE
If the set parameter value exceeds its thresholds when you distribute the licenses to the operators, the Message dialog box is displayed, informing you that a parameter value has exceeded its thresholds. Click OK and tune the parameter value. If a parameter value set for a NodeB owned by an operator exceeds the recommended value range, the Confirmation dialog box is displayed. Click Yes to continue the license delivery or click No to cancel the license delivery.
----End
Deleting a RAN License

This describes how to delete the inactivated licenses of the RAN.
Prerequisite
l l l l
You have logged in to the M2000 client. The M2000 service is running properly. The RAN license is uploaded to the M2000 server. You have successfully obtained the ESN from the RAN.
Procedure
Based on user requirements, determine the process to delete a license.
l
To delete RNC licenses, perform the following steps: 1. 2. 3. 4. Choose Software > Browser. The Software Browser window is displayed. Click the Server tab. Choose Server > RNC and select an RNC node. In the right part of the window, click the License tab. The license information on the NE is displayed in the list. Click Delete. In the displayed Confirm dialog box, click Yes.
To delete NodeB licenses, perform the following steps: 1. 2. Choose Software > License Management to display the License Browser. In the left part, select an RNC node from the structure tree in the License Browser window. The detailed license list on the right part of the window displays the licenses of all the NodeBs on the RNC node. 3. Select a license whose Activated is set to False, and then right-click the license and choose Delete from the shortcut menu.
NOTE
If you attempt to delete an active license, you must activate another license first. In this case, a license in the activated state automatically changes to the deactivated state. For details, see 8.4.1.3 Activating a RAN License.
----End
8-76
Issue 06 (2008-12-16)
Querying the License Information about the RAN

This describes how to view all the license information on the RAN system through the M2000 client. The RAN license consists of the license of one RNC and the licenses distributed on NodeBs.
Prerequisite
l l l l
You have logged in to the M2000 client. The M2000 service is running properly. You have successfully obtained the ESN from the RAN. You have successfully uploaded the RAN licenses from the M2000 client to the M2000 server. In addition, you have distributed licenses to the NodeBs.
Context
l
The value sum of a certain parameter of all NodeBs under one RNC must be less than the value defined for this parameter in the license control information. For example, if the license control information defines LQW9ULCE01 = 128, it shows that the value sum of UL CE of all NodeBs under this RNC should be less than 128. You can manually modify the license information distributed to the NodeB.
Procedure
Based on user requirements, determine the process to query the licenses.
l
To query the RNC licenses, perform the following steps: 1. 2. 3. Choose Software > Browser. The Software Browser window is displayed. Click the NE tab. Choose NE > RNC and select an RNC node. In the right part of the window, click the License tab. The license information on the RNC node is displayed in the list.
NOTE
Click Show License Detail to view the detailed license information.

l
To query licenses distributed on NodeBs, perform the following steps: 1. 2. Choose Software > License Management. The License Browser window is displayed. From the navigation tree on the left part of the window, select an RNC node. The two tables in the upper right part of the window show the operators and licenses related to the RAN.
The operator information consists of Operator, ESN, and Primary Operator

NOTE
In case that the RAN is shared, the information about the operator contains Operator, ESN, and Primary Operator. In case that the RAN is not shared, the information about the operator contains only ESN.
The license information consists of LicenseSN, Activated, CreateDate, EndDate,and Control. For descriptions of the parameters, refer to 8.6.7 Parameters for License Information of NodeBs Controlled by an RNC.
3.
After selecting a license, you can view the details about how this license is assigned to each NodeB in the detail table.
Issue 06 (2008-12-16)
For detailed parameter description, refer to Parameter for Listing of Licenses Assigned to Each NE.
NOTE
In the license list, double-click a license. The Detail dialog box is displayed, informing you about the detailed license information.
----End
Related Concepts
8.1.5 RAN License
Related References
8.6.7 Parameters for License Information of NodeBs Controlled by an RNC
Querying the ESN of the RAN System

The mobile country code (MCC), mobile network code (MNC), and RNC ID are sequenced and encrypted to form the ESN of an RAN system. The mobile network code is associated with an operator. When an RAN system is shared by multiple operators, the RAN system may have multiple ESNs. This describes how to query the ESN of an RAN system.
Prerequisite
l l l
You have logged in to the M2000 client. The M2000 service is running properly. You have successfully obtained the ESN from the RAN.
Procedure
Step 1 Choose Software > License Management. The License Browser window is displayed. Step 2 In the left part, select an RNC node from the structure tree in the License Browser window. The ESN column of the operator information list on the right part of the window shows the ESNs associated with all the operators. ----End
Distributing RAN Licenses

This describes how to assign the RAN licenses uploaded to the M2000 server to each operator and set usable licenses for each operator.
Prerequisite
l l l l l
You have logged in to the M2000 client. The M2000 service is running properly. You have successfully obtained the ESN from the RAN. The valid license file is already uploaded to the M2000 server. The RAN system is shared by multiple operators.
8-78
Procedure
Step 1 Choose Software > License Management to display the License Browser. Step 2 From the file navigation tree on the left part of the License Browser window, select an RNC node whose license file is already uploaded to the M2000 server. The detailed license list on the right part of the window displays all the licenses of the RNC node. Step 3 Select a license, right-click it, and choose License Distributed to Operator from the shortcut menu. The License Distributed to Operator window is displayed. Step 4 In this window, assign the number of licenses to each operator. For detailed parameter description, refer to 8.6.9 Parameters for the Operator.
NOTE
The number of local cells set by the user must be equal to or more than the number of actual cells. If the number of preset local cells is less than the number of actual cells, the distribution of NodeB license is doomed to fail. By using the MML command, you can query the parameter information of the NodeB. For example, you can use the MML command to query the number of cells under a NodeB. After modifying the distributed License information of a NodeB, you must redistribute the license information to all the NEs under this RNC for the modification to take effect.
l l
Step 5 In the NE distribution information list box, select an operator tab. All the licenses distributed to the operator are displayed in the list box. Step 6 Double-click a piece of NE license distribution record or right-click the information and choose Modify from the shortcut menu. The Modify dialog box is displayed. Step 7 Redistribute the licenses of the NodeB for each operator and deliver the licenses from each operator to the NEs. ----End
8.4.2 Managing Licenses Between NEs

This describes how to implement license sharing between the NEs in the entire group by classifying multiple NEs into one group and directly issuing the license control information from the M2000 client. In this way, the license utilization between the NEs in the entire group is improved and the investment is reduced.
Issue 06 (2008-12-16)
8-79
Context
CAUTION
l
The function of license sharing management between NEs is available only after you purchase the license of the <M2000keyword> NEs License Sharing Management function. You can perform the license sharing management operations between the NEs only after you are authorized to handle licenses. The operation rights of the license belong to the application rights of the M2000. For details about the setting of operation rights, see 4.5.10 Assigning Operation Rights to an OM User. The BSC6000 and the BSC32 that are managed by the M2000 support the function. The versions of NEs that support the support are later versions of BSC6000V900R008C01B040, G3BSC32V300R008C01B015, and later versions of G3BSC32V300R008C01B015. The M2000 currently supports only the license sharing between the NEs of the same type.
Table 8-4 describes the concepts related to the function of license sharing between the NEs. Table 8-4 Concepts related to license sharing Concept License sharing group Description Multiple NEs are classified into one group and the license resources of all the NEs in this group can be shared. For example, there are two base station controllers, that is, BSC1 and BSC2. Each of them has 200 license resources. After you combine them into a license sharing group, you can adjust the license resources between them. For example, you can assign 300 to BSC1 and 100 to BSC2 as long as the total amount does not exceed 200 + 200. Network license A network license refers to the license control information delivered by the M2000. The control items in the network license are based on the sharing-enabled control items in the NE local license file in the license sharing group. After network licenses are delivered to NEs, the delivered values of Allocated and Activated are recorded on the M2000 and on the NE side respectively. If the network licenses are not successfully delivered to the NEs because of NE disconnection, the Allocated value and the Activated value are different.
8-80
Issue 06 (2008-12-16)
Concept NE management status
Description The management status of an NE license can be local management or centralized management.
l
Local management: For the NEs in local management status, the license resources use the values of the control items in the local license file. Centralized management: For the NEs in centralized management status, the license resources use the values of the control items in the network license.
In a license sharing group, an NE is in local management status if the network license is not issued to this NE. After the M2000 successfully issues the network license to the NE, it changes to centralized management status. License list Local value Available A license list lists the shared license control items supported by a certain NE type. One NE type corresponds to a license list. Local values refer to the values of the control items in the local license file on the NEs. Available value refers to the sum of certain control items in the local license files of all the NEs in a sharing group. It refers to the available maximum value of a certain license control item in the sharing group. The allocated values are the network values that have been distributed to the NEs and recorded by the M2000. The activated values are the network values that have been successfully issued to the NEs and recorded by the NE side.
Allocated Activated
8.4.2.1 Uploading a License List to a Server This describes how to upload a license list to a server. A license list displays the sharing-enabled control items supported by the NE local license file. After a license list is uploaded from a local client to the M2000 server, you can deliver the network license to the NEs through the M2000 client to share the NE license. 8.4.2.2 Viewing a License List This describe how to view a license list. By viewing a license list, you can learn which license control items of an NE type support the sharing function. One NE type corresponds to a license list. 8.4.2.3 Downloading a License List from a Server This describes how to download a license list from the M2000 server to a local computer for future use. 8.4.2.4 Adding a License Sharing Group After you combine multiple NEs into a license sharing group, you can adjust license resources between NEs to maximize the usage of licenses for the NEs in the group, thus reducing your investment. 8.4.2.5 Modifying a License Sharing Group This describes how to modify a license sharing group to add or delete the NEs in a created license sharing group. After you modify a license sharing group, the system automatically refreshes the
license information about the sharing group. The license information includes the Available, Assigned, and Activated values. 8.4.2.6 Deleting a License Sharing Group This describes how to delete a license sharing group. You can delete the license sharing groups that are not required, so as to save system resources. After a license sharing group is successfully deleted, the status of the NEs in the sharing group changes from centralized management to local management. 8.4.2.7 Viewing the Sharing Group License Information This describes how to view the license information in the sharing group. By viewing the license information in the sharing group, you can learn the information on the available license resources of the sharing group and each NE in the group, and also the information on the allocated and activated network licenses. 8.4.2.8 Checking the NE License Information When you adjust license resources between NEs in the license sharing group, the network licenses on NEs may differ from the network licenses that are actually allocated to the M2000 server because of NE disconnection. By using the function of checking NE license information, you can check whether the network licenses on NEs are consistent with the network licenses on the M2000. 8.4.2.9 Adjusting an NE License in a Sharing Group When the traffic flow on an NE in a license sharing group reaches the upper limitation and the required value of a license control item exceeds the applied value, you can regulate the license resources between NEs without applying for NE licenses. In this way, you can improve the usage of NE licenses in the entire sharing group and reduce the invested money.
Related References
Uploading a License List to a Server

This describes how to upload a license list to a server. A license list displays the sharing-enabled control items supported by the NE local license file. After a license list is uploaded from a local client to the M2000 server, you can deliver the network license to the NEs through the M2000 client to share the NE license.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to handle licenses. License operation rights belong to the application rights of the M2000. For details about the setting of user operation rights, see 4.5.10 Assigning Operation Rights to an OM User.
Context
The BSC6000 and the BSC32 managed by the M2000 support the license sharing function. One NE type corresponds to a license list.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Right-click the NE License Sharing Management node and choose Upload License List from the shortcut menu. Step 3 Click to select the license list to be uploaded, and select the NE type corresponding to the license list from the Select NE Type drop-down list. Step 4 Click OK to upload the license list. If the license list of this NE already exists on the M2000 server, the system automatically replaces it with the uploaded list.
NOTE
You can check the uploaded license list. For details, refer to 8.4.2.2 Viewing a License List.
----End
Postrequisite
After the license list is uploaded to the M2000 server, you can create a license sharing group to adjust the license resources between the NEs. For details, refer to 8.4.2.4 Adding a License Sharing Group and 8.4.2.9 Adjusting an NE License in a Sharing Group.
Viewing a License List

This describe how to view a license list. By viewing a license list, you can learn which license control items of an NE type support the sharing function. One NE type corresponds to a license list.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to query or handle licenses. The query or operation rights of the license belong to the application rights of the M2000. For details about the setting of operation rights, see 4.5.10 Assigning Operation Rights to an OM User.
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 Right-click the NE License Sharing Management node and choose View NE License List from the shortcut menu. Step 3 Select the NE type to be viewed from the NE Type drop-down list. The Resource List displays the detailed information about the shared control items supported by the NE local license file. The information consists of the resource name, resource label, and the maximum and minimum values of the resource. Step 4 Click Close to close the View NE License List window. ----End
Downloading a License List from a Server

This describes how to download a license list from the M2000 server to a local computer for future use.
Prerequisite
l l
Context
The BSC6000 and the BSC32 managed by the M2000 support the license sharing function. One NE type corresponds to a license list.
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 Right-click the NE License Sharing Management node and choose Download License List from the shortcut menu. Step 3 Click to select a save path for the license list. Select the NE type corresponding to the license list from the Select NE Type drop-down list. Step 4 Click OK to download the license list. You can check the downloaded license list on the M2000 client. For details, refer to 8.4.2.2 Viewing a License List. ----End
Adding a License Sharing Group

After you combine multiple NEs into a license sharing group, you can adjust license resources between NEs to maximize the usage of licenses for the NEs in the group, thus reducing your investment.
Prerequisite
l l
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 From the navigation tree, select the NEs License Sharing Management node. Right-click the node, and then choose Add Sharing Group from the shortcut menu. Step 3 In the Add Sharing Group dialog box, set the name and NEs of a sharing group. For the detailed description of parameters, see 8.6.10 Parameters for Adding/Modifying License Sharing Groups.

NOTE
When you set an NE in a sharing group, the NE is not displayed in the Local Controled Nes group box if you are not authorized to operate the NE. For details on how to add an NE to the management domain of a user, see 4.5.11 Setting the Managed Domain for an OM User.
Step 4 Click OK. A new license sharing group is created. The new license sharing group is displayed as a node in the navigation tree.
NOTE
Originally, the NEs in a sharing group are in the local management status. After you deliver the related network licenses to the NEs, their management status changes to the centralized management status. For more information about the status of local management and centralized management, see 8.4.2 Managing Licenses Between NEs.
----End
Postrequisite
Based on the traffic status of the NEs in a sharing group, you can adjust licenses among NEs to maximize the usage of NE licenses, thus protecting your investment. For details, see 8.4.2.9 Adjusting an NE License in a Sharing Group.
Related References
8.6.10 Parameters for Adding/Modifying License Sharing Groups
Modifying a License Sharing Group

This describes how to modify a license sharing group to add or delete the NEs in a created license sharing group. After you modify a license sharing group, the system automatically refreshes the license information about the sharing group. The license information includes the Available, Assigned, and Activated values.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to handle licenses. License operation rights belong to the application rights of the M2000. For details about the setting of user operation rights, see 4.5.10 Assigning Operation Rights to an OM User. Related NEs are properly connected to the M2000.
Context
For details about the Available, Assigned, and Activated values, refer to 8.4.2 Managing Licenses Between NEs.
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 Right-click a license sharing group to be modified in the navigation tree and choose Modify NE (s) Sharing Mode from the shortcut menu. Step 3 Click
Issue 06 (2008-12-16)
or
to add or remove the NEs in the sharing group.

8-85
For the detailed description of parameters, see 8.6.10 Parameters for Adding/Modifying License Sharing Groups. Step 4 Click OK to close the modification dialog box. ----End
Postrequisite
When NEs are removed from the sharing group, the M2000 automatically delivers the command to switch the status of the NEs to local management. If the NE status is not successfully switched, the status of NEs automatically switches to local management after 15 days. You can check whether the corresponding sharing group is successfully modied through the license task list. For details, see 8.2.7 Managing Task List.
Related References
Deleting a License Sharing Group

This describes how to delete a license sharing group. You can delete the license sharing groups that are not required, so as to save system resources. After a license sharing group is successfully deleted, the status of the NEs in the sharing group changes from centralized management to local management.
Prerequisite
l l
Context
NOTE
When you delete a license sharing group, you need to remove all the NEs from the sharing group, and then delete this empty sharing group.
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 Remove the NEs in the license sharing group. 1. 2. 3. Right-click a sharing group node in the navigation tree and choose Modify NE(s) Sharing Mode from the shortcut menu. Select the to-be-removed NEs from Group NEs. Then, click to remove them from the sharing group. Click OK. Step 3 Right-click the sharing group node in the navigation tree and choose Delete Sharing Group from the shortcut menu. ----End
or
Viewing the Sharing Group License Information

This describes how to view the license information in the sharing group. By viewing the license information in the sharing group, you can learn the information on the available license resources of the sharing group and each NE in the group, and also the information on the allocated and activated network licenses.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to query or handle licenses. The query or operation rights of the license belong to the application rights of the M2000. For details about the setting of operation rights, see 4.5.10 Assigning Operation Rights to an OM User.
Procedure
Step 1 Choose Software > License Management to view the License Browser window. Step 2 Click a sharing group or an NE node in the navigation tree and view the corresponding license information on the right part of the window.
l
If you click a sharing group node, the right window displays the network license resources available to the sharing group (Available), the network licenses that are recorded on the M2000 server and allocated to the NEs (Assigned), and the network licenses that are recorded on the NE side and successfully delivered to the NEs ( Activated). If you click an NE node, the right window displays the values of the sharing control items in the NE local license file (Local Value), the network licenses that are recorded on the M2000 server and allocated to the NEs (Assigned), and the network licenses that are recorded on the NE side and successfully delivered to the NEs ( Activated).
NOTE
After you click a sharing group node in the navigation tree and deliver the network licenses to the NEs in the right window, the M2000 and the NE side record the delivered values, that is, the Assigned value and the Activated value. If the network licenses are not successfully delivered to the NEs because of NE disconnection, the Assigned value and the Activated value are different.
----End
Checking the NE License Information

When you adjust license resources between NEs in the license sharing group, the network licenses on NEs may differ from the network licenses that are actually allocated to the M2000 server because of NE disconnection. By using the function of checking NE license information, you can check whether the network licenses on NEs are consistent with the network licenses on the M2000.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to handle licenses. License operation rights belong to the application rights of the M2000. For details about the setting of user operation rights, see 4.5.10 Assigning Operation Rights to an OM User. Relevant NEs are properly connected to the M2000.
Issue 06 (2008-12-16)
Context
NOTE
The M2000 provides the automatic check function. In general, the system automatically checks the consistency of NE licenses at a specific time every day. For details, refer to 14.9 Modifying NE License Sharing Management. This part describes only the procedure of manual check.
Figure 8-8 shows the system processing flow during the automatic or manual check. Figure 8-8 Process for checking NE licenses
Table 8-5 describes the Figure 8-8 process. Table 8-5 Process for checking NE licenses procedure Update the information about NE licenses Description The M2000 searches for the local NE licenses and the network licenses, and updates the NE license resources and the available resources of the license sharing group in the M2000 database.
8-88
Issue 06 (2008-12-16)
procedure Checking the license resources of the sharing group and NEs
Description
l
The system checks whether the network licenses allocated to NEs by the license sharing group outnumbers the actual available resource value. If the allocated network value outnumbers the available license resources, the system sends an alarm to the M2000 server, indicating that the number of used licenses exceeds the limit. Based on the alarm information, you can handle the problem. For details, see ALM-515 The amount of used license's resource exceeds the threshold. If the local license files on NEs are updated or out of date, the network license that are assigned to NEs by the license sharing group may exceed the actual available resource value. The system checks whether the network license on NEs is consistent with the network license on the server. If they are inconsistent, the system sends an alarm to the M2000 server, indicating that the number of NE licenses changes. Based on the alarm information, you can handle the problem. For details, see ALM-514 Changes in the usage of NE license resources. When you adjust license resources between NEs in the license sharing group, the network licenses on NEs may differ from the network licenses that are actually allocated to the M2000 server because of NE disconnection.
NOTE When performing an automatic check, the system checks whether an NE in the license sharing group is disconnected from the M2000 for over 15 days. If an NE is disconnected for over 15 days, the system automatically removes the NE from the group.
Procedure
Step 1 Choose Software > License Management to view the License Browser window. Step 2 Check the information about NE licenses.
l
From the navigation tree, select the node of the sharing group. Right-click the node, and then choose Synchronize NE(s) License from the shortcut menu. Then, check for the license information about all the NEs in the sharing group. From the navigation tree, select the node of an NE. Right-click the node, and then choose Synchronize NE from the shortcut menu. Then, check for the license information about the NE.
----End
Adjusting an NE License in a Sharing Group

When the traffic flow on an NE in a license sharing group reaches the upper limitation and the required value of a license control item exceeds the applied value, you can regulate the license
resources between NEs without applying for NE licenses. In this way, you can improve the usage of NE licenses in the entire sharing group and reduce the invested money.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to handle licenses. License operation rights belong to the application rights of the M2000. For details about the setting of user operation rights, see 4.5.10 Assigning Operation Rights to an OM User. Related NEs are properly connected to the M2000.
Procedure
Step 1 Choose Software > License Management to open the License Browser window. Step 2 Click in the navigation tree the sharing group node that an NE belongs to. Then, set the corresponding network license of the NE in the right part of the window. The values of control items in the network license must be within the specified NE value range of license control items. If the entered values are not within the specified value range, you cannot enter the values on a client. You can know the value range of license control items by checking the license list. For details, see 8.4.2.2 Viewing a License List. Step 3 Right-click in the navigation tree the sharing group node that an NE belongs to, and then choose Distribute from the shortcut menu.
l
The M2000 delivers network licenses to the corresponding NEs in the sharing group. The previously mentioned NEs consist of the NEs whose network licenses are not consistent with those on the M2000 and the NEs whose network licenses need to be reset. You can check whether the network license is successfully delived to an NE by checking the license task list. For details, see 8.2.7 Managing Task List. For the detailed description of the License Browser window, see 8.6.2 Interface Description: NE Licenses Management.
CAUTION
l
When the M2000 delivers a network license to an NE, the system checks whether the allocated network license exceeds the available resource value of the entire sharing group. If the allocated network license exceeds the available resource value, the system displays a message, indicating that the resource value has exceeds the upper limit. In this case, you need to reset the network license. When the M2000 delivers a network license to an NE, the delivery fails if the upper limit of a control item in the delivered network license is less than the resource value that is already used by the NE or is more than the resource value that is supported by the NE. You can identify the problem by checking the detailed task information in the license task list.
----End
Result
After the network license is successfully delivered to the NE through an M2000 client, the NE is in the centralized management status. In this situation, the local license file of the NE is invalid.
Postrequisite
After network licenses are delivered to NEs, the delivered values of Allocated and Activated are recorded on the M2000 and on the NE side respectively. If the network licenses are not successfully delivered to the NEs because of NE disconnection, the Assigned value and the Activated value are different. In general, the system checks the consistency between NE licenses at a specific time every day. For details, see 14.9 Modifying NE License Sharing Management. You can manually check whether the Allocated value is consistent with the Activated value. For details, see 8.4.2.8 Checking the NE License Information.
8.5 Querying Version Information on Software Installed on the Server

This describes how to query the version information about the OMC, adaptation layer, ENM, and northbound Corba interface installed on the server through the M2000 client.
Prerequisite
The M2000 server normally operates.
Context
On the M2000 client, you can query the version information about the software installed on the server. The version information includes the following items:
l
The OMC version information, which includes the version numbers of the software and patch installed on the OMC server. The version information about the adaptation layer, which refers to the version number of the adaptation layer connected to the NEs. The ENM version information, which refers to the version number of the components used for the NE maintenance. The version information of the northbound Corba interface, which refers to the version number of the Corba interface used for the communication between the M2000 and the network management system.
Procedure
. Step 1 Choose Software > Browser or click The Software Browser window is displayed. Step 2 Select the Server tab. Run the operations according to your requirements.
Issue 06 (2008-12-16)
8-91
Version information OMC version information
Then... In the structure tree of the file, select the Server > OMC node. The primary version and the patch version of the OMC are displayed in the list box at the right of the Software Browser window. See 8.6.11 Parameters for Version Information on Software Installed for details.
NOTE For a patch version, you can write remarks in the Remarks column and save it on the server. The edited remarks can be saved on the server. You can only view the remarks about the primary version.
Editing the remarks is not allowed.
Version information about the adaptation layer In the structure tree of the file, select the NE node under the Server > OMC > Mediation to check the version information about the adaptation layer. The version information about the adaptation layer of each node is displayed in the list at the right of the Software Browser window. See 8.6.11 Parameters for Version Information on Software Installed for details.
OMC version information
In the structure tree of the file, select the Server > OMC > ENM node. All the version information about the ENM installed on the server is displayed in the list at the right of the Software Browser window. See 8.6.11 Parameters for Version Information on Software Installed for details.
Version information about the northbound In the structure tree of the file, select the Corba interface Server > OMC > CorbaNBI. northbound Corba interfaces installed on the server is displayed in the list at the right of the Software Browser window. See 8.6.11 Parameters for Version Information on Software Installed for details. ----End
Related References
8.6.11 Parameters for Version Information on Software Installed
8.6 Reference for Software Management Interfaces

This part describes the software management interface and the related parameters. 8.6.1 Interface Description: Software Browser This describes the software browser interface, which helps you to understand the related functions. 8.6.2 Interface Description: NE Licenses Management This describes the main interface of NE license management. In details, this describes the interface layout of the License Browser window and the elements in the window. 8.6.3 Parameters for RNC Patch This part describes the parameters used for RNCs and the patches required. 8.6.4 Parameters for Other NE Software and Patch This describes the parameters that are used to upgrade NE software and patches. 8.6.5 Parameters for NE Data This part describes the data of all the related NEs. 8.6.6 Parameters for Upgrading the NodeB Software This part describes the parameters used for upgrading the NodeB software. 8.6.7 Parameters for License Information of NodeBs Controlled by an RNC This describes the parameters related to querying the license information of NodeBs concerned. 8.6.8 Parameters for Setting Parameters of Files Transferring This part describes parameters used for setting file transfer. 8.6.9 Parameters for the Operator This describes the parameters in the Assign License to Operator window and Modify window. You can refer to these parameters when you perform the related operations. 8.6.10 Parameters for Adding/Modifying License Sharing Groups This describes the parameters for adding or modifying license sharing groups. 8.6.11 Parameters for Version Information on Software Installed This describes the version information about the OMC, adaptation layer, ENM, and northbound Corba interfaces installed on the server.
8.6.1 Interface Description: Software Browser

This describes the software browser interface, which helps you to understand the related functions. Figure 8-9 shows the software browser under the Server tab.
Issue 06 (2008-12-16)
8-93
Figure 8-9 Software Browser interface under the Server tab
Table 8-6 describes each part on the interface. Table 8-6 Interface description No. (1) (2) (3) Name Navigation tree Tab Content window Description Lists NE types. Comprise immediate tasks, scheduled tasks, and file transfer tasks. Lists software version, patches, license, and data of NEs saved on the server. The M2000 supports different file types for different NEs. For details, refer to 8.1.4 Software Management File Types. Lists software, patches, and data of NEs saved on the server. Lists details of operation tasks. Arranges provided operation buttons.
(4) (5)
Content window Operation bar
Table 8-7 lists types of NE files stored on the server. Table 8-7 File type Item Version Patch
8-94
Description Software versions of NEs. Patch versions of NEs.

Item License Data Voice Others
Description License files of NEs. Configuration files of NEs. Voice files of NEs. Other files, such as logs.
Figure 8-10 shows the software browser under the NE tab. Figure 8-10 Software browser interface under the NE tab
The software browser under the NEtab is the same as that under the Server tab. For details, refer to the descriptions of the software browser under the Server tab.

This describes the main interface of NE license management. In details, this describes the interface layout of the License Browser window and the elements in the window.
Interface of NE License Sharing Management

The interface of NE license sharing management has four child windows, as shown in Figure 8-11. For the detailed description of each child window, refer to Table 8-8.
Issue 06 (2008-12-16)
8-95
Figure 8-11 Interface of NE license sharing management
Table 8-8 Interface description of NE license sharing management Number of a Child Window 1 Name Description
Child window of the navigation tree
The license sharing group and its NEs are displayed in the navigation tree. You can right-click the child window of the navigation tree and choose correponding menu items from the shortcut menu to perform related operations on the sharing group and the license list.
8-96
Issue 06 (2008-12-16)
Number of a Child Window 2
Name
Description
Child window of attributes
After you select the NEs License Sharing Management node in the child window of the navigation tree, all the NEs that support the license sharing function, management status of the NEs, and belonged sharing groups are displayed in the child window of attributes. When a sharing group node is selected in the navigation tree, the available license resources and resource allocation of the sharing group are displayed in the child window of attributes. Where,
l
Available: Its value equals the sum of the values of a specified control item in all the NE local license files. It indicates the maximum value of a specified control item in the sharing group. Allocated: indicates the network licenses that are recorded on the M2000 server and allocated to NEs. Activated: indicates the network licenses that are recored on the NE side and successfully delivered to NEs.
NOTE In the child window of network license allocation, after network licenses are delivered to NEs, the delivered values are recorded on the M2000 and on the NE side respectively. If the network licenses are not successfully delivered to the NEs because of NE disconnection, the Allocated value and the Activated value are different.
Child window of network license allocation
In the child window of network license allocation, you can regulate the license resources between NEs. When you select a sharing group node in the child window of the navigation tree, the chid window is displayed in the right window.
Issue 06 (2008-12-16)
8-97
Number of a Child Window 4
Name
Description
Chid window of the task list
All the executed tasks are displayed in the chid window of the task list after you open the License Browser window.
l
The tasks related to licenses, are displayed in the license task list. The tasks include the synchronization of network licenses and the setting of NE sharing modes. The file transfer tasks between the M2000 client and the server are displayed in the file transfer list.
You can right-click in the child window of the task list and choose corresponding menu items from the shortcut menu to perform related operations on the executed tasks.
Interface of License Management in the RAN System

The interface of NE license management in the RAN system has three child windows, as shown in Figure 8-12. For the detailed description of each child window, refer to Table 8-9. Figure 8-12 Interface of license management in the RAN system
8-98
Issue 06 (2008-12-16)
Table 8-9 Interface description of license management in the RAN system Number of a Child Window 1 Name Description
Child window of the navigation tree
The RAN NEs are displayed in the navigation tree. You can right-click the child window of the navigation tree and choose correponding menu items from the shortcut menu to perform related operations on the licenses in the RAN system. After you select an RNC node in the chid window of the navigation tree, the operator information and license information in the RAN system are displayed in the child window of attributes. After you select a license, the license allocation information on all the NodeBs in the RAN system is displayed in the table. All the executed tasks are displayed in the chid window of the task list after you open the License Browser window.
l
Child window of attributes
Chid window of the task list
The operation tasks related to licenses, are displayed in the license task list. The tasks include the synchronization of network licenses and the setting of NE sharing modes. The file transfer tasks between the M2000 client and the server are displayed in the file transfer list.
You can right-click in the child window of the task list and choose corresponding menu items from the shortcut menu to perform related operations on the executed tasks.
Related Tasks
8.4.1 Managing RAN Licenses 8.4.2 Managing Licenses Between NEs
8.6.3 Parameters for RNC Patch

This part describes the parameters used for RNCs and the patches required. Table 8-10 lists the parameters of RNC patch. Table 8-10 Parameters of RNC patch NE Type RNC Parameter Cabinet No. Value Range Numeric Description Number of RNC cabinet
8-99
Issue 06 (2008-12-16)
NE Type
Parameter Subrack No. Slot No. CPU No. PatchType
Value Range Numeric Numeric Numeric WMUX, WSPU/ WSPUB, WFMR, WXIE, WOSE/ WOME, WBIE/ WTIE Numeric
Description Number of RNC subrack Number of RNC slot Number of RNC CPU Type of RNC patch
PatchId
ID of RNC patch
Related Tasks
8.3.2.6 Confirming the RNC Software Patch

This describes the parameters that are used to upgrade NE software and patches. Table 8-11 lists the parameters that are used to upgrade NE software and patches. Table 8-11 Parameters used to upgrade NE software and patches Parameter Software type Subrack NO Slot NO Board Place SSN Board type Description Type of the software to be operated Number of a subrack, which uniquely identifies a subrack Number of a slot Location of a board. The value is FRONT or BACK. Number of a pinch board Type of a board. The value can be A4L, ASU, BAP, BEA, BFE, BGE, BLU, CLK, CMU, E1G, E32, E8T, EAC, ECU, FLU, HRB, MPU, NLU, P1H, P4L, PIE, PPU, S1L, S2L, SPF, T32, TAC, TNU, or VPU.
Related Tasks
8.3.3 Upgrading the SGSN Software and Patch 8.3.4 Upgrading the GGSN Software and Patch 8.3.9 Upgrading NodeB NE Software and Patch 8.3.6 Upgrading the MGW Software and Patch
8.3.5 Upgrading the MSC Server Software Patch
8.6.5 Parameters for NE Data

This part describes the data of all the related NEs. The backup files of NE data are saved to the path: M2000 server/export/home/sysm/ftproot/ NE type (for example: RNC)/data type/NE FDN. Table 8-12 lists the backup data of NEs. Table 8-12 NE data NE Type NodeB Data Configuration data Engineering parameters Operation logs Device files Main control data Board logs RTWP routine test logs SGSN Configuration data System data User data Command conversion file Alarm conversion file Performance tasks User-defined performance options Performance templates Tracing tasks License System description MGW Environment configuration Description Configuration data of the BS Engineering data of the BS Data about BS maintenance Manufacturing data of all boards in the BS NMPT O&M data O&M data of each board in the BS RTWP data SGSN configuration data SGSN system data SGSN user data The MML commands changed to the default ones of the SGSN The alarms changed to the default ones of the SGSN Data about SGSN performance tasks Data about user-defined SGSN performance options Data about SGSN performance templates Data about SGSN tracing tasks SGSN license Description on the SGSN hardware Information on application types of the UMG
Issue 06 (2008-12-16)
8-101
NE Type
Data Configuration data Performance task configuration Performance object templates Performance counter templates Performance time templates Performance task templates User defined performance counters Tracing task configuration Routine test task configuration Alarm configuration modification Alarm filter conditions Alarm board filter conditions Alarm synchronization number Data management configuration User data
Description UMG configuration data Data about UMG performance tasks Data about UMG performance object templates Data about UMG performance counter templates Data about UMG performance time templates Data about UMG performance task templates UMG user defined performance counters Configuration data about tracing tasks Configuration data about UMG routine test tasks Modified UMG alarm configuration data UMG filter conditions Conditions for filtering UMG boards UMG alarm synchronization number Configuration data about the UMG data management UMG user data GGSN configuration data GGSN alarm logs GGSN operation logs GGSN performance statistics GGSN user data GGSN configuration data MSC Server configuration data CG configuration data
GGSN
Configuration data Alarm logs Operation logs Performance statistics User data
RNC MSC Server CG
Configuration data Configuration data Configuration data
8-102
Issue 06 (2008-12-16)
NE Type HLR IWF ASN-GW
Data Configuration data Configuration data Configuration data Alarm logs Operation logs Performance statistics User data
Description HLR configuration data IWF configuration data ASN-GW configuration data ASN-GW alarm logs ASN-GW operation logs ASN-GW performance statistics ASN-GW user data Manufacturing data of all boards in the BS
BWA
Device files
8.6.6 Parameters for Upgrading the NodeB Software

This part describes the parameters used for upgrading the NodeB software. In the NE Upgrade Wizard dialog box, select the software to be upgraded, and then specify the operation and version number. For details of the parameters related to the NodeB software upgrade, refer to Table 8-13. Table 8-13 Parameters related to the NodeB software upgrade Software Type to Upgrade Upgrade Bootrom and Software Upgrade Operation Type Synchronize Version Description Synchronize the master software with the backup software. That is, the master and backup software is of the same version. Download the Bootrom to the NodeB. The system will ask you to select a version number under Bootrom Version . Download the software to the NodeB. The system will ask you to select a version number under Software Version . Activate the downloaded Bootrom. The system will ask you to select a version number under Bootrom Version. Activate the downloaded NodeB software. The system will ask you to select a version number under Software Version.
Download Bootrom
Download Software
Activate Bootrom
Activate Software
Issue 06 (2008-12-16)
8-103
Software Type to Upgrade
Upgrade Operation Type Download by Configuration
Description Download the software according to the configurations. The system will ask you to select a version number under Software Version. Click Upload new config File , you can upload or upgrade the configuration file. Synchronize the master software with the backup software. That is, the master and backup software is of the same version. Download the patch to the NodeB. The system will ask you to select a version number under Patch Version. Activate the downloaded NodeB patch. The system will ask you to select a version number under Patch Version. Download the patch to the NodeB. The system will ask you to select a version number under Hot Patch Version.
Upload or download config file Upgrade Cold Patch Synchronize Version
Download Patch
Activate Patch
Upgrade Hot Patch
Download Patch
Activate Patch
Activate the patch downloaded to the NodeB.
Confirm Patch
Confirm the activated patch.
Deactivate Patch Unload Patch
Deactivate the patch that is activated but not confirmed. Delete the patch.
Related Tasks
8.3.9 Upgrading NodeB NE Software and Patch
8.6.7 Parameters for License Information of NodeBs Controlled by an RNC

This describes the parameters related to querying the license information of NodeBs concerned.
Table 8-14 and Table 8-15 list the descriptions of the parameters for querying RAN license information. Table 8-14 NodeB license list Parameter License SN Activated CreateDate EndDate Control Description License serial number. License status True indicates that the license is already activated, while False indicates that the license is not activated yet. Time the license is created. Time the license is expired. Control information contained in the License.
Table 8-15 NodeB license distribution list Parameter NE Name isSync UL CE(0/0) DL CE(0/0) Local Cell(0/0) HSDPA(0/0) HSDPA User(0/0) HSDPA RRM(0/0) HS-PDSCH Code(0/0) MBMS(0/0) HSUPA(0/0) PA[44.8dBm] Description Name of an NE Whether to synchronize license information with a NodeB Number of uplink CEs If this parameter is set to Unlimited, the number of CEs is not limited. Number of downlink CEs If this parameter is set to Unlimited, the number of CEs is not limited. Number of local cells If this parameter is set to Unlimited, the number of cells is not limited. HSDPA function switch HSDPA users HSDPA service function items If this parameter is set to Unlimited, the number of HSDPA services is not limited. Number of HS-PDSCH codes If this parameter is set to Unlimited, the number of HS-PDSCH codes is not limited. MBMS service function items If this parameter is set to Unlimited, the number of MBMS services is not limited. HSUPA service function items If this parameter is set to Unlimited, the number of HSUPA services is not limited. Number of local cells where the maximum trasmit power is smaller than 44.8 dBm If this parameter is set to Unlimited, the number of cells is not limited. The quantity of this parameter is not fixed. The value in the square brackets is also a variable, which is set according to the actual situation.
Issue 06 (2008-12-16)
8-105
Related Concepts
8.1.5 RAN License
Related Tasks
8.4.1.5 Querying the License Information about the RAN
8.6.8 Parameters for Setting Parameters of Files Transferring

This part describes parameters used for setting file transfer. Table 8-16 lists parameters used for setting file transfer. Table 8-16 File transfer parameters Parameter File transfer mode FTP SFTP Description Basic FTP mode. Transfer mode based on the SSH protocol. SFTP uses a mature public key mechanism or private key mechanism to encrypt data packets in the network. In this case, data communication between two ends can be performed in an encrypted channel. Optional functions of file transfer Breakpoint During file transfers between clients and servers, if destination files exist, the system prompts users to select resumable downloading or overwriting. If you select resumable downloading, files are transferred from the size of destination files. To improve bandwidth and support the file compression transfer between clients and servers, you need to compress files or directories before you upload files. When you download files, decompress files or directories transferred by servers. The compressed files are in .zip format. The client actively requests for connection. The server listens and determines whether to establish FTP connection.
Compress
Passive
Related Tasks
8.2.8 Setting Parameters of File Transferring
8.6.9 Parameters for the Operator

This describes the parameters in the Assign License to Operator window and Modify window. You can refer to these parameters when you perform the related operations.
8-106
Issue 06 (2008-12-16)
Parameter Operator Description Name of an operator The name of an operator comprises 1 to 30 characters. It does not include underlines. Number of uplink CEs
l
If a function switch is set for this parameter, X indicates the maximum number assigned to each operator. For example, if X is equal to 10, you can infer that the value assigned to each operator is 10. If a function switch is not set for this parameter, X indicates the sum of numbers assigned to all operators. For example, if X is equal to 10, you can infer that the sum of numbers assigned to all operators is 10.
UL CE(X/1000)
For the parameter, 1000 indicates the maximum value that can be assigned to operators. X must be smaller than 1000. Number of downlink CEs
l
DL CE(X/1000)
For the parameter, 1000 indicates the maximum value that can be assigned to operators. X must be smaller than 1000. Number of local cells
l
Local Cell(X/1500)
For the parameter, 1500 indicates the maximum value that can be assigned to operators. X must be smaller than 1500.
Issue 06 (2008-12-16)
8-107
Parameter
Description HSDPA function switch

l
HSDPA(X/1000)
For the parameter, 1000 indicates the maximum value that can be assigned to operators. X must be smaller than 1000. Control item of HSDPA capacity
l
HSDPA User(X/1000)
For the parameter, 1000 indicates the maximum value that can be assigned to operators. X must be smaller than 1000. HSDPA service function items
l
HSDPA RRM(X/ Unlimited)
If this parameter is set to Unlimited, the number of HSDPA services is not limited. Number of HS-PDSCH codes
l
HS-PDSCH Code(X/ Unlimited)
If this parameter is set to Unlimited, the number of HS-PDSCH codes is not limited.
8-108
Issue 06 (2008-12-16)
Parameter
Description MBMS service function items

l
MBMS(X/Unlimited)
If this parameter is set to Unlimited, the number of MBMS services is not limited. HSUPA service function items
l
HSUPA(X/Unlimited)
If this parameter is set to Unlimited, the number of HSUPA services is not limited. Number of local cells where the maximum transmit power is smaller than 41.8 dBm.
l
PA[41.8dBm](X/500)
The value in the square brackets is a variable. The value 500 is set depending on the actual situation. If this parameter is set to Unlimited, the number of cells is not limited.

This describes the parameters for adding or modifying license sharing groups.
Issue 06 (2008-12-16)
8-109
Parameters
Parameter Group Name Description Indicates the name of a sharing group. Value range:
l l l l
160 characters Allowed characters: English letters, numbers, -, and _ Unique and not null Case sensitive
Local Controled Nes
Indicates the NEs that do not belong to any sharing group but support the license sharing function.
NOTE If you are not authorized to operate related NEs, the NEs are not displayed in the Local Controled Nes group box.
Group Nes
Indicates the NEs that have been added to a sharing group.
Related Tasks
8.4.2.4 Adding a License Sharing Group 8.4.2.5 Modifying a License Sharing Group
8.6.11 Parameters for Version Information on Software Installed

This describes the version information about the OMC, adaptation layer, ENM, and northbound Corba interfaces installed on the server.
Version Type OMC Parameter Version Description All the primary version numbers and patch version numbers of the OMCs installed on the server. The version numbers are displayed in the mode of extended node. The patch version numbers are displayed under the corresponding nodes of the primary version numbers. Remark Function remarks of corresponding versions. You can query rather than edit the function remarks corresponding to the primary versions. The corresponding function remarks of patch versions can be queried and edited. Mediation layer neVersion NE version number corresponding to the adaptation layer.
8-110
Issue 06 (2008-12-16)
Version Type
Parameter Matching version
Description The version number of the adaptation layer matching NE version. NE version number corresponding to the ENM. The version number of the adaptation layer matching NE version. The ENM version number matching NE version. The platform version number matching NE version. For example, if the NE version number is BTS3812EV100R008"ENG"C01B031, the corresponding platform version number is iLMTV100R002C06B017.
ENM
neVersion Matching version ENM matching version Platform version
Corba
Version Protocol Status
Version number of the northbound Corba interface. The protocol that the Corba interface complies with. The current status of the Corba interface.
Related Tasks
8.5 Querying Version Information on Software Installed on the Server
Issue 06 (2008-12-16)
8-111
9 Configuration Management
9
About This Chapter
Configuration Management
The M2000 provides the NE centralized management function. On the M2000 client, you can run the MML command or start the LMT of an NE to configure the NE. The NEs of class B and class C do not support the configuration of MML commands. 9.1 Basic Knowledge of Configuration Management Before performing the operations related with configuration management, you must be familiar with the basic knowledge of configuration, such as MIT, MML, NE resource status, and bulk project configuration. The basic configuration knowledge helps you understand the contents of configuration management. 9.2 Configuring NEs by MML Commands You can configure the attributes of the MML command input window and output window on the MML command client. 9.3 Viewing NE Configuration Information The NE configuration data includes the basic configuration data and the configuration data about the NE connection. The NE configuration consists of two categories of information: physical information and logical information. The information includes NE MIT information, NE resource report, NE link report, NE statistics report, and NE report. 9.4 Handling NE Configuration Data This task is performed to handle the NE configuration data. You can manually synchronize or export the data. 9.5 Managing Inventory Data Using the function of inventory management, the M2000 performs centralized and effective management for the physical assess information and key logical configuration information on the entire network devices. You can query, synchronize, modify, import, and export asset information and configuration information about the NEs managed by the M2000. 9.6 Viewing NE Resource Information Through the resource state management, you can monitor resource objects of NEs in real time. The M2000 user can browse resource states of NEs after being granted the browse authority, and can browse and monitor resources of NEs if you have monitor authority. The objects that support browsing and monitoring are categorized into three types: CNNode, board, link, and cell.
9.7 Starting the CME The configuration management express (CME) is a graphic offline configuration tool used for the WRAN. The M2000 provides the function that users can directly start the CME of an NE on the topological view. 9.8 Starting the LMT of an NE The Local Maintenance Terminal (LMT) is the local O&M system of an NE. If an NE cannot be connected directly owing to the configuration of the firewall, you can use the LMT to connect the NE. To ease the use of the LMT, the M2000 enables you to start the LMT of an NE on the topology view. 9.9 Starting the Telnet The M2000 provides the function that users can directly start the Telnet of a BWA, IP device, and IPsec Gateway on the topological view. 9.10 Operating CBSS Device The CBSS consists of the CBSC and the CBTS. You can perform the following maintenance tasks on the CBSS device panel: querying basic information on the board, querying alarms, and configuring the board. 9.11 Reference for Configuration Management Interfaces This topic describes the interface of configuration management and related reference information. The interface and reference information include the MML command interface, follow-up message browser interface, and parameter information involved in the configuration management.
9-2
Issue 06 (2008-12-16)
9.1 Basic Knowledge of Configuration Management

Before performing the operations related with configuration management, you must be familiar with the basic knowledge of configuration, such as MIT, MML, NE resource status, and bulk project configuration. The basic configuration knowledge helps you understand the contents of configuration management. 9.1.1 Management Information Tree (MIT) Management Information Tree (MIT) is used to check the configuration information of NEs. This part describes the MIT, which helps you view the configuration of NEs. 9.1.2 MML command MML command is man machine language. It is the main mode for operating and maintaining NEs. For convenience of NE maintenance, the M2000 provides an MML client on which you can send MML commands to the NE and query the result. 9.1.3 NE Resource States The status of an resource object is determined by the resource type. This part describes the NE resource states supported by the M2000. 9.1.4 CBSS Device Panel The CBSS device panel displays the frame and board on the subrack of the CBSS by using graphics. You can use the CBSS device panel to maintain the board.
9.1.1 Management Information Tree (MIT)

Management Information Tree (MIT) is used to check the configuration information of NEs. This part describes the MIT, which helps you view the configuration of NEs.
l
Through the MIT browser, the system displays the configuration information of required objects in the form of trees. The configuration information comprises physical information and logical information. You can use the navigation tree on the MIT browser interface to search information and set conditions for querying the information of configuration objects. Configuration objects refer to resource types or resource objects.
9.1.2 MML command

MML command is man machine language. It is the main mode for operating and maintaining NEs. For convenience of NE maintenance, the M2000 provides an MML client on which you can send MML commands to the NE and query the result. On the M2000 client, you can send commands to NEs. The MML window displays the messages returned after the MML commands are run. The MML Command window can display only one message. When more than one message is returned after the system delivers an MML command to an NE, you can query the other messages through the Follow-up Reports Browser. The M2000 provides the function of sending MML command scripts. By using this function, you can save the commands of a batch of common tasks or specific tasks as a script file. By running this script file, you can send these commands rather than manually sending them.
Issue 06 (2008-12-16)
9-3
9.1.3 NE Resource States

The status of an resource object is determined by the resource type. This part describes the NE resource states supported by the M2000. Table 9-1 lists all the resource object states. Table 9-1 NE Resource States Status Administration status Administration status Value
l l l
Type Board, cell, and RNCNodeB
Unlocked Locked Shutting down Enable Disable Idle Active Busy Uncongested Congested Unblocked Locked Local locked Remote locked Local and remote locked Active Inactive Unreleased Released Normal Fault Uninstalled Unconfigured Inconsistent PowerOff Active Standby
Operation Status Operation status Usage Status Usage status
l l l l l
Boards, cells, and links
Boards
Congestion status Congestion status Inhibited status Inhibited status
l l l l l l l
Links
Links
Activate status Activate Release status Release Availability status Availability
l l l l l l l l l l
Links
Links
Boards
Standby Status Standby
l l
Boards
9-4
Issue 06 (2008-12-16)
Status CN Node Status CN Node Status
Value
l l l
Type CNNode
Normal Off-load Inhibited
9.1.4 CBSS Device Panel

The CBSS device panel displays the frame and board on the subrack of the CBSS by using graphics. You can use the CBSS device panel to maintain the board. M2000 clients display the CBSS device panel by using graphics. The physical location relation between racks, subracks, and boards is shown on the device panel. On the device panel, you can query basic board information, configure boards, and query alarms. Table 9-2 lists the operations supported by the CBSC board. Table 9-3 lists the operations supported by the CBTS board. Table 9-2 Operations supported by the CBSC board Operation Query Board Information Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, and CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, and CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, and CRSU CFMR, CEVC CPPU and CBPU
Query CPU Usage
Reset Board
Query DSP Status and DSP CPU Usage Query PCF or BSC Buffer Occupancy
Block or Unblock the CXIE IMA Link Query A2 Circuit Status (No RAC) Resetting the A2 Circuit (No RAC) Querying EVC Timeslot Occupancy CRMU CRMU CEVC
Issue 06 (2008-12-16)
9-5
Operation Query Subsystem Status Query E1/T1 Status Start Manual Switching Set or Cancel Board Segregate Query IMA Link Status Query Clock Status
Board CMUX, CBIE CXIE, CAIE, CSTU, COIE, CBIE, CBPE, CAPE CMUX, CSPU, CRMU, CHAC, CPCU, CUMB, CNET, CMPU, CEUB, CRSU CPPU, CFMR, CEVC, CBPU, CIWF, CPDU CXIE, COIE CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CBPU, CPCU, CIWF, CBIE, CLIU, CBPE, CAPE, CUMB, CLCB, CNET, CEUB, CRSU CIWF
Query Interface IP Information and Query Pool Information Query L Interface Channel Query MODEM Chip Parameter and Query IWF Modem Chip Query Board Version Information Query ATM Port Status Query GCKP Clock Information Query Satellite Card Information Query GCKP Board Information Reset the GCKP Board Check DSP Type Query FE Link Status Start GCKP Manual Switching
CIWF CIWF
CNET, CMPU, CLPC CLPC GCKP GCKP GCKP GCKP CFMR CPDU, CBPF, CAPF GCKP
9-6
Issue 06 (2008-12-16)
Operation Query Alarms
Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Refresh Alarms
Table 9-3 Operations supported by the CBTS board Operation Query Board Information Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, and CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU BCKM, BCIM , BRDM, CCPM, CTRM, MTRM, CECM, CMTR, OMTR, STRM CCPM, CECM BCKM BCKM BCIM MTRM, OMTR BCKM
Query CPU Usage
Reset Board
Download or Activate BTS Software or Data Block or Unblock BTS CPM Board Query Current Time of BTS Query BTS Ethernet IP Query FE Port Information Query the Fiber Length Reset BTS
Issue 06 (2008-12-16)
9-7
Operation Query Alarms
Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU, CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM, CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Refresh Alarms
9.2 Configuring NEs by MML Commands

You can configure the attributes of the MML command input window and output window on the MML command client.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC Server, MGW, HLR9820, IWF, BSC, BSC6000, IP Clock Server, and AG.
NOTE
The Confirmation dialog box is displayed with an audible alert when you run some of the MML commands.
9.2.1 Executing an MML Command An MML command is used to perform operation and maintenance on NEs. You can configure NEs and query parameters of the NEs by using MML commands. 9.2.2 Viewing the Result of an MML Command After an MML command is executed, you can view the result in MML Command window. 9.2.3 Viewing Follow-Up Reports Only one prompt can be displayed in the MML Command window. When more than one messages are returned after the M2000 delivers an MML command to an NE, you can query them by using this function. 9.2.4 Setting the Attributes of the "MML Command" Interface You can set attributes of the MML command input/output window and the MML command execution mode on the MML command client. 9.2.5 Setting Report Redirection You can set report redirection to dynamically save the MML command output messages to the specified file. 9.2.6 Setting Report Scroll Display The Common Maintenance parameter on the command output window of the MML command client displays the messages that have executed MML commands. When carrying out MML commands in batches, you can control the scroll display of the Common Maintenance if necessary. 9.2.7 Clearing History Commands The command input window of MML Command Client displays the latest 20 history commands. You can clear these history commands if necessary. 9.2.8 Saving the Result of an MML Command
You can save the MML command output messages to a specified file.
9.2.1 Executing an MML Command

An MML command is used to perform operation and maintenance on NEs. You can configure NEs and query parameters of the NEs by using MML commands.
Context
l
In addition to running an MML command at a time, the system can also run MML commands in batches. When MML commands are run in batches on multiple NEs, the system distributes the MML commands to the NEs one by one. An MML command may have several messages. In this situation, when the M2000 runs these commands, the Common Maintenance tab displays only the first report. You can view the remaining messages in the Follow-up Reports Browser window. For details, see 9.2.3 Viewing Follow-Up Reports.
Procedure
Step 1 Select Maintenance > MML Command or click MML Command. to view the 9.11.1 Interface Description:
Step 2 In the NE window, select the NEs for which an MML command is to be carried out. Step 3 Select an MML command. Step 4 In the command window, set related parameters.
NOTE
The active and standby servers can simultaneously distribute the MML commands related to domain and dual homing.
to run the command. Step 5 Click You can click Stop in 9.2.2 Viewing the Result of an MML Command to stop the MML command that is not executed. ----End
9.2.2 Viewing the Result of an MML Command

After an MML command is executed, you can view the result in MML Command window.
Procedure
Step 1 Choose Maintenance > MML Command or click the shortcut icon Command window. Step 2 Select an MML command in the Commands tab. Step 3 On the NEs tab, the MML commands are classified by NE type and displayed in a list. Click the name of the NE on which the MML command is executed. Step 4 View the command and result report in Common Maintenance. ----End
to display the MML
Postrequisite
The M2000 supports the export and clear-up of messages. To export or clear messages, perform the following steps: 1. 2. On the Commands or NEs tab page, right-click an MML command. Choose Export All or Clean from the shortcut menu.
NOTE
l l l
Messages of the MML commands whose Status are Completed can be cleared up. When MML commands are being delivered, the options Export All and Clean on the shortcut menu are unavailable. Before you clean up the messages, the Confirmation dialog box is displayed, asking you whether or not to export messages. If you click Yes, the system saves exported messages in the predefined path. If you click No, the system does not save the messages already reported.
9.2.3 Viewing Follow-Up Reports

Only one prompt can be displayed in the MML Command window. When more than one messages are returned after the M2000 delivers an MML command to an NE, you can query them by using this function.
Context
When the Follow-up Reports Browser window is displayed, the system automatically generates a cache file for follow-up reports. In the information area located on the lower part of the Followup Reports Browser window, a message is displayed, indicating that the user message is saved in the file. After the Follow-up Reports Browser is closed, the system automatically deletes the cache file.
Procedure
Step 1 Choose Maintenance > Follow-up Reports Browser or click Browser window is displayed. . The Follow-up Reports
Step 2 Right-click in the right window and select Set Follow-up Reports Hint from the shortcut menu. Step 3 Select one or more NEs in the navigation tree. When receiving follow-up messages returned from the selected NE or NEs, the M2000 displays a prompt in the system output window or through at the bottom right corner of the client.
NOTE
You can perform the following operations on the displayed messages in Follow-up Reports Browser:
l l l l
Click Clear or right-click and select Clear Report to clear all the messages displayed in the output window. Click Save or right-click and select Save as to save the displayed output messages. Right-click and select Start Scroll to display the messages through automatic scrolling. Right-click and select Pause Scroll to stop the scrolling display. For details, refer to 9.2.5 Setting Report Redirection. Right-click and select Cancel Redirection to disable the redirection.
----End
Related References
9.11.2 Interface Description: Follow-Up Reports Browser
9.2.4 Setting the Attributes of the "MML Command" Interface

You can set attributes of the MML command input/output window and the MML command execution mode on the MML command client.
Procedure
Step 1 Choose Maintenance > MML Command or click Description: MML Command window. Step 2 Expand the navigation tree and select an NE. Step 3 Select the Common Maintenance tab. Right-click in the blank and select Parameter Setting to view the MML Client Setting dialog box. Step 4 Set the relevant parameters and click OK. 9.11.7 Parameters for Setting the Attributes of the MML Command Interface lists the descriptions of the parameters for viewing NE backup files.
NOTE
to view the 9.11.1 Interface
The settings made in the command output window are still valid after the MML command client resets.
----End
Related References
9.11.7 Parameters for Setting the Attributes of the MML Command Interface
9.2.5 Setting Report Redirection

You can set report redirection to dynamically save the MML command output messages to the specified file.
Context
l
To save the message obtained before the redirection, refer to 9.2.8 Saving the Result of an MML Command. You can set the size of the redirection report when 9.2.4 Setting the Attributes of the "MML Command" Interface.
Procedure
Step 1 Choose Maintenance > MML Command or click Description: MML Command window. Step 2 Expand the navigation tree and select an NE. Step 3 Select Common Maintenance tab. Right-click in the blank area and select Report Redirection to save the output messages as a file. To cancel the redirection, right-click and select Cancel Redirection. ----End
to view the 9.11.1 Interface
9.2.6 Setting Report Scroll Display

The Common Maintenance parameter on the command output window of the MML command client displays the messages that have executed MML commands. When carrying out MML commands in batches, you can control the scroll display of the Common Maintenance if necessary.
Context
When carrying out MML commands one by one, you cannot control the scroll display of Common Maintenance through this operation.
Procedure
. Step 1 Choose Maintenance > MML Command or click The 9.11.1 Interface Description: MML Command window is displayed. Step 2 Select an NE in the NE window. Step 3 In the command output window of the MML command client, select Auto Scroll from the shortcut menu in Command Maintenance. Then , each MML messages are automatically scroll displayed.
NOTE
l l
When carrying out MML commands in batches, select Auto Scroll, and the Common Maintenance starts scroll display of the MML command reports according to the sequence of the MML commands. When carrying out MML commands in batches, if you do not select Auto Scroll, the Common Maintenance displays only the MML command report that is currently issued. To query the report of other MML commands, select the MML command to be queried in the Carried out Command List Window, and the corresponding report will be displayed in the Common Maintenance.
----End
9.2.7 Clearing History Commands

The command input window of MML Command Client displays the latest 20 history commands. You can clear these history commands if necessary.
Procedure
Step 1 Select Maintenance > MML Command or click Step 2 Select an NE in the NE window. Step 3 In the command input window of MML Command Client, right-click and select Clear History Command to clear the history commands. This operation only clears the history command records in the command input window. It does not affect the history command records in the command output window. ----End and enter MML Command window.
9.2.8 Saving the Result of an MML Command

You can save the MML command output messages to a specified file.
Prerequisite
l l l
You have logged in to the M2000 client as an NE user of the NE. The MML Command window is displayed. The NE user is bound with the relevant command groups.
Procedure
Step 1 Choose Maintenance > MML Command or click Description: MML Command window. to view the 9.11.1 Interface
Step 2 Select an NE and an NE version in the MML Command window. The GUI displays the MML Command Navigation tree and the command input box. Step 3 Right-click in the Command Maintenance tab in the MML Command window, and select Report Redirection. Step 4 In the displayed Save dialog box, enter a name for the file to save the MML command result. Run MML commands. The command results are displayed in Common Maintenance and automatically saved to the specified file.
NOTE
l l
To stop saving of the command result, right-click in the Command Maintenance tab, and select Cancel Redirection. Right-click in the Common Maintenance tab, and select Save as from the shortcut menu. Then you can save the results displayed in Common Maintenance to the specified file.
----End
9.3 Viewing NE Configuration Information

The NE configuration data includes the basic configuration data and the configuration data about the NE connection. The NE configuration consists of two categories of information: physical information and logical information. The information includes NE MIT information, NE resource report, NE link report, NE statistics report, and NE report. 9.3.1 Viewing NE MIT Information The MIT browser supports the navigation tree search function. You can query configuration information of NEs. The configuration information consists of physical information and logical information. 9.3.2 Viewing NE Resource Reports You can query basic information and other configuration information of multiple NEs. Only the MGW and MSC Server support this function. 9.3.3 Viewing NE Link Reports You can query the information about all the links related to an NE. 9.3.4 Viewing NE Statistics Reports You can query information about the NE version. 9.3.5 Viewing NE Reports You can query the basic information about multiple NEs at a time.
9.3.1 Viewing NE MIT Information

The MIT browser supports the navigation tree search function. You can query configuration information of NEs. The configuration information consists of physical information and logical information.
Prerequisite
l l
You have logged in to the M2000 client. The NE is properly connected to the M2000.
Procedure
Step 1 Choose Configuration > MIT Browser, or click . The MIT Browser interface is displayed.
Step 2 Expand the navigation tree. Select an NE, resource types, or resources.
NOTE
If the number of configuration data records for an NE exceeds 200, the system browses on a page basis.
Step 3 Right-click the NE, resource type, or resource object, and select Search, or press Ctrl+F to view the Search box. The search dialog box is displayed and the search function is enabled.
NOTE
The system can display a maximum of the earliest 100 searching results.
Step 4 Set search condition. 9.11.8 Parameters for NE MIT Information lists the descriptions of the parameters for viewing NE backup files. If cases are sensitive during search, select Case sensitive. Step 5 Click Search. The search results are displayed in the Search results. Double-click a record. You can find the resource node on the navigation tree. In the list, the system displays the configuration information of this node. During search, click Cancel to stop searching. The searching results, however, are displayed in Search results. ----End
Related Concepts
9.1.1 Management Information Tree (MIT) 9.1.1 Management Information Tree (MIT)
Related References
9.11.3 Interface Description: MIT Browsing 9.11.8 Parameters for NE MIT Information
9-14
Issue 06 (2008-12-16)
9.3.2 Viewing NE Resource Reports

You can query basic information and other configuration information of multiple NEs. Only the MGW and MSC Server support this function.
Procedure
Step 1 Choose Report > NE Resource Report to view the NE Selection - NE Resource Report dialog box. Step 2 Select one or more NEs in the navigation tree. Step 3 Click OK. The NE Resource Report window is displayed. The upper part of the window lists the NE information, and the lower part lists the number of each type of NEs.
NOTE
In the NE Resource Report window, you can query, save and print reports.
----End
9.3.3 Viewing NE Link Reports

You can query the information about all the links related to an NE.
Context
The wizard applies only to the SGSN, MSC Server, RNC and TGW. For the link types matching the SGSN, MSC Server, RNC and TGW, refer to Table 9-4. Table 9-4 Link types matching the NE link reports NE Type SGSN MSC Server RNC TGW Link Type Supports MTP3 link reports, MTP3 route reports, MTP3B link reports, NSVC reports, and MTP3B route reports. Supports MTP3 link reports and MTP3 route reports. Supports PPP link reports, MLPPP link reports, PPP Group link reports, IPPATH link reports, and SCTP link reports. Supports PPP link reports, MLPPP link reports, and PPP Group link reports.
Procedure
Step 1 Choose Report > Link Report Wizard. The Create NE Link Report Wizard dialog box is displayed. Step 2 Select an NE type, and click Next. Step 3 Select one or more NEs in the navigation tree, and click Next. Step 4 Select a link report type, and click Finish.
NOTE
In the dialog box listing the link reports. you can query, save and print reports.
----End
9.3.4 Viewing NE Statistics Reports

You can query information about the NE version.
Procedure
Step 1 Select Report > NE Statistic Report to view the NE Selection - NE Statistic Report dialog box. For details, refer to 9.11.10 Parameters for NE Statistics Report. Step 2 Select one or more NEs in the navigation tree. Step 3 Click OK to view the NE Statistic Report window. Information about versions and number of versions of the selected NEs is listed in the NE Statistic Report window.
NOTE
In the NE Statistic Report window, you can query, save and print reports.
----End
Related References
9.11.10 Parameters for NE Statistics Report
9.3.5 Viewing NE Reports

You can query the basic information about multiple NEs at a time.
Procedure
Step 1 Select Report > NE Report to view the NE Selection - NE Report dialog box. Step 2 Select one or more NEs in the navigation tree. Step 3 Click OK to view the NE Reports window. The upper part of the window lists the NE information, and the lower part lists the number of each type of NEs.
NOTE
In the NE Reports window, you can query, save and print reports. For real RNC, the function of exporting RNC IP can be performed in the interface.
----End
9.4 Handling NE Configuration Data

This task is performed to handle the NE configuration data. You can manually synchronize or export the data.
9-16
Issue 06 (2008-12-16)
9.4.1 Manually Synchronizing NE Configuration Data After a physical NE is disconnected from the M2000, it must connect to the M2000 again. If the configuration data of the NE has any change when the NE is reconnected to the M2000, you need to manually synchronize the changed data to the M2000 database.In the case of some NEs that do not support the automatic synchronization function, you need to manually synchronize the configuration data of these NEs. 9.4.2 Manually Exporting NE Configuration Data You can manually exports configuration data of physical NEs and save the required configuration data to a specified path.. 9.4.3 Importing the Configuration Files of PCU Users can edit the exported PCU configuration files, and then import the edited files to the PCU. The PCU NEs process the successfully exported configuration files, and then generate files that records the processing results. The M2000 downloads the result files and combine them into a file. The file is saved in the directory specified previously. 9.4.4 Exporting the Configuration Files of PCU Users can currently export the configuration files of one or more PCU NEs. PCU configuration file
9.4.1 Manually Synchronizing NE Configuration Data

After a physical NE is disconnected from the M2000, it must connect to the M2000 again. If the configuration data of the NE has any change when the NE is reconnected to the M2000, you need to manually synchronize the changed data to the M2000 database.In the case of some NEs that do not support the automatic synchronization function, you need to manually synchronize the configuration data of these NEs.
Prerequisite
l l
You have logged in to the M2000 client. The NE is connected to the M2000, and the relevant mediation layer is installed.
Context
In general, when the configuration data of an NE has changes, the changed data is automatically synchronized to the M2000 database. Two automatic synchronization types are available: NEtriggering automatic synchronization and scheduled-triggering automatic synchronization. The process of NE-triggering automatic synchronization is as follows: 1. 2. 3. 4. 5. 6. 7.
Issue 06 (2008-12-16)
After the configuration data of an NE is added, deleted, or modified, the NE automatically sends the change notification to the Mediation of the M2000. After the Mediation receives the change notification, it converts the notification to an automatic synchronization event and then sends the event to the configuration server. After the configuration server receives the event, it determines the synchronization range according to the description in the event. (The range can be a whole NE or a subtree.) The Mediation layer converts the request and synchronization conditions to the command that can recognized by the NE. The M2000 sends the command to the NE. The NE handles the command filter message and returns the required NE message. The configuration server receives and parsed the message.
8.
The database and the MIT are updated.
Scheduled-triggering automatic synchronization: On the integrated task management interface, you can enable the configuration data of an NE to be synchronized on a scheduled basis. You can set the synchronization time and the period. After the settings are made, the server synchronizes the configuration data on a scheduled basis. All the configuration data of the NE are synchronized during the scheduled synchronization. For details, see 14.4.2 Modifying the Synchronization of NE Configuration Data. The procedure is as follows: 1. 2. The server periodically executes the task of synchronizing NEs. The configuration module obtains the configuration data. The following two modes are available:
l
The server delivers the message of LST to check the configuration data of an NE. After the Mediation parse the message returned by the NE, it returns all the configuration data to the configuration modules. The server asks the NE to upload configuration data by sending an MML command to the NE. After the NE receives the command, it exports the data file and then upload the configuration data to a position specified by the M2000 through the FTP. When the M2000 receives the command indicating that the configuration data is successfully uploaded, it gets access to the position and obtains and parses the data file. After the data file is parsed, the configuration data is saved to the database. This method can be applicable NEs such as NodeB, RNC, MSCe, and MSC Server.
3.
The configuration modules send the new configuration data to the client and update the MIT.
CAUTION
l
For NEs other than new physical NEs, you should refresh the node in the navigation tree in the MIT Browser window after each synchronization. You are not allowed to manually synchronize an NE if the NE is in the Automatic or Periodic synchronizing state. If an automatic synchronization task is being executed when you trigger automatic synchronization, the task is added to a queue. The task can be executed only after the previous synchronization task is executed.
Procedure
Step 1 Select one or more physical NEs on the topology view. Step 2 Right-click the NEs, and then choose Synchronize CM data or Synchronize CM data in batches on the displayed shortcut menu. If you plan to stop the synchronization task, you can right-click the NEs and then choose Cancel Synchronization on the displayed shortcut menu. The synchronization progress is displayed on the top left corner of the NE icon. When 100% is displayed, the synchronization is complete and the progress percentage bar disappears. ----End
9.4.2 Manually Exporting NE Configuration Data

You can manually exports configuration data of physical NEs and save the required configuration data to a specified path..
Prerequisite
The NE is properly connected to the M2000.
Procedure
Step 1 Choose Configuration > MIT Browser or click . The MIT Browsing window is displayed.
Step 2 Expand the navigation tree. Select a physical NE to export the configuration data. Step 3 Right-click the NE, and select Export to view the Export Configuration Data dialog box. Step 4 Enter a file name, and select a path for saving the file. Step 5 Select a file type. Step 6 Click Export. The system supports two export format, that is, .xml and .csv. ----End
9.4.3 Importing the Configuration Files of PCU

Users can edit the exported PCU configuration files, and then import the edited files to the PCU. The PCU NEs process the successfully exported configuration files, and then generate files that records the processing results. The M2000 downloads the result files and combine them into a file. The file is saved in the directory specified previously.
Context
l
The import lasts for some time. You can view the related information in the system information area. If the configuration files of multiple PCUs are imported, each PCU processes its configuration file and generates a result file. The M2000 downloads the result files generated by the PCUs and merges the files into one. In the merged file, the original result files are separated by the PCU name. The PCU file transfer mode can be active or passive. You can set the file transfer mode by referring to 8.2.8 Setting Parameters of File Transferring.
Procedure
Step 1 Choose Configuration > PCU Integrated Configuration > Import. The Import PCU config file dialog box is displayed. Step 2 Click
NOTE
to choose a file to imported.
If the PCU NEs contained in the configuration files are still connected, the PCU NEs are displayed in the Import PCU config file dialog box.
Issue 06 (2008-12-16)
9-19
Step 3 Select one or more PCU NEs whose configuration files will be imported. Step 4 Click Upload. Step 5 In the Choose a file to save result dialog box, click files. to select a path to save the PCU result
Step 6 The Information dialog box is displayed, prompting that the file uploading is complete. You can check whether the import is successful in the system output window. ----End
9.4.4 Exporting the Configuration Files of PCU

Users can currently export the configuration files of one or more PCU NEs. PCU configuration file
Context
l
The exportation lasts for some time. You can view the related processes in the system information area. If the configuration files of multiple PCUs are exported, the M2000 merges these files into one. In the merged file, the original configuration files are separated by the PCU name. The PCU file transfer mode can be active or passive. You can set the file transfer mode by referring to 8.2.8 Setting Parameters of File Transferring.
Procedure
Step 1 Choose Configuration > PCU Integrated Configuration . The Export PCU config file dialog box is displayed. Step 2 Click to select the save path of the file to be exported.
Step 3 Select one or more PCU NEs whose configuration files will be exported. Step 4 Click OK. You can check whether the export is successful in the system output window. ----End
9.5 Managing Inventory Data

Using the function of inventory management, the M2000 performs centralized and effective management for the physical assess information and key logical configuration information on the entire network devices. You can query, synchronize, modify, import, and export asset information and configuration information about the NEs managed by the M2000.
Context
NOTE
You can manage inventory data only after purchasing the license of the inventory management function.
Inventory management involves physical inventory management and logical inventory management.

l
Logical inventory management mainly manages logical inventory objects, that is, cells and software or patches. The management of cells is supported by only the BSC, CBSC and RNC. Physical inventory management mainly manages physical inventory objects, that is, subracks, frames, slots, boards, ports, and antennas.Only the CBTS, BTS, and NodeB support the management of antennas.
The hierarchy of the navigation tree in the Inventory Management window is as follows: 1. 2. 3. 4. 5. Level 1: NE type. For example, MGW and RNC. Level 2: specific NEs. Level 3: types of inventory objects. For example, physical and logical inventory objects. Level 4: MOC. For example, cells, frames, and boards. Level 5: MO. For example, board 1 and board 2.
9.5.1 Adding Inventory Data Due to different module files on M2000 servers, some types of inventory data cannot be synchronized to the M2000. The inventory data that cannot be synchronized to the M2000 are determined by the module files on the M2000 server. 9.5.2 Querying Inventory Data This describes how to query inventory data. Thus you can know the configuration of network devices and the logical resources such as cells. 9.5.3 Importing Inventory Data This describes how to import inventory data to the M2000 database. By using this function, you can quickly update inventory data when expanding the system or modifying part of device information. 9.5.4 Modifying Inventory Data For the inventory data that cannot be synchronized to M2000, after you add the inventory data that fails to be synchronized to the M2000 database, you can manually update the inventory data in the M2000 database. The inventory data that cannot be synchronized to the M2000 are determined by the module files on the M2000 server. 9.5.5 Manually Synchronizing Inventory Data This describes how to manually synchronize the required inventory data to the M2000. You can synchronize the inventory data of multiple NEs at the same time. 9.5.6 Manually Exporting Inventory Data This task describes how to export the inventory data of all or specified MOs under an NE to a specified file for future query.
Related References
9.11.4 Interface Description: Inventory Management
9.5.1 Adding Inventory Data

Due to different module files on M2000 servers, some types of inventory data cannot be synchronized to the M2000. The inventory data that cannot be synchronized to the M2000 are determined by the module files on the M2000 server.
Issue 06 (2008-12-16)
9-21
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform inventory management.
Context
You can add inventory data in batches by means of exporting files. For details, refer to 9.5.3 Importing Inventory Data.
NOTE
Only antennas support this function.
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is displayed. Step 2 In the navigation tree, right-click an MOC node and choose Add on the shortcut menu. Step 3 Enter the attribute in the displayed Setting dialog box. Step 4 Click OK. The displayed Message box shows whether the operation succeeds. If the operation is successful, the added inventory data is displayed as a sub-node of the MOC node in the navigation tree. Step 5 Click OK to close the Message dialog box. ----End
9.5.2 Querying Inventory Data

This describes how to query inventory data. Thus you can know the configuration of network devices and the logical resources such as cells.
Prerequisite
l l
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is displayed. Step 2 Query the information on the inventory data. You can check the data by using the following two methods. Query Mode Browse Mode Operation Select the related MO in the navigation tree. Then you can view the detailed inventory information in a table in the right pane.
9-22
Query Mode Search
Operation 1. Right-click the node in the navigation tree, and then choose Search on the shortcut menu. 2. In the displayed Condition setting dialog box, set the search conditions. 3. Click Search. The right pane of the Inventory Management window displays all inventory information that meets the conditions.
NOTE A maximum of five results are listed in the right pane of the Inventory Management window.
----End
Related References
9.11.11 Parameters for Querying Inventory Data
9.5.3 Importing Inventory Data

This describes how to import inventory data to the M2000 database. By using this function, you can quickly update inventory data when expanding the system or modifying part of device information.
Prerequisite
l l
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is displayed. Step 2 In the navigation tree, right-click an NE node or the MOC node and choose Import on the shortcut menu. Step 3 In the displayed Open dialog box, select the file to be imported and click Open. Step 4 In the displayed Setting dialog box, select the import mode. Import Mode Description
Overwrite the duplicate name during the If the imported data is the same as the key words import of an existing record, overwrite the existing data. Ignore the duplicate name during the import Step 5 Click OK.
If the imported data is the same as the key words of an existing record, use the existing data.
The displayed Message box shows whether the import is successful. Step 6 Click OK. The Message box is closed. ----End
9.5.4 Modifying Inventory Data

For the inventory data that cannot be synchronized to M2000, after you add the inventory data that fails to be synchronized to the M2000 database, you can manually update the inventory data in the M2000 database. The inventory data that cannot be synchronized to the M2000 are determined by the module files on the M2000 server.
Prerequisite
l l
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is displayed. Step 2 In the navigation tree, right-click an MO and choose Mod on the shortcut menu. Step 3 Modify the attribute in the displayed Setting dialog box. Step 4 Click OK. The displayed Message box shows whether the modification succeeds. Step 5 Click OK to close the Message dialog box. ----End
9.5.5 Manually Synchronizing Inventory Data

This describes how to manually synchronize the required inventory data to the M2000. You can synchronize the inventory data of multiple NEs at the same time.
Context
The M2000 can synchronize the inventory data at predefined time. For details, refer to 14.4.4 Modifying the Synchronization of Inventory Data.
Procedure
Step 1 Choose Configuration > Inventory Management to view the Inventory Management window. Step 2 Right-click the blank area in Table of synchronization progress and choose Add Task on the shortcut menu. Step 3 In the displayed Synchronization dialog box, select the NE to synchronize the inventory data. You can select multiple NEs. Step 4 Click OK.
The displayed Message box shows whether the synchronization task is successful. At the same time, one record is added in Table of synchronization progress and you can view the synchronization progress.
NOTE
If the synchronization fails, the Message field in Table of synchronization progress shows Failed. You can right-click the record and choose Fail details on the shortcut menu to view the reason.
Step 5 Click OK to close the Message dialog box. ----End
9.5.6 Manually Exporting Inventory Data

This task describes how to export the inventory data of all or specified MOs under an NE to a specified file for future query.
Context
An NE is composed of multiple MOCs. An MOC is composed of multiple MOs. For example, an RNC is composed of boards and antennas. A board is composed of multiple instances such as board 1 and board 2. In this example, board and antenna are MOCs. Board 1 and board 2 are MOs.
Procedure
Step 1 Choose Configuration > Inventory Management to view the Inventory Management window. Step 2 Right-click an NE or MO in the navigation tree and choose Export on the shortcut menu.
l l
If you select an NE, the inventory data of all its MOs is exported. If you select an MO, the inventory data of this MO is exported.
Step 3 In the displayed Save dialog box, set the file name, save path, and file type.
l l
If you export the inventory data of all MOs under the NE, File Type is .txt, .xml or .csv. If you export the inventory data of a specific MO, File Type is .xml or .csv.
Step 4 Click Save. The displayed Message box shows whether the export is successful.
NOTE
If the system fails to export the inventory data of all MOs under the NE, the Message box shows the reason.
Step 5 Click OK. The Message box is closed. ----End
9.6 Viewing NE Resource Information

Through the resource state management, you can monitor resource objects of NEs in real time. The M2000 user can browse resource states of NEs after being granted the browse authority, and can browse and monitor resources of NEs if you have monitor authority. The objects that support browsing and monitoring are categorized into three types: CNNode, board, link, and cell.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC SERVER, MGW, HLR9820, IWF, IP Clock Server,and AG. 9.6.1 Viewing NE Resource States M2000 supports the function of viewing NE resource states. You can set conditions to view NE resource status. If you have only the browse authority, then you can browse resource status rather than monitor the status. 9.6.2 Monitoring NE Resource States in Real Time M2000 supports the function of monitoring NE resource states in real time. You can monitor the status of the NEs in real time. Only the users with the monitoring privilege can perform this operation.
9.6.1 Viewing NE Resource States

M2000 supports the function of viewing NE resource states. You can set conditions to view NE resource status. If you have only the browse authority, then you can browse resource status rather than monitor the status.
Prerequisite
l l l l l
You have the related authority. You have logged in to the M2000 client as an NE user. The mediation software of the NE is installed on both the M2000 server and client. The NE is properly connected to the M2000. The version of the NE enhanced maintenance is upgraded.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC SERVER, MGW, HLR9820, IWF, IP Clock Server,and AGRNC, NodeB, SGSN, GGSN80, MSC SERVER, MGW, HLR9820*, and IWF.
Procedure
Step 1 Choose Configuration > State Management > State Browser . The State Management dialog box is displayed. 9.11.9 Parameters for NE Resource Report lists the descriptions of the parameters for viewing NE backup files. Step 2 Select the State Browser tab. Step 3 Expand the Resource Type navigation. Select the type of the resource object. Step 4 Unfold the NE navigation tree, and select the NE to which these resource objects belong. Step 5 Click Query. A bar is displayed to show the query progress. To stop the query, click Cancel in the progress prompt box. The queried results are not displayed. ----End
Result
The status information about the queried resource objects is listed in the right part of the Status Browser dialog box. The total number of resource objects that meet the query conditions is displayed at the left bottom.
Related Concepts
Related References
9.11.9 Parameters for NE Resource Report
9.6.2 Monitoring NE Resource States in Real Time

M2000 supports the function of monitoring NE resource states in real time. You can monitor the status of the NEs in real time. Only the users with the monitoring privilege can perform this operation.
Prerequisite
l l
You have the related authority. The NE is properly connected to the M2000.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC SERVER, MGW, HLR9820, IWF, IP Clock Server,and AG. The operations related to monitoring the resource status include:
l l
Starting or Stopping Resource Status. Deleting Resource Status Monitoring Tasks.
An M2000 client can monitor up to 1,000 resource objects. The resource status monitoring refers to real-time monitoring tasks. They are valid only for the activated users. After the client restarts, the monitoring settings become invalid. The settings, however, remain unaffected after you close the Status Management window.
Procedure
Step 1 Choose Configuration > State Management > State Monitor . The State Management dialog box is displayed. Step 2 Select the State Browser tab to view the resource status. For details, refer to 9.6.1 Viewing NE Resource States. Step 3 Select one or more records in the list of queried results. Step 4 Right-click the selected records, and select Monitor or click Monitor to start a monitoring task. Step 5 Select the State Monitor tab. Select a resource object under the Resource Type node in the navigation tree. The monitoring tasks on the status of this resource object is listed in the right part of the tab.
Step 6 Select one or more resource status records. You can perform the following operations: Task Reset Zoom Then... Right-click and select Resume from the shortcut menu to start the monitoring task. Alternatively, click Resume.
Suspend a measurement task Right-click and select Suspend from the shortcut menu to stop the monitoring task. Alternatively, click Suspend. Delete Right-click and select Delete from the shortcut menu to delete the monitoring task. Alternatively, click Delete.
9.11.6 Parameters for Monitoring NE Resource States in Real Time lists the descriptions of the parameters for viewing NE backup files. ----End
Related Concepts
Related References
9.11.6 Parameters for Monitoring NE Resource States in Real Time 9.11.9 Parameters for NE Resource Report
9.7 Starting the CME

The configuration management express (CME) is a graphic offline configuration tool used for the WRAN. The M2000 provides the function that users can directly start the CME of an NE on the topological view.
Prerequisite
l
Before starting the CME, users must install the CME software of correct version on the M2000 client. The version of the installed CME must be consistent with that of the NE.
Context
Only the RNC and NodeB support starting the CME.
Procedure
On the main interface of the M2000 client, choose Maintenance > WRAN CME to start the CME client. ----End
9.8 Starting the LMT of an NE

The Local Maintenance Terminal (LMT) is the local O&M system of an NE. If an NE cannot be connected directly owing to the configuration of the firewall, you can use the LMT to connect the NE. To ease the use of the LMT, the M2000 enables you to start the LMT of an NE on the topology view.
Prerequisite
l
Before starting the LMT of an NE, ensure that the correct LMT software corresponding to the NE is installed on the M2000 client. The version of the LMT installed on the M2000 must be the same as that installed on the NE. Otherwise, the LMT cannot be started.
Context
l
If you have bound the user to NE, then the system will automatically log in the LMT using the user ID of the NE User when starting the LMT, otherwise you should manually input the user name and password. Only when the NE type is NodeB, the M2000 server will serve as LMT's proxy if you start the LMT from the physical topology.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology dialog box is displayed. Step 2 On the physical topology view or under the physical topology navigation tree, select the NEs whose LMTs need to be started. Step 3 Right-click the NE, and select Maintenance Client. ----End
9.9 Starting the Telnet

The M2000 provides the function that users can directly start the Telnet of a BWA, IP device, and IPsec Gateway on the topological view.
Prerequisite
The NE is properly connected to the M2000.
Context
This function is supported by only the BWA, IP device, and IPsec Gateway.
Procedure
On the main interface of the M2000 client, right-click an NE that requires the startup of Telnet, and then choose Start Telnet from the displayed shortcut menu. ----End
9.10 Operating CBSS Device

The CBSS consists of the CBSC and the CBTS. You can perform the following maintenance tasks on the CBSS device panel: querying basic information on the board, querying alarms, and configuring the board. 9.10.1 Operating CBSS Board The CBSS board consists of the CBSC board and the CBTS board. The operations described in this part can be performed on both the CBSC board and the CBTS board. 9.10.2 Maintaining CBSC The topic describes how to maintain the CBSC. 9.10.3 Maintaining CBTS The topic describes how to maintain the CBTS.
Related Concepts
Related References
9.11.5 Interface Description: Device Panel
9.10.1 Operating CBSS Board

The CBSS board consists of the CBSC board and the CBTS board. The operations described in this part can be performed on both the CBSC board and the CBTS board. 9.10.1.1 Querying the Board Information After you log in to the device panel, you can check the status, operational status, management status, active/standby status, and ATM bus port information about the CBSS board. 9.10.1.2 Refreshing a Panel After you log in to the device panel, you need to refresh the panel to obtain the latest NE data so that the status of the panel is consistent with the actual status. 9.10.1.3 Resetting a Board This topic describes how to reset a board. 9.10.1.4 Switching over a Board This topic describes how to switch over the CBTS board and the CBSC board. 9.10.1.5 Querying the Alarms This topic describes how to query the alarms of the CBSS board 9.10.1.6 Refreshing the Alarms After you log in to the device panel, you need to refresh alarms to obtain the latest alarm information so that the alarm information on the panel is consistent with the actual alarm information. 9.10.1.7 Showing/Hiding the Fault Bar This topic describes how to show or hide the fault bar. By default, the fault bar is shown. 9.10.1.8 Showing/Hiding the Legend
This topic describes how to show or hide the legend. By default, the legend is shown.
Querying the Board Information

After you log in to the device panel, you can check the status, operational status, management status, active/standby status, and ATM bus port information about the CBSS board.
Prerequisite
l l
The login user has relevant rights. The CBSS communicates with the M2000 properly.
Context
To check board types, refer to 9.1.4 CBSS Device Panel. The functions supported by the CBSC are different from those supported by the CBTS. This section describes how to query CBSC information. The difference between the operations for querying CBSC information and those for querying CBTS information is detailed in relevant steps.
Procedure
Step 1 Open the Device Panel window. You can use either of the following ways to open the Device Panel window.
l l
Choose Configuration > Device Map. Right-click an NE node in the physical topology navigation tree or the physical topology view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Board Information. The following functions are available to the CBTS:
l l l
Query Board Status Query Board Version Information Query Board Special Status
Step 4 Check the board information in Query Board Information. For details of the parameter description of board information, refer to 9.11.12 Parameters for Querying the Board Information. Step 5 After the query is complete, save the query result or close the window.
l l
Click Save to save the query result as a .txt file. Click Close to close the window.
----End
Related References
9.11.12 Parameters for Querying the Board Information
Refreshing a Panel
After you log in to the device panel, you need to refresh the panel to obtain the latest NE data so that the status of the panel is consistent with the actual status.
Prerequisite
The CBSS communicates with the M2000 properly.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Select the entire subrack panel. Right-click the panel, and then choose Refresh. ----End
Resetting a Board
This topic describes how to reset a board.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. For the board that is in active/standby mode, such as CMUX/CRMU/CSPU/CPCU/CHAC, if you want to perform active/standby switchover, manual switchover is recommended. If you reset the main board where the full backup of active/standby data is performed, the standby board resets automatically after the standby board becomes the active board. Before you reset the resource board, isolate the board. In this case, new services are assigned to the board so that the impact on the services is reduced.
Procedure
l l
9-32
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset Board. Step 4 In the Confirm dialog box, click OK. Step 5 Check the information in Reset Board. Step 6 Save the query result or close the window.
l l
----End
Switching over a Board

This topic describes how to switch over the CBTS board and the CBSC board.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. This operation is performed when the software of the board is upgraded. If you want to upgrade the CMUX board, reload and upgrade the standby CMUX, and then start manual switchover to achieve smooth transition. The operation is performed to upgrade versions within a specified range. If you want to upgrade to other versions not specified, contact Huawei technical support engineers. Do not perform manual switchover until five minutes have passed after the standby board is upgraded to the active board. You should not perform manual switchover if the full backup of the configuration data on the active/standby board is performed. When the system works properly, you must maintain the consistency of the loaded programs between the active board and the standby board.
CAUTION
The operation may have great impact on the system performance. Do not perform the operation unless otherwise specified.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Start Manual Switching. Step 4 In the Confirm dialog box, click OK. Step 5 Check the information in Start Manual Switching. Step 6 Save the query result or close the window.
l l
----End
Querying the Alarms

This topic describes how to query the alarms of the CBSS board
Prerequisite
l l
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Check the displayed device panel. If a board has alarms, there are alarms in red on the board. Step 4 Select the board that has alarms. Right-click the board, and then choose Query Alarms. Step 5 Check the alarm information in Current Fault Alarms. ----End
Refreshing the Alarms

After you log in to the device panel, you need to refresh alarms to obtain the latest alarm information so that the alarm information on the panel is consistent with the actual alarm information.
Prerequisite
l l
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Select a board. Right-click the board, and then choose Refresh Alarms. The system synchronizes NE alarm information. ----End
Showing/Hiding the Fault Bar

This topic describes how to show or hide the fault bar. By default, the fault bar is shown.
Context
The fault bar displays the specific subrack, slot, and board that have faults. When you stop the mouse pointer on the fault bar, the bar stops moving.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Select the entire rack panel. Right-click the panel, and then choose Show/Hide Fault Bar. ----End
Showing/Hiding the Legend

This topic describes how to show or hide the legend. By default, the legend is shown.
Context
Legends are categorized into alarm legends and alarm status legends.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Select the entire rack panel. Right-click the panel, and then choose Show/Hide Legend. ----End
9.10.2 Maintaining CBSC

The topic describes how to maintain the CBSC. 9.10.2.1 Querying the Board Version This topic describes how to query the board version. 9.10.2.2 Querying the Subsystem Status After you log in to the device panel, you can check the operational status, management status, and active/standby status of the subsystem. 9.10.2.3 Querying the Clock Status This topic describes how to query the clock status. 9.10.2.4 Querying the CPU Usage This topic describes how to query the CPU usage. 9.10.2.5 Querying the E1/T1 Status This topic describes how to query the E1/T1 link status. 9.10.2.6 Querying the A2 Circuit Status This topic describes how to query the A2 circuit status. 9.10.2.7 Querying the PCF Buffer Usage This topic describes how to query PCF buffer occupancy. 9.10.2.8 Querying the FE Link Status This topic describes how to query the FE link status. 9.10.2.9 Querying the IMA Link Status After you log in to the device panel, you can check online the near-end and far-end IMA link status. By checking the status, you can know whether the IMA link is configured and whether the near end and the far end can receive information.
9.10.2.10 Querying the DSP Information This topic describes how to query the DSP information, such as DSP status, usage, and program type. 9.10.2.11 Querying the EVC Timeslot Occupancy This topic describes how to query the EVC timeslot occupancy. 9.10.2.12 Querying the IP Information After you log in to the device panel, you can check the information on the interface IP address and the IP address pool. The IP address pool consists of start IP address, end IP address, and subnet mask. 9.10.2.13 Querying the Modem Information This topic describes how to query Modem information. 9.10.2.14 Querying the L Interface Channel After you log in to the device panel, you can check the status of a specified channel under an L interface. An L interface has multiple channels. The operations described in this part involve all the channels between the start channel number and the end channel number. 9.10.2.15 Setting/Cancelling Board Isolation This topic describes how to set and cancel board isolation. 9.10.2.16 Blocking/Unblocking the IMA Link This topic describes how to block or unblock the IMA link. 9.10.2.17 Resetting the A2 Circuit This topic describes how to reset the A2 circuit. 9.10.2.18 Querying the ATM Port Status This topic describes how to query the ATM port status. 9.10.2.19 Querying the GCKP Clock Information This topic describes how to query GCKP clock information. 9.10.2.20 Querying the Satellite Card Information This topic describes how to query satellite card information. 9.10.2.21 Querying the GCKP Board Information This topic describes how to query the GCKP board information. 9.10.2.22 Resetting the GCKP Board This topic describes how to reset the GCKP board. 9.10.2.23 Starting the GCKP Manual Switching This topic describes how to start the GCKP manual switching. For example, upgrade the standby board first and then switch over the GCKP board to achieve the smooth upgrade.
Querying the Board Version

This topic describes how to query the board version.
Prerequisite
l l
The login user has relevant rights. The CBSC communicates with the M2000 properly.
Issue 06 (2008-12-16)
9-37
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Board Version Information. Step 4 Check the information in Query Board Version Information. Step 5 Save the query result or close the window.
l l
----End
Querying the Subsystem Status

After you log in to the device panel, you can check the operational status, management status, and active/standby status of the subsystem.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located.
Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query Subsystem Status. Step 4 Enter the subsystem number in Subsystem No. of Query Subsystem Status, and then click OK.
l
When you point to the Subsystem No. entry box, you can view the value range of Subsystem No.. If you do not type the subsystem number, use the default subsystem number, which is zero.
Step 5 Check the information in Query Subsystem Status. For details of the parameter description of subsystem status, refer to 9.11.13 Parameters for Querying the Subsystem Status. Step 6 Save the query result or close the window.
l l
----End
Related References
9.11.13 Parameters for Querying the Subsystem Status
Querying the Clock Status

This topic describes how to query the clock status.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Clock Status. Step 4 Check the information in Query Clock Status. For details of the parameter description of clock status, refer to 9.11.14 Parameters for Querying the Clock Status.
Step 5 After the query is complete, save the query result or close the window.
l l
----End
Related References
9.11.14 Parameters for Querying the Clock Status
Querying the CPU Usage

This topic describes how to query the CPU usage.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. At present, only CMUX/CBIE supports the No. 1 subsystem information. Other boards support the No. 0 subsystem.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query CPU Usage. Step 4 Type the number of the subsystem in Subsystem No. of Query CPU Usage, and then click OK.
l
When you point to the Subsystem No. entry box, you can view the value range of Subsystem No.. If you do not type the subsystem number, use the default subsystem number, which is zero.
Step 5 Check the information in Query CPU Usage. Step 6 Save the query result or close the window.
l l
----End
Querying the E1/T1 Status

This topic describes how to query the E1/T1 link status.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query E1/ T1 Status. Step 4 Enter the E1/T1 number in E1/T1 No. of Query E1/T1 Status, and then click OK.
l l l
When you point to the E1/T1 No. entry box, you can view the value range of E1/T1 No.. If no E1/T1 number is entered, all the E1/T1s on the board are queried by default. The value range of the E1/T1 number varies with the type of an interface board.
Step 5 Check the information in Query E1/T1 Status. Step 6 Save the query result or close the window.
l l
----End
Querying the A2 Circuit Status

This topic describes how to query the A2 circuit status.
Prerequisite
l l
Issue 06 (2008-12-16)
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. A signaling point can support a maximum of 4,096 circuits.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query A2 Circuit Status. Step 4 According to Parameters for querying A2 circuit status, enter parameters in Query A2 Circuit Status, and then click OK. Step 5 Check the information in Query A2 Circuit Status. Step 6 Save the query result or close the window.
l l
----End
Related References
9.11.15 Parameters for Querying the A2 Circuit Status
Querying the PCF Buffer Usage

This topic describes how to query PCF buffer occupancy.
Prerequisite
l l
Context
Procedure

l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query PCF Buffer Occupancy. Step 4 Check the information in Query PCF Buffer Occupancy. You can query the PCF buffer occupancy on the CBPU board and the BSC buffer occupancy on the CPPU board. For details of the parameter description of buffer occupancy, refer to 9.11.16 Parameters for Querying the PCF Buffer Usage. Step 5 Save the query result or close the window.
l l
----End
Related References
9.11.16 Parameters for Querying the PCF Buffer Usage
Querying the FE Link Status

This topic describes how to query the FE link status.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. If the FE link is set to Auto-negotiation Enable, you must ensure that the peer port connected by the port of the link is operational before you query the FE link status for the first time. Otherwise, the system displays
Link Not Configured
.
l
The FE link status information to be queries consists of:

Link configuration status Link status Whether the optical port is available Actual operational status of the link Link rate Link duplex mode Whether the link is auto-negotiated
Issue 06 (2008-12-16)

Link loopback mode Link traffic mode Interface type at the system side Verification type BURST length
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query FE Link Status. Step 4 Enter the FE port number in Port No. of Query FE Link Status, and then click OK.
l l
When you point to the Port No. entry box, you can view the value range of Port No.. If no FE port number is entered, you can infer that all the FE links configured by the BAM at the slot are queried.
Step 5 Check the information in Query FE Link Status. The FE link is available only when the link status is Link Activated and the link running status is In Service. Step 6 Save the query result or close the window.
l l
----End
Querying the IMA Link Status

After you log in to the device panel, you can check online the near-end and far-end IMA link status. By checking the status, you can know whether the IMA link is configured and whether the near end and the far end can receive information.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query IMA Link Status. Step 4 Enter the IMA link number in E1 No. of Query IMA Link Status, and then click OK.
l l
When you point to the E1 No. entry box, you can view the value range of E1 No.. A type of interface board has a unique value range.
Step 5 Check the information in Query IMA Link Status. Step 6 Save the query result or close the window.
l l
----End
Querying the DSP Information

This topic describes how to query the DSP information, such as DSP status, usage, and program type.
Prerequisite
l l
Context
Procedure
l l
Step 3 Check the DSP status.
CAUTION
Do not perform the operation when the DSP is loaded. 1. 2. In the displayed device panel, select a board. Right-click the board, and then choose Query DSP Status. Enter the DSP number in DSP No. of Query DSP Status, and then click OK.
l
By default, the CFMR has 8 DSPs, which are numbered from 0 to 7. The CEVC has 16 DSPs, which are numbered from 0 to 15. When you point to the DSP No. entry box, you can view the value range of DSP No.. If no DSP number is typed, you can infer that the status of all the DSPs on the board is queried.
l l
3. 4.
Check the information in Query DSP Status. For details of the parameter description of DSP status, refer to 9.11.17 Parameters for Querying the DSP Information. Save the query result or close the window.
l l
Step 4 Check the CPU usage of the DSPs. 1. 2. In the displayed device panel, select a board. Right-click the board, and then choose Query DSP CPU Usage. Enter the DSP number in DSP No. of Query DSP CPU Usage, and then click OK.
l
By default, the CFMR has 8 DSPs, which are numbered from 0 to 7. The CEVC has 16 DSPs, which are numbered from 0 to 15. When you point to the DSP No. entry box, you can view the value range of DSP No.. If no DSP number is typed, you can infer that the CPU usage of all the DSPs on the board is queried.
l l
3.
Check the information in Query DSP CPU Usage. For details of the parameter description of the CPU usage of the DSP, refer to 9.11.17 Parameters for Querying the DSP Information. After the query is complete, save the query result or close the window.
l l
4.
Step 5 Check the type of the DSP type. 1. 2. 3. In the displayed device panel, select a board. Right-click the board, and then choose Query DSP Type. Check the information in Query DSP Type. For details of the parameter description of the DSP type, refer to 9.11.17 Parameters for Querying the DSP Information. Save the query result or close the window.
l
Click Save to save the query result as a .txt file.

9-46

l
Click Close to close the window.
----End
Related References
9.11.17 Parameters for Querying the DSP Information
Querying the EVC Timeslot Occupancy

This topic describes how to query the EVC timeslot occupancy.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query EVC Timeslot Occupancy. Step 4 In Query EVC Timeslot Occupancy, enter the DSP number in DSP No. and the DSP timeslot number in TimeSlot No.. Then click OK.
l
When you point to the DSP No. or TimeSlot No. entry box, you can view the value range of the DSP No. or TimeSlot No.. Each DSP has 16 timeslots, which are numbered from 0 to 15. The DSP number must be entered. When you do not enter the DSP timeslot number, you can infer that the occupancy of all the DSP timeslots is queried.
Step 5 Check the information in Query EVC Timeslot Occupancy. For details of the parameter description of EVC timeslot occupancy, refer to 9.11.18 Parameters for Querying the EVC Timeslot Occupancy. Step 6 After the query is complete, save the query result or close the window.
l
Click Save to save the query result as a .txt file.

Issue 06 (2008-12-16)
l
Click Close to close the window.
----End
Related References
9.11.18 Parameters for Querying the EVC Timeslot Occupancy
Querying the IP Information

After you log in to the device panel, you can check the information on the interface IP address and the IP address pool. The IP address pool consists of start IP address, end IP address, and subnet mask.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Check the information on the interface IP address. 1. 2. 3. 4. In the displayed device panel, select the CIWF board. Right-click the board, and then choose Query Interface IP Information. Enter the interface name of Interface Name in Query Interface IP Information, and then click OK. Check the information in Query Interface IP Information. Save the query result or close the window.
l l
Step 4 Check the information on the IP address pool. 1. 2. 3.

9-48
In the displayed device panel, select the CIWF board. Right-click the board, and then choose Query Pool Information. Check the information in Query Pool Information. Save the query result or close the window.

l l
----End
Querying the Modem Information

This topic describes how to query Modem information.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 Check the chip status of the Modem. 1. 2. 3. In the displayed device panel, select a board. Right-click the board, and then choose Query IWF Modem Chip. Check the information in Query IWF Modem Chip. Save the query result or close the window.
l l
Step 4 Check the chip parameters of the Modem. 1. 2. 3. In the displayed device panel, select a board. Right-click the board, and then choose Query MODEM Chip Parameter. Check the information in Query MODEM Chip Parameter. Save the query result or close the window.
l l
----End
Querying the L Interface Channel

After you log in to the device panel, you can check the status of a specified channel under an L interface. An L interface has multiple channels. The operations described in this part involve all the channels between the start channel number and the end channel number.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select the CIWF board. Right-click the board, and then choose Query L Interface Channel. Step 4 Enter the start channel number and the end channel number in Start Channel No and End Channel No of Query L Interface Channel, and then click OK. When you point to Start Channel No and End Channel No, you can see the value ranges of Start Channel No and End Channel No respectively. For details of related parameters, refer to 9.11.19 Parameters for Querying the L Interface Channel. Step 5 Check the information in Query L Interface Channel. Step 6 Save the query result or close the window.
l l
----End
Related References
9.11.19 Parameters for Querying the L Interface Channel
Setting/Cancelling Board Isolation

This topic describes how to set and cancel board isolation.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. After the isolated board or the main control board is started after being reset, the isolation status is cancelled automatically.
NOTE
The CPCU is the main control board for the CBPU, the CRMU for the CPPU and the CIWF, and the CMUX for the CEVC.
l
Before you set board isolation, the system prompts you to confirm execution. Usually, the last resource board, such as CFMR, CEVC, CBPU, and CPPU, cannot be isolated. If you try to block the last resource board non-forcedly, the system displays a failure notice suggesting that you select forced isolation. If you perform the non-forced isolation for the last available CIWF board under the same signaling point when you set board isolation, the system will display a failure notice suggesting that this is last available CIWF board. If the CFMR, CEVC, CBPU, and CPPU boards are isolated, new calls are assigned to and handled on another board of the same type that is not isolated in the same subrack. If the CIWF board is isolated, new calls are assigned to and handled on the CIWF board that is not isolated at the same signaling point.
CAUTION
After a board is isolated, new calls cannot be connected to the board. The calls that are connected before the isolation, however, are not affected. Do not use the command unless otherwise specified.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Set Board Segregate or Cancel Board Segregate. Step 4 If you choose Set Board Segregate, you need to set related parameters. 1.
Issue 06 (2008-12-16)
Select YesNo in Forced Flag of Set Board Segregate, and then click OK.
Forced segregation means that the resource board of the same type requires segregation even if the board to be segregated is the only available board in the system. 2. In the Confirm dialog box, click OK. Step 5 Check the information in Set Board Segregate or Cancel Board Segregate. Step 6 Save the query result or close the window.
l l
----End
Blocking/Unblocking the IMA Link

This topic describes how to block or unblock the IMA link.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. If the IMA link is in the block status, you can still perform "Block IMA Link" successfully without affecting the system. If the IMA link is in the unblock status, you can still perform "Unblock IMA Link" successfully without affecting the system.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device board, select a panel. Right-click the board, and then choose Block IMA Link or Unblock IMA Link. Step 4 Enter the E1 number in E1 No. of Block IMA Link or Unblock IMA Link, and then click OK. When you point to the E1 No. entry box, you can view the value range of E1 No.. Step 5 In the Confirm dialog box, click OK. Step 6 Check the information in Block IMA Link or Unblock IMA Link. Step 7 Save the query result or close the window.

l l
----End
Resetting the A2 Circuit

This topic describes how to reset the A2 circuit.
Prerequisite
l l
Context
l l l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. The originating signaling point is configured. A signaling point can support a maximum of 4,096 circuits. After you reset the circuit that is in the block status, the circuit changes to the idle status.
CAUTION
Performing this operation may result in clearing the calls in circuits. Thus, do not perform this operation unless otherwise specified.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset A2 Circuit. Step 4 According to Table 9-5, enter parameters in Reset A2 Circuit, and then click OK. Table 9-5 Resetting parameters in the A2 circuit Parameter Name OPC
Issue 06 (2008-12-16)
Description Indicates the originating signaling point code where the A2 circuit is located.
Parameter Name Network Indicator Start Circuit No. End Circuit No.
Description Indicates the network indicator where the A2 circuit is located. Indicates the start circuit number and the end circuit number. When you point to the Start Circuit No. and End Circuit No. entry boxes, you can view the value range of the two entry boxes respectively. The start circuit number must not be greater than the end circuit number.
Step 5 Check the information in Reset A2 Circuit. Step 6 Save the query result or close the window.
l l
----End
Querying the ATM Port Status

This topic describes how to query the ATM port status.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query ATM Port Status. Step 4 Enter the subslot number and the slot number respectively in Sub Slot No. and Slot No. of Query ATM Port Status, and then click OK. When you point to the Sub Slot No. and Slot No. entry boxes, you can view the value range of the two entry boxes respectively.
Step 5 Check the information in Query ATM Port Status. Step 6 Save the query result or close the window.
l l
----End
Querying the GCKP Clock Information

This topic describes how to query GCKP clock information.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select the CIWF board. Right-click the board, and then choose Query GCKP Clock Information. Step 4 Check the information in Query GCKP Clock Information. Step 5 Save the query result or close the window.
l l
----End
Querying the Satellite Card Information

This topic describes how to query satellite card information.
Prerequisite
l l
Issue 06 (2008-12-16)
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Satellite Card Information. Step 4 Check the information in Query Satellite Card Information. Step 5 Save the query result or close the window.
l l
----End
Querying the GCKP Board Information

This topic describes how to query the GCKP board information.
Prerequisite
l l
Context
Procedure
l l
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query GCKP Card Information. Step 4 Check the information in Query GCKP Card Information. Step 5 Save the query result or close the window.
l l
----End
Resetting the GCKP Board

This topic describes how to reset the GCKP board.
Prerequisite
l l
Context
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset GCKP Card. Step 4 In the displayed Confirm dialog box, click OK. Step 5 Check the information in Reset GCKP Card. Step 6 Save the query result or close the window.
l l
----End
Starting the GCKP Manual Switching

This topic describes how to start the GCKP manual switching. For example, upgrade the standby board first and then switch over the GCKP board to achieve the smooth upgrade.
Prerequisite
l l
Context
l l
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel. This operation supports the upgrade between specified versions. That is, switchover commands are used to upgrade some versions. Before the upgrade, you should contact Huawei technical support engineers and ensure that software is loaded from the BAM. During normal operation, ensure that the same programs are loaded on both the active board and the standby board. When service capability decreases, perform this operation if you are certain of clock signal problems. Before the switchover, ensure that the original standby GCKP board is adjusted to use the same clock source as the original active board does. In addition, ensure that the clock source works properly.
Procedure
l l
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated is located. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Start GCKP Manual Switching. Step 4 In the Confirm dialog box, click OK. Step 5 Check the information in Start GCKP Manual Switching. Step 6 Save the query result or close the window.
l l
----End
9.10.3 Maintaining CBTS

The topic describes how to maintain the CBTS. 9.10.3.1 Downloading/Activating the BTS Software or Data This topic describes how to download or activate the BTS software or data. 9.10.3.2 Blocking/Unblocking the BTS CPM Board
Block types consist of immediate block, delay block, and idle block. Unblock has only one type, that is, immediate unblock. You can block or unblock the BTS CPM board by selecting the block or unblock BTS CPM board function. 9.10.3.3 Querying the Current Time of a BTS This topic describes how to query the current time of a BTS. 9.10.3.4 Querying a BTS Ethernet IP This topic describes how to query the Ethernet IP address of the BTS. 9.10.3.5 Querying the FE Port Information This topic describes how to query the configuration information and the status information about the FE port on the BCIM board. 9.10.3.6 Querying the Fiber Length This topic describes how to query the fiber length between the host subrack and the ODU. 9.10.3.7 Resetting a BTS When a BTS works improperly, you can reset the BTS on the device panel. This topic describes how to reset a BTS. 9.10.3.8 Maintaining Environment Monitoring Unit When maintaining environment monitoring units, you can query the EMUA information, temperature range, humidity range, extended port, and alarms. In addition, you can reset the EMUA. 9.10.3.9 Maintaining Power Management Unit When maintaining power management units, you can query the PMU version information, alarm threshold, battery parameters, and alarm definition. 9.10.3.10 Maintaining Power Supply Unit (DC/DC) When maintaining DC power supply units, you can query power the power parameters and alarms of the PSU (DC/DC) and refresh the alarms of the PSU (DC/DC).
Downloading/Activating the BTS Software or Data

This topic describes how to download or activate the BTS software or data.
Prerequisite
l l l
The login user has relevant rights. You have logged in to the M2000 client. NEs communicate with the M2000 properly.
Context
Issue 06 (2008-12-16)
9-59
NOTE
l l l
There are two activation modes: automatic and manual. If the board ID for automatic activation is not selected, the software or data is only loaded but not activated for the BTS. The service and maintenance of the BTS are not affected if the software or data is not activated. Software activation may result in the reset of corresponding boards and interruption of service. The activation of configuration data or INI files does not reset the BTS, but changes the configuration of the BTS according to the configuration of the activation file. The impact on the service varies with the configuration files.
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Download BTS Software or Data or Activate BTS Software or Data. 1. When you choose Download BTS Software or Data, the Download BTS Software or Data dialog box is displayed. a. b. c. 2. Enter or select related information in BTS ID, Object Type, Software Type, and ID of Board To be Auto-activate. Click OK to view the Confirm dialog box. Click OK to upgrade the BTS. For details of the parameters, refer to 9.11.20 Parameters for Downloading the BTS Software or Data.
When you choose Download BTS Software or Data, the Download BTS Software or Data dialog box is displayed. a. b. c. Enter or select related information in BTS ID, Board ID, Object Type, and Software Type. Click OK to view the Confirm dialog box. Click OK to upgrade the BTS. For details of the parameters, refer to 9.11.20 Parameters for Downloading the BTS Software or Data.
----End
Related References
9.11.20 Parameters for Downloading the BTS Software or Data
Blocking/Unblocking the BTS CPM Board

Block types consist of immediate block, delay block, and idle block. Unblock has only one type, that is, immediate unblock. You can block or unblock the BTS CPM board by selecting the block or unblock BTS CPM board function.
Prerequisite
l l l
Context
CAUTION
l
Blocking the BTS CPM may cause multiple sector carriers to be deleted and interrupt the service borne by this CPM. Perform this operation only when necessary. Calls cannot be connected in the case of "Delay block" or "Idle block".
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Block BTS CPM Board or Unblock BTS CPM Board. 1. When you choose Block BTS CPM Board, the Block BTS CPM Board dialog box is displayed. a. b. c. 2. Enter values in BTS ID and Board ID, and then select Block Type from the dropdown list. Click OK to view the Confirm dialog box. Click OK to block the board. For details of related parameters, refer to 9.11.21 Parameters for Blocking the BTS CPM Board.
When you choose Unblock BTS CPM Board, the Unblock BTS CPM Board dialog box is displayed. a. b. Enter values in BTS ID and Board ID. Click OK to unblock the board. For details of related parameters, refer to 9.11.21 Parameters for Blocking the BTS CPM Board.
----End
Related References
9.11.21 Parameters for Blocking the BTS CPM Board
Querying the Current Time of a BTS

This topic describes how to query the current time of a BTS.
Prerequisite
l l l
Context
NOTE
If any of the following situations occurs, "2000-01-01 00:00:00" is reported.

l l
The BTS clock is not started. The BTS clock does not apply for the time of the BAM, and the BTS GPS receiver does not lock the satellite succesfully.
If the BTS GPS receiver succeeds in locking the satellite, the returned time is synchronized with the GPS time. In this case, there may be some differences between the GPS time and the BAM time.
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Current Time of BTS. The Query Current Time of BTS dialog box is displayed. The local UTC time of the BTS is displayed at the BTS Current Time parameter line. ----End
Querying a BTS Ethernet IP

This topic describes how to query the Ethernet IP address of the BTS.
Prerequisite
l l l
9-62
Context
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Ethernet IP. The Query Ethernet IP dialog box is displayed. For details of the parameters in the dialog box, refer to 9.11.22 Parameters for Querying the BTS Ethernet IP. At the Local O&M IP parameter line, the IP address of the BTS is displayed. At the Reverse Maintenance Status parameter line, the inverse maintenance status is displayed. ----End
Related References
9.11.22 Parameters for Querying the BTS Ethernet IP
Querying the FE Port Information

This topic describes how to query the configuration information and the status information about the FE port on the BCIM board.
Prerequisite
l l l
Context
Procedure
l
Choose Configuration > Device Map.

Issue 06 (2008-12-16)
l
Right-click an NE node in the physical topology navigation tree or the physical topology view, and then choose Device Panel from the displayed shortcut menu.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query FE Port Information. The Query FE Port Information dialog box is displayed. For details of the parameters in the dialog box, refer to 9.11.23 Parameters for Querying the FE Port Information. ----End
Related References
9.11.23 Parameters for Querying the FE Port Information
Querying the Fiber Length

This topic describes how to query the fiber length between the host subrack and the ODU.
Prerequisite
l l l
Context
NOTE
The queried filber length refers to the actual length between the primary rack and the ODU.
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query Fiber Length. ----End
Resetting a BTS
When a BTS works improperly, you can reset the BTS on the device panel. This topic describes how to reset a BTS.
Prerequisite
l l l
Context
CAUTION
Resetting the BTS may affect services. Thus, you should reset the BTS with caution.
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Reset BTS. The Reset BTS dialog box is displayed. Step 4 In the BTS ID entry box, enter the ID of the BTS. Step 5 Click OK. The Confirm dialog box is displayed. Step 6 Click OK to start resetting the BTS. When you invoke the CORBA interface to reset the board, a dialog box is displayed to show the result.
l
If the board is reset successfully, the system displayed a dialog box to notify you of the successful result. If the board fails to be reset, the system displays specific reasons. The reasons may be that you click Cancel to disrupt the resetting process or that CORBA fails to be invoked.
----End
Maintaining Environment Monitoring Unit

When maintaining environment monitoring units, you can query the EMUA information, temperature range, humidity range, extended port, and alarms. In addition, you can reset the EMUA.
Prerequisite
l l l
Context
The maintenance of environment monitoring units is only applicable for the EMUA board.
CAUTION
Resetting the environment monitoring board may affect services. Thus, you should reset the EMUA with caution.
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 On the displayed device panel, right-click the EMUA board and then choose relevant items to operate and maintain the EMUA. For details on how to operate and maintain the EMUA, refer to Table 9-6. Table 9-6 Operating and maintaining the EMUA Operation Query Board Information Query EMUA Temperature Range Set EMUA Temperature Range Remarks On the device panel, you can invoke this operation to check the detailed information on the EMUA. On the device panel, you can invoke this operation to check the temperature range of the EMUA. On the device panel, you can invoke this operation to set the humidity range of the EMUA.
Issue 06 (2008-12-16)
9-66
Operation Query EMUA Humidity Range Set EMUA Humidity Range Query EMUA Switch Extended Port Set EMUA Switch Extended Port Query EMUA Analog Extended Port Set EMUA Analog Extended Port Reset Board Query Alarm Refresh Alarm
Remarks On the device panel, you can invoke this operation to check the humidity range of the EMUA. On the device panel, you can invoke this operation to set the humidity range of the EMUA. On the device panel, you can invoke this operation to check the switch extended port of the EMUA. On the device panel, you can invoke this operation to set the switch extended port of the EMUA. On the device panel, you can invoke this operation to check the analog extended port of the EMUA. On the device panel, you can invoke this operation to set the analog extended port of the EMUA. When the EMUA works improperly, you can invoke this operation on the device panel to reset the EMUA. On the device panel, you can invoke this operation to check the alarms of the EMUA. On the device panel, you can invoke this operation to refresh alarms of the EMUA and to obtain the latest alarm information.
----End
Maintaining Power Management Unit

When maintaining power management units, you can query the PMU version information, alarm threshold, battery parameters, and alarm definition.
Prerequisite
l l l
Context
The maintenance of power management units is applicable only for the PMU.
Procedure
l
Choose Configuration > Device Map.

Issue 06 (2008-12-16)
l
Right-click an NE node in the physical topology navigation tree or the physical topology view, and then choose Device Panel from the displayed shortcut menu.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 On the displayed device panel, right-click the PMU panel and then choose relevant items to operate and maintain the PMU. For details on how to operate and maintain the PSU, refer to Table 9-7. Table 9-7 Operating and maintaining the PSU Operation Query Board Version Information Query BTS Power Supply Unit Remarks On the device panel, you can invoke this operation to check the detailed information on the PMU. On the device panel, you can invoke this operation to check the detailed information on the AC/DC power supply units of the BTS. On the device panel, you can invoke this operation to check the mains alarm threshold. On the device panel, you can invoke this operation to set the mains alarm threshold. On the device panel, you can invoke this operation to check the parameters of BTS storage batteries. On the device panel, you can invoke this operation to set the parameters of BTS storage batteries. On the device panel, you can invoke this operation to check the alarm threshold of environment temperature. On the device panel, you can invoke this operation to set the alarm threshold of environment temperature. On the device panel, you can invoke this operation to check the alarm threshold of environment humidity. On the device panel, you can invoke this operation to set the alarm threshold of environment humidity. On the device panel, you can invoke this operation to check the alarm information on the PMU environment monitoring extended port. On the device panel, you can invoke this operation to set the alarm information on the PMU environment monitoring extended port.
Query AC Alarm Threshold Set BTS AC Alarm Threshold Query BTS Battery Parameter Set BTS Battery Parameter Query BTS Environment Temperature Alarm Threshold Set BTS Environment Temperature Alarm Threshold Query BTS Environment Humidity Alarm Threshold Set BTS Environment Humidity Alarm Threshold Query the Alarm Information of the PMU Environment Monitoring Extended Port Set the Alarm Information of the PMU Environment Monitoring Extended Port ----End
9-68
Issue 06 (2008-12-16)
Maintaining Power Supply Unit (DC/DC)

When maintaining DC power supply units, you can query power the power parameters and alarms of the PSU (DC/DC) and refresh the alarms of the PSU (DC/DC).
Prerequisite
l l l
Context
The maintenance of DC power supply units is applicable only for the PSU (DC/DC).
Procedure
l l
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in the right part of the window. Step 3 On the displayed device panel, right-click the PSU (DC/DC) and then choose relevant items to operate and maintain the PSU (DC/DC). For details on how to operate and maintain the PSU (DC/DC), refer to Table 9-8. Table 9-8 Operating and maintaining the PSU (DC/DC) Operation Query Power Supply Parameters Query Alarm Refresh Alarm Remarks On the device panel, you can invoke this operation to check the parameters of power supplies. On the device panel, you can invoke this operation to check the alarms of the PSU (DC/DC). On the device panel, you can invoke this operation to refresh the alarms of the PSU (DC/DC) and to obtain the latest alarm information.
----End
9.11 Reference for Configuration Management Interfaces

This topic describes the interface of configuration management and related reference information. The interface and reference information include the MML command interface, follow-up message browser interface, and parameter information involved in the configuration management.
9.11.1 Interface Description: MML Command This part describes the MML Command interface, which helps you know the functions of the interface. 9.11.2 Interface Description: Follow-Up Reports Browser This part describes the follow-up reports browser, which helps you know the functions of this interface. 9.11.3 Interface Description: MIT Browsing This describes the composition and function of the MIT Browsing interface. 9.11.4 Interface Description: Inventory Management This describes the composition and function of the inventory management interface. 9.11.5 Interface Description: Device Panel This topic describes the window of the GBSS device panel so that you can understand the function of each part in the window of the CBSS device panel. 9.11.6 Parameters for Monitoring NE Resource States in Real Time This part introduces the parameters for monitoring the NE resources in real time. 9.11.7 Parameters for Setting the Attributes of the MML Command Interface This part describes parameters for configuring the MML command client. 9.11.8 Parameters for NE MIT Information This part describes the parameters for querying NE configuration. 9.11.9 Parameters for NE Resource Report This part describe the parameters for querying the NE resource status. 9.11.10 Parameters for NE Statistics Report This part describes the parameters of the NE statistic report. 9.11.11 Parameters for Querying Inventory Data This part describes the parameters shown in the Condition setting dialog box. You can refer to this part when setting the conditions for searching for inventory data. 9.11.12 Parameters for Querying the Board Information This topic describes the parameters for querying the board information. 9.11.13 Parameters for Querying the Subsystem Status This topic describes the parameters for querying the subsystem status. 9.11.14 Parameters for Querying the Clock Status This topic describes the parameters for querying the clock status. 9.11.15 Parameters for Querying the A2 Circuit Status This topic describes the parameters for querying the A2 circuit status. 9.11.16 Parameters for Querying the PCF Buffer Usage This topic describes the parameters for querying the PCF buffer usage. 9.11.17 Parameters for Querying the DSP Information this topic describes the parameters for querying the DSP information. 9.11.18 Parameters for Querying the EVC Timeslot Occupancy This topic describes the parameters for querying the EVC timeslot occupancy. 9.11.19 Parameters for Querying the L Interface Channel This topic describes the parameters for querying the L interface channel.
9.11.20 Parameters for Downloading the BTS Software or Data This topic describes the parameters for downloading the BTS software or data. 9.11.21 Parameters for Blocking the BTS CPM Board This topic describes the parameters for blocking the BTS CPM board. 9.11.22 Parameters for Querying the BTS Ethernet IP This topic describes the parameters for querying the BTS Ethernet IP address. 9.11.23 Parameters for Querying the FE Port Information This topic describes the parameters for querying the FE port information .
9.11.1 Interface Description: MML Command

This part describes the MML Command interface, which helps you know the functions of the interface. The MML Command interface on the client is shown in Figure 9-1. Figure 9-1 MML Command interface on the client
(1)NE window. All the NEs that support the delivery of MML commands are displayed on the topology view according to the topology structure of the NEs. (2)MML command navigation tree window. The MML command navigation tree of a specific NE is displayed. (3)Command output window. which has the Common Maintenance tab, Historical Commands tab, and Help Information tab. The Common Maintenance tab displays the delivered commands and command results. The Historical Commands tab lists the executed commands and their parameter configuration. The Help Information tab displays the help information of MML commands. (4)Command display window. which displays the executed commands and their parameter configuration. (5) Executed commands list which displays he all the executed MML commands and the number of commands executed on each NE. (6)Command input window. which displays Historical Command, Command Input and Command Parameter. Historical Command displays the latest 20 historical commands and the related parameter configuration.
Issue 06 (2008-12-16)
9-71
NOTE
For some MML commands, the M2000 may generated multiple reports for one MML command. In this situation, when the M2000 runs these MML commands, the Common Maintenance tab displays only the first report. You can view the remaining messages in the Follow-up Reports Browser window.
9.11.2 Interface Description: Follow-Up Reports Browser

This part describes the follow-up reports browser, which helps you know the functions of this interface. The MML Command window can display only one message. When more than one message is returned after the system delivers an MML command to an NE, you can query the other messages through the follow-up messages browser. Figure 9-2 shows the Follow-Up Reports Browser interface. Figure 9-2 Follow-Up Reports Browser Interface
(1) is an navigation tree where you can select one or more NEs. (2) is the output window of the messages. When the M2000 receives the follow-up messages returned by the selected NEs, the prompt information is displayed in the output window of messages and at the right corner of the client. (3) displays buffer file name and path of the follow-up reports. (4) are the operation buttons that you can click to save follow-up reports, clear follow-up reports, and close the window.
Related Tasks
9.2.3 Viewing Follow-Up Reports
9.11.3 Interface Description: MIT Browsing

This describes the composition and function of the MIT Browsing interface. The inventory management interface is composed of three parts, as shown in Figure 9-3. Table 9-9 describes each part.
Figure 9-3 MIT browsing interface
Table 9-9 Description of the MIT Browsing interface SN 1 Name MIT Description The MIT is structured as follows:
l l l
First-level node: NE type. For example, RNC. Level 2: specific NEs. Level 3: management object class (MOC). The node displays the object types. For example, board. Level 4: management object (MO). The node displays the specific objects. For example, board 1 and board 2.
An object is an MO of its parent node MOC. It can also have subobjects and serve as their MOC. The MIT always has not only four node levels. From the level 3 node, multiple MOCs and MOs can exist based on the NE module. 2 Search area You must press Ctrl+F to display this area. For descriptions of the parameters, refer to 9.11.8 Parameters for NE MIT Information. Displays the configuration information about the selected NE or MO.
Object informatio n
Related Concepts
Related Tasks
9.11.4 Interface Description: Inventory Management

This describes the composition and function of the inventory management interface. The inventory management interface is composed of three parts, as shown in Figure 9-4. Table 9-10 describes each part. Figure 9-4 Inventory management interface
Table 9-10 Description of the interface management interface SN 1 Name Navigation tree Description The navigation tree of the inventory management is structured as follows:
l l l
First-level node: NE type. For example, RNC. Level 2: specific NEs. Level 3: inventory object node, which is classified into physical inventory object and logical inventory object. Level 4: management object class (MOC). The node displays the object types. For example, board. Level 5: management object (MO). The node displays the specific objects. For example, board 1 and board 2.
An object is an MO of its parent node MOC. It can also have subobjects and serve as their MOC. The navigation tree usually has not only five node levels. From the level 3 node, multiple MOCs and MOs can exist based on the NE module. 2 Display area Displays the inventory data of the selected MO.
9-74
Issue 06 (2008-12-16)
SN 3
Name Synchroniz ation progress list
Description Displays the progress of inventory data synchronization and the related information.
Related Tasks
9.5 Managing Inventory Data
9.11.5 Interface Description: Device Panel

This topic describes the window of the GBSS device panel so that you can understand the function of each part in the window of the CBSS device panel. Figure 9-5 shows the client window of the GBSS device panel. Figure 9-5 Client window of the GBSS device panel
(1) NE window. The window displays all the NEs of the CBSS in topology according to the topology structure of the CBSS. (2) Device panel window. The window displays the status of all the boards on the rack specified by the CBSS. (3) Fault bar. The fault information on the board is listed and rolled on the fault bar. (4) Legend window. The window displays the meanings of board colors and icons on the device panel.
Related Concepts
Related Tasks
9.10 Operating CBSS Device
9.11.6 Parameters for Monitoring NE Resource States in Real Time

This part introduces the parameters for monitoring the NE resources in real time. Table 9-11 lists descriptions of the parameters for real-time monitoring of NE resources. Table 9-11 Descriptions of the parameters for real-time monitoring of NE resources Parameter ID Monitor Status Description Whether the status of a resource is monitored, which includes:
l l
Enable. Disable.
Effect Status
Validity of a resource status monitoring task, which includes:

l l
Effective: The monitoring task is in the Started state. Noneffective: The monitoring task is in the Stopped state. The monitoring task is in this state when it failed to be executed because of communication failures with the NE. Invalid: The monitoring task is in the Suspended state.
Name NE Name Specific resource object state
Name of a queried resource object. NE to which the queried resource object belongs. The state of a resource object is visible only when it is started. The states vary depending on the types of the resource objects. For details, refer to 9.1.3 NE Resource States.
Related Tasks
9.6.2 Monitoring NE Resource States in Real Time
9.11.7 Parameters for Setting the Attributes of the MML Command Interface
This part describes parameters for configuring the MML command client. Table 9-12 lists the descriptions of the parameters for configuring MML command client.
9-76
Issue 06 (2008-12-16)
Table 9-12 Descriptions of the parameters for configuring MML Command Client Parameter Max History Commands Value range 10-1000 Default value: Description The number of history commands displayed in History Command in the right part of the MML Command dialog box. When the number of history commands exceeds this value, the client displays only the commands executed recently. Max Report Lines 100-20000 Default value: Maximum lines of the output the screen displays in the Common Maintenance tab for an MML command. When lines of the output messages exceed this value, the client displays only the output messages reported recently. Max Log file Size (MB) 20-50 Default value: The size of the reports redirection file. When the size of the redirection file reaches this value, the system creates automatically a new file under the same directory to save the received messages. The file is named YYYYMMDD.TXT. YYYY, MM and DD are respectively the current year, month and date. Max Report Buffer Size (MB) 1-5 Default value: The size of the MML command output messages to be displayed in Common Maintenance. When the size of the output messages exceeds this value, the client displays only those generated recently.
NOTE When the messages saved in the system nearly accounts for 70% of the Max Report Buffer Size set by the user, a warning is displayed, prompting you to clear up memories. If the amount of messages saved in the system already reach the preset Max Report Buffer Size,the system prompts you to clear the messages.
the system forces you to clear up memories.
Command Display Explain
Command sequence
Sort: Sort the commands in the drop-down list behind Command Input alphabetically. If you do not select this, the MML commands in the drop-down list behind Command Input are sorted according to the sequence in the configuration file.
Default value:
Explain: Select whether to display the command description in the text box behind Command Input.
Issue 06 (2008-12-16)
9-77
Parameter Operation Mode
Value range
l l
Description
l
Script Mode Multiwindow Mode
If you select Script mode, the selected commands are not delivered to the NE. Instead, they are used for creating script tasks. If you do not select this mode, the selected commands are delivered to the NE. If you select Multiwindow Mode, you can open up to three MML Command windows at the same time. If the parameter setting is changed, you need to open the MML Command window again.
General
Step into
Step into:
l
If you select this parameter, the system executes the commands one by one. If not, the system executes the commands in batch.
Related Tasks
9.2.4 Setting the Attributes of the "MML Command" Interface
9.11.8 Parameters for NE MIT Information

This part describes the parameters for querying NE configuration. Table 9-13 lists descriptions of the parameters for querying NE configuration. Table 9-13 Parameters for querying NE configuration Parameter Key words Value The name should not be null. It is composed of up to 64 characters, excluding special characters such as `, -, !, @, #, $, %, ^, &, *, +, \, |, ;, ', :, ", , , ., ?, /, and the Chinese dash.
l l
Description The characters contained in the name of the configuration object to be searched.
Match Case
Selected: case sensitive. Cleared: case insensitive.
The key words entered for searching are case sensitive. Name of a found node. Hierarchy of resource objects in the MIT navigation tree.
Node name Node path
Name of an existing resource object. //Node name/Node name/...
Related Concepts
9-78
Issue 06 (2008-12-16)
Related Tasks
9.11.9 Parameters for NE Resource Report

This part describe the parameters for querying the NE resource status. Table 9-14 lists the descriptions of parameters for querying the resource status of the NEs. Table 9-14 Parameters for querying the resource status of the NEs Parameter ID Name NE name Monitor Status Description Name of the queried resource object. NE to which the queried resource objects belong. Indicates whether a resource object is being monitored. The Monitor Status and be Enableor Disable.
Related Concepts
Related Tasks
9.6.1 Viewing NE Resource States 9.6.2 Monitoring NE Resource States in Real Time
9.11.10 Parameters for NE Statistics Report

This part describes the parameters of the NE statistic report. Table 9-15 lists descriptions of the parameters in the NE statistic report. Table 9-15 Descriptions of the parameters in the NE statistic report Parameter NE Type NE Version NE Sum Description Type of an NE. Refer to 3.3.1 NE Type. Version of an NE. Number of versions of a selected NE.
Related Tasks
9.3.4 Viewing NE Statistics Reports
9.11.11 Parameters for Querying Inventory Data

This part describes the parameters shown in the Condition setting dialog box. You can refer to this part when setting the conditions for searching for inventory data.
Parameter Moc Type Description Specific inventory objects.
l
Logical inventory objects include cells, and software or patches. Only the RNC, BSC, and CBSC support the management of cells. Physical inventory objects include subracks, frames, slots, boards, ports, and antennas. Only the CBTS, BTS, and NodeB support the management of antennas.
Attribute Operator
Attribute of inventory object instances. For example, NE ID, cabinet number, and slot location. The relation between the attribute values of the inventory object instances. You need select the operator, such as >, <, =, >=, and <= from the drop-down list.
Value Relation
Attribute value of the inventory object instance. The relation between the search conditions. You need select the relation, that is, AND and OR from the drop-down list.
Sort
Keywords Asc Dec
Sorts the search results in descending or ascending order by the key words.
Example of Condition Setting

Figure 9-6 shows how to set search conditions. Figure 9-7 show the search results.
9-80
Issue 06 (2008-12-16)
Figure 9-6 Setting search conditions
Issue 06 (2008-12-16)
9-81
Figure 9-7 Search results
Related Tasks
9.5.2 Querying Inventory Data
9.11.12 Parameters for Querying the Board Information

This topic describes the parameters for querying the board information. For details of the parameters for querying the board information, refer to Table 9-16.
NOTE
The displayed parameters after the query vary with NE versions.
Table 9-16 Parameters for querying the board information Parameter Name Frame No. Slot No. Board Type Operational Status Management Status Description Number of the frame where the board is located Number of the slot where the board is located Type of the board If the operational status is activated, you can infer that the board operates properly. If the operational status is not activated, you can infer that the board is faulty. If the management status is activated, you can infer that the board can be managed. If the management status is deactivated, you can infer that the board cannot be managed. After the board is isolated, the management status of the board is deactivated.
9-82
Issue 06 (2008-12-16)
Parameter Name Active/Standby Status ATM Bus Port Subsystem Software Version No. BIOS Software Version No. PCB Version No. CPLD Hardware Logic Version No.
Description Active and standby status of the board Number of the ATM bus port Number of the subsystem software version
Version number of BIOS software Version number of PCB Logic version number of CPLD hardware
Related Tasks
9.10.1.1 Querying the Board Information
9.11.13 Parameters for Querying the Subsystem Status

This topic describes the parameters for querying the subsystem status. For details of the parameters for querying the subsystem status, refer to Table 9-17.
NOTE
Table 9-17 Parameters for querying the subsystem status Parameter Name Board Type Subsystem No. Description Type of the board Generally, a board has only the default subsystem number as 0. Currently, only CMUX and CBIE support the query of the subsystem whose number is 1. If the operational status is activated, you can infer that the board operates properly. If the operational status is not activated, you can infer that the board is faulty. If the management status is activated, you can infer that the board can be managed. If the management status is deactivated, you can infer that the board cannot be managed. After the board is isolated, the management status of the board is deactivated.
Operational Status Management Status
Issue 06 (2008-12-16)
Parameter Name Active/Standby Status Subsystem Software Version No. BIOS Software Version No. PCB Version No. CPLD Hardware Logic Version No. FPGA Hardware Logic Version No. Finished Board Version No.
Description Active and standby status of the board Version number of subsystem software
Version number of BIOS software Version number of PCB Logic version number of CPLD hardware
logic version number of FPGA hardware
Version number of a finished board
Related Tasks
9.10.2.2 Querying the Subsystem Status
9.11.14 Parameters for Querying the Clock Status

This topic describes the parameters for querying the clock status. For details of the parameters for querying the clock status, refer to Table 9-18.
NOTE
The displayed parameters after the query vary with board types or NE versions.
9-84
Issue 06 (2008-12-16)
Table 9-18 Parameters for querying the clock status Board Model CMUX Clock Information This command can be used to query the current status of the clock reference sources of the CMUX. As the main control board, the CMUX provides the 32 MHz/8 kHz clock for the boards in the subrack. The clock reference source, which serves as the reference clock of the CMUX, provides the 32 MHz/8 kHz clock. An appropriate clock reference source can be selected according to the current status of the reference sources and actual requirements. The CMUX can select the following clock reference sources:
l
Two TDM 8 kHz clock reference sources (E1 line clock) provided by CBIE/ CXIE/CAIE One 8 kHz clock reference source (line clock of ATM switch optical port) provided by the local optical port Two SDH 8 kHz clock reference sources provided by the CSTU One 8 kHz clock reference source provided by the local crystal oscillator; one 8 kHz clock reference clock provided by the GCKP
l l
CBIE/ CXIE
The CXIE/CBIE provides two 2 MHz reference clocks through the board panel and two 8 kHz clocks through the back board. Using this operation, you can know whether these clocks are enabled or disabled. The query result includes the selection situation of the IMA clock source. The result also includes the status of 32 MHz and 8 kHz clocks exported to the CBIE/CXIE from the CMUX.
CAIE/ CBIE/ CXIE CFMR CEVC/ CLAP CSPU
The clock status information that can be queried for the CAIE is the same as that for the CBIE and the CXIE. The only difference is that the CAIE does not have the IMA clock source. The purpose of querying the clock status of the CFMR is to check whether the 32 MHz/8 kHz clocks, internal clocks, and RFN clocks work properly. The purpose of querying the clock status of the CEVC/CLCB is to check whether the 32 MHz/8 kHz external clocks work properly. The purpose of querying the CSPU is to check whether there is any fault with 8 kHz clock and whether the status of RFN pulses and RFN synchronization information elements is proper. The purpose of querying CPPU/CBPU/CPCU/CRMU boards is to check whether there is any fault with the 8 kHz clock.
CPPU/ CBPU/ CPCU/ CRMU
Issue 06 (2008-12-16)
9-85
Board Model CSTU
Clock Information Querying the CSTU involves querying the status of CSTU SDH Clock Source, Returned SDH8K Clock Source, Returned TDM8K Clock Source, and Returned Clock Group.
l
CSTU SDH Clock Source can be 8 kHz optical port clock, TDM 32 MHz clock, or SDH 19.44 MHz clock. Returned SDH8K Clock Source must be 8 kHz optical port clock. Returned TDM8K Clock Source can be OUT_CLK_FMR2M1, OUT_CLK_FMR2M2, OUT_CLK_FMR2M3, OUT_CLK_FMR2M4, OUT_CLK_FMR2M5, OUT_CLK_FMR2M6, OUT_CLK_FMR2M7, or OUT_CLK_FMR2M8. Returned Clock Group can be 0 (group 1) or 1 (group 2).
l l
Related Tasks
9.10.2.3 Querying the Clock Status
9.11.15 Parameters for Querying the A2 Circuit Status

This topic describes the parameters for querying the A2 circuit status. For details of the parameters for querying A2 circuit status, refer to Table 9-19.
NOTE
Table 9-19 Parameters for querying A2 circuit status Parameter Name OPC Network Indicator Start Circuit No. End Circuit No. Description Indicates the originating signaling point code where the A2 circuit is located. Indicates the network indicator where the A2 circuit is located. Indicates the start circuit number and the end circuit number. When you point to the Start Circuit No. and End Circuit No. entry boxes, you can view the value range of the two entry boxes respectively. The start circuit number must not be greater than the end circuit number. The number of circuits for each operation cannot exceed 256.
Related Tasks
9.10.2.6 Querying the A2 Circuit Status
9.11.16 Parameters for Querying the PCF Buffer Usage

This topic describes the parameters for querying the PCF buffer usage.
For details of the parameters for querying PCF or BSC buffer usage, refer to Table 9-20.
NOTE
Table 9-20 Parameters for querying PCF or BSC buffer usage Parameter Name Buffer Occupancy Buffer Type Description Indicates the usage of buffer. The unit is %. The buffer type can be PCF or RAC.
Related Tasks
9.10.2.7 Querying the PCF Buffer Usage
9.11.17 Parameters for Querying the DSP Information

this topic describes the parameters for querying the DSP information. For details of the parameters for querying the DSP information, refer to Table 9-21.
NOTE
Table 9-21 Parameters for querying the DSP information Parameter Name DSP No. DSP Status Description Type of the board The DSP status can be queried even if the DSPs are faulty. The DSP status cannot be queried only when the board cannot communicate with the BAM. If the DSP functions well, the DSP status is displayed as "working properly". CPU Usage When DSP resources are not used, the CPU usage of the DSP on the CFMR is not zero by default. The CPU usage of the DSP on the CEVC is zero by default. If other value except the default value is queried, you can infer that services are operational on the DSP. If the DSP is in the loaded or faulty state, the CPU usage of the DSP cannot be queried. DSP Type Type of the DSP
Related Tasks
9.10.2.10 Querying the DSP Information
9.11.18 Parameters for Querying the EVC Timeslot Occupancy

This topic describes the parameters for querying the EVC timeslot occupancy.
For details of the parameters for querying the EVC timeslot occupancy, refer to Table 9-22.
NOTE
Table 9-22 Parameters for querying the EVC timeslot occupancy Parameter Name DSP No. Timeslot No. Management Status Operation Status Description Number of the DSP Each DSP has 16 timeslots, which are numbered from 0 to 15. Block: management status; timeslots cannot be used Unblock: management status; timeslots can be used Faulty: The DSP is not loaded or has physical faults. Idle: Timeslot resources can be used. Busy: Timeslots are occupied because calls are carried out in the timeslots.
Related Tasks
9.10.2.11 Querying the EVC Timeslot Occupancy
9.11.19 Parameters for Querying the L Interface Channel

This topic describes the parameters for querying the L interface channel. For details of the parameters for querying the L interface channel, refer to Table 9-23.
NOTE
Table 9-23 Parameters for querying the L interface channel Parameter Name Start Channel No. End Channel No. Description Indicates the start number of the L channel to be queried. Indicates the end number of the L channel to be queried.
Related Tasks
9.10.2.14 Querying the L Interface Channel
9.11.20 Parameters for Downloading the BTS Software or Data

This topic describes the parameters for downloading the BTS software or data. For details of the parameters for downloading the BTS software or data, refer to Table 9-24.
Table 9-24 Parameters for downloading the BTS software or data Symbol BTSNAM E Parameter Name BTS Name Description String parameter Name of the BTS Maximum length: 30 BTSID BTS ID Numeric parameter BTS ID assigned by the BSC OBJTP SOFTTP BRDID Object Type Software Type Board ID Type of the object Type of the software Numeric parameter. ID of the board to be auto-activated. If this parameter is not entered, the software or data is downloaded but not activated. Numeric parameter. Mode for activating the software.
ACTM
Software Activation Mode
Related Tasks
9.10.3.1 Downloading/Activating the BTS Software or Data
9.11.21 Parameters for Blocking the BTS CPM Board

This topic describes the parameters for blocking the BTS CPM board. For details of the parameters for blocking the BTS CPM board, refer to Table 9-25. Table 9-25 Parameters for blocking the BTS CPM board Symbol BTSNAME Parameter Name BTS Name Description String parameter Name of the BTS Maximum length: 30 BTSID BTS ID Numeric parameter BTS ID assigned by the BSC BRDID CPM ID Numeric parameter ID of the CPM BLKTP Block Type Numeric parameter Type of the block
Issue 06 (2008-12-16)
9-89
Symbol DLYTM
Parameter Name Time Delayed
Description Numeric parameter Delay time unit: second. This parameter is mandatory when the block type is delay block.
Related Tasks
9.10.3.2 Blocking/Unblocking the BTS CPM Board
9.11.22 Parameters for Querying the BTS Ethernet IP

This topic describes the parameters for querying the BTS Ethernet IP address. For details of the parameters for querying the BTS Ethernet IP address, refer to Table 9-26. Table 9-26 Parameters for querying the BTS Ethernet IP address Symbol BTSNAME Parameter Name BTS Name Description String parameter Name of the BTS Maximum length: 30 BTSID BTS ID Numeric parameter BTS ID assigned by the BSC
Related Tasks
9.10.3.4 Querying a BTS Ethernet IP
9.11.23 Parameters for Querying the FE Port Information

This topic describes the parameters for querying the FE port information . For details of the parameters for querying the FE port information, refer to Table 9-27. Table 9-27 Parameters for querying the FE port information Symbol BTSNAM E Parameter Name BTS Name Description String parameter Name of the BTS Maximum length: 30 BTSID BTS ID Numeric parameter BTS ID assigned by the BSC BRDID BCIM ID Numeric parameter BCIM number of the FE port to be queried
Symbol PORTID
Parameter Name FE port ID
Description Numeric parameter FE port number to be queried. If the parameter value is not specified, the information on all the FE ports of the specified BCIM is queried.
Related Tasks
9.10.3.5 Querying the FE Port Information
Issue 06 (2008-12-16)
9-91
10 Data Management
10
About This Chapter
Data Management
The M2000 manages both NE data and NM data. The management of NM data covers manually or periodically backing up NM data, and viewing NM backup files. The management of NE data covers manually or periodically backing up NE data, viewing NE backup files, restoring NE data, and collecting network optimization data. The M2000 also provides the function of collecting NM log files. 10.1 Basic Knowledge of Data Management Before you perform the data management, you need be familiar with the basic information of data management, such as NM backup data, NE backup data, and NM log files. This helps you understand the contents of data management. 10.2 NE Backup Data You can back up the NE data in two ways: the periodic backup and the manual backup. When a backup task is performed, a backup file is generated on the M2000 server, regardless of the manual or periodic backup. Then you can restore the NE data through these backup files when required. 10.3 NM Backup Data M2000You can back up the NM data in two ways: periodic backup and manual backup. When a backup task is performed, a backup file is generated on the M2000 server, regardless of the manual or periodic backup. Then you can restore the data through these backup files if required. 10.4 Collecting Network Optimization Data You can collect the analysis data required by network planning and optimization through the M2000. The data collected by M2000 involves the neighbor cell optimization data and the uplink ARFCN data. The collected data is stored in the designated directory of the M2000 server. Network engineers use such data to analyze the neighbor cell and the uplink ARFCN through the Nastar. The neighbor cell optimization data is stored in opt/OMC/var/fileint/other/ adjacentCell, whereas the uplink ARFCN data is stored in opt/OMC/var/fileint/other/ ne<fdn>/frqlog. The neighbor cell optimization data refers to the performance data and configuration data of a cell. It shows the configurations of the neighbor cell. Uplink ARFCN data refers to the uplink level of a frequency. It shows the received signal strength of a frequency. 10.5 Collecting NM Log File When the M2000 client or server cannot run properly, you can collect all the running information from the M2000 client and server to locate faults.
10 Data Management
10.6 Reference for Data Management Interfaces This part describes the data management interface, which consists of the backup management interface and the log information collector interface, and the parameters used in NE or NM data backup. This helps you understand the functions of data management.
10-2
Issue 06 (2008-12-16)
10 Data Management
10.1 Basic Knowledge of Data Management

Before you perform the data management, you need be familiar with the basic information of data management, such as NM backup data, NE backup data, and NM log files. This helps you understand the contents of data management. 10.1.1 NM Backup Data The M2000 provides the function of backing up NM data. Using this function, you can back up the partial configuration files on the M2000 server, and dynamic data during the running of the system. 10.1.2 NE Backup Data The M2000 provides the function of NE data backup. Therefore, you can back up the configuration files of all NEs managed by the M2000 and the files that change dynamically during the operation. 10.1.3 NM Log Data When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic information from the M2000 Server and Client through the FTP protocol.
10.1.1 NM Backup Data

The M2000 provides the function of backing up NM data. Using this function, you can back up the partial configuration files on the M2000 server, and dynamic data during the running of the system.
l l
M2000You can back up the NM data in two ways: periodic backup and manual backup. You can back up the server data through the full backup and the incremental backup.
When a full backup is performed successfully, the system deletes all the backup files previously stored on the server for the full or incremental backup. The server stores only one and the latest full backup compressed file. The previous backup may be a full backup or an incremental backup, for example, all-20060106103055.tar.gz. A new backup file is generated based on the previous backup each time an incremental backup is performed. The previous backup can be a full backup or an incremental backup. The naming rule for the incremental backup is inc-current time.
The server data to be backed up includes the files in the /export/home/omc/var/ and / export/home/sysm/ directories on the M2000 server. The backup files of the server data are stored in the path of M2000 server /export/home/ backup/omc/.
Related Tasks
10.2.2 Viewing NE Backup File
Related References
10.6.5 Parameters for NE Backup File
Issue 06 (2008-12-16)
10-3
10 Data Management
10.1.2 NE Backup Data

The M2000 provides the function of NE data backup. Therefore, you can back up the configuration files of all NEs managed by the M2000 and the files that change dynamically during the operation. You can back up the NE data in two ways: the periodic backup and the manual backup. When a backup task is performed, a backup file is generated on the M2000 server, regardless of the manual or periodic backup. The maximum number of NE backup files stored on the server is determined by the M2000 configuration file. At present, a maximum of seven backup files can be stored on each NE. When more than seven backup files are generated for an NE, the M2000 server stores only the latest seven backup files for this NE. Meanwhile, the M2000 server refreshes the backup file list. The backup files of NE data are saved to the path: M2000 server/export/home/sysm/ftproot/ NE type (for example: RNC)/data type/NE FDN.
NOTE
l l
For the CG, all M2000 users are considered as the user named M2000. Before backing up the CG data, log in to the LMT and authorize the CDR querying or browsing privilege to the M2000 user of the CG.
Related Tasks
10.3.2 Viewing NM Backup File
Related References
10.6.6 Parameters for NM Backup File
10.1.3 NM Log Data

When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic information from the M2000 Server and Client through the FTP protocol. By using this information, you can locate faults. The collected information includes:
l l
Trace files on the client, for example, Client_DebugTrace. Java virtual machine thread stack and lock state in client, for example, Client_ThreadStackDump.txt Trace files on the server, for example, iMAP.root.trace (to store the current trace files) and imap_stacks.20070206.170237.trace (to store the historical trace files collected before the NM log files) Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack File of alarm NE synchronization number, for example, FMSyncNo The pstack file, for example, imap_stacks.20070207.155817.trace. Information about the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, and SYBLog.20070206.171040.zip.
l l l l
By default, the collected files are saved in M2000 client\iManagerM2000Client\diagnosis \collected files. You can change the save path.
10 Data Management
Related Tasks
10.5 Collecting NM Log File
Related References
10.6.3 Parameters for Collecting NM Logs Parameters
10.2 NE Backup Data

You can back up the NE data in two ways: the periodic backup and the manual backup. When a backup task is performed, a backup file is generated on the M2000 server, regardless of the manual or periodic backup. Then you can restore the NE data through these backup files when required. 10.2.1 Manual NE Backup Data The M2000 supports manual NE data backup. 10.2.2 Viewing NE Backup File You can view the backup files stored on the server for all the NEs. 10.2.3 Restoring NE Data The M2000 supports restoring the backup NE data from the M2000 server to NEs.
10.2.1 Manual NE Backup Data

The M2000 supports manual NE data backup.
Prerequisite
l l l
You have logged in to the M2000 client. The FTP server is configured. You are authorized with the relevant privileges.
Context
For manual backup, the backup files are named BAKDATA+current time. For details, refer to the glossary and acronyms. The M2000 server acts as the FTP server to connect the client and NEs. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > Backup Management to view the Backup Management dialog box. Step 2 Click the NE Backup List tab. Step 3 Expand the navigation tree and select an NE.
l
Press Ctrl to select multiple NEs at a time. To select all the NEs, click the root node.
Issue 06 (2008-12-16)
10 Data Management
l
If you select an NE with sub-NEs, for example, if you select RNC, the system prompts you whether to back up the data of all the sub-NEs. You can also select sub-NEs of this NE to back up the data.
Step 4 Click Back up. Click Yes in the displayed Confirm dialog box. ----End
Result
When the backup task starts, you can view the execution progress and the detailed information in the Task List in the lower part of the Backup Management window.

You can view the backup files stored on the server for all the NEs.
Prerequisite
l l l l
You have logged in to the M2000 client. The FTP server is configured. You are authorized with the relevant privileges. The backed up NE files exist on the server.
Procedure
Step 1 Choose Maintenance > Backup Management. The Backup Management window is displayed. Step 2 Click the NE Backup List tab. Step 3 Expand the navigation tree and select an NE. Click Refresh to refresh the backup file list. If you select an NE with sub-NEs, for example, if you select RNC, the backup file list displays only the backup files of the RNC, but not those of the sub-NEs. If you select a subnet, the backup file list displays the backup files of all the NEs in this subnet. 10.6.5 Parameters for NE Backup File lists the descriptions of the parameters for viewing NE backup files. ----End
Related Concepts
Related References
10.2.3 Restoring NE Data

The M2000 supports restoring the backup NE data from the M2000 server to NEs.
10 Data Management
Prerequisite
l l l l
You have logged in to the M2000 client. The FTP server is configured. You are authorized with the relevant privileges. The NE data is backed up on the server.
Context
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > Backup Management to view the Backup Management dialog box. Step 2 Click the NE Backup List tab. Step 3 Expand the navigation tree and select an NE. Press Ctrl to select multiple NEs at a time. To select all the NEs, click the root node. The backup files of the NE is listed in NE Backup List. Step 4 Select a backup file in the list. Step 5 Choose Restore from the shortcut menu or click Restore in the dialog box. Step 6 Click Yes in the displayed Confirm dialog box.
CAUTION
The NE restarts after you perform the restore operations. ----End
10.3 NM Backup Data

M2000You can back up the NM data in two ways: periodic backup and manual backup. When a backup task is performed, a backup file is generated on the M2000 server, regardless of the manual or periodic backup. Then you can restore the data through these backup files if required. 10.3.1 Manual Backup of M2000 Data In addition to the periodic backup of M2000 data, M2000 also supports manual backup in real time as required. 10.3.2 Viewing NM Backup File You can view all the backup files on the M2000 server.
10.3.1 Manual Backup of M2000 Data

In addition to the periodic backup of M2000 data, M2000 also supports manual backup in real time as required.
10 Data Management
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform relevant operations.
CAUTION
l
If a standby server exists in the M2000 networking solution, do not change the storage medium of the backup data. If the M2000 networking solution is SLS, ensure that the storage mediums of the backup data are consistent on each server.
Procedure
Step 1 Choose Maintenance > Backup Management to view the Backup Management dialog box. Step 2 Click the Server Backup List tab. Step 3 Select the storage medium of backup data. The default storage medium is the backup medium of the current system. You can change the storage medium based on the actual requirements. 1. 2. Click Reset. Select the required storage medium from the Medium Type Setting dialog box. You can choose one from disk, tape, disk and tape or Veritas as the storage medium. If you choose disk and tape, the backup data is stored on both storage mediums. If you choose Veritas, the storage medium of backup data is determined by Veritas backup and restore solution. It can be a tape drive, a tape library or a disk. Step 4 Click Full Backup. For details, see 10.1.1 NM Backup Data. When the backup task starts, you can view the details of the execution progress and the backup task in the Backup Task List in the lower part of the Backup Management window. If the backup fails, a message is displayed, notifying you of the failure. ----End

You can view all the backup files on the M2000 server.
Prerequisite
l l l l
You have logged in to the M2000 client. The FTP server is configured. You are authorized with the relevant privileges. The backed up NM files exist on the server.
10-8
10 Data Management
Procedure
Step 1 Choose Maintenance > Backup Management. Open the Backup Management dialog box. For details, refer to 10.6.6 Parameters for NM Backup File. Step 2 Click the Server Backup List tab. Right-click the Server Backup List tab page, and then choose Refresh from the shortcut menu. You can refresh the server backup list in real time. All the server backup files are displayed in the list at the upper part of the tab page. ----End
Related Concepts
Related References
10.4 Collecting Network Optimization Data

You can collect the analysis data required by network planning and optimization through the M2000. The data collected by M2000 involves the neighbor cell optimization data and the uplink ARFCN data. The collected data is stored in the designated directory of the M2000 server. Network engineers use such data to analyze the neighbor cell and the uplink ARFCN through the Nastar. The neighbor cell optimization data is stored in opt/OMC/var/fileint/other/ adjacentCell, whereas the uplink ARFCN data is stored in opt/OMC/var/fileint/other/ ne<fdn>/frqlog. The neighbor cell optimization data refers to the performance data and configuration data of a cell. It shows the configurations of the neighbor cell. Uplink ARFCN data refers to the uplink level of a frequency. It shows the received signal strength of a frequency. 10.4.1 Collecting Neighbor Cell Optimization Data This describes how to collect the neighbor cell optimization data. By collecting the neighbor cell optimization data, the M2000 provides data for the Nastar during the analysis of neighbor cells. After the data collection task for neighbor cell optimization is created on the M2000, the M2000 delivers MML commands, informing a cell to send a system message to all terminals within the cell. According to the system message, terminals perform neighbor cell measurement and report the results to the M2000. The neighbor cell optimization data refers to the performance data and configuration data of the cell. It shows the configurations of the neighbor cell. 10.4.2 Collecting the Uplink ARFCN Data This describes the function of collecting the uplink ARFCN data provided by the M2000. The collected data are used by the Nastar during the analysis of the uplink interference. The ARFCN data is the measurement result of uplink level. It reflects the received signal strength of a frequency of a cell. The data can help network engineers choose appropriate frequencies.
10.4.1 Collecting Neighbor Cell Optimization Data

This describes how to collect the neighbor cell optimization data. By collecting the neighbor cell optimization data, the M2000 provides data for the Nastar during the analysis of neighbor cells. After the data collection task for neighbor cell optimization is created on the M2000, the
10 Data Management
M2000 delivers MML commands, informing a cell to send a system message to all terminals within the cell. According to the system message, terminals perform neighbor cell measurement and report the results to the M2000. The neighbor cell optimization data refers to the performance data and configuration data of the cell. It shows the configurations of the neighbor cell.
Context
Currently, only the BSC6000 supports this function. 10.4.1.1 Creating a Data Collection Task for Neighbor Cell Optimization You can create tasks of collecting neighbor cell optimization data to test certain frequencies. The test results are used as input data for Nastar in neighbor cell analysis. 10.4.1.2 Checking the Status of a Data Collection Task for Neighbor Cell Optimization This describes how to check the status of a data collection task. You can check the measurement status of a Running task. The measurement status covers the frequency group that is being measured and the measurement details of this frequency group. For data collection tasks in Finished or Idle status, you can view the detailed execution information in the Result Info. pane.
Creating a Data Collection Task for Neighbor Cell Optimization

You can create tasks of collecting neighbor cell optimization data to test certain frequencies. The test results are used as input data for Nastar in neighbor cell analysis.
Prerequisite
l l
You have logged in to the M2000 client. The M2000 and NEs communicate normally.
Context
l
The neighbor cell optimization tasks are user timing tasks. They are managed centrally by the integrated task management function of the M2000. For details on timing task management, see 14.10 Managing Timing Tasks. The path to save the data of neighbor cell optimization tasks is opt/OMC/var/fileint/other/ adjacentCell.
Procedure
Step 1 Choose Maintenance > Task Management, and the Task Management window is displayed. Step 2 Click New. The New Task dialog box is displayed.
TIP
You can choose Task Type > Other > Neighbor Cells Optimizing in the navigation tree. Double-click the task. The New Task dialog box is displayed. By default, the Task Type is Neighbor Cells Optimizing.
Step 3 Set the basic information of the task. 1. 2. 3.

10-10
Enter the name of the timing task in the Task Name field. Choose Neighbor Cells Optimizing under Task Type. In the Run Type group box, select Once or Period.
10 Data Management
Step 4 Click Next to set the timing information of the task. Step 5 Click and the Date/Time Selection dialog box is displayed. Set the start time of the task in the dialog box.
NOTE
l l l l l
The time format is DD-MM-YYYY HH:MM:SS. Start Time must be later than the current server time. Only one neighbor cell optimization task is allowed at a specific time on an NE. That is, the time segments of multiple measurement tasks cannot overlap. When all the frequencies are measured, the task ends automatically. If Run Type is set to Once, the Start Time parameter is invalid if you select Run At Once. In addition, the task is performed immediately after the settings are complete.
Step 6 Click Next to set the parameters of the task. For details on the parameters of neighbor cell optimization tasks, see 10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization. Step 7 Set NEs whose data is to be collected. 1. 2. Select the required NE type from the NE Type drop-down list. Select the NE whose data is to be collected from the NE Name drop-down list.
Step 8 Set Duration, Period, and Step.

l l l
Duration refers to the maximum period that a periodic task can last each time. Period refers to the duration of the measurement of each frequency group. Step refers to the number of frequencies in each group.
Step 9 Select cells. 1. 2. 3. In the Set Cell Parameter area, click Add. The Select Cell dialog box is displayed. Select required cells in The Unselected Cell List based on Cell Index or Cell Name. You can enter keywords in the text box next to Search to find required cells quickly. Click You can click to add one candidate cell to The Selected Cell List. to add all candidate cells to The Selected Cell List. You can click to delete all cells.
to delete a cell from The Selected Cell List, or click Step 10 Set frequencies.
NOTE
Before setting frequencies, you should set Step. All the selected frequencies are divided into groups according to the value of Step. For example, suppose that the parameter is set to 2, and three frequencies of 59, 60, and 61 are selected. Then these three frequencies are divided into two groups of (59,60) and (61). The M2000 measures different frequency sets within one measurement period in turn. After the frequencies are set, you can modify the Step to divide the frequencies into different groups.
1. 2.
In the Set Frequency Parameter area, click Add. The Select Frequency dialog box is displayed. Choose frequencies to be collected in the BCCH Frequency and All Frequency tabs. The selected frequencies are displayed in gray. You can check the number of selected frequencies from Number of Selected Frequencies.
Issue 06 (2008-12-16)
10 Data Management
NOTE
l l
BCCH Frequency: all the BCCH frequencies of the current cell and its neighbor cells. All Frequency: all the frequencies supported by a cell, including BCCH frequencies.
3.
Click OK. The selected frequencies are divided into groups based on the value of Step. The grouping information is displayed in Set Frequency Parameter.
Step 11 Optional: Set the soft parameters of neighbor cell optimization tasks. 1. 2. 3. Click Soft Parameter tab. Select Set Soft Parameter. After this field is selected, the soft parameters that you set take effect in this task. Set the thresholds for soft parameters. For the detailed description of soft parameters, see 10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization. Step 12 Click Finish. The added neighbor cell optimization tasks are displayed in the task list. ----End
Related References
10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization
Checking the Status of a Data Collection Task for Neighbor Cell Optimization
This describes how to check the status of a data collection task. You can check the measurement status of a Running task. The measurement status covers the frequency group that is being measured and the measurement details of this frequency group. For data collection tasks in Finished or Idle status, you can view the detailed execution information in the Result Info. pane.
Prerequisite
l l l
You have logged in to the M2000 client. The M2000 and NEs communicate normally. At least one neighbor cell optimization task is available.
Procedure
Step 1 Choose Maintenance > Task Management, and the Task Management window is displayed. Step 2 Query the status of a running task. 1. 2. In the task list, select a neighbor cell optimization task that is in Running status. Right-click the task, and choose Query from the shortcut menu. The Task Status dialog box is displayed. The information of the task status involve Cell Index, Cell Name, Measure Frequence Set, Measurement Period, Measurement Step, Frequency Being Measured, and Execution Time. 3.
10-12
Click OK to stop querying status.

10 Data Management
Step 3 Optional: You can view the detailed execution information of the selected task in the Result Info. pane. In the Result Info. pane, right-click and choose Save As from the shortcut menu to save the results to the local computer in *.txt format. ----End
10.4.2 Collecting the Uplink ARFCN Data

This describes the function of collecting the uplink ARFCN data provided by the M2000. The collected data are used by the Nastar during the analysis of the uplink interference. The ARFCN data is the measurement result of uplink level. It reflects the received signal strength of a frequency of a cell. The data can help network engineers choose appropriate frequencies.
Context
Currently, only the BSC6000 supports this function. 10.4.2.1 Creating a Task of Collecting the Uplink ARFCN Data After you create uplink frequency scan tasks on the M2000, you can analyze uplink frequency through Nastar. The uplink frequency analysis function tests the uplink level. It reflects the received signal strength of a frequency of a cell. The analysis can help network engineers choose appropriate frequencies. 10.4.2.2 Viewing the Progress of Collecting the Uplink ARFCN Data You can view the progress of the uplink frequency scan tasks from the task list in the Task Management window.
Creating a Task of Collecting the Uplink ARFCN Data

After you create uplink frequency scan tasks on the M2000, you can analyze uplink frequency through Nastar. The uplink frequency analysis function tests the uplink level. It reflects the received signal strength of a frequency of a cell. The analysis can help network engineers choose appropriate frequencies.
Prerequisite
l l
You have logged in to the M2000 client. The M2000 and NEs communicate normally.
Context
l
The uplink frequency scan tasks are user timing tasks. They are managed centrally by the integrated task management function of the M2000. For details on timing task management, see 14.10 Managing Timing Tasks. The path to save the data of uplink frequency scan tasks is opt/OMC/var/fileint/other/ ne<fdn>/frqlog.
Procedure
Step 1 Choose Maintenance > Task Management, and the Task Management window is displayed. Step 2 Click New. The New Task dialog box is displayed.
10 Data Management
TIP
You can choose Task Type > Other > FrequencyScan in the navigation tree. Double-click the task. The New Task dialog box is displayed. By default, the Task Type is FrequencyScan.
Step 3 Set the basic information of the task. 1. 2. 3. Enter the name of the timing task in the Task Name field. Select FrequencyScan under Task Type. In the Run Type group box, select Once or Period.
Step 4 Click Next to set the timing information of the task. Step 5 Click
NOTE
and the Date/Time Selection dialog box is displayed. Set the start time of the task.
l l
Start Time must be later than the current server time. If Run Type is set to Once, the Start Time parameter is invalid after you select Run At Once. In addition, the task is performed immediately after the settings are complete.
Step 6 Click Next to set the parameters of the task. For details on uplink frequency scan tasks, see 10.6.8 Parameters for Creating a Task of Collecting the Uplink ARFCN Data. Step 7 Set Time (Minute), that is, the duration of the task. Step 8 Select cells to be measured. 1. 2. 3. Select the required NE type from the NE Type drop-down list. Select the frequency used by a cell from the Cell Filter drop-down list. Select the required NE from the NE tree according to NE names, cell index, and cell names.
Step 9 Set frequencies to be measured. 1. 2. Select the required frequency type from the Frequency Type drop-down list. Optional: If you select The User Selected Frequency In the Frequency Segment from the Frequency Type drop-down list, you should select frequencies to be measured from the frequency list. The selected frequencies are displayed in gray.
----End
Related References
10.6.8 Parameters for Creating a Task of Collecting the Uplink ARFCN Data
Viewing the Progress of Collecting the Uplink ARFCN Data

You can view the progress of the uplink frequency scan tasks from the task list in the Task Management window.
Prerequisite
l l l
You have logged in to the M2000 client. The M2000 and NEs communicate normally. At least one uplink frequency scan task is available.
10-14
10 Data Management
Procedure
Step 1 Choose Maintenance > Task Management, and the Task Management window is displayed. Step 2 Select an uplink frequency scan task in the task list. 1. 2. You can view the progress of the task in Progress. You can view the detailed execution information of the selected task in the Result Info. pane. In the Result Info. pane, right-click and choose Save As from the shortcut menu to save the results to the local computer in *.txt format. ----End

When the M2000 client or server cannot run properly, you can collect all the running information from the M2000 client and server to locate faults.
Context
l
The progress of the information collection is displayed in the Collection Details box of the M2000 Log Information Collector window. The M2000 diagnostic tool automatically collects diagnostic information from the client and then from the server.
Procedure
Step 1 Choose Programs > iManager M2000 Client > M2000 Diagnosis Tool. Open the M2000 Log Collection Tool window. Step 2 The FTP server is configured. 1. 2. 3. Enter the IP address of the M2000 server. .Enter the port number. Enter the FTP user name and password used to log in to the target server.
Step 3 Choose the information to be collected. For details, refer to 10.6.3 Parameters for Collecting NM Logs Parameters.
l
If you want to collect trace files in the client, trace files in the server, core files in the server, or trace files in the local maintenance station, you should enter Start Time and End Time to collect the information within the specified time range. If you want to collect alarm diagnostic data of the NE, enter the name of the NE whose alarm diagnostic data you want collect in NE Name.
Step 4 Set a save path for the collected diagnostic data. By default, the collected files are saved in M2000 client installation path\diagnosis\collected files. The default M2000 installation path is C:\iManagerM2000Client. You can change the save path of the collected files. Step 5 Click Collect to collect the diagnostic information.
10 Data Management
l
If you click Stop when the diagnostic tool is collecting information from a client, you are not allowed to stop the progress of collecting information from the client. If you click Stop when the diagnostic tool is collecting information from the M2000 server, you are not allowed to get any diagnostic information about the server. If you need to view the collected diagnostic information, click Browse to enter the directory of the collected files.
----End
Related Concepts
10.1.3 NM Log Data
Related References
10.6 Reference for Data Management Interfaces

This part describes the data management interface, which consists of the backup management interface and the log information collector interface, and the parameters used in NE or NM data backup. This helps you understand the functions of data management. 10.6.1 Interface Description: Backup Management This describes the backup management interface, which helps you learn the functions of the interface. 10.6.2 Interface Description: Log Information Collector When the log information collector on the M2000 client or server is faulty, you can collect all related log files through FTP from the M2000 client or server to locate faults. 10.6.3 Parameters for Collecting NM Logs Parameters This part describes the parameters listed in the M2000 Log Information Collector dialog box. When collecting NMS log files, refer to the information described here for parameter setting. 10.6.4 Parameter Description of the Fields in the Backup and Restore Task List This describes the detailed parameters of the fields in the backup and restore task list. 10.6.5 Parameters for NE Backup File This part describes the parameters used for backing up NE files. 10.6.6 Parameters for NM Backup File This part describes the parameters used for backing up the M2000 files. 10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization This describes the parameters related to neighbor cell optimization tasks. You can refer to this part when creating or modifying neighbor cell optimization tasks. 10.6.8 Parameters for Creating a Task of Collecting the Uplink ARFCN Data This describes the parameters related to uplink frequency scan tasks. You can refer to this part when creating or modifying uplink frequency tasks.
10-16
Issue 06 (2008-12-16)
10 Data Management
10.6.1 Interface Description: Backup Management

This describes the backup management interface, which helps you learn the functions of the interface. The backup management interface is composed of the upper and lower parts.
l
The upper part consists of the Server Backup List tab and the NE Backup List tab. These two tabs separately display the server data backup files and the NE data backup files. The lower part lists the operation progress in real time and the details about the manual and periodic backup or restoration tasks.
CAUTION
l
If a standby server exists in the M2000 networking solution, do not change the storage medium of the backup data. If the M2000 networking solution is SLS, ensure that the storage mediums of the backup data are consistent on each server.
Figure 10-1 displays the backup management interface. Figure 10-1 Backup Management Interface
10.6.4 Parameter Description of the Fields in the Backup and Restore Task List describes the fields in the backup and restore task list.
10.6.2 Interface Description: Log Information Collector

When the log information collector on the M2000 client or server is faulty, you can collect all related log files through FTP from the M2000 client or server to locate faults. The log information collector contains four parts:
l
Server Information: In this area, you can set Server Address, Port, FTP User Name, and Password.
Issue 06 (2008-12-16)
10 Data Management
l
Items Selection: In this area, you can select the required information. To collect the client trace files, server trace files, or server core files, you must set Start Time and End Time of a specific time segment. To collect the alarm location information, enter an NE name in NE Name. Directory: This area shows the path for saving the diagnosis information. You can change the path. Collected Information Details: In this area, you can view the information collection process and progress.
Figure 10-2 shows the interface. Figure 10-2 Log Information Collector interface

This part describes the parameters listed in the M2000 Log Information Collector dialog box. When collecting NMS log files, refer to the information described here for parameter setting.
Parameter Server informatio n Server address Description Complies with the principles of IP address rules. Cannot be null.
10-18
Issue 06 (2008-12-16)
10 Data Management
Parameter Port Number
Description Indicates the port of the server. Value range: 1-65536. The default value is 10119. Cannot be null. FTP User name Indicates a valid name that the user already registered to the M2000. Cannot be null. password Indicates the password that is used to log in to the target server. Cannot be null.
Items selection
Trace files in Local Host Trace files in server Core files in server LMT trace files in server Start Time End Time Standby Collection Number of server threads and state Sun Explorer Alarm diagnostic data NE Name
Collects the trace files from the M2000 client. Collects the trace files from the M2000 server. Collects the core files from the server. Collects the trace files from the local maintenance terminal (LMT). Indicates the start time for collecting trace files and core files. Indicates the end time for collecting trace files and core files. Collects the information of the HA system. Collects the number of server threads and state from the M2000 server. Collects the information about Sun Explorer. Collects the alarm synchronization signals of NEs. Collects the NEs involved in alarm diagnostic data. Indicates the directory for the collected diagnostic data.
Save Positions
Save Positions
Related Concepts
10.1.3 NM Log Data
Related Tasks
Issue 06 (2008-12-16)
10-19
10 Data Management
10.6.4 Parameter Description of the Fields in the Backup and Restore Task List
This describes the detailed parameters of the fields in the backup and restore task list. Table 10-1 describes the fields in the backup and restore task list. Table 10-1 Fields in the backup and restore task list Field Object Description The name of an object to be backed up. The object can be the M2000 or an NE.
l
MaintenanceService is displayed when M2000 data is backed up. An NE name is displayed when NE data is backed up.
Progress Backup file State
Execution progress of a backup task or a restore task. The name of a backup file. The execution status of a backup task or a restore task.
l l l
Failed: indicates that a task fails. TaskProgress: indicates that the task is being executed. Succeeded: indicates that a task is successfully executed. TimeOut: indicates that a task times out.
Message Backup type
Message displayed during the backup or restoration. The system displays different messages for different situations. Backup types of the M2000 data are as follows:
l
Full backup: backs up all M2000 data. For details, see 10.1.1 NM Backup Data. Incremental backup: backs up new or changed M2000 data based on the previous backup data. For details, see 10.1.1 NM Backup Data. NA: indicates that a backup task fails.
NA is displayed when NE data is backed up. Operation type Operation type of a task.
l l
Backup: backs up NE data to the M2000 server. Restoration: restores the NE data backed up on the M2000 server to the NE.
Backup mode
Backup modes of M2000 data and NE data.

l l
Periodic: periodic backup. Manual: manual backup.
Task Start Time

10-20
Time when a backup task starts.

Issue 06 (2008-12-16)
10 Data Management
Field Task End Time
Description Time when a backup task ends.

This part describes the parameters used for backing up NE files. Table 10-2 describes the parameters used for backing up NE files. Table 10-2 Parameters for backing up NE files Parameter NE Name neVersion NE Type Description NE name that is defined during the NE setup. indicates the version of the NE. This parameter indicates the type of an NE. For details, refer to the descriptions of file types in software management. Backup File Backup Time File Size Path Message Name of a backup file. Time when the NE data is backed up. Size of a backup file. Path for storing a backup file on the M2000 server. Message of a backup file.
Related Concepts
Related Tasks

This part describes the parameters used for backing up the M2000 files. Table 10-3 describes the parameters used for backing up the M2000 files. Table 10-3 Parameters used for backing up the M2000 files Parameter ID Service Backup File Description Name of the service that executes the backup task. Name of a file automatically generated during the backup of the server data.
Issue 06 (2008-12-16)
10 Data Management
Parameter ID Backup Time
Description Time when the server data is backed up. The time format is the same as that set in the region setting. For details, refer to 1.4.5.1 Setting the Time Format of the Client.
Backup Type
Type of the backup selected for 10.3.1 Manual Backup of M2000 Data, which consists of:
l l
Full backup: backs up all NM data. Incremental backup: backs up new and changed NM data based on the previous backup data.
For details, refer to 10.1.1 NM Backup Data.
Related Concepts
Related Tasks
10.6.7 Parameters for Creating the Data Collection Task for Neighbor Cell Optimization
This describes the parameters related to neighbor cell optimization tasks. You can refer to this part when creating or modifying neighbor cell optimization tasks.
Parameter Task Task Name NE Type NE Name Duration Time Setting Run At Once Description Name of a task. Type of the NE on which you need to create or modify a task, for example, BSC6000. Name of the NE on which you need to create or modify a task, for example, BSC6000_num1. Maximum period that a periodic task can last each time. The task is performed immediately after the setting is complete. If you select this parameter, Start Time cannot be configured. Start Time The start time of the task.
10-22
Issue 06 (2008-12-16)
10 Data Management
Parameter
Description
NOTE
l The time format is DD/MM/YYYY HH:MM:SS. l Start Time must be later than the current time. l Only one neighbor cell optimization task is allowed at
a specific time on an NE. That is, the time segments of multiple measurement tasks cannot overlap.
l When all the frequencies are measured, the task ends
automatically.
Measure Task
Period
Duration of the measurement of each frequency group. The value is an integer from 1 to 48. The unit is *15 (minute), that is, the value must be multiples of 15 minutes. For example, if this parameter is set to 2, the time to measure each frequency group is 215 minutes, that is, 30 minutes.
Step
Number of frequencies in one group. The value is an integer from 1 to 32.
Set Cell Parameter
The cells selected in the data collection task. You can click Add to open the Select Cell dialog box and select cells to be measured.
Set Frequency Parameter
The frequencies selected in the data collection task. The frequencies are divided into groups. The number of frequencies of each group is determined by Step. You can click Add to view the Select Frequency dialog box and select the frequencies to be measured.
NOTE
l You can select a maximum of 762 frequencies. If the
number exceeds 762, the NE returns an error message, informing you that the creation or modification fails.
l Before setting this parameter, you must set Step.
Soft Parameter
RSSThres
The value is an integer from 0 to 127. When the measurement report indicates that the difference between the levels of the neighbor cell and the serving cell is greater than this value, the counter for relevant traffic statistics adds 1.
ASSThres
The value is an integer from 0 to 63. When the measurement report indicates that the level of the neighbor cell is greater than this value, the counter for relevant traffic statistics adds 1.
Issue 06 (2008-12-16)
10-23
10 Data Management
Parameter ADJINLVThres 1-7
Description You can set the threshold of the interference level for seven neighbor cells respectively. The value is an integer from 0 to 63. When the measurement report indicates that the difference between the levels of the neighbor cell and the serving cell is greater than this value, the counter for relevant traffic statistics adds 1.
NOTE
l l l
Level refers to the strength of the received or transmitted signal. It is generally used in power control and handover algorithm. ASSThres and RSSThres evaluate the feasibility of the neighbor cell. According to the actual requirements, you can modify these two values to adjust the evaluation standard. ADJINLVThres 1-7 evaluates the distribution of carrier-to-interference ratio (CIR) between neighbor cells and serving cells and the ratio among each segment. This parameter is used to analyze the level of frequency interference in combination with frequency configurations, which in turn is used to adjust the C/I distribution segment of neighbor cells and serving cells. Carrier-to-interference ratio distribution refers to the distribution of the power of the carrier signals and the power of the interference signals, that is, C/I distribution.
Related Tasks
10.4.1.1 Creating a Data Collection Task for Neighbor Cell Optimization
10.6.8 Parameters for Creating a Task of Collecting the Uplink ARFCN Data
This describes the parameters related to uplink frequency scan tasks. You can refer to this part when creating or modifying uplink frequency tasks.
Parameter Task Task Name NE Type NE Name Time Setting Run At Once Description Name of a task. Type of the NE on which you need to create or modify a task, for example, BSC6000. Name of the NE on which you need to create or modify a task, for example, BSC6000_num1. The task is performed immediately after the setting is complete. If you select this parameter, Start Time cannot be configured.
10-24
Issue 06 (2008-12-16)
10 Data Management
Description The start time of the task.

NOTE
l The format is DD-MM-YYYY HH:MM:SS. l Start Time must be later than the current time.
Time (Minute) Cell Parameter NE Type Cell Filter
Duration of a task. Type of an NE. The frequency band used by the cell. The M2000 supports the following frequency bands:
l l l l l l
DSC1800 E-GSM900 GSM850 P-GSM900 PSC1900 R-GSM900
Frequency Parameter
Frequency Type
Specifying the type of frequency to be measured. Three values are available:

l
All Frequency In The Frequency Segment All the frequencies in the specified frequency band are measured objects. All Configuration Frequency In the Selected Cells All the frequencies in the specified cell are measured objects. The User Selected Frequency In the Frequency Segment If this type is selected, you should specify the frequency to be measured.
Related Tasks
10.4.2.1 Creating a Task of Collecting the Uplink ARFCN Data
Issue 06 (2008-12-16)
10-25
11 Dual-Homing and LN Domain Management
11
About This Chapter
Dual-Homing and LN Domain Management
This part describes the basic functions provided by dual-homing and local network domain management. 11.1 Basic Knowledge This part introduces some of the basic knowledge about dual-homing and Local Area Network (LAN). 11.2 Managing the Dual-Homing This task is performed to manage the dual-homing. The dual-homing management is to manage the relation between the active MSCe/MSC Server and the standby MSCe/MSC Server. Configure the actual parameters to manage the dual-homing. 11.3 Managing the Local Network Domain The multi-area local network domain management functions provided by the M2000 are designed based on the correlations between domains and NEs/users. The functions mainly include creating/deleting/modifying domains, setting/disabling the domain authorities of users, and modifying the softswitch settings in a domain. 11.4 Reference for Management of Dual-Homing and Local Network Domain Interfaces This part describes the information on the interface of dual-homing and domain management and on the data consistency page of the dual-homing. In this way, you can execute operations involved in the dual-homing and the area-based privilege management of the multi-area network.
Issue 06 (2008-12-16)
11-1
11.1 Basic Knowledge

This part introduces some of the basic knowledge about dual-homing and Local Area Network (LAN). 11.1.1 Dual-Homing This part describes the basic knowledge of dual-homing. Dual-homing is a disaster tolerance mechanism to prevent the system breakdown and ensure the reliability of the mobile network. 11.1.2 Local Network Domain This part describes the basic knowledge on local network, multi-area (MA) network, and areabased privilege management of multi-area network. The local network domain refers to the areas that are managed by the local network. Each local network has an automatic PSTN and a specified number for toll that indicates the range of local network. For the subscribers in the same local network, they only need to dial up local telephone number. The local network is further divided into multi-area network and are network. The resources in the multi-area network can be divided into different domains. The authority granting policy enables the subscribers in the multi-area network can manage the resources in the local network.
11.1.1 Dual-Homing
This part describes the basic knowledge of dual-homing. Dual-homing is a disaster tolerance mechanism to prevent the system breakdown and ensure the reliability of the mobile network. To be specific, the dual-homing is a kind of networking mode where an MGW is homed to two MSCe/MSC Servers that together function as a dual-homing pair. Usually, the MGW registers only to the active MSCe/MSC Server. When the active MSCe/MSC Server fails, the MGW registers to the standby MSCe/MSC Server to guarantee the continuity of communication services. The active and standby MSCs know the status of each other through heartbeat signals, and ensure data synchronization through network management system. When dual-homing is applied on the MSCe/MSC Server, the following three modes are available:
l
1+1 active/standby: indicates that one MSCe/MSC Server serves as an active server, while the other MSCe/MSC Server is a standby server. 1+1 assistant: indicates that each MSCe/MSC Server is not only an active server but a standby server of the other MSCe/MSC Server. N+1 active/standby: indicates that there are N MSCe/MSC Servers that serve as active servers, while only one MSCe/MSC Server acts as the standby server for those N MSCe/ MSC Servers.
All schemes are the same for the MGW, because each MGW is configured with an active MSCe/ MSC Server and a standby MSCe/MSC Server. The configuration data in the dual-homing system falls into the following categories:
l
Data in the database are divided into active dual-homing data and standby dual-homing data. The active dual-homing data is always valid, but the standby-homing data is valid only when the active and standby MSCe/MSC Servers work in assistant mode. Data in the active and standby MSCe/MSC Servers are the same. Data in the active and standby MSCe/MSC Servers are totally different.
l l
11-2
11.1.2 Local Network Domain

This part describes the basic knowledge on local network, multi-area (MA) network, and areabased privilege management of multi-area network. The local network domain refers to the areas that are managed by the local network. Each local network has an automatic PSTN and a specified number for toll that indicates the range of local network. For the subscribers in the same local network, they only need to dial up local telephone number. The local network is further divided into multi-area network and are network. The resources in the multi-area network can be divided into different domains. The authority granting policy enables the subscribers in the multi-area network can manage the resources in the local network.
Local Network
Local network is shorted for local telephone network. A local network is a telephony network within a toll call numbering zone. The local network is composed of local exchange, transit exchange, inter-office trunk cables, rural toll trunk cables, subscriber lines, and telephone terminals. Local network is an extension of local communication network. After the automatic continuity is applied in the suburban areas, towns, and rural areas, cities and their suburban areas, towns, and rural areas are combined together into a local network. The local network mode has the following advantages: be conducive to the development of telephony service, facilitate the subscribers' usage, improve the efficiency to cost ratio, and enhance the management efficiency. Local networks generally apply to areas where the toll call numbers are of two or three digit long. A local network has a mobile switching center (MSC) or more than one if required. If there is more than one MSC in a local network, the MSCs intercommunicate with each other through highly efficient direct routes, which form a mesh network.
Multi-Area Network
The multi-area network is a network in which an MSC server controls several local networks with the bearer part separated from the control part. The MSC server controls all services in the MA network. In the MA network, equipment of each local network is connected with the local media gateway (MGW), and a local network intercommunicates with other local networks through an MGW. A multi-area network has a maximum of 16 local network. Here, a local network refers to the areas controlled by a virtual MSC server.
Area-Based Privilege Management of Multi-local Network

The resources in the multi-area are grouped into different domains. The authority granting policy enables the subscribers in the multi-area network to manage the resources in the local network. Area-based privilege management of multi-area network applies to the scenario where an MSC server manages multiple areas divided on a logical or physical basis while user management is still on a local basis. Area-based privilege management of multi-area network is categorized into domain management and domain authority management. A domain contains multiple users and a user has the authorities either in a private domain or a global domain. The following part illustrates the authorities of users belonging to either local or global domains.
l
A user belonging to a global domain has the following authorities:

Issue 06 (2008-12-16)

l
Setting the authorities of an object to the authorities of a local or global domain Changing the domain of an object that supports the domain Deleting an object that supports the domain Setting the authorities of an object that supports domain A to the authorities in domain A Changing the domain of an object that supports domain A Deleting an object that supports domain A
A user belonging to a private domain (such as domain A) has the following authorities:
Only the system administrator is authorized to manage domains and to set the domain authorities of non-administrator users. By default, an unspecified non-administrator user belongs to a global domain. Domains and NEs are in many-to-many relations. Thus, a domain may has more than one MSC server, and an NE may belong to multiple domains.
11.2 Managing the Dual-Homing

This task is performed to manage the dual-homing. The dual-homing management is to manage the relation between the active MSCe/MSC Server and the standby MSCe/MSC Server. Configure the actual parameters to manage the dual-homing. 11.2.1 Checking the Dual-Homing Information You can view the relationship between the MGW and the MSCe/MSC Server, the basic information about the MSCe/MSC Server, and the information about the link. 11.2.2 Checking the Dual-Homing Data Dual-homing data is part of the basic data of the MSCe/MSC Server. It includes the data of dualhoming virtual node, dual-homing working mode, dual-homing heartbeat link, and dual-homing backup route. This task aims to ensure the consistency of the MSCe/MSC Servers that are in assistant mode. In this way, the data on an MSCe/MSC Server can be partially or totally taken over by another MSCe/MSC Server when the MSCe/MSC Servers are switched over. 11.2.3 Setting the Attributes for Data Check Interface This task is performed to setting attributes for data check interface. To satisfy different users' demands for browsing the resource consistency, you can set some attributes for the Consistency Check tab page. For instance, set whether to show line numbers, grid line, or color. 11.2.4 Saving the Audit Result of Dual-Homing Data This task is performed to save the check result of dual-homing data. After checking the consistency of the dual-homing data, save the results to facilitate your analysis. 11.2.5 Generating the Script for Adjusting Difference Data After checking dual-homing data, you can generate an MML script based on the check result to modify inconsistent NE data. The script can be issued by the M2000 to NEs for execution. 11.2.6 Delivering the MML Command You can deliver an MML command to one MSCe/MSC Server of a dual-homing pair. Also you can deliver an MML command to both MSCe/MSC Servers of a dual-homing pair so that you can operate them at the same time. 11.2.7 Synchronizing the Dual-Homing Data After checking the consistency of dual-homing data and generating the adjustment script, you can synchronize the dual-homing data and issue the script to the NEs for execution, to ensure
the data consistency between the MSCe/MSC Servers that have a mutual-aid relationship. Thus, after a dual-homing switchover, one MSCe/MSC Server can take over part or all of the data of the other MSCe/MSC Server.
11.2.1 Checking the Dual-Homing Information

You can view the relationship between the MGW and the MSCe/MSC Server, the basic information about the MSCe/MSC Server, and the information about the link.
Prerequisite
l l l l
You have the right to manage dual homing. You have the right to operate the NEs that are related to dual homing. Dual-homing NEs have be created on the M2000. Dual-homing parameters have been set on the NEs.
Context
An MGW is homed to a maximum of two MSCe/MSC Servers, and multiple MGWs can be connected to the same MSCe/MSC Server.
NOTE
You cannot view the dual-homing information about a CDMA network.
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed. Step 2 On the State Monitor tab page and the information pane below it, you can view the dual-homing information.
l
On the State Monitor tab page, you can view the relationship between the MGW and the MSCe/MSC Server. On the State Monitor tab page, select an MSCe/MSC Server. The Basic Information tab page displays the basic information about the NE, such as the NE name, dual-homing indication, working mode, and virtual node name. On the State Monitor tab page, select a link. The UDP Heartbeat Information, M3UA Heartbeat Information, VDB Backup Router Information, and Physical Link Information tab pages display the details about this link.
----End
11.2.2 Checking the Dual-Homing Data

Dual-homing data is part of the basic data of the MSCe/MSC Server. It includes the data of dualhoming virtual node, dual-homing working mode, dual-homing heartbeat link, and dual-homing backup route. This task aims to ensure the consistency of the MSCe/MSC Servers that are in assistant mode. In this way, the data on an MSCe/MSC Server can be partially or totally taken over by another MSCe/MSC Server when the MSCe/MSC Servers are switched over.
Prerequisite
l
You have the right to manage dual homing.

Issue 06 (2008-12-16)

l l
You have the right to operate the NEs that are related to dual homing. The NE data is updated on the M2000.
Context
NOTE
Generally, a pair of dual-homing NEs can automatically synchronize data between them. The purpose of checking dual-homing data is to check the consistency of dual-homing data and to ensure that one MSCe/ MSC Server can take over part or all of the data of the other MSCe/MSC Server after a dual-homing switchover.
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed. Step 2 In the Basic information list, select a dual-homing pair to be checked. Step 3 Click Check, or click on the interface and then choose Check on the shortcut menu. The system displays the Consistency Check tab page. Step 4 In the Consistency Check tab page, select the data resource type to be checked. The system displays the check result in the right pane.
l
You can enter the resource type or key word in Search. Then the related resource types are listed under Search. You can quickly select the resource type to be checked by doubleclicking the type. By default, the system displays inconsistent data by red characters on pink background. To set the colors of characters and background, refer to 11.2.3 Setting the Attributes for Data Check Interface. Click in the navigation tree, and then choose Hide Identical Pages. The system displays only the tab pages that include inconsistent data. After you re-select a data resource type in the navigation tree, the system displays all the consistency check results. In the tab page, you can save check results, generate MML scripts, and run the scripts. For details, refer to 11.2.4 Saving the Audit Result of Dual-Homing Data, 11.2.5 Generating the Script for Adjusting Difference Data, and 11.2.7 Synchronizing the Dual-Homing Data.
----End
11.2.3 Setting the Attributes for Data Check Interface

This task is performed to setting attributes for data check interface. To satisfy different users' demands for browsing the resource consistency, you can set some attributes for the Consistency Check tab page. For instance, set whether to show line numbers, grid line, or color.
Prerequisite
The data consistency of the dual-homing pair have been checked. For detailed operations, refer to 11.2.2 Checking the Dual-Homing Data.
Procedure
Set the parameters in the Consistency Check tab page.
Attribute
Operation
Show Line Numbers In the Consistency Check tab page, right-click a record and then choose Show Line Numbers on the shortcut menu. To cancel the showing of line numbers, perform an inverse operation. Show Grid Line In the Consistency Check tab page, right-click a record and then choose Show Grid Line on the shortcut menu. To cancel the showing of grid, perform an inverse operation. Set Color... 1. Right-click the data and choose Set Color . The Set Color dialog box is displayed. 2. Click a color to open the Color Settings dialog box. 3. You can set colors for inconsistent data and overwritten data in either of the following ways:
l l l
Under Swatches, select the color you want. Under HSB, move the sliders to select the specific colors. In the RGB, move the sliders to select the specific colors.
4. Click OK. 5. Click OK or Apply. To use the default color settings, click Default in the Set Color dialog box. By default, the system uses red characters in pink background to express inconsistent data and uses green characters in orange background to express modified data.
----End
Related References
11.4.2 Interface Description: Checking the Dual-Homing Data
11.2.4 Saving the Audit Result of Dual-Homing Data

This task is performed to save the check result of dual-homing data. After checking the consistency of the dual-homing data, save the results to facilitate your analysis.
Prerequisite
Procedure
Step 1 In the Consistency Check tab page, click Save Data. The system displays the Select File Path dialog box.

NOTE
To obtain the latest data, click Refresh in the Consistency Check tab page.
Step 2 Set the storage path, type, and name for the file.
l l
The file can be saved in either .txt or .csv format. By default, the name is in the format of: Name of the active NE (IP)&Name of the standby NE (IP)_Data_Generation time, and the time is in the format of YYYY-MM-DD HH-MMSS. For instance, the default file name is as follows: OM_SX2(173.20.80.128)&OM_SX8 (173.20.80.132)_Data_2007-03-29 11_20_26.
Step 3 Click OK. The system displays the content of the file in a dialog box with the file name in the title.
NOTE
You can edit the content of the file in the dialog box and save the modified file.
Step 4 Click Close. ----End
11.2.5 Generating the Script for Adjusting Difference Data

After checking dual-homing data, you can generate an MML script based on the check result to modify inconsistent NE data. The script can be issued by the M2000 to NEs for execution.
Prerequisite
Procedure
Step 1 In the Consistency Check tab page, select a record with inconsistent data.
l
If the data of the left NE is correct, click it and then choose Overlap To Right on the shortcut menu. If the data of the right NE is correct, right-click it and then choose Overlap To Left on the shortcut menu.
TIP
l l
To select multiple records, press Ctrl or Shift. To select all the records, press Ctrl+a. To recover the modified data, right-click it and then choose Revert Left, Revert Right, and Revert All.
Step 2 Repeat 1 to modify other inconsistent data. Step 3 Click Generate MML. The Select File Path dialog box is displayed.
NOTE
In the generated MML script file, each MML command is followed by the name of the NE that executes this command. For example, MOD SEVNODE: SN="MSOFT_2", IMMT=TDM, IMCT=NOTALLMGW, IMSM=AUTO; {MSC_FF1}, where MSC_FF1 is the name of the NE that executes this command.
Step 4 Set the storage path, type, and name for the file.

l l
The file can be saved in either .txt or .csv format. By default, the name is in the format of: Name of the active NE (IP)&Name of the standby NE (IP)_DiffMML_Generation time, and the time is in the format of YYYY-MM-DD HHMM-SS. For instance, the default file name is as follows: OM_SX2(173.20.80.128) &OM_SX8(173.20.80.132)_DiffMML_2007-03-29 11_20_26.
Step 5 Click OK. The system displays the content of the file in a dialog box with the file name in the title.
NOTE
You can edit the content of the file in the dialog box as well as save and run the modified script.
Step 6 Click Close. ----End
11.2.6 Delivering the MML Command

You can deliver an MML command to one MSCe/MSC Server of a dual-homing pair. Also you can deliver an MML command to both MSCe/MSC Servers of a dual-homing pair so that you can operate them at the same time.
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed. Step 2 In the Basic information list, select a dual-homing pair. Step 3 Click MML Command, or click in the window and then choose MML Command on the shortcut menu, to open the MML Command tab page. Step 4 Deliver an MML command. 1. 2. In the ROOT navigation tree, select an NE. In the MML Command Navigation Tree, select an MML command. By clicking the Search tab page and using the search function, you can select an MML command quickly. In the command window, set related parameters. Do as follows to determine whether to select the Send to assistant host check box:
l
3. 4.
If you plan to deliver the MML command to both the active and standby MSCe/MSC Servers, select the Send to assistant host box. If you plan to deliver the MML command only to the active server, do not select this check box.
to run the command. Step 5 Click The execution results takes effect on the corresponding MSCe/MSC Server(s), and accordingly the involved settings of the MSCe/MSC Server(s) are modified. ----End
Postrequisite
The M2000 supports the clear-up of messages. To clear up messages, perform the following steps:
1.
On the Common Maintenance tab page, right-click Clear Report.

NOTE
l l
Messages of the MML commands whose Status are Completed can be cleared up. When MML commands are being delivered, the option Clear Report on the shortcut menu is unavailable.
11.2.7 Synchronizing the Dual-Homing Data

After checking the consistency of dual-homing data and generating the adjustment script, you can synchronize the dual-homing data and issue the script to the NEs for execution, to ensure the data consistency between the MSCe/MSC Servers that have a mutual-aid relationship. Thus, after a dual-homing switchover, one MSCe/MSC Server can take over part or all of the data of the other MSCe/MSC Server.
Prerequisite
The inconsistency adjustment script has been created. For detailed operations, refer to 11.2.5 Generating the Script for Adjusting Difference Data.
Procedure
Step 1 In the Consistency Check tab page, click Run MML Script. The system displays the Select File Path dialog box.
TIP
Also, you can synchronize dual-homing data in either of the following ways:
l l
Run the script after generating an inconsistency adjustment script. For detailed operations, refer to 11.2.5 Generating the Script for Adjusting Difference Data. In the Task Management window, create an MML script task by referring to 14.2.1 Creating MML Command Script.
Step 2 Select a script file. This script file must be the one generated after the data consistency check. For details, refer to 11.2.5 Generating the Script for Adjusting Difference Data. Step 3 Click OK. The system displays the content of the file in a dialog box with the file name in the title. Step 4 Click Run. The Create Task dialog box is displayed. Step 5 Type the task name. The length of a task name is 1 to 60 characters that only includes letters, digits, -, or _. Step 6 Click OK. The system displays the Confirmation dialog box, prompting that this task is created successfully and asking you whether to view the task. Step 7 In the Confirmation dialog box, click OK. The system displays the Task Management window, in which you can view the task details, such as the task name, task status, and execution time. ----End
11.3 Managing the Local Network Domain

The multi-area local network domain management functions provided by the M2000 are designed based on the correlations between domains and NEs/users. The functions mainly include creating/deleting/modifying domains, setting/disabling the domain authorities of users, and modifying the softswitch settings in a domain. 11.3.1 Creating a Local Network Domain This task is performed to create a local network domain. An MSC Server can manage several local networks and the operations in each local network do not affect each other. Since the user management is still at the local network level, a subscriber in a local network can set or check the information of only this local network. After creating a local network domain, you need to bind subscribers or NEs and the local network domain together. In this way, you can manage the resource of the local network domain. 11.3.2 Managing Local Network Resources This task is performed to manage the resources in the local network domain. Managing local network resources is to grant authority for resources and to manage the configuration data. 11.3.3 Managing Users in the Local Network Domain This task is performed to manage users in the local network domain. The users in the local network domain refers to those users that have the authority for using the resources in the local network domain. The user management in the local network domain is to bind users to a certain domain so that the users have the authority for this domain. 11.3.4 Managing NEs in the Local Network Domain This describes how to manage NEs in the local network domain. The data on the NEs is assigned to domains so that the subscribers in the local network domain can manage the resources in the domain. 11.3.5 Modifying the Name of Local Network Domain A system administrator can change the name of a domain. The modification of domain names affects users' operation rights. By performing synchronization operations, users can have operation rights of the resources in new domains. 11.3.6 Synchronizing the Information of Local NE Domain This describes how to synchronize the information of local NE domain. When the domain name on the M2000 is inconsistent with that on the NE, the users on the NE domain do not have the authority for the domains. In such a situation, you need to synchronize the information of the local NE domain so that the users in the NE domain have the associated authority. 11.3.7 Deleting Local Network Domain This task is performed to delete the local network domain. You can delete a local network domain when it is no longer required. After the deletion of the local network domain, the subscribers in the previous local network domain become the subscribers of the global network domain. The NE resources in the previous local network domain become resources of the public domain. 11.3.8 Instances of Area-Based Privilege Configuration Area-based privilege management of multi-area network applies to the scenario where an MSC server manages multiple areas divided on a logical or physical basis while user management is still on a local basis. This part describes an instance of area-based privilege configuration to help you have a better understanding on area-based privilege management of multi-area network.
Issue 06 (2008-12-16)
11-11
11.3.1 Creating a Local Network Domain

This task is performed to create a local network domain. An MSC Server can manage several local networks and the operations in each local network do not affect each other. Since the user management is still at the local network level, a subscriber in a local network can set or check the information of only this local network. After creating a local network domain, you need to bind subscribers or NEs and the local network domain together. In this way, you can manage the resource of the local network domain.
Procedure
Step 1 Choose Configuration > Domain Management to open the Domain Management window. Step 2 Right-click the Domain node and choose Create. The Create Domain dialog box is displayed. Step 3 Enter the name for the new domain in the Please Input Domain Name field.
NOTE
l l
You can type one to 30 characters in the field mentioned previously. Special characters excluding the underline are not allowed. Select NEs and users from the NE List and User List to bind these them to this local network domain.
Step 4 Click OK or Apply to create a local network domain. The new domain is displayed both under the Domain node and in the Domain List in the Domain Management window. ----End
11.3.2 Managing Local Network Resources

This task is performed to manage the resources in the local network domain. Managing local network resources is to grant authority for resources and to manage the configuration data.
Procedure
Step 1 Choose Maintenance > MML Command. The MML Command window is displayed. Step 2 Select the MSC servers that have the dual-homing relation from the navigation tree. Enter the command in the Command Input field. For instance, enter ADD ACC. Step 3 Set Deliver the Standby Server to Yes. Step 4 Press F9 or perform ----End .
11.3.3 Managing Users in the Local Network Domain

This task is performed to manage users in the local network domain. The users in the local network domain refers to those users that have the authority for using the resources in the local network domain. The user management in the local network domain is to bind users to a certain domain so that the users have the authority for this domain.
Prerequisite
You have the authority for domain operation.
Procedure
Step 1 Choose Configuration > Domain Management to open the Domain Management window. Step 2 Click the Domain tab in the lower left. Step 3 Select a field in the Domain navigation tree and select User Liston right. Step 4 Right-click the selected field and select Bind User on the shortcut menu. Alternatively, click Bind User to view the Bind User dialog box.
NOTE
You can also select a user in User List on right and right-click it to select Bind User on the shortcut menu.
Step 5 In User List, select the user to be bound or deselect a bound user. Step 6 Click OK. ----End
11.3.4 Managing NEs in the Local Network Domain

This describes how to manage NEs in the local network domain. The data on the NEs is assigned to domains so that the subscribers in the local network domain can manage the resources in the domain.
Context
The NE to be added or removed is in connection with the M2000. You have the authority for domain operation.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is displayed. Step 2 On the left pane, right-click a domain under the Domain node. Alternatively, right-click a domain on the NE List. Choose Bind NE or click Bind NE. The Bind NE dialog box is displayed.
NOTE
If an NE is in disconnected, the NE cannot be bound.
Step 3 Click the NE List tab to select or clear the NE to be bound. Step 4 Click OK. ----End
Related References
11.4.3 Interface Description: Managing the Local Network Element Domain
Issue 06 (2008-12-16)
11-13
11.3.5 Modifying the Name of Local Network Domain

A system administrator can change the name of a domain. The modification of domain names affects users' operation rights. By performing synchronization operations, users can have operation rights of the resources in new domains.
Prerequisite
You have the authority for domain operation.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is displayed. Step 2 In the left pane, select the Domain tab. Two methods are available for changing the name of a domain: Method Method one Procedure 1. In the Domain Managementwindow, select a domain under the node Domain. 2. Right-click it and select Rename... on the shortcut menu. The system displays the Rename Domain dialog box. 3. Enter the new name of the domain. 4. Click OK. Method Two 1. In the Domain Management window, select a domain under Domain List. 2. Right-click the domain and select Rename... on the shortcut menu, or click Rename.... The system displays the Rename Domain dialog box. 3. Enter the new name of the domain. 4. Click OK.
NOTE
If the NEs in the modified domain are disconnected from the M2000, the NEs are Different after the name of the domain is changed. After the NEs are connected, you can right-click an NE whose Synchronization Status is inconsistent from the NE List, and then choose Synchronization to synchronize the modified domain name to the NE.
----End
11.3.6 Synchronizing the Information of Local NE Domain

This describes how to synchronize the information of local NE domain. When the domain name on the M2000 is inconsistent with that on the NE, the users on the NE domain do not have the authority for the domains. In such a situation, you need to synchronize the information of the local NE domain so that the users in the NE domain have the associated authority.
Prerequisite
You have the authority for domain operation. The NEs are in inconsistent status.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is displayed. Step 2 In the navigation tree, select the Domain node. Select an NE whose Synchronized State is Different on the NE List tab. Step 3 Choose Synchronize or click Synchronize to synchronize the information of local network domain. If the NE is connected, the Synchronized State of the NE becomes Accordant. If the an NE is disconnected, the Synchronized State is still Different. ----End
11.3.7 Deleting Local Network Domain

This task is performed to delete the local network domain. You can delete a local network domain when it is no longer required. After the deletion of the local network domain, the subscribers in the previous local network domain become the subscribers of the global network domain. The NE resources in the previous local network domain become resources of the public domain.
Prerequisite
You have the authority for domain operation. The resources in the local network domain are not used by other domains and the NEs in the domain is correctly connected.
Context
Once the local network domain is deleted, the subscribers in the previous domain become the subscribers of the global network domain.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is displayed. Step 2 Select the Domain node and use either of the following methods to delete the local network domain:
Issue 06 (2008-12-16)
11-15
Method
Step
Method 1 1. Right-click a domain under the Domain node. 2. Choose Delete. 3. In the displayed Confirmation dialog box, click Yes to delete the local network domain. Method 2 1. Right-click a domain from the Domain List in the Domain Management window. 2. Choose Delete. Alternatively, click Deleteafter selecting a domain. 3. In the displayed Confirmation dialog box, click Yes to delete the local network domain. ----End
11.3.8 Instances of Area-Based Privilege Configuration

Area-based privilege management of multi-area network applies to the scenario where an MSC server manages multiple areas divided on a logical or physical basis while user management is still on a local basis. This part describes an instance of area-based privilege configuration to help you have a better understanding on area-based privilege management of multi-area network.
Adding a Domain
1. 2. 3. 4. Choose Configuration > Domain Management. The Domain Management window is displayed. Right-click the Domain node and choose Create. The Create Domain dialog box is displayed. In the Please Input Domain Name field, enter the name of the desired domain. In the NE List or User List, select NEs or users to bind NEs and users. Click OK to add a domain.
Logging In to the LMT Client

On the LMT client, enter the user name of the domain in the User Name field. Select an office for user login in the Office field. Click Login. After the login to the LMT, the operation data belongs to the resources of local domain.
11.4 Reference for Management of Dual-Homing and Local Network Domain Interfaces
This part describes the information on the interface of dual-homing and domain management and on the data consistency page of the dual-homing. In this way, you can execute operations involved in the dual-homing and the area-based privilege management of the multi-area network. 11.4.1 Interface Description: Managing the Dual-Homing Through the description, you can know the details about the Dual Homing window.
11.4.2 Interface Description: Checking the Dual-Homing Data Through the description, you can know the details about the tab page. 11.4.3 Interface Description: Managing the Local Network Element Domain This part describes the interface for managing the local network element domain.
11.4.1 Interface Description: Managing the Dual-Homing

Through the description, you can know the details about the Dual Homing window. The Dual Homing window has two parts: the State Monitor tab page and the information pane below it.
l
The State Monitor tab page illustrates the relationship between the MGW and the MSCe/ MSC Server as well as the status of the MSCe/MSC Server virtual node. In the State Monitor tag page, select an MSCe/MSC Server. The Basic Information tab page displays the NE's basic information, such as the NE name, dual-homing indication, working mode, and virtual node name. In the State Monitor tab page, select a link. The UDP Heartbeat Information, M3UA Heartbeat Information, VDB Backup Router Information, and Physical Link Information tab pages display the details about this link.
For 1+1 mutual-aid networking mode, the Dual Homing window is shown in Figure 11-1. For 1+1 active/standby networking mode, the Dual Homing window is shown in Figure 11-2. For N+1 active/standby networking mode, the Dual Homing window is shown in Figure 11-3. Figure 11-1 Dual Homing window (for 1+1 mutual-aid networking mode)
Issue 06 (2008-12-16)
11-17
Figure 11-2 Dual Homing window (for 1+1 active/standby networking mode)
Figure 11-3 Dual Homing window (for N+1 active/standby networking mode)
11.4.2 Interface Description: Checking the Dual-Homing Data

Through the description, you can know the details about the tab page.
The Consistency Check tab page is composed of the navigation tree in the left part and the pane in the right part. After you select a data resource type, the right pane displays whether the active MSCe/MSC Server is consistent with the standby MSCe/MSC Server. In the tab page, you can save check results, generate MML scripts, and run the scripts. For details, refer to 11.2.4 Saving the Audit Result of Dual-Homing Data, 11.2.5 Generating the Script for Adjusting Difference Data, and 11.2.7 Synchronizing the Dual-Homing Data. Figure 11-4 shows the consistency check tab page. Table 11-1 describes Figure 11-4. Figure 11-4 The Consistency Check tab page
Table 11-1 Interface description No. (1) (2) Name Navigation tree Searching panel Description Displays all the data resource types to be checked. Displays the related data resource types after you enter a data resource type or the key word in the Search box. By clicking a type, you can locate it in the navigation tree. Displays consistency check results. Provides the related operation buttons.
(3) (4)
Content window Button panel
Related Tasks
11.2.3 Setting the Attributes for Data Check Interface
11.4.3 Interface Description: Managing the Local Network Element Domain

This part describes the interface for managing the local network element domain.
The interface for managing the local network element domain is as shown in Figure 11-5. Figure 11-5 Interface for managing the local network element domain
No. (1) (2) (3)
Meaning Refers to a defined domain. Refers to the list of NEs that belong to a specified domain. Refers to the list of users that belong to a specified domain.
Related Tasks
11.3.4 Managing NEs in the Local Network Domain
11-20
Issue 06 (2008-12-16)
12 MSC Pool Management
12
About This Chapter
MSC Pool Management
MSC Pool refers to a resource pool composed of MSC servers. The access network RNC/ BSC is connected to all the MSC servers in the pool. By using the MSC Pool, you can distribute the user service to the MSC servers in the pool according to the capacity ratio. In this way, the traffic peak in different districts and different time ranges can be balanced. The operator can make an investment based on the maximum traffic of the whole city rather than that of each district. Thus, the network capacity can be optimized and the investment is economized. Through the M2000 client, you can monitor and maintain the MSC Pool network and configure data. 12.1 Basic Knowledge of MSC Pool This describes the conceptual knowledge related to MSC Pool management, which consists of basic principle, principle of user transfer, principle of load balance, networking application, and authority management. The basic knowledge helps you better maintain the MSC Pool. 12.2 Creating MSC Pool Topology on the M2000 This describes how to create an MSC Pool for all related NEs so that you can perform related operations on the M2000. 12.3 Initial Configuration of MSC Pool This describes how to perform the initial configuration for the MSC Pool. After you create a new MSC Pool, you should perform the initial configuration. The configuration includes tasks such as setting an alarm for MSC Pool load unbalance, creating an auto-check task for the MSC Pool, and setting attributes for the MSC Pool. The configuration enables you to monitor and maintain the MSC Pool network in the future. 12.4 Routine Maintenance of MSC Pool This describes how to perform routine maintenance for the MSC Pool on the M2000 client. The maintenance and operation tasks include checking the MSC Pool alarms , measuring the MSC Pool performance, monitoring the load of the MSC Pool in real time, checking the MSC server where the specific user is located, displaying the MSC Pool topology, and managing the autocheck task of the MSC Pool. 12.5 MSC Pool Network Maintenance This describes how to perform the fault maintenance for the MSC Pool on the M2000 client. The fault maintenance includes the load balancing of the MSC Pool and the data checking of the MSC Pool.
12.6 Management Interface of MSC Pool This describes the management interfaces of the MSC Pool and the parameters. This describes the main interface of MSC Pool operation and maintenance, the interface for viewing MSC Pool alarms, the MSC Pool configuration interface, and parameters related to Pool configuration or maintenance operations. In this way, you can perform operations related to MSC Pool management.
12-2
Issue 06 (2008-12-16)
12.1 Basic Knowledge of MSC Pool

This describes the conceptual knowledge related to MSC Pool management, which consists of basic principle, principle of user transfer, principle of load balance, networking application, and authority management. The basic knowledge helps you better maintain the MSC Pool. 12.1.1 Basic Scheme of MSC Pool By using the Iu/A-Flex technology, the MSC Pool enables an RNC/BSC to share multiple MSC servers. The system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of MSC server. Thus, the resources on the MSC server can be shared. 12.1.2 Load balance scheme of MSC Pool In an MSC Pool network, one RNC/BSC is connected to multiple MSC servers within an MSC Pool. According to the load balancing scheme, the system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of the MSC servers. In this way, the utilization of the entire CN resources is improved and the investment is reduced. 12.1.3 Transfer Scheme of MSC Pool Users You can transfer users through 3GPP 23.236 protocol or inter-office E interface redirection. On the M2000, the default transfer scheme is inter-office E interface redirection. 12.1.4 MSC Pool Networking Application The MSC Pool scheme is applicable to a hybrid network of GSM, and WCDMA. The MSC Pool network consists of core network comprising MSC server and the MGW, and access network NEs such RNC, BSC, or RNC&BSC. 12.1.5 User Authority Management of the MSC Pool A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. After purchasing the license of the M2000 MSC Pool and being granted the relevant right, you can perform the operations related to the MSC Pool on the M2000 client.
12.1.1 Basic Scheme of MSC Pool

By using the Iu/A-Flex technology, the MSC Pool enables an RNC/BSC to share multiple MSC servers. The system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of MSC server. Thus, the resources on the MSC server can be shared.
Background
The traffics in different districts and different periods vary depending on many factors, such as the mobility of mobile subscribers, population density, and individual calling habits. During traffic peak periods, for example, festivals, the high load of the network in high traffic districts leads to unstable equipment performance and declined service quality. On the other hand, the equipment in low traffic districts cannot be fully utilized. To reduce the impact of traffic peak, operators perform more redundancy configurations for equipment capacity and thus the investment is increased. In this situation, the Huawei MSC Pool solution is proposed for solving this problem. Compared with the traditional network, the MSC Pool technology has the following advantages:
l
Load balancing: indicates balancing the load between the MSC servers to improve the resource efficiency of the entire CN and to save the investment on the equipment.
Issue 06 (2008-12-16)

l
Network disaster tolerance: realizes the disaster recovery and backup on the MSC server level If an MSC server in the MSC Pool is faulty, the NNSF nodes, that is, MGW/RNC/BSC can detect the fault and transfer the initiated user service from the faulty MSC server to a functional MSC server.
Decreasing location updates between offices and reducing the signaling traffic over the C/ D interface Reducing handoffs between different MSC servers to improve users'conversation quality. Simplifying the network planning: the planning for the CN is different from that for the access network (AN).
l l
Network Structure
Take the GSM network as an example. As shown in Figure 12-1, the BSC connects to all the MSC serves within the MSC Pool through the Iu/A-Flex interface. The coverage area of all the BSCs constitutes a pool area, and thus the MSC server expands its services to the whole pool area. When a user roams within the pool, the corresponding MSC server does not change. Figure 12-1 Networking of the MSC Pool
Basic Concepts
For related description of the MSC Pool concepts, see Table 12-1. Table 12-1 Basic concepts concerning the MSC Pool Concept MSC Pool Description As shown in Figure 12-1, a group of MSC servers form an MSC Pool.
12-4
Concept MSC Pool Area
Description If one or more RNCs/BSCs belong to an MSC Pool, the service areas covered by the RNCs/BSCs form an MSC Pool area, as shown in Figure 12-1. The subscribers in the pool area are served by the MSCs in the MSC Pool.
Iu/A-Flex function
Refers to the technology used for connecting the RNC/ BSC to multiple MSC servers. According to the 3GPP 23.236 protocol, the BSC in an MSC Pool must support the A-flex function. The BSC on the current network, however, does not support the A-Flex. In addition, the A-Flex supported by BSCs manufactured by different vendors is not consistent. Therefore, the MGW is the agent of A-Flex in the CDMA pool. To solve this problem, Huawei MGW can be used to act as the A-Flex agent. In this way, BSCs on the present network can access the MSC Pool without upgrade.
NNSF Function (NAS node selection function)
Indicates the node selection function on the non-access stratum (NAS). It is used to select an MSC server for an MS/ UE.
12.1.2 Load balance scheme of MSC Pool

In an MSC Pool network, one RNC/BSC is connected to multiple MSC servers within an MSC Pool. According to the load balancing scheme, the system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of the MSC servers. In this way, the utilization of the entire CN resources is improved and the investment is reduced. In an MSC Pool, one RNC/BSC is connected to multiple MSC servers in the pool. Therefore, when the MS/UE in the RNC/BSC service area initiates a new service request, the RNC/BSC needs to select a serving MSC server for the service. For details, see Table 12-2. Table 12-2 Load balance scheme of MSC Pool Call Mode The MS/UE initiates a service based on the IMSI or IMEI. Load Balancing Scheme According to the load balancing algorithm, the RNC/BSC selects a valid MSC server for the MS/UE based on the proportion of subscriber capacity of the MSC servers in the MSC Pool. If an MS/UE initiates a service using IMSI, the selected MSC server distributes a TMSI containing the NRI of the MSC to the MS/UE. As shown in Figure 12-2, if the available capacity of MSC server1 is 4, the available capacity of MSC server2 is 3, and the number of MSs/UEs is 7, then the RNC/BSC assigns four MSs to MSC server1 and three to MSC server2 to ensure the load balance.
Issue 06 (2008-12-16)
12-5
Call Mode The MS/UE initiates a service based on the IMSI.
Load Balancing Scheme The RNC/BSC selects the serving MSC server for the MS/UE according to the mapping between the NRI and MSC server.
NOTE When the selected MSC server is invalid or no mapping is available between the NRI and the MSC server, the RNC/BSC uses the load balancing algorithm and distributes MSC server according to the proportion of subscriber capacity of the MSC servers. Then, the selected MSC server assigns a TMSI containing the office NRI to the MS/UE.
The MSC server pages the called MS/UE based on the IMSI.
The RNC/BSC temporally saves the mapping between the MSI and the paged MSC server. When the paged MS/UE pages the corresponding network based on the IMSI, the RNC/BSC selects the MSC server according to whether the NRI is available on the MS/UE.
l
If the NRI is available on the MS/UE, the RNC/BSC selects an MSC server according the mapping between the NRI and the MSC server. If the NRI is unavailable on the MS/UE, the RNC/BSC selects the MSC server according to the temporally saved mapping between the IMSI and the MSC server.
NOTE If the selected MSC server is invalid or the system fails to select the MSC server according to the mapping, the RNC/BSC selects an MSC server according to the load balancing algorithm.
Figure 12-2 Load balancing principle
12-6
Issue 06 (2008-12-16)
CAUTION
l
When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/ BSC considers the MSC to be faulty or invalid. The proportions of subscriber capacity of the RNC/BSC to each MSC server needs to be configured statically on the RNC/BSC. In addition, the MSC servers can notify the subscriber capacity regularly, and the RNC/ BSC dynamically adjusts the proportion of subscriber capacity of MSC servers according to the subscriber capacity of each MSC server in the notification. This mode, however, only applies to the case that all MSC servers in the MSC Pool and BSCs and RNCs in the MSC Pool area are Huawei equipment. For other modes, the RNC can configure the subscriber capacity of MSC servers statically.
The subscriber capacity of an MSC server described previously is the total number of subscribers of the MSC server (number of licensed subscribers for the MSC server). However, when an MSC server connects with RNCs or BSCsoutside the MSC Pool, the subscriber capacity reserved for these RNCs or BSCs needs to be subtracted from total capacity as for calculation of subscriber capacity of the MSC server.
12.1.3 Transfer Scheme of MSC Pool Users

You can transfer users through 3GPP 23.236 protocol or inter-office E interface redirection. On the M2000, the default transfer scheme is inter-office E interface redirection. See Table 12-3 for details.
Issue 06 (2008-12-16)
12-7
Table 12-3 Principles of user transfer User Transfer Mode 3GPP TS 23.236 protocol Description The NEs with the Iu/A-Flex function are required, such as the MGW/RNC/BSC. On these NEs, you should set the status of the MSC server from which users are to be transferred to off-load.
NOTE
l When using this method, the
Principle of User Transfer among MSC Servers 1. On the MSC server and the RNC/ BSC, set the MSC server where users are transferred to the off-load status. 2. When an MS/UE registered in the off-load MSC server initiates services, the MSC server distributes the TMSI that contains the Null TMSI to the MS/UE. Meanwhile, the current LAI of the MS/UE is designated as local Nonbroadcast LAI. 3. After the MS/UE ends the current service, the Non-broadcast LAI prompts the MS/UE to update the location. This is because the Non-broadcast LAI is different from the RAI broadcast by the RNC/BSC of the MS/UE. 4. Upon receiving a location update message containing null-NRI from the MS/UE, the RNC/BSC selects a valid MSC server according to the proportion of user capacity of valid MSC servers (excluding the off-load MSC server) and routes services to the selected MSC server. The selected MSC server registers the MS/UE and distributes a TMSI containing its NRI to the MS/UE. During the registration, the selected MSC server determines the original MSC server where the MS/UE is registered according to the Non-broadcast LAI carried by the MS/UE. The server also obtains user data, that is, IMSI and unused encryption parameters from the original MSC server. 5. After transferring users, restore the state of the MSC server on the MSC server and the RNC/BSC through the M2000. For details, see 12.3.3.9 Setting the
destination MSC server cannot be specified. The system selects the destination MSC server according to the load balancing algorithm.
l After transferring users, you
should restore the MSC server state that is configured on the MSC server and the RNC through the M2000.
12-8
Issue 06 (2008-12-16)
User Transfer Mode
Description
Principle of User Transfer among MSC Servers Maintenance State of NEs in MSC Pool.
Inter-office E interface redirection
The NEs with the Iu/A-Flex function, that is, the MGW/RNC/ BSC, are not required. You only need to specify a destination MSC server, and the system automatically routes the distributed users to the specified MSC server.
NOTE This method aims to reduce the dependence on the access network when users are manually transferred. The operation can be independently performed in the CN by distributing the NRI of the destination MSC server. This also reduces the operations that must be performed on both the CN and access network.
1. On the MSC server and the RNC/ BSC, set the MSC server where users are transferred to the off-load status. 2. When an MS/UE registered in the off-load MSC server initiates a location update request or service release request, the MSC server initiates the location update request to the destination MSC server based on the redirection message. 3. Upon receiving the request, the destination MSC server encrypts the authentication, obtains the ID, checkimei, and TMSI redistribution message from the MS/ UE, and then sends the information to the originating MSC server. The originating MSC server interacts with the MS/UE. In addition, the destination MSC server initiates the location update to the HLR and finally distributes, by using the TMSI, a TMSI containing the NRI of the destination office to the MS/UE. Thus, the subsequent location updates or service requests are directly delivered to the destination MSC server. 4. After transferring users, restore the state of the MSC server on the MSC server and the RNC/BSC through the M2000.
Related Tasks
12.5.1.3 Manual Transfer of Users
Related References
12.6.7 Parameters for Transferring MSC Pool Users Manually
Issue 06 (2008-12-16)
12-9
12.1.4 MSC Pool Networking Application

The MSC Pool scheme is applicable to a hybrid network of GSM, and WCDMA. The MSC Pool network consists of core network comprising MSC server and the MGW, and access network NEs such RNC, BSC, or RNC&BSC. According to the 3GPP 23.236 protocol, the RNC/BSC in an MSC Pool must support the Iu/AFlex function. The RNC/BSC on the current network, however, does not support the Iu-A-Flex function. In addition, the Iu/A-Flex function supported by RNCs/BSCs manufactured by different vendors is not consistent. To solve this problem, Huawei MGW can be used to act as the Iu/A-Flex agent. In this way, RNCs/BSCs on the present network can access the MSC Pool without upgrade. Table 12-4 describes the application scenarios of MSC Pool networking. Table 12-4 Scenarios of MSC Pool Application Scenario Creating a GSM network having the MSC Pool structure Networking Scheme
l
The core network uses the softswitch structure. The MSC server and MGW collectively perform the MSC function. The access network uses the BSS system. The BSC supports the A-Flex function. No special requirements are needed for the MGW. The core network uses the softswitch structure. The MSC server and MGW collectively perform the MSC function. The access network uses the BSS system. The BSC supports the A-Flex function. The MGW performs the A-Flex function. The core network uses the softswitch structure. The MSC server and MGW collectively perform the MSC function. The access network uses the RAN system. The RNC supports the Iu-Flex function. No special requirements are needed fro the MGW. The core network uses the softswitch structure. The MSC server and MGW collectively perform the MSC function. The access network uses the RAN system. The RNC supports the Iu-Flex function. The MGW performs the Iu-Flex function.
Evolve the existing GSM network to the MSC Pool network
Creating a WCDMA network having the MSC Pool structure
Evolve the existing WCDMA network to the MSC Pool network
12-10
Issue 06 (2008-12-16)
Application Scenario Create a hybrid network comprising the GSM and WCDMA
Networking Scheme
l
The core network uses the softswitch structure. The MSC server and MGW collectively perform the MSC function. The access network side uses the BSS and RAN system. The BSC and RNC can connect to the same MGW. Based on the data configuration, the MGW identifies whether it needs to perform the Iu-Flex or A-Flex function for the BSC and the RNC.
CAUTION
On the M2000 client, you can view the RNC/BSC for which the MGW is the agent. For details, see 12.4.6 Viewing the Proxy Relation Between the MGW and the RAN.
12.1.5 User Authority Management of the MSC Pool

A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. After purchasing the license of the M2000 MSC Pool and being granted the relevant right, you can perform the operations related to the MSC Pool on the M2000 client. The M2000 performs the following functions in the MSC Pool:
l l
Centrally configuring and managing the parameters associated with MSC Pool features. Supporting real-time load monitoring with the minimum period as 30 seconds and monitoring idle users, powered-off users, users in conversation, total users, CPU usage, and MGW contexts. Supporting the statistics on the entire office performance, applying common KPIs on the MSC Pool level, and providing global KPIs of the MSC Pool. Supporting data consistency check and synchronization. You can periodically or manually check whether the configuration data on each NE is consistent within the Pool. If data inconsistency exists, a synchronization script is generated to achieve consistency. Supporting user transfer within the Pool and thus ensuring the load balance between the MSC servers in the Pool. Enabling you to quickly find the MSC server where the specified user is located.
For details about the operations and required rights, see Table 12-5. For details of the MSC Pool operation authorities, see Table 12-6.
Issue 06 (2008-12-16)
12-11
Table 12-5 MSC Pool operation settings Operation Monitor loads in real time, search for users, manually check MSC Pool data, browse MSC Pool information, and view Pool topology Authority Setting The MSC Pool is within the management domain of the user. That is, the user is authorized to perform the operations on the MSC Pool. For details about how to set a user management domain, refer to 4.5.11 Setting the Managed Domain for an OM User. Create/modify/delete the MSC Pool, set Pool alarm parameters, browse Pool performance, transfer users, manage Pool data auto-check task, configure Pool parameters, and synchronize Pool data The user has the corresponding operation rights. For details, see Table 12-6. For details on user operation rights, see 4.5.10 Assigning Operation Rights to an OM User.
Table 12-6 MSC Pool operation rights list Bound privileges Creating an MSC Pool Description You can create an MSC Pool after being granted the operation right.
NOTE
l After a user creates an MSC
Type Network management application authority
Pool, the user is automatically authorized to modify, delete, and view the pool.
l After a user is authorized to
create, modify, or delete an MSC Pool, the system automatically grants the view right of the pool to the user. That is, the user can view the pool in the administration domain.
Setting advanced alarm parameters
After being granted the authority, you can set the threshold for setting Pool load imbalance alarms. After being granted this right, you can modify the basic information about an MSC Pool, such as Pool name, description, and NEs. You can delete an MSC Pool after being granted the operation right.
Network device right
Adjust the MSC Pool by adding or deleting NEs
Delete an MSC Pool
12-12
Issue 06 (2008-12-16)
Bound privileges Configure the MSC Pool parameters
Description After being granted this right, you can configure the parameters related to Pool properties, such as NRI, Null NRI, the relation between the NRI and CN ID. After being granted this right, you can re-distribute users between MSC servers. After being granted this right, you can synchronize the data between MSC servers with an MSC Pool or the data between MGWs. In this way, you can ensure the data consistency. After being granted this right, you can set auto-check tasks for MSC Pool data, such as creating, modifying, suspending, and activating tasks, and browsing task information.
Type Network device right
Load re-distribution
Synchronize the check results to the NE
Manage auto check tasks
NOTE
By default, the Guests and Operators user groups have the new device right of the MSC Pool. For details of the new device right, refer to 4.6.2.3 Modifying the Authority to the New Devices in an OM User Group. The right to perform the Pool takes precedence over the right to perform the NEs within the Pool. That is, an authorized user can perform a Pool function even if the user is not authorized to perform the supporting function. For example, to configure the Pool parameters, a user needs to send the modification command to the NEs within the Pool. If the user is authorized to configure parameters for the Pool but is not authorized to issue commands to NEs within the Pool, the user can still issue NE configurations to the NEs.
12.2 Creating MSC Pool Topology on the M2000

This describes how to create an MSC Pool for all related NEs so that you can perform related operations on the M2000.
Prerequisite
l
The radio access network NEs support the Iu/A-Flex function and they are configured on the basis of network planning. Relevant NEs have been connected to the M2000. You are authorized to create an MSC Pool.
l l
Issue 06 (2008-12-16)
Procedure
Step 1 Choose Maintenance > Pool Management or click Management window is displayed. on the toolbar. The Pool
Step 2 In the navigation tree, right-click the MSC Pool node and choose Create MSC Pool from the shortcut menu. Step 3 Set the pool information in the displayed Create MSC Pool dialog box. 1. 2. 3. Enter the Pool name in Pool Name. Select the networking type of the Pool on right of the Pool Name box. Select the NEs to be added to the Pool in Optional Nes. Click NEs are added to Selected Nes.
l l l
. Then the
In Selected Nes, you can use Shift or Ctrl to select multiple NEs at the same time. You can click You can click Selected Nes. to add all the NEs in Optional Nes to Selected Nes. or to remove the selected NEs from
For the detailed description of parameters, see 12.6.4 Parameters for Creating/Modifying MSC Pool. Step 4 Click OK. A Message box showing that the Pool is successfully created is displayed. You can view the created MSC Pool in the navigation tree on the MSC Pool Management window. Step 5 Click OK to close the Message dialog box. The Confirm dialog box is displayed, asking you whether to configure the parameters.
l
To configure the parameters immediately, click OK. For details, see 12.3.3 Setting the Attributes of MSC Pool. To configure the parameters later, click Cancel to close the dialog box.
----End
Postrequisite
1. After a pool is created, you need to perform initial configuration and data check for the pool to check whether the configurations of the MSC Pool are correct. For details about how to perform initial configuration for the pool, refer to 12.3 Initial Configuration of MSC Pool. For details about how to perform data check, refer to 12.5.2.2 Manually Checking MSC Pool Data. If the configuration data that must be consistent with all NEs in the pool is inconsistent, you need to synchronize the data on the basis of reference values. For details, refer to 12.5.2.4 Synchronizing MSC Pool Data. 2. After the data are correctly configured, you can start the pool to perform routine operations and maintenance. For details about routine operations and maintenance, refer to 12.4 Routine Maintenance of MSC Pool.
Related References
12.6.4 Parameters for Creating/Modifying MSC Pool 12.6.3 Interface Description: MSC Pool Configuration 12.6.4 Parameters for Creating/Modifying MSC Pool 12.6.3 Interface Description: MSC Pool Configuration
12.3 Initial Configuration of MSC Pool

This describes how to perform the initial configuration for the MSC Pool. After you create a new MSC Pool, you should perform the initial configuration. The configuration includes tasks such as setting an alarm for MSC Pool load unbalance, creating an auto-check task for the MSC Pool, and setting attributes for the MSC Pool. The configuration enables you to monitor and maintain the MSC Pool network in the future. 12.3.1 Setting an Alarm for MSC Pool Load Imbalance This describes how to set an alarm for the MSC Pool load unbalance. After you set an alarm for MSC Pool load imbalance, the system can periodically checks the load of the MSC servers in the MSC Pool. The system reports the alarm for the MSC Pool load unbalance when the deviation between the highest load and the lowest load exceeds the configured threshold. You can perform load transfer according to the alarm information to facilitate balancing loads. 12.3.2 Creating the Task of Auto-Checking MSC Pool In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. The M2000 provides the function of automatically checking the data that must be consistent on the NEs. You can set the related parameters so that the M2000 can check the data periodically. If inconsistent data exists, an alarm is raised. 12.3.3 Setting the Attributes of MSC Pool This describes how to set the attributes of the MSC Pool. You must ensure that the settings of the parameters closely related to Pool features, such as the NRI and load balancing, are consistent between the radio access network side and the core network side. The M2000 provides the centralized management function and supports one-click upgrade for maintenance of the parameters on various NEs. This reduces the pool parameter maintenance workload and ensures the correctness of Pool parameter configuration.
12.3.1 Setting an Alarm for MSC Pool Load Imbalance

This describes how to set an alarm for the MSC Pool load unbalance. After you set an alarm for MSC Pool load imbalance, the system can periodically checks the load of the MSC servers in the MSC Pool. The system reports the alarm for the MSC Pool load unbalance when the deviation between the highest load and the lowest load exceeds the configured threshold. You can perform load transfer according to the alarm information to facilitate balancing loads.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform the associated operations.
Context
The type of the MSC Pool load unbalance alarm is Fault Alarm, and the alarm severity is Critical. For details, see ALM-1 Load Unbalance Alarm.
Procedure
Step 2 In the navigation tree, select the MSC Pool whose alarms for load unbalance need to be set. Right-click the pool and select Property from the shortcut menu. Step 3 In the navigation tree in the left pane of the Pool Property Settings dialog box, select Alarm Load Balance Parameters and set the alarm threshold and automatic check period. See 12.6.16 Parameters for Setting Load Unbalance Alarm for the details of parameters. Step 4 Click OK. The Message dialog box is displayed, showing the operation results.
NOTE
If the configuration of alarm parameters fails, the detailed reason for the failure is displayed in the Message dialog box.
Step 5 Click OK. The Message dialog box is closed. ----End
Result
When an alarm for load unbalance is generated, the MSC Pool Management interface displays the message Pool load balance status:Abnormal in red.
Postrequisite
l
You can check detailed information about the Pool load unbalance by querying fault alarms. For details, refer to 12.4.1.1 Viewing the Current Fault Alarms of MSC Pool. When a load unbalance alarm is generated, you can manually transfer MSC server users to balance the load of each MSC server in the Pool. For details, refer to 12.5.1.3 Manual Transfer of Users.
Related References
12.6.16 Parameters for Setting Load Unbalance Alarm
12.3.2 Creating the Task of Auto-Checking MSC Pool

In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. The M2000 provides the function of automatically checking the data that must be consistent on the NEs. You can set the related parameters so that the M2000 can check the data periodically. If inconsistent data exists, an alarm is raised.
Prerequisite
l l
12-16
Issue 06 (2008-12-16)
Context
The type of the alarm about inconsistent MSC Pool data is event alarm, and the alarm severity level is critical. For details, see ALM-2 Data Inconsistency Alarm.
NOTE
You can manually check MSC Pool data. If the inconsistent data has no effect on the MSC Pool service, you can shield this data. The shielded data will not be checked in future checks. For details, see 12.5.2.3 Setting the Checking Items of MSC Pool Data.
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to mange auto-check tasks, and choose Data Consistency Check > Automatic Check from the shortcut menu. Step 3 In the displayed Automatic Check dialog box, click the Check Task tab. In the displayed tab page, click Add. Step 4 Set the parameters of the automatic check task. 1. 2. 3. Select the NE type from the Choose NE Type drop-down list. Enter the task name in Task Name. Select the NE whose data needs be checked in Select NE.
NOTE
You must select at least two NEs.
4. 5. 6.
Select the data items in the Select Data Item group box. You can use the Find box to quickly find the data item to be checked. Select the period for checking the data from the Check Period drop-down list. Set the check time in Check Time.
For the detailed description of parameters, see 12.6.9 Parameters for Setting the Auto-Check of MSC Pool. Step 5 Click OK. The added automatic check task is displayed on the Check Task tab page. ----End
Result
If inconsistent data is found, the system reports a critical event alarm.
Postrequisite
If inconsistent data exists, you can perform the following operations: 1. 2. Check the result to get the information about the inconsistent data. For details, see 12.5.2.1 Viewing the Result of Auto-Checking MSC Pool Data. On the Check Result tab page of the Automatic Check dialog box, click Manual Check to check the data again.
Issue 06 (2008-12-16)
3.
Manually synchronize the inconsistent data to ensure consistency. For details, see 12.5.2.4 Synchronizing MSC Pool Data.
Related Tasks
12.5.2 Checking MSC Pool Data 12.5.2.3 Setting the Checking Items of MSC Pool Data 12.5.2.3 Setting the Checking Items of MSC Pool Data
Related References
12.6.9 Parameters for Setting the Auto-Check of MSC Pool
12.3.3 Setting the Attributes of MSC Pool

This describes how to set the attributes of the MSC Pool. You must ensure that the settings of the parameters closely related to Pool features, such as the NRI and load balancing, are consistent between the radio access network side and the core network side. The M2000 provides the centralized management function and supports one-click upgrade for maintenance of the parameters on various NEs. This reduces the pool parameter maintenance workload and ensures the correctness of Pool parameter configuration. 12.3.3.1 Parameters of MSC Pool Attributes This describes the parameters of MSC Pool attributes and the function of each parameter. 12.3.3.2 Viewing the Attributes of MSC Pool This describes how to view and set the parameters of the MSC Pool on the M2000 client. 12.3.3.3 Setting CN ID of an MSC Server A CN ID identifies an MSC server in the Pool. When the network planning is changed or incorrect, you can modify the CN ID of the SGSN on the M2000 client. 12.3.3.4 Adding the NRI of MSC Pool This describes how to add the NRI of MSC Pool. Because the NRI occupies the user identification resources of the TMSI, you can enlarge the user numbers of the MSC server by increasing the NRI of the MSC server when current TMSI digits cannot handle the actual user numbers. 12.3.3.5 Setting the Mapping Between NRI and CN ID This describes how to set the mapping relation between the NRI and the CN ID. Then the NNSF node such as MGW, RNC, and BSC, can route the MS/UE to the related MSC server. You can change the setting of the mapping relation between the NRI and the CN ID through the M2000 when faults occur during network planning or NRI planning adjustment. 12.3.3.6 Setting the Null NRI or the Length of NRI This describes how to set the Null NRI or the length of the NRI. When the network planning changes or the valid length of the NRI digits changes as a result of the lack of NRI resources, you can re-define the NRI length through the M2000. Based on the NRI length, the NNSF nodes such as the MGW, RNC, and BSCobtain NRI information from the TMSI and route the MS to the relevant MSC server. The Null NRI value is used to coach the NNSF nodes to re-select an MSC server for the MS/UE. 12.3.3.7 Setting the Load Balancing Parameters of MSC Pool This describes how to set the load balance parameters of the MSC Pool. After setting up an MSC Pool, you should specify the user capacity of each MSC server in the MSC Pool. In this way,
you can balance user allocation according to the defined user capacity when guiding the RNC/ BSC to access users. 12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool This describes how to set the non-broadcast LAIs of the MSC Pool. When the users in the MSC Pool are transferred, the destination MSC server determines the address of the original MSC server of the MS/UE on the basis of the non-broadcast LAI and obtains users' information. The non-broadcast LAI of each MSC server is set during network planning. You can modify the network settings through the M2000 when the setting is incorrect. 12.3.3.9 Setting the Maintenance State of NEs in MSC Pool This describes how to manually set the maintenance state of the NEs in the MSC Pool when you need to segregate the MGW or perform user transfer. The NE maintenance status can be MGW Segregate Status and CN Node Status. 12.3.3.10 Setting the Operator for MSC Pool This describes how to set the operator for the MSC Pool. When the access side of the MSC Pool supports network sharing, you need to set the operator of the MSC Pool.
Parameters of MSC Pool Attributes

This describes the parameters of MSC Pool attributes and the function of each parameter. For detailed description about the MSC Pool attribute parameters, refer to Table 12-7.
CAUTION
When the MSC Pool consists of only the radio access network NEs, the following parameters cannot be configured on the M2000 client:
l l l
CN ID Non-broadcast LAI MGW Segregation Status
Table 12-7 Parameters of Pool attributes Parameter CN ID Meaning Core network identifier. Impact on the MSC Pool Execution A CN ID identifies an MSC server in the Pool.
Issue 06 (2008-12-16)
12-19
Parameter NRI
Meaning Network resource identifier.
Impact on the MSC Pool Execution Used to identify an MSC server One MSC server may have multiple NRIs. The NRIs within the Pool or within the intersection between Pools cannot be duplicate. The NRIs used in two separate Pools can be duplicate. When an MS/UE initially registers to an MSC server in the MSC Pool, the MSC server distributes the TMSI that contains the NRI of the MSC server to the MS/UE. In this case, when the MS/UE initiates the services again, it carries the NRI information. By using the NRI information, the NNSF node, that is, the MGW, RNC,orBSC, routes the MS initiated services to the NRI related MSC server. In this way, when the MS/UE roams in the MSC Pool area, it uses the same MSC server. Compared with the traditional networking, this function can reduce the location updating signaling message over the C and D interfaces.
12-20
Issue 06 (2008-12-16)
Parameter Non-broadcast LAI
Meaning Special LAI. The special LAI has the same coding system as the common LAI. LAI indicates the local area identifier.
Impact on the MSC Pool Execution The functions of the Nonbroadcast LAI are as follows:
l
During user transfer, Nonbroadcast LAI can be used to trigger the immediate location update of an MS/UE after the current service is complete. When the user transfers, the destination MSC server determines the address of the original MSC server that serves the MS/UE based on the Non-broadcast LAI. At the same time, the destination MSC server obtains the user information such as the user's IMSI and the unused encrypted parameters.
NOTE Each MSC server in the MSC Pool has a unique Non-broadcast RAI. Each MSC server must be able to identify the Non-broadcast RAIs of other MSC servers in the same MSC Pool.
Pool Available Capacity
Indicates the actual user capacity of the MSC server in the Pool. The pool available capacity is the converted capacity value of the license capacity. For example, if an MSC server in the pool is connected to an RNC orBSCoutside the pool, the pool available capacity of the MSC server in the pool equals the user capacity provided outside the pool subtracted from the license capacity.
NOTE The user capacity for an RNC orBSC outside the Pool is defined during the planning of the MSC Pool network.
After a pool is initially established, by setting the pool available capacity of the MSC server, you can balance user allocation when guiding the NNSF node, that is, MGW, RNC andBSC, to access users.
Issue 06 (2008-12-16)
12-21
Parameter MGW Segregation Status
Meaning The MGW states are Normal and Segregate.

NOTE The MGW refers to the VMGW that acts as an agent of the Iu-Flex function.
Impact on the MSC Pool Execution By setting the MGW status to Segregate, the MGW exits smoothly and has no impact on the users' services. For detailed description of MGW status, refer to 12.6.14 Parameters for Setting NE State of MSC Pool. By setting OffLoad or Forbidden for the MSC server, you enable the MSC server to smoothly exit without affecting user services. For detailed description of MSC server status, refer to 12.6.14 Parameters for Setting NE State of MSC Pool.
VMGWs are logically divided MGWs. CN Node State Status of the MSC servers in the Pool, such as Normal, OffLoad, and Forbidden.
Iu/A-Flex Activated Status
Displays whether the Iu/AFlex function is supported by the NEs within the pool.
l
The prerequisite for joining the Pool is that the related CN NEs support the Iu/A-Flex function.
True: indicates that NEs within the pool support the Iu/A-Flex function. False: indicates that NEs within the pool do not support the Iu/A-Flex function.
NOTE Iu/A-Flex function refers to the function that enables an RNC orBSC to connect multiple CNs.
12-22
Issue 06 (2008-12-16)
Parameter NRI Length
Meaning The NRI is included in the TMSI distributed to the MS/ UE by the MSC server. The NRI length refers to the length of the NRI in the TMSI. As shown in Figure 12-3, the NRI is located between the 23rd bit and the 14th bit of the TMSI. The length is adjustable, that is, from 0 to 10 (unit: bit). When the length of the NRI is not 0, the NRI begins with the 23rd bit. When the length of the NRI is 0, you can infer that the MSC Pool function is not supported.
Impact on the MSC Pool Execution Only when the length of the NRI is set, the NNSF node, that is, the MGW, RNC, orBSC, can obtain the NRI information from the TMSI based on the length of the NRI, and thus route the MS to the related MSC server.
NOTE
l The length of the NRI configured
for different MSC servers and different RNCs orBSCswithin the MSC Pool should be the same.
l In the event of overlapping pool
area, the length of the NRI configured for each RNC orBSCwithin the MSC Pool area and the length of the NRI for each MSC server within the MSC Pool should be equal.
Null NRI
A special NRI, which has the same coding with the common NRI.
When the user transfers, the null NRI is used to instruct the RNC orBSC to select another MSC server for the MS/UE. Within the MSC Pool of a single operator, the Null NRI is unique. When Multi-Operator Core Network (MOCN) is supported, however, different operators within the MSC Pool have different Null NRIs. That is, each CN operator has a unique Null NRI.
Figure 12-3 TMSI Structure
31st bit-30th bit: indicator of the CS or PS service. 29th bit: count of VLR restarts. 23rd bit-nth bit (n14): NRI Other bits: user identifiers.
Issue 06 (2008-12-16)
12-23
Related Tasks
12.3.3.3 Setting CN ID of an MSC Server 12.3.3.4 Adding the NRI of MSC Pool 12.3.3.5 Setting the Mapping Between NRI and CN ID 12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool 12.3.3.7 Setting the Load Balancing Parameters of MSC Pool 12.3.3.9 Setting the Maintenance State of NEs in MSC Pool 12.3.3.6 Setting the Null NRI or the Length of NRI 12.3.3.10 Setting the Operator for MSC Pool
Related References
12.6.10 Parameters for Setting CN ID of an MSC Server 12.6.11 Parameters for Setting NRI of an MSC Pool 12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool 12.6.13 Parameters for Setting Load-Balancing of an MSC Pool 12.6.14 Parameters for Setting NE State of MSC Pool 12.6.15 Parameters for Superior Settings
Viewing the Attributes of MSC Pool

This describes how to view and set the parameters of the MSC Pool on the M2000 client.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool of which you plan to view the attributes, and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting dialog box. If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the Advanced Setting tab and set the parameters.
Step 3 Click the related tabs to perform the required settings.

For details about each tab page, see 12.6.3 Interface Description: MSC Pool Configuration. ----End
Setting CN ID of an MSC Server

A CN ID identifies an MSC server in the Pool. When the network planning is changed or incorrect, you can modify the CN ID of the SGSN on the M2000 client.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool whose CN ID needs to be redefined, and then choose Pool Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the CN ID tab, and then select from the list the MSC server whose CN ID needs to be set. Step 4 Double-click the record or click Modify. The Modify dialog box is displayed. Step 5 Enter a value in the CN ID field. For details of the parameters, see 12.6.10 Parameters for Setting CN ID of an MSC Server. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC servers within the pool, and displays the Send Status and Send Result of the command.
NOTE
l l
When the system is issuing MML commands, you can click Stop to prevent the system from issuing the commands that have not been issued yet. If all MML commands fail to be run, you can click Send to issue the MML commands again. If part of the MML commands are issued, the Send button is unavailable. You can infer that the command cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box. ----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.10 Parameters for Setting CN ID of an MSC Server
Adding the NRI of MSC Pool

This describes how to add the NRI of MSC Pool. Because the NRI occupies the user identification resources of the TMSI, you can enlarge the user numbers of the MSC server by increasing the NRI of the MSC server when current TMSI digits cannot handle the actual user numbers.
Prerequisite
l l
Context
You should add the NRI of the MSC server through the M2000 when the MSC server in the MSC Pool increases.
CAUTION
The change of NRI greatly affects network services. It is recommended that you confirm the change during the network planning and then add the NRI on the M2000 client.
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to which you plan to add the NRI, and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
12-26
Issue 06 (2008-12-16)

NOTE
Step 3 Click the CN ID-NRI Setting tab and click Add. The Add dialog box is displayed. Step 4 Set the NRI related parameters. 1. 2. In the MSC server drop box, select the MSC server that needs to add the NRI. Enter the NRI value in NRI.
CAUTION
The added NRI value cannot be the same as the existed NRI values in the Pool. See 12.3.3.1 Parameters of MSC Pool Attributes for detailed information on the NRI. Step 5 Click OK. Step 6 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within the pool, and displays the Send Status and Send Result of the command.
NOTE
l l
Step 7 Click Close to close the The MML Commands send to NE dialog box. Step 8 In Step 6, if part of the MML commands are issued, then the Consistency in the CN ID-NRI Setting tab is Inconsistent. You should clickSynchronize and then Send ensure that the NRI of a specific MSC server is consistently configured on all the NEs within the Pool. Step 9 Click Close to close the Pool Parameter Settings dialog box. ----End
Related Concepts
Related References
12.6.11 Parameters for Setting NRI of an MSC Pool
Setting the Mapping Between NRI and CN ID

This describes how to set the mapping relation between the NRI and the CN ID. Then the NNSF node such as MGW, RNC, and BSC, can route the MS/UE to the related MSC server. You can change the setting of the mapping relation between the NRI and the CN ID through the M2000 when faults occur during network planning or NRI planning adjustment.
Prerequisite
l l
Context
The NNSF node refers to the NE node that provides the NNSF function, that is, the MSC server that is used to select service for an MS/UE. For example, an NNSF node can be an MGW, RNC, or BSC.
CAUTION
Different Pool networking types have different implications for operations such as modification and deletion. For details, refer to Table 12-8.
Table 12-8 Description of the operations Pool Net Type Pool including the CN NEs Modification: Operation
l
Modification: indicates that only the NRI configured on a specific MSC server is modified. Deletion: indicates that only the NRI configured on a specific MSC server is deleted. Modification: indicates that the NRI of a specific MSC server, which is configured on all RNCs/ BSCs, is modified. Deletion: indicates that the NRI of a specific MSC server, which is configured of all RNCs/BSCs, is deleted.
Pool that contains the NEs only from the radio access network
Procedure
Step 2 In the navigation tree, right-click the MSC Pool on which you plan to set the mapping between NRI and CN ID, and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.

NOTE
Step 3 Click the CN ID-NRI Setting tab, and then select from the list the NRI record that needs to be set. Step 4 Double-click the record or click Modify. The Modify dialog box is displayed. Step 5 Enter the new NRI value in the NRI field.
CAUTION
The new NRI value should be unique. For detailed description about the mapping relation between the NRI and the CN ID, refer to 12.3.3.1 Parameters of MSC Pool Attributes. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC Servers in the local office, and displays the Send Status and Send Result of the command.
NOTE
l l
Step 8 Click Close to close the The MML Commands send to NE dialog box. Step 9 Click Close to close the Pool Parameter Settings dialog box. ----End
Result
l
On the CN ID-NRI Setting tab page, a new record is added to the task list, displaying the new NRI-related information. The former NRI record, that is, in the NE Name column, Unknown ne is displayed.
Postrequisite
After successfully changing the NRI of the MSC server in the local office, you need to select the changed NRI record in the list, click Synchronize and then Send. Then the changed NRI is applied to all the other MSC servers, MGWs, and RNCs/BSCs in the MSC Pool.
Related Concepts
Related References
Setting the Null NRI or the Length of NRI

This describes how to set the Null NRI or the length of the NRI. When the network planning changes or the valid length of the NRI digits changes as a result of the lack of NRI resources, you can re-define the NRI length through the M2000. Based on the NRI length, the NNSF nodes such as the MGW, RNC, and BSCobtain NRI information from the TMSI and route the MS to the relevant MSC server. The Null NRI value is used to coach the NNSF nodes to re-select an MSC server for the MS/UE.
Prerequisite
l l
Context
CAUTION
The re-definition of the NRI length may affect the services near the Pool. Re-plan the NRI of the Pool on the entire network before performing this operation.
Procedure
Step 2 In the navigation tree, choose the MSC Pool whose NRI length or the Null NRI value needs to be re-defined, and then right-click Pool Parameter Setting. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the Advanced Setting tab. Click Set in the NRI group box. Step 4 Re-define the NRI length or the Null NRI value in the displayed Modify dialog box.
For detailed information on the NRI length and Null NRI, see 12.3.3.1 Parameters of MSC Pool Attributes. Step 5 Click OK. Step 6 In the displayed dialog box, click Yes. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within the Pool, and displays the Send Status and Send Result of the command.
NOTE
l l
Related Concepts
Related References
12.6.15 Parameters for Superior Settings
Setting the Load Balancing Parameters of MSC Pool

This describes how to set the load balance parameters of the MSC Pool. After setting up an MSC Pool, you should specify the user capacity of each MSC server in the MSC Pool. In this way, you can balance user allocation according to the defined user capacity when guiding the RNC/ BSC to access users.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, select the MSC Pool whose parameters for load balance need to be set. Right-click the pool and select Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.

NOTE
Step 3 Click the Load Balance Parameter tab, and choose the MSC server record whose available capacity needs to be re-defined.
l l
You can view the license capacity of each MSC server in the pool on the Load Balance Parameter tab page. The maximum license capacity cannot be modified. For detailed description of the parameters on the Load Balance Parameter tab page, refer to 12.6.13 Parameters for Setting Load-Balancing of an MSC Pool.
Step 4 Double-click the record or click Modify. The system displays the Modify dialog box. Step 5 Enter the new available capacity of the MSC server in New Pool Available Capacity. See 12.3.3.1 Parameters of MSC Pool Attributes for detailed information on the Pool available capacity. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within the pool, and displays the Send Status and Send Result of the command.
NOTE
l l
Step 8 Click Close to close the The MML Commands send to NE dialog box. Step 9 In Step 7, if part of the MML commands are issued, then the Consistency in the Load Balance Parameter tab is Inconsistent. You should clickSynchronize and then Send to make the pool available capacity of the MSC server consistent on all MSC servers, MGWs and RNCs/BSCs. Step 10 Click Close to close the Pool Parameter Settings dialog box. ----End
Related Concepts
Related References
12.6.13 Parameters for Setting Load-Balancing of an MSC Pool
Setting the Non-Broadcast LAIs of MSC Pool

This describes how to set the non-broadcast LAIs of the MSC Pool. When the users in the MSC Pool are transferred, the destination MSC server determines the address of the original MSC
server of the MS/UE on the basis of the non-broadcast LAI and obtains users' information. The non-broadcast LAI of each MSC server is set during network planning. You can modify the network settings through the M2000 when the setting is incorrect.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool whose Non-broadcast LAI needs to be redefined, and then choose Pool Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the Non-broadcast LAI Setting tab, and select the MSC server record whose nonbroadcast LAI needs to be re-defined. Step 4 Double-click the record or click Modify. The Modify dialog box is displayed. Step 5 Enter a new value in New non-broadcast LAI. See 12.3.3.1 Parameters of MSC Pool Attributes for detailed information about the nonbroadcast LAI. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MSC servers within the pool, and displays the Send Status and Send Result of the command.
NOTE
l l
Step 9 In Step 7, if part of the MML commands are issued, then the Consistency in the Non-broadcast RAI Setting tab is Inconsistent. You should clickSynchronize and then Send to make the Nonbroadcast LAIs of an MSC server consistent on all MSC servers.. Step 10 Click Close to close the Pool Parameter Settings dialog box. ----End
Related Concepts
Related References
12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool
Setting the Maintenance State of NEs in MSC Pool

This describes how to manually set the maintenance state of the NEs in the MSC Pool when you need to segregate the MGW or perform user transfer. The NE maintenance status can be MGW Segregate Status and CN Node Status.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to which you plan to set the NE maintenance state, and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the NE Status Maintenance tab, and choose the NE status in the Choose Status Type drop box according to the requirements of network maintenance. Requirements of network maintenance Network Maintenance Requirements Status Type Segregate the MGW. Select MGW Segregate Status.
12-34
Issue 06 (2008-12-16)
Requirements of network maintenance Network Maintenance Requirements Perform user transfer. Select CN Node Status.
Step 4 Choose the NE record that needs to set the status. Double-click the record or click Modify. Step 5 Choose the NE status according to your requirements in the Set Status drop box. See 12.6.14 Parameters for Setting NE State of MSC Pool for detailed information about the meaning of NE status. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. For the CN node status, the system issues MML commands to all the MGWs and RNCs/BSCs within the pool. For the MGW segregate status, the system issues MML commands to all the MSC servers within the pool. The system also displays Send Status and Send Result of the MML commands.
NOTE
l l
Related Concepts
Related References
12.6.14 Parameters for Setting NE State of MSC Pool
Setting the Operator for MSC Pool

This describes how to set the operator for the MSC Pool. When the access side of the MSC Pool supports network sharing, you need to set the operator of the MSC Pool.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the associated operations. CN NEs exists in the MSC Pool.
Issue 06 (2008-12-16)
12-35
Context
NOTE
l l
You can view the information about the radio access network NEs in the Parameter Setting dialog box only after you specify the operator of the Pool. The M2000 provides this function only when the networking type of the MSC Pool is Radio Access Network Only or Core&Radio Access Network.
Procedure
Step 2 In the navigation tree, right-click the MSC Pool whose operator needs to be set, and then choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is updated, a Message box is displayed, informing you that the operator identity is not set. Step 3 In the displayed Message dialog box, click OK. Step 4 Click the Advanced Setting tab. Click Set in the PLMN group box. Step 5 In the displayed Modify dialog box, enter a new MCC and MNC. For description of the related parameters, see 12.6.15 Parameters for Superior Settings. Step 6 Click OK. The displayed dialog box shows whether the operation is successful. Step 7 Click OK to close the dialog box. ----End
Related Concepts
Related References
12.4 Routine Maintenance of MSC Pool

This describes how to perform routine maintenance for the MSC Pool on the M2000 client. The maintenance and operation tasks include checking the MSC Pool alarms , measuring the MSC Pool performance, monitoring the load of the MSC Pool in real time, checking the MSC server where the specific user is located, displaying the MSC Pool topology, and managing the autocheck task of the MSC Pool. 12.4.1 Viewing the Alarms of MSC Pool This describes how to view the alarms of MSC Pool. By viewing the alarms of the MSC Pool, you can monitor the network alarms to perform maintenance. MSC Pool alarms have two types: load unbalancing alarm, which is a fault alarm, and data inconsistency alarm, which is an event alarm.
12.4.2 Monitoring the Load of MSC Pool in Real Time This describes how to monitor the load of the MSC Pool in real time. In normal situations, the load balancing algorithm of the system ensures load balance of the MSC Pool. 12.4.3 Viewing the Operation Logs of MSC Pool This describes how to view the operation logs of an MSC Pool. The operation logs of MSC Pool record the operations related to the MSC Pool. 12.4.4 Viewing the MSC Where a Specific User Is Located This describes how to view the MSC where a specific user is located. In the MSC Pool, an RNC/ BSC does not map to an MSC server. The users under the same RNC/BSC may also be distributed to different MSC servers. The M2000 provides the Subscriber Search function. By using this function, you can quickly find the MSC server where a specific user is located. 12.4.5 Viewing the Relation Between the MGW and the RAN This describes how to view the relation between the the MGW and the RAN. 12.4.6 Viewing the Proxy Relation Between the MGW and the RAN 12.4.7 Displaying MSC Pool Topology This describes how to display the MSC Pool topology. The MSC Pool topology is used to display the logical networking structure of the MSC Pool. 12.4.8 Managing the Task of Auto-Checking MSC Pool This describes how to manage the task of auto-checking the MSC Pool. You can modify and delete the tasks of auto-checking the MSC Pool. 12.4.9 Viewing the MSC Pool Performance Report After an MSC Pool is created, counters of a single NE, such as mobile office direction traffic, call connection ratio, call drop rate, and local network traffic, fail to serve as the statistical information about the entire network. By querying the MSC Pool performance report, you can summarize the performance data reported by NEs and get the counter data applicable for the entire network.
12.4.1 Viewing the Alarms of MSC Pool

This describes how to view the alarms of MSC Pool. By viewing the alarms of the MSC Pool, you can monitor the network alarms to perform maintenance. MSC Pool alarms have two types: load unbalancing alarm, which is a fault alarm, and data inconsistency alarm, which is an event alarm.
Context
l
For details of the operations related to the alarms, such as synchronizing, printing, and confirming the alarm, refer to 2.2 Monitoring Network Alarms. On the Pool Management interface, you can right-click an MSC Pool in the navigation tree and choose Query Alarm > History Fault Alarm from the shortcut menu to view the history fault alarms of MSC Pool. For details, refer to 2.2.7.2 Querying History Fault Alarms.
12.4.1.1 Viewing the Current Fault Alarms of MSC Pool Fault alarms of MSC Pool refer to the alarms that are raised because of unbalanced loads. You can set multiple query conditions to quickly locate the unbalanced loads to perform maintenance. 12.4.1.2 Viewing the Event Alarms of MSC Pool This describes how to view the event alarms of MSC Pool. Event alarms of MSC Pool are mainly generated because of data inconsistency between MSC servers or MGWs in the MSC Pool. You
can set multiple query conditions to quickly locate the inconsistent data. Thus you can synchronize them in time to ensure the normal operation of the MSC Pool.
Related References
12.6.2 Interface Description: Viewing MSC Pool Alarms
Viewing the Current Fault Alarms of MSC Pool

Fault alarms of MSC Pool refer to the alarms that are raised because of unbalanced loads. You can set multiple query conditions to quickly locate the unbalanced loads to perform maintenance.
Prerequisite
l l
Context
Fault alarms of MSC Pool refer to the alarms raised because of unbalanced loads in MSC Pool. The alarm type is internal NM. For details, refer to ALM-1 Load Unbalance Alarm. To view the current fault alarms of specific NEs in the MSC Pool, you can use one of the following methods:
l l
Use the alarm query function described in 2.2.7 Querying Alarms. View the icon color and alarm balloon of the NE on the M2000 physical topology view or the Pool topology view. When an NE generates fault alarms, the color of the NE icon changes to that for the most severe alarm. In addition, an alarm balloon appears beside the icon. The balloon displays the alarm severity identity and number of alarms.
Procedure
View the current fault alarms of MSC Pool. Use one of the following methods to view the Event Alarms window: Method From the Pool Management window Procedure 1. Choose Maintenance > Pool Management or click on the toolbar. The Pool Management window is displayed. 2. Right-click an MSC Pool in the navigation tree and choose Query Alarm > Current Fault Alarm from the shortcut menu. From the main window of the M2000 client 1. Choose Monitor > Current Fault Alarms or click on the toolbar. The Filter dialog box is displayed. 2. Click the Alarm Source tab to select the MSC Pool whose alarms need to be checked.
Issue 06 (2008-12-16)
12-38
Method From the toolbar of the M2000 client
Procedure 3. On the Base Setting tab page, set the time segment of the alarm. 4. Click OK.
NOTE You must select Critical in Level and Internal in Type. All alarm severities and alarm types are selected by default.
For details of the operations related to alarms, such as saving, printing, and viewing alarm details, refer to 2.2 Monitoring Network Alarms. ----End
Result
In Current Fault Alarms, you can view the details of current fault alarms of MSC Pool.
Related References
Viewing the Event Alarms of MSC Pool

This describes how to view the event alarms of MSC Pool. Event alarms of MSC Pool are mainly generated because of data inconsistency between MSC servers or MGWs in the MSC Pool. You can set multiple query conditions to quickly locate the inconsistent data. Thus you can synchronize them in time to ensure the normal operation of the MSC Pool.
Prerequisite
l l
Context
l
Event alarms of MSC Pool are the event alarms raised when data inconsistency is detected during data auto-check. The alarm type is internal NM. For details, refer to ALM-2 Data Inconsistency Alarm. To view the event alarms of specified NEs in the Pool, you can use the alarm query function described in 2.2.7 Querying Alarms.
Procedure
View the event alarms of MSC Pool. Use one of the following methods to view the Event Alarms window:
Issue 06 (2008-12-16)
12-39
Method From the Pool Management window
Procedure 1. Choose Maintenance > Pool Management or click on the toolbar. The Pool Management window is displayed. 2. Right-click an MSC Pool in the navigation tree and choose Query Alarm > Event Alarm from the shortcut menu.
From the main window of the M2000 client From the toolbar of the M2000 client
1. Choose Monitor > Event Alarms or click on the toolbar to view the Filter dialog box. 2. Click the Alarm Source tab to select the MSC Pool whose alarms need to be checked. 3. On the Base Setting tab page, set the time segment of the alarm. 4. Click OK.
For details of the operations related to alarms, such as saving, printing, and viewing alarm details, refer to 2.2 Monitoring Network Alarms. ----End
Result
In Event Alarms, you can view the details of event alarms of MSC Pool .
Related References
12.4.2 Monitoring the Load of MSC Pool in Real Time

This describes how to monitor the load of the MSC Pool in real time. In normal situations, the load balancing algorithm of the system ensures load balance of the MSC Pool.
Application Scenario
The scenarios of monitoring the load of MSC Pool in real time are as follows:
l
After the imbalance alarm is generated, check the Pool load status in real time to obtain the information about the users on each MSC server and to draw up the user transfer scheme. After manually transferring users, monitor the Pool load status to obtain the information such as progress of user transfer and CPU load of each NE in the Pool. Periodic monitoring in routine maintenance
12.4.2.1 Setting the Real-Time Monitoring of MSC Pool This describes how to set the real-time monitoring of MSC Pool. After you set the real-time monitoring of MSC Pool, the loads of the MSC server are displayed in bar charts and line charts.
From the real-time monitoring chart, you can monitor the number of users served by the MSC server, the CPU usage, and the MGW contexts. 12.4.2.2 Real-Time Monitoring Counters of MSC Pool This describes the real-time monitoring counters shown in the Create a Real-time Load Monitor Task dialog box. You can refer to this topic when setting real-time monitoring for an MSC Pool.
Setting the Real-Time Monitoring of MSC Pool

This describes how to set the real-time monitoring of MSC Pool. After you set the real-time monitoring of MSC Pool, the loads of the MSC server are displayed in bar charts and line charts. From the real-time monitoring chart, you can monitor the number of users served by the MSC server, the CPU usage, and the MGW contexts.
Prerequisite
l l
Context
The real-time monitoring chart of the MSC Pool can be a line chart or bar chart. The difference is as follows:
l
Line chart: The vertical coordinate refers to the counter values. The horizontal coordinate refers to the monitoring time. Bar chart: The vertical coordinate refers to the counter values. The horizontal coordinate refers to the monitored object
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to be monitored, and choose Real-time Monitor from the shortcut menu. Step 3 In the displayed Create a Real-time Load Monitor Task, set the monitoring parameters. 1. Select the monitoring counters. For details of monitoring counters, see 12.4.2.2 Real-Time Monitoring Counters of MSC Pool. Select the monitoring period of the counter from the Period drop-down list of the related monitored object. The system refreshes the monitoring counters based on the specified period. The monitoring period can be 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, or 20 minutes. Select the NEs to be monitored from the NE group box. You can select multiple monitored objects.
2.
3.
Step 4 Click OK. The load changes of the MSC server are displayed in a line chart. you can also select Histogram in Chart Type. You can right-click in the real-time monitoring chart and perform the following operations:

l l l l l
Save as an image: to save the monitoring chart as an image. The image is in .jpg format. Export data: to save the monitoring data to a file. The file is in .csv format. Print: Print: to print the current monitoring chart. Set NE color: to display different NE data by colors.
NOTE
The created tasks are named by Monitor TaskN with N as an integer starting from 1. For example, the first monitoring task is named Monitor Task, and the second task is named Monitor Task2. You can change the task names as required.
----End
Real-Time Monitoring Counters of MSC Pool

This describes the real-time monitoring counters shown in the Create a Real-time Load Monitor Task dialog box. You can refer to this topic when setting real-time monitoring for an MSC Pool. The real-time monitoring counters are MSC Server Subscriber Quantity, MSC Server CPU Occupancy Rate, and Number of MGW Contexts. Table 12-9 shows the meanings of these counters. Table 12-9 Real-time monitoring counters Real-Time Monitoring Counter MSC Server Subscriber Quantity Total Conversation Idle Power-Off Description Number of all subscribers on the MSC server, that is, users inside and outside the Pool. Number of active subscribers on the MSC server, that is, active subscribers inside and outside the Pool. Number of idle subscribers on the MSC server, that is, idle subscribers inside and outside the Pool. Number of subscribers whose mobile phones are powered off on the MSC server, that is, subscribers inside and outside the Pool. Transient mean of the CPU usage on all the active CCU/CSU boards of the MSC server Total number of VMGW contexts on the MSC server.
MSC Server CPU Occupancy Rate Number of MGW Contexts
12.4.3 Viewing the Operation Logs of MSC Pool

This describes how to view the operation logs of an MSC Pool. The operation logs of MSC Pool record the operations related to the MSC Pool.
12-42
Issue 06 (2008-12-16)
Prerequisite
l l
Procedure
Step 1 Choose System > Log Management > Query Operation Logs . Step 2 In the Filter Condition window, click Choose in the Operation group box. Step 3 In the displayed Operation Select dialog box, view the operations related to the MSC Pool. Step 4 Click OK. Step 5 In the Filter Condition window, set the filtering conditions and then click OK. The procedures are the same as those describes in 5.3.2 Querying Operation Logs. For details of other operations related to logs, such as saving and printing query results, refer to 5 Log Management. ----End
12.4.4 Viewing the MSC Where a Specific User Is Located

This describes how to view the MSC where a specific user is located. In the MSC Pool, an RNC/ BSC does not map to an MSC server. The users under the same RNC/BSC may also be distributed to different MSC servers. The M2000 provides the Subscriber Search function. By using this function, you can quickly find the MSC server where a specific user is located.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool of the user and choose Subscriber Search from the shortcut menu. Step 3 In the displayed Search for subscribers, select the number type of the user to be found. The number type can be MSISDN or IMSI. The meanings of the number types are as follows:
l
MSISDN: indicates the international ISDN of a mobile station. The calling party is the number that initiates the call attempt in the telephone network. IMSI: indicates the identity number of the international mobile subscriber. The IMSI number is the only identity number for the subscriber in the network.
Step 4 Enter the number of the subscriber that you need to search in the Number field. Set the result display mode as Basic Information or Full Information.
l
If you choose Basic Information, the system displays only the information that you are most concerned with, such as IMSI, MSISDN, and HLR No..
Issue 06 (2008-12-16)

l
If you choose Full Information, the system displays all the information about the subscriber, for example, the calling number and the called number of the most recent call.
Step 5 Click Search.

NOTE
l l
If the user to be located is not available in this MSC Pool, a dialog box is displayed, informing you that no related information about this user is found in this MSC Pool. If no MSC server is available in the Pool, a dialog box is displayed, informing you that no such MSC server is found in this Pool.
----End
12.4.5 Viewing the Relation Between the MGW and the RAN
This describes how to view the relation between the the MGW and the RAN.
Prerequisite
l l
Context
NOTE
If both CN NEs and AN NEs are available in the MSC Pool, you can view the relation between the MGW and RAN.
Procedure
Step 1 Choose Maintenance > Pool Management or click Management interface is displayed. on the toolbar. The Pool
Step 2 In the navigation tree, right-click an MSC Pool and choose Property from the shortcut menu. Step 3 In the left navigation tree of the Pool Property Settings dialog box, select Property. Step 4 In the right window, click the Relation between MGW and RAN tab and select the view type. You can view the relation between the MGWs and the RNC in a tree. For details of the view type, refer to 12.6.6 Parameters for Viewing the Connection Between MGW and RAN. ----End
Related References
12.6.6 Parameters for Viewing the Connection Between MGW and RAN
12.4.6 Viewing the Proxy Relation Between the MGW and the RAN
Prerequisite
l l
12-44
Procedure
Step 2 In the navigation tree, select the MGW to view the proxy relation, and then you can view their proxy relation in the right pane. ----End
12.4.7 Displaying MSC Pool Topology

This describes how to display the MSC Pool topology. The MSC Pool topology is used to display the logical networking structure of the MSC Pool.
Prerequisite
l l
Context
NOTE
l l
Right-click on the topology view of the MSC Pool and choose Pool Maintenance Main Frame. The Main Frame of the Pool Operation and Maintenance window. For details of other shortcut menus, such as alarm balloon tips display and alarm query, refer to the related contents in 3 Topology Management and 2.2 Monitoring Network Alarms.
Procedure
Step 2 In the navigation tree, select the MSC Pool whose topology structure you plan to view, and then choose Topo from the shortcut menu. Step 3 In the displayed Main Topology window, view the logical networking structure of the MSC Pool.
NOTE
Double-click the core network icon
and radio access network icon
to display the core network and and .
NEs and radio access network NEs separately in a box. Double-click above the box, the NEs are collapsed into
----End
12.4.8 Managing the Task of Auto-Checking MSC Pool

This describes how to manage the task of auto-checking the MSC Pool. You can modify and delete the tasks of auto-checking the MSC Pool.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the associated operations. The auto-check task of the MSC Pool is available.
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to mange auto-check tasks, and choose Data Consistency Check > Automatic Check from the shortcut menu. Step 3 Click the Check Task tab. Then, you can manage the auto-check task as required. Management Function Browse detailed information about the task Operation
l
In Task Table, you can view the detailed information, such as Task Name, Check Plan, Nes, Data Items, and Task Status. In Task Result, you can view the details of the task execution, such as Task Name, Result, Acknowledgement, Last Check Time, Nes, and Data Items.
Modify the information about the task
1. Select the task to be modified in Task Table. 2. Either double-click the task or click Modify. 3. In the displayed Modify an Automatic Check Task dialog box, modify the information as required. 4. Click OK.
Delete the auto-check task
1. Select the task to be deleted in Task Table. 2. Click Delete. 3. In the displayed Message dialog box, click Yes.
Activate the auto-check task
1. In Task Table, choose a task whose Task Status is Suspended. 2. Right-click Active. Then, the system performs the task based on the scheduled period.
Suspend the auto-check task
1. In Task Table, choose a task whose Task Status is Activated. 2. Right-click Suspend. Then, the system does not perform the auto-check task.
12-46
Issue 06 (2008-12-16)

NOTE
When managing the auto-check tasks of multiple Pools, you can click easily switch between different Pools.
on right of the Pool box to
----End
Related References
12.4.9 Viewing the MSC Pool Performance Report

After an MSC Pool is created, counters of a single NE, such as mobile office direction traffic, call connection ratio, call drop rate, and local network traffic, fail to serve as the statistical information about the entire network. By querying the MSC Pool performance report, you can summarize the performance data reported by NEs and get the counter data applicable for the entire network.
Prerequisite
l l
Procedure
Step 1 Use either of the following methods to open the Performance Report window. Method Operation 1 2 Choose Report > Performance Report > Report Management.
1. Choose Maintenance > Pool Management or click
on the toolbar.
2. Select an MSC Pool in the navigation tree and choose Performance Query from the shortcut menu. Step 2 Right-click the performance report in the navigation tree and choose Query from the shortcut menu. For information about each performance report, refer to 7.5 MSC POOL Report Group. Step 3 In the displayed Report Condition Setting dialog box, set the query conditions. 1. Select the time dimension in Time dimension. Then the system summarizes the performance counter results of the query objects based on the time dimension. For example, if Time dimension is set to Hour, the system summarizes the performance counter results at a regular interval of one hour. 2. Select the query object in Object dimension. For Pool performance counters, the object dimensions are LocalSection level, NE level, and Pool level. The respective meanings are as follows:

l
LocalSection level: The system summarizes the data of the same local network of different NEs in a Pool. For example, call attempts of local network 1(all)=call attempts of local network 1 (msc1)+call attempts of local network 1(msc2). NE level: The system summarizes the data of all objects of one MSC server in a Pool. For example, call attempts of MSC 1=call attempts of local network 1 (msc1)+call attempts of local network 2 (msc1)+call attempts of local network 3 (msc1). Pool level: The system summarizes data of all the MSC servers in a Pool. For example, call attempts of a Pool=call attempts of MSC 1+call attempts of MSC 2.
3. 4.
Select the query object in Object range. Select the query time in the Date selection and Time segment selection group boxes.
Step 4 Click Query. The query results are displayed in tables.

NOTE
For details of the operations related to performance reports, such as filtering reports, setting query templates, and setting display conditions, refer to 7 Performance Report Management.
----End
12.5 MSC Pool Network Maintenance

This describes how to perform the fault maintenance for the MSC Pool on the M2000 client. The fault maintenance includes the load balancing of the MSC Pool and the data checking of the MSC Pool. 12.5.1 Balancing MSC Pool Load This describes how to monitor the load of the MSC Pool in real time. When the load is unbalanced because of MSC server upgrade or network adjustment, you can manually migrate MSC server users on the M2000 so that the load of each MSC server in the MSC Pool is balanced. 12.5.2 Checking MSC Pool Data In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. The M2000 enables you to check the data that must be consistent. In this way, you can perform the related operation according to the check results.
12.5.1 Balancing MSC Pool Load

This describes how to monitor the load of the MSC Pool in real time. When the load is unbalanced because of MSC server upgrade or network adjustment, you can manually migrate MSC server users on the M2000 so that the load of each MSC server in the MSC Pool is balanced. 12.5.1.1 Load balance scheme of MSC Pool In an MSC Pool network, one RNC/BSC is connected to multiple MSC servers within an MSC Pool. According to the load balancing scheme, the system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of the MSC servers. In this way, the utilization of the entire CN resources is improved and the investment is reduced. 12.5.1.2 Mode for Manual Transfer of Users This describes the common modes for manual transfer of MSC Pool users and the application scenarios. 12.5.1.3 Manual Transfer of Users
This describes how to manually transfer users. By manually transferring users, you can transfer one or several users on the MSC server to other MSC servers in the Pool. In this way, you can maintain the MSC server in the MSC Pool without affecting user services.
Load balance scheme of MSC Pool

In an MSC Pool network, one RNC/BSC is connected to multiple MSC servers within an MSC Pool. According to the load balancing scheme, the system assigns connected MSs/UEs to the relevant MSC servers based on the capacity proportion of the MSC servers. In this way, the utilization of the entire CN resources is improved and the investment is reduced. In an MSC Pool, one RNC/BSC is connected to multiple MSC servers in the pool. Therefore, when the MS/UE in the RNC/BSC service area initiates a new service request, the RNC/BSC needs to select a serving MSC server for the service. For details, see Table 12-10. Table 12-10 Load balance scheme of MSC Pool Call Mode The MS/UE initiates a service based on the IMSI or IMEI. Load Balancing Scheme According to the load balancing algorithm, the RNC/BSC selects a valid MSC server for the MS/UE based on the proportion of subscriber capacity of the MSC servers in the MSC Pool. If an MS/UE initiates a service using IMSI, the selected MSC server distributes a TMSI containing the NRI of the MSC to the MS/UE. As shown in Figure 12-4, if the available capacity of MSC server1 is 4, the available capacity of MSC server2 is 3, and the number of MSs/UEs is 7, then the RNC/BSC assigns four MSs to MSC server1 and three to MSC server2 to ensure the load balance. The MS/UE initiates a service based on the IMSI. The RNC/BSC selects the serving MSC server for the MS/UE according to the mapping between the NRI and MSC server.
NOTE When the selected MSC server is invalid or no mapping is available between the NRI and the MSC server, the RNC/BSC uses the load balancing algorithm and distributes MSC server according to the proportion of subscriber capacity of the MSC servers. Then, the selected MSC server assigns a TMSI containing the office NRI to the MS/UE.
The MSC server pages the called MS/UE based on the IMSI.
The RNC/BSC temporally saves the mapping between the MSI and the paged MSC server. When the paged MS/UE pages the corresponding network based on the IMSI, the RNC/BSC selects the MSC server according to whether the NRI is available on the MS/UE.
l
If the NRI is available on the MS/UE, the RNC/BSC selects an MSC server according the mapping between the NRI and the MSC server. If the NRI is unavailable on the MS/UE, the RNC/BSC selects the MSC server according to the temporally saved mapping between the IMSI and the MSC server.
NOTE If the selected MSC server is invalid or the system fails to select the MSC server according to the mapping, the RNC/BSC selects an MSC server according to the load balancing algorithm.
Issue 06 (2008-12-16)
12-49
Figure 12-4 Load balancing principle
CAUTION
l
When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/ BSC considers the MSC to be faulty or invalid. The proportions of subscriber capacity of the RNC/BSC to each MSC server needs to be configured statically on the RNC/BSC. In addition, the MSC servers can notify the subscriber capacity regularly, and the RNC/ BSC dynamically adjusts the proportion of subscriber capacity of MSC servers according to the subscriber capacity of each MSC server in the notification. This mode, however, only applies to the case that all MSC servers in the MSC Pool and BSCs and RNCs in the MSC Pool area are Huawei equipment. For other modes, the RNC can configure the subscriber capacity of MSC servers statically.
The subscriber capacity of an MSC server described previously is the total number of subscribers of the MSC server (number of licensed subscribers for the MSC server). However, when an MSC server connects with RNCs or BSCsoutside the MSC Pool, the subscriber capacity reserved for these RNCs or BSCs needs to be subtracted from total capacity as for calculation of subscriber capacity of the MSC server.
Mode for Manual Transfer of Users

This describes the common modes for manual transfer of MSC Pool users and the application scenarios. Table 12-11 shows the modes for manual transfer of users.
Table 12-11 Transfer Mode Transferring Method Redistribution all subscribers on the MSC to other MSCs Application Scenario When you update one or more MSC servers in an MSC Pool, you need to transfer all the users on the MSC servers to other MSC servers in the MSC Pool and then upgrade the MSC servers to ensure the normal operation.
l
Redistribution a certain ratio of subscribers on the MSC to other MSCs Redistribution a certain number of subscribers on the MSC to other MSCs
When the loads of an MSC Pool are unbalanced, you need manually adjust the loads. Manual load adjustment is common during network adjustment. After updating an MSC server, you need transfer some users of other MSC servers to the updated MSC server. By using this transfer mode, you can provide special service which is provided on only a specified MSC server for users in a specified area. To achieve this, you need to transfer specified users on the RNC or BSC to this MSC server. Before the Pool is split, you must distribute the users to the specified MSC server based on the relation between the users and the MSC servers. Adjust the link between the MSC server and the RNC or BSC.
Redistribution the subscribers with specified RNC on the MSC to other MSCs Redistribution the subscribers with specified BSC on the MSC to other MSCs
Redistribution the subscribers with specified LAI on the MSC to other MSCs
By using transfer mode, you can provide special service, which is provided on only a specified MSC server, for users in a specified area. To achieve this, you need to transfer specified users on the LAI to this MSC server. This mode transfers the users subscribed in MSC server 1 to MSC server 2 for the purpose of network commissioning.
Redistribution the subscribers on the MSC to other MSCs
Related Tasks
Related References
Manual Transfer of Users

This describes how to manually transfer users. By manually transferring users, you can transfer one or several users on the MSC server to other MSC servers in the Pool. In this way, you can maintain the MSC server in the MSC Pool without affecting user services.
Issue 06 (2008-12-16)
12-51
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to operate the MSC Pool. Before transferring users, you can view each NE's load in the current network through the M2000 load supervision function and choose a proper transfer method.
Context
You can transfer users through 3GPP TS 23.236 protocol and inter-office E interface redirection. The default transfer scheme is inter-office E interface redirection. For details, refer to 12.1.1 Basic Scheme of MSC Pool.
Procedure
Step 2 In the navigation tree, right-click the MSC Pool to transfer users and choose Load Redistribution from the shortcut menu. The system displays the Load redistribution-Select a type dialog box. Step 3 Choose the distribution method according to your requirements, and then click Next. See 12.5.1.2 Mode for Manual Transfer of Users for detailed information on distribution methods. Step 4 Run different operations according to the user distribution methods. Transferring Method Operation
Redistribution all subscribers on the MSC 1. Choose the MSC server from which the users to other MSCs are transferred in the Source NE. 2. In the Destination NE, select a destination MSC server. 3. Enter the load balancing ratio of the destination NE in the Load ratio field. Click Allocate load ratios, and the system automatically generates the load ratios according to the remaining capacity of the destination NE. This ensures the load balance of each destination NE. 4. Select the user distribution speed in the Redistribution speed drop-down list.
NOTE
l If the preset destination NE cannot hold all the
migrated users, the system displays that the the destination NE has insufficient capacity. In this case, you need to select the destination NE again.
l The Medium speed is recommended for the
Redistribution speed.
12-52
Issue 06 (2008-12-16)
Transferring Method Redistribution a certain ratio of subscribers on the MSC to other MSCs
Operation The operation is similar to that whose transferring method is Redistribution all subscribers on the MSC to other MSCs. The Redistribution ratio should also be configured. The operation is similar to that whose transferring mode is Redistribution all subscribers on the MSC to other MSCs. The subscribers should also be configured.
Redistribution a certain number of subscribers on the MSC to other MSCs
Redistribution the subscribers with 1. Select the RNC in the Candidate RNC list specified RNC on the MSC to other MSCs box and then click Next. 2. The operation is the same as that whose transferring method is Redistribution all subscribers on the MSC to other MSCs. Redistribution the subscribers with 1. Select the BSC in the Candidate BSC list specified BSC on the MSC to other MSCs box, and then click Next. 2. The operation is the same as that whose transferring method is Redistribution all subscribers on the MSC to other MSCs. Redistribution the subscribers with 1. Select the LAI in the Candidate LAIs list specified LAI on the MSC to other MSCs box, and then click Next. 2. The operation is the same as that whose transferring method is Redistribution all subscribers on the MSC to other MSCs. Redistribution the subscribers on the MSC to other MSCs 1. In the Number Type, choose the number type of the transferred users. 2. In the Source NE, select the MSC server from which users are transferred. 3. Enter the subscriber number in the Enter the subscriber number list. 4. In the Destination NE, select a destination MSC server.
NOTE
l You can choose only one source and destination
MSC server.
l Up to 10 users of specified numbers can be
transferred.
l The Number Type of all the transferred users can
only use IMSI or MSISDN at the same time. The two cannot be mixed in use.
Issue 06 (2008-12-16)
12-53
See 12.6.7 Parameters for Transferring MSC Pool Users Manually for detailed information on the parameters.
CAUTION
l
If an MSC server is operating a transfer task, it cannot serve as a source NE and a destination NE for the transfer. If an MSC server is acting as the destination of a transfer task that is in process, the server can be specified as the destination of another transfer task.
Step 5 Click Next to check the detailed information on user transfer. Step 6 Click OK. An information box is displayed, showing whether the M2000 has successfully issue the transfer command to the related NE. Step 7 Click OK to close the dialog box. ----End
Postrequisite
You can view the transfer progress in the task list of the Main Interface. For details of the Main Frame for MSC Pool operation and maintenance, see 12.6.1 Interface Description: Main Interface of Pool OM.
Related Concepts
12.5.1.2 Mode for Manual Transfer of Users 12.1.3 Transfer Scheme of MSC Pool Users
Related References
12.5.2 Checking MSC Pool Data

In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. The M2000 enables you to check the data that must be consistent. In this way, you can perform the related operation according to the check results. 12.5.2.1 Viewing the Result of Auto-Checking MSC Pool Data This describes how to view the result of auto-check MSC Pool data. You can perform the related operations to ensure the data consistency. 12.5.2.2 Manually Checking MSC Pool Data In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. You can manually check this type of data on the M2000. After selecting the NEs and data item, you can view the check results so that you can take related measures to ensure the data consistency on the NE. 12.5.2.3 Setting the Checking Items of MSC Pool Data
This describes how to set the checking items of MSC Pool data. The M2000 enables you to set the Pool data check items flexibly. If the inconsistent data found in manual check does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. You can restore the shielded data. 12.5.2.4 Synchronizing MSC Pool Data In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. When the data is inconsistent, you can synchronize the data to ensure the consistency.
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool
Viewing the Result of Auto-Checking MSC Pool Data

This describes how to view the result of auto-check MSC Pool data. You can perform the related operations to ensure the data consistency.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the associated operations. At least one auto-check task is performed.
Procedure
Step 2 In the navigation tree, right-click an MSC Pool, and choose Data Consistency Check > Automatic Check from the shortcut menu. The Automatic Check tab is displayed.
NOTE
You can also view the check results in the area about data consistency in Main Frame. By double-clicking a record, you can view the Automatic Check tab page.
Step 3 Click the Check Task tab. Select the task to be viewed in Task Table. In Task Result, you can view the details of the task execution, such as Result, Nes, and Last Check Time. After you select a record whose Result is Inconsistent or Abnormal, you can perform the following operations: Operation Acknowledgement Description Indicates that the check results are processed. This operation applies to only the results that are not acknowledged. Unacknowledge Identifies the acknowledged check results as unacknowledged. This operation applies to only acknowledged results. Step 4 In Task Result, select a result whose Result is Inconsistent or Abnormal. Click Result Detail or the Check Result tab.

NOTE
l l l l l
The Inconsistency Data tree displays the inconsistent data in the check result. You can view the detailed check results in the group box beside the Inconsistency Data tree. The inconsistent data is in red. Click Export Result to save the check results containing the inconsistent data to a .csv file. You need to manually synchronize the inconsistent data. For details, see 12.5.2.4 Synchronizing MSC Pool Data. If the inconsistent data does not affect the MSC Pool service, you can click Manual Check and then shield this data. For details, see 12.5.2.3 Setting the Checking Items of MSC Pool Data.
----End
Related Tasks
12.5.2.3 Setting the Checking Items of MSC Pool Data
Manually Checking MSC Pool Data

In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. You can manually check this type of data on the M2000. After selecting the NEs and data item, you can view the check results so that you can take related measures to ensure the data consistency on the NE.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the MSC Pool for which you plan to check the data, and choose Data Consistency Check > Manual Check&Synchronize Data from the shortcut menu. The Manual Check dialog box is displayed. Step 3 Select the NE type from the NE Type drop-down list. Step 4 Select the NE whose data needs be checked in Select NE.
NOTE
Step 5 Select the data items in the Select Data Item group box.
NOTE
l l
You can select multiple data items at the same time. You can use the Find box to quickly find the data item to be checked.
Step 6 Click Start Check. A progress bar is displayed, showing the refresh progress of the NE data cached on the server.

NOTE
l l
Before checking the data, the M2000 server requests NEs for the data to be checked, thus ensuring the consistency between the data on the M2000 server and the data on the NEs. If the M2000 fails to obtain the NE data, the group box at the bottom of the progress bar displays the failure details. Then, the system extracts and checks the data cached on the M2000 server.
Step 7 On the Manual Check tab page, view the check result.
l
If inconsistent data exists, the Inconsistency Data tree displays the data. The group box displays the detailed check result and highlights the inconsistent data in red. If the data is consistent, the Inconsistency Data tree does not display any data. When the system extracts and checks the data cached on the M2000 server, the right bottom of the Manual Check tab page displays The check data may be not the latest data..
l l
----End
Postrequisite
l
If data inconsistency exists, you need manually synchronize the data. For details, see 12.5.2.4 Synchronizing MSC Pool Data. If the inconsistent data does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. For details, see 12.5.2.3 Setting the Checking Items of MSC Pool Data.
Related Tasks
12.5.2.3 Setting the Checking Items of MSC Pool Data 12.5.2.3 Setting the Checking Items of MSC Pool Data
Setting the Checking Items of MSC Pool Data

This describes how to set the checking items of MSC Pool data. The M2000 enables you to set the Pool data check items flexibly. If the inconsistent data found in manual check does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. You can restore the shielded data.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to operate the MSC Pool.
Procedure
l Shield data checking items. 1. 2. Check the data of the MSC Pool manually. For details, refer to 12.5.2.2 Manually Checking MSC Pool Data. In the Inconsistency Data tree, right-click the data to be shielded and choose Shield from the shortcut menu.
You can press Ctrl or Shift to select multiple records.

Issue 06 (2008-12-16)
After the data is shielded, the corresponding background color of the NE record turns grey. You can right-click the NE record of the shielded data item and choose Resume from the shortcut menu to restore the shielded data.
3. l
Click Close to close the Manual Check dialog box.
Restore the shielded checking items. 1. 2. Choose Maintenance > Pool Management or click Management window is displayed. on the toolbar. The Pool
Right-click the MSC Pool of which the data checking items are shielded and choose Data Consistency Check > Cancel the Shield Status of Check Item from the shortcut menu. Select the data and NEs to be restored in Shielded Item. Click OK.
3. 4. ----End
Result
The setting takes effect at the next automatic or manual check.
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool 12.5.2.2 Manually Checking MSC Pool Data 12.3.2 Creating the Task of Auto-Checking MSC Pool 12.5.2.2 Manually Checking MSC Pool Data
Synchronizing MSC Pool Data

In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs. When the data is inconsistent, you can synchronize the data to ensure the consistency.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform the associated operations. The configuration data that must be consistent with all the MSC servers and MGWs in the Pool is inconsistent.
Context
On the basis of data inconsistency, the M2000 generates MML commands to adjust the data. These commands are issued to the relevant NEs to adjust NE data and achieve data consistency.
NOTE
For certain NE data, the system cannot generate data adjustment command on the M2000. You can view a message in the right pane of the Manual Check tab page, showing the specific data that is not supported. In this case, adjust the data through the LMT of the NE.
12-58
Issue 06 (2008-12-16)
Procedure
Step 2 In the navigation tree, choose an MSC Pool and check Pool data. You can check the data by using either of the following methods: Method Manually Checking MSC Pool Data In the consistency status area of Main Frame, double-click the record whose Result is Inconsistent and manually check the data again. Description For details, see 12.5.2.2 Manually Checking MSC Pool Data. 1. Double-click the record whose Result is Inconsistent. 2. In the displayed Automatic Check dialog box, click Manual Check on the Check Task tab page. 3. After setting the data check items in the displayed Manual Check dialog box, click Start Check. Step 3 In the Inconsistency Data tree of the Manual Check tab page, select the data to be synchronized. You can select a data item or a data type. Step 4 Click Synchronize. Step 5 Select an NE in Reference NE. The system uses the data of this NE as the reference of the synchronization. Step 6 Select the NEs to be synchronized in Destination NE. Step 7 Click Generate MML. The right pane on the Manual Check tab page displays the details of the MML commands.
NOTE
l l l
Edit the MML commands in the right pane. Alternatively, click Save MML to save the MML commands as files for subsequent operations. If the data in Destination NE is consistent with that in Reference NE, the right pane displays a message showing that the data is consistent and displays the specific value. If a data item does not support a certain generated MML command, the right pane also displays a message, showing that the data does not support the MML command. In this case, adjust data through the LMT of the NE. The right pane can display a maximum of 500 lines of MML commands. When the MML commands have more than 5000 lines, the system displays that the MML commands are excessive. In this case, you need to click Export MML and manually edit the MML commands. Then, send the script file to the NE through the M2000. For details, see 14.2.1 Creating MML Command Script.
Step 8 Click Send MML to select the issuing mode, and then issue the MML commands.
Issue 06 (2008-12-16)
12-59
Whether ignore errors in MML execution Click Yes.
Command Issuing Mode
When the MML commands are being issued, the system proceeds to issue the remaining MML commands if one MML command is incorrect. When the MML commands are being issued, the system does not issue the remaining MML commands if one MML command is incorrect.
Click No.
NOTE
l l
When the MML command is being issued, you can click Terminate MML to terminate the command issuing. The execution process of the MML commands is displayed in an MML message in the right pane. In the MML message, Total Count indicates the number of MML commands to be sent, Success Count indicates the number of MML commands that are successfully run on the NE, Fail Count indicates the number of MML commands that fail to be run on the NE, and Unsent Count indicates the number of MML commands that fail to be sent by the M2000. For the MML commands that fail to be issued by the M2000 and those fail to be run on the NE, you can get the related information by checking the MML messages returned from the NE.
Step 9 Click Backward and repeat Step 3 through Step 8 to synchronize other data. ----End
Postrequisite
Click Export Result on the Manual Check tab page to save the results of the MML commands to a file.
12.6 Management Interface of MSC Pool

This describes the management interfaces of the MSC Pool and the parameters. This describes the main interface of MSC Pool operation and maintenance, the interface for viewing MSC Pool alarms, the MSC Pool configuration interface, and parameters related to Pool configuration or maintenance operations. In this way, you can perform operations related to MSC Pool management. 12.6.1 Interface Description: Main Interface of Pool OM This describes the layout of the Main Interface of the MSC Pool, CDMA Pool, and SGSN Pool, and the information about each element on the interface. 12.6.2 Interface Description: Viewing MSC Pool Alarms This describes the layout of the interface for viewing MSC Pool alarms and the information about each element on the interface. 12.6.3 Interface Description: MSC Pool Configuration This describes the MSC Pool parameter setting interface, that is, the layout of the Pool Parameter Setting interface and the information about each interface element.
12.6.4 Parameters for Creating/Modifying MSC Pool This describes the parameters used for creating or modifying the MSC Pool. 12.6.5 Parameters for Browsing MSC Pool Basic Information This describes the related parameters in the Pool Properties Settings dialog box. You can refer to these parameters when you browse the MSC Pool basic information. 12.6.6 Parameters for Viewing the Connection Between MGW and RAN This describes the related parameters on the Relation between MGW and RAN tab page in the Pool Attribute Setting dialog box. You can refer to these parameters when you view the relation between the MGW and the RAN. 12.6.7 Parameters for Transferring MSC Pool Users Manually This describes the parameters for manually transferring MSC Pool users. You can refer to these parameters when manually transferring SGSN users. 12.6.8 Parameters for Specifying User Numbers to Be Transferred This describes the related parameters in the Load redistribution-Select NE & Enter Subscriber Number dialog box. You can refer to these parameters when you manually transfer the users of specific numbers on the MSC server. 12.6.9 Parameters for Setting the Auto-Check of MSC Pool This describes the related parameters in the Create Automatic Check Task dialog box. You can refer to these parameters when you create an auto-check task. 12.6.10 Parameters for Setting CN ID of an MSC Server This describes the related parameters on the CN ID Setting tab page in the Pool Parameter Setting dialog box. You can refer to these parameters when you set the CN ID. 12.6.11 Parameters for Setting NRI of an MSC Pool This describes the parameters on the CN ID-NRI Setting tab page in the Pool Parameter Setting dialog box. You can refer to these parameters when you set the relation between the CN ID and the NRI. 12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool This describes the parameters shown on the Non-broadcast LAI Setting tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting Non-broadcast LAIs. 12.6.13 Parameters for Setting Load-Balancing of an MSC Pool This describes the parameters shown on the Load Balance Parameter tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting load balancing parameters. 12.6.14 Parameters for Setting NE State of MSC Pool This describes the parameters shown on the NE Status Maintenance tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting NE states. 12.6.15 Parameters for Superior Settings This describes the parameters shown on the Advanced Setting tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting NRI lengths and Null NRIs. 12.6.16 Parameters for Setting Load Unbalance Alarm This describes the parameters of load balance alarms in the Pool Property Settings dialog box. You can refer to these parameters when you set the load unbalance alarms.
Issue 06 (2008-12-16)
12-61
12.6.1 Interface Description: Main Interface of Pool OM

This describes the layout of the Main Interface of the MSC Pool, CDMA Pool, and SGSN Pool, and the information about each element on the interface.
Main Interface of MSC Pool OM

The Main Interface of MSC Pool operation and maintenance comprises four areas, as shown in Figure 12-5. For the detailed description of each area, refer to Table 12-12. Figure 12-5 Main Interface of MSC Pool OM
Table 12-12 Description of the Main Interface of MSC Pool OM SN 1 Name MSC Pool object area Description The created MSC Pool and the NEs in the pool are displayed in a navigation tree. The MSC Pool object area provides a shortcut menu so that you can perform maintenance operations on the pool, such as parameter configuration, user migration, and user search.
12-62
Issue 06 (2008-12-16)
SN 2
Name Status area for load balancing
Description This area periodically refreshes and displays the number of all current pool users of the MSC server within the pool, the capacity load, and the load balance status of the Pool. The load balance status of the Pool can be Normal, Exception, or Unchecked.
l
Normal: The loads between each MSC server within the Pool are balanced. Exception: The offset between the highest loads the lowest load of the MSC server within the Pool exceeds the threshold. Unchecked: The number of MSC servers within the Pool is smaller than 2 and the system cannot identify the state of the Pool.
Status area for data consistency
Shows the operation results of all the auto-check tasks. The status for data consistency is classified into four types: Unchecked, Inconsistent&Acknowledged, Inconsistent&Unacknowledged, and Consistent. The respective meanings are as follows:
l
Unchecked: indicates that no auto-check task is available or the auto-check tasks are not executed. Inconsistent&Acknowledged: indicates that data checked between the NEs is inconsistent and that the checking result is already acknowledged. Inconsistent&Unacknowledged: indicates that the data checked between the NEs is inconsistent and that the checking result is still unacknowledged. Consistent: indicates that the data checked between the NEs is consistent.
Task list
This area displays the information about manual user transfer and data synchronization tasks. This area provides a shortcut menu so that you can perform the following operations on the task records:
l l l l l
Refreshing the task list. Viewing the detailed task information. Stopping a task. Viewing the operation results. Deleting a task.
Main Interface of CDMA Pool OM

The Main Interface of CDMA Pool operation and maintenance comprises four areas, as shown in Figure 12-6. For the detailed description of each area, refer to Table 12-13.
Issue 06 (2008-12-16)
12-63
Figure 12-6 Main Interface of CDMA Pool OM
Table 12-13 Description of the Main Interface of CDMA Pool OM SN 1 Name CDMA Pool object area Description The created CDMA Pool and the NEs in the Pool are displayed in a navigation tree. The CDMA Pool object area provides a shortcut menu so that you can perform maintenance operations on the pool, such as parameter configuration, user migration, and user search. 2 Status area for load balancing This child window periodically refreshes and displays the number of all current Pool users of the MSCe within the Pool, the capacity load, and the load balance status of the Pool. The load balance status of the Pool can be Normal, Exception, or Unchecked.
l
Normal: The loads between each MSCe within the Pool are balanced. Exception: The offset between the highest loads the lowest load of the MSCe within the Pool exceeds the threshold. Unchecked: The number of MSCes within the Pool is smaller than 2 and the system cannot identify the state of the Pool.
12-64
Issue 06 (2008-12-16)
SN 3
Name Status area for data consistency
Description Shows the operation results of all the auto-check tasks. The status for data consistency is classified into four types: Unchecked, Inconsistent&Acknowledged, Inconsistent&Unacknowledged, and Consistent.
l
Unchecked: indicates that no autocheck task is available or the autocheck tasks are not executed. Inconsistent&Acknowledged: indicates that data checked between the NEs is inconsistent and that the checking result is already acknowledged. Inconsistent&Unacknowledged: indicates that the data checked between the NEs is inconsistent and that the checking result is still unacknowledged. Consistent: indicates that the data checked between the NEs is consistent.
Task list
Displays the information about the data synchronization tasks in the pool. This area provides a shortcut menu so that you can perform the following operations on the task records:
l l
l l l

This describes the layout of the interface for viewing MSC Pool alarms and the information about each element on the interface. The MSC Pool alarm browse interface composes of current alarm browse interface and event alarm browse interface. When the viewing conditions are set, detailed information about the related alarms is displayed in either the Current Fault Alarms or the Event Alarms window. If you select an alarm from the list, the system displays its detailed information and handling suggestions. Figure 12-7 shows the interface.
Issue 06 (2008-12-16)
12-65
Figure 12-7 Alarm Viewing interface of the MSC Pool
Related Tasks
12.4.1 Viewing the Alarms of MSC Pool 12.4.1.1 Viewing the Current Fault Alarms of MSC Pool 12.4.1.2 Viewing the Event Alarms of MSC Pool
12.6.3 Interface Description: MSC Pool Configuration

This describes the MSC Pool parameter setting interface, that is, the layout of the Pool Parameter Setting interface and the information about each interface element. The Pool Parameter Setting interface contains the following tabs:
l l l l l l
CN ID Setting CN ID-NRI Setting Non-broadcast LAI Setting Load Balance Parameter NE Status Maintenance Advanced Setting
Figure 12-8 shows the pool parameter setting interface. Table 12-14 describes each tab page.
12-66
Issue 06 (2008-12-16)
CAUTION
When the MSC Pool manages only the radio access network, the features of the Pool Parameter Setting are as follows:
l l l l
The CN ID Setting tab and the Non-broadcast LAI Setting tab are not available. The NE Status Maintenance tab has no MGW Segregate Status. The CN ID-NRI Setting tab has no NE Name field. The CN Node Status on the NE Status Maintenance tab does not have the MSCServer NE field.
When the MSC Pool manages only the CN, there is no PLMN setting function.
Figure 12-8 Pool Parameter Setting interface
Table 12-14 Pool Parameter Setting interface Tab CN ID Setting CN ID-NRI Setting Description Displays the CN IDs of all MSC servers in the MSC Pool. You can modify the CN IDs as required. Displays the NRIs of the MSC servers in the MSC Pool. You can add or modify the NRIs.
l
Add: to expand the maximum users that the MSC server can accommodate. Modify: to adapt to he network adjustment.
12-67
Issue 06 (2008-12-16)
Tab Nonbroadcast LAI Setting Load Balance Parameter
Description Displays the Non-broadcast LAIs of the MSC servers in an MSC Pool. You can modify the Non-broadcast LAIs as required. Displays the capacity of MSC servers in an MSC Pool. Provides the function of changing the available capacity of MSC servers. In this way, you can plan the available MSC server capacity within the pool according to the actual situations. In addition, you can balance user allocation based on the set user capacity when instructing the RNCs or BSCsto access users. For example, after an MSC server is expanded, you need modify its available capacity in the Pool. Provides the functions of setting maintenance states of NEs in an MSC Pool, such as MGW segregation state and CN node state.
l l
NE Status Maintenance
MGW states are Normal and Segregate. The state of a CN node can be Normal, OffLoad, or Forbidden.
For detailed description of MGW segregation status and CN node status, see 12.6.14 Parameters for Setting NE State of MSC Pool. Advanced Setting Provides the function of setting the NRI length, Null NRI value, and carrier of the MSC Pool.
Related Tasks
12.2 Creating MSC Pool Topology on the M2000 12.2 Creating MSC Pool Topology on the M2000
12.6.4 Parameters for Creating/Modifying MSC Pool

This describes the parameters used for creating or modifying the MSC Pool.
Parameter Pool Name Description Indicates the name of the MSC Pool. The value range of the name is as follows:
l l
A maximum of 60 characters. Composed of English characters, Chinese characters, numbers or other special characters except @ # ! % ^ & * . [ ] / ' " and space. Unique and not empty.
Description
The Pool description is used to differentiate the MSC Pools. The value range of the name is as follows:
l l
A maximum of 64 characters. The value can be empty.
12-68
Issue 06 (2008-12-16)
Parameter Pool Net Type
Description Indicates the networking type of the Pool.

l
Core Network Only: indicates that only NEs of the CN are included in this Pool such as the MSC server and the MGW. Radio Access Network Only: indicates that the Pool contains only NEs of the radio access network, such as the RNC. Core&Radio Access Network: indicates that NEs of both the core network and the radio access network form the Pool.
NOTE When you modify the MSC Pool, the networking type of the Pool should not be changed.
Optional Nes
This list in the form of a navigation tree provides the NEs that can be added to the MSC Pool. Based on the NEs that are connected to the M2000 and the selected networking type of the Pool, the system automatically filters the NEs that can be added to the MSC Pool.
Selected Nes
The list in the form of a navigation tree shows the NEs that are already selected in the MSC Pool.
Related Tasks
12.2 Creating MSC Pool Topology on the M2000 12.2 Creating MSC Pool Topology on the M2000
12.6.5 Parameters for Browsing MSC Pool Basic Information

This describes the related parameters in the Pool Properties Settings dialog box. You can refer to these parameters when you browse the MSC Pool basic information.
Parameter Name Description Number of NE Description Indicates the name of the MSC Pool. Describes the MSC Pool. Indicates the number of the NEs and the specific NEs within the MSC Pool. For example, MSC server(2) MGW(0) RNC(0) BSC(0)indicates that the MSC Pool contains two MSC servers.
Issue 06 (2008-12-16)
12-69
Parameter Net Type
Description Indicates the networking type of the MSC Pool.

l
Core Network Only: indicates that only NEs of the CN are included in this Pool such as the MSC server and the MGW. Radio Access Network Only: indicates that the Pool contains only NEs of the radio access network, such as the RNC and BSC. Core&Radio Access Network: indicates that NEs of both the core network and the radio access network form the Pool.
CN ID and NRI Relation
Indicates the mapping relation between each CN ID value and its corresponding NRI value in the MSC Pool. For example, 1-1,2-2,2-4 indicates that:
l l
When CN ID = 1, its corresponding NRI = 1. When CN ID = 2, its corresponding NRI = 2 and 4.
NRI Length
Indicates the NRI length configured by the NEs within the MSC Pool.
12.6.6 Parameters for Viewing the Connection Between MGW and RAN
This describes the related parameters on the Relation between MGW and RAN tab page in the Pool Attribute Setting dialog box. You can refer to these parameters when you view the relation between the MGW and the RAN.
Parameter Choose ViewStyle Description Select the method to view the relation between the MGW and the RAN.
l
Query by MGW: In the Root navigation tree, the MGW acts as the first node, which shows the RNCs/ BSCs under different MGWs. Query by RAN: In the Root navigation tree, the RNC/ BSC acts as the first node which shows the RNCs/ BSCs under an MGW.
Related Tasks
12.4.5 Viewing the Relation Between the MGW and the RAN

This describes the parameters for manually transferring MSC Pool users. You can refer to these parameters when manually transferring SGSN users.
User Transfer Mode

Parameter Redistribution all subscribers on the MSC to other MSCs Redistribution a certain ratio of subscribers on the MSC to other MSCs Redistribution a certain number of subscribers on the MSC to other MSCs Redistribution the subscribers with specified RNC on the MSC to other MSCs Redistribution the subscribers with specified BSC on the MSC to other MSCs Redistribution the subscribers with specified LAI on the MSC to other MSCs Redistribution the subscribers on the MSC to other MSCs Description Transfers all users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers a certain ratio of users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers a certain number of users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers the specified RNC users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers the specified BSC users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers the specified LAI users on one or multiple MSC servers to other MSC servers in the MSC Pool.
Transfers the users with the specified number on one MSC server to other MSC servers in the MSC Pool.
Parameters for Transferring Subscribers

Parameter Source NE Description Lists all MSC servers in an MSC Pool. You can select one or more MSC servers to transfer their users.
Issue 06 (2008-12-16)
12-71
Parameter Destination NE Load ratio
Description Lists the MSC servers that accommodate the transferred users. Defines the load ratio, which is the basis of distributing the transferred users to the destination NEs.
NOTE The sum of all the load ratios of destination NEs is 100%.
You can manually enter the load ratio of target NEs or click Allocate load ratios. Then the system generates the load ratios based on the idle capacity of the destination NE and thus ensure the load balance of each target NE. Redistribution speed Indicates the speed of transferring users. The value of this parameter is Low speed, Medium speed, or High speed. The meanings of these values are as follows:
l
Low speed: Four or five location update periods are required for the transfer. Medium speed: Two or three location update periods are required for the transfer. High speed: One or two location update periods are required for the transfer.
NOTE Medium speed is recommended.
Redistribution ratio
Indicates the ratio of transferred users to total users. This parameter is valid only when the transfer mode is Redistribution a certain ratio of subscribers on the MSC to other MSCs.
Subscribers
Indicates the number of users transferred from the source NEs. This parameter is valid only when the transfer mode is Redistribution a certain number of subscribers on the MSC to other MSCs.
Candidate RNC
Displays all the RNCs in an MSC Pool. You can select one or more RNCs to transfer their users from the source NEs. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified RNC on the MSC to other MSCs.
Selected RNC
Displays the selected RNCs, where the users to be transferred from the source NEs are located. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified RNC on the MSC to other MSCs.
12-72
Issue 06 (2008-12-16)
Parameter Candidate BSC
Description Displays all the BSCs in an MSC Pool. You can select one or more BSCs to transfer their users from the source NEs. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified BSC on the MSC to other MSCs.
Selected BSC
Displays the selected BSCs where the users to be transferred from the source NEs are located. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified BSC on the MSC to other MSCs.
Candidate LAIs
Displays all the LAIs in an MSC Pool. You can select one or more LAIs to transfer their users from the source NEs. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified LAI on the MSC to other MSCs.
Selected LAIs
Displays the selected LAIs where the users to be transferred from the source NEs are located. This parameter is valid only when the transfer mode is Redistribution the subscribers with specified LAI on the MSC to other MSCs.
Related Concepts
12.5.1.2 Mode for Manual Transfer of Users 12.1.3 Transfer Scheme of MSC Pool Users
Related Tasks
12.6.8 Parameters for Specifying User Numbers to Be Transferred

This describes the related parameters in the Load redistribution-Select NE & Enter Subscriber Number dialog box. You can refer to these parameters when you manually transfer the users of specific numbers on the MSC server.
Issue 06 (2008-12-16)
12-73
Parameter Number type Description Indicates the number type of a transferred user. Number type is either MSISDN or IMSI. The meanings of the number types are as follows:
l
MSISDN: indicates international ISDN number of the mobile station. The calling party is the number that initiates the call attempt in the telephone network. IMSI: indicates the number of the international mobile subscriber identity. The IMSI number is the only identity number for the subscriber in the network.
NOTE The Number type of all transferred users must be identical.
Source NE
Indicates the MSC server whose users need to be transferred.

NOTE You can select only one source NE.
Enter the subscriber number
Indicates the number of the users to be transferred.

NOTE You can enter a maximum of 10 subscriber numbers.
Destination NE
Lists the MSC servers that accommodate the transferred users.

NOTE
l You can select only one destination NE. l The destination NE must differ from the source NE.

This describes the related parameters in the Create Automatic Check Task dialog box. You can refer to these parameters when you create an auto-check task.
Parameter Choose NE Type Task Name Description Indicates the NE type of the data to be checked. Indicates the name of the auto-check task. The value range of the name is as follows:
l l
12-74
Issue 06 (2008-12-16)
Parameter Select NE
Description Indicates the specific NE whose the data to be checked.

NOTE You need select two or more NEs.
Find
Used to quickly find the data item to be checked. Supporting case insensitive search rather than wildcard search. Enter the data item in the Find text box and click Find Next. The system automatically selects the first mapping data item in the Data Item navigation tree. You can click Find Next and Find Prev to select the data item to be checked.
Data Item
Indicates the data items to be checked. The Data Item group box lists all the data items that are configured on each MSC server or each MGW in the Pool. Indicates the period for the system to regularly check the data of NEs within the Pool. The check periods are: Everyday, Every week, Every month, and Single time. Single time indicates that this auto-check task is performed only once.
NOTE If you set the Check Period to Every month and the set Day is not available every month, for example 31, the system performs the checking task on the last day of that month by default in the month of fewer than 31 days.
Check Period
Day
Indicates that the system checks the data of the NEs within the Pool in a specific day of a scheduled week in a month. This parameter is valid only when Check Period is Every week or Every month. Indicates the specific time for the system to check the data of NEs within the Pool.
NOTE When Check Period is Single time, the Check Time should be later than the current time of the system.
Check Time
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool 12.4.8 Managing the Task of Auto-Checking MSC Pool
12.6.10 Parameters for Setting CN ID of an MSC Server

This describes the related parameters on the CN ID Setting tab page in the Pool Parameter Setting dialog box. You can refer to these parameters when you set the CN ID.
Parameter NE Name Description Displays the names of all MSC servers in an MSC Pool.
Issue 06 (2008-12-16)
12-75
Parameter CN ID
Description Indicates the CN ID values of the corresponding MSC servers within the Pool. The CN ID is the unique identification of the MSC server within the Pool. When faults occur in the network planning, you can modify the CN ID value through the M2000. Value range: 0 to 65535.
Related Concepts
Related Tasks
12.3.3.3 Setting CN ID of an MSC Server

This describes the parameters on the CN ID-NRI Setting tab page in the Pool Parameter Setting dialog box. You can refer to these parameters when you set the relation between the CN ID and the NRI.
Parameter Local Office NE Description Name of the MSC server that is configured with the mapping between the NIR and the CN ID
NOTE
l If the MSC Pool manages only the radio access network, this parameter
is not displayed on the client.

l After you modify the NRI of an MSC server, the NE Name column of
the original NRI is displayed as Unknown ne. You need to delete this record.
CN ID NRI
The value of CN ID corresponding to the MSC server in the pool The value of NRI corresponding to the MSC server in the pool Value range: 0 to 1023.
NOTE The NRI values for different MSC servers within the same Pool should not be identical.
Consistency
Indicates whether the NRI of a specific MSC server is consistently configured on all NEs within the Pool. The status is either Consistent or Inconsistent. If the status is Inconsistent, you can Click Synchronize and then Sendto ensure that the NRI of a specific MSC server is consistently configured on all the NEs within the Pool.
12-76
Issue 06 (2008-12-16)
Related Concepts
Related Tasks
12.3.3.4 Adding the NRI of MSC Pool 12.3.3.5 Setting the Mapping Between NRI and CN ID
12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool

This describes the parameters shown on the Non-broadcast LAI Setting tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting Non-broadcast LAIs.
Parameter Local Office NE Non Broadcast LAI Description Name of the MSC server that is configured with Nonbroadcast LAI Value of the Non-broadcast LAI corresponding to the MSC server in the pool Each MSC server in a Pool has a unique Non-broadcast LAI. Shows whether the configuration of Non-broadcast LAI of an MSC server is consistent on all MSC servers in the Pool. The status is either Consistent or Inconsistent. If the status is Inconsistent, you can Click Synchronize and then Send to make the Non-broadcast LAIs of an MSC server consistent on all MSC servers.
Consistency
Related Concepts
Related Tasks
12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool
12.6.13 Parameters for Setting Load-Balancing of an MSC Pool

This describes the parameters shown on the Load Balance Parameter tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting load balancing parameters.
NOTE
When the MSC Pool networking type is radio access network, the load balancing parameters are CN ID, Pool Available Capacity, and Consistency. When the MSC Pool networking type is core network only or core&radio access network, the load balancing parameters are Local Office NE, License Capacity, Pool Available Capacity, and Consistency.
Issue 06 (2008-12-16)
12-77
Parameter Local Office NE
Description Indicates the name of each MSC server in the Pool This parameter is available only when the MSC Pool networking type is radio access network or core & radio access network.
CN ID
The value of CN ID corresponding to the MSC server in the Pool. This parameter is available only when the MSC Pool networking type is radio access network.
License Capacity
Indicates the capacity specified by the license file on the MSC server. This parameter is available only when the MSC Pool networking type is radio access network or core&radio access network.
Pool Available Capacity
Indicates the actual user capacity of the MSC server in the Pool. After the pool is initially established, by setting the pool available capacity of the MSC server, you can balance user allocation according to the defined user capacity when guiding the NNSF node, that is, MGW, RNC, and BSC, to access users. The pool available capacity is the converted capacity value of the license capacity. For example, if an MSC server in the pool is connected to an RNC/ BSCoutside the pool, the pool available capacity of the MSC server in the pool equals the user capacity provided outside the pool subtracted from the license capacity.
NOTE
l The value of Pool available capacity ranges from 0 to
the license capacity.

l The user capacity for an RNC/BSC outside the Pool is
defined during the planning of the MSC Pool network.
Consistency
Shows whether the pool available capacity of an MSC server is uniformly configured on all MSC servers, MGWs, and RNCs/BSCsin the Pool. The status is either Consistent or Inconsistent. If the status is Inconsistent, you can ClickSynchronize and then Send to make the pool available capacity of the MSC server consistent on all MSC servers, MGWs, and RNCs.
Related Concepts
Related Tasks
12.3.3.7 Setting the Load Balancing Parameters of MSC Pool
12.6.14 Parameters for Setting NE State of MSC Pool

This describes the parameters shown on the NE Status Maintenance tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting NE states.
Descriptions of MGW Segregation Parameters

Parameter Linked MSCServer MGW NE Description Name of the MSC server connected to the MGW. Name of the MGW.
NOTE
l The MGWs previously mentioned are the VMGWs that provide
the A-Flex function. VMGWs are logically divided MGWs.

l If MGW NE is displayed as Unknown ne, you can infer that
the information about the MGW is unavailable.
Status
MGW states are Normal, and Segregate.

l
When the MGW is in the Normal state, you can infer that the MGW is running properly. When the MGW is in the Segregate state, you can infer that the MGW supports only the original service rather than new services. If you set the MGW to the Segregate status, the MGW exits smoothly and has no impact on the services of users within the Pool.
CAUTION
When an MSC Pool manages only the RAN, the MGW state parameters are not displayed on the M2000 client.
Descriptions of CN State Parameters

Parameter MSCServer NE Description Displays the names of all MSC servers in an MSC Pool.
NOTE When an MSC Pool manages only the RAN, this parameter is not displayed on the M2000 client.
NE Name CN ID
Displays the names of all NEs configured with CN IDs. Indicates the CN ID values of the corresponding MSC servers within the Pool.
Issue 06 (2008-12-16)
12-79
Parameter CN Node State
Description States of CN nodes, that is, Normal, OffLoad, and Forbidden.

l
When the MSC server is in the Normal state, you can infer that it is running properly. When an MSC server is in the OffLoad state, the RNC/BSC does not send new user service to it. When transferring users, you can set the state of the MSC server from which the users are to be transferred to the OffLoad state. This can optimize the user transfer. When an MSC server is in the Forbidden? state, the RNC/BSC does not send any user service to it. The Forbidden state is applicable when you upgrade the segregation of an MSC server in the MSC Pool.
Related Concepts
Related Tasks
12.3.3.9 Setting the Maintenance State of NEs in MSC Pool

This describes the parameters shown on the Advanced Setting tab page in the Pool Parameter Setting dialog box. You can refer to this topic when setting NRI lengths and Null NRIs.
Parameter NRI The length of NRI The value of Null NRI Description Length of the NRI Value range: 1-10 Value of the Null NRI Value range: 0-1023.
12-80
Issue 06 (2008-12-16)
Parameter PLMN
Description Specifies the carrier of the MSC Pool when radio access network NEs exist.
NOTE
l You can view the information about the radio
access network NEs in the Parameter Setting dialog box only after you specify the operator of the Pool.
l This parameter is unavailable if only radio
access network NEs exist in the MSC Pool.
The parameters for setting the PLMN are as follows:

l
Mobile country code: This three-digit code is used to identify different countries. For example, the MCC of China is 460. The MCC is globally assigned. Mobile network code: This two-digit code is used to identify different network operators, for example, the MNC for China Mobile is 00.
Related Concepts
Related Tasks
12.3.3.6 Setting the Null NRI or the Length of NRI 12.3.3.10 Setting the Operator for MSC Pool
12.6.16 Parameters for Setting Load Unbalance Alarm

This describes the parameters of load balance alarms in the Pool Property Settings dialog box. You can refer to these parameters when you set the load unbalance alarms.
Parameter Threshold of capacity offset Description Indicates the threshold value of the load unbalance alarm for the MSC Pool. When the difference between the maximum and minimum load of the MSC server within the MSC Pool exceeds this threshold value. the system reports the load unbalance alarm for the MSC Pool. Load of the MSC server equals the ratio of the number of the current MSC server subscribers to the total user capacity of the MSC server. Automatic detection period The system periodically detects the interval of each MSC server load within the MSC Pool. The check periods are5 minutes, 15 minutes,30 minutes,1 hour,2 hours,6 hours,12 hours, and 24 hours.
12-81
Automatic detection period
Issue 06 (2008-12-16)
Related Tasks
12.3.1 Setting an Alarm for MSC Pool Load Imbalance
12-82
Issue 06 (2008-12-16)
13 CDMA Pool Management
13
About This Chapter
CDMA Pool Management
This describes the CDMA pool, which is comprised of multiple MSCes. The CBSC of the access network connects to all MSCes in the pool. If the network is deployed as a CDMA pool, user services are distributed to MSCes on the basis of the capacity proportion of each MSCe. In this way, you can balance the traffic of MSCe in the pool in different regions on weekdays or weekends. Therefore, operators calculate the device investment on the basis of the maximum traffic of the city rather than that of each region. This helps operators to optimize network capacity and reduce the investment. You can configure data, monitor the performance, and maintain the CDMA pool network through the M2000 client. 13.1 Basic Knowledge of CDMA Pool This describes the conceptual knowledge related to CDMA Pool management, which consists of basic principle, principle of user transfer, principle of load balance, networking application, and authority management. The basic knowledge helps you better maintain the CDMA Pool. 13.2 Creating CDMA Pool This describes how to create a CDMA pool for all related NEs so that you can perform related operations on the M2000. 13.3 Initial Configuration of CDMA Pool This describes how to perform the initial configuration for the CDMA pool. After you create a new CDMA pool, you should perform the initial configuration. The configuration includes tasks such as setting an alarm for CDMA pool load imbalance, creating an auto-check task for the CDMA pool, and setting attributes for the CDMA pool. The configuration enables you to monitor and maintain the CDMA pool network. 13.4 Commissioning the CDMA Pool Network This describes how to commission the link between the MSCe and each CBSC by using the CDMA single NE user commissioning function. 13.5 Routine Maintenance of CDMA Pool This describes how to perform routine maintenance for the CDMA pool on the M2000 client. The maintenance and operation tasks include checking the CDMA pool alarms, measuring the CDMA pool performance, viewing CDMA pool operation log, monitoring the load of the CDMA pool in real time, checking the MSCe where the specific user is located, displaying the CDMA pool topology, and managing the auto-checking task of the CDMA pool.
13.6 CDMA Pool Network Maintenance This describes how to perform the fault maintenance for the CDMA pool on the M2000 client. The fault maintenance includes the load balancing of the CDMA pool and the data checking of the CDMA pool. 13.7 Management Interface of CDMA Pool This describes the management interfaces of the CDMA Pool and the parameters. This describes the main interface of CDMA Pool operation and maintenance, the interface for viewing CDMA Pool alarms, the CDMA Pool configuration interface, and parameters related to Pool configuration or maintenance operations. In this way, you can perform operations related to CDMA Pool management.
13-2
Issue 06 (2008-12-16)
13.1 Basic Knowledge of CDMA Pool

This describes the conceptual knowledge related to CDMA Pool management, which consists of basic principle, principle of user transfer, principle of load balance, networking application, and authority management. The basic knowledge helps you better maintain the CDMA Pool. 13.1.1 Basic Scheme of CDMA Pool By using the A-Flex technology, the CDMA pool enables a CBSC to share multiple MSCes. The system assigns connected MSs to the relevant MSCes based on the capacity proportion of MSCes. Thus, the MSCe resources can be shared. 13.1.2 Load Balancing Scheme of CDMA Pool On a CDMA Pool network, one CBSC is connected to multiple MSCes within a CDMA Pool. According to the load balancing scheme, the system assigns connected MSs to the relevant MSCe based on the capacity proportion of the MSCes. In this way, the entire CN resources are fully utilized and the investment is reduced. 13.1.3 Transfer Scheme of CDMA Pool Users In the case of MSCe upgrade and network adjustment, the load may be uneven. You can transfer the MSCe users through the M2000 to ensure that the load is balanced among MSCes in the Pool. 13.1.4 CDMA Pool Networking Application This describes the networking schemes of the CDMA Pool in different application scenarios. 13.1.5 User Authority Management of the CDMA Pool A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. You can perform relevant operations provided that you have purchased the license of the M2000 CDMA pool and have relevant rights.
13.1.1 Basic Scheme of CDMA Pool

By using the A-Flex technology, the CDMA pool enables a CBSC to share multiple MSCes. The system assigns connected MSs to the relevant MSCes based on the capacity proportion of MSCes. Thus, the MSCe resources can be shared.
Background
The traffics in different districts and different periods vary depending on many factors, such as the mobility of mobile subscribers, population density, and individual calling habits. During traffic peak periods, for example, festivals, the high load of the network in high traffic districts leads to unstable equipment performance and declined service quality. On the other hand, the equipment in low traffic districts cannot be fully utilized. To reduce the impact of traffic peak, carriers perform more redundancy configurations for equipment capacity and thus the investment is increased. The CDMA pool solution provided by Huawei is intended for the previous problem. Compared with the traditional solution, the pool technology provides the following features:
l
Balancing the load between MSCes to improve the resource efficiency of the entire CN and to reduce the investment on devices Providing disaster recovery and backup at MSCe level
Issue 06 (2008-12-16)
When a MSCe in the pool is faulty, the services of the faulty MSCe are handed over to other MSCes in the pool. Therefore, no services are affected.
l
Reducing the location update between the MSCe and the HLR, and lowering the signaling traffic of the C and D interfaces to improve the capacity of the MSCe. Reducing handoffs between different MSC servers to improve users'conversation quality. Simplifying the network planning: the planning for the CN is different from that for the access network (AN). Reducing the work load incurred by cut over and improving network reliability
l l
Network Structure
As shown in Figure 13-1, the CBSC is connected to all MSCes in an MSC Pool through the A interface. Areas covered by CBSCs are termed as pool areas. The MSCe can be shared in the pool areas. When a subscriber roams into the pool areas, its homing MSCe does not change. Figure 13-1 Networking of the CDMA Pool
Basic Concepts
Table 13-1 describes the basic concepts concerning the CDMA Pool.
13-4
Issue 06 (2008-12-16)
Table 13-1 Basic concepts concerning the CDMA Pool Concept A-Flex Description Refers to the technology used for connecting the CBSC to multiple MSCes. The CBSC on the current network does not support the A-Flex. In addition, the A-Flex supported by CBSCs manufactured by different vendors is not consistent. Therefore, the MGW is the agent of AFlex in the CDMA Pool. MSC Pool MSC Pool Area As shown in Figure 13-1, a group of MSC servers form an MSC Pool. If one or more CBSCs belong to an MSC pool, the service areas covered by the CBSCs form an MSC pool area, as shown in Figure 13-1. The subscribers in the pool area are served by the MSCs in the MSC Pool.
13.1.2 Load Balancing Scheme of CDMA Pool

On a CDMA Pool network, one CBSC is connected to multiple MSCes within a CDMA Pool. According to the load balancing scheme, the system assigns connected MSs to the relevant MSCe based on the capacity proportion of the MSCes. In this way, the entire CN resources are fully utilized and the investment is reduced.
Load Balancing Scheme in Common Situations

1. By using the HASH function, the CDMA pool evenly divides all connected users into 1,000 user blocks. Owing to the randomness of the HASH function, the loads of the 1,000 user blocks divided by the HASH function are the same. 2. 3. On the basis of the capacity proportion of MSCes, the pool distributes a portion of user blocks to each MSCe and specify certain MSCe to process user blocks. The pool configures the user blocks on the MGW. When an MS sends requests for service initialization, the MGW calculates the number of corresponding user blocks on the basis of IMSI and HASH functions. The MGW then finds out the corresponding MSCe server ID and sends the request to the MSCe again.
NOTE
Each MGW contains two tables, namely, user block table and MSC capacity indicator table. The user block table is exported from the MSC capacity indicator table by using a specific algorithm. After you configure or modify the MSC capacity indicator table, the MGW automatically updates the user block table.
For example, the capacity proportion of three MSCes is 1:1:3. The configuration of the user block table is listed in Table 13-2.
Issue 06 (2008-12-16)
13-5
Table 13-2 User block table User Block 0-199 200-399 400-999 Capacity Proportion 20% 20% 60% MSC server ID 1 2 3
Load Balancing Scheme in the Case of NE Link Fault

When the link between an MSCe and an MGW is faulty, the MGW automatically assigns the users on the MSCe to other MSCes in the pool on the basis of capacity proportion. The services of the MSCe are handed over to other MSCes in the pool. Therefore, no services are affected. The load balancing scheme in the case of link or device fault is as follows: 1. 2. Based on the connection status of the MSCe, the MGW automatically connects to MSCes that function well and assigns the users to the MSCes on the basis of capacity proportion. The MGW then transfers users according to the user blocks mapping to the MSCe listed on the user block table.
13.1.3 Transfer Scheme of CDMA Pool Users

In the case of MSCe upgrade and network adjustment, the load may be uneven. You can transfer the MSCe users through the M2000 to ensure that the load is balanced among MSCes in the Pool. 1. You can transfer the users on the basis of the load on each NE of the current network. You can view the load of each NE through the function of real-time monitoring of the CDMA pool. For details, see 13.5.2.1 Setting the Real-Time Monitoring of CDMA Pool. For details about how to transfer users, see 13.6.1.2 Transferring CDMA Pool Users Manually. 2. Upon receiving the user transfer command, the MGW automatically modifies the MSC capacity indicator table and assigns corresponding user blocks on the basis of the new MSC capacity indicator table. The MGW then transfers users according to the user blocks mapping to the MSCe listed on the user block table.
3.
13.1.4 CDMA Pool Networking Application

This describes the networking schemes of the CDMA Pool in different application scenarios. Table 13-3 describes the application scenarios of CDMA Pool networking.
13-6
Issue 06 (2008-12-16)
Table 13-3 Scenarios of CDMA Pool Application Scenario Creating a CDMA network having the CDMA Pool structure Networking Scheme
l
The core network uses the softswitch structure. The MSCe and MGW collectively perform the CMSC function. The access network uses the CBSS system. The CBSC supports the A-Flex function. No special requirements are needed from the MGW. The core network uses the softswitch structure. The MSCe and MGW collectively perform the CMSC function. The access network uses the CBSS system. The CBSC supports the A-Flex function. The MGW performs the A-Flex function.
Evolve the existing CDMA network to the CDMA Pool network
13.1.5 User Authority Management of the CDMA Pool

A user right describes the operations that a user is allowed to perform. Based on user authority, the system authenticates the user operations and determines whether to perform or reject the operations. You can perform relevant operations provided that you have purchased the license of the M2000 CDMA pool and have relevant rights. The M2000 provides the following functions in the CDMA pool:
l
Performing centralized management on the parameters related to the attributes of the CDMA pool. Monitoring the real-time load at intervals of 30s and monitoring the number of idle, poweroff, conversation, and total subscribers, CPU usage, and number of MGW contexts. Collecting the statistics of the performance of global CDMA pool, summing common KPIs at CDMA pool level, and providing the KPIs of global CDMA pool. Supporting data consistency check and synchronization. You can periodically or manually check whether the configuration data on each NE is consistent within the Pool. If data inconsistency exists, a synchronization script is generated to achieve consistency. Supporting the redistribution of subscribers to implement load balancing among the MSCes in the CDMA pool. Supporting the quick search of the MSCe where a specific user is located.
For details about the operations and required rights, see Table 13-4. For details of the CDMA Pool operation authorities, see Table 13-5.
Issue 06 (2008-12-16)
13-7
Table 13-4 CDMA Pool Operation Settings Operation Monitor load in real time, search for users, manually check CDMA pool data, view CDMA pool information, and view pool topology Authority Setting The CDMA Pool is within the management domain of the user. That is, the user is authorized to perform the operations on the CDMA Pool. For details about how to set a user management domain, refer to 4.5.11 Setting the Managed Domain for an OM User. Create, modify, and delete the CDMA pool, configure alarm parameters of the pool, view the performance of the pool, transfer users, manage the automatic check of pool data, configure pool parameters, and synchronize Pool data Table 13-5 CDMA Pool Operation Rights List Bound privileges Creating CDMA Pool Description You can create a CDMA Pool after being granted the operation right.
NOTE
l After a user creates a CDMA
The user has the corresponding operation rights. For details, see Table 13-5. For details on user operation rights, see 4.5.10 Assigning Operation Rights to an OM User.
Type Network management application authority
pool, the user is automatically authorized to modify, delete, and view the pool.
l After a user is authorized to
create, modify, or delete a CDMA pool, the system automatically grants the view right of the pool to the user. That is, the user can view the pool in the administration domain.
Setting advanced alarm parameters
After being granted the authority, you can set the threshold for setting Pool load imbalance alarms. After being granted this right, you can modify the basic information about a CDMA Pool, such as Pool name, description, and NEs. You can delete a CDMA Pool after being granted the operation right.
Adjust the SGSN Pool by adding or deleting NEs
Delete the CDMA Pool
13-8
Issue 06 (2008-12-16)
Bound privileges Setting the parameters of the CDMA Pool
Description After being granted this right, you can configure the parameters related to the Pool properties, such as MSCe Server ID, load balancing parameters, and MGW node management status. After being granted this right, you can re-distribute users between MSCes. After being granted this right, you can synchronize the data between MSCes within a CDMA Pool or the data between MGWs. In this way, you can ensure the data consistency. After being granted this right, you can set auto-check tasks for CDMA Pool data, such as creating, modifying, suspending, and activating tasks, and browsing task information.
Type Network device right
Load re-distribution
Synchronize the check results to the NE
Manage auto check tasks
NOTE
By default, the Guests and Operators user groups own the new equipment rights of the CDMA pool. For details of the new device right, refer to 4.6.2.3 Modifying the Authority to the New Devices in an OM User Group. The right to perform the Pool takes precedence over the right to perform the NEs within the Pool. That is, an authorized user can perform a Pool function even if the user is not authorized to perform the supporting function. For example, to configure the Pool parameters, a user needs to send the modification command to the NEs within the Pool. If the user is authorized to configure parameters for the Pool but is not authorized to issue commands to NEs within the Pool, the user can still issue NE configurations to the NEs.
13.2 Creating CDMA Pool

This describes how to create a CDMA pool for all related NEs so that you can perform related operations on the M2000.
Prerequisite
l
The radio access network NEs support the A-Flex function and they are configured on the basis of network planning. Relevant NEs have been connected to the M2000.
Issue 06 (2008-12-16)

l
You are authorized to create a CDMA pool.
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool node and select Create CDMA Pool from the shortcut menu. Step 3 Set the Pool information in the displayed Create CDMA Pool dialog box. 1. 2. Enter the Pool name in Pool Name. Select the networking type of the Pool on right of the Pool Name box.
NOTE
The supported networking type is Core Network Only, you can select MSCe and MGW.
3.
Select the NEs to be added to the Pool in Optional Nes. Click NEs are added to Selected Nes.
l l l
. Then the
In Selected Nes, you can use Shift or Ctrl to select multiple NEs at the same time. You can click You can click Selected Nes. to add all the NEs in Optional Nes to Selected Nes. or to remove the selected NEs from
For the detailed description of parameters, see 13.7.4 Parameters for Creating/Modifying CDMA Pool. Step 4 Click OK. A Message box is displayed, showing that the Pool is successfully created. You can view the created CDMA Pool in the navigation tree on the Pool Management window. Step 5 Click OK to close the Message dialog box. The Confirm dialog box is displayed, asking you whether to configure the parameters.
l
To configure the parameters immediately, click OK. For details, see 13.3.3 Setting the Parameters of CDMA Pool. To configure the parameters later, click Cancel to close the dialog box.
----End
Postrequisite
1. After a pool is created, you need to perform initial configuration and data check for the pool to check whether the configurations of the CDMA pool are correct. For details about how to perform initial configuration for the pool, refer to 13.3 Initial Configuration of CDMA Pool. For details about how to perform data check, refer to 13.6.2.2 Manually Checking CDMA Pool Data. If the configuration data that must be consistent with all NEs in the pool is inconsistent, you need to synchronize the data on the basis of reference values. For details, refer to 13.6.2.4 Synchronizing CDMA Pool Data. 2. After the data are correctly configured, you can start the pool to perform routine operations and maintenance.
13-10
For details about routine operations and maintenance, refer to 13.5 Routine Maintenance of CDMA Pool.
Related References
13.7.4 Parameters for Creating/Modifying CDMA Pool 13.7.3 Interface Description: CDMA Pool Configuration 13.7.4 Parameters for Creating/Modifying CDMA Pool 13.7.3 Interface Description: CDMA Pool Configuration
13.3 Initial Configuration of CDMA Pool

This describes how to perform the initial configuration for the CDMA pool. After you create a new CDMA pool, you should perform the initial configuration. The configuration includes tasks such as setting an alarm for CDMA pool load imbalance, creating an auto-check task for the CDMA pool, and setting attributes for the CDMA pool. The configuration enables you to monitor and maintain the CDMA pool network. 13.3.1 Setting an Alarm for CDMA Pool Load Imbalance This describes how to set an alarm for the CDMA Pool load imbalance. After you set an alarm for CDMA Pool load imbalance, the system can periodically check the load of the MSCe in the CDMA Pool. The system reports the alarm for the CDMA Pool load unbalance when the deviation between the highest load and the lowest load exceeds the configured threshold. You can perform load transfer according to the alarm information to facilitate balancing loads. 13.3.2 Creating the Task of Auto-Checking CDMA Pool This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. The M2000 provides the function of automatically checking the data that must be consistent on the NEs. You can set the related parameters so that the M2000 can check the data periodically. If inconsistent data exists, an alarm is generated. 13.3.3 Setting the Parameters of CDMA Pool This describes how to set the attributes of the CDMA Pool. You must ensure that the settings of the parameters closely related to Pool features, such as the MSC Server ID and load balancing, are consistent between the MGW side and the MSCe side. The M2000 provides the centralized management function and supports one-click upgrade for maintenance of the parameters on various NEs. This reduces the pool parameter maintenance workload and ensures the correctness of Pool parameter configuration.
13.3.1 Setting an Alarm for CDMA Pool Load Imbalance

This describes how to set an alarm for the CDMA Pool load imbalance. After you set an alarm for CDMA Pool load imbalance, the system can periodically check the load of the MSCe in the CDMA Pool. The system reports the alarm for the CDMA Pool load unbalance when the deviation between the highest load and the lowest load exceeds the configured threshold. You can perform load transfer according to the alarm information to facilitate balancing loads.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized with the relevant privileges of CDMA Pool.
Issue 06 (2008-12-16)
Context
The type of the CDMA Pool load unbalance alarm is Fault Alarm, and the alarm severity is Critical. For details, see ALM-1 Load Unbalance Alarm.
Procedure
Step 2 In the navigation tree, select the CDMA Pool whose alarms for load unbalance need to be set. Right-click the pool and select Property from the shortcut menu. Step 3 In the navigation tree in the left pane of the Pool Property Settings dialog box, select Alarm Load Balance Parameters and set the alarm threshold and automatic check period. See 13.7.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool for the details of parameters. Step 4 Click OK. The Message dialog box is displayed, showing the operation results.
NOTE
If the configuration of alarm parameters fails, the detailed reason for the failure is displayed in the Message dialog box.
Step 5 Click OK. The Message dialog box is closed. ----End
Result
When an alarm for load unbalance is generated, the MSC Pool Management interface displays the message Pool load balance status:Abnormal in red.
Postrequisite
l
You can check detailed information about the Pool load unbalance by querying fault alarms. For details, refer to 13.5.1.1 Viewing the Current Fault Alarms of CDMA Pool. When a load unbalance alarm is generated, you can manually transfer MSCe users to balance the load of each MSCe in the pool. For details, refer to 13.6.1.2 Transferring CDMA Pool Users Manually.
Related References
13.7.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool
13.3.2 Creating the Task of Auto-Checking CDMA Pool

This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. The M2000 provides the function of automatically checking the data that must be consistent on the NEs. You can set the related parameters so that the M2000 can check the data periodically. If inconsistent data exists, an alarm is generated.
Prerequisite
l l
Context
The type of the alarm about inconsistent CDMA Pool data is event alarm, and the alarm severity level is critical. For details, see ALM-2 Data Inconsistency Alarm.
NOTE
You can manually check CDMA Pool data. If the inconsistent data has no effect on the MSC Pool service, you can shield this data. The shielded data is not checked in future operations. For details, see 13.6.2.3 Setting the Checking Items of CDMA Pool Data.
Procedure
Step 2 Select a CDMA pool whose tasks are to be check in the navigation tree and choose Data Consistency Check > Automatic Check from the shortcut menu. Step 3 In the displayed Automatic Check dialog box, click the Check Task tab. In the displayed tab page, click Add. Step 4 Set the parameters of the automatic check task. 1. 2. 3. Select the NE type from the Choose NE Type drop-down list. Enter the task name in Task Name. Select the NE whose data needs be checked in Select NE.
NOTE
4. 5. 6.
Select the data items in the Select Data Item group box. You can use the Find box to quickly find the data item to be checked. Select the period for checking the data from the Check Period drop-down list. Set the check time in Check Time.
For the detailed description of parameters, see 13.7.6 Parameters for Setting the Auto-Check of CDMA Pool. Step 5 Click OK. The added automatic check task is displayed on the Check Task tab page. ----End
Result
If inconsistent data is found, the system reports a critical event alarm.
Postrequisite
If inconsistent data exists, you can perform the following operations:
1. 2. 3.
Check the result to get the information about the inconsistent data. For details, see 13.6.2.1 Viewing the Result of Auto-Checking CDMA Pool Data. On the Check Result tab page of the Automatic Check dialog box, click Manual Check to check the data again. Manually synchronize the inconsistent data to ensure consistency. For details, see 13.6.2.4 Synchronizing CDMA Pool Data.
Related Tasks
13.6.2 Checking CDMA Pool Data
Related References
13.7.6 Parameters for Setting the Auto-Check of CDMA Pool
13.3.3 Setting the Parameters of CDMA Pool

This describes how to set the attributes of the CDMA Pool. You must ensure that the settings of the parameters closely related to Pool features, such as the MSC Server ID and load balancing, are consistent between the MGW side and the MSCe side. The M2000 provides the centralized management function and supports one-click upgrade for maintenance of the parameters on various NEs. This reduces the pool parameter maintenance workload and ensures the correctness of Pool parameter configuration. 13.3.3.1 Parameters of CDMA Pool This describes the parameters of CDMA Pool attributes and how the parameters affect the CDMA Pool execution. 13.3.3.2 Viewing the Parameters of CDMA Pool This describes how to view and set the attributes of CDMA pool on the M2000 client. 13.3.3.3 Setting the MSCe Server ID This describes how to set the MSCe server ID. Generally, the MSCe server ID is already set during the planning of the CDMA pool network. If the MSCe server ID on the MGW side is inconsistent with that on the MSCe side owing to network planning error, you need to change the MSCe server ID on the MSCe side through the M2000 client. In this way, the MGW can transfer users to corresponding MSCes. 13.3.3.4 Setting the Load Balancing Parameters of CDMA Pool This describes how to set the load balance parameters of the CDMA Pool. After setting up a CDMA pool, you should specify the user capacity of each MSCe in the CDMA pool. When you coach the MGW to access users, the MGW distributes users on the basis of the defined user capacity to ensure that the load of each MSCe is balanced. 13.3.3.5 Setting the Maintenance State of NEs in CDMA Pool When an MGW in the Pool needs expansion and upgrade, you can remove the MGW from the Pool by setting the maintenance state of the MGW so that the current services within the Pool are not affected.
Parameters of CDMA Pool

This describes the parameters of CDMA Pool attributes and how the parameters affect the CDMA Pool execution. For detailed description about the CDMA Pool attribute parameters, refer to Table 13-6.
Table 13-6 Parameters of CDMA Pool attributes Parameter MSC Server ID License Capacity Pool Available Capacity Meaning Indicates the ID of the MSCe. The MSC Server ID is the unique identification of the MSCe within the Pool. Indicates the maximum capacity specified by the license file on the MSCe. Indicates the actual user capacity of the MSCe in the Pool. After the pool is initially established, by setting the pool available capacity of the MSCe, you can balance user allocation according to the set user capacity when guiding the MGW to access users. The pool available capacity is the converted capacity value of the license capacity. For example, if an MSCe in the Pool is connected to a CBSC external to the Pool, the pool available capacity of the MSCe in the Pool equals the result subtracting the user capacity provided outside the Pool from the license capacity. The user capacity for a CBSC external to the Pool is defined during the planning of the CDMA Pool network. MGW Node State The MGW states are Normal and Inhibited. If you set the MGW to the Inhibited status, the MGW exits smoothly and has no impact on the services of users within the Pool.
Related Tasks
13.3.3.3 Setting the MSCe Server ID 13.3.3.5 Setting the Maintenance State of NEs in CDMA Pool
Related References
13.7.7 Parameters for Setting MSCe Server ID of CDMA Pool 13.7.8 Parameters for Setting Load Balancing of CDMA Pool 13.7.9 Parameters for Setting NE State of CDMA Pool
Viewing the Parameters of CDMA Pool

This describes how to view and set the attributes of CDMA pool on the M2000 client.
Prerequisite
l l
Issue 06 (2008-12-16)
13-15
Procedure
Step 2 In the navigation tree, right-click the the CDMA pool whose properties is to be viewed and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting dialog box.
Step 3 Click the related tabs to perform the required settings.

l
MSCe Server ID Setting tab: After a pool is initially created, you can set the MSCe Server IDs to uniquely identify the MSCes in the pool so that the MGW can allocates users to associated MSCes. Load Balance Parameter tab: By setting the pool available capacity of the MSCe, you can balance user allocation according to the set user capacity when guiding the MGW to access users. MGW Node Management Status tab: By setting the status of the MGW, the MGW in the pool can normally operate or smoothly exit without affecting the services of users in the pool.
----End
Setting the MSCe Server ID

This describes how to set the MSCe server ID. Generally, the MSCe server ID is already set during the planning of the CDMA pool network. If the MSCe server ID on the MGW side is inconsistent with that on the MSCe side owing to network planning error, you need to change the MSCe server ID on the MSCe side through the M2000 client. In this way, the MGW can transfer users to corresponding MSCes.
Prerequisite
l l
Context
CAUTION
The changes in the MSCE Server ID have great impacts on network services. Huawei recommends that the ID be determined by the network planning first and be modified on the M2000 client.
13-16
Issue 06 (2008-12-16)
Procedure
Step 2 In the navigation tree, right-click the the CDMA pool whose properties is to be viewed and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the MSCe Server ID Setting tab, and choose the MSCe record whose ID needs to be redefined.. Step 4 Double-click the record or click Modify. Step 5 Enter the new MSCe server ID in MSCe Server ID.
NOTE
The value ranges from 0 to 7. The value of the ID cannot be the same as the existing MSCe server ID.
Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to the relevant MSCe NEs. The system also displays Send Status and Send Result of the MML commands.
NOTE
l l
When the system is issuing MML commands, you can click Stop to prevent the system from issuing the commands that have not been issued yet. If all MML commands fail to be run, you can click Send to issue the MML commands again. If part of the MML commands are issued, the Send button is unavailable.
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Related References
13.7.7 Parameters for Setting MSCe Server ID of CDMA Pool
Setting the Load Balancing Parameters of CDMA Pool

This describes how to set the load balance parameters of the CDMA Pool. After setting up a CDMA pool, you should specify the user capacity of each MSCe in the CDMA pool. When you coach the MGW to access users, the MGW distributes users on the basis of the defined user capacity to ensure that the load of each MSCe is balanced.
Prerequisite
l l
Procedure
Step 2 n the navigation tree, select the CDMA pool whose parameters for load balance need to be set. Right-click the pool and select Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the Load Balance Parameter tab, and choose the MSCe record whose available capacity needs to be re-defined.
l
You can view the maximum capacity of each MSCe in the pool on the Load Balance Parameter tab page. The maximum capacity cannot be modified. For detailed description of the parameters on the Load Balance Parameter tab page, refer to 13.7.8 Parameters for Setting Load Balancing of CDMA Pool.
Step 4 Double-click the record or click Modify. Step 5 Enter the new available capacity of the MSCe in New Pool Available Capacity.
l l
The value of real capacity ranges from 0 to the maximum value. The value of real capacity is calculated on the basis of license capacity. For example, if an MSCe within the Pool is connected to a CBSC external to the Pool, the actual user capacity configured by the MSCe within the pool equals the result subtracting the user capacity provided by the Pool from the maximum user capacity.
The user capacity for a CBSC external to the Pool is defined during the planning of the CDMA Pool network.
Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to all the MGWs within the pool, and displays the Send Status and Send Result of the command.
NOTE
l l
Setting the Maintenance State of NEs in CDMA Pool

When an MGW in the Pool needs expansion and upgrade, you can remove the MGW from the Pool by setting the maintenance state of the MGW so that the current services within the Pool are not affected.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool to which you plan to set the NE maintenance state and choose Parameter Setting from the shortcut menu. The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress. After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog box is displayed.
NOTE
Step 3 Click the MGW Node Management Status tab and select the required NE from the list.
NOTE
If the system fails to obtain the information on an MSCe, the MSCe is displayed as Unknown ne on the MGW Node Management Status tab page. In this case, the node status of the MGW cannot be modified.
Step 4 Double-click the record or click Modify. Step 5 Choose the NE status according to your requirements in the Set Status drop box. See 13.7.9 Parameters for Setting NE State of CDMA Pool for detailed information about the meaning of MGW status. Step 6 Click OK. Step 7 In the displayed The MML Commands send to NE dialog box, click Send. The system issues MML commands to the relevant MGWs. The system also displays Send Status and Send Result of the MML commands.
NOTE
l l
Related Concepts
Related References
13.7.9 Parameters for Setting NE State of CDMA Pool
13.4 Commissioning the CDMA Pool Network

This describes how to commission the link between the MSCe and each CBSC by using the CDMA single NE user commissioning function.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to operate the CDMA Pool.
Context
l
The function of single NE user commissioning function is generally used during a site deployment. During the commissioning, you can click Cancel Test or Cancel All to cancel the migration of commissioning users.
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool of the user and choose Single NE Test from the shortcut menu. Step 3 On the Single NE Test tab page, click Test. The Single NE Test dialog box is displayed. Step 4 In IMSI, enter the number of the commissioning user. In Destination Ne, select the destination MSCe to which the commissioning use is to be migrated. Step 5 Click OK. The commissioning starts and the execution results are displayed in Information. ----End
13.5 Routine Maintenance of CDMA Pool

This describes how to perform routine maintenance for the CDMA pool on the M2000 client. The maintenance and operation tasks include checking the CDMA pool alarms, measuring the
CDMA pool performance, viewing CDMA pool operation log, monitoring the load of the CDMA pool in real time, checking the MSCe where the specific user is located, displaying the CDMA pool topology, and managing the auto-checking task of the CDMA pool. 13.5.1 Viewing the Alarms of CDMA Pool This describes how to view the alarms of CDMA Pool. By viewing the alarms of the Pool, you can monitor the network alarms to facilitate network maintenance. CDMA Pool alarms have two types: load unbalancing alarm, which is a fault alarm, and data inconsistency alarm, which is an event alarm. 13.5.2 Monitoring the Load of CDMA Pool in Real Time This describes how to monitor the load of the CDMA Pool in real time. In normal situations, the load balancing algorithm of the system ensures load balance of the CDMA Pool. The load may be unbalanced when the NEs or links are faulty, or when you adjust the network and transfer users. You should monitor the load in the CDMA pool in real time. Thus the load in the CDMA pool is balanced after you perform the related operations such as user transference. 13.5.3 Viewing the Operation Logs of CDMA Pool This describes how to view the operation logs of a CDMA Pool. The operation logs of CDMA Pool record the operations related to the CDMA Pool. 13.5.4 Viewing the MSCe Where a Specific User Is Located This describes how to view the MSCe where a specific user is located. In a CDMA Pool, a CBSC does not map to an MSCe. The users under the same CBSC may also be distributed to different MSCes. The M2000 provides the subscriber search function and IMSI history information search function. By using these functions, you can quickly find the MSCe where a specific user is located and query the MSCes that the user registered with in the history. 13.5.5 Displaying CDMA Pool Topology This describes how to display the CDMA pool topology. The CDMA pool topology is used to display the logical networking structure of the CDMA pool. You can also expand it to view the NEs and their connections within the pool. 13.5.6 Managing the Task of Auto-Checking CDMA Pool This describes how to manage the task of auto-checking CDMA Pool. You can modify and delete an auto-check task of the CDMA Pool. 13.5.7 Viewing the CDMA Pool Performance Report After a CDMA Pool is created, counters of a single NE, such as mobile office direction traffic, call connection ratio, and call drop rate, do not serve as the statistical information about the entire network. By querying the CDMA Pool performance report, you can summarize the performance data reported by NEs and obtain the counter data applicable for the entire network.
13.5.1 Viewing the Alarms of CDMA Pool

This describes how to view the alarms of CDMA Pool. By viewing the alarms of the Pool, you can monitor the network alarms to facilitate network maintenance. CDMA Pool alarms have two types: load unbalancing alarm, which is a fault alarm, and data inconsistency alarm, which is an event alarm.
Context
l
For details of the operations related to the alarms, such as synchronizing, printing, and confirming the alarm, refer to 2.2 Monitoring Network Alarms. On the Pool Management interface, you can right-click an CDMA Pool in the navigation tree and choose Query Alarm > History Fault Alarm from the shortcut menu to view
Issue 06 (2008-12-16)
the history fault alarms of CDMA Pool. For details, refer to 2.2.7.2 Querying History Fault Alarms. 13.5.1.1 Viewing the Current Fault Alarms of CDMA Pool A CDMA Pool fault alarm refers to an alarm that is generated because of unbalanced loads. You can set multiple query conditions to quickly locate the unbalanced loads to perform maintenance. 13.5.1.2 Viewing the Event Alarms of CDMA Pool This describes how to view the event alarms of CDMA Pool. Event alarms of CDMA Pool are mainly generated because of data inconsistency between MSCes or MGWs in the CDMA Pool. You can set multiple query conditions to quickly locate the inconsistent data. Thus you can synchronize them in time to ensure the normal operation of the CDMA Pool.
Related References
13.7.2 Interface Description: Viewing CDMA Pool Alarms
Viewing the Current Fault Alarms of CDMA Pool

A CDMA Pool fault alarm refers to an alarm that is generated because of unbalanced loads. You can set multiple query conditions to quickly locate the unbalanced loads to perform maintenance.
Prerequisite
l l
Context
A CDMA Pool fault alarm refers to an alarm that is generated because of unbalanced loads. The alarm type is internal NM. For details, refer to ALM-1 Load Unbalance Alarm. To view the current fault alarms of specific NEs in the MSC Pool, you can use one of the following methods:
l l
Use the alarm query function described in 2.2.7 Querying Alarms. View the icon color and alarm balloon of the NE on the M2000 physical topology view or the Pool topology view. When an NE generates fault alarms, the color of the NE icon changes to that for the most severe alarm. In addition, an alarm balloon appears beside the icon. The balloon displays the alarm severity identity and number of alarms.
Procedure
Viewing the current fault alarms of CDMA Pool Use one of the following methods to view the Event Alarms window:
13-22
Issue 06 (2008-12-16)
Method From the Pool Management window
Procedure 1. Choose Maintenance > Pool Management or click on the toolbar. The Pool Management window is displayed. 2. Right-click a CDMA Pool in the navigation tree and choose Query Alarm > Current Fault Alarm from the shortcut menu.
From the main window of the M2000 client From the toolbar of the M2000 client
1. Choose Monitor > Current Fault Alarms or click on the toolbar. The Filter dialog box is displayed. 2. Click the Alarm Source tab to select the CDMA Pool whose alarms need to be checked. 3. On the Base Setting tab page, set the time segment of the alarm. 4. Click OK.
For details of the operations related to the alarms, such as synchronizing, printing, and confirming the alarm, refer to 2 Network Monitoring. ----End
Result
In Current Fault Alarms, you can view the details of current fault alarms of CDMA Pool.
Related References
Viewing the Event Alarms of CDMA Pool

This describes how to view the event alarms of CDMA Pool. Event alarms of CDMA Pool are mainly generated because of data inconsistency between MSCes or MGWs in the CDMA Pool. You can set multiple query conditions to quickly locate the inconsistent data. Thus you can synchronize them in time to ensure the normal operation of the CDMA Pool.
Prerequisite
l l
Context
l
Event alarms of CDMA Pool are the event alarms generated when data inconsistency is detected during data auto-check. The alarm type is internal NM. For details, refer to ALM-2 Data Inconsistency Alarm.
Issue 06 (2008-12-16)

l
To view the event alarms of specified NEs in the Pool, you can use the alarm query function described in 2.2.7 Querying Alarms.
Procedure
Viewing the Event Alarms of CDMA Pool Use one of the following methods to view the Event Alarms window: Method From the Pool Management window Procedure 1. Choose Maintenance > Pool Management or click on the toolbar. The Pool Management window is displayed. 2. Right-click a CDMA Pool in the navigation tree and choose Query Alarm > Event Alarm from the shortcut menu. From the main window of the M2000 client From the toolbar of the M2000 client 1. Choose Monitor > Event Alarms or click on the toolbar to view the Filter dialog box. 2. Click the Alarm Source tab to select the CDMA Pool whose alarms need to be checked. 3. On the Base Setting tab page, set the time segment of the alarm. 4. Click OK.
For details of the operations related to the alarms, such as synchronizing, printing, and confirming the alarm, refer to 2 Network Monitoring. ----End
Result
In Event Alarms, you can view the details of event alarms of the CDMA Pool.
Related References
13.5.2 Monitoring the Load of CDMA Pool in Real Time

This describes how to monitor the load of the CDMA Pool in real time. In normal situations, the load balancing algorithm of the system ensures load balance of the CDMA Pool. The load may be unbalanced when the NEs or links are faulty, or when you adjust the network and transfer users. You should monitor the load in the CDMA pool in real time. Thus the load in the CDMA pool is balanced after you perform the related operations such as user transference.
13-24
Issue 06 (2008-12-16)
Application Scenario
The function of monitoring the load of CDMA pool in real time is applied in the following scenarios:
l
After an imbalance load alarm is generated, you can view the load of the pool in real time. Thus you need to learn the status of users on each MSCe and design a transferring plan. After users are manually transferred, you can view the load of the pool in real time. Thus you can monitor the load of NEs in the pool and the progress of user transferring. You can perform scheduled monitoring in routine maintenance.
13.5.2.1 Setting the Real-Time Monitoring of CDMA Pool This describes how to set the real-time monitoring of CDMA Pool. After you set the real-time monitoring of CDMA Pool, the load of the MSCe are displayed in a bar chart or a line chart. From the real-time monitoring chart, you can monitor the number of MSCe subscriber, the CPU usage, and the MGW contexts. 13.5.2.2 Real-Time Monitoring Counters of CDMA Pool This describes the real-time monitoring counters in the Create a Real-time Load Monitor Task dialog box. You can refer to this part when setting real-time monitoring for a CDMA Pool.
Setting the Real-Time Monitoring of CDMA Pool

This describes how to set the real-time monitoring of CDMA Pool. After you set the real-time monitoring of CDMA Pool, the load of the MSCe are displayed in a bar chart or a line chart. From the real-time monitoring chart, you can monitor the number of MSCe subscriber, the CPU usage, and the MGW contexts.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to operate the CDMA Pool. Relevant NEs are properly connected to the M2000.
Context
The real-time monitoring chart of the CDMA Pool can be a line chart or bar chart. The difference is as follows:
l
Line chart: The vertical coordinate refers to the counter values. The horizontal coordinate refers to the monitoring time. Bar chart: The vertical coordinate refers to the counter values. The horizontal coordinate refers to the monitored object
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool to be monitored, and choose Real-time Monitor from the shortcut menu. Step 3 In the displayed Create a Real-time Load Monitor Task, set the monitoring parameters.
1.
Select the monitoring counters. For details of monitoring counters, see 13.5.2.2 Real-Time Monitoring Counters of CDMA Pool.
2.
Select the monitoring period of the counter from the Period drop-down list of the related monitored object. The system refreshes the monitoring counters based on the specified period. The monitoring period can be 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, or 20 minutes.
3.
Select the NEs to be monitored from the NE group box. You can select multiple monitored objects.
Step 4 Click OK. The load changes of the MSCes are displayed in a line chart. you can also select Histogram in Chart Type. You can right-click in the real-time monitoring chart and perform the following operations:
l l l l l
Save as an image: to save the monitoring chart as an image. The image is in .jpg format. Export data: to save the monitoring data to a file. The file is in .csv format. Print: Print: to print the current monitoring chart. Set NE color: to display different NE data by colors.
NOTE
The created tasks are named by Monitor TaskN with N as an integer starting from 1. For example, the first monitoring task is named Monitor Task, and the second task is named Monitor Task2. You can change the task names as required.
----End
Real-Time Monitoring Counters of CDMA Pool

This describes the real-time monitoring counters in the Create a Real-time Load Monitor Task dialog box. You can refer to this part when setting real-time monitoring for a CDMA Pool. The real-time monitoring counters include MSCe Subscribers, MSCe CPU Usage, and Number of MGW Contexts. Table 13-7 shows the meanings of these counters. Table 13-7 Real-time monitoring counters Real-Time Monitoring Counter MSCe Subscribers Total number of subscribers Conversation Description Number of all the users on the MSCe, that is, users inside and outside the Pool. Number of active users on the MSCe, that is, active users inside and outside the Pool. Number of idle users on the MSCe, that is, users inside and outside the Pool
Idle
13-26
Issue 06 (2008-12-16)
Real-Time Monitoring Counter Power-Off
Description Number of users inside and outside the pool who power off their mobile phones on the MSCe Instantaneous mean of the CPU usage on all the online CCU/CSU boards of the MSCe Total number of contexts generated by the VMGW under the MSCe
MSCe CPU Usage
Number of MGW Contexts
13.5.3 Viewing the Operation Logs of CDMA Pool

This describes how to view the operation logs of a CDMA Pool. The operation logs of CDMA Pool record the operations related to the CDMA Pool.
Prerequisite
l l
Procedure
Step 1 Choose System > Log Management > Query Operation Logs . Step 2 In the Filter Condition window, click Choose in the Operation group box. Step 3 In the displayed Operation Select dialog box, view the operations related to the MSC Pool. Step 4 Click OK. Step 5 In the Filter Condition window, set the filtering conditions and then click OK. The procedures are the same as those describes in 5.3.2 Querying Operation Logs. For details of other operations related to logs, such as saving and printing query results, refer to 5 Log Management. ----End
13.5.4 Viewing the MSCe Where a Specific User Is Located

This describes how to view the MSCe where a specific user is located. In a CDMA Pool, a CBSC does not map to an MSCe. The users under the same CBSC may also be distributed to different MSCes. The M2000 provides the subscriber search function and IMSI history information search function. By using these functions, you can quickly find the MSCe where a specific user is located and query the MSCes that the user registered with in the history.
Prerequisite
l l
Issue 06 (2008-12-16)
Procedure
l Search the MSCe that the specified user belongs to at present. 1. 2. 3. Choose Maintenance > Pool Management or click Management window is displayed. on the toolbar. The Pool
In the navigation tree, right-click the CDMA Pool of the user and choose Subscriber Search from the shortcut menu. In the displayed Search for subscribers, select the number type of the user to be found. The number type can be IMSI, MIN, or MDN. The meanings of the number types are as follows:
IMSI: indicates the identity number of the international mobile subscriber. The IMSI number is the only identity number for the subscriber in the network. MIN: It is short for Mobile Identification Number. The CDMA system in north America uses the MIN rather than the IMSI to uniquely identify the mobile subscriber. MDN: It is short for Mobile Directory Number. The MDN is the number that is required by a calling user to call a mobile subscriber in the CDMA PLMN. The use of the MDN is similar to the use of the PSTN in a fixed network.
4.
Enter the number of the subscriber that you need to search in the Number field. Set the result display mode as Basic Information or Full Information.
If you choose Basic Information, the system displays only the information that you are most concerned with, such as IMSI, MDN, and HLR No.. If you choose Full Information, the system displays all the information about the subscriber, for example, the calling number and the called number of the most recent call.
NOTE
5.
Click Search.
If the user to be located is not available in this CDMA Pool, a dialog box is displayed, informing you that no related information about this user is found in this CDMA Pool. If no MSCe is available in the Pool, a dialog box is displayed, informing you that the MSCe is not found in this Pool.
l l
Search the MSCe that the specified user belongs to in the history. 1. 2. 3. 4. Choose Maintenance > Pool Management or click Management window is displayed. on the toolbar. The Pool
In the navigation tree, right-click the CDMA Pool of the user and choose IMSI History Information Search from the shortcut menu. Enter the number of the IMSI that you need to search in the IMSI field. Set a time segment for Time. Set the result display mode as Basic Information or Full Information.
If you select the display mode as Basic Information, the system displays only the user-registered MSCe names. If you select the display mode as Full Information, the system displays the userregistered MSCe names, the time segment of the registration, and the number of users that registered with the same MSCe.
13-28
5.
Click Search.
NOTE
l l
If the user to be located is not available in this CDMA Pool, a dialog box is displayed, informing you that no related information about this user is found in this CDMA Pool. If no MSCe is available in the Pool, a dialog box is displayed, informing you that the MSCe is not found in this Pool.
----End
13.5.5 Displaying CDMA Pool Topology

This describes how to display the CDMA pool topology. The CDMA pool topology is used to display the logical networking structure of the CDMA pool. You can also expand it to view the NEs and their connections within the pool.
Prerequisite
l l
Context
NOTE
l l
Right-click on the topology view of the CDMA Pool and choose Pool Maintenance Main Frame. The Main Frame of the Pool Management interface is displayed. See 3 Topology Management and 2 Network Monitoring for the details about other shortcut menus on the pool topology view. The menus include the functions such as setting forewarning pop and querying NE alarms.
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool whose topology structure you plan to view, and then choose Topo from the shortcut menu. Step 3 In the displayed Main Topology window, view the logical networking structure of the CDMA Pool.
NOTE
Double-click the CN icon the
, all the CN NEs in the Pool are displayed in a rectangle . Double-click icon, all the NEs are collapsed as .
----End
13.5.6 Managing the Task of Auto-Checking CDMA Pool

This describes how to manage the task of auto-checking CDMA Pool. You can modify and delete an auto-check task of the CDMA Pool.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized with the relevant privileges of CDMA Pool. The auto-check task of the CDMA Pool is available.
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool to mange auto-check tasks, and choose Data Consistency Check > Automatic Check from the shortcut menu. Step 3 Click the Check Task tab. Then, you can manage the auto-check task as required. Management Function Browse detailed information about the task Operation
l
In Task Table, you can view the detailed information, such as Task Name, Check Plan, Nes, Data Items, and Task Status. In Task Result, you can view the details of the task execution, such as Task Name, Result, Acknowledgement, Last Check Time, Nes, and Data Items.
Modify the information about the task
1. Select the task to be modified in Task Table. 2. Either double-click the task or click Modify. 3. In the displayed Modify an Automatic Check Task dialog box, modify the information as required. 4. Click OK.
Delete the auto-check task
1. Select the task to be deleted in Task Table. 2. Click Delete. 3. In the displayed Message dialog box, click Yes.
Activate the auto-check task
1. In Task Table, choose a task whose Task Status is Suspended. 2. Right-click Active. Then, the system performs the task based on the scheduled period.
Suspend the auto-check task
1. In Task Table, choose a task whose Task Status is Activated. 2. Right-click Suspend. Then, the system does not perform the auto-check task.
13-30
Issue 06 (2008-12-16)

NOTE
When managing the auto-check tasks of multiple Pools, you can click easily switch between different Pools.
on right of the Pool box to
----End
Related References
13.5.7 Viewing the CDMA Pool Performance Report

After a CDMA Pool is created, counters of a single NE, such as mobile office direction traffic, call connection ratio, and call drop rate, do not serve as the statistical information about the entire network. By querying the CDMA Pool performance report, you can summarize the performance data reported by NEs and obtain the counter data applicable for the entire network.
Prerequisite
l l
Procedure
Step 1 Use either of the methods to open the Performance Report window. Method Operation 1 2 Choose Report > Performance Report > Report Management.
1. Choose Maintenance > Pool Management or click
on the toolbar.
2. Select a CDMA Pool in the navigation tree and choose Performance Query from the shortcut menu. Step 2 Right-click the performance report in the navigation tree and choose Query from the shortcut menu. For information about each performance report, refer to 7.6 MSCe Pool Report Group. Step 3 In the displayed Report Condition Setting dialog box, set the query conditions. 1. Select the time dimension in Time dimension. Then the system summarizes the performance counter results of the query objects based on the time dimension. For example, if Time dimension is set to Hour, the system summarizes the performance counter results at a regular interval of one hour. 2. Select Pool in Object dimension. Pool level: The system summarizes data of all the MSCes in a Pool. For example two MSCes exist in the Pool, and the call attempts of a pool equals the call attempts of MSCe1 and the call attempts of MSCe2. 3.
Issue 06 (2008-12-16)
Select the query object in Object range.

4.
Select the query time in the Date selection and Time segment selection group boxes.
Step 4 Click Query. The query results are displayed in tables.

NOTE
For details of the operations related to performance reports, such as filtering reports, setting query templates, and setting display conditions, refer to 7 Performance Report Management.
----End
13.6 CDMA Pool Network Maintenance

This describes how to perform the fault maintenance for the CDMA pool on the M2000 client. The fault maintenance includes the load balancing of the CDMA pool and the data checking of the CDMA pool. 13.6.1 Balancing CDMA Pool Load This describes how to balance CDMA pool load. In normal situations, the load balancing algorithm maintains the load balance of the CDMA pool. When the load is unbalanced owing to the MSCe upgrade or network adjustment, you can manually move MSCe subscribers on the M2000. Thus, the load of each MSCe in the CDMA pool is balanced. 13.6.2 Checking CDMA Pool Data This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. The M2000 enables you to check the data that must be consistent. In this way, you can perform the related operation according to the check results.
13.6.1 Balancing CDMA Pool Load

This describes how to balance CDMA pool load. In normal situations, the load balancing algorithm maintains the load balance of the CDMA pool. When the load is unbalanced owing to the MSCe upgrade or network adjustment, you can manually move MSCe subscribers on the M2000. Thus, the load of each MSCe in the CDMA pool is balanced. 13.6.1.1 Load Balancing Scheme of CDMA Pool On a CDMA Pool network, one CBSC is connected to multiple MSCes within a CDMA Pool. According to the load balancing scheme, the system assigns connected MSs to the relevant MSCe based on the capacity proportion of the MSCes. In this way, the entire CN resources are fully utilized and the investment is reduced. 13.6.1.2 Transferring CDMA Pool Users Manually This describes how to manually transfer CDMA Pool users when you upgrade one or more MSCes in a CDMA Pool. During the upgrade, you need to transfer all the users on the MSCes to other MSCes in a CDMA Pool and retransfer the users to the MSCe after the upgrade. This ensures the normal operation.
Load Balancing Scheme of CDMA Pool

On a CDMA Pool network, one CBSC is connected to multiple MSCes within a CDMA Pool. According to the load balancing scheme, the system assigns connected MSs to the relevant MSCe based on the capacity proportion of the MSCes. In this way, the entire CN resources are fully utilized and the investment is reduced.
Load Balancing Scheme in Common Situations

1. By using the HASH function, the CDMA pool evenly divides all connected users into 1,000 user blocks. Owing to the randomness of the HASH function, the loads of the 1,000 user blocks divided by the HASH function are the same. 2. 3. On the basis of the capacity proportion of MSCes, the pool distributes a portion of user blocks to each MSCe and specify certain MSCe to process user blocks. The pool configures the user blocks on the MGW. When an MS sends requests for service initialization, the MGW calculates the number of corresponding user blocks on the basis of IMSI and HASH functions. The MGW then finds out the corresponding MSCe server ID and sends the request to the MSCe again.
NOTE
Each MGW contains two tables, namely, user block table and MSC capacity indicator table. The user block table is exported from the MSC capacity indicator table by using a specific algorithm. After you configure or modify the MSC capacity indicator table, the MGW automatically updates the user block table.
For example, the capacity proportion of three MSCes is 1:1:3. The configuration of the user block table is listed in Table 13-8. Table 13-8 User block table User Block 0-199 200-399 400-999 Capacity Proportion 20% 20% 60% MSC server ID 1 2 3
Load Balancing Scheme in the Case of NE Link Fault

When the link between an MSCe and an MGW is faulty, the MGW automatically assigns the users on the MSCe to other MSCes in the pool on the basis of capacity proportion. The services of the MSCe are handed over to other MSCes in the pool. Therefore, no services are affected. The load balancing scheme in the case of link or device fault is as follows: 1. 2. Based on the connection status of the MSCe, the MGW automatically connects to MSCes that function well and assigns the users to the MSCes on the basis of capacity proportion. The MGW then transfers users according to the user blocks mapping to the MSCe listed on the user block table.
Transferring CDMA Pool Users Manually

This describes how to manually transfer CDMA Pool users when you upgrade one or more MSCes in a CDMA Pool. During the upgrade, you need to transfer all the users on the MSCes to other MSCes in a CDMA Pool and retransfer the users to the MSCe after the upgrade. This ensures the normal operation.
Prerequisite
l

Issue 06 (2008-12-16)

l
You are authorized with the relevant privileges of CDMA Pool.
Context
For details about the scenario description and how to manually transfer users, refer to Table 13-9. Table 13-9 Manually transferring users Transfer Method Transferring all the users on the MSCe Application Scenario When you upgrade one or more MSCe in a CDMA Pool, you need to transfer all the users on the MSCe to other MSCes in the CDMA Pool and then upgrade the MSCes to ensure the normal operation. After the upgrade, you need to retransfer the users to the MSCe.
Retransferring all the users on the MSCe
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool to transfer users and choose Load Redistribution from the shortcut menu. The Load Redistribution window is displayed. Step 3 Run different operations according to the user transfer methods.
13-34
Issue 06 (2008-12-16)
Transfer Method Transfer all subscribers on the MSCe to other MSCes
Then 1. Choose the MSCe from which the users are transferred in the Transferred MSCe Source list. 2. Choose the MGW which performs the transferring operation in the Transferred MGW NE Information list. 3. Choose redistribution speed in Redistribution speed. There are three redistribution-speed levels: low speed, medium speed , and high speed. Low speed: Four or five periodic location update periods are required for the redistribution. Medium speed: Two or three periodic location update periods are required for the redistribution. High speed: One or two periodic location update periods are required for the redistribution. 4. Click Transfer Out.
NOTE When the users on the MSCe are being transferred, the list under Transferred MGW NE Information displays the transferring status and progress. You can select the checkbox of a transferring record from the list, and click cancel to cancel the transferring process.
5. Perform Step 4.
Issue 06 (2008-12-16)
13-35
Transfer Method
Then
Retransferring all the users on the MSCe 1. Choose the MSCe from which the users are retransferred in the Transferred MSCe Source list. 2. Choose the MGW which performs the transferring operation in the Transferred MGW NE Information list. 3. Choose redistribution speed in Redistribution speed. There are three redistribution-speed levels: low speed, medium speed , and high speed. Low speed: Four or five periodic location update periods are required for the redistribution. Medium speed: Two or three periodic location update periods are required for the redistribution. High speed: One or two periodic location update periods are required for the redistribution. 4. Click Transfer Back.
NOTE When the users on the MSCe are being transferred, the list under Transferred MGW NE Information displays the transferring status and progress. You can select the checkbox of a transferring record from the list, and click cancel to cancel the transferring process.
5. Perform Step 4. Step 4 Click OK to close the Load Redistribution window. ----End
13.6.2 Checking CDMA Pool Data

This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. The M2000 enables you to check the data that must be consistent. In this way, you can perform the related operation according to the check results. 13.6.2.1 Viewing the Result of Auto-Checking CDMA Pool Data This describes how to view the result of auto-check CDMA Pool data. You can perform the related operations to ensure the data consistency. 13.6.2.2 Manually Checking CDMA Pool Data This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. You can manually check the data on the M2000. After selecting the NEs and data
item, you can view the check results so that you can take related measures to ensure the data consistency on the NE. 13.6.2.3 Setting the Checking Items of CDMA Pool Data This describes how to set the check items of MSC Pool data. The M2000 enables you to set the Pool data check items flexibly. If the inconsistent data found in manual check does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. You can restore the shielded data. 13.6.2.4 Synchronizing CDMA Pool Data This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. When the data is inconsistent, you can synchronize the data to ensure the consistency.
Related Tasks
13.3.2 Creating the Task of Auto-Checking CDMA Pool
Viewing the Result of Auto-Checking CDMA Pool Data

This describes how to view the result of auto-check CDMA Pool data. You can perform the related operations to ensure the data consistency.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized with the relevant privileges of CDMA Pool. At least one auto-check task is performed.
Procedure
Step 2 In the navigation tree, right-click a CDMA Pool, and choose Data Consistency Check > Automatic Check from the shortcut menu. The Automatic Check tab is displayed.
NOTE
You can also view the check results in the area about data consistency in Main Frame. By double-clicking a record, you can view the Automatic Check tab page.
Step 3 Click the Check Task tab. Select the task to be viewed in Task Table. In Task Result, you can view the details of the task execution, such as Result, Nes, and Last Check Time. After you select a record whose Result is Inconsistent or Abnormal, you can perform the following operations: Operation Acknowledgement Description Indicates that the check results are processed. This operation applies to only the results that are not acknowledged.
Operation Unacknowledge
Description Identifies the acknowledged check results as unacknowledged. This operation applies to only acknowledged results.
Step 4 In Task Result, select a result whose Result is Inconsistent or Abnormal. Click Result Detail or the Check Result tab.
NOTE
l l l l l
The Inconsistency Data tree displays the inconsistent data in the check result. You can view the detailed check results in the group box beside the Inconsistency Data tree. The inconsistent data is in red. Click Export Result to save the check results containing the inconsistent data to a .csv file. You need to manually synchronize the inconsistent data. For details, see 13.6.2.4 Synchronizing CDMA Pool Data. If the inconsistent data does not affect the MSC Pool service, you can click Manual Check and then shield this data. For details, see 13.6.2.3 Setting the Checking Items of CDMA Pool Data.
----End
Manually Checking CDMA Pool Data

This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. You can manually check the data on the M2000. After selecting the NEs and data item, you can view the check results so that you can take related measures to ensure the data consistency on the NE.
Prerequisite
l l
Procedure
Step 2 In the navigation tree, right-click the CDMA Pool for which you plan to check the data, and choose Data Consistency Check > Manual Check&Synchronize Data from the shortcut menu. The Manual Check dialog box is displayed. Step 3 Select the NE type from the NE Type drop-down list. Step 4 Select the NE whose data needs be checked in Select NE.
NOTE
Step 5 Select the data items in the Select Data Item group box.

NOTE
l l
You can select multiple data items at the same time. You can use the Find box to quickly find the data item to be checked.
Step 6 Click Start Check. A progress bar is displayed, showing the refresh progress of the NE data cached on the server.
NOTE
l l
Before checking the data, the M2000 server requests NEs for the data to be checked, thus ensuring the consistency between the data on the M2000 server and the data on the NEs. If the M2000 fails to obtain the NE data, the group box at the bottom of the progress bar displays the failure details. Then, the system extracts and checks the data cached on the M2000 server.
Step 7 On the Manual Check tab page, view the check result.
l
If inconsistent data exists, the Inconsistency Data tree displays the data. The group box displays the detailed check result and highlights the inconsistent data in red. If the data is consistent, the Inconsistency Data tree does not display any data. When the system extracts and checks the data cached on the M2000 server, the right bottom of the Manual Check tab page displays The check data may be not the latest data..
l l
----End
Postrequisite
l
If data inconsistency exists, you need manually synchronize the data. For details, see 13.6.2.4 Synchronizing CDMA Pool Data. If the inconsistent data does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. For details, see 13.6.2.3 Setting the Checking Items of CDMA Pool Data.
Setting the Checking Items of CDMA Pool Data

This describes how to set the check items of MSC Pool data. The M2000 enables you to set the Pool data check items flexibly. If the inconsistent data found in manual check does not affect the MSC Pool service, you can shield this data. The shielded data is not checked in future automatic or automatic checks. You can restore the shielded data.
Prerequisite
l l
Procedure
l Shield data checking items. 1. 2. Check the data of the CDMA Pool manually. For details, refer to 13.6.2.2 Manually Checking CDMA Pool Data. In the Inconsistency Data tree, right-click the data to be shielded and choose Shield from the shortcut menu.
You can press Ctrl or Shift to select multiple records.

Issue 06 (2008-12-16)
After the data is shielded, the corresponding background color of the NE record turns grey. You can right-click the NE record of the shielded data item and choose Resume from the shortcut menu to restore the shielded data.
3. l
Click Close to close the Manual Check dialog box.
Restore the shielded checking items. 1. 2. Choose Maintenance > Pool Management or click Management window is displayed. on the toolbar. The Pool
Right-click the CDMA Pool of which the data check items are shielded and choose Data Consistency Check > Cancel the Shield Status of Check Item from the shortcut menu. Select the data and NEs to be restored in Shielded Item. Click OK.
3. 4. ----End
Result
The setting takes effect at the next automatic or manual check.
Synchronizing CDMA Pool Data

This describes how to manually check CDMA pool data. On a CDMA pool network, certain configuration data items must be consistent with all the NEs so that the CDMA pool can operate normally. When the data is inconsistent, you can synchronize the data to ensure the consistency.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to operate the CDMA Pool. The configuration data that must be consistent with all the MSCes and MGWs in the CDMA Pool is inconsistent.
Context
On the basis of data inconsistency, the M2000 generates MML commands for adjusting the data. These commands are issued to the relevant NEs to adjust NE data and achieve data consistency.
NOTE
For certain NE data, the system cannot generate data adjustment command on the M2000. You can view a message in the right pane of the Manual Check tab page, showing the specific data that is not supported. In this case, adjust the data through the LMT of the NE.
Procedure
Step 2 In the navigation tree, choose a CDMA Pool and check the Pool data. You can check the data by using either of the following methods:
Method Manually Checking MSC Pool Data In the consistency status area of Main Frame, double-click the record whose Result is Inconsistent and manually check the data again.
Description For details, see 13.6.2.2 Manually Checking CDMA Pool Data. 1. Double-click the record whose Result is Inconsistent. 2. In the displayed Automatic Check dialog box, click Manual Check on the Check Task tab page. 3. After setting the data check items in the displayed Manual Check dialog box, click Start Check.
Step 3 In the Inconsistency Data tree of the Manual Check tab page, select the data to be synchronized. You can select a data item or a data type. Step 4 Click Synchronize. Step 5 Select an NE in Reference NE. The system uses the data of this NE as the reference of the synchronization. Step 6 Select the NEs to be synchronized in Destination NE. Step 7 Click Generate MML. The right pane on the Manual Check tab page displays the details of the MML commands.
NOTE
l l l
Edit the MML commands in the right pane. Alternatively, click Save MML to save the MML commands as files for subsequent operations. If the data in Destination NE is consistent with that in Reference NE, the right pane displays a message showing that the data is consistent and displays the specific value. If a data item does not support a certain generated MML command, the right pane also displays a message, showing that the data does not support the MML command. In this case, adjust data through the LMT of the NE. The right pane can display a maximum of 500 lines of MML commands. When the MML commands have more than 5000 lines, the system displays that the MML commands are excessive. In this case, you need to click Export MML and manually edit the MML commands. Then, send the script file to the NE through the M2000. For details, see 14.2.1 Creating MML Command Script.
Step 8 Click Send MML to select the issuing mode, and then issue the MML commands. Whether ignore errors in MML execution Click Yes. Command Issuing Mode
When the MML commands are being issued, the system proceeds to issue the remaining MML commands if one MML command is incorrect.
Issue 06 (2008-12-16)
13-41
Whether ignore errors in MML execution Click No.
Command Issuing Mode
When the MML commands are being issued, the system does not issue the remaining MML commands if one MML command is incorrect.
NOTE
l l
When the MML command is being issued, you can click Terminate MML to terminate the command issuing. The execution process of the MML commands is displayed in an MML message in the right pane. In the MML message, Total Count indicates the number of MML commands to be sent, Success Count indicates the number of MML commands that are successfully run on the NE, Fail Count indicates the number of MML commands that fail to be run on the NE, and Unsent Count indicates the number of MML commands that fail to be sent by the M2000. For the MML commands that fail to be issued by the M2000 and those fail to be run on the NE, you can get the related information by checking the MML messages returned from the NE.
Step 9 Click Backward and repeat Step 3 through Step 8 to synchronize other data. ----End
Postrequisite
Click Export Result on the Manual Check tab page to save the results of the MML commands to a file.
13.7 Management Interface of CDMA Pool

This describes the management interfaces of the CDMA Pool and the parameters. This describes the main interface of CDMA Pool operation and maintenance, the interface for viewing CDMA Pool alarms, the CDMA Pool configuration interface, and parameters related to Pool configuration or maintenance operations. In this way, you can perform operations related to CDMA Pool management. 13.7.1 Interface Description: Main Interface of Pool OM This describes the layout of the Main Interface of the MSC Pool, CDMA Pool, and SGSN Pool, and the information about each element on the interface. 13.7.2 Interface Description: Viewing CDMA Pool Alarms This describes the layout of the interface for viewing CDMA Pool alarms and the information about each element on the interface. 13.7.3 Interface Description: CDMA Pool Configuration This describes the CDMA Pool parameter setting interface. That is, the layout of the Pool Parameter Setting interface and the information about each interface element. 13.7.4 Parameters for Creating/Modifying CDMA Pool This describes the parameters used for creating or modifying the CDMA Pool. You can refer to this part when creating or modifying the CDMA Pool. 13.7.5 Parameters for Browsing the Basic Information About the CDMA Pool
This describes the related parameters in the Pool attribute browsing dialog box. You can refer to these parameters when you browse the CDMA Pool basic information. 13.7.6 Parameters for Setting the Auto-Check of CDMA Pool This describes the related parameters in the Create/Modify an Automatic Check Task dialog box. You can refer to these parameters when you create or modify an auto-checking task. 13.7.7 Parameters for Setting MSCe Server ID of CDMA Pool This describes the parameters of the MSCe Server ID Setting tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting the MSCe Server ID. 13.7.8 Parameters for Setting Load Balancing of CDMA Pool This describes the parameters of the Load Balance Parameter tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting load balancing parameters. 13.7.9 Parameters for Setting NE State of CDMA Pool This describes the parameters of the MGW Node Management Status tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting the MGW status. 13.7.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool This describes the parameters of load balance alarms in the Pool Property Settings dialog box. You can refer to these parameters when you set the load unbalance alarms.
13.7.1 Interface Description: Main Interface of Pool OM

This describes the layout of the Main Interface of the MSC Pool, CDMA Pool, and SGSN Pool, and the information about each element on the interface.
Main Interface of MSC Pool OM

The Main Interface of MSC Pool operation and maintenance comprises four areas, as shown in Figure 13-2. For the detailed description of each area, refer to Table 13-10. Figure 13-2 Main Interface of MSC Pool OM
Issue 06 (2008-12-16)
13-43
Table 13-10 Description of the Main Interface of MSC Pool OM SN 1 Name MSC Pool object area Description The created MSC Pool and the NEs in the pool are displayed in a navigation tree. The MSC Pool object area provides a shortcut menu so that you can perform maintenance operations on the pool, such as parameter configuration, user migration, and user search. 2 Status area for load balancing This area periodically refreshes and displays the number of all current pool users of the MSC server within the pool, the capacity load, and the load balance status of the Pool. The load balance status of the Pool can be Normal, Exception, or Unchecked.
l
Normal: The loads between each MSC server within the Pool are balanced. Exception: The offset between the highest loads the lowest load of the MSC server within the Pool exceeds the threshold. Unchecked: The number of MSC servers within the Pool is smaller than 2 and the system cannot identify the state of the Pool.
Shows the operation results of all the auto-check tasks. The status for data consistency is classified into four types: Unchecked, Inconsistent&Acknowledged, Inconsistent&Unacknowledged, and Consistent. The respective meanings are as follows:
l
Unchecked: indicates that no auto-check task is available or the auto-check tasks are not executed. Inconsistent&Acknowledged: indicates that data checked between the NEs is inconsistent and that the checking result is already acknowledged. Inconsistent&Unacknowledged: indicates that the data checked between the NEs is inconsistent and that the checking result is still unacknowledged. Consistent: indicates that the data checked between the NEs is consistent.
13-44
Issue 06 (2008-12-16)
SN 4
Name Task list
Description This area displays the information about manual user transfer and data synchronization tasks. This area provides a shortcut menu so that you can perform the following operations on the task records:
l l l l l
Main Interface of CDMA Pool OM

The Main Interface of CDMA Pool operation and maintenance comprises four areas, as shown in Figure 13-3. For the detailed description of each area, refer to Table 13-11. Figure 13-3 Main Interface of CDMA Pool OM
Table 13-11 Description of the Main Interface of CDMA Pool OM SN 1 Name CDMA Pool object area Description The created CDMA Pool and the NEs in the Pool are displayed in a navigation tree. The CDMA Pool object area provides a shortcut menu so that you can perform maintenance operations on the pool, such as parameter configuration, user migration, and user search.
SN 2
Name Status area for load balancing
Description This child window periodically refreshes and displays the number of all current Pool users of the MSCe within the Pool, the capacity load, and the load balance status of the Pool. The load balance status of the Pool can be Normal, Exception, or Unchecked.
l
Normal: The loads between each MSCe within the Pool are balanced. Exception: The offset between the highest loads the lowest load of the MSCe within the Pool exceeds the threshold. Unchecked: The number of MSCes within the Pool is smaller than 2 and the system cannot identify the state of the Pool.
Shows the operation results of all the auto-check tasks. The status for data consistency is classified into four types: Unchecked, Inconsistent&Acknowledged, Inconsistent&Unacknowledged, and Consistent.
l
Unchecked: indicates that no autocheck task is available or the autocheck tasks are not executed. Inconsistent&Acknowledged: indicates that data checked between the NEs is inconsistent and that the checking result is already acknowledged. Inconsistent&Unacknowledged: indicates that the data checked between the NEs is inconsistent and that the checking result is still unacknowledged. Consistent: indicates that the data checked between the NEs is consistent.
13-46
Issue 06 (2008-12-16)
SN 4
Name Task list
Description Displays the information about the data synchronization tasks in the pool. This area provides a shortcut menu so that you can perform the following operations on the task records:
l l
l l l

This describes the layout of the interface for viewing CDMA Pool alarms and the information about each element on the interface. The interface for viewing CDMA Pool alarms consists of the interface for viewing current fault alarms and the interface for viewing event alarms. After the search conditions are set, the Current Fault Alarms or the Event Alarms interface displays the related alarms. If you select an alarm from the list, the system displays its detailed information and handling suggestions. Figure 13-4 shows the interface. Figure 13-4 Interface for viewing the CDMA Pool alarms
Related Tasks
13.5.1 Viewing the Alarms of CDMA Pool 13.5.1.1 Viewing the Current Fault Alarms of CDMA Pool
13.5.1.2 Viewing the Event Alarms of CDMA Pool
13.7.3 Interface Description: CDMA Pool Configuration

This describes the CDMA Pool parameter setting interface. That is, the layout of the Pool Parameter Setting interface and the information about each interface element. The Pool Parameter Setting interface comprises three tabs, that is, MSCe Server ID Setting, Load Balance Parameter, and MGW Node Management Status. Figure 13-5 shows the pool parameter setting interface. Table 13-12 describes each tab page. Figure 13-5 CDMA Pool parameter setting interface
Table 13-12 CDMA Pool parameter setting interface Tab MSCe Server ID Setting Description Displays all the MSCe Server IDs in the CDMA Pool. Provides the function of modifying the MSCe Server ID. In this way, you can change the MSCe Server ID value on the MSCe side according to actual situations when the MSCe Server IDs set on the MGW and MSCe sides are inconsistent because of network planning mistakes.
13-48
Issue 06 (2008-12-16)
Tab Load Balance Parameter
Description Displays the capacity of MSCes within the CDMA Pool. Provides the function of changing the available MSCe Pool capacity. In this way, you can plan the available MSCe capacity within the Pool according to the actual situations. In addition, you can balance user allocation based on the set user capacity when booting the MGWs to access users. For example, if an MSCe within the Pool is connected to a CBSC external to the Pool, the actual user capacity configured by the MSCe within the pool equals the result subtracting the user capacity provided by the Pool from the maximum user capacity.
MGW Node Management Status
Provides the function of setting the MGW maintenance status within the CDMA Pool. The MGW states are Normal and Inhibited. If you set the MGW to the Inhibited status, the MGW exits smoothly and has no impact on the services of users within the Pool.
Related Tasks
13.2 Creating CDMA Pool 13.2 Creating CDMA Pool
13.7.4 Parameters for Creating/Modifying CDMA Pool

This describes the parameters used for creating or modifying the CDMA Pool. You can refer to this part when creating or modifying the CDMA Pool.
Parameter Pool Name Description Indicates the name of the MSC Pool. The value range of the name is as follows:
l l
Issue 06 (2008-12-16)
13-49
Description The Pool description is used to differentiate the CDMA Pools. The value range of the name is as follows:
l l
A maximum of 64 characters. The value can be empty.
Pool Net Type
Indicates the networking type of the Pool. The CDMA Pool networking type supports only the Core Network Only, which contains the MSCe and the MGW.
NOTE When you modify the CDMA Pool, the networking type of the Pool cannot be changed.
Optional Nes
The NEs that can be added to the CDMA Pool are displayed in a navigation tree. Based on the NEs that are connected to the M2000 and the selected networking type of the Pool, the system automatically filters the NEs that can be added to the CDMA Pool.
Selected Nes
The NEs existing in the CDMA Pool are displayed in a navigation tree.
Related Tasks
13.2 Creating CDMA Pool 13.2 Creating CDMA Pool
13.7.5 Parameters for Browsing the Basic Information About the CDMA Pool
This describes the related parameters in the Pool attribute browsing dialog box. You can refer to these parameters when you browse the CDMA Pool basic information.
Parameter Name Description Description Indicates the name of the CDMA Pool. Indicates the description information about the CDMA Pool.
13-50
Issue 06 (2008-12-16)
Parameter Net Type
Description Indicates the networking type of the CDMA Pool. Core Network Only: indicates that the Pool contains only core network NEs, such as MSCe and MGW..
NOTE The CDMA Pool networking type supports only the Core Network Only.
Number of NE
Indicates the specific NEs and the number of the NEs within the CDMA Pool. For example, MSC e(2) MGW (2) indicates that the CDMA Pool contains two MSCes and two MGWs.

This describes the related parameters in the Create/Modify an Automatic Check Task dialog box. You can refer to these parameters when you create or modify an auto-checking task.
Parameter Choose NE Type Task Name Description Indicates the NE type of the data to be checked. Indicates the name of the auto-check task. The value range of the name is as follows:
l l
Select NE
Indicates the specific NE whose the data to be checked.

NOTE You need select two or more NEs.
Find
Used to quickly find the data item to be checked. Supporting case insensitive search rather than wildcard search. Enter the data item in the Find text box and click Find Next. The system automatically selects the first mapping data item in the Data Item navigation tree. You can click Find Next and Find Prev to select the data item to be checked.
Data Item
Indicates the data items to be checked. The Check data item navigation tree lists all the data items that are configured on each MSCe or each MGW in the Pool.
Issue 06 (2008-12-16)
13-51
Parameter Check Period
Description Indicates the period for the system to regularly check the data of NEs within the Pool. The check periods are: Everyday, Every week, Every month, and Single time. Single time indicates that this auto-check task is performed only once.
NOTE If you set the Check Period to Every month and the set Day is not available every month, for example 31, the system performs the checking task on the last day of that month by default in the month of fewer than 31 days.
Day
Indicates that the system checks the data of the NEs within the Pool in a specific day of a scheduled week in a month.
NOTE This parameter is valid only when Check Period is Every week or Every month.
Check Time
Indicates the specific time for the system to check the data of NEs within the Pool.
NOTE When Check Period is Single time, the Check Time should be later than the current time of the system.
Related Tasks
13.3.2 Creating the Task of Auto-Checking CDMA Pool 13.5.6 Managing the Task of Auto-Checking CDMA Pool
13.7.7 Parameters for Setting MSCe Server ID of CDMA Pool

This describes the parameters of the MSCe Server ID Setting tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting the MSCe Server ID.
Parameter NE Name MSC server ID Description Displays the names of all the MSCes in the Pool. Displays the ID of each MSCe within the Pool. The MSC Server ID is the unique identification of the MSCe within the Pool. The value of the MSC Server ID ranges from 0 to 7.
NOTE The changes in the MSCE Server ID have great impacts on network services. Huawei recommends that the ID be determined by the network planning first and be modified on the M2000 client.
13-52
Issue 06 (2008-12-16)
Related Concepts
Related Tasks
13.3.3.3 Setting the MSCe Server ID
13.7.8 Parameters for Setting Load Balancing of CDMA Pool

This describes the parameters of the Load Balance Parameter tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting load balancing parameters.
Parameter Local Office NE License Capacity Pool Available Capacity Description Displays the names of all the MSCes in the Pool. Indicates the capacity specified by the license file on the MSCe. Indicates the actual user capacity of the MSCe in the Pool. After the pool is initially established, by setting the pool available capacity of the MSCe, you can balance user allocation according to the set user capacity when guiding the MGW to access users. The pool available capacity is the converted capacity value of the license capacity. For example, if an MSCe in the Pool is connected to a CBSC external to the Pool, the pool available capacity of the MSCe in the Pool equals the result subtracting the user capacity provided outside the Pool from the license capacity.
NOTE
l The value of Pool available capacity ranges from 0 to
the license capacity.

l The user capacity for a CBSC external to the Pool is
defined during the planning of the CDMA Pool network.
Issue 06 (2008-12-16)
13-53
Parameter Consistency
Description Shows whether the Pool available capacity of an MSCe is uniformly configured on all the MGWs in the Pool. The status can be Consistent, Inconsistent or Unchecked.
l
Consistent: Indicates that the Pool available capacity of an MSCe is uniformly configured on all the MGWs in the Pool. Inconsistent: Indicates that the Pool available capacity of an MSCe is not uniformly configured on all the MGWs in the Pool. Unchecked: Indicates that the capacity information about the MSCe is not configured on all the MGWs in the Pool.
Related Concepts
13.7.9 Parameters for Setting NE State of CDMA Pool

This describes the parameters of the MGW Node Management Status tab page in the Pool Parameter Setting dialog box. You can refer to this part when setting the MGW status.
Parameter MSCe NE MGW Name MSC Server ID CN Node State Description Displays the names of all the MSCes connected to the MGW in the Pool. Displays the names of all the MGWs in the Pool. Displays the ID of each MSCe within the Pool. The MGW status can be Normal or Inhibited. The respective meanings are as follows:
l l
Normal: The MGW runs normally. Inhibited: The MS does not send the inhibited MGW any request for initializing services. If you set the MGW to the Inhibited status, the MGW exits smoothly and has no impact on the current services within the Pool.
Related Concepts
13-54
Issue 06 (2008-12-16)
Related Tasks
13.3.3.5 Setting the Maintenance State of NEs in CDMA Pool
13.7.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool

This describes the parameters of load balance alarms in the Pool Property Settings dialog box. You can refer to these parameters when you set the load unbalance alarms.
Parameter Threshold of capacity offset Description Indicates the threshold of the load unbalance alarm for the CDMA Pool. When the difference between the maximum and minimum load of the MSCe within the CDMA Pool exceeds this threshold, the system reports the load unbalance alarm of the CDMA Pool. Load of the MSCe equals the ratio of the number of current MSCe subscribers to the total user capacity of the MSCe. The system periodically detects the interval of each MSCe load within the CDMA Pool. The check periods are 15 minutes,30 minutes,1 hour,2 hours, 6 hours,12 hours, and 24 hours.
Automatic detection period
Related Tasks
13.3.1 Setting an Alarm for CDMA Pool Load Imbalance
Issue 06 (2008-12-16)
13-55
14 Integrated Task Management
14
About This Chapter
Integrated Task Management
The M2000 provides the function of integrated management of scheduled tasks. Thus, you can browse information such as the task status and the progress. You can also create, modify, and delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and save task result files to the client. 14.1 Basic Knowledge The integrated task management integrates the concepts such as types of integrated tasks, task scheduling parameters, states of timing tasks. The knowledge of integrated task management helps you perform the operations related to the integrated task management. 14.2 Creating Timing Tasks for Users The M2000 enables you to create customized tasks. Thus, you can create timing tasks by setting common parameters and extended parameters to maintain a network. 14.3 Modifying Timing Tasks for Users You can modify some parameters of created user-scheduled tasks in the M2000. If a userscheduled task is finished, you cannot modify the parameters. 14.4 Modifying Data Synchronization Due to the reasons such as communication interruption, partial data may be missing from the M2000. The synchronization function enables the M2000 to obtain the latest data from the NEs. For an existing data synchronization task, you can modify some parameters of the task. Only users in the administrator group can modify the parameters of the task. If a data synchronization task is complete, you cannot modify the parameters. 14.5 Modifying Database Capacity For an existing task of database capacity management, you can modify some parameters of the task. Only users in the administrator group can modify the parameters of the task. If a task of database capacity management is complete, you cannot modify the parameters. 14.6 Modifying Data Export The file export function enables you to periodically export various data to a specified directory of the server. Using this function, you can externally save the data. The exported data is saved in the database. You can set condition parameters to export the data meeting your requirement, such as performance data, configuration data, and log data. After modifying the export conditions, you can export data by using the new parameters.
14.7 Modifying Data Backup in the M2000 You can modify common parameters and detailed parameters of a data backup task in the M2000 system. 14.8 Modifying Alarm Timing Acknowledgement This task describes how to modify parameters of an alarm timing acknowledgement task created by the M2000. 14.9 Modifying NE License Sharing Management NE license sharing management is used to check the license resources on the license sharing group and on the NEs in the group at a specific time every day. In this way, you can learn the situation of NE license sharing. This task is a system timing task and you can modify the start time to carry out the task. 14.10 Managing Timing Tasks You can view the status of user scheduled tasks and perform the operations such as suspend, delete, cancel, and undo these tasks. 14.11 Browsing the Information of Timing Tasks The M2000 offers the integrated task browsing function, which allows the authorized users to browse tasks. 14.12 Checking the Task Progress You can view the progress of all the sub-tasks of a specific task or a CME task. 14.13 Checking the Task Execution You can view the last execution results of a timing task 14.14 Downloading Result Files This describes how to download the results of timing tasks. You can save the results of timing tasks on the server to the local client in .txt format. 14.15 Reference for Integrated Task Management Interfaces This part describes the integrated task management interfaces and related information such as the parameters used in the integrated task management. This helps you understand the functions of integrated task management.
14-2
Issue 06 (2008-12-16)
14.1 Basic Knowledge

The integrated task management integrates the concepts such as types of integrated tasks, task scheduling parameters, states of timing tasks. The knowledge of integrated task management helps you perform the operations related to the integrated task management. 14.1.1 Types of Integrated Tasks The M2000 categorizes the centrally-managed timing tasks based on execution periods, functions, and task features. 14.1.2 System Timing Tasks The system timing tasks are created by the M2000 during system installation or upgrade. The omc user is the Creator of system timing tasks.omc Such tasks involve database capacity management, NIC, synchronization, file interface, alarm acknowledgement, NE license sharing management, and backup (excluding NE backup). 14.1.3 User Timing Tasks User timing tasks are created and defined by users to meet the requirements of network maintenance. Such tasks consist of MML script, RRS scheduled task, uplink frequency scan, dual home management, NE software download, NE backup, HSL script, neighbor cells optimizing, CME upload, CME download, and network health check. 14.1.4 Task Scheduling Parameters The task scheduling parameters are the parameters related to the task execution type, task start time, task execution period, and execution times. 14.1.5 States of a Scheduled Task A timing task has four states: idle, active, suspended, and complete. The CME task has an additional state, that is, archiving. 14.1.6 Customizing the Interface for Managing Timing Tasks This describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks meeting the condition in the task list.
14.1.1 Types of Integrated Tasks

The M2000 categorizes the centrally-managed timing tasks based on execution periods, functions, and task features.
Tasks Divided According to Execution Period

According to the execution period of tasks, the M2000 divides the centrally-managed timing tasks into two types: one-time task and periodic task. Table 14-1 describes the meanings of each task type. Table 14-1 Tasks divided according to execution period Task Type One-time task Periodic task
Issue 06 (2008-12-16)
Description A task is performed only once at a specific time. A task is performed periodically after a specific time.
Tasks Divided According to Functions

According to the functions of tasks, the M2000 divides the centrally-managed timing tasks into categories of database capacity management, file interface, NE Information Collector (NIC), others, synchronization, backup, CME, and network health check. Table 14-2 describes the meanings of each task type.
NOTE
l l
CME tasks support RNC and NodeB NEs only. Therefore, CME tasks are available only after you install the CME software that maps with the NE version. Network health check tasks are available only after you purchase and install the relevant components.
Table 14-2 Tasks divided according to functions Task Type Database Capacity Management Description The system periodically deletes the data that reaches the specified Hold Days in the Database from the database. This task ensures the capacity of databases to be kept within a proper range and prevents faults caused by insufficient database capacity. By default, the maximum Hold Days in the Database is 90 days. The value cannot exceed 90 days. The databases that can be managed involve operation log, system log, security log, NE operation log, NE security loge, alarm database, and performance data. File Interface This task enables you to export various data to a specified directory of the server periodically. In this way, you can externally save the data. The exported data remains in the database. The data that can be exported consists of performance data, configuration data, NE operation log, NE security log, inventory data, alarm data, network management operation log, network management system log, and network management security log. NIC This task provides data for the Nastar during the performance analysis, and the querying and checking of configuration data.
l
NE Basic Information Export: providing basic NE information for the Nastar. NIC CMExport: providing data for the Nastar during the querying and checking of NE configuration data.
14-4
Issue 06 (2008-12-16)
Task Type Others
Description This task type involves MML script, PRS scheduled task, uplink frequency scan, dual home management, alarm acknowledgement, NE license sharing management, NE software download, HSL script, and neighbor cell optimizing.
l
MML Script: After an MML script is configured, the M2000 can deliver commands in the script in batches. Therefore, you need not deliver the commands one by one. PRS Scheduled Task: You can set PRS scheduled tasks in the M2000 to collect the performance data and generate performance reports of your interest. Frequency Scan: providing uplink frequency data for the Nastar during the analysis of the uplink interference. Dual Home Management: The system checks the data of dual home NE pairs periodically or on schedule to see whether the data is consistent. Thus, you can ensure that an MSC server can take over some or all data of the other MSC server. Alarm Acknowledgement: acknowledging the faults or event alarms that meet the user-defined conditions regularly to reduce operations. NE License Sharing Management: The system periodically checks the license resources on the license sharing group and on the NEs in the group to learn the situation of NE license sharing. NE Software Download: downloading NE adaptation software from the M2000 server to specified NEs regularly. Thus, the NE versions can be delivered to the NE within the scheduled time. HSL Script: modifying NE parameters and obtaining alarm data by running the preset HSL scripts. Neighbor Cells Optimizing: providing data for Nastar during the analysis and optimization of neighbor cells.
Synchronization
Due to reasons such as communication interruption, data may be missing. The synchronization function enables the M2000 to obtain the latest data from NEs. The synchronization tasks involve NE configuration data, NE log, inventory data, and alarm.
Issue 06 (2008-12-16)
14-5
Task Type Backup
Description The M2000 supports saving the server data and NE data as backup files to a specified directory on the server. The saved data can be used to restore the system and NEs in the event of data missing or the abnormality of the system and NEs. The backup task consists of NE backup and server backup. The data that can be backed up on the M2000 consists of configuration data and log data. The system files and operating system cannot be backed up.
CME
The CME task consists of CME upload tasks and CME download tasks.
l
CME Upload: uploading the configuration data of NEs specified by the user periodically to the CME server to ensure that the CME uses the latest NE data for configuration. CME Download: delivering the data configured by the CME to NEs to ensure that the configured data takes effect on NEs.
Network Health Check
The network health check checks the status of NE devices and M2000, performance of NE devices, and alarm information. This task outputs the health check report in .html format. The network health check can find potential problems, avoid severe faults, and ensures the normal operation of devices. For details, refer to the online help on the network health check.
Tasks Divided According to Task Features

According to different task features, the M2000 divides the centrally-managed timing tasks into system timing tasks and user timing tasks. Table 14-3 describes the meanings of each task type. Table 14-3 Tasks divided according to task features Task Type System Timing Tasks Description System timing tasks are necessary for the normal operation of the M2000 system. Such tasks consist of database capacity management tasks, NIC tasks, synchronization tasks, file interface tasks, alarm acknowledgement tasks, NE license sharing management tasks, and backup tasks (excluding NE backup). For details, see 14.1.2 System Timing Tasks.
14-6
Issue 06 (2008-12-16)
Task Type User Timing Tasks
Description User timing tasks are created and defined by users to meet the requirements of network maintenance. Such tasks consist of MML script, RRS scheduled task, uplink frequency scan, dual home management, NE software download, NE backup, HSL script, neighbor cells optimizing, CME upload, CME download, and network health check. For details, see 14.1.3 User Timing Tasks.
14.1.2 System Timing Tasks

The system timing tasks are created by the M2000 during system installation or upgrade. The omc user is the Creator of system timing tasks.omc Such tasks involve database capacity management, NIC, synchronization, file interface, alarm acknowledgement, NE license sharing management, and backup (excluding NE backup). The M2000 uses
NOTE
to indicate system timing tasks and
to indicate user timing tasks.
l l l
Only users in the Administrators group can manage and view system timing tasks. Other users have no such authority. The system timing tasks cannot be copied or deleted. Only some parameters of the system timing tasks can be modified. You cannot suspend or delete the database capacity management tasks. You can suspend or delete synchronization tasks and backup tasks by setting a time point. Then the system automatically suspends or deletes such tasks at that time point.
Table 14-4 describes system timing tasks. Table 14-4 System timing tasks Task Type Database Capacity Management Task Name Performance Data NE Operation Log NE Security Log Alarm Data Operation Log System Log Security Log Description For details, see 14.5.7 Modifying the Capacity of Performance Database. For details, see 14.5.4 Modifying the Capacity of NE Operation Log Database. For details, see 14.5.5 Modifying the Capacity of NE Security Log Database. For details, see 14.5.6 Modifying the Capacity of Alarm Database. For details, see 14.5.1 Modifying the Capacity of Operation Log Database. For details, see 14.5.2 Modifying the Capacity of System Log Database. For details, see 14.5.3 Modifying the Capacity of Security Log Database.
14-7
Issue 06 (2008-12-16)
Task Type File Interface
Task Name Performance Data Export Configuration Data Export NE Operation Log Export NE Security Log Export Inventory Data Export Alarm Data Export Operation Log Export System Log Export Security Log Export
Description For details, see 14.6.1 Modifying the Export of Performance Data. For details, see 14.6.3 Modifying the Export of Configuration Data. For details, see 14.6.7 Modifying the Export of NE Operation Log. For details, see 14.6.8 Modifying the Export of NE Security Log. For details, see 14.6.9 Modifying the Export of Inventory Data. For details, see 14.6.2 Modifying the Export of Alarm Data. For details, see 14.6.4 Modifying the Export of Operation Log. For details, see 14.6.5 Modifying the Export of System Log. For details, see 14.6.6 Modifying the Export of Security Log. For details, see 14.6.10 Modifying the Export of Basic NE Information. For details, see 14.6.3 Modifying the Export of Configuration Data. For details, see 14.8 Modifying Alarm Timing Acknowledgement. For details, see 14.9 Modifying NE License Sharing Management. For details, see 14.4.2 Modifying the Synchronization of NE Configuration Data. For details, see 14.4.3 Modifying the Synchronization of NE Log. For details, see 14.4.4 Modifying the Synchronization of Inventory Data. For details, see 14.4.1 Modifying NE Alarm Synchronization. For details, see 14.7 Modifying Data Backup in the M2000.
NIC
NE Basic Information Export NIC CMExport
Others
Alarm Acknowledgement NE License Sharing Management
Synchronization
NE Configuration Data Synchronization NE Log Synchronization Inventory Data Synchronization Alarm Synchronization
Backup
Server Backup
14-8
Issue 06 (2008-12-16)
14.1.3 User Timing Tasks

User timing tasks are created and defined by users to meet the requirements of network maintenance. Such tasks consist of MML script, RRS scheduled task, uplink frequency scan, dual home management, NE software download, NE backup, HSL script, neighbor cells optimizing, CME upload, CME download, and network health check.
l l
You can create, modify, delete, copy, suspend, and restore user timing tasks. The M2000 uses to indicate system timing tasks and to indicate user timing tasks.
For details about user timing tasks, see Table 14-5.

NOTE
l l
CME tasks support RNC and NodeB NEs only. Therefore, CME tasks are available only after you install the CME software that maps with the NE version. Network health check tasks are available only after you purchase and install relevant components.
Table 14-5 User timing tasks Task Type Backup Task Name NE Backup Description You can regularly save the NE data as backup files to a specified directory on the server. In this way, you can prevent data from being lost, and the backed-up data can be used to restore NE configurations when error occurs. You can back up the data of entire NEs, certain NE types, or certain NEs. You can run the MML script files regularly to deliver commands in the script in batches. Thus, you need not to deliver commands one by one. This task provides uplink frequency data for the Nastar to analyze the uplink interference. This task is performed to download the NE adaptation software from the M2000 to NEs regularly. In this way, the NE versions are delivered to NEs within the scheduled time. Reference For details, see 14.2.3 Creating NE Backup.
Others
MML Script
For details, see 14.2.1 Creating MML Command Script.
Frequency Scan
For details, see 10.4.2.1 Creating a Task of Collecting the Uplink ARFCN Data. For details, see 14.2.2 Creating Software Download.
NE Software Download
Issue 06 (2008-12-16)
14-9
Task Type
Task Name Dual Home Management
Description The system checks the data of dual home NE pairs periodically or on schedule to see whether the data is consistent. Thus you can ensure that an MSC server can take over some or all data of the other MSC server. By running the preset HSL scripts, you can modify NE parameters or obtain alarm data. This task provides data for Nastar to analyze and optimize neighbor cells.
Reference For details, see 14.2.7 Creating Dual-Home Management.
HSL Script
For details, see 14.2.6 Creating HSL Script. For details, see 10.4.1.1 Creating a Data Collection Task for Neighbor Cell Optimization.
Neighbor Cells Optimizing
CME
CME Upload
This task can upload the For details, see 14.2.4 configuration data of NEs Creating CME Upload. specified by the user to the CME server regularly. In this way the CME can use the latest NE data for configurations.. This task only supports the RNC and NodeB NEs. This task can deliver data configured by the CME to NEs at a designated point. Thus, the data configured by the CME takes effect when delivered to NEs. This task only supports the RNC and NodeB NEs. The network health check consists of device check, alarm check, performance check, and result file compare. This task is performed to find potential problems of devices. The purpose is to avoid severe accidents and ensure the normal operation of the current network. For details, refer to the help on the network health check. For details, see 14.2.5 Creating CME Download.
CME Download
Network Health Check
For details, refer to the online help on the network health check.
14.1.4 Task Scheduling Parameters

The task scheduling parameters are the parameters related to the task execution type, task start time, task execution period, and execution times.
Table 14-6 describes the task scheduling parameters. Table 14-6 Description of the task description parameters Parameter Task Type Description According to different task execution periods, the M2000 divides the execution types of the managed timing tasks into two types: periodic execution and one-time execution. The execution type of the system timing tasks is periodic execution. The execution type of the CM download tasks in user timing tasks is one-time execution. The execution type of the other user timing tasks can be periodic execution or one-time execution. Indicates start time of periodic tasks and one-time tasks set upon task creation, including date and time. The start time of tasks should be later than the current server time. Interval between periodic tasks. It has two enlistment: unit and duration. The task execution period can be represented by month, week, day, hour, and minute. Second is not supported. The period interval range is as follows: 1 to 12 for month, 1 to 52 for week, 1 to 365 for day, 1 to 8760 for hour, and 1 to 525600 for second. Indicates execution times of a periodic task. The execution times range from 0 to 65535. The value 0 indicates no limit.
Task start time
Period
Run Times
If the scheduling parameters of the entire network NE backup task are: Execution type = Periodicity, Start time = 2006-10-21 09:07:28, Execution period = 1 day, and Period execution times = 0, infer that the system start to carry out the entire network NE backup task every day on 2006-10-21 09:07:28.
14.1.5 States of a Scheduled Task

A timing task has four states: idle, active, suspended, and complete. The CME task has an additional state, that is, archiving. The states of a scheduled task change with different operations. For details, see Figure 14-1.
Issue 06 (2008-12-16)
14-11
Figure 14-1 State transition of a scheduled task
State transition of a scheduled task is as follows:

l l l l l l
A scheduled task is in the idle state after it is initially created. An idle task is changed to the running state after being scheduled. A idle task is changed to the suspended state after being suspended. A running task is changed to the idle state after being cancelled. A suspended task is changed to the idle state after being restored. If a task need not be scheduled after being performed, it is in the finished state. If it needs to be scheduled again, it returns to the idle state.
If a CME task is in the complete state and you terminate the task, the CME task is in the archiving state. When a timing task is in the idle, suspended, or complete state and a CME task is in the archiving state, you can delete the timing task.
14.1.6 Customizing the Interface for Managing Timing Tasks

This describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks meeting the condition in the task list.
Prerequisite
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Perform different operations according to different customized requirement. Customized Requirement Operation
Customize the navigation tree. Procedure 1. Right-click in the navigation tree and choose Filter Type from the shortcut menu. The Filter Type dialog box is displayed. 2. Select the timing task type to be displayed. By default, all the timing task types that the current user is authorized to browse are displayed. Customize the task list Procedure 1. Right-click the task list and select Filter Task. The Task Filter Setting dialog box is displayed. 2. Set the User Name, Category, Task State, and Last Run Result as the filtering conditions. For detailed parameter description, refer to 14.15.2 Parameters for Setting Filtering Conditions. Step 3 Click OK to save the setting. ----End
Related References
14.15.2 Parameters for Setting Filtering Conditions
14.2 Creating Timing Tasks for Users

The M2000 enables you to create customized tasks. Thus, you can create timing tasks by setting common parameters and extended parameters to maintain a network. 14.2.1 Creating MML Command Script The script file is a text file recording MML commands for one NE or multiple NEs of the same type. After the MML command scripts are created, you can deliver commands in the script files in batch and need not manually deliver commands one by one. 14.2.2 Creating Software Download The software download task means downloading NE mediation software from the M2000 server to specified NEs. After you create the software download task, the NE mediation software is delivered to NEs at the specified time. 14.2.3 Creating NE Backup The NE backup means saving NE data as backup files to a specified directory on the server. The backing up of NE data prevents the data from missing and restores an NE when error occurs. 14.2.4 Creating CME Upload
The CME upload means uploading configuration data of NEs to the CME server side according to user-selected NEs. After you create the CME upload, CME can configure the latest NE data. 14.2.5 Creating CME Download Through a CME download task, you can download NE data configured by the CME to NEs. 14.2.6 Creating HSL Script HSL scripts provides the function of connecting NEs, sending MML commands, and accessing databases. By running the preset HSL scripts, you can perform the operations such as modifying NE parameters and getting alarm data. 14.2.7 Creating Dual-Home Management This describes how to create dual homing management tasks. After you create a dual-homing management task, the system checks the data of dual home pair NE periodically or on schedule and generates check results. The purpose of checking the data is to ensure consistency so that an MSC server can take over some or all data on the other MSC server. 14.2.8 Copying User Timing This provides a shortcut method for creating multiple user timing tasks of the same type.
14.2.1 Creating MML Command Script

The script file is a text file recording MML commands for one NE or multiple NEs of the same type. After the MML command scripts are created, you can deliver commands in the script files in batch and need not manually deliver commands one by one.
Prerequisite
l l
You have logged in to the M2000 client. MML script files are already created.
Context
l l
The MML script task is a user-timing task. The task can be performed for an interval or for one time. Execution Period is expressed in minute, hour, or day. The MML script task allows you to create multiple instances. When the number of MML script instances exceeds the upper limit, creating any more instances fails. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Click New. The New Task dialog box is displayed.
TIP
Choose Task Type > Other > MML Script in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the system sets Task Type to MML Script.
Step 3 Set the information about the task. 1. 2.

14-14
Enter the name of timing task in Task Name. Select MML Script Task from Task Type.
3.
Under Run Type, select Once or Period.
Step 4 Click Next to set the time. Step 5 Click

NOTE
. In the displayed Date/Time Selection dialog box, set the start time.
Start Time must be later than the current server time. If Run Type is set to Once, the Start Time parameter is invalid after you select Run At Once. In addition, the task is performed immediately after the settings are complete. Perform different operations according to the run type.
l l
Step 6 Perform different operations based on task types. Task Type Operation
One-time task Perform Step 7. Periodic task In Period and Run Times fields, enter the associated information. Then, perform Step 7.
Step 7 Click Next to configure the script files. Step 8 Click

l
. In the displayed Open dialog box, select a script file.
If the created task is a one-time task, you can select Redirect Result and set the path of Redirect File to add the task result to the specified redirection file. You can create a nonexistent file. If the redirection file exists, the new messages does not overwrite the original messages. If you set the result redirection of a task, the path of Redirect File cannot be changed after the task is completely created. When creating MML scripts, you must select Select Ne to choose NE objects if the script file are lack of object information.
Step 9 Set Run Mode. If... The MML commands in the script are issued to the NE concurrently. The MML commands are issued to the NE in sequence. Step 10 Click Finished. The added MML script task is displayed in the task list. ----End Then ... You select Collateral
You select Serial
Related References
14.15.8 Parameters for Creating/Modifying/Copying MML Command Script
14.2.2 Creating Software Download

The software download task means downloading NE mediation software from the M2000 server to specified NEs. After you create the software download task, the NE mediation software is delivered to NEs at the specified time.
Prerequisite
Context
l l l
The software download task is a user timing task. The task is performed for an interval or for one time. The unit of Period is Day. You can download software by NE type. Before downloading the mediation software, you need to select the NE type. The software download task allows you to create multiple instances. When the number of software download tasks exceeds the upper limit, creating any more tasks fails. The M2000 allows you to download the mediation software of one NE to NEs of the same type at a time.
Procedure
TIP
Choose Task Type > Other > NE Software Download in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the system sets Task Type to NE Software Download.
Step 3 Set the information about the task. 1. 2. 3. Enter the name of timing task in Task Name. Select NE Software Download from Task Type. In the Run Type drop-down list, select Once or Period.

NOTE
l l
Step 6 Perform different operations based on task types. Task Type Operation.
One-time task Perform Step 7.
14-16
Issue 06 (2008-12-16)
Task Type Periodic task
Operation. In Period and Run Times fields, enter the associated information. Then, perform Step 7.
Step 7 Click Next to select files to be downloaded and NE types. 1. 2. Select an NE type in the NE Type drop-down box. Select a detailed version file and an NE from Edition List and NE List.
Step 8 Click Finish. The newly added software download task is displayed in the task list. ----End
Related References
14.15.9 Parameters for Creating/Modifying Software Download
14.2.3 Creating NE Backup

The NE backup means saving NE data as backup files to a specified directory on the server. The backing up of NE data prevents the data from missing and restores an NE when error occurs.
Prerequisite
Context
l
The backup of NE data takes up too many system resources. Therefore, avoid backing up NE data at busy hours. The NE backup task is a user timing task. This task supports both periodic execution and one-time execution. The Period is represented by Day, Week, and Month. The NE backup task allows you to create multiple instances. When the number of entire NE backup tasks exceeds the upper limit, you cannot create such tasks.
l l
Procedure
TIP
You can choose Task Type > Backup > NE Backup in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the Task Type is NE Backup.
Step 3 Set the basic information of the task. 1. 2. 3.

Issue 06 (2008-12-16)
Enter the name of the task in Task Name. Select NE Backup under Task Type. In the Run Type group box, select Once or Period.
Step 4 Click Next to set the time. Step 5 Click and the Date/Time Selection dialog box is displayed. Set the start time of the task in the dialog box.
NOTE
l l
Step 6 Perform different operations based on the Run Type of the task. Run Type Operation Once Period Perform Step 7. In Period and Run Times fields, enter the associated information. Then, perform Step 7.
Step 7 Click Next to choose the backup mode.

l l l
Select Backup All NE. Select By NE Type. Then, select the required NE type from the NE Type navigation tree. Select By NE. Then, select the required NEs from the NE navigation tree.
The system selects Backup All NE by default. Step 8 Click Finish. The added NE backup tasks are displayed in the task list. ----End
Related References
14.15.10 Parameters for Creating/Modifying/Copying NE Backup
14.2.4 Creating CME Upload

The CME upload means uploading configuration data of NEs to the CME server side according to user-selected NEs. After you create the CME upload, CME can configure the latest NE data.
Prerequisite
l l
You have logged in to the M2000 client successfully. The RNC or NodeB exists on the network and the relevant CME software is installed.
Context
l l
The CME upload is a user timing task. The task can be performed for an interval or for one time. Execution Period is represented in days, weeks, or months.
14-18

l
The CME upload only supports the RNC and NodeB.
Procedure
TIP
Choose Task Type > CME > CME Upload in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the system sets Task Type to CME Upload.
Step 3 Set the basic information for the task. 1. 2. 3. Enter the name of timing task in Task Name. Select CME upload from Task Type. Select Once or Period from the Run Type field box.
Step 4 Click Next to set the run time for the task. Step 5 Click
NOTE
. In the displayed Date/time dialog box, select the start time for the task.
l l
Step 6 Perform different operations according to the run type. The run type consists of two types, that is, once and period. Run Type Once Period Operation Execute Step 7. Enter values in Period and Run Times, and then go to Step 7.
Step 7 Click Next, and then select the types of NEs whose configuration data need be uploaded to the CME server side. Select All NE Configuration Data or NEs. Step 8 Click Finish. The added CME upload task is displayed in the task list. ----End
Related References
14.15.11 Parameters for Creating/Modifying/Copying CME Upload
14.2.5 Creating CME Download

Through a CME download task, you can download NE data configured by the CME to NEs.
Prerequisite
l l
You have logged in to the M2000 client. The RNC or NodeB exists on the network and the relevant CME software is installed.
Context
l l l
CME download is a user scheduled task. The task execution type is once rather than periodic. The CME download only supports the RNC and NodeB.
Procedure
TIP
Choose Task Type > CME > CME Download in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the system sets Task Type to CME Download.
Step 3 Set the information about the task. 1. 2. Enter the name of timing task in Task Name. Select CME download from Task Type.
Step 4 Click Next. You can set parameters as required such as task execution time. If you select Run At Once, the Start Time parameter is invalid. In addition, the task is performed immediately after the related settings are complete. For details of setting parameters, refer to 14.15.14 Parameters for Creating/Modifying CME Download. Step 5 Click . Select required configuration files from the displayed Open dialog box.
Step 6 Click Finished. You can view the upload progress in the displayed dialog box. The added CME download task is displayed in the task list. ----End
Related References
14.15.5 Parameters for Setting Common Information for CME Download Tasks 14.15.14 Parameters for Creating/Modifying CME Download
14.2.6 Creating HSL Script

HSL scripts provides the function of connecting NEs, sending MML commands, and accessing databases. By running the preset HSL scripts, you can perform the operations such as modifying NE parameters and getting alarm data.
Prerequisite
l l
You have logged in to the M2000 client. The HSL script exists.
Context
l l
The HSL script task is a user timing task. The task can be performed for an interval or for one time. Run Period is represented in Minute, Hour, Day, Week, or Month. The HSL script task allows you to create multiple instances. When the number of HSL script instances exceeds the upper limit, creating any more instances fails.
Procedure
TIP
Choose Task Type > Other > Script Executor in the navigation tree. Double-click the node. The New Task dialog box is displayed. By default, the system sets Task Type to Script Executor.
Step 3 Set the information about the task. 1. 2. 3. Enter the name of timing task in Task Name. Select ScriptExecutor under Task Type. In the Run Type drop-down list, select Once or Period.

NOTE
l l
Step 6 Perform different operations based on task types. Task Type Then...
One-time task Perform Step 7. Periodic task In Period and Run Times fields, enter the associated information. Then, perform Step 7.
Step 7 Click Next to select an script file to be uploaded. Step 8 Click besides the Main File text box. In the displayed Open dialog box, select the required script file. This file is the entry file for later script operation.
The entry files are the entry for running the whole script. Other Accessory Files or involved NEs may be used during the task execution. Step 9 If the script file invokes other script files or includes operations to NEs, you need to set Accessory Files or NE Selection. Script File Then...
The main file invokes other script files. Click besides the Accessory Files text box. Select the required script file in the displayed Open dialog box, and then perform Step 10. NE operation is involved, Click besides the NE Selection text box. Select one or more NEs in the displayed Please Select NE dialog box, and then perform Step 10. Perform Step 10.
No script files are invoked, Step 10 Click Finished.
You can view the upload progress in the displayed dialog box. The newly added HSL script task is displayed in the task list. ----End
Related References
14.15.15 Parameters for Creating/Modifying/Copying HSL Script
14.2.7 Creating Dual-Home Management

This describes how to create dual homing management tasks. After you create a dual-homing management task, the system checks the data of dual home pair NE periodically or on schedule and generates check results. The purpose of checking the data is to ensure consistency so that an MSC server can take over some or all data on the other MSC server.
Prerequisite
l l l l
You have logged in to the M2000 client. You have the right to manage dual homing. You have the right to operate the NEs that are related to dual homing. The NE data is updated on the M2000.
Context
l
The dual homing management task is a timing task. For details, refer to 11 Dual-Homing and LN Domain Management. A dual homing task can be performed periodically or once. The units of Period is represented by day, week, and month. The dual homing management task allows you to create multiple instances. When the number of dual homing tasks exceeds the upper limit, creating any more tasks.
14-22
Procedure
TIP
In the navigation tree, choose Task Type > Other > Dual Home Management and double-click the selected node. The New Task dialog box is displayed. The default Task Type is Dual Home Management.
Step 3 Set the information about the task. 1. 2. 3. Enter the name of timing task in Task Name. Enter a task name in Task Name In the Run Type drop-down list, select Once or Period.
Step 4 Click Next. Then perform the related operation according to the task type. Task Type One-time task Then...
l l
To run a task immediately, select Run Immediately. To run a task periodically, click . In the displayed Date/Time Selection dialog box, select the start time and end time. . In the displayed Date/Time Selection dialog box, set the start
Periodic task
1. Click time.
2. Set values in Period and Run Times.
NOTE
Start Time must be later than the current server time.
Step 5 Click Next, and then set the information about the dual homing pair to be checked. 1. 2. Select the dual homing pair from the Dual Homing Pairs drop-down list. Select the data resource type in the Resource Type navigation tree. You can enter the resource type or key word in Search. Then the related resource types are listed under Search. You can quickly select the resource type to be checked by doubleclicking the type. Step 6 Click Finished. The added dual homing management task is displayed in the task list. ----End
Postrequisite
l
You can obtain the information about data consistency by viewing the check result. For details, refer to 14.14 Downloading Result Files. If data inconsistency exists, you need to generate a script to adjust the data difference and synchronize the data. For details, refer to 11.2.5 Generating the Script for Adjusting Difference Data and 11.2.7 Synchronizing the Dual-Homing Data.
Issue 06 (2008-12-16)
Related References
14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management
14.2.8 Copying User Timing

This provides a shortcut method for creating multiple user timing tasks of the same type.
Prerequisite
l l
You have logged in to the M2000 client. The copying user timing task does not support the batch operation.
Context
l
Copying user timing tasks cannot be performed in batches. Therefore, do not select multiple user timing tasks for copying. This function does not support system tasks and single-instance tasks. Multiple-instance user timing tasks have the following types: MML command script task, software download tasks, entire NE backup task, and HSL script task. The number of instances for user timing task is limited. When existing instances for the timing task exceed the maximum value, you cannot copy this type of tasks any more.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select a user timing task that support multiple instances and click Copy. The Copy Task dialog box is displayed. If you have requirement for tasks, modify original basic information parameters such as the task name. For details of modifying the basic parameters, refer to the creation of each type of user timing task. Step 3 Click Next. If you have requirement for tasks, modify the original time parameters such as the start time. For details of modifying the time parameter, refer to the creation of each type of user timing task. Step 4 Click Finish. The newly created user timing task is displayed in the task list. ----End
14.3 Modifying Timing Tasks for Users

You can modify some parameters of created user-scheduled tasks in the M2000. If a userscheduled task is finished, you cannot modify the parameters. 14.3.1 Modifying MML Command Script This describes how to modify some information of the created MML command scripts. 14.3.2 Modifying Software Download
This task is performed to modify some information of created software download. 14.3.3 Modifying NE Backup This is performed to modify the information of the created NE backup tasks. 14.3.4 Modifying CME Upload This describes how to modify some information of the created CME upload task. 14.3.5 Modifying CME Download This describes how to modify some information of the created CME download task. 14.3.6 Modifying HSL Script The task is performed to modify some information of the created HSL script task. 14.3.7 Modifying Dual-Home Management This describes how to modify expired or incorrect dual-homing management tasks as required. The dual-home management function is used to check the data of dual home pair NE periodically or on schedule. You can modify the parameters of a dual-home management task based on your requirement.
14.3.1 Modifying MML Command Script

This describes how to modify some information of the created MML command scripts.
Prerequisite
l l
You have logged in to the M2000 client. The MML command script task is already created.
Context
l
You can modify only the following parameters: Task Name, Start Time, Run Period, Run Times, Script File, and Run Mode. You are not allowed to modify the parameters of a complete MML script task. The Status column shows whether the task is complete. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Other > MML Script in the navigation tree on the left of the window. Step 3 Select a created MML command script task from the task list. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to 14.15.4 Parameters for Setting Common Information and 14.15.8 Parameters for Creating/ Modifying/Copying MML Command Script.
Issue 06 (2008-12-16)
14-25

NOTE
l l
The reset value of Start Time must be later than the current server time. For the MML command script task whose Run Type is Period, the reset value of Run Times should be greater than the number of executed times. You can know the times for which the task has been executed by viewing Executed Times column of the task list. If the task is a one-time task you set the result redirection of a task, the path of Redirect File cannot be changed after the task is completely created.
Step 6 Click OK or Apply. You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.3.2 Modifying Software Download

This task is performed to modify some information of created software download.
Prerequisite
l l
You have logged in to the M2000 client successfully. The software download task is already created.
Context
For an uncompleted software download task, you can modify the following parameters: Task Name, Start Time, Period, Run Times, NE Type, Version, and NE.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Other > NE Software Download in the navigation tree on the left of the window. Step 3 Select an already created software download task from the task list to the right. Step 4 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 5 Click Common parameters or Extended Parameters. For details of resetting parameters, refer to 14.15.9 Parameters for Creating/Modifying Software Download.
NOTE
l l
The reset value of Start Time must be later than the current server time. For the software download task whose Run Type is Period, the reset value of Run Times should be greater than the number of executed times.

You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect during the next running.
----End
Related References
14.3.3 Modifying NE Backup

This is performed to modify the information of the created NE backup tasks.
Prerequisite
l l
You have logged in to the M2000 client. The system has created NE backup tasks.
Context
For an uncompleted NE backup task, you can modify the following parameters: Task Name, Start Time, Period, Run Times, File Path, and backup mode.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Backup > NE Backup in the navigation tree on the left pane of the window. Step 3 Select a created NE backup task from the task list on the upper right pane of the window. Step 4 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 5 Click Common Parameters or Extended Parameters. Reconfigure the parameters by referring to 14.15.4 Parameters for Setting Common Information and 14.15.10 Parameters for Creating/Modifying/Copying NE Backup.
NOTE
l l
For an NE backup task whose Run Type is Period, the reset value of Run Times should be greater than the executed times of the task. The reset value of Start Time must be later than the current server time.
Step 6 Click OK or Apply. You can browse the latest task information in the task list.
NOTE
----End
Related References
14.3.4 Modifying CME Upload

This describes how to modify some information of the created CME upload task.
Prerequisite
l l
You have logged in to the M2000 client. The CME upload task is already created.
Context
l l
CME upload is a timing task. The system supports period tasks and once tasks. The units of Period is represented by day, week, and month. You can modify the following parameters: Task Name, Start Time, Period, Run Times, All NE Configuration Data, and NE. CME upload supports only the RNC and NodeB. This type of task is available only after you install the relevant CME software.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task TypeCMECMECME Upload in the navigation tree on the left of the window. Step 3 Select an already created CME upload task from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common parameters or Extended Parameters. For details of resetting parameters, refer to 14.15.4 Parameters for Setting Common Information and 14.15.11 Parameters for Creating/Modifying/Copying CME Upload.
NOTE
l l
For a CME upload task whose Run Type is Period, the reset value of Run Times should be greater than the number of executed times. The reset value of Start Time must be later than the current server time.
NOTE
----End
Related References
14.3.5 Modifying CME Download

This describes how to modify some information of the created CME download task.
Prerequisite
l l
You have logged in to the M2000 client. The CME download task is already created.
Context
l
CME download supports only the RNC and NodeB. This type of task is available only after you install the relevant CME software. CME download is a user scheduled task. The task execution type is once rather than periodic. You can modify the following parameters: Validate Interval, Preactivate Interval, Activate Interval, Retry after Failure, Partially Retry, Retry Counts, Retry Interval, Stop at Error, Rectify at Error, and Upload Files. Once a subtask is running, you can modify only Stop at Error or Rectify at Error in Extended Parameter. For finished or archived CME download tasks, the parameters are not allowed to change.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > CME > CME Download in the navigation tree. Step 3 Select an already created CME download task from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to 14.15.5 Parameters for Setting Common Information for CME Download Tasks and 14.15.14 Parameters for Creating/Modifying CME Download.
NOTE
The reset value of Start Time must be later than the current server time.
Step 6 Click OK or Apply. You can browse the newest task information in the task list. ----End
Related References
14.15.5 Parameters for Setting Common Information for CME Download Tasks 14.15.14 Parameters for Creating/Modifying CME Download
14.3.6 Modifying HSL Script

The task is performed to modify some information of the created HSL script task.
Prerequisite
l l
You have logged in to the M2000 client. The HSL script task is already created.
Issue 06 (2008-12-16)
Context
For an uncompleted HSL script task, you can modify the following parameters: NE Selection, Task Name, Start Time, Period, and Run Times.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Other > Script Executor in the navigation tree on the left of the window. Step 3 Select an already created HSL script task from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to 14.15.4 Parameters for Setting Common Information and 14.15.15 Parameters for Creating/Modifying/Copying HSL Script.
NOTE
l l
For the HSL script task whose Run Type is Period, the reset value of Run Times must be greater than the executed times. The reset value of Start Time must be later than the current server time.
NOTE
----End
Related References
14.3.7 Modifying Dual-Home Management

This describes how to modify expired or incorrect dual-homing management tasks as required. The dual-home management function is used to check the data of dual home pair NE periodically or on schedule. You can modify the parameters of a dual-home management task based on your requirement.
Prerequisite
l l l l
You have logged in to the M2000 client. A dual homing management task is available. You have the right to manage dual homing. You have the right to operate the NEs that are related to dual homing.
14-30
Issue 06 (2008-12-16)
Context
l
For the dual homing management tasks that are not completely performed, you can modify the information such as Task Name, Start Time, Period, Dual Homing Pairs, and the data resource type of the dual homing pair to be checked. For the dual homing management tasks that are completely performed, the related information cannot be modified. For details of dual homing management, refer to 11 Dual-Homing and LN Domain Management.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Other > Dual Home Management. Step 3 In the task list, double-click a dual homing management task that is not completely performed. Alternatively, select the task and click Attribute. Step 4 Click Common Parameters or Extended Parameters. Set the parameters by referring to 14.15.4 Parameters for Setting Common Information and 14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management.
NOTE
l l
The reset value of Start Time must be later than the current server time. For a dual-homing task whose Run Type is Period, the modified Run Times must be greater than the executed times.
NOTE
----End
Related References
14.4 Modifying Data Synchronization

Due to the reasons such as communication interruption, partial data may be missing from the M2000. The synchronization function enables the M2000 to obtain the latest data from the NEs. For an existing data synchronization task, you can modify some parameters of the task. Only users in the administrator group can modify the parameters of the task. If a data synchronization task is complete, you cannot modify the parameters. 14.4.1 Modifying NE Alarm Synchronization This describes how to modify some information of the NE alarm synchronization task created by the system. 14.4.2 Modifying the Synchronization of NE Configuration Data
This describes how to modify some information of the system-created task for synchronizing NE configuration data. 14.4.3 Modifying the Synchronization of NE Log This describes how to modify some information of the system-created task for synchronizing the NE log. 14.4.4 Modifying the Synchronization of Inventory Data This describes how to modify some information of the system-created task for synchronizing the inventory data.
14.4.1 Modifying NE Alarm Synchronization

This describes how to modify some information of the NE alarm synchronization task created by the system.
Prerequisite
Context
l
The NE alarm synchronization task is a system timing task and only supports the period type. Only users in the administrator group can modify the task. You can modify the following parameters of NE alarm synchronization:Task Name, Start Time, and Period
l l
Procedure
Step 1 Choose Maintenance > Task Management.The Task Management dialog box is displayed. Step 2 Choose Task Type > Synchronization > Alarm Synchronization in the navigation tree on the left of the window. Step 3 Select an already created NE alarm synchronization task from the task list to the right. Step 4 Double-click or click Attribute to open the Attribute dialog box. Step 5 Click Common Parameters. For details of resetting the parameters, refer to 14.15.4 Parameters for Setting Common Information.
NOTE
NOTE
----End
14.4.2 Modifying the Synchronization of NE Configuration Data

This describes how to modify some information of the system-created task for synchronizing NE configuration data.
Prerequisite
Context
l
The synchronization of NE configuration data is the system timing task and only supports the period type. Only users in the administrator group can modify the task. You can modify only the following parameters: Task Name, Start Time, Period, All NE Configuration Data, and NE. The synchronization of NE configuration data is applicable for the CDMA and GSM NEs that do not support manual synchronization.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Synchronization > NE Configuration Data Synchronization node in the navigation tree on the left of the window. Step 3 Select an already created synchronization task of NE configuration data from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data .
NOTE
NOTE
----End
Related References
14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data
14.4.3 Modifying the Synchronization of NE Log

This describes how to modify some information of the system-created task for synchronizing the NE log.
Prerequisite
Context
l
The synchronization of the NE log is the system timing task and only supports the period type. Only users in the administrator group can modify the task. You can modify the following parameters: Task Name, Start Time, and Period. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Synchronization > NE Log Synchronization. Step 3 Select an already created synchronization task of the NE log from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters. For details of resetting the parameters, refer to 14.15.4 Parameters for Setting Common Information.
NOTE
NOTE
----End
14.4.4 Modifying the Synchronization of Inventory Data

This describes how to modify some information of the system-created task for synchronizing the inventory data.
Prerequisite
14-34
Issue 06 (2008-12-16)
Context
l
Inventory data refers to the physical asset information and major logical configuration information. The synchronization of the inventory data is the system timing task and only supports the period type. Only users in the administrator group can modify the task. You can modify the following parameters: Task Name, Start Time, Period, and NE. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Synchronization > Inventory Data Synchronization. Step 3 Select an already created synchronization task of the inventory data from the task list to the right. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.13 Parameters for Modifying the Synchronization of Inventory Data.
NOTE
NOTE
----End
Related References
14.15.13 Parameters for Modifying the Synchronization of Inventory Data
14.5 Modifying Database Capacity

For an existing task of database capacity management, you can modify some parameters of the task. Only users in the administrator group can modify the parameters of the task. If a task of database capacity management is complete, you cannot modify the parameters. 14.5.1 Modifying the Capacity of Operation Log Database You can modify the database capacity management for operation logs. 14.5.2 Modifying the Capacity of System Log Database You can modify the database capacity management for system logs.
14.5.3 Modifying the Capacity of Security Log Database You can modify the database capacity management for security logs. 14.5.4 Modifying the Capacity of NE Operation Log Database You can modify the database capacity management for NE operation logs. 14.5.5 Modifying the Capacity of NE Security Log Database You can modify the database capacity management for NE security logs. 14.5.6 Modifying the Capacity of Alarm Database You can modify the database capacity management for alarm data. 14.5.7 Modifying the Capacity of Performance Database You can modify the database capacity management for performance data.
Related References
14.15.18 Parameters for Modifying Database Capacity
14.5.1 Modifying the Capacity of Operation Log Database

You can modify the database capacity management for operation logs.
Prerequisite
Context
l
As a system periodic task, the database capacity management task for operation logs can be executed only periodically. Only users in the administrator group can modify the task. You can modify the following parameters: Task Name, Start Time, File Format, Compress after Export, and Save Days.
l l
Procedure
Step 1 Choose Maintenance > Task Management.The Task Management dialog box is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Operation Log. Step 3 From the task list, select one database capacity management task that is already created for operation logs. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE

NOTE
----End
14.5.2 Modifying the Capacity of System Log Database

You can modify the database capacity management for system logs.
Prerequisite
Context
l
As a system periodic task, the database capacity management task for system logs can be executed only periodically. Only the users belonging to the administrator group have the right to modify the database capacity management for system logs. You can modify only the following parameters: Task Name, Start Time, File Format, Compress after Export, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > System Logs. Step 3 From the task list, select one database capacity management task that is already created for system logs. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE
NOTE
----End
14.5.3 Modifying the Capacity of Security Log Database

You can modify the database capacity management for security logs.
Prerequisite
Context
l
As a system periodic task, the database capacity management task for security logs can be executed only periodically. Only the users belonging to the administrator group have the right to modify the database capacity management for security logs. You can modify only the following parameters: Task Name, Start Time, Compress after Export, File Format, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Security Log. Step 3 From the task list, select one database capacity management task that is already created for security logs. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE
NOTE
----End
14.5.4 Modifying the Capacity of NE Operation Log Database

You can modify the database capacity management for NE operation logs.
Prerequisite
Context
l
As a system periodic task, the database capacity management for NE operation logs can be executed only periodically. Only the users belonging to the administrator group have the right to modify the database capacity management for NE operation logs. You can modify only the following parameters: Task Name, Start Time, Compress after Export, File Format, and Save Days. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
14-38
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > NE Operation Log. Step 3 From the task list, select one database capacity management task that is already created for NE operation logs. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE
NOTE
----End
14.5.5 Modifying the Capacity of NE Security Log Database

You can modify the database capacity management for NE security logs.
Prerequisite
Context
l
As a system periodic task, the database capacity management task for NE security logs can be executed only periodically. Only users in the administrator group can modify the task. You can modify only the following parameters: Task Name, Start Time, Compress after Export, File Format, and Save Days. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > NE Security Log. Step 3 From the task list, select one database capacity management task that is already created for NE security logs.
Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE
NOTE
----End
14.5.6 Modifying the Capacity of Alarm Database

You can modify the database capacity management for alarm data.
Prerequisite
Context
l
As a system periodic task, the database capacity management task of alarm data can be executed only periodically. Only users in the administrator group can modify the task. You can modify only the following parameters: Task Name, Start Time, Compress after Export, File Format, and Save Days.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select Task Type > Database Capacity Management > Alarm Data. Step 3 From the task list, select one database capacity management task that is already created for alarm data. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE

NOTE
----End
14.5.7 Modifying the Capacity of Performance Database

You can modify the database capacity management for performance data.
Prerequisite
Context
l
As a system periodic task, the database capacity management task for performance data can be executed only periodically. Only users in the administrator group can modify the task. You can modify only the following parameters: Task Name, Start Time, Compress after Export, and Save Days.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Performance Data. Step 3 From the task list, select one database capacity management task that is already created for performance data. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for Modifying Database Capacity.
NOTE
NOTE
----End
14.6 Modifying Data Export

The file export function enables you to periodically export various data to a specified directory of the server. Using this function, you can externally save the data. The exported data is saved in the database. You can set condition parameters to export the data meeting your requirement,
such as performance data, configuration data, and log data. After modifying the export conditions, you can export data by using the new parameters. 14.6.1 Modifying the Export of Performance Data This describes how to modify the export of performance data. Before exporting the performance data, you can modify the related common parameters and extended parameters as required. 14.6.2 Modifying the Export of Alarm Data The M2000 provides the function of exporting alarm data. Before the alarm data is exported, you can modify common parameter and detailed parameter setting of the alarm data task. 14.6.3 Modifying the Export of Configuration Data M2000 provides the function of exporting configuration data. The M2000 supports two types of configuration data export tasks:NIC CMExportandConfiguration Data ExportNIC CMExport tasks provide data for the Nastar to query and check configuration data.Configuration Data Export tasks export the configuration data of specified NEs and back up such data. The exported and backed-up data is used to restore the NE configurations. The two types of configuration data export tasks are system timing tasks. You can modify the Common Parameters and Extended Parameters before exporting configuration data. 14.6.4 Modifying the Export of Operation Log The M2000 offers the function of exporting operation logs. Before carrying out a task of exporting operation logs, you can modify the public parameters and parameter settings of this task as required. 14.6.5 Modifying the Export of System Log The M2000 offers the function of exporting system logs. Before carrying out a task of exporting system logs, you can modify the public parameters and parameter settings of this task as required. 14.6.6 Modifying the Export of Security Log The M2000 offers the function of exporting security logs. Before carrying out a task of exporting security logs, you can modify the public parameters and parameter settings of this task as required. 14.6.7 Modifying the Export of NE Operation Log The M2000 offers the function of exporting NE operation logs. Before carrying out a task of exporting NE operation logs, you can modify the public parameters and parameter settings of this task as required. 14.6.8 Modifying the Export of NE Security Log The M2000 offers the function of exporting NE security logs. Before carrying out a task of exporting NE security logs, you can modify the public parameters and parameter settings of this task as required. 14.6.9 Modifying the Export of Inventory Data The M2000 provides the function of exporting inventory data. Before the inventory data is exported, you can modify common parameter and detailed parameter setting of the inventory data task. 14.6.10 Modifying the Export of Basic NE Information This describes the function of exporting basic NE information provided by the M2000. The exported information is used by the Nastar in performance analysis. Before exporting the basic NE information, you can modify the common parameters and extended parameters of a task.
14-42
Issue 06 (2008-12-16)
14.6.1 Modifying the Export of Performance Data

This describes how to modify the export of performance data. Before exporting the performance data, you can modify the related common parameters and extended parameters as required.
Prerequisite
l l
You have logged in to the M2000 client. The performance data is exported.
Context
l
The M2000 enables you to export performance data based on the performance result query template. The task of exporting performance data is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, File Format, Hold Days, Object, Measurement Period, Export Period, and Delay Time. SBC, IMSOMU, CCF and MRF do not support this function.
l l
Procedure
Step 1 Choose Maintenance > Task Management to view the Task Management window. Step 2 In the navigation tree, choose Task Type > File Interface > Performance Data Export . Step 3 Select a task from the task list in the right part of the window. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Modify the parameter settings. Parameters to be modified. Operation Common parameter Click the Common Parameter tab and then modify the parameter settings. For details, refer to 14.15.4 Parameters for Setting Common Information.
Issue 06 (2008-12-16)
14-43
Parameters to be modified. Operation Extended parameter 1. Select the tab which shows the measurement period of the performance measurement subset to be exported, for example, 5Minute. 2. An optional step: If you need to export the performance measurement data based on performance query template, click the Template tab and then choose one or more query templates. For a detailed description of the performance result query template, refer to 6.3.9 Managing Result Query Templates. 3. On the Function Subset tab page, select the function subset to be exported. You can select Show Measuring Function Subsets or Show All Function Subsets to set the navigation tree organization style. You can enter the conditions for filtering the search to locate the function subset. to add the selected function subset to 4. Click Selected Function Subsets list. You can also click to remove function subsets from the Selected Function Subsets list. 5. Set Export Period and Hold Days. For details, refer to 14.15.23 Parameters for Modifying the Export of Performance Data.
NOTE
If you export performance data by template, the M2000 enables you to export by period. That is, if the measurement period of an NE is 30 minutes, the measurement period set in the template is 60 minutes, then the M2000 summarized the performance data of 30-minute period and export them by 60-minute period. After you export performance data by template, the Export Period setting cannot be modified.
Result
Modified parameter values are displayed in the task list.
Related References
14.15.23 Parameters for Modifying the Export of Performance Data
14.6.2 Modifying the Export of Alarm Data

The M2000 provides the function of exporting alarm data. Before the alarm data is exported, you can modify common parameter and detailed parameter setting of the alarm data task.
14-44
Issue 06 (2008-12-16)
Prerequisite
l l
You have logged in to the M2000 client. The alarm data export task is exported.
Context
l
The task of exporting performance data is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, Period, File Format, Compact, Alarm Level, Type, Category, and Alarm Name.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select Task Type > File Interface > Alarm Data Export. Step 3 Select a task from the task list in the right part of the window. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.19 Parameters for Modifying the Export of Alarm Data. Step 6 Click OK. If the modification fails, a system output displays. ----End
Result
Related References
14.15.19 Parameters for Modifying the Export of Alarm Data
14.6.3 Modifying the Export of Configuration Data

M2000 provides the function of exporting configuration data. The M2000 supports two types of configuration data export tasks:NIC CMExportandConfiguration Data ExportNIC CMExport tasks provide data for the Nastar to query and check configuration data.Configuration Data Export tasks export the configuration data of specified NEs and back up such data. The exported and backed-up data is used to restore the NE configurations. The two types of configuration data export tasks are system timing tasks. You can modify the Common Parameters and Extended Parameters before exporting configuration data.
Prerequisite
l l
You have logged in to the M2000 client. The system has created configuration data export tasks.
Issue 06 (2008-12-16)
Context
l
The task of exporting configuration data is a system timing task and only supports the periodic execution. Only users in the Administrators user group can perform this operation.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Perform corresponding operations based on the task type. Task Type NIC CMExport Operation Choose Task Type > NIC > NIC CMExport in the navigation tree on the left pane of the window.
Configuration Data Export Choose Task Type > File Interface > Configuration Data Export in the navigation tree on the left pane of the window. Step 3 Select a task from the task list in the upper right pane of the window. Double-click the task or click Attribute . The Attribute dialog box is displayed. Step 4 Click the Common Parameters tab or the Extended Parameters tab to reconfigure the parameters. For details, see 14.15.4 Parameters for Setting Common Information and 14.15.20 Parameters for Modifying the Export of Configuration Data. Step 5 Click OK. ----End
Related References
14.15.20 Parameters for Modifying the Export of Configuration Data
14.6.4 Modifying the Export of Operation Log

The M2000 offers the function of exporting operation logs. Before carrying out a task of exporting operation logs, you can modify the public parameters and parameter settings of this task as required.
Prerequisite
l l
You have logged in to the M2000 client. The operation log is exported.
Context
l
The task of exporting operation logs is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation.
14-46

l
You can modify only the following parameters: Task Name, Start Time, Compress File After Export, File Format and Hold Days in the Database.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select Task Type > File Interface > Operation Log Export. Step 3 Select a task from the task list in the right part of the window. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.22 Parameters for Modifying the Export of Operation Log. Step 6 Click OK. If the parameter modification fails, a prompt is displayed. ----End
Result
After the modification, the new values are displayed in the task list.
Related References
14.15.22 Parameters for Modifying the Export of Operation Log
14.6.5 Modifying the Export of System Log

The M2000 offers the function of exporting system logs. Before carrying out a task of exporting system logs, you can modify the public parameters and parameter settings of this task as required.
Prerequisite
l l
You have logged in to the M2000 client. The system log is exported.
Context
l
The task of exporting system logs is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, Period, Whether to compress, and File Format.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Integrated Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > File Interface > System Log Export.
Step 3 On the right side of the window, select a task from the task list. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. Step 6 Click OK. If the parameter modification fails, a prompt is displayed. ----End
Result
14.6.6 Modifying the Export of Security Log

The M2000 offers the function of exporting security logs. Before carrying out a task of exporting security logs, you can modify the public parameters and parameter settings of this task as required.
Prerequisite
l l
You have logged in to the M2000 client. The operation log is exported.
Context
l
The task of exporting security logs is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, Period, Whether to compress, and File Format.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose Task Type > File Interface > Security Log Export. Step 3 On the right side of the window, select a task from the task list. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. Step 6 Click OK. If the parameter modification fails, a prompt is displayed. ----End
Result
14.6.7 Modifying the Export of NE Operation Log

The M2000 offers the function of exporting NE operation logs. Before carrying out a task of exporting NE operation logs, you can modify the public parameters and parameter settings of this task as required.
Prerequisite
l l
You have logged in to the M2000 client. The NE operation log is exported.
Context
l
The task of exporting NE operation logs is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, Period, and File Format. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select Task Type > File Interface > NE Operation Log Export. Step 3 On the right side of the window, select a task from the task list. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.21 Parameters for Modifying the Export of NE Log. Step 6 Click OK. If the parameter modification fails, a prompt is displayed. ----End
Result
Related References
14.15.21 Parameters for Modifying the Export of NE Log
14.6.8 Modifying the Export of NE Security Log

The M2000 offers the function of exporting NE security logs. Before carrying out a task of exporting NE security logs, you can modify the public parameters and parameter settings of this task as required.
Prerequisite
l l
You have logged in to the M2000 client. The NE security log is exported.
Context
l
The task of exporting NE security logs is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify only the following parameters: Task Name, Start Time, Period, and File Format. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select Task Type > File Interface > NE Security Log Export. Step 3 On the right side of the window, select a task from the task list. Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.21 Parameters for Modifying the Export of NE Log. Step 6 Click OK. If the parameter modification fails, a prompt is displayed. ----End
Result
Related References
14.6.9 Modifying the Export of Inventory Data

The M2000 provides the function of exporting inventory data. Before the inventory data is exported, you can modify common parameter and detailed parameter setting of the inventory data task.
Prerequisite
l l
Log in to the M2000 client successfully. The task of exporting performance data is already created.
14-50
Context
l
The task of exporting inventory data is a system-schedule task and only supports the periodic execution. Only users in the administrator user group can perform this operation. You can modify the following parameters: Task Name, Start Time, Period, File Path, and NE. IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
l l
Procedure
Step 1 Choose Maintenance > Task Management to view the Task Management window. Step 2 Select Task Type > File Interface > Inventory Data Export node in the navigation tree to the left. Step 3 Select a task from the task list in the right part of the window. Step 4 Double-click or click Attribute to view the Attribute dialog box. Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.24 Parameters for Modifying the Export of Inventory Data. Step 6 Click OK. ----End
Result
Related References
14.15.24 Parameters for Modifying the Export of Inventory Data
14.6.10 Modifying the Export of Basic NE Information

This describes the function of exporting basic NE information provided by the M2000. The exported information is used by the Nastar in performance analysis. Before exporting the basic NE information, you can modify the common parameters and extended parameters of a task.
Prerequisite
l l
You have logged in to the M2000 client. The system has created the task of exporting basic NE information.
Context
l
The task of exporting basic NE information is a system timing task and only supports periodic execution. Only users in the Administrators user group can perform this operation.
Issue 06 (2008-12-16)

l
The path of exporting basic NE information is /export/home/omc/var/fileint/network/ EAMInfo.xml.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > NIC > NE Basic Information Export in the navigation tree on the left pane of the window. Step 3 Select a task from the task list in the upper right pane of the window. Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Click the Common Parameters tab or the Extended Parameters tab to reconfigure the parameters.For details about Common Parameters, refer to 14.15.4 Parameters for Setting Common Information. In the Extended Parameters tab, you can set the export method and required NEs. The export method includes:
l
Export All NE The NE tree is unavailable and the M2000 exports the basic information of all NEs. Export By NE Type You need to select the NE type and the M2000 exports the basic information of such NE type.
Export By NE You need to select the NE and the M2000 exports the basic information of that NE.
14.7 Modifying Data Backup in the M2000

You can modify common parameters and detailed parameters of a data backup task in the M2000 system.
Context
l
The M2000 system data backup is a scheduled task. The task only supports the periodic run type. Only users in the administrator user group can perform this operation. For the backup of M2000 system data, you can modify the following parameters: Task Name, Start Time, and Server Full Backup Date.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Under the task navigation tree in the left pane, select Backup. Step 3 From the task list in the right pane, select the server backup task.
Step 4 Click Attribute. The Attribute dialog box is displayed. Step 5 Click the Common Parameters tab or the Extended Parameters tab and set the parameters.
l
To know how to set the Common Parameters, refer to 14.15.4 Parameters for Setting Common Information. To know how to set the Extended Parameters, refer to 14.15.25 Parameters for Modifying Data Backup in the M2000.
Result
You can query modified parameter values in the task list.
Related References
14.15.25 Parameters for Modifying Data Backup in the M2000
14.8 Modifying Alarm Timing Acknowledgement

This task describes how to modify parameters of an alarm timing acknowledgement task created by the M2000.
Prerequisite
l l
You have logged in to the M2000 client. The alarm timing acknowledgement task is created.
Context
NOTE
l l l
The task of alarm timing acknowledgement is a scheduled task of a system. The task supports only the periodic run type. Only users in the administrator user group can modify parameters of an alarm timing acknowledgement task. You can modify only the following parameters: Task Name, Start Time, Period, Alarm Level, and Alarm Status.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree in the left pane, select Task Type > Other > Alarm Acknowledgement. Step 3 From the task list in the right pane, select a created alarm scheduled acknowledgement task. Step 4 Double-click this task or click Attribute.
The Attribute dialog box is displayed. Step 5 Click the Common Parameters tab or the Extended Parameters tab and set parameters. To know how to set the parameters, refer to 14.15.17 Parameters for Modifying Alarm Timing Acknowledgement.
NOTE
The reset start time must be later than the current server time.
Step 6 Click OK or Apply. You can view the latest information about the task in the task list.
NOTE
If the task is running, the modified data takes effect when the task is restarted.
----End
Related References
14.15.17 Parameters for Modifying Alarm Timing Acknowledgement
14.9 Modifying NE License Sharing Management

NE license sharing management is used to check the license resources on the license sharing group and on the NEs in the group at a specific time every day. In this way, you can learn the situation of NE license sharing. This task is a system timing task and you can modify the start time to carry out the task.
Prerequisite
l l
You have logged in to the M2000 client. The NE license sharing management task has been created in the system.
Context
l
The NE license sharing management task is a system timing task and can be carried out periodically. Only the users in the Administrators user group can modify the NE license sharing management task. The system checks whether the network licenses allocated to NEs by the license sharing group outnumbers the actual available resource value. If the allocated network value outnumbers the available license resources, the system sends an alarm to the M2000 server, indicating that the number of used licenses exceeds the limit. Based on the alarm information, you can handle the problem. For details, see ALM-515 The amount of used license's resource exceeds the threshold. If the local license files on NEs are updated or out of date, the network license that are assigned to NEs by the license sharing group may exceed the actual available resource value.
When the NE license sharing mangement task is running, the system checks the following items:
l
The system checks whether the network license on NEs is consistent with the network license on the server. If they are inconsistent, the system sends an alarm to the M2000
14-54
server, indicating that the number of NE licenses changes. Based on the alarm information, you can handle the problem. For details, see ALM-514 Changes in the usage of NE license resources. When you adjust license resources between NEs in the license sharing group, the network licenses on NEs may differ from the network licenses that are actually allocated to the M2000 server because of NE disconnection.
l
The system checks whether an NE in the license sharing group is disconnected from the M2000 for over 15 days. If an NE is disconnected for over 15 days, the system automatically removes the NE from the group.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Other > NE Software Download in the left navigation tree. Step 3 Select an already created NE license sharing management task from the right task list. Step 4 Double-click or click Attribute to open the Attribute dialog box. Step 5 Reset the start time to carry out the task.
NOTE
Step 6 Click OK. You can browse the newest task information in the task list.
NOTE
----End
14.10 Managing Timing Tasks

You can view the status of user scheduled tasks and perform the operations such as suspend, delete, cancel, and undo these tasks. 14.10.1 Deleting Timing Tasks You can delete created tasks to save the system resources. 14.10.2 Suspending Timing Tasks To delay the time for scheduling a task, you can suspend an idle timing task. After a task is suspended, it is changed to the suspended state. 14.10.3 Resuming Timing Tasks You can restore a suspended task to wait for the dispatching. Then the status of the task is changed to idle. 14.10.4 Cancelling Timing Tasks You can cancel a running task. The task status is changed to idle after being cancelled. 14.10.5 Setting Time of Timing Tasks You can set an automatic suspend time or an automatic restore time for a scheduled task. In this situation, the M2000 automatically suspends the task or restores the task.
14.10.6 Browsing CME Subtask When you create an CME tasks, the system automatically creates multiple subtasks by NE. You can browse a CME subtask to view the main task name, the creator, the completion progress, and the result of the subtask. 14.10.7 Setting Period of CME Subtask By setting a period of a CME subtask, you can better control execution time of each subtask in the period. 14.10.8 Terminating Descendant Tasks You can terminate CME downloading sub-tasks. 14.10.9 Rolling Back Descendant Tasks You can roll back the activated CME download subtasks.
14.10.1 Deleting Timing Tasks

You can delete created tasks to save the system resources.
Prerequisite
l l
You have logged in to the M2000 client. At least one timing task exists.
Context
l
Each user can delete only the tasks that are created by him. A user in the Administrators group can delete all the user timing tasks created by any user. System tasks cannot be deleted. Running tasks cannot be deleted. You can delete only an Archived CME download task.
l l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. Step 3 Select one or more scheduled tasks in the task list in the right pane. Step 4 Click Delete. The Confirm dialog box is displayed. Step 5 Click Yes. ----End
Result
Then the task is deleted from the task list.
14.10.2 Suspending Timing Tasks

To delay the time for scheduling a task, you can suspend an idle timing task. After a task is suspended, it is changed to the suspended state.
Prerequisite
l l
You have logged in to the M2000 client. At least one idle timing task exists.
Context
The system uses the tasks that are not suspended.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. Step 3 Select one or more tasks in the task list in the right pane. Step 4 Right-click the task and select Suspend from the shortcut menu. Step 5 Click Yes in the displayed Confirm dialog box. Then the status of the task is changed from idle to suspended. ----End
14.10.3 Resuming Timing Tasks

You can restore a suspended task to wait for the dispatching. Then the status of the task is changed to idle.
Prerequisite
l l
You have logged in to the M2000 client. At least one suspended scheduled task exists.
Context
Only idle tasks can wait to be used.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. Step 3 Select one or more tasks in the task list in the right pane. Step 4 Right-click the task and select Restore from the shortcut menu. Step 5 Click Yes in the displayed Confirm dialog box. Then the status of the task is changed from suspended to idle. ----End
14.10.4 Cancelling Timing Tasks

You can cancel a running task. The task status is changed to idle after being cancelled.
Prerequisite
l l
You have logged in to the M2000 client. At least one Running timing task exists.
Context
A user in the common user group can cancel only the tasks created by himself. A user in the Administrators group can cancel all the user timing tasks created by any user.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. Step 3 Select one or more running tasks in the task list in the right pane. Step 4 Right-click the task and select Cancel from the shortcut menu. Step 5 Click Yes in the displayed Confirm dialog box. Then the status of the task is changed from running to idle. ----End
14.10.5 Setting Time of Timing Tasks

You can set an automatic suspend time or an automatic restore time for a scheduled task. In this situation, the M2000 automatically suspends the task or restores the task.
Prerequisite
l l
You have logged in to the M2000 client. At least one suspended or idle timing task exists.
Context
l
The system suspends an idle task and delay the time for using this task. If the timing task is not in the Idle state at the specified time, it fails to be suspended. In the specified time, the system resume a suspended task and then the task is in the idle status and wait to be dispatched. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You are not allowed to set auto-suspend or resume a Running timing task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to suspend. Step 3 From the task list in the right part of the window, select a timing task to be suspended. Step 4 Right-click the task and choose Timing Suspend/Resume.
Step 5 In the displayed Timing Suspend/Resume dialog box, select Suspend Time or Resume Time as required. Step 6 Set the suspend time or resume time. For details of setting an automatic suspend time or an automatic restore time, refer to 14.15.26 Parameters for Setting Time of Timing Tasks. ----End
Related References
14.15.26 Parameters for Setting Time of Timing Tasks
14.10.6 Browsing CME Subtask

When you create an CME tasks, the system automatically creates multiple subtasks by NE. You can browse a CME subtask to view the main task name, the creator, the completion progress, and the result of the subtask.
Prerequisite
l l
You have logged in to the M2000 client. At least one CME subtask exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > CME > CME Download in the navigation tree. Step 3 Select a task from the task list in the right part of the window. Step 4 Right-click the task and choose Subtask. The Subtask Browsing dialog box is displayed. For details about the parameter meaning of the subtask browsing, refer to 14.15.27 Parameters for Browsing CME Subtask. ----End
Related References
14.15.27 Parameters for Browsing CME Subtask
14.10.7 Setting Period of CME Subtask

By setting a period of a CME subtask, you can better control execution time of each subtask in the period.
Prerequisite
l l
You have logged in to the M2000 client. At least one CME download subtask is not scheduled.
Context
The operation is performed only for the CME download task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > CME > CME Download in the navigation tree. Step 3 Select a task from the task list in the right part of the window. Step 4 Right-click the task and choose Subtask. Step 5 Select a subtask in the displayed Subtask dialog box. Step 6 Right-click the subtask and choose Phase Time or click the Phase Time button. The Phase Time Setting dialog box is displayed. For details about the setting of a period, refer to 14.15.28 Parameters for Setting Period of CME Subtask. Step 7 Click OK. ----End
Related References
14.15.28 Parameters for Setting Period of CME Subtask
14.10.8 Terminating Descendant Tasks

You can terminate CME downloading sub-tasks.
Prerequisite
l l
You have logged in to the M2000 client. At least one Running CME download subtask exists.
Context
Only CME download subtasks can be terminated.
CAUTION
The determination of sub-tasks cannot be restored. Once a sub-task is terminated, it cannot be dispatched and all the related operations such suspending and recovering are inapplicable. Be cautious when performing this operation.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, choose CME > CME Download. Step 3 Select one or more tasks in the task list in the right pane. Step 4 Right-click the task and select Terminate from the shortcut menu.
Step 5 Click Yes in the displayed Confirm dialog box. ----End
14.10.9 Rolling Back Descendant Tasks

You can roll back the activated CME download subtasks.
Prerequisite
l l
You have logged in to the M2000 client. An activated CME download subtask exists. The configuration data takes effect on the NE.
Context
Only the CME download subtasks support the fallback function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. Step 3 In the task list, select one or multiple activated CME subtasks. Step 4 Right-click and then select Resume in the displayed shortcut menu. Step 5 In the displayed Confirmation dialog box, click Yes. ----End
14.11 Browsing the Information of Timing Tasks

The M2000 offers the integrated task browsing function, which allows the authorized users to browse tasks.
Prerequisite
l l
Context
l
Common users, that is, the users not belonging to the administrator group, are allowed to browse all user tasks rather than system tasks. Users in the administrator group are allowed to browse all tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree.
l
In the task list, all the tasks are displayed.

Issue 06 (2008-12-16)

l
If you want to view the common parameters and extended parameters of each task, go to Step 3
Step 3 Double click a task, or select a task and click Attribute. The Attribute dialog box is displayed. In the Common Parameter and Extended Parameter tab pages, you can view the task details. ----End
14.12 Checking the Task Progress

You can view the progress of all the sub-tasks of a specific task or a CME task.
Prerequisite
l l
Context
l
During the creation of CME tasks, sub-tasks are created, which are executed in different phases. You can browse the execution progress of subtasks of CME tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to check the progress.
l l
View the task progress in the Progress column at the right. To check the progress of the CME subtask, select the task in the list and view the progress in the Progress column.
----End
14.13 Checking the Task Execution

You can view the last execution results of a timing task
Prerequisite
l l
Context
l
During the creation of CME tasks, sub-tasks are created, which are executed in different phases. You can browse the execution progress of subtasks of CME tasks.
14-62
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree.
l
View the execution conditions in the Prev Execution Result column in the task list in the right pane. You can check the result details in the Result Info area.
----End
14.14 Downloading Result Files

This describes how to download the results of timing tasks. You can save the results of timing tasks on the server to the local client in .txt format.
Prerequisite
l l
You have logged in to the M2000 client. The timing task that is used for downloading the result files exists and it is run for at least once.
Context
The allowable operations vary depending on the task type, as shown in Table 14-7. Table 14-7 Allowable operations for different task types Task Type CME and HSL script tasks Allowable Operation The task result are saved on the server in logs. The Result Info area displays only the information about the last task execution. The result logs are not displayed. You can download all the result files to the local client. Result files of multiple tasks can be downloaded concurrently. MML script task Network health check task Dual Home Management tasks Timing task, NE Software Download task, and NE Backup task You can download the latest result file to the local client. Result files of multiple tasks can be downloaded concurrently. You can download the result file of the selected task. Result files of multiple tasks can be downloaded concurrently. You can view the latest consistency check result on line. If a task is performed at least once, you can save the messages in the Result Info area to a local path.
Issue 06 (2008-12-16)
14-63
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the type of the task that is used to download the result files. Select the specific tasks in the right pane. Step 3 Perform the following operations according to the task type. Task Type CME or HSL script task Procedure To download the result logs of a download task, perform the following steps: 1. Select the task whose result logs you plan to download. 2. Click Save Log. In the displayed Please select a directory dialog box, set the save path 3. Click OK.
NOTE The system generates a folder for the log file generated each time and saves the folder to the specified path. The result log file is named in the format YYYY-MMDD_HH-MM-SS, for example, 2008-04-18_10-27-53.
MML script task
To download the result files of a single task, do as follows: 1. Select the MML script task whose result files you plan to download. 2. Right-click a task and choose Save MML Result on the shortcut menu. Alternatively, you can right-click the Result Info field and choose Save AS on the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save. To download the result files of multiple tasks, do as follows: 1. Press Ctrl or Shift to select multiple MML script tasks in the task list. 2. Right-click the tasks and choose Save MML Result on the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save. Save the execution results of multiple MML script tasks to the same file.
14-64
Issue 06 (2008-12-16)
Task Type Network health check task
Procedure 1. Select the task whose result files you plan to download. 2. Right-click a task and choose NHC Report on the shortcut menu. 3. In the displayed NHC Report dialog box, select the check report based on Report Nameand then click Save.
NOTE You can click Open to view the contents of the check report and decide whether the report needs to be downloaded.
4. Set the save path in the displayed Please select a directory dialog box. 5. Click OK. Dual Home Management tasks Right-click a task and choose Checked Result from the shortcut menu.
NOTE If data inconsistency exists, you need to generate a script to adjust the data difference and synchronize the data. For details, refer to 11.2.5 Generating the Script for Adjusting Difference Data and 11.2.7 Synchronizing the Dual-Homing Data.
Timing task, NE Software Download task, and NE Backup task
To download the result information about a download task, perform the following steps: 1. Select a task whose result information needs to be downloaded. 2. Right-click in the Result Info area can choose Save As from the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save.
----End
14.15 Reference for Integrated Task Management Interfaces

This part describes the integrated task management interfaces and related information such as the parameters used in the integrated task management. This helps you understand the functions of integrated task management. 14.15.1 Interface Description: Managing Timing Tasks This part describes the Task Management interface and relevant parameters, which helps you perform the related operations. 14.15.2 Parameters for Setting Filtering Conditions
This part describes the parameters in the Task Filter Setting dialog box. Set filtering conditions for task list. 14.15.3 Parameters for Creating/Copying Common Information This part describes the parameters in the New Task dialog box. Set the parameters by referring to the information listed below. 14.15.4 Parameters for Setting Common Information This describes the parameters listed in the Common Parameters tab of all the timing task attribute except that of the CME download task. When modifying periodic tasks, set parameters in this tab by referring to the information described below. 14.15.5 Parameters for Setting Common Information for CME Download Tasks This part describes parameters in the Common Parameters of Attribute dialog box. When viewing information of CME download tasks, refer to the information described below. 14.15.6 Parameters for Creating/Copying Time Settings for Scheduled Tasks This part describes the parameters in the time panel of the New Task dialog box for periodic tasks. Set the parameters in the time panel for periodic tasks by referring to the information described below. 14.15.7 Parameters for Creating/Copying Time Settings for One-Off Tasks This part describes the parameters in the time panel of the New Task dialog box for oneoff tasks. Set the parameters in the time panel for oneoff tasks by referring to the information described below. 14.15.8 Parameters for Creating/Modifying/Copying MML Command Script This part describes the parameters in the MML command script. When creating or modifying MML command script, set the parameters by referring to the information described below. 14.15.9 Parameters for Creating/Modifying Software Download This part describes the parameters in the software download task. When creating or modifying software download task, set the parameters for software download task by referring the information described below. 14.15.10 Parameters for Creating/Modifying/Copying NE Backup This describes the parameters related to NE backup tasks. You can refer to this part when creating or modifying NE backup tasks. 14.15.11 Parameters for Creating/Modifying/Copying CME Upload This part describes the parameters in the CME upload task. When creating or modifying tasks, set the parameters in the CME upload task by referring to the information described below. 14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data This part describes parameters used for synchronization of NE configuration data. When modifying the parameters, set the parameters by referring to the information described below. 14.15.13 Parameters for Modifying the Synchronization of Inventory Data This part describes parameters used for synchronization of inventory data. When modifying the parameters, set the parameters by referring to the information described below. 14.15.14 Parameters for Creating/Modifying CME Download This part describes the parameters in the CME download task. When creating or modifying CME download task, set the parameters in the CME download task by referring to the information described below. 14.15.15 Parameters for Creating/Modifying/Copying HSL Script This part describes the parameters in the HSL script task. When creating or modifying HSL scripts, set the parameters in the HSL tasks by referring to the information described below.
14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management This describes the parameters used in dual-homing management. You can refer to these parameters when creating, modifying, or copying dual-home management. 14.15.17 Parameters for Modifying Alarm Timing Acknowledgement This part describes the parameters in the alarm acknowledgement. When modifying alarm acknowledgement, set the parameters in the alarm acknowledgement by referring to the information described below. 14.15.18 Parameters for Modifying Database Capacity This part describes the parameters in database capacity management. When modifying the database capacity management, set the parameters in the database capacity management by referring to the information described below. 14.15.19 Parameters for Modifying the Export of Alarm Data This part gives the descriptions of parameters for exporting alarm data, which can be your reference during the parameter modification. 14.15.20 Parameters for Modifying the Export of Configuration Data This describes the parameters of two task types: NIC CMExport and Configuration Data Export. You can refer to this part when modifying relevant parameters. 14.15.21 Parameters for Modifying the Export of NE Log This part gives the descriptions of parameters for exporting NE logs, which can be your reference during the parameter modification. 14.15.22 Parameters for Modifying the Export of Operation Log This part gives the descriptions of parameters for exporting operation logs, which can be your reference during the parameter modification. 14.15.23 Parameters for Modifying the Export of Performance Data This part gives the descriptions of parameters for exporting performance data, which can be your reference during the parameter modification. parameter 14.15.24 Parameters for Modifying the Export of Inventory Data This part gives the descriptions of parameters for exporting inventory data, which can be your reference during the parameter modification. 14.15.25 Parameters for Modifying Data Backup in the M2000 This part gives the descriptions of data backup parameters, which can be your reference during the parameter modification. 14.15.26 Parameters for Setting Time of Timing Tasks This gives the descriptions of parameters of time for automatic suspending and automatic resuming timing tasks 14.15.27 Parameters for Browsing CME Subtask This part describes the parameters of CME subtasks. 14.15.28 Parameters for Setting Period of CME Subtask This part gives the descriptions of parameters for setting the execution time of each period of CME subtasks. parameter
14.15.1 Interface Description: Managing Timing Tasks

This part describes the Task Management interface and relevant parameters, which helps you perform the related operations.
Issue 06 (2008-12-16)
14-67
After you log in to the server, the Timing Task Management interface is displayed, as shown in Figure 14-2. Table 14-8 describes each element displayed in Figure 14-2. Figure 14-2 Timing Task Management interface
Table 14-8 Description of the Timing Task Management interface No. (1) (2) Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out central task management are available on the button panel. You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors are used for indicate different states of tasks: Gray: complete Orange: suspended Blue: active White: idle The selected color of the task is darker than the previous color of the task.
Issue 06 (2008-12-16)
(3)
Button panel
(4)
Task list
14-68
14.15.2 Parameters for Setting Filtering Conditions

This part describes the parameters in the Task Filter Setting dialog box. Set filtering conditions for task list.
Parameter User Name Catego ry Current User Other Users User Task System Task Idle Running Suspend Finished Archived Description Indicates the user that operates the client. Indicates other users except the current user. Indicates the task created by users. Indicates the task created by OMC during the system installation or upgrade. Indicates that the task waits for being performed by the system. Indicates that the task is being performed by the system. The task is not ready to be scheduled. Indicates that the task is completed by the system. The archived state is supported only by the CME download task. After the CME download task is stopped, the task is archived. Only when the task is in the archived state, the task can be deleted. Indicates that the task is successfully carried out. Indicates that the task is being processed by the system. Indicates that the task is partly successfully carried out. Indicates that the task fails to carry out. Indicates that the task misses the previous performed time. If the server is not running properly or the task is suspended before the execution, the task may miss the previous execution. Indicates that the previous execution result in the server is lost caused by improper service or sudden power cut. Thus, after recovery, the previous execution result cannot be determined.
State
Last Run Result
Success Processing Partly Success Failed Miss Run Time Unknown
Related Tasks
14.1.6 Customizing the Interface for Managing Timing Tasks
14.15.3 Parameters for Creating/Copying Common Information

This part describes the parameters in the New Task dialog box. Set the parameters by referring to the information listed below.
Issue 06 (2008-12-16)
14-69
l
Description Refers to the name of a timing task
This parameter allows a maximum of 60 characters. You can enter only English letters, numbers, - and underlines. This parameter is exclusive and cannot be empty. These characters are case sensitive.
Task Type
Select from Task Type.
Select a task that you require, such as NE Backup. Select this check box and the system runs the tasks that you create only once at some time. Select this check box and the system runs the tasks that you create on a regular basis.
Run Type
Once
None.
Period
None.
14.15.4 Parameters for Setting Common Information

This describes the parameters listed in the Common Parameters tab of all the timing task attribute except that of the CME download task. When modifying periodic tasks, set parameters in this tab by referring to the information described below.
l l
Description Refers to the name of a timing task
A maximum of 60 characters Allowed characters: English letters, numbers, -, and _ Unique and not null Case sensitive
l l
Run Type
One-time task
None
If you select this option, the system runs the created task once at the defined time point. If you select this option, the system runs the created task periodically.
Periodic task
None
14-70
Issue 06 (2008-12-16)
Value Range None
Description This parameter sets the time for starting a task. The start time should be later than the time displayed on the server. If you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete.
Period
Tasks can be executed in minutes, hours, and days. The valid values for periods are as follows: Day (1 to 366), Hour (1 to 366 x 24), Minute (1 to 366 x 24 x 60)
Interval between periodic tasks. It has two enlistment: unit and duration.
Run Times
0-65535
This parameter indicates the times that a periodic task is executed.
14.15.5 Parameters for Setting Common Information for CME Download Tasks
This part describes parameters in the Common Parameters of Attribute dialog box. When viewing information of CME download tasks, refer to the information described below.
Parameter Task Name Description Indicates the name of a task. The Task Name cannot be modified in this dialog box.
Related Tasks
14.2.5 Creating CME Download 14.3.5 Modifying CME Download
14.15.6 Parameters for Creating/Copying Time Settings for Scheduled Tasks

This part describes the parameters in the time panel of the New Task dialog box for periodic tasks. Set the parameters in the time panel for periodic tasks by referring to the information described below.
Parameter Time Setting Start Time Value Range None. Description You can either enter the time value in this field, or click to select the date and time in the Date/ Time Selection dialog box. Period Setting Period
l
The period can be represented in either of the following units: months, weeks, days, hours, minutes. The period, however, cannot be represented in seconds. The value range for period should be as follows: Month (1 - 12), Week (1 - 52), Day (1 366), Hour (1 - 366 x 24), Minute (1- 366 x 24 x 60).
This parameter gives the interval for a task to be executed again. This parameter not only gives the period but the units for period.
Run Times
0 - 65535
This parameter indicates the times that a periodic task is executed.
14.15.7 Parameters for Creating/Copying Time Settings for One-Off Tasks

This part describes the parameters in the time panel of the New Task dialog box for oneoff tasks. Set the parameters in the time panel for oneoff tasks by referring to the information described below.
Parameter Time Setting Start Time Description You can either enter the time value in this field, or click to select the date and time in the Date/Time Selection dialog box. If the Run Immediately check box is selected, the task is performed immediately after you set the parameters.
14-72
Issue 06 (2008-12-16)

This part describes the parameters in the MML command script. When creating or modifying MML command script, set the parameters by referring to the information described below.
Parameter Script file Value Range The script file is in .txt format. The maximum size is 1 MB. None. Description The script file is a text file recording MML commands for one NE or multiple NEs of the same type. Enter the path for MML script file in this field or click script file in the Open dialog box. to select MML
Redirect result
If the created task is a one-time task, you can select Redirect Result and set the path of Redirect File to add the task result to the specified redirection file. You can create a non-existent file. If the redirection file exists, the new messages does not overwrite the original messages. If you set the result redirection of a task, the path of Redirect File cannot be changed after the task is completely created.
Select NE
None.
After you select this option, you can change the NE of the script command by selecting the NE in the NE tree instead of modifying the script file. After the NE is reelected, the original NE information is invalid and all commands are sent to all the newly selected NEs. The NE tree displays all the NEs in a physical topology tree. The function buttons for selecting NEs are as follows:
l l l
: to expand the NE tree. : to expand the NE tree. : to use the Single Select mode. That is, if you select a node, the subnodes are not selected. You can click this button to switch to the Recursive Select mode. : to use the Recursive Select mode. That is, if you select a node, the subnodes are also selected. You can click this button to switch to the Single Select mode.
NOTE When creating MML scripts, you must select Select Ne to choose NE objects if some command lines in the script file are lack of object information.
Issue 06 (2008-12-16)
14-73
Parameter Run Mode
Value Range Collateral or Serial.
Description Two modes for issuing MML commands are available:

l
Collateral: indicates that the MML commands are issued to the NE concurrently. Serial: indicates that the MML commands are issued to the NE in sequence.
Related Tasks
14.2.1 Creating MML Command Script 14.3.1 Modifying MML Command Script

This part describes the parameters in the software download task. When creating or modifying software download task, set the parameters for software download task by referring the information described below.
Parameter NE Type Edition List Value Range Select the value from the drop-down list. None. Description Indicates all of the NE types available in the current network. Indicates the editions of all NEs that can be downloaded from the server. These NEs are of the same type. Multiple choices are not allowed. Indicates all of the NEs of an NE type available in the current network. Multiple choices are supported.
NE List
None.
Related Tasks
14.2.2 Creating Software Download 14.3.2 Modifying Software Download

This describes the parameters related to NE backup tasks. You can refer to this part when creating or modifying NE backup tasks.
Parameter File Path Description Refers to the path to save NE data backup files. It is specified by the system.
14-74
Issue 06 (2008-12-16)
Parameter Backup All NE By NE Type By NE
Description If you select this parameter, the system backs up the data of all NEs available in the current network. By default, the system backs up the data of all NEs in the entire network. If this option is selected, you should specify the NE type in the NE Type navigation tree. If this option is selected, you should specify the NE in the NE navigation tree.
Related Tasks
14.2.3 Creating NE Backup 14.3.3 Modifying NE Backup

This part describes the parameters in the CME upload task. When creating or modifying tasks, set the parameters in the CME upload task by referring to the information described below.
Parameter All NE NE Description Select this check box and the system uploads the configuration data of all RNCs and NodeBs in the current network. Indicates the specified NEs of RNC or NodeB in the current network. Multiple choices are supported.
Related Tasks
14.2.4 Creating CME Upload 14.3.4 Modifying CME Upload
14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data

This part describes parameters used for synchronization of NE configuration data. When modifying the parameters, set the parameters by referring to the information described below.
Parameter description
Parameter All NE Configuration Data Please Select NE
Issue 06 (2008-12-16)
Description If All NE Configuration Data is selected, the system synchronizes the configuration data of all existing NEs in the network. Select existing NEs in the entire network. Multiple NEs are supported.
14-75
Related Tasks
14.4.2 Modifying the Synchronization of NE Configuration Data
14.15.13 Parameters for Modifying the Synchronization of Inventory Data

This part describes parameters used for synchronization of inventory data. When modifying the parameters, set the parameters by referring to the information described below.
Parameter All NE Please Select NE Description If you select this option, the system synchronizes the inventory data of all NEs on the network. Indicates all the NEs in the entire network. Multiple NEs are supported. You can select the specific NEs in Please Select NE only after you seselect All NE.
Related Tasks
14.4.4 Modifying the Synchronization of Inventory Data
14.15.14 Parameters for Creating/Modifying CME Download

This part describes the parameters in the CME download task. When creating or modifying CME download task, set the parameters in the CME download task by referring to the information described below.
Parameter Check interval Pre-activation interval Activation interval Retry after a failure Partial retry Value Range 0-65535 0-65535 0-65535 None. Description Time interval for checking the validity of delivered commands. Time interval for pre-activating configuration commands on NEs. Time interval for executing the delivered bulk commands on NEs. If a task is not performed successfully, the system performs this task again after you select this item. If a task is not performed successfully, the system performs the unsuccessful part of this task again after you select this item. Times of retrying tasks. Interval for retrying a task.
Issue 06 (2008-12-16)
None.
Retry times Retry interval

14-76
1-65535 0-65535
Parameter Stop upon an error
Value Range None.
Description In case the system incurs an error when executing a task, the system stops the task if you select this item. By default, the system selects Stop upon an error. In case the system incurs an error when executing a task, the system ignores the error and continue the task if you select this item. Upload a command file from a local client to the M2000 server.
Best effort
None.
Upload files
The upload file is in .xml format. The upload file cannot be empty.
Related Tasks
14.2.5 Creating CME Download 14.3.5 Modifying CME Download

This part describes the parameters in the HSL script task. When creating or modifying HSL scripts, set the parameters in the HSL tasks by referring to the information described below.
Parameter Main File Value Range The main file is in .hsl format. The main file has a maximum size of 1 MB. The assistant file has a maximum size of 1 MB. None. Description The main file is the entry file for the execution of script files.
Assistant File
When the script files are being executed, the main file selects from assistant files if the main file need to invoke other script files. You need to select NEs when script files contain operations on several NEs. Multiple choices are supported.
NE Selection
Related Tasks
14.2.6 Creating HSL Script 14.3.6 Modifying HSL Script

This describes the parameters used in dual-homing management. You can refer to these parameters when creating, modifying, or copying dual-home management.
Parameter Dual Homing Pairs Description Indicates the dual-homing pairs. For detailed information about dual homing, refer to 11 Dual-Homing and LN Domain Management. Indicates the data resource type of the dual homing pairs to be checked. Data resource types vary depending on the version of dual-homing pair NE. Setting Select from the drop-down list.
Resource Type
Select the item in the Resource Type navigation tree. Enter the data resource type or key word in the Search box. Then the related resource types are listed under the Search box. You can doubleclick resource type to be checked.
Search
Use to search for the type of the data resource to be checked. The search conditions support case insensitive fuzzy search. Wildcard search is not supported.
Enter the data resource type of key word in the Search box.
Related Tasks
14.2.7 Creating Dual-Home Management 14.3.7 Modifying Dual-Home Management
14.15.17 Parameters for Modifying Alarm Timing Acknowledgement

This part describes the parameters in the alarm acknowledgement. When modifying alarm acknowledgement, set the parameters in the alarm acknowledgement by referring to the information described below.
Parameter Alarm Level Value Range
l l l l
Description Indicates the level of alarms. Multiple choices are supported.
14-78
Issue 06 (2008-12-16)
Parameter Alarm State
Value Range
l
Description Indicates the alarm states. Multiple choices are supported.
Unacknowledge and unclear Fault Unacknowledge and clear Fault
Related Tasks
14.8 Modifying Alarm Timing Acknowledgement
14.15.18 Parameters for Modifying Database Capacity

This part describes the parameters in database capacity management. When modifying the database capacity management, set the parameters in the database capacity management by referring to the information described below.
Parameter Compress File After Export Value Range Select the value from the drop-down list. Description When the data in the database expires, the system can choose to compress files during export. You can select either Yes or No in this field. The system selects Yes by default. The format of the file that saves the exported data. File formats vary with tasks as follows:
l
File Format
Select the value from the drop-down list.
The data files for performance database capacity management are in .csv format. The data files for NE operation and security log database capacity management are in .txt or .csv format. The data files in database capacity management for alarms, operation logs, system logs, and security logs are in .xml or .csv format.
Issue 06 (2008-12-16)
14-79
Parameter Exported file format
Value Range None
Description Indicates the path for saving exported data. The save file path is specified by the server and cannot be modified by users. The default export path for each database capacity management task is as follows:
l
Log database capacity management tasks: / export/home/omc/var/ThresholdExport/ Log. Alarm database capacity management tasks: /export/home/omc/var/ ThresholdExport/FM. Performance database capacity management tasks: /export/home/omc/ var/ThresholdExport/PM/.
Hold Days in the Database
1 to 90
It refers to the days when data is saved in the database. The value of Hold Days is 30 by default.
Related Tasks
14.5 Modifying Database Capacity
14.15.19 Parameters for Modifying the Export of Alarm Data

This part gives the descriptions of parameters for exporting alarm data, which can be your reference during the parameter modification. Table 14-9 lists the extended parameters. Table 14-9 Descriptions of extended parameters Parameter File Type Value Range You can choose:
l l
Description Exports to a .csv file or .xml file.
CSV XML
l
Compress Exported File
You can select and deselect.
Select the parameter to compress the .csv files or .xml files to a packet and export. Deselect the parameter to export to a .csv file or .xml file.
Export Path
Default value. No change. The default path is: /export/ home/omc/var/fileint/fm/.
Indicates the save path of the exported alarm data.
14-80
Issue 06 (2008-12-16)
Parameter Alarm Level,Category,Type
Value Range Options in the drop-down list.

l
Description Select the severity level, type, and category of the alarm.
Alarm severity levels are: Critical, Major, Minor, and Warning. Alarm types are: current alarm, event alarm, history alarm, and shielded alarm. Alarm categories are: Power System, Environment System, Signaling System, Trunk System, Hardware System, Software System, Running System, Communication System, QoS, Processing Error, and Internal.
Alarm Name
Options in the drop-down list.
Lists the alarms whose data can be exported currently.
Related Tasks
14.6.2 Modifying the Export of Alarm Data
14.15.20 Parameters for Modifying the Export of Configuration Data

This describes the parameters of two task types: NIC CMExport and Configuration Data Export. You can refer to this part when modifying relevant parameters. Table 14-10 lists the extension parameters of NIC CMExport tasks. Table 14-10 Extension parameters of NIC CMExport tasks Parameter Export Path Value Range Default value. No change. The default path is: /export/home/ omc/var/fileint/ cm/GExport. File Save Time Default value. No change. The default value is 3 days. Refers to the duration to save the exported configuration data files on the M2000. Description Refers to the path to save the exported configuration data files on the M2000.
Issue 06 (2008-12-16)
14-81
Parameter File Need Compressed
Value Range Default value. No change. The default value is Yes.
Description Refers to whether to compress the exported configuration files.
Export NEs
You can select required NEs in the NE tree.
Export All NE The M2000 exports the configuration data of all NEs. Export By NE Type You need to select the NE type and the M2000 exports the configuration data of such NE type. Export By NE You need to select the required NE and the M2000 exports the configuration data of the NE.
Table 14-11 lists the extension parameters of Configuration Data Export tasks. Table 14-11 Extension parameters of Configuration Data Export tasks Parameter File Format Value Range Two formats are available, that is, .xml and .csv. You can select from the dropdown list. Default value. No change. The default path is: /export/home/ omc/var/fileint/ cm/autoExport. Please Select NE You can select the required NEs in Physical Topology Tree. If All NE Configuration Data is selected, the Physical Topology Tree becomes unavailable. Then the M2000 exports the configuration data of all NEs.
l l l
Description Refers to the format in which the exported data files are saved.
File Path
Refers to the path to save the exported configuration data.
Click Click
to expand all the sub nodes. to collapse all the sub nodes.
refers to cascading select. That is, by selecting a parent node, all the subnodes under it are selected.
14-82
Issue 06 (2008-12-16)
Related Tasks
14.6.3 Modifying the Export of Configuration Data

This part gives the descriptions of parameters for exporting NE logs, which can be your reference during the parameter modification. Table 14-12 lists the extended parameters. Table 14-12 Descriptions of extended parameters Parameter File Path Value Range Default value. No change. The default path is: /export/ home/omc/var/fileint/nelogs/. File Format You can choose TXT or CSV format. Description Indicates the path to save the NE logs.
Exports the operation logs to a .txt file or .csv file.
Related Tasks
14.6.7 Modifying the Export of NE Operation Log 14.6.8 Modifying the Export of NE Security Log
14.15.22 Parameters for Modifying the Export of Operation Log

This part gives the descriptions of parameters for exporting operation logs, which can be your reference during the parameter modification. Table 14-13 lists the extended parameters. Table 14-13 Descriptions of extended parameters Parameter Compress Exported File Value Range
l l
Description
l
Yes. No.
If you select Yes, the .csv files or .xml files are compressed to a packet and exported. If you select No, the .csv files or .xml files are directly exported.
Exported File Format
You can choose:

l l
CSV XML
Exports operation logs to a .csv file or .xml file.
Issue 06 (2008-12-16)
14-83
Parameter Save File Path
Value Range Default value. No change. The default path is:/export/ home/omc/var/fileint/ ***logs/, where *** stands for the log type.
Description The path to save the exported operation logs.
Related Tasks
14.6.4 Modifying the Export of Operation Log
14.15.23 Parameters for Modifying the Export of Performance Data

This part gives the descriptions of parameters for exporting performance data, which can be your reference during the parameter modification. parameter Table 14-14 lists the extended parameters. Table 14-14 Descriptions of extended parameters Parameter File Format Value Range You can choose:
l l l
Description Exports to a .csv or .xml file.
CSV. XML. TXT. The data is deleted from the server after the setting days. -
Hold Days
Enter as required. The default value is 90.
File Path
Default value. No change. The default path is /export/ home/omc/var/fileint/pm/.
Filter search
None
Search by name of function subset. The query condition supports a non-case-sensitive fuzzy search. The query condition does not support wildcard. Set the measure period of the exported task. Set the execution period of the exported task. The value is determined by the NE type.
NOTE The export period of performance data must be consistent with the measure period of performance data.
Measurement Period Export Period
You can click different measurement period tabs. Options in the drop-down list.
14-84
Issue 06 (2008-12-16)
Parameter Delay Time
Value Range The value must be multiples of 5 minutes. Value range: 5-1440. The unit is minute.
Description The parameter stands for the delay time of running the task.
Related Tasks
14.6.1 Modifying the Export of Performance Data
14.15.24 Parameters for Modifying the Export of Inventory Data

This part gives the descriptions of parameters for exporting inventory data, which can be your reference during the parameter modification.
Parameter File Path Description Indicates the path to save the exported inventory data. Default value: /export/home/omc/var/fileint/cm/InvtTimerExport. All NE Please Select NE If you select this option, the system exports the inventory data of all NEs on the network. This option is selected by default. Indicates all the NEs in the entire network. Multiple NEs are supported. You can select the specific NEs in Please Select NE only after you deselect All NE.
Related Tasks
14.6.9 Modifying the Export of Inventory Data
14.15.25 Parameters for Modifying Data Backup in the M2000

This part gives the descriptions of data backup parameters, which can be your reference during the parameter modification. Table 14-15 lists the extended parameters. Table 14-15 Descriptions of extended parameters Parameter Server Full Backup Date File Path Value Range Form Monday to Sunday Description The full backup is executed each week. If you set to Monday, the full backup is performed each Monday. The path to save the backup M2000 system data.
Default value. No change. The default path is:/export/ home/backup/omc.
Issue 06 (2008-12-16)
14-85
Related Tasks
14.7 Modifying Data Backup in the M2000
14.15.26 Parameters for Setting Time of Timing Tasks

This gives the descriptions of parameters of time for automatic suspending and automatic resuming timing tasks Table 14-16 lists the parameters of auto-suspend time and auto-resume time for timing tasks. Table 14-16 Descriptions of parameters for setting timing task time Parameter Suspend Time Description The system suspends an idle task and delay the time for using this task. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You can set the value manually. Alternatively, you can click
l l l l l l
and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS. yyyy stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
Resume Time
In the specified time, the system resume a suspended task and then the task is in the idle status and wait to be dispatched. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You can set the value manually. Alternatively, you can click
l l l l l l
and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS. yyyy stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
Related Tasks
14.10.5 Setting Time of Timing Tasks
14-86
Issue 06 (2008-12-16)
14.15.27 Parameters for Browsing CME Subtask

This part describes the parameters of CME subtasks. Table 14-17 lists the parameters of CME subtasks. Table 14-17 Descriptions of CME subtask parameters Parameter Task Name User Name Task Type Run Type Part Retry Description Name of the main task that the subtask belongs to. Creator of the main task. CME downloading. Execution type of the main task. The type can be Once or Period. Parameter of failure policy.
l
If Yes, then the system executes from the last failure, excluding the completed ones. If No, then the system executes the whole subtask.
Retry times Retry interval Name of the subtask. Phase
Times of retries. Value range: Next execution time=Last failed time+Retry period. Name of the subtask. Five phases are available:
l
Download: The current CME subtask is being downloaded to the client from the server. Verify: The current CME subtask is being verified. Preactivate: The configuration data of the current CME subtask is being verified. Activate: The current CME subtask is being activated. RollBack: The current CME subtask is being rolled back.
l l
l l
Status
Five states are available:

l l
Idle: The current CME subtask is in the idle status. Suspended: The current CME subtask is in the suspended status. Running: The current CME subtask is in the running status. Finished: The current CME subtask is in the finished status. Archived: The current CME subtask is in the archived status. It only indicates the status of the CME download task after the operation is complete.
l l l
Start Time
Start time of the Download phase of the subtask.
Issue 06 (2008-12-16)
14-87
Parameter Verity Period Reactivated Period Activated Period Progress Last Run Result Result information
Description Start time of verity period, which equals to end time of downloading plus verification interval. Start time of peractivated period, which equals to end time of verity period plus preactivation interval. Start time of activated period, which equals to end time of verity period plus activation interval. Progress of executing the subtask. Result of the subtask last time. Information on the running subtask results.
Related Tasks
14.10.6 Browsing CME Subtask
14.15.28 Parameters for Setting Period of CME Subtask

This part gives the descriptions of parameters for setting the execution time of each period of CME subtasks. parameter Table 14-18 lists the parameters for setting the execution time of each period of CME subtasks. Table 14-18 Descriptions of parameters of execution time of each period Parameter Start Time of Download Description The time for starting the CME subtask download. You can set the value manually, or select from the time select panel. The time format is YYYY-MM-DD HH:MM:SS.
l l l l l l
yyyy stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
Verity Period Reactivated Period Activated Period
The interval between the end time of the download period and the start time of the verity period. The interval between the end time of the verity period and the start time of the Preactivate period. The interval between the end time of the Preactivate period and the start time of the activated period.
14-88
Issue 06 (2008-12-16)
Related Tasks
14.10.7 Setting Period of CME Subtask
Issue 06 (2008-12-16)
14-89
15 NE Commissioning
15
About This Chapter
NE Commissioning
The M2000 automatically commissions NEs. The commissioning items are as follows: the automatic detection and configuration of NEs, the automatic performance check of new NEs, and the automatic report generation. You can monitor the commissioning process, and collect and analyze the commissioning report on the M2000 client. Currently, the commissioning of NodeB can be performed. 15.1 Managing a NodeB Commissioning Project To improve the commissioning efficiency, the M2000 can automatically perform the NodeB commissioning tasks. You need to only monitor the commissioning process and obtain the NE commissioning report after the NE commissioning task is complete. By analyzing the commissioning report, you can check the commissioning status. The management of an NE commissioning project enables you to change the NEs to be commissioned in a commissioning project, start or stop an NE commissioning task, or reupload the NE configuration files required during the commissioning process. 15.2 Obtaining the NodeB Commissioning Report You can learn the NE commissioning status by viewing the NE commissioning report on the M2000. 15.3 Reuploading the NE Configuration File This describes how to upload the NE configuration files to the server again. In this way, the NE configuration files on the server can be updated. 15.4 Reference to the NE Commissioning Interface This describes the NodeB commissioning interface and parameters to facilitate the NodeB commissioning operations.
Issue 06 (2008-12-16)
15-1
15 NE Commissioning
15.1 Managing a NodeB Commissioning Project

To improve the commissioning efficiency, the M2000 can automatically perform the NodeB commissioning tasks. You need to only monitor the commissioning process and obtain the NE commissioning report after the NE commissioning task is complete. By analyzing the commissioning report, you can check the commissioning status. The management of an NE commissioning project enables you to change the NEs to be commissioned in a commissioning project, start or stop an NE commissioning task, or reupload the NE configuration files required during the commissioning process. 15.1.1 NodeB Commissioning Items This describes the NE commissioning items that can be performed on the M2000. The items include the download of the software and configuration files, software activation, and network health check. When setting an NE commissioning task, you can choose one or multiple commissioning items according to the actual requirements. 15.1.2 Creating a NodeB Commissioning Project This describes how to create an NE commissioning project. In this way, the NEs that meet the requirements can automatically perform commissioning. In addition, the information about the commissioning process is displayed on the M2000 client. When a commissioning project is created successfully, the M2000 creates a commissioning task for each NodeB in the commissioning project. 15.1.3 Viewing the NodeB Commissioning Progress You can obtain the information about the commissioning project by viewing the NE commissioning project and the NE commissioning task within the project. 15.1.4 Adjusting the Commissioning Object You can add or delete the NEs to be commissioned in a commissioning project. The M2000 creates a commissioning task for each NE in a commissioning project. If you need to change a commissioning item in a commissioning project, you have to delete this project and create a new commissioning project to meet your requirements. 15.1.5 Deleting an NE Commissioning Task This describes how to delete unnecessary NE commissioning tasks. This part takes deleting a NodeB commissioning task as an example. The process for deleting a NodeB commissioning task is also applicable to that of deleting TGW and NodeB commissioning tasks. 15.1.6 Starting/Stopping a NodeB Commissioning Task This describes how to stop or restart a commissioning task according to your requirements.
15.1.1 NodeB Commissioning Items

This describes the NE commissioning items that can be performed on the M2000. The items include the download of the software and configuration files, software activation, and network health check. When setting an NE commissioning task, you can choose one or multiple commissioning items according to the actual requirements. For details about NE commissioning items, see Table 15-1.
15-2
Issue 06 (2008-12-16)
15 NE Commissioning
Table 15-1 NE commissioning items NE Commissioning Items BootRom Download BootRom Activate Software Download Software Activate ConfigFile Download Clock Synchronization Health Check Description
Downloads the BootRom on the server to the related NE. Downloads the BootRom software, which is saved in the NE standby file partition, to each board and upgrade the BootRom of each board. Downloads the NE software on the server to the related NE. Downloads the NE software, which is saved in the NE standby file partition, to each board to make the software take effect. Downloads the configuration file on the server to the corresponding NodeB. You can click Upload new config file to upload the saved configuration file on the M2000 server. This check box is selected by default. Synchronizes the clock information between the NE and the M2000. Checks the operating status of the entire network. The check items consist of the configuration status, cell, IPRAN status, and environment.
15.1.2 Creating a NodeB Commissioning Project

This describes how to create an NE commissioning project. In this way, the NEs that meet the requirements can automatically perform commissioning. In addition, the information about the commissioning process is displayed on the M2000 client. When a commissioning project is created successfully, the M2000 creates a commissioning task for each NodeB in the commissioning project.
Prerequisite
l l
An NE is properly connected to the M2000. The required preparation for the commissioning is complete. For details about the commissioning preparations, see Preparation Before Commissioning.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 Click Create NodeB Commissioning Project. The Create NodeB Commissioning Project Please Select The NodeBs To Be Surveyed dialog box is displayed. Step 3 Set the Project Name and select the NodeBs that need to be commissioned.
l
Choose one or multiple conditions from RNC, NodeB Type, Version, and DualMode to regroup the NEs in the NE navigation tree. If you choose one or multiple conditions, but the M2000 fails to obtain the selected conditions, then the NodeB is displayed under a nameless parent node. For example, if the RNC is selected as one condition, but the M2000 fails to
Issue 06 (2008-12-16)
15 NE Commissioning
obtain the information about the RNC that the NodeB belongs to, then, the NodeB is displayed under a nameless parent node.
l l l
Enter the name of the NodeB in Search, and then the system directly locates it. You can choose multiple NodeBs for commissioning from a commissioning project. After a commissioning project is created, you can add NEs to be commissioned in this commissioning project. For details, see 15.1.4 Adjusting the Commissioning Object. The NodeB whose commissioning tasks are created is not displayed on the NE navigation tree in the Create NodeB Commissioning Project- Please Select The NodeBs To Be Surveyed dialog box.
Step 4 Click Next. The Create NodeB Commissioning Project Parameter Setting dialog box is displayed. Step 5 In Operation Setting, select the commissioning items.
l l
For details about the commissioning items, see 15.1.1 NodeB Commissioning Items. You can select all the operation items by selecting All.
Step 6 Optional: Set the BootRom versions. If the BootRom Download or the BootRom Activate commissioning item is selected, choose a BootRom version from the drop-down list of BootRom Version for each NE in the commissioning project. Step 7 Optional: Set the software versions. If the Software Download or the Software Activate commissioning item is selected, choose a software version from the drop-down list of Software Version for each NE in the commissioning project. Step 8 Optional: Upload the configuration files. If the ConfigFile Download commissioning item is selected, you need to upload the configuration files generated by the CME. 1. 2. Click Upload new config file. In Choose ConfigFile Directory, find the folder where the NodeB configuration files are saved.
NOTE
You need to save the NodeB configuration files in the folder named by the corresponding NodeB, and save the folder in the specified path. The default path is client installation path\client\Data \NodeBSurvey\NodeBConfig. You can upload the configuration files in batches. You can upload all the NodeB configuration files to the server in batches if you choose the default path client installation path\client\Data \NodeBSurvey\NodeBConfig as the save path for the NodeB configuration files.
3.
Click Upload Config To Server. The NodeB configuration files in the specified save path are uploaded to the server.
Step 9 Click Finish. The system displays the following message: Do you want to run this project now?. Step 10 Click Yes to run the commissioning project immediately.
l
If performed immediately, the project is under the Runningnode; If not performed immediately, the project is under the Waiting node.
15-4

l
15 NE Commissioning
Right-click a commissioning project that is not started, and then choose Run Project Now to manually perform this commissioning project.
Step 11 Optional: Delete a commissioning project. 1. Right-click a commissioning project to be deleted, and then choose Delete Project. The system displays the following message: Do you want to delete this project?. 2. Click Yes.
----End
Postrequisite
l
To view the commissioning progress of an NE commissioning task, see 15.1.3 Viewing the NodeB Commissioning Progress. To add or to delete an NE in a commissioning project, see 15.1.4 Adjusting the Commissioning Object. To start or stop a commissioning task in a commissioning project, see 15.1.6 Starting/ Stopping a NodeB Commissioning Task. To upload the NE configuration files required by the ConfigFile Download commissioning item, see 15.3 Reuploading the NE Configuration File. To obtain an NE commissioning report, see 15.2 Obtaining the NodeB Commissioning Report.
15.1.3 Viewing the NodeB Commissioning Progress

You can obtain the information about the commissioning project by viewing the NE commissioning project and the NE commissioning task within the project.
Prerequisite
Some NE commissioning tasks are created.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. You can query the status and progress of a commissioning project and those of a commissioning task within the project. Step 2 View the status of a commissioning project. The Projects tab page lists all the commissioning projects on the M2000. A commissioning project can be in one of the following three status: WaitingRunning, and Finished. Step 3 View the progress of a commissioning task.
l
If you click a commissioning project under the Waiting node or under the Running node, the window in the right pane displays the information about all the commissioning tasks contained in this commissioning project. The information consists of NodeB Name, Current Status, and Percent.
Issue 06 (2008-12-16)
15 NE Commissioning
l
On the NodeB Check Information tab page, monitor the detailed information about a NodeB commissioning task. You can also right-click the blank area on this tab page, and then choose Clean All Messages to delete all the commissioning information displayed in this field.
Step 4 Optional: Click Refresh to refresh the information in the NodeB Commissioning window in real time. ----End
15.1.4 Adjusting the Commissioning Object

You can add or delete the NEs to be commissioned in a commissioning project. The M2000 creates a commissioning task for each NE in a commissioning project. If you need to change a commissioning item in a commissioning project, you have to delete this project and create a new commissioning project to meet your requirements.
Prerequisite
The NE commissioning tasks are created.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 Perform the following operations to change the NodeBs to be commissioned according to the actual requirements. Adding/Deleting a NodeB Adding a NodeB Operation 1. In Projects, right-click the commissioning project that you want to add a NodeB to, and then choose Add NodeBs To Project from the shortcut menu. 2. In Create NodeB Commissioning Project Please Select The NodeBs To Be Surveyed, select one or multiple NodeBs. Click Next. 3. If you select the CongifFile Download commissioning item when creating a commissioning task, you can upload the NodeB configuration files to the server again. For details about how to upload the NE configuration files, see 15.3 Reuploading the NE Configuration File.
15-6
Issue 06 (2008-12-16)
15 NE Commissioning
Adding/Deleting a NodeB Deleting a NodeB
Operation Two methods available for deleting a NodeB in a commissioning project are as follows: Deleting a NodeB through Projects and deleting a NodeB through Survey NodeBs. To delete a NodeB through Projects, perform the following operations: 1. In Projects, choose the project that you want to delete a NodeB. 2. In the list of commissioning tasks, right-click the NodeB commissioning task, and then choose Delete NodeBs From Project . To delete a NodeB through Survey NodeBs, perform the following operations: 1. In Survey NodeBs, select a NodeB node according to the NodeB name. You can locate the required NodeB quickly by entering key words in the Search text box. 2. Right-click a commissioning task in the task list in the right pane, and then choose Delete NodeBs From Project .
----End
15.1.5 Deleting an NE Commissioning Task

This describes how to delete unnecessary NE commissioning tasks. This part takes deleting a NodeB commissioning task as an example. The process for deleting a NodeB commissioning task is also applicable to that of deleting TGW and NodeB commissioning tasks.
Prerequisite
l l
The NE commissioning tasks are created. The NE commissioning process of the task to be deleted is complete.
Context
For the TGW, you can choose Maintenance > TGW Commissioning to start the operation.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 Choose a NodeB commissioning task to be deleted from Project. Right-click this task and choose Delete Project. Step 3 In the displayed Delete NodeB Commissioning Project dialog box, click Yes. ----End
15.1.6 Starting/Stopping a NodeB Commissioning Task

This describes how to stop or restart a commissioning task according to your requirements.
15 NE Commissioning
Prerequisite
Context
l l
Running commissioning tasks cannot be restarted. Finished commissioning tasks cannot be stopped.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 In Projects, choose the commissioning project where the NodeB commissioning task exists. On the Survey NodeBs tab page, you can select the NodeB nodes according to the NodeB name. Step 3 In the commissioning task list in the right pane, start or stop a commissioning task as required. Operation Type Start Stop Procedure Right-click a commissioning task that needs to be restarted, and then choose Start NodeBs Commissioning Task . Right-click a commissioning task that needs to be stopped, and then choose Stop NodeBs Commissioning Task .
----End
15.2 Obtaining the NodeB Commissioning Report

You can learn the NE commissioning status by viewing the NE commissioning report on the M2000.
Prerequisite
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 In Projects, right-click the project whose NodeB commissioning report is required, and then choose Get Project Report. The browser automatically opens and displays the content of the commissioning report. The check items of the commissioning report consist of configuration status, cells, IPRAN status, and environment. You can learn the entire commissioning process by analyzing the commissioning report.
NOTE
The NodeB commissioning report is complete only when 100% is displayed in the Percent area of a commissioning task.
15-8
Issue 06 (2008-12-16)
15 NE Commissioning
Step 3 Optional: You can save the commissioning report to the specified path by clicking Save...as on the browser. ----End
15.3 Reuploading the NE Configuration File

This describes how to upload the NE configuration files to the server again. In this way, the NE configuration files on the server can be updated.
Prerequisite
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning window is displayed. Step 2 In Projects, right-click the commissioning project whose configuration files need to be uploaded again, and then choose Upload NodeBs Congif File Again. Step 3 In Create NodeB Commissioning Project Please Select The NodeBs To Be Surveyed, click Next. The Create NodeB Commissioning Project Parameter Setting window is displayed. Step 4 Click Upload new config file. Step 5 In Choose NodeBs Config Directory, specify the directory where the NodeB configuration files are placed. The NodeB configuration files are saved in the folders named by the corresponding NodeB name. All the folders that save the NodeB configuration files are saved in a parent folder, such as NodeBConfig.
NOTE
The configuration files can be uploaded in batches. Therefore, all the configuration files are uploaded to the server if you select the directory of the NodeBConfig folder, regardless of one or multiple configuration files that you select for the upload.
Step 6 Click Upload Config To Server. The mapping NodeB configuration files are uploaded to the server. Step 7 Click Finish. ----End
15.4 Reference to the NE Commissioning Interface

This describes the NodeB commissioning interface and parameters to facilitate the NodeB commissioning operations. 15.4.1 Interface Description: Viewing the NodeB Commissioning Progress This describes the NodeB commissioning interface so that you can learn the interface components and the functions of each component.
15 NE Commissioning
15.4.2 Parameter for Creating an NodeB Commissioning Project This describes the parameters in the Create NodeB Commissioning Project dialog box. 15.4.3 Parameter for Selecting the Path to the Configuration File This describes the parameters in the Choose Config Directory dialog box.
15.4.1 Interface Description: Viewing the NodeB Commissioning Progress

This describes the NodeB commissioning interface so that you can learn the interface components and the functions of each component. The NodeB Commissioning interface consists of the following four parts: the Projects tab, the Survey NodeBs tab, the list of NodeB commissioning tasks, and the NodeB Check Information tab, as shown in Figure 15-1. Figure 15-1 NodeB Commissioning interface
Number Description (1) (2) All the created commissioning projects are displayed on the Projects tab page. According to the names of NodeBs, the currently created commissioning tasks are displayed on the Survey NodeBs tab page. The system directly locates the NE if you enter an NE name in Search. (3) All the commissioning tasks contained in a selected project are displayed in the list of NodeB commissioning tasks. The M2000 creates a commissioning task for each NodeB in the commissioning project. The details about the NodeB commissioning process are displayed on the NodeB Check Information tab page.
(4)
15-10
Issue 06 (2008-12-16)

Number Description (5)
15 NE Commissioning
You can use the buttons to perform different operations, such as creating a NodeB commissioning project and manually refreshing the information in the window.
15.4.2 Parameter for Creating an NodeB Commissioning Project

This describes the parameters in the Create NodeB Commissioning Project dialog box.
Parameters in the Create NodeB Commissioning Project Please Select The NodeB Dialog Box
Parameter Project Name Description Indicates the project name of the created NE commissioning task. The name is unique and cannot be null. The value range is from 1 to 255 characters. The project name cannot contain special characters, such as ` ~ ! @ # $ % ^ & * ( ) + = { } [ ] \\ | ; ' : \ " < > , . ? / and space. Search RNC NodeB Type Version After entering the corresponding NE name, you can locate the NE in the OMC tree. If you select this option, then every NodeB in the OMC tree is regrouped according to the RNCs that the NodeBs belong to. If you select this option, then every NodeB in the OMC tree is regrouped according to the NodeB types. If you select this option, then every NodeB in the OMC tree is regrouped according to the NodeB versions.
Parameters in the Create NodeB Commissioning Project- Parameter Setting Dialog Box
Parameter Parameter Setting BootRomVersion SoftwareVersion Operation Setting All BootRom Download BootRom Activate Description Choose the version of the BootRom from the dropdown list. Choose the version number of the NodeB from the drop-down list. Selects all the following operation items. Downloads the BootRom on the server to the NodeB. Downloads the BootRom software, which is saved in the NodeB standby file partition, to each board and upgrades the BootRom of each board.
15-11
Issue 06 (2008-12-16)
15 NE Commissioning
Parameter Software Download Software Activate
Description Downloads the NodeB software on the server to the NodeB. Downloads the NodeB software, which is saved in the NodeB standby file partition, to each board so that the software takes effect. Downloads the configuration file on the server to the NodeB. You can click Upload new config file to upload the saved configuration file to the M2000 server. This check box is selected by default. Synchronizes the clock information between the NE and the M2000. Checks the operating status of the entire network. The check items consist of the configuration status, cells, IPRAN status, and environment.
ConfigFile Download
Clock Synchronization Health Check
15.4.3 Parameter for Selecting the Path to the Configuration File

This describes the parameters in the Choose Config Directory dialog box.
Parameter Look In File Name File Type Description Chooses the save path of the configuration files from the dropdown list. Indicates the name of the folder where the configuration files are saved. The file type is null and unavailable.
15-12
Issue 06 (2008-12-16)
16 NE Maintenance Enhanced Management
16
NE Maintenance Enhanced Management
About This Chapter

The M2000 provides the enhanced maintenance management for some NEs to facilitate servicing these NEs. The NE enhanced maintenance management involves device management, trace management, monitoring management, and real-time performance monitoring. You can start this function only after the related components are upgraded on the client. 16.1 Upgrading the Version of Enhanced NE Maintenance When enhanced versions of NE maintenance are upgraded, the Enhance NE Maintenance menu is generated. 16.2 Equipment Management Equipment management is to configure and maintain the equipment of the NEs through MML command, and ensure the proper operation of the system. 16.3 Tracing Management Tracing management is to locate and remove the NE equipment faults through tracking the information of interfaces and signaling links. It is an important part of the routine NE maintenance. 16.4 Monitoring Management Monitoring management is to monitor the equipment of the NEs and service operating status in graphic and data mode in real time, and analyze and handle the exceptions. It is an important part of the routine NE maintenance. 16.5 Realtime Performance Monitoring Management The M2000 provides real-time performance monitoring, which monitors the performance of connection, cells, and links by using graphics or data. In addition, through the analysis of exceptional cases, this function facilitates servicing equipment and troubleshooting.
Issue 06 (2008-12-16)
16-1
16.1 Upgrading the Version of Enhanced NE Maintenance

When enhanced versions of NE maintenance are upgraded, the Enhance NE Maintenance menu is generated.
Procedure
Step 1 Select a physical NE on the topology view or from the navigation tree. Step 2 Right-click the NE and select Upgrade Enhanced NE Maintenance from the shortcut menu. The Confirm dialog box is displayed. Step 3 Click Yes. The Confirm dialog box is displayed, prompting The upgrade file exists. Do you want to redownload the upgrade file?. If no upgrade file exists in the local PC, the dialog box is not displayed. Step 4 Click Yes.
NOTE
The local system can save only three versions of the upgrade file. Click Yes to redownload the upgrade file. Click No to run the existing upgrade file.
Step 5 Select the installation directory.

NOTE
The directory must be the installation directory of the current client.
Step 6 Click Next to install upgrade file. Step 7 Click Finish. Finish the installation of the upgrade file. Step 8 Reboot the M2000. Step 9 Select a physical NE and right-click the NE. The Enhance NE Maintenance menu is generated.
NOTE
Select a function menu item on the Enhance NE Maintenance menu. If the enhanced public component version of NE maintenance on the M2000 client is consistent with the version on the M2000 server, the function is performed. If their versions are not consistent, you need to perform the following operations:
l
If the client version is earlier than the server version, the system prompts that enhanced public components of NE maintenance need be upgraded. Click Yes to start the upgrade of the enhanced public components of NE maintenance; click No to forcibly perform the maintenance. If the client version is later than the server version, the system prompts that enhanced versions of NE maintenance need be installed on the server. You can also uninstall enhanced public components of NE maintenance and re-upgrade enhanced versions of NE maintenance.
----End
16.2 Equipment Management

Equipment management is to configure and maintain the equipment of the NEs through MML command, and ensure the proper operation of the system.
Prerequisite
Start the device panel on the M2000 client to perform the tracking management on the NEs. The startup of the device panel must satisfy the following three conditions:
l l l
You have logged in to the M2000 client as an NE user of the NE. The mediation software of the NE is installed on both the M2000 server and client. The NE is properly connected to the M2000.
16.3 Tracing Management

Tracing management is to locate and remove the NE equipment faults through tracking the information of interfaces and signaling links. It is an important part of the routine NE maintenance.
Prerequisite
Start the trace panel on the M2000 client to perform the tracking management on the NEs. The startup of the tracking panel must satisfy the following three conditions:
l l l
16.4 Monitoring Management

Monitoring management is to monitor the equipment of the NEs and service operating status in graphic and data mode in real time, and analyze and handle the exceptions. It is an important part of the routine NE maintenance.
Prerequisite
Start the monitor panel on the M2000 client to perform the tracking management on the NEs. The startup of the monitor panel must satisfy the following three conditions:
l l l
16.5 Realtime Performance Monitoring Management

The M2000 provides real-time performance monitoring, which monitors the performance of connection, cells, and links by using graphics or data. In addition, through the analysis of exceptional cases, this function facilitates servicing equipment and troubleshooting.
Prerequisite
Before starting the real-time performance monitoring management, ensure that the following four conditions are satisfied:
l l l l
You have logged in to the M2000 client as an NE user of the NE. The mediation software of the NE is installed on both the M2000 server and client. The NE is properly connected to the M2000. Only devices of RNC or NodeB support this function.
16-4
Issue 06 (2008-12-16)
17 FAQ
17
About This Chapter
17.1 Why Cannot I Log In to the Client? This part describes the prompts of client login failure and analyzes the causes. 17.2 Why Does the Client Abort? This part analyzes the causes of client abort and gives the solution. 17.3 Why Can't the Client Work? This part analyzes the causes of running client failure and gives the solution. 17.4 Why Is the Client Interface Abnormal? This part analyzes the causes of client abnormality and gives the solution.
FAQ
This part describes the typical faults of the M2000 client, analyzes the possible causes, and provides the solution.
17.5 Why Is the Connection Between Client and Server Discontinuous? This part analyzes the discontinuous connection between client and server and gives the solution. 17.6 Why Can't a Topology View Be Refreshed? This part analyzes the causes of refreshing topology view failure and gives the solution. 17.7 Why Does the Automatic NodeB Search Fail? This part analyzes the causes of the failure of automatic NodeB search and gives the solution. 17.8 Why Is the Name of a New Topology Object a Repeat One? This part analyzes the causes of the prompt "The attribute value name already exists." and gives the solution. 17.9 Why Cannot Creating/Deleting an NE /Be Completed after a Long Time? This part analyzes the reason for failure to creating or deleting NEs and gives the solution. 17.10 Why Does a Real-Time Print Delay? This part analyzes the causes of the real-time print delay and gives the solution. 17.11 Why Can't Alarm Notifications by SMS Be Received? Failure of receiving alarm notifications by SMS falls into two types: failed to receive alarm SMS in real time and failed to receive alarm SMS. This part analyzes the respective causes and gives the solution.
17 FAQ
17.12 How to select or unselect multiple nodes? This part describes the functions of the keys Ctrl and Shift, and how to use the space key to quickly select and deselect check boxes.
17-2
Issue 06 (2008-12-16)
17 FAQ
17.1 Why Cannot I Log In to the Client?

This part describes the prompts of client login failure and analyzes the causes. 17.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and correct." This part analyzes the causes of system prompting wrong user name and password and gives the solution. 17.1.2 Prompt "Invalid user account." This part analyzes the cause of the prompt "Invalid user account." and gives the solution. 17.1.3 Prompt "Invalid login duration." This part analyzes the cause of the prompt "Invalid login duration." and gives the solution. 17.1.4 Prompt "Invalid password." This part analyzes the cause of the prompt "Invalid password." and gives the solution. 17.1.5 Prompt "The password has expired. Please change your password!" This part analyzes the causes of the prompt "The password has expired. Please change your password!" and gives the solution. 17.1.6 Prompt "Maintenance Mode." This part analyzes the causes of the prompt "Maintenance Mode." and gives the solution. 17.1.7 Prompt "The User Has Reached the Maximum Login Attempts. The User Account Has Been Locked, and It Can Be Unlocked in 1 Minute." This part analyzes the causes of system prompting user locked and gives the solution. 17.1.8 Prompt "The Server Doesn't Exist or Service Is Not Running." This part analyzes the cause of the prompt "The Server Doesn't Exist or Service Is Not Running." and gives the solution. 17.1.9 Prompt "Exceed Maximum Sessions." This part analyzes the causes of the prompt "Exceed maximum sessions" at the login and gives the solutions. 17.1.10 Prompt "Loading Module Failed, System Will Exit." This part analyzes the cause of the prompt "Loading Module Failed, System Will Exit." and gives the solution. 17.1.11 Prompt "Failed to Log in to the Server after the Auto Client Upgrade or Running Exception" This part analyzes the abnormal running of the client after automatic upgrade and gives the solution.
17.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and correct."
This part analyzes the causes of system prompting wrong user name and password and gives the solution.
Issue 06 (2008-12-16)
17-3
17 FAQ
Symptoms
The login to the M2000 client fails. The system prompts Login failed. Confirm that your user name and password are case sensitive and correct.
Possible Causes
The possible causes include:
l l
The user account does not exist. The user account is deleted because the user account has not been used for login for more than six months.
Handling Suggestions
1. 2. Relog in to the M2000 client with the correct user name and password. Recreate the user account.
17.1.2 Prompt "Invalid user account."

This part analyzes the cause of the prompt "Invalid user account." and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts Invalid user account.
Possible Causes
l l
The user account is set to Invalid. The system automatically sets this user account to Invalid because the user account has not been used for login for three months.
Contact the M2000 administrator to set the status of the user account to Valid.
17.1.3 Prompt "Invalid login duration."

This part analyzes the cause of the prompt "Invalid login duration." and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts Invalid login duration.
Possible Causes
The current time is not in the time range of permitting the user account to perform operation.
Contact the M2000 administrator to change the operating time range for this user account.
17 FAQ
17.1.4 Prompt "Invalid password."

This part analyzes the cause of the prompt "Invalid password." and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts Invalid password.
Possible Causes
The password is incorrect.
Relog in to the M2000 client with the correct user name and the password.
17.1.5 Prompt "The password has expired. Please change your password!"
This part analyzes the causes of the prompt "The password has expired. Please change your password!" and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts Password expired. Please change your password!.
Possible Causes
The login password of the user account has expired.
Contact the M2000 administrator to reset the password for this user account.
17.1.6 Prompt "Maintenance Mode."

This part analyzes the causes of the prompt "Maintenance Mode." and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts Maintenance mode.
Possible Causes
The M2000 system is running in the maintenance mode.
Contact the M2000 administrator to reset the running mode of the M2000 system.
17 FAQ
17.1.7 Prompt "The User Has Reached the Maximum Login Attempts. The User Account Has Been Locked, and It Can Be Unlocked in 1 Minute."
This part analyzes the causes of system prompting user locked and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts The user has reached the maximum login attempts. The user account has been locked, and it can be unlocked in 1 minute.
Possible Causes
The password used for the current user account to log in to the system is incorrect, and the number of attempts to log in has reached the set threshold.
Contact the M2000 administrator to unlock the user account, or wait until the system unlocks the user account.
17.1.8 Prompt "The Server Doesn't Exist or Service Is Not Running."

This part analyzes the cause of the prompt "The Server Doesn't Exist or Service Is Not Running." and gives the solution.
Symptoms
The login to the M2000 client fails. The system prompts The server doesn't exist or service is not running.
Possible Causes
l l l l
The IP address of the server is incorrect. The communication between the client and the server is faulty. The server or the service is not running. The server has more than one IP address.
1. 2. Use correct server IP address. Check the connection between the client and the server. Ensure that the client can ping to the server. For details, refer to the related software installation user guide. 3.
17-6
Contact the M2000 administrator to check the operational status of the server.
17 FAQ
17.1.9 Prompt "Exceed Maximum Sessions."

This part analyzes the causes of the prompt "Exceed maximum sessions" at the login and gives the solutions.
Symptoms
The login to the M2000 client fails. The M2000 prompts Exceed maximum sessions.
Possible Causes
The number of users logging in to the M2000 system reaches the limit.
Wait until a user exits the system.
17.1.10 Prompt "Loading Module Failed, System Will Exit."

This part analyzes the cause of the prompt "Loading Module Failed, System Will Exit." and gives the solution.
Symptoms
The login to the M2000 client fails. The M2000 prompts Loading module failed, system will exit.
Possible Causes
The time on the client is inconsistent with that on the server.
Maintain time consistency between the client and the server.
17.1.11 Prompt "Failed to Log in to the Server after the Auto Client Upgrade or Running Exception"
This part analyzes the abnormal running of the client after automatic upgrade and gives the solution.
Symptoms
When you log in to the server from the client, the system prompts for an upgrade. After the upgrade, you cannot log in to the server, or function exceptions occur after you log in to the server.
Possible Causes
l
The server version and the client version are inconsistent. During the upgrade, the client version is higher than the server version.
Issue 06 (2008-12-16)
17-7
17 FAQ
l
The client and server versions do not belong to the same version series. The client upgrade will be smooth if: The client version and the server version belong to the same version series, for example, C02B022. The server version is higher than the client version, for example, the server version is C02B022SP01 and the client version is C02B022.
Uninstall the existing client, and install the client with the correct version.
17.2 Why Does the Client Abort?

This part analyzes the causes of client abort and gives the solution.
Symptoms
The M2000 client interface closes automatically.
Possible Causes
l
You are forced to exit the M2000 client. The user with the operation privileges, such as the M2000 administrator, can force you to exit the M2000 client. The M2000 client prompts a message before your exit.
You change the time of the current M2000 client. In this case, the M2000 client does not prompt any message before your exit. The M2000 conflicts with a third-party program. In this case, the M2000 client does not prompt any message before your exit.
1. 2. 3. Contact the M2000 administrator for the operation privilege. Do not change the time of the current M2000 client during the M2000 operation. Exit the M2000 client before you change the time. Close the third-party program that possibly conflicts with the M2000.
17.3 Why Can't the Client Work?

This part analyzes the causes of running client failure and gives the solution.
Symptoms
The M2000 client fails to start.
Possible Causes
l
The computer is short of memory.

17-8
17 FAQ
The M2000 client operation requires a memory of 256 MB. When the system runs short of memory, the M2000 client prompts out of memory.
l
Errors occur when you install the M2000 client.
1. 2. 3. Avoid starting several M2000 clients on the same terminal. Quit other programs irrelevant to the M2000 client on the terminal. Uninstall the existing M2000 client, and install a new one.
17.4 Why Is the Client Interface Abnormal?

This part analyzes the causes of client abnormality and gives the solution.
Symptoms
Characters displayed on the M2000 client are abnormal.
Possible Causes
The configuration file is incorrect.
1. 2. Uninstall the existing M2000 client applications. Install new applications.
17.5 Why Is the Connection Between Client and Server Discontinuous?

This part analyzes the discontinuous connection between client and server and gives the solution.
Symptoms
The client cannot receive the event alarms and broadcast messages from the server. On the client, the bulb at the lower right corner of the GUI is on and off intermittently. See Figure 17-1. Figure 17-1 The connection fails between the client and the server
Possible Causes
A CORBA event is called in a different way from a common CORBA request. For a common request, the client initiates a connection and sends the request to the server. The server responds
17 FAQ
to the client using the same connection; however, for a CORBA event, when the client initiates a subscription request, the server sets up a new connection with the client and sends the event to the client using this new connection. Therefore, such a fault results from the failure in setting up a connection from the server to the client. The possible causes are as follows:
l
You are using dual IP addresses of the client. The client monitors either of the IP addresses. Therefore, sometimes the client connects to the server normally, sometimes does not.
You are using a firewall.
l
If you set dual client IP addresses, change the settings on the client as follows. Open default.xml in \lib\openorb\config, and then find the following information.
 <property name="listenAddress" value="0.0.0.0"> <description> Address to listen on on multi-homed host. Defaults to 0.0.0.0, all local addresses. </description> </property> <property name="port" value="53100"> <description> Port for the iiop transport to listen on. Defaults to 0, any available port.<p/> Command line alias Port is available. </description> </property>
Change the value of listenAddress to a client IP address that you can ping successfully from the server. In addition, you can use this IP address to connect to the port 53100 by Telnet.
l
If you use a firewall, change the settings as follows. On the firewall, open port 53100 from the server to the client IP address. The IP address and the port must be consistent with those set in the configuration file on the client.
17.6 Why Can't a Topology View Be Refreshed?

This part analyzes the causes of refreshing topology view failure and gives the solution.
Symptoms
The connection between the client and the server is normal. The topology view, however, cannot be refreshed in real time.
Possible Causes
Multiple IP addresses are configured for the PC serving as the client.
In this case, specify the IP address for communications before logging in to the M2000 server. For details, refer to the related software installation user guide.
17 FAQ
17.7 Why Does the Automatic NodeB Search Fail?

This part analyzes the causes of the failure of automatic NodeB search and gives the solution.
Symptoms
The system fails to discover NodeBs automatically.
Possible Causes
The names of the NodeBs are invalid. The NodeB name must not contain the following characters: ~ ! @ # $ % ^ & * ( ) + - = { } [ ] \ \ | ; ' : \ " < > . ? /. Also the name must not end with a space.
Execute the corresponding commands on the RNC to reset the names of the NodeBs.
17.8 Why Is the Name of a New Topology Object a Repeat One?

This part analyzes the causes of the prompt "The attribute value name already exists." and gives the solution.
Symptoms
When you create a topology object, the system prompts The attribute value name already exists., but you cannot see the topology object with this name on the topology view.
Possible Causes
l l
The current topology is not refreshed in real time. You do not have the privilege to create objects with the same name.
Change the object name and recreate the topology object.
17.9 Why Cannot Creating/Deleting an NE /Be Completed after a Long Time?

This part analyzes the reason for failure to creating or deleting NEs and gives the solution.
17 FAQ
Symptoms
An NE cannot be created or deleted after a long period of time.
Possible Causes
A CORBA event is called in a different way from a common CORBA request. For a common request, the client initiates a connection and sends the request to the server. The server responds to the client using the same connection; however, for a CORBA event, when the client initiates a subscription request, the server sets up a new connection with the client and sends the event to the client using this new connection. When the client has two IP address, the client monitors either of the IP addresses. Therefore, sometimes the client connects to the server normally, sometimes does not.
Open default.xml in \lib\openorb\config, and then find the following information.
 <property name="listenAddress" value="0.0.0.0"> <description> Address to listen on on multi-homed host. Defaults to 0.0.0.0, all local addresses. </description> </property> <property name="port" value="53100"> <description> Port for the iiop transport to listen on. Defaults to 0, any available port.<p/> Command line alias Port is available. </description> </property>
Change the value of listenAddress to a client IP address that you can ping successfully from the server. In addition, you can use this IP address to connect to the port 53100 by Telnet.
17.10 Why Does a Real-Time Print Delay?

This part analyzes the causes of the real-time print delay and gives the solution.
Symptoms
After you enable the alarm messages real-time print function, the printer cannot print the reported alarm messages displayed in the browse window.
Possible Causes
The printer prints the alarm messages when the records fill one whole page or five minutes after the printer receives the alarms.
This is normal. No operation is necessary.
17-12
Issue 06 (2008-12-16)
17 FAQ
17.11 Why Can't Alarm Notifications by SMS Be Received?

Failure of receiving alarm notifications by SMS falls into two types: failed to receive alarm SMS in real time and failed to receive alarm SMS. This part analyzes the respective causes and gives the solution.
Symptoms
l l
The alarm SMS received on the mobile phone notifies the alarm generated 10 minutes ago. Both an e-mail address and a phone number are set in the Remote notify tab of the Fault Service Settings dialog box. But only an e-mail is received when an alarm occurs.
Possible Causes
l
Failure to receive alarm SMSs in real time: It takes about six seconds for an SMS to reach the receiver. Therefore, the M2000 can send a maximum of 10 SMSs in one minute. The delay occurs when too many alarms are generated. Failure to receive alarm Emails in real-time: The phone number is incorrect. The phone number must begin with the country code, for example, 861361234xxx1, where 86 is the country code of the People's Republic of China (PRC). In some countries or districts, however, the phone number must not begin with the country code, for example, the Unite Arab Emirates (UAE).
l
Failure to receive alarm SMSs in real-time: In the Remote Notify tab of Fault Service Settings, select fewer types of alarms to send by SMS. Ensure that only alarms with the highest priority are sent to the mobile phone through the SMS. Failure to receive alarm Emails in real-time: Enter the correct phone number in Remote notify detail settings.
17.12 How to select or unselect multiple nodes?

This part describes the functions of the keys Ctrl and Shift, and how to use the space key to quickly select and deselect check boxes. To quickly select or deselect multiple check boxes, do as follows:
l
If the check boxes are not arranged sequentially, as shown in Figure 17-2, then: Figure 17-2 Check box arrange style 1
Issue 06 (2008-12-16)
17-13
17 FAQ
You can press Ctrl and select the desired check boxes. The color of the selected check boxes is deeper, as shown in Figure 17-2. Press the space key, and then the deep colored check boxes are selected, as shown in Figure 17-3. To deselect the deep colored check boxes, press the space key again. Figure 17-3 Selected check boxes style 1
You can also select the check boxes by ticking off the . Then the check boxes change to . Select the check boxes, as shown in Figure 17-4. Figure 17-4 Selected check boxes style 2
If the check boxes are not arranged sequentially, as shown in Figure 17-5, then: Figure 17-5 Check box arrange style 2
You can press Shift, and click the first desired check box and then the last one. Then the color of all the desired check boxes is deeper, as shown in Figure 17-5. Press the space key, and then the deep colored check boxes are selected, as shown in Figure 17-6. To deselect the deep colored check boxes, press the space key again. Figure 17-6 Selected check boxes style 3
17-14
Issue 06 (2008-12-16)
17 FAQ
Issue 06 (2008-12-16)
17-15
18 Terms, Acronyms, and Abbreviations
18
Terms, Acronyms, and Abbreviations
About This Chapter

This part gives the M2000 glossary and abbreviations. 18.1 Terms M2000 glossary. 18.2 Abbreviations This describes the M2000 abbreviations.
Issue 06 (2008-12-16)
18-1
18.1 Terms
M2000 glossary.
FDN
Unique identification of an NE in the topology. For example, 0.4.1.
Numeric Type
At present, four types of data are available, which includes:
l l l l
Data: NE configuration and log files. License: NE license. Software: NE version or patch files. Other: Other types of data.
Current Time
Time displayed on the server. The time format is YYYYMMDDHHmmss, for example, 20060106103055.
MO
Configuration or resource object managed.
Resource Type
Type of an resource object
LMT
Local Maintenance Terminal is a logical concept. LMT is connected to the external network of the RNC and provides the user interface for RNC operation and maintenance. In RNC operation and maintenance subsystem, LMT is the terminal for operating and maintaining the RNC.
18.2 Abbreviations
This describes the M2000 abbreviations. A ACL ADPCM AL AMG
18-2
Access Control List Adaptive Differential Pulse Code Modulation Audit Logger Access Media Gateway
ASN.1 ASN-GW B BWA C CM CORBA CPU D DHCP E EM EMF EML EMS F FTP FM G GUI H HTTP I iM2000 ID IP L LMT M MA MB
Abstract Syntax Notation One Access Service Network Gatway
Broadband Wireless Access
Configure Manager Common Object Request Broker Architecture Center Processing Unit
Dynamic Host Configuration Protocol
Event Manager Element Management Framework Element Management Layer Element Management System
File Transfer Protocol Fault Manager
Graphic User Interface
Hyper Text Transport Protocol
integrated Management Application Platform Identity Internet Protocol
Local Maintenance Terminal
Multi-service Access MegaByte
Issue 06 (2008-12-16)
18-3
MAU MIB MML MTBF MTTR N NBI NGN NML NMS O OAM OMC OSS P PM Q QoS R RAS RM S SBM SGSN SM SML SNMP SQL T TFTP
Media Attachment Unit Management Information Base Man Machine Language Mean Time Between Failures Mean Time To Recovery
Northbound Interface Next Generation Network Network Management Layer Network Management System
Operations, Administration and Maintenance Operation and Maintenance Center Operation Support System
Performance Manager
Quality of Service
Remote Access Server Resource Manager
System Backup Manager HUAWEI M900/M1800 Serving GPRS Support Node Security Manager Service Management Layer Simple Network Management Protocol Structured Query Language
Trivial File Transfer Protocol
18-4
Issue 06 (2008-12-16)
TM TMF TMN X XML
Topology Manager Tele Management Forum Telecommunications Management Network
Extensible Mark-up Language
Issue 06 (2008-12-16)
18-5
Index
Index
A
ACL modifying, 4-34 system, 4-10 user, 4-25 activating counter threshold, 6-47 NE software AG, 8-48 ASN-GW, 8-67 NE software patch AG, 8-50 ASN-GW, 8-69 BSC, 8-58 adding alarm filter condition, 2-47 domain, 11-16 level redefinition, 2-49 monitored object group, 2-114 result query template, 6-31 adding user to user group, 4-23 adjusting topology view, 3-54 advanced correlation rule a single alarm, example, 2-55 adding, 2-53 modifying, 2-54 two alarms, example, 2-56 alarm acknowledging, 2-33 auto acknowledgement, 2-48 categories, 2-6 correlation analysis principle, 2-51 levels, 2-5 monitoring, 2-14 notification methods, 2-40 Pop-Up pane, 3-57 status, 2-5 types, 2-8 alarm board introduction, 2-40 setting, 2-41 alarm data
Issue 06 (2008-12-16)
printing, 2-27 saving, 2-26 alarm query result printing, 2-27 saving, 2-26 alarm statistic result printing, 2-27 saving, 2-26 alarm-related fault removing, 2-33 audit result of dual-homing data saving, 11-7 automatically searching for sub-NEs of IMSOMU, 3-24 automatically upgrading client software, 1-8
B
blocking cell, 2-123 broadcasting sending, 1-21 browsing monitoring panel, 2-120 NodeB plan upgrade task, 8-20 scheduled upgrade, 8-20
C
cell alarm checking, 2-132 viewing, 2-132 cell monitoring counter checking, 2-131 viewing, 2-131 changing password, 1-9 check result of dual-homing data saving, 11-7, 11-7 checking alarm information on specified link of Iu interface, 2-131 on specified link of Iur interface, 2-131 alarm information on specified link of Iub interface, 2-131
i-1
Index
basic cell configuration, 2-128 basic NodeB configuration information, 2-127 basic RNC configuration information, 2-124 basis RNC configuration, 2-124 CCH configuration, 2-128 cell alarm, 2-132 cell distribution on RNC, 2-125 cell exceptional counter, 2-122 cell monitoring counter, 2-131 cell neighboring relation, 2-129 client, upgrade, 1-7 configuration status, 2-121 detail information of configuration status, 2-121 detail information of exceptional counter, 2-122 detailed alarm information, 2-121 E1 status of RNC, 2-130 E1T1 status of RNC, 2-130 information on specified link of Iub interface, 2-127 Iu interface link alarm information, 2-131 Iub interface link alarm information, 2-131 Iur interface link alarm information, 2-131 monitored object group exception, 2-118 monitoring counter chart, 2-122 monitoring object group parameter, 2-115 neighbor information, 2-129 NodeB distribution on RNC, 2-125 RNC exceptional counter, 2-122 RNC Iu interface, 2-125 RNC Iub interface, 2-126 RNC Iur interface, 2-125 RNC monitoring counter, 2-130 specified link of Iu interface, 2-126 specified link of Iur interface, 2-126 T1 status of RNC, 2-130 update interval, 1-8 clearing alarm, 2-34 history command, 9-12 CME upload creating, 14-18 common option interface organization tree tab, 1-36 others tab, 1-36 status table tab, 1-36 time parameter tab, 1-36 parameter organization tree tab, 1-45 others tab, 1-45 status table tab, 1-45 time parameter tab, 1-45 setting, 1-17 compare rights, 4-38 confirming NE software patch AG, 8-51 ASN-GW, 8-69
i-2
BSC, 8-59 GGSN, 8-39 MSC Server, 8-43 RNC, 8-27 SGSN, 8-33 consistency check window setting, 11-6 copying monitored object group, 2-116 correlation advanced, 2-51 simple, 2-51 counter threshold activating, 6-47 deactivating, 6-47 modifying, 6-46 creating CME upload, 14-18 local network domain, 11-12 SNMP parameter template, 3-32 user account, 4-22 user group, 4-19 customizing client GUI style common option, 1-17 measurement, 1-16
D
data backup modifying, 14-52 data check interface setting, 11-6 database threshold, 2-142 deactivating counter threshold, 6-47 NE software patch AG, 8-51 ASN-GW, 8-70 BSC, 8-59 MSC Server, 8-44 RNC, 8-27 default layout, 3-55 deleting alarm filter condition, 2-48 local network domain, 11-15 monitored object group, 2-118 physical link, 3-50 severity redefinition, 2-50 SNMP parameter template, 3-33 detailed alarm information checking, 2-121 viewing, 2-121 displaying measurement result in table, 6-28 monitoring result, 2-99 displaying measurement result
Issue 06 (2008-12-16)
Index
in bar chart, 6-29 in line chart, 6-28 domain adding, 11-16 downloading NE mediation data, 1-23 NE software BSC, 8-56 dual-homing, 11-2 dual-homing data synchronizing, 11-10
E
equipment management, 16-3 example a single alarm, advanced correlation rule , 2-55 alarm handling, 2-37 simple correlation rules of alarms, 2-54 two alarms, advanced correlation rule, 2-56 exiting client, 1-7 exported file managing, 1-24 exporting measurement object, 6-36 measurement setting, 6-37 NE measurement state, 6-18 plan upgrade task, 8-21 scheduled upgrade, 8-21 type 3 object template, 6-12
service not running, 17-6 unselect multiple node, 17-13 user account locked, 17-6 wrong user name, 17-3 wrong user password, 17-3 fault alarms status, 2-21 forcing user exiting, 4-48 format date, 1-15 time, 1-14 function alarm management, 2-3
G
granting rights over new NEs to an OM user group, 4-20 rights, OM user, 4-24 rights, user group, 4-20
H
hiding navigation tree of topology view, 3-52 hierarchical, 3-55 history command clearing, 9-12
I
importing measurement object data, 6-36 plan upgrade task, 8-20 scheduled upgrade, 8-20 type 3 object, 6-12 instance area-based privilege configuration, 11-16 interface M2000 client interface, 1-28 monitoring panel, 2-165 performance management common option, 1-36 inventory data manually exporting, 9-25
F
faq attribute value name already exist, 17-11 automatic NodeB search failure, 17-11 cannot discover NodeB automatically, 17-11 cannot receive alarm notification by SMS, 17-13 cannot refresh topology view, 17-10 client abnormality, 17-9 client cannot start, 17-8 client cannot work, 17-8 client interface abnormal, 17-9 exceed maximum session, 17-7 invalid login duration, 17-4 invalid password, 17-5 invalid user account, 17-4 loading module failure, 17-7 maintenance mode, 17-5 maximum login attempt, 17-6 password expire, 17-5 real-time print delay, 17-12 receiving alarm notification failure, 17-13 refreshing topology view failure, 17-10 running client failure, 17-8 select multiple node, 17-13 server exist failure, 17-6
L
level redefinition adding, 2-49 license information viewing, 1-22 link deleting, 3-50 LMT setting prompt, 1-21 LMT client logging, 11-16 loading
i-3
Issue 06 (2008-12-16)
Index
NE software AG, 8-47 ASN-GW, 8-67 NE software patch AG, 8-49 ASN-GW, 8-68 BSC, 8-57 local network, 11-3 local network domain, 11-3 creating, 11-12 deleting, 11-15 managing user, 11-12 local network resource managing, 11-12 locating alarm, 2-13 locking client automatically, 1-18 manually, 1-18 log type, 5-2 log query result printing, 5-12 logging LMT client, 11-16 logging in, 1-3 logging in to M2000 server automatically upgrading client software, 1-8 logging out, 1-6
M
maintenance experience exporting, 2-35 importing, 2-36 Management Information Tree, 9-3 managing exported file, 1-24 local network resource, 11-12 result query template directory, 6-33 user in local network domain, 11-12 manually exporting inventory data, 9-25 matrix layout, 3-55 measurement counter querying, 6-35 measurement object exporting, 6-36 importing data, 6-36 modifying memo, 6-38 modifying remark, 6-38 measurement result displaying in table, 6-28 querying reliability, 6-14 measurement setting exporting, 6-37 measuring NodeB alarm by alarm ID, 2-139 measuring RNC alarm
i-4
by alarm ID, 2-134 by alarm level, 2-133 by alarm severity, 2-133 by cell, 2-136 by E1 link, 2-137 by NodeB, 2-135 by SAAL link, 2-136 by T1 link, 2-137 mesuring NodeB alarm by alarm level, 2-138 by alarm severity, 2-138 MIT, 9-3 MML command result viewing, 9-9 Modify password of an NE user, 4-41 modifying alarm acknowledgement, 14-53 alarm data export, 14-44 alarm filter conditions, 2-47 alarm timing acknowledgement, 14-53 basic attribute subnet, 3-45 counter threshold, 6-46 inventory data export, 14-50 measurement object memo, 6-38 measurement object remark, 6-38 monitoring object group parameter, 2-115 NE operation log export, 14-49 NE security log export, 14-49 object group name, 2-116 physical link, 3-47 result query template, 6-32 security log export, 14-48 server backup, 14-52 severity redefinition, 2-50 SNMP parameter template, 3-32 software download, 14-26 system data backup, 14-52 system log export, 14-47 virtual link, 3-48 monitored object group adding, 2-114 checking exception, 2-118 copying, 2-116 deleting, 2-118 monitoring database status, 2-144 hard disk status, 2-143 measurement result integrity, 6-16 NE status, 3-33 OM user operations, 4-46 performance status, 2-143 process status, 2-145 service status, 2-145 through topology view, 2-13 monitoring chart printing, 2-107
Issue 06 (2008-12-16)
Index
saving, 2-106 setting threshold, 2-102 showing scale, 2-103 zoom in, 2-101 zoom out, 2-101 monitoring counter chart checking, 2-122 viewing, 2-122 monitoring data synchronizing, 2-95 monitoring management, 16-3 monitoring object querying, 2-120 searching, 2-120 monitoring object group checking parameter, 2-115 modifying parameter, 2-115 monitoring parameter database, 2-142 hard disk, 2-142 performance, 2-141 service, 2-143 monitoring table saving, 2-106 setting threshold, 2-100 monitoring table filtering condition setting, 2-100 multi-area network, 11-3 area-based privilege management, 11-16
N
creating virtual NE, 3-7 deleting, 3-49 NE maintenance enhanced version upgrading, 16-2 NE measurement state exporting, 6-18 viewing, 6-18 NE report querying, 9-16 viewing, 9-16 NE software, 8-2 AG, 8-47 activating, 8-48 loading, 8-47 synchronizing, 8-49 ASN-GW, 8-66 activating, 8-67 loading, 8-67 BSC, 8-56 downloading, 8-56 SGSN synchronizing, 8-32 NE software patch AG, 8-47 activating, 8-50
Issue 06 (2008-12-16)
NE
confirming, 8-51 deactivating, 8-51 loading, 8-49 removing, 8-52 ASN-GW, 8-66 activating, 8-69 confirming, 8-69 deactivating, 8-70 loading, 8-68 removing, 8-70 BSC, 8-56 activating, 8-58 confirming, 8-59 deactivating, 8-59 loading, 8-57 removing, 8-60 rollbacking, 8-60 GGSN confirming, 8-39 MSC Server confirming, 8-43 deactivating, 8-44 upgrading, 8-41 RNC confirming, 8-27 deactivating, 8-27 SGSN confirming, 8-33 state, 8-3 NE statistic report viewing, 9-16 NE version viewing, 9-16 new alarm, displaying location, 2-37 number, display mode, 1-16
O
OM user managed domain, 4-24 modifying information, 4-36 Operation alarm alarm sound, 2-42
P
parameter alarm statistics setting, 2-226 alarm time acknowledgement, 14-78 analyzing monitoring counter trend, 2-222 backing up NM file, 10-21 batch creating physical NE, 3-80 CCH configuration, 2-236 cell common channel basic configuration, 2-236 cell configuration status, 2-235
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i-5
Index
cell distribution on RNC, 2-232 cell monitoring counter, 2-242 checking distribution cell, 2-232 NodeB, 2-232 checking E1 status of RNC, 2-232 checking information on basic NodeB configuration, 2-233 on basic RNC configuration, 2-229 on CCH configuration, 2-236 on Iu of RNC, 2-229 on Iub interface of RNC, 2-230 on Iur of RNC, 2-229 on specified link of Iu interface, 2-230 on specified link of Iub interface, 2-231 on specified link of Iur interface, 2-230 checking monitoring counter value cell, 2-242 RNC, 2-228 checking T1 status of RNC, 2-232 CME download task, 14-76 CME download task common information, 14-71 CME upload task, 14-75 common information, 14-69 configuration status, 2-235 copying CME upload, 14-75 copying common information, 14-69 copying HSL script, 14-77 copying scheduled task time setting, 14-71 counter filter condition, 6-54 creating IP device, 3-72 creating CME download, 14-76 creating CME upload, 14-75 creating common information, 14-69 creating HSL script, 14-77 creating scheduled task time setting, 14-71 creating software download, 14-74 E1T1 status of RNC, 2-232 exporting .ini template, 3-78 exporting alarm data, 14-80 exporting inventory data, 14-85 exporting NE log, 14-83 exporting operation log, 14-83 HSL script, 14-77 inventory data synchronization, 14-76 Iu interface link, 2-230 Iu interface of RNC, 2-229 Iub interface link, 2-231 Iub interface of RNC, 2-230 Iur interface link, 2-230 Iur interface of RNC, 2-229 license information tab, 1-44 measurement result reliability, 6-55 missing measurement result, 6-55 modifying subnet basic attribute, 3-81
i-6
modifying alarm data export, 14-80 modifying alarm timing acknowledgement, 14-78 modifying CME download, 14-76 modifying CME upload, 14-75 modifying HSL script, 14-77 modifying inventory data export, 14-85 modifying inventory data synchronization, 14-76 modifying M2000 data backup, 14-85 modifying NE alarm level, 2-192 modifying NE configuration data synchronization, 14-75 modifying NE log export, 14-83 modifying operation log export, 14-83 modifying software download, 14-74 monitor chart threshold, 2-225 monitoring chart background color, 2-222 monitoring chart property, 2-223 monitoring counter trend, 2-222 monitoring table filtering condition, 2-223 monitoring table threshold, 2-225 monitoring threshold rule, 2-224 NE configuration data synchronization, 14-75 NE measurement result, 6-56 NE operation log information, 5-24 statistic, 5-31 NE security log information, 5-25 statistic, 5-32 NE software patch RNC, 8-99 NM backup file, 10-21 NodeB basic configuration, 2-233 NodeB configuration status, 2-235 NodeB distribution on RNC, 2-232 NodeB license information, 8-105 performance management common option, 1-45 periodic task time setting, 14-71 printing topology view, 3-82 query alarm level redefinition, 2-193 querying measurement result reliability, 6-55 missing measurement result, 6-55 querying NE alarm level redefinition, 2-193 querying NE operation log, 5-36 querying NE operation log result, 5-24 querying NE resource report, 9-79 querying NE resource status, 9-79 querying NE security log, 5-37 querying NE security log result, 5-25 real-time monitoring NE resource state, 9-76 redefining NE alarm level, 2-192 RNC basic configuration, 2-229 RNC configuration status, 2-235 RNC KPI counter, 2-228 RNC license information, 8-105 scheduled task time setting, 14-71
Issue 06 (2008-12-16)
Index
searching monitored object, 2-242 select NE, 2-179 selecting NE, 2-179 server backup, 14-85 setting counter filter condition, 6-54 file transfer, 8-106 monitor chart threshold, 2-225 monitoring chart background color, 2-222 monitoring chart property, 2-223 monitoring table filtering condition, 2-223 monitoring table threshold, 2-225 monitoring threshold rule, 2-224 sorting displayed result mode, 6-56 specified result time range, 6-61 setting alarm interface column, 2-167 setting CME download task common information, 14-71 SNMP parameter template, 3-84 software download task, 14-74 sorting displayed result mode, 6-56 specifying result time range, 6-61 summarizing NodeB alarm, 2-226 summarizing RNC alarm, 2-226 synchronizing NE measurement result, 6-56 upgrading NE software NodeB, 8-103 viewing subnet basic attribute, 3-81 viewing NE resource report, 9-79 viewing NE resource status, 9-79 viewing NE statistic report, 9-79 viewing NM license information, 1-44 performance measurement function set, 6-5 function subset, 6-5 printing result, 6-31 specifying result period, 6-25 physical link deleting, 3-50 modifying, 3-47 viewing, 3-47 physical subnet creating, 3-6 physical topology design, 3-5 plan upgrade task exporting, 8-21 importing, 8-20 policy account, 4-8 auto processing, 2-39 password, 4-7 system, 4-8 printing alarm data, 2-27 alarm query result, 2-27 alarm statistic result, 2-27
Issue 06 (2008-12-16)
log query result, 5-12 monitoring chart, 2-107 performance measurement result, 6-31 topology view, 3-59 priority, correlation analysis, 2-52 procedure alarm reporting, 2-9
Q
querying alarm details, 2-33 authorization, 4-38 current alarms, 2-15, 2-31 event alarms, 2-17 historical measurement result integrity, 6-17 history fault alarms, 2-17 masked event alarms, 2-20 masked fault alarms, 2-19 measurement counter, 6-35 measurement result reliability, 6-14 monitoring object, 2-120 NE report, 9-16 operation log, 5-8 security log, 5-10 system log, 5-9 querying measurement result by new condition, 6-21 by template, 6-20
R
radial tree layout, 3-55 re-querying result, 6-22 real-time performance monitoring, 16-4 recording, alarm handling experience, 2-35 relation, threshold and alarms, 2-141 remote notification parameters, 2-45 rule, 2-44 removing alarm-related fault, 2-33 NE software patch AG, 8-52 ASN-GW, 8-70 BSC, 8-60 resetting password, 4-36 result query template adding, 6-31 managing directory, 6-33 modifying, 6-32 resuming timing task, 14-57 rollbacking NE software patch BSC, 8-60
i-7
Index
S
saving alarm data, 2-26 alarm query result, 2-26 alarm statistic result, 2-26 audit result of dual-homing data, 11-7 monitoring chart, 2-106 monitoring table, 2-106 scanning correlated monitoring counter value, 2-105 scheduled upgrade browsing, 8-20 exporting, 8-21 importing, 8-20 searching monitoring object, 2-120 server backup modifying, 14-52 setting alarm box, 2-42 alarm color, 2-43 alarm highlight, 2-44 alarm interface column, 2-11 chart background color, 6-30 consistency check window, 11-6 data check interface, 11-6 disconnect, alarm sound, 1-20 display effect of topology icons, 1-12 file transferring parameter, 8-15 filtering result counter condition, 6-26 LMT prompt, 1-21 monitoring chart attribute, 2-101 monitoring chart background color, 2-103 monitoring chart background picture, 2-102 monitoring chart curve color, 2-103 monitoring chart property, 2-101 monitoring chart threshold, 2-102 monitoring table filtering condition, 2-100 monitoring table threshold, 2-100 monitoring threshold filtering rule, 2-97 monitoring threshold rule, 2-97 output information, 1-11 performance management common option, 1-17 running mode of system multi-user mode, 1-19 single-user mode, 1-19 single-user mode, 4-9 sorting displayed result mode, 6-26 user group, managed domain, 4-19 setting layout, 3-55 Setting shortcut buttons, 1-12 setting topology background, 3-5 severity redefinition deleting, 2-50 modifying, 2-50 showing
i-8
monitoring chart scale, 2-103 navigation tree of topology view, 3-52 simple correlation rule adding, 2-52 modifying, 2-54 SNMP parameter template creating, 3-32 deleting, 3-33 modifying, 3-32 software download modifying, 14-26 software management file type, 8-4 specifying queried object, 6-24 result measurement function set, 6-23 function subset, 6-23 result measurement period, 6-25 result time range, 6-25 statistics event alarms, 2-25 fault alarms, 2-24 operation log, 5-14 security log, 5-15 system log, 5-14 status event alarms, 2-22 fault alarms, 2-21 Subnet Deleting Subnets, 3-48 summarizing NodeB alarm by alarm ID, 2-139 by alarm level, 2-138 by alarm severity, 2-138 summarizing RNC alarm by alarm ID, 2-134 by alarm level, 2-133 by alarm severity, 2-133 by cell, 2-136 by E1 link, 2-137 by NodeB, 2-135 by SAAL link, 2-136 by T1 link, 2-137 switching current subnet, 3-53 synchronizing dual-homing data, 11-10 monitoring data, 2-95 NE software AG, 8-49 SGSN, 8-32
T
template alarm query, 2-23 alarm statistics, 2-26
Issue 06 (2008-12-16)
Index
log query, 5-8 log statistics, 5-13 time format, 1-14 mode, 1-15 timing task resuming, 14-57 topology object searching, 3-36 topology view adjusting, 3-54 alarm display, 3-53 filter condition, 3-54 hiding navigation tree, 3-52 printing, 3-59 refreshing, 3-51 showing navigation tree, 3-52 tracing management, 16-3 transferring file NE to NM, 8-12 NM to client, 8-9 NM to NE, 8-10 setting parameter, 8-15 tree layout, 3-55 type 3 object exporting template, 6-12 importing, 6-12
information on specified link of Iub interface, 2-127 MML command result, 9-9 monitoring counter chart, 2-122 monitoring panel, 2-120 monitoring service, 2-115 NE file information, 8-9 NE measurement state, 6-18 NE report, 9-16 NE statistic report, 9-16 NE version, 9-16 NM license information, 1-22 NodeB distribution on RNC, 2-125 physical link, 3-47 resource key, 1-22 RNC Iu interface, 2-125 RNC Iub interface, 2-126 RNC Iur interface, 2-125 RNC monitoring counter, 2-130 specified link of Iu interface, 2-126 specified link of Iur interface, 2-126 virtual link, 3-48 viewing topology overview, 3-55 virtual link creating, 3-9 modifying, 3-48 viewing, 3-48
U
unblocking cell, 2-123 unlocking user, 4-49 unlocking client, 1-18 upgrading NE maintenance enhanced version, 16-2 NE software patch MSC Server, 8-41 user in local network domain managing, 11-12 user mode, 4-9
W
WRAN configured object model, 2-108
Z
zoom in monitoring chart, 2-101 zoom out monitoring chart, 2-101 zooming in, 3-54 zooming out, 3-54
V
version, 8-2 viewing basic attribute subnet, 3-45 basic cell configuration, 2-128 basic NodeB configuration, 2-127 cell alarm, 2-132 cell distribution on RNC, 2-125 cell monitoring counter, 2-131 configuration status, 2-121 detail information of configuration status, 2-121 detailed alarm information, 2-121 exported file, 1-24 function key, 1-22
Issue 06 (2008-12-16) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i-9

00366248-M2000 Operator Guide (V200R006 - 06)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

00366248-M2000 Operator Guide (V200R006 - 06)

Enviado por

Direitos autorais:

Formatos disponíveis

M2000 V200R006

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

M2000 Operator Guide

2 Network Monitoring................................................................................................................. 2-1

M2000 Operator Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

M2000 Operator Guide

M2000 Operator Guide

M2000 Operator Guide

7 Performance Report Management..........................................................................................7-1

M2000 Operator Guide 7.2.11 Managing a Custom Performance Report Template..........................................................................7-15

M2000 Operator Guide

M2000 Operator Guide

11 Dual-Homing and LN Domain Management...................................................................11-1

M2000 Operator Guide

12 MSC Pool Management........................................................................................................12-1

M2000 Operator Guide 12.5.2 Checking MSC Pool Data................................................................................................................12-54

13 CDMA Pool Management....................................................................................................13-1

M2000 Operator Guide

14 Integrated Task Management..............................................................................................14-1

M2000 Operator Guide

16 NE Maintenance Enhanced Management.........................................................................16-1

M2000 Operator Guide

18 Terms, Acronyms, and Abbreviations...............................................................................18-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

M2000 Operator Guide Figure 2-28 System Monitor Browser interface...............................................................................................2-166

M2000 Operator Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

About This Document

About This Document

Network administrator Shift operator

Update History 06(2008-12-16)

About This Document

M2000 Operator Guide

Context Data Management Monitoring NE Performance in Real Time Performance Management

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide

About This Document

About This Document

M2000 Operator Guide

M2000 Operator Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

M2000 Operator Guide

M2000 Operator Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Operator Guide