huawei LMT guide

RNC V200R011

LMT User Guide

Issue

03

Date

2009-04-25

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

Website:

http://www.huawei.com

Email:

[email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. 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.


RNC LMT User Guide

Contents

Contents About This Document.....................................................................................................................1 1 Changes in RNC LMT User Guide.........................................................................................1-1 2 Introduction to the RNC LMT.................................................................................................2-1 2.1 Definitions of the LMT...................................................................................................................................2-2 2.2 Functions of the RNC LMT............................................................................................................................2-2 2.3 RNC OM Networking.....................................................................................................................................2-2 2.4 Computer Requirements of the LMT..............................................................................................................2-3

3 Components of the RNC LMT.................................................................................................3-1 3.1 Local Maintenance Terminal of RNC.............................................................................................................3-3 3.2 FTP Client of RNC LMT................................................................................................................................3-5 3.3 Trace Viewer of RNC LMT............................................................................................................................3-6 3.4 Monitor Viewer of RNC LMT........................................................................................................................3-7 3.5 Performance Browser Tool of RNC LMT......................................................................................................3-9 3.6 Convert Management System of RNC LMT................................................................................................3-10

4 Installing the RNC LMT Application....................................................................................4-1 5 Getting Started with the RNC LMT.......................................................................................5-1 5.1 Setting the IP Address of the RNC LMT PC..................................................................................................5-3 5.2 Connecting the RNC LMT to the BAM..........................................................................................................5-5 5.3 Starting the Local Maintenance Terminal of the RNC....................................................................................5-6 5.4 Setting the Properties of the RNC Local Maintenance Terminal....................................................................5-9 5.5 Configuring the Identity Certificate..............................................................................................................5-10 5.6 Setting the Office Information on the RNC LMT.........................................................................................5-12 5.7 Locking the Local Maintenance Terminal of the RNC.................................................................................5-16 5.8 Unlocking the Local Maintenance Terminal of the RNC.............................................................................5-17 5.9 Exiting the Local Maintenance Terminal of the RNC..................................................................................5-17

6 Running RNC MML Commands............................................................................................6-1 6.1 Concepts of RNC MML Commands...............................................................................................................6-3 6.1.1 Introduction to RNC MML Commands.................................................................................................6-3 6.1.2 Introduction to the RNC MML Client....................................................................................................6-5 6.1.3 Policies for RNC Configuration Failure Handling.................................................................................6-6 6.1.4 RNC Data Configuration Right Management........................................................................................6-7 Issue 03 (2009-04-25)


i

RNC LMT User Guide

Contents

6.1.5 RNC Data Configuration Rollback........................................................................................................6-7 6.2 Starting the RNC MML Client........................................................................................................................6-8 6.3 Viewing the Ownership of RNC Data Configuration Right...........................................................................6-8 6.4 Obtaining the RNC Data Configuration Right................................................................................................6-9 6.5 Running a Single MML Command...............................................................................................................6-10 6.6 Batch Running MML Commands.................................................................................................................6-11 6.7 Undoing a Single RNC Data Configuration Action......................................................................................6-13 6.8 Redoing a Single RNC Data Configuration Action......................................................................................6-14 6.9 Undoing Multiple RNC Data Configuration Actions...................................................................................6-14 6.10 Redoing Multiple RNC Data Configuration Actions..................................................................................6-15

7 Managing Authorities for RNC Operations......................................................................... 7-1 7.1 Concepts of RNC Authority Management......................................................................................................7-2 7.1.1 Principles of RNC Authority Management............................................................................................7-2 7.1.2 RNC LMT Operator Password ..............................................................................................................7-2 7.1.3 RNC Command Groups.........................................................................................................................7-3 7.1.4 RNC LMT User Types...........................................................................................................................7-4 7.1.5 RNC LMT Operator Authorities............................................................................................................7-4 7.1.6 RNC LMT Operating Time Limits........................................................................................................7-5 7.2 Managing RNC LMT Operator Accounts.......................................................................................................7-6 7.2.1 Adding an RNC LMT External Operator Account................................................................................7-6 7.2.2 Modifying the Properties of an RNC LMT External Operator Account................................................7-8 7.2.3 Deleting an RNC LMT External Operator Account..............................................................................7-9 7.3 Managing RNC LMT Operator Passwords...................................................................................................7-10 7.3.1 Defining Policies for RNC LMT Login Passwords.............................................................................7-11 7.3.2 Querying Policies for RNC LMT Login Passwords............................................................................7-12 7.3.3 Changing the Password of the Active RNC LMT Operator Account..................................................7-12 7.3.4 Changing the Password of an RNC LMT External Operator Account................................................7-13 7.4 Managing RNC Command Groups...............................................................................................................7-14 7.4.1 Querying RNC Command Groups.......................................................................................................7-14 7.4.2 Renaming an RNC Command Group...................................................................................................7-14 7.4.3 Changing Commands in an RNC Command Group............................................................................7-15

8 Managing the RNC License..................................................................................................... 8-1 8.1 Basic Concepts of the RNC License...............................................................................................................8-2 8.1.1 License File............................................................................................................................................8-2 8.1.2 License Control for Multiple Operators.................................................................................................8-3 8.1.3 License Validation Mechanism..............................................................................................................8-5 8.2 Activating the RNC License...........................................................................................................................8-7 8.2.1 Obtaining ESN Information from the RNC...........................................................................................8-7 8.2.2 Uploading the RNC License File to the BAM.......................................................................................8-8 8.2.3 Checking RNC Basic Information and Operator Information...............................................................8-9 8.2.4 Activating and Verifying the RNC License.........................................................................................8-10 8.3 Reallocating the RNC License......................................................................................................................8-11 ii


Issue 03 (2009-04-25)

RNC LMT User Guide

Contents

8.4 Checking RNC Current User Number/Throughput......................................................................................8-12

9 Managing RNC Alarms.............................................................................................................9-1 9.1 Concepts of RNC Alarm Management...........................................................................................................9-2 9.1.1 RNC Alarm Type...................................................................................................................................9-2 9.1.2 RNC Alarm Level..................................................................................................................................9-3 9.1.3 RNC Event Alarm Types.......................................................................................................................9-3 9.1.4 RNC Alarm Box.....................................................................................................................................9-4 9.2 Setting RNC Alarm Logs................................................................................................................................9-4 9.2.1 Setting the Capacity and Time Limit of an RNC Alarm Log................................................................9-5 9.2.2 Querying the Capacity and Time Limit of an RNC Alarm Log.............................................................9-5 9.3 Masking RNC Alarms.....................................................................................................................................9-5 9.3.1 Adding an RNC Alarm Shield...............................................................................................................9-6 9.3.2 Deleting an RNC Alarm Shield..............................................................................................................9-6 9.3.3 Querying RNC Alarm Shields................................................................................................................9-7 9.4 Masking RNC Derived Alarms.......................................................................................................................9-7 9.4.1 Setting the Mask Level of an RNC Derived Alarm...............................................................................9-8 9.4.2 Querying the Mask Level of an RNC Derived Alarm............................................................................9-8 9.5 Monitoring RNC Alarms.................................................................................................................................9-8 9.5.1 Setting the Properties of the Alarm Browse Window............................................................................9-9 9.5.2 Setting the Properties of RNC Fault Alarm Sounds.............................................................................9-10 9.5.3 Browsing Alarms..................................................................................................................................9-11 9.5.4 Querying RNC Alarm Logs.................................................................................................................9-12 9.5.5 Querying RNC Alarm Handling Suggestions......................................................................................9-14 9.5.6 Manually Setting a Cleared RNC Alarm..............................................................................................9-16 9.5.7 Saving the Information on an RNC Alarm...........................................................................................9-16 9.5.8 Setting the Preferences for Printing RNC Alarms in Real Time..........................................................9-17 9.5.9 Manually Printing RNC Alarms...........................................................................................................9-18 9.6 Managing the Convert Management System................................................................................................9-19 9.6.1 Starting the RNC Convert Management System..................................................................................9-20 9.6.2 Setting the Parameters of the RNC Convert Management System......................................................9-20 9.6.3 Saving the Information in the Output Window....................................................................................9-21 9.6.4 Exiting the RNC Convert Management System..................................................................................9-22 9.7 Operating the RNC Alarm Box.....................................................................................................................9-22 9.7.1 Connecting the RNC Alarm Box to the RNC LMT.............................................................................9-23 9.7.2 Resetting the RNC Alarm Box.............................................................................................................9-24 9.7.3 Stopping an RNC Alarm Sound...........................................................................................................9-25 9.7.4 Manually Turning Off an RNC Alarm Light.......................................................................................9-26 9.7.5 Querying the Version of the RNC Alarm Box.....................................................................................9-27 9.7.6 Querying the State of an RNC Alarm Light.........................................................................................9-27 9.7.7 Setting the Shield Severity of the RNC Alarm Box.............................................................................9-28 9.7.8 Querying the Mask Level of the RNC Alarm Box...............................................................................9-28

10 Managing RNC Logs.............................................................................................................10-1 Issue 03 (2009-04-25)


iii

RNC LMT User Guide

Contents

10.1 Concepts of RNC Log Management...........................................................................................................10-3 10.1.1 RNC Log Types.................................................................................................................................10-3 10.1.2 RNC Log Management Authority......................................................................................................10-3 10.2 Setting the Time and Count Limits of the RNC Log..................................................................................10-3 10.3 Querying the Time and Count Limits of the RNC Log...............................................................................10-4 10.4 Querying an RNC Operation Log...............................................................................................................10-4 10.5 Exporting an RNC Operation Log..............................................................................................................10-5 10.6 Querying RNC Security Logs.....................................................................................................................10-6 10.7 Exporting an RNC Security Log.................................................................................................................10-7 10.8 Exporting an RNC Running Log.................................................................................................................10-8 10.9 Collecting Fault Log Information...............................................................................................................10-9

11 Managing the RNC Equipment by Using the Device Panel and Display Panel.......11-1 11.1 Using the RNC Device Panel......................................................................................................................11-2 11.1.1 Introduction to the RNC Device Panel...............................................................................................11-2 11.1.2 Starting the RNC Device Panel..........................................................................................................11-3 11.1.3 Showing or Hiding the Legend on the RNC Device Panel................................................................11-4 11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel..........................................................11-6 11.1.5 Browsing the Status of an RNC Board...............................................................................................11-7 11.1.6 Querying the Detailed Status of an RNC Board................................................................................11-8 11.1.7 Querying the CPU/DSP Usage of an RNC Board..............................................................................11-9 11.2 Using the RNC Display Panel...................................................................................................................11-10 11.2.1 Introduction to the RNC Display Panel............................................................................................11-11 11.2.2 Starting the RNC Display Panel.......................................................................................................11-12 11.2.3 Querying the Status of FE Ports on an RNC Board.........................................................................11-13 11.2.4 Querying the Status of GE Ports on an RNC Board........................................................................11-14 11.2.5 Querying the Detailed Status of a DSP on the DPUb Board...........................................................11-15 11.2.6 Querying the Detailed Status of an E1/T1 Link...............................................................................11-16 11.2.7 Querying Alarms through a Board Alarm Light..............................................................................11-17 11.3 Viewing Active Alarms of an RNC Board................................................................................................11-17 11.4 Querying the Configuration Mode of a Subrack.......................................................................................11-18

12 Tracing and Viewing RNC Messages................................................................................12-1 12.1 Concepts of RNC Message Tracing Management......................................................................................12-4 12.1.1 Functions of RNC Message Tracing Management............................................................................12-4 12.1.2 Working Principles of RNC Message Tracing Management.............................................................12-4 12.1.3 Authority of RNC Message Tracing Management............................................................................12-5 12.2 Tracing Iu Interface Messages....................................................................................................................12-6 12.3 Tracing Iur Interface Messages...................................................................................................................12-9 12.4 Tracing Iub Interface Messages................................................................................................................12-12 12.5 Tracing Uu Interface Messages.................................................................................................................12-14 12.6 Tracing UE Messages................................................................................................................................12-17 12.7 Tracing IOS Messages..............................................................................................................................12-20 12.8 Tracing Cell Messages..............................................................................................................................12-21 iv


Issue 03 (2009-04-25)

RNC LMT User Guide

Contents

12.9 Tracing REDIRECT Messages.................................................................................................................12-22 12.10 Tracing MNCDT Messages....................................................................................................................12-25 12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells.................................................12-26 12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells.................................................12-27 12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells..........................................................12-28 12.11 Tracing OS Messages..............................................................................................................................12-29 12.12 Tracing SCCP Messages.........................................................................................................................12-30 12.13 Tracing MTP3 Messages.........................................................................................................................12-32 12.14 Tracing QAAL2 Messages......................................................................................................................12-35 12.15 Tracing SAAL Messages........................................................................................................................12-36 12.16 Tracing SCTP Messages.........................................................................................................................12-38 12.17 Tracing M3UA Messages........................................................................................................................12-41 12.18 Tracing Location Messages.....................................................................................................................12-42 12.19 Basic Operations of RNC Message Tracing...........................................................................................12-43 12.19.1 Browsing an RNC Traced Message Online...................................................................................12-44 12.19.2 Querying the Properties of the Tracing Task.................................................................................12-45 12.19.3 Viewing a Message Translation.....................................................................................................12-46 12.19.4 Saving an RNC Traced Message....................................................................................................12-46 12.19.5 Pausing an RNC Tracing Task.......................................................................................................12-48 12.19.6 Resuming an RNC Tracing Task...................................................................................................12-48 12.19.7 Closing an RNC Tracing Task.......................................................................................................12-49 12.19.8 Browsing an RNC Traced Message Offline...................................................................................12-50 12.19.9 Managing All Tracing Tasks..........................................................................................................12-53 12.20 Parameter Reference for RNC Message Tracing and Viewing...............................................................12-54 12.20.1 Parameter Reference for Iu Interface Tracing................................................................................12-54 12.20.2 Parameter Reference for Iur Interface Tracing...............................................................................12-56 12.20.3 Parameter Reference for Iub Interface Tracing..............................................................................12-57 12.20.4 Parameter Reference for Uu Interface Tracing..............................................................................12-59 12.20.5 Parameter Reference for UE Tracing.............................................................................................12-59 12.20.6 Parameter Reference for IOS Tracing............................................................................................12-60 12.20.7 Parameter Reference for Cell Tracing............................................................................................12-61 12.20.8 Parameter Reference for REDIRECT Tracing...............................................................................12-62 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing.........................................................12-62 12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing.......................................................12-63 12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing................................................................12-64 12.20.12 Parameter Reference for OS Tracing...........................................................................................12-65 12.20.13 Paramter Reference for Location Reporting Control...................................................................12-66

13 RNC Real-Time Performance Monitoring........................................................................13-1 13.1 Concepts of RNC Real-Time Performance Monitoring..............................................................................13-3 13.1.1 Introduction to RNC Real-Time Performance Monitoring................................................................13-3 13.1.2 Working Principles of RNC Real-Time Performance Monitoring....................................................13-3 13.1.3 Authority of the RNC Real-Time Performance Monitoring..............................................................13-5 Issue 03 (2009-04-25)


v

RNC LMT User Guide

Contents

13.2 Monitoring the RNC CPU/DSP Occupancy...............................................................................................13-5 13.3 Monitoring the RNC Connection Performance...........................................................................................13-8 13.3.1 Monitoring P-CPICH Ec/No and RSCP...........................................................................................13-10 13.3.2 Monitoring the SIR Measurement Values of UL RLSs...................................................................13-12 13.3.3 Monitoring the Enhanced Outer Loop Power Control.....................................................................13-14 13.3.4 Monitoring the SIR Error Values of UL RLSs................................................................................13-16 13.3.5 Monitoring DL Code TX Power......................................................................................................13-17 13.3.6 Monitoring the UE TX Power..........................................................................................................13-19 13.3.7 Monitoring UL Traffic.....................................................................................................................13-20 13.3.8 Monitoring DL Traffic.....................................................................................................................13-22 13.3.9 Monitoring UL Throughput and Bandwidth....................................................................................13-24 13.3.10 Monitoring DL Throughput and Bandwidth..................................................................................13-25 13.3.11 Monitoring Handover Delay..........................................................................................................13-27 13.3.12 Monitoring the BLER of the DL Transport Channel.....................................................................13-28 13.3.13 Monitoring the AMR Mode...........................................................................................................13-30 13.4 Monitoring the RNC Cell Performance....................................................................................................13-31 13.4.1 Monitoring Cell P-CPICH TX Power..............................................................................................13-33 13.4.2 Monitoring UL RX Total Wideband Power of a Cell......................................................................13-35 13.4.3 Monitoring DL Carrier TX Power of a Cell.....................................................................................13-37 13.4.4 Monitoring the Number of Cell Users..............................................................................................13-39 13.4.5 Monitoring Node Synchronization...................................................................................................13-40 13.4.6 Monitoring the UL CAC..................................................................................................................13-42 13.4.7 Monitoring DL CAC........................................................................................................................13-44 13.4.8 Monitoring the Number of UL Equivalent Users.............................................................................13-45 13.4.9 Monitoring the Number of DL Equivalent Users.............................................................................13-47 13.4.10 Monitoring the Cell Code Tree......................................................................................................13-48 13.4.11 Monitoring the Minimum Required Power of the HS-DSCH........................................................13-50 13.4.12 Monitoring the Bit Rate Provided by the HS-DSCH.....................................................................13-51 13.4.13 Monitoring the Bit Rate Provided by the E-DCH..........................................................................13-52 13.4.14 Monitoring UL Throughput of a Cell.............................................................................................13-54 13.4.15 Monitoring DL Throughput of a Cell.............................................................................................13-55 13.4.16 Monitoring the Cell CE..................................................................................................................13-56 13.4.17 Monitoring the FDPCH SYMBOL................................................................................................13-58 13.5 Monitoring the RNC Link Performance....................................................................................................13-59 13.5.1 Monitoring the IMA Group Traffic..................................................................................................13-60 13.5.2 Monitoring the UNI Link Traffic.....................................................................................................13-62 13.5.3 Monitoring the Fractional ATM Link Traffic..................................................................................13-64 13.5.4 Monitoring the SAAL Link Traffic..................................................................................................13-66 13.5.5 Monitoring the IPoA PVC Traffic...................................................................................................13-67 13.5.6 Monitoring the AAL2 Path Traffic..................................................................................................13-69 13.5.7 Monitoring the FE/GE Traffic..........................................................................................................13-71 13.5.8 Monitoring the PPP Link Traffic.....................................................................................................13-73 vi


Issue 03 (2009-04-25)

RNC LMT User Guide

Contents

13.5.9 Monitoring the MLPPP Group Traffic.............................................................................................13-75 13.5.10 Monitoring the SCTP Link Traffic.................................................................................................13-76 13.5.11 Monitoring the IP Path Traffic.......................................................................................................13-78 13.5.12 Monitoring the Logical Ports.........................................................................................................13-80 13.5.13 Monitoring OAM Traffic...............................................................................................................13-82 13.5.14 Monitoring Bandwidth of Logical Ports........................................................................................13-83 13.6 Monitoring the RNC Board Resource.......................................................................................................13-84 13.7 Basic RNC Real-Time Performance Monitoring Operations....................................................................13-87 13.7.1 Browsing the RNC Monitoring Results Online...............................................................................13-87 13.7.2 Switching the Display Mode............................................................................................................13-88 13.7.3 Setting the Default Display Mode....................................................................................................13-89 13.7.4 Editing the Display Mode for the Chart...........................................................................................13-90 13.7.5 Saving RNC Monitoring Results......................................................................................................13-90 13.7.6 Pausing and Resuming an RNC Monitoring Task...........................................................................13-91 13.7.7 Adding an RNC CPU/DSP Monitoring Task...................................................................................13-92 13.7.8 Deleting an RNC CPU/DSP Monitoring Task.................................................................................13-92 13.7.9 Stopping an RNC Monitoring Task.................................................................................................13-93 13.7.10 Browsing RNC Monitoring Results Offline...................................................................................13-93 13.8 Parameter Reference for RNC Real-Time Performance Monitoring........................................................13-96 13.8.1 Parameter Reference for RNC CPU Usage Monitoring...................................................................13-96 13.8.2 Parameter Reference for Connection Performance Monitoring.......................................................13-97 13.8.3 Parameter Reference for Cell Performance Monitoring...................................................................13-97 13.8.4 Parameter Reference for Link Performance Monitoring..................................................................13-98 13.8.5 Parameter Reference for Board Resource Monitoring...................................................................13-100

14 Testing RNC Faults................................................................................................................14-1 14.1 Testing Faults on the Physical Layer..........................................................................................................14-2 14.1.1 Physical Layer Testing.......................................................................................................................14-2 14.1.2 Testing the Local E1/T1 Loopback....................................................................................................14-3 14.1.3 Testing the Remote E1/T1 Loopback.................................................................................................14-4 14.1.4 Testing the E1/T1 BER......................................................................................................................14-4 14.1.5 Testing the E1/T1 Loopback..............................................................................................................14-5 14.1.6 Testing E1/T1 Wrong Connection.....................................................................................................14-6 14.1.7 Testing the SDH Loopback................................................................................................................14-7 14.1.8 Querying SDH....................................................................................................................................14-7 14.1.9 Querying FE/GE.................................................................................................................................14-8 14.2 Testing Faults on the Link Layer................................................................................................................14-8 14.2.1 Link Layer Testing.............................................................................................................................14-9 14.2.2 Testing the AAL2 Path.....................................................................................................................14-10 14.2.3 Testing the SAAL Link....................................................................................................................14-11 14.2.4 Testing the SCTP Link.....................................................................................................................14-11 14.2.5 Testing PPP/MLPPP Wrong Connection.........................................................................................14-12 14.2.6 Querying an PPP/MLPPP Link........................................................................................................14-13 Issue 03 (2009-04-25)


vii

RNC LMT User Guide

Contents

14.2.7 Testing the NodeB Maintenance IPoA Link....................................................................................14-13 14.2.8 Testing the Iu-PS IPoA Link............................................................................................................14-14 14.2.9 Querying IMA..................................................................................................................................14-15 14.3 Testing Other RNC Faults.........................................................................................................................14-16 14.3.1 Other Tests.......................................................................................................................................14-16 14.3.2 Testing IPC Connectivity.................................................................................................................14-17 14.3.3 Testing the Cell Common Channel..................................................................................................14-18 14.3.4 Testing RFN.....................................................................................................................................14-19 14.3.5 Testing the Clock.............................................................................................................................14-19 14.3.6 Testing Load Control of a Board......................................................................................................14-20 14.4 Basic Operations of the RNC Fault Tests.................................................................................................14-21 14.4.1 Browsing Fault Testing Results.......................................................................................................14-21 14.4.2 Manually Saving Fault Testing Results...........................................................................................14-21 14.4.3 Stopping a Fault Testing Task..........................................................................................................14-22 14.5 Parameter Reference for the RNC Fault Tests..........................................................................................14-22 14.5.1 Parameter Reference for the Local E1/T1 Loopback Test...............................................................14-24 14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test............................................................14-24 14.5.3 Parameter Reference for the E1/T1 BER Test.................................................................................14-25 14.5.4 Parameter Reference for the E1/T1 Loopback Test.........................................................................14-26 14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test...........................................................14-26 14.5.6 Parameter Reference for the SDH Loopback Test...........................................................................14-27 14.5.7 Parameter Reference for SDH Query...............................................................................................14-27 14.5.8 Parameter Reference for FE/GE Query............................................................................................14-28 14.5.9 Parameter Reference for the AAL2 Path Test..................................................................................14-29 14.5.10 Parameter Reference for SAAL Link Test.....................................................................................14-29 14.5.11 Parameter Reference for SCTP Link Test......................................................................................14-30 14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test..............................................14-30 14.5.13 Parameter Reference for PPP/MLPPP Query................................................................................14-31 14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test........................................................14-32 14.5.15 Parameter Reference for the Iu-PS IPoA Test................................................................................14-32 14.5.16 Parameter Reference for IMA Query.............................................................................................14-33 14.5.17 Parameter Reference for the IPC Connectivity Test......................................................................14-33 14.5.18 Parameter Reference for the Cell Common Channel Test.............................................................14-34 14.5.19 Parameter Reference for the RFN Test..........................................................................................14-34 14.5.20 Parameter Reference for the Clock Test.........................................................................................14-35 14.5.21 Parameter Reference for the Load Control Test of the Boards......................................................14-35

15 Using the RNC LMT Performance Browser Tool............................................................15-1 15.1 Starting the RNC LMT Performance Browser Tool...................................................................................15-2 15.2 Setting the Parameters of the RNC LMT Performance Browser Tool........................................................15-2 15.3 Browsing Description Files.........................................................................................................................15-4 15.4 Downloading Performance Measurement Results......................................................................................15-6 15.5 Querying Performance Measurement Data.................................................................................................15-7 viii


Issue 03 (2009-04-25)

RNC LMT User Guide

Contents

15.6 Filtering Performance Measurement Data..................................................................................................15-8 15.7 Exporting Performance Measurement Data................................................................................................15-9 15.8 Exiting the RNC LMT Performance Browser Tool..................................................................................15-10

16 Using the FTP Client of the RNC LMT..............................................................................16-1 16.1 Logging in to the FTP Server on the LMT FTP Client...............................................................................16-2 16.2 Uploading Data Files to the RNC FTP Server............................................................................................16-3 16.3 Downloading Data Files from the RNC FTP Server...................................................................................16-4 16.4 Setting the Encryption Mode of the RNC FTP Server................................................................................16-4 16.5 Querying the Encryption Mode of the RNC FTP Server............................................................................16-5 16.6 Disconnecting the LMT FTP Client from the RNC FTP Server.................................................................16-5

Issue 03 (2009-04-25)


ix

RNC LMT User Guide

Figures

Figures Figure 2-1 RNC OM networking......................................................................................................................... 2-3 Figure 3-1 Main interface of the Local Maintenance Terminal...........................................................................3-3 Figure 3-2 Main interface of the FTP Client........................................................................................................3-5 Figure 3-3 Main interface of the Trace Viewer....................................................................................................3-6 Figure 3-4 Main interface of the Monitor Viewer................................................................................................3-8 Figure 3-5 Main interface of the Performance Browser Tool..............................................................................3-9 Figure 3-6 Main interface of the Convert Management System........................................................................3-11 Figure 4-1 Selecting a setup language..................................................................................................................4-1 Figure 4-2 Copyright notice.................................................................................................................................4-2 Figure 4-3 Selecting software components..........................................................................................................4-3 Figure 4-4 Confirming installation.......................................................................................................................4-4 Figure 5-1 Local Area Connection Properties dialog box....................................................................................5-4 Figure 5-2 Internet Protocol (TCP/IP) Properties dialog box.............................................................................. 5-5 Figure 5-3 User Login dialog box........................................................................................................................5-7 Figure 5-4 Office Management dialog box before adding an office....................................................................5-7 Figure 5-5 To add an office, perform the following steps:...................................................................................5-8 Figure 5-6 Office Management dialog box after adding an office.......................................................................5-8 Figure 5-7 User Login dialog box........................................................................................................................5-9 Figure 5-8 Certificate Configuration dialog box................................................................................................5-11 Figure 5-9 Open dialog box................................................................................................................................5-12 Figure 5-10 Office Management dialog box......................................................................................................5-13 Figure 5-11 Adding an office.............................................................................................................................5-13 Figure 5-12 Modifying an office........................................................................................................................5-14 Figure 5-13 Open dialog box..............................................................................................................................5-15 Figure 5-14 Adding an office.............................................................................................................................5-16 Figure 6-1 MML client.........................................................................................................................................6-5 Figure 6-2 Data configuration user being NULL.................................................................................................6-9 Figure 6-3 Data configuration user being admin..................................................................................................6-9 Figure 6-4 Data configuration user being admin................................................................................................6-10 Figure 6-5 Immediate batch running of MML commands.................................................................................6-12 Figure 6-6 Scheduled batch running of MML commands.................................................................................6-13 Figure 7-1 Operator Management dialog box......................................................................................................7-7 Figure 7-2 Modify Operator dialog box...............................................................................................................7-8 Issue 03 (2009-04-25)


xi

RNC LMT User Guide

Figures

Figure 7-3 Operator Management dialog box......................................................................................................7-9 Figure 7-4 Deleting an operator.........................................................................................................................7-10 Figure 7-5 Setting password policies.................................................................................................................7-11 Figure 7-6 Change Password dialog box............................................................................................................7-13 Figure 7-7 Setting command group names.........................................................................................................7-15 Figure 7-8 Modifying a command group...........................................................................................................7-16 Figure 8-1 Activating the license of the primary operator...................................................................................8-4 Figure 8-2 Activating the license of the secondary operator................................................................................8-4 Figure 8-3 ESN in the returned message..............................................................................................................8-8 Figure 8-4 Adding the basic information about the RNC....................................................................................8-9 Figure 8-5 Adding the basic information about the primary operator..................................................................8-9 Figure 8-6 ESN in the returned message............................................................................................................8-10 Figure 9-1 Alarm box...........................................................................................................................................9-4 Figure 9-2 Customizing alarms..........................................................................................................................9-10 Figure 9-3 Details about an alarm......................................................................................................................9-11 Figure 9-4 Querying an alarm log......................................................................................................................9-13 Figure 9-5 Query Alarm Log window................................................................................................................9-13 Figure 9-6 Details about an alarm......................................................................................................................9-15 Figure 9-7 Alarm online help.............................................................................................................................9-15 Figure 9-8 Saving alarms...................................................................................................................................9-17 Figure 9-9 Setting alarm real-time print.............................................................................................................9-18 Figure 9-10 Printing alarms................................................................................................................................9-19 Figure 9-11 Configuring the Convert Management System..............................................................................9-21 Figure 9-12 Configuring the Convert Management System..............................................................................9-23 Figure 9-13 Resetting alarm box........................................................................................................................9-24 Figure 9-14 Alarm Box Control.........................................................................................................................9-25 Figure 9-15 Alarm Box Control.........................................................................................................................9-26 Figure 9-16 Setting the alarm shield severity.....................................................................................................9-28 Figure 9-17 Querying alarm mask level.............................................................................................................9-29 Figure 10-1 Server entry bar..............................................................................................................................10-6 Figure 10-2 Server entry bar..............................................................................................................................10-7 Figure 10-3 Server entry bar..............................................................................................................................10-8 Figure 11-1 RNC device panel...........................................................................................................................11-3 Figure 11-2 Navigation tree of the device panel................................................................................................11-4 Figure 11-3 Displaying the color legend............................................................................................................11-5 Figure 11-4 Hiding the color legend..................................................................................................................11-5 Figure 11-5 Showing the failure bar...................................................................................................................11-6 Figure 11-6 Hiding the failure bar......................................................................................................................11-7 Figure 11-7 Querying details of boards..............................................................................................................11-8 Figure 11-8 Output interface of the CPU/DSP Usage window........................................................................11-10 Figure 11-9 RNC display panel........................................................................................................................11-11 Figure 11-10 Edge of a subrack.......................................................................................................................11-12 xii


Issue 03 (2009-04-25)

RNC LMT User Guide

Figures

Figure 11-11 Status of an FE port....................................................................................................................11-13 Figure 11-12 Status of an GE port....................................................................................................................11-14 Figure 11-13 Query DSP Status.......................................................................................................................11-15 Figure 11-14 Detailed status of an E1/T1 link.................................................................................................11-16 Figure 11-15 Querying alarms through an alarm light.....................................................................................11-17 Figure 11-16 Configuration modes of subracks...............................................................................................11-18 Figure 12-1 Working principles of the message tracing....................................................................................12-5 Figure 12-2 Setting the parameters for Iu interface tracing............................................................................12-7 Figure 12-3 Output of Iu interface tracing......................................................................................................12-8 Figure 12-4 Setting the parameters for Iur interface tracing...........................................................................12-10 Figure 12-5 Output of Iur interface tracing..................................................................................................12-11 Figure 12-6 Setting the parameters for Iub interface tracing.........................................................................12-13 Figure 12-7 Output of Iub interface tracing..................................................................................................12-14 Figure 12-8 Setting the parameters for Uu interface tracing.........................................................................12-15 Figure 12-9 Output of Uu interface tracing...................................................................................................12-16 Figure 12-10 Setting the parameters for UE tracing ......................................................................................12-18 Figure 12-11 Output of UE tracing.................................................................................................................12-19 Figure 12-12 Setting the parameters for REDIRECT tracing ......................................................................12-23 Figure 12-13 Output of REDIRECT tracing.................................................................................................12-24 Figure 12-14 Save dialog box..........................................................................................................................12-24 Figure 12-15 Missed intra-frequency neighboring cell tracing........................................................................12-26 Figure 12-16 Missed inter-frequency neighboring cell tracing........................................................................12-27 Figure 12-17 Missed inter-RAT neighboring cell tracing................................................................................12-28 Figure 12-18 Setting the parameters for Iu interface tracing.........................................................................12-31 Figure 12-19 Output of SCCP tracing...........................................................................................................12-32 Figure 12-20 Setting the parameters for Iu interface tracing.........................................................................12-33 Figure 12-21 Output of MTP3 tracing...........................................................................................................12-34 Figure 12-22 Setting the parameters for Iu interface tracing.........................................................................12-37 Figure 12-23 Output of SAAL tracing...........................................................................................................12-38 Figure 12-24 Setting the parameters for Iu interface tracing.........................................................................12-39 Figure 12-25 Output of SCTP tracing...........................................................................................................12-40 Figure 12-26 Message Browser window.........................................................................................................12-45 Figure 12-27 Save dialog box.........................................................................................................................12-47 Figure 12-28 Pausing a tracing task.................................................................................................................12-48 Figure 12-29 Resuming a tracing task..............................................................................................................12-49 Figure 12-30 Clonging a tracing task...............................................................................................................12-49 Figure 12-31 Opening a file containing traced messages.................................................................................12-50 Figure 12-32 Displaying traced messages........................................................................................................12-51 Figure 12-33 Message Browser window.........................................................................................................12-52 Figure 13-1 CPU/DSP usage monitoring...........................................................................................................13-3 Figure 13-2 Working principle of connection/cell/link performance monitoring..............................................13-4 Figure 13-3 Add Tasks dialog box.....................................................................................................................13-6 Issue 03 (2009-04-25)


xiii

RNC LMT User Guide

Figures

Figure 13-4 CPU/DSP Usage monitoring window in a list................................................................................13-7 Figure 13-5 CPU/DSP Usage monitoring window in a chart............................................................................ 13-7 Figure 13-6 Querying properties of a CPU/DSP usage monitoring task........................................................... 13-8 Figure 13-7 Connection performance monitoring dialog box..........................................................................13-11 Figure 13-8 Connection performance monitoring dialog box..........................................................................13-13 Figure 13-9 Connection performance monitoring dialog box..........................................................................13-15 Figure 13-10 Connection performance monitoring dialog box....................................................................13-16 Figure 13-11 Connection performance monitoring dialog box........................................................................13-18 Figure 13-12 Connection performance monitoring dialog box........................................................................13-20 Figure 13-13 Connection performance monitoring dialog box........................................................................13-21 Figure 13-14 Connection performance monitoring dialog box........................................................................13-23 Figure 13-15 Connection performance monitoring dialog box........................................................................13-24 Figure 13-16 Connection performance monitoring dialog box........................................................................13-26 Figure 13-17 Connection performance monitoring dialog box........................................................................13-28 Figure 13-18 Connection performance monitoring dialog box........................................................................13-29 Figure 13-19 Connection performance monitoring dialog box........................................................................13-31 Figure 13-20 Cell performance monitoring dialog box....................................................................................13-34 Figure 13-21 Output interface of cell P-CPICH TX power monitoring...........................................................13-35 Figure 13-22 Cell performance monitoring dialog box....................................................................................13-36 Figure 13-23 Output interface of UL RX total wideband power monitoring for a cell...................................13-37 Figure 13-24 Cell performance monitoring dialog box....................................................................................13-38 Figure 13-25 Output interface of DL TX carrier power monitoring for a cell.................................................13-39 Figure 13-26 Cell performance monitoring dialog box................................................................................13-40 Figure 13-27 Cell performance monitoring dialog box....................................................................................13-41 Figure 13-28 Output interface of node synchronization monitoring................................................................13-42 Figure 13-29 Cell performance monitoring dialog box................................................................................13-43 Figure 13-30 Cell performance monitoring dialog box................................................................................13-45 Figure 13-31 Cell performance monitoring dialog box................................................................................13-46 Figure 13-32 Cell performance monitoring dialog box................................................................................13-47 Figure 13-33 Cell performance monitoring dialog box....................................................................................13-48 Figure 13-34 Output of the cell code tree usage in static view........................................................................13-49 Figure 13-35 Cell performance monitoring dialog box....................................................................................13-50 Figure 13-36 Cell performance monitoring dialog box................................................................................13-52 Figure 13-37 Cell performance monitoring dialog box................................................................................13-53 Figure 13-38 Cell performance monitoring dialog box....................................................................................13-54 Figure 13-39 Cell performance monitoring dialog box....................................................................................13-56 Figure 13-40 Cell performance monitoring dialog box................................................................................13-57 Figure 13-41 Cell performance monitoring dialog box................................................................................13-58 Figure 13-42 Link performance monitoring dialog box...................................................................................13-61 Figure 13-43 Output interface of IMA group real-time traffic monitoring......................................................13-62 Figure 13-44 Link performance monitoring dialog box...................................................................................13-63 Figure 13-45 Output interface of UNI link real-time traffic monitoring..........................................................13-64 xiv


Issue 03 (2009-04-25)

RNC LMT User Guide

Figures

Figure 13-46 Link performance monitoring dialog box...............................................................................13-65 Figure 13-47 Link performance monitoring dialog box...................................................................................13-66 Figure 13-48 Output interface of SAAL link real-time traffic monitoring......................................................13-67 Figure 13-49 Link performance monitoring dialog box...................................................................................13-68 Figure 13-50 Output interface of IPoA PVC real-time traffic monitoring.......................................................13-69 Figure 13-51 Link performance monitoring dialog box...................................................................................13-70 Figure 13-52 Output interface of AAL2 path real-time traffic monitoring......................................................13-71 Figure 13-53 Link performance monitoring dialog box...................................................................................13-72 Figure 13-54 Output interface of FE/GE real-time traffic monitoring.............................................................13-73 Figure 13-55 Link performance monitoring dialog box...................................................................................13-74 Figure 13-56 Link performance monitoring dialog box...................................................................................13-76 Figure 13-57 Link performance monitoring dialog box...................................................................................13-77 Figure 13-58 Output interface of SCTP link real-time traffic monitoring.......................................................13-78 Figure 13-59 Link performance monitoring dialog box...................................................................................13-79 Figure 13-60 Output interface of IP path real-time traffic monitoring............................................................13-80 Figure 13-61 Link performance monitoring dialog box...................................................................................13-81 Figure 13-62 Link performance monitoring dialog box...................................................................................13-82 Figure 13-63 Link performance monitoring dialog box...................................................................................13-83 Figure 13-64 Board Resource monitoring dialog box......................................................................................13-85 Figure 13-65 Output interface of board resource monitoring..........................................................................13-86 Figure 13-66 Adding CPU/DSP usage monitoring tasks.................................................................................13-92 Figure 13-67 Deleting a CPU/DSP usage monitoring task..............................................................................13-93 Figure 13-68 Open dialog box..........................................................................................................................13-94 Figure 13-69 Displaying monitoring results in a list........................................................................................13-95 Figure 13-70 Displaying monitoring results in a chart.....................................................................................13-95 Figure 14-1 Saving testing results....................................................................................................................14-22 Figure 15-1 Select Net dialog box......................................................................................................................15-2 Figure 15-2 Net Configure dialog box..............................................................................................................15-3 Figure 15-3 Browsing description files..............................................................................................................15-5 Figure 15-4 Checking details.............................................................................................................................15-5 Figure 15-5 Downloading the measurement results...........................................................................................15-6 Figure 15-6 Auto Download Settings dialog box...............................................................................................15-7 Figure 15-7 Add dialog box...............................................................................................................................15-7 Figure 15-8 Querying performance measurement results..................................................................................15-8 Figure 15-9 Filtering results...............................................................................................................................15-9 Figure 15-10 Save dialog box..........................................................................................................................15-10 Figure 16-1 Main interface of the FTP Client....................................................................................................16-2

Issue 03 (2009-04-25)


xv

RNC LMT User Guide

Tables

Tables Table 2-1 Hardware requirements........................................................................................................................2-3 Table 2-2 Software requirements.........................................................................................................................2-4 Table 3-1 Main interface of the Local Maintenance Terminal.............................................................................3-3 Table 3-2 Online help of the Local Maintenance Terminal.................................................................................3-4 Table 3-3 Main interface of the FTP Client.........................................................................................................3-5 Table 3-4 Online help of the FTP Client..............................................................................................................3-6 Table 3-5 Main interface of the Trace Viewer.....................................................................................................3-7 Table 3-6 Online help of the Trace Viewer..........................................................................................................3-7 Table 3-7 Main interface of the Monitor Viewer.................................................................................................3-8 Table 3-8 Online help of the Monitor Viewer......................................................................................................3-8 Table 3-9 Main interface of the Performance Browser Tool................................................................................3-9 Table 3-10 Online help of the Performance Browser Tool................................................................................3-10 Table 3-11 Main interface of the Convert Management System........................................................................3-11 Table 3-12 Online help of the Convert Management System............................................................................3-11 Table 6-1 Actions of the MML commands..........................................................................................................6-3 Table 6-2 Fields on the MML client.....................................................................................................................6-6 Table 7-1 Command groups.................................................................................................................................7-3 Table 7-2 External operators of different levels...................................................................................................7-5 Table 7-3 Examples of operation time limit settings............................................................................................7-6 Table 9-1 Fault alarms and event alarms..............................................................................................................9-2 Table 9-2 RNC Alarm severity levels..................................................................................................................9-3 Table 9-3 Display properties and setting methods...............................................................................................9-9 Table 12-1 Operations for browsing an RNC traced message online..............................................................12-44 Table 12-2 Parameters on the input GUI..........................................................................................................12-62 Table 12-3 Parameters on the output GUI........................................................................................................12-63 Table 12-4 Parameters on the input GUI..........................................................................................................12-63 Table 12-5 Parameters on the output GUI........................................................................................................12-64 Table 12-6 Parameters on the input GUI..........................................................................................................12-64 Table 12-7 Parameters on the output GUI........................................................................................................12-65 Table 14-1 Items of the physical layer test.........................................................................................................14-2 Table 14-2 Items of the link layer test................................................................................................................14-9 Table 14-3 Items of other tests.........................................................................................................................14-17 Table 14-4 Parameters for the local E1/T1 loopback test.................................................................................14-24 Issue 03 (2009-04-25)


xvii

RNC LMT User Guide

Tables

Table 14-5 Parameters for the remote E1/T1 loopback test.............................................................................14-24 Table 14-6 Parameters for the E1/T1 BER test................................................................................................14-25 Table 14-7 Parameters for the E1/T1 loopback test.........................................................................................14-26 Table 14-8 Parameters for the E1/T1 wrong connection test...........................................................................14-26 Table 14-9 Parameters for the SDH loopback test...........................................................................................14-27 Table 14-10 Parameters for SDH query...........................................................................................................14-27 Table 14-11 Parameters for FE/GE query........................................................................................................14-28 Table 14-12 Parameters for the AAL2 path test...............................................................................................14-29 Table 14-13 Parameters for the SAAL link test...............................................................................................14-29 Table 14-14 Parameters for the SCTP link test................................................................................................14-30 Table 14-15 Parameters for the PPP/MLPPP wrong connection test...............................................................14-31 Table 14-16 Parameters for PPP/MLPPP Query..............................................................................................14-31 Table 14-17 Parameters for the NodeB maintenance IPoA test.......................................................................14-32 Table 14-18 Parameters for the Iu-PS IPoA test..............................................................................................14-32 Table 14-19 Parameters for IMA query...........................................................................................................14-33 Table 14-20 Parameters for the IPC connectivity test......................................................................................14-33 Table 14-21 Parameters for the cell common channel test...............................................................................14-34 Table 14-22 Parameters for the RFN test.........................................................................................................14-34 Table 14-23 Parameters for the clock test........................................................................................................14-35 Table 14-24 Parameters for the load control test of the boards........................................................................14-35 Table 15-1 Parameters in the Net Configure dialog box....................................................................................15-3 Table 16-1 Implementation method of encryption.............................................................................................16-3

xviii


Issue 03 (2009-04-25)

RNC LMT User Guide

About This Document

About This Document

Purpose This document describes the installation, functions, and interfaces of the RNC Local Maintenance Terminal (LMT). It also provides instructions for performing basic OM operations.

Product Version The following table lists the product version related to this document. Product Name

Product Model

Product Version

RNC

BSC6810

V200R011

Intended Audience This document is intended for: l

Network operators

l

Shift operators

l

System engineers

l

Field engineers

Organization 1 Changes in RNC LMT User Guide This describes the changes in RNC LMT User Guide. 2 Introduction to the RNC LMT This describes the definition and functions of the LMT, the topology of the RNC operating system, and the computer configuration requirements for LMT installation. 3 Components of the RNC LMT This describes the following software components of the RNC LMT: the local maintenance terminal, FTP client, trace viewer, monitor viewer, performance browser tool, and convert management system. 4 Installing the RNC LMT Application Issue 03 (2009-04-25)


1

RNC LMT User Guide

About This Document

This describes how to install the RNC LMT application. This task takes V200R011C00SPC100 as an example. 5 Getting Started with the RNC LMT This describes how to start, configure, use, and quit the LMT application. When running the LMT application, ensure that the free space of the hard disk is no less than 1 GB. 6 Running RNC MML Commands This describes how to run MML commands on the Local Maintenance Terminal to perform comprehensive operations and maintenance on the RNC system. 7 Managing Authorities for RNC Operations This describes how to manage the authorities for the RNC operations. To manage the authorities for the RNC operations is to manage the operator accounts, operator passwords, and RNC command groups. 8 Managing the RNC License This describes how to manage the RNC license, for example, activate and reallocate the RNC license, check the quantity of current RNC operators, the traffic on the RNC, or the alarms related to the RNC license. 9 Managing RNC Alarms This describes how to manage RNC alarms. It helps analyze the alarm, locate, and rectify the faults. 10 Managing RNC Logs This describes how to manage RNC logs. The logs are saved in .txt and .log files. 11 Managing the RNC Equipment by Using the Device Panel and Display Panel This describes how to manage the RNC equipment by using the device panel and display panel. By performing this task, you can query the information about the boards, board ports, board links, and board alarms in GUI mode. 12 Tracing and Viewing RNC Messages This describes how to manage the RNC traced messages. RNC message tracing is implemented through menus. You can use the Trace Viewer to query the tracing data recorded in the files. 13 RNC Real-Time Performance Monitoring This describes how to monitor RNC performance in real time. 14 Testing RNC Faults This describes the following concepts of the RNC fault tests: the physical layer test, data link layer test, and other fault tests. 15 Using the RNC LMT Performance Browser Tool This describes how to start, configure, and exit the RNC LMT Performance Browser Tool. 16 Using the FTP Client of the RNC LMT This describes how to use the FTP Client of the RNC LMT. By performing this task, you can use and exit the FTP Client. You can also set and query the encryption mode of the FTP server. 2


Issue 03 (2009-04-25)

RNC LMT User Guide

About This Document

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. 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

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

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.

Issue 03 (2009-04-25)

Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

3

RNC LMT User Guide

About This Document

Convention

Description

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

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.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention

Description

Boldface

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

Description

Key

Press the key. For example, press Enter and press Tab.

Key 1+Key 2

Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently.

Key 1, Key 2

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.

4

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

Press and hold the primary mouse button and move the pointer to a certain position. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide

1 Changes in RNC LMT User Guide

1

Changes in RNC LMT User Guide

This describes the changes in RNC LMT User Guide.

03 (2009-04-25) This is the second commercial release. Compared with issue 02 (2009-03-25) of V200R011, no part is added to or removed from this document. The following table describes the changes in each part. Parts

Changes

14.5.1 Parameter Reference for the Local E1/T1 Loopback Test

The name of some boards are modified: FG2 is changed to FG2a, GOU is changed to GOUa, AOU is changed to AOUa, and POU is changed to POUa.

14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test

The name of UOI board is modified: UOI_ATM/UOI_IP is changed to UOIa.

14.5.3 Parameter Reference for the E1/T1 BER Test 14.5.7 Parameter Reference for SDH Query 14.5.8 Parameter Reference for FE/GE Query

02 (2009-03-25) This is the first commercial release. Compared with issue 01 (2009-02-10) of V200R011, no part is added to or removed from this document. The following table describes the changes in each part.

Issue 03 (2009-04-25)


1-1

RNC LMT User Guide


Parts

Changes

12.6 Tracing UE Messages

The figure of tracing UE Messages is optimized.

12.5 Tracing Uu Interface Messages

Some language mistakes of tracing Uu Interface Messages are modified.

01 (2009-02-10) This is the field trial release. Compared with issue 03 (2008-08-30) of V200R010, the following parts are added: l

12.6 Tracing UE Messages

l

12.19.9 Managing All Tracing Tasks

l

13.4.16 Monitoring the Cell CE

l

13.4.17 Monitoring the FDPCH SYMBOL

l

12.20.5 Parameter Reference for UE Tracing

Compared with issue 03 (2008-08-30) of V200R010, the following parts are deleted: l

Tracing UE (Standard Interfaces) Messages

l

Tracing UE (Signaling Plane and User Plane) Messages

l

Tracing CDT Messages

l

Tracing CellDT Messages

l

Interface Reference for UE Tracing (Standard Interface)

l

Interface Reference for UE Tracing (Signaling Plane and User Plane)

l

Interface Reference for SCCP Message Tracing

l

Interface Reference for MTP3 Message Tracing

l

Interface Reference for QAAL2 Message Tracing

l

Interface Reference for SAAL Message Tracing

l

Interface Reference for SCTP Message Tracing

l

Interface Reference for M3UA Message Tracing

l

Managing RNC Patches

Compared with issue 03 (2008-08-30) of V200R010, this issue incorporates the changes described in the following table.

1-2

Parts

Changes

Obtaining the RNC Data Configuration Right

Alarm name of 20016,20017,20018,20012 are modified.

Obtaining the RNC Data Configuration Right

The switch of the data configuration right is modified in prerequisites.


Issue 03 (2009-04-25)

RNC LMT User Guide


Parts

Changes

Tracing Messages of Missed IntraFrequency Neighboring Cells

The detect switch of the missed neighboring cell tracing is added in prerequisites.

Tracing Messages of Missed InterFrequency Neighboring Cells Tracing Messages of Missed Inter-RAT Neighboring Cells Introduction to the RNC MML Client

The History Command pane in the GUI is changed to the Operation Record pane.

Batch Running MML Commands

The description of the syntax analysis in the process of batch running is added.

Checking RNC Basic Information and Operator Information

The figures of the MML command GUIs are replaced.

License Control for Multiple Operators

Three optional functions that can be controlled by the primary operator is added. The figures of the license activation GUIs are replaced.

Tracing Iu Interface Messages Tracing Iur Interface Messages Tracing Iub Interface Messages

The context information, figures of input and output GUIs, procedures, and postrequisite information are modified.

Tracing Uu Interface Messages Tracing IOS Messages

The context information, figures of the input and output GUIs, and postrequisite information are modified.

Tracing Cell Messages

The context information, figures of the input and output GUIs, procedures, and postrequisite information are modified.

Tracing REDIRECT Messages

The figure of the input GUI is changed.

Tracing MNCDT Messages

The full spelling of MNCDT is added.

Tracing SCCP Messages

The figures of the input and output GUIs are changed.

Tracing MTP3 Messages Tracing QAAL2 Messages Tracing SAAL Messages Tracing SCTP Messages Tracing M3UA Messages Parameter Reference for RNC Message Tracing and Viewing

The wording of "Interface Reference" in the titles is changed into "Parameter Reference".

Parameter Reference for RNC Real-Time Performance Monitoring Parameter Reference for the RNC Fault Tests

Issue 03 (2009-04-25)


1-3

RNC LMT User Guide


Parts

Changes

Parameter Reference for Iu Interface Tracing

The descriptions of some parameters are modified.

Parameter Reference for Iur Interface Tracing Parameter Reference for Iub Interface Tracing Parameter Reference for Uu Interface Tracing Parameter Reference for IOS Tracing Parameter Reference for Cell Tracing Parameter Reference for OS Tracing

1-4


Issue 03 (2009-04-25)

RNC LMT User Guide

2 Introduction to the RNC LMT

2

Introduction to the RNC LMT

About This Chapter This describes the definition and functions of the LMT, the topology of the RNC operating system, and the computer configuration requirements for LMT installation. 2.1 Definitions of the LMT When using the Local Maintenance Terminal (LMT), you need to know the following concepts: LMT, LMT PC, and LMT application. 2.2 Functions of the RNC LMT The RNC OM system functions in client/server mode. The LMT acts as a client, and the Back Administration Module (BAM) acts as the server. 2.3 RNC OM Networking The RNC OM networking provides operation and maintenance for the RNC and NodeB. 2.4 Computer Requirements of the LMT The computer requirements are categorized into the following: hardware requirements, software requirements, and communication capability requirements.

Issue 03 (2009-04-25)


2-1

RNC LMT User Guide


2.1 Definitions of the LMT When using the Local Maintenance Terminal (LMT), you need to know the following concepts: LMT, LMT PC, and LMT application.

LMT The LMT is a logical concept. It refers to the operation and maintenance (OM) terminal installed with the Huawei Local Maintenance Terminal software group and connected to the actual OM network of the related NE. You can use the LMT to operate and maintain an NE.

LMT PC The LMT PC is the hardware of the LMT. It refers to the computer to be installed with the LMT application.

LMT Application The LMT application refers to the Huawei proprietary application, the Huawei Local Maintenance Terminal software group, which is installed on the LMT PC.

2.2 Functions of the RNC LMT The RNC OM system functions in client/server mode. The LMT acts as a client, and the Back Administration Module (BAM) acts as the server. The LMT communicates with the BAM through a Local Area Network (LAN) or a Wide Area Network (WAN). As an operating terminal, the LMT provides a graphical user interface (GUI) for the operation and maintenance of the RNC equipment. On the LMT, you can run the MML commands, query execution results, trace messages, query alarms, and collect performance statistics.

2.3 RNC OM Networking The RNC OM networking provides operation and maintenance for the RNC and NodeB. Figure 2-1 shows the RNC OM networking.

2-2


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 2-1 RNC OM networking

As shown in Figure 2-1, either local or remote maintenance is applicable to the RNC and NodeB. Local maintenance is performed on the LMT, and remote maintenance is performed through the OM network. The RNC-NodeB OM channel is configurable. Through the OM channel, remote maintenance of the NodeB can be performed on the Network Management System (NMS), M2000, or NodeB LMT.

2.4 Computer Requirements of the LMT The computer requirements are categorized into the following: hardware requirements, software requirements, and communication capability requirements.

Hardware Requirements Table 2-1 lists the hardware requirements for the computer on which the LMT application will be installed. Table 2-1 Hardware requirements

Issue 03 (2009-04-25)

Item

Quantity

Recommended Configuration

Minimum Configuration

CPU

1

2.8 GHz or above

866 MHz

RAM

1

512 MB

256 MB

Hard disk

1

80 GB

10 GB

Display adapter resolution

-

1024 by 768 pixels or above

800 x 600


2-3

RNC LMT User Guide


Item

Quantity


Minimum Configuration

CD-ROM drive

1

-

-

Ethernet adapter

1

10 Mbit/s or 100 Mbit/s

10 Mbit/s or 100 Mbit/s

Others

5x1

Keyboard, mouse, modem, audio adapter, sound box

-

Software Requirements Table 2-2 lists the software requirements for the computer on which the LMT application will be installed. Table 2-2 Software requirements Item


Operating system

Microsoft Windows XP Professional

Default language of the operating system

English (United States)

Web browser

Microsoft Internet Explorer 5.5 or later

WARNING To guarantee stable system operation, the LMT application should be installed on a computer with the recommended configurations.

Communication Capability Requirements The computer on which the LMT application will be installed supports the TCP/IP protocols.

2-4


Issue 03 (2009-04-25)

RNC LMT User Guide

3 Components of the RNC LMT

3

Components of the RNC LMT

About This Chapter This describes the following software components of the RNC LMT: the local maintenance terminal, FTP client, trace viewer, monitor viewer, performance browser tool, and convert management system. 3.1 Local Maintenance Terminal of RNC The Local Maintenance Terminal is a subsystem of the LMT application. On the GUI of the Local Maintenance Terminal, you can perform tasks, such as authority management, equipment maintenance, message tracing, and real-time monitoring. The Local Maintenance Terminal supports many Man Machine Language (MML) commands for system configuration and maintenance. In addition, it provides detailed online help. To use the Local Maintenance Terminal for online OM, ensure that the LMT communicates with the BAM server properly. 3.2 FTP Client of RNC LMT The FTP Client is an FTP tool for the LMT application. It enables the LMT to communicate with the FTP server through the FTP protocol. 3.3 Trace Viewer of RNC LMT You can use the Trace Viewer to open tracing files (*.tmf) to view tracing data and recur the tracing situations. The Trace Viewer is an offline tool. It can be used when the LMT and the BAM are disconnected. 3.4 Monitor Viewer of RNC LMT You can use the Monitor Viewer to open monitoring files (*.mrf) to view monitoring data and recur the monitoring situations. The Monitor Viewer is an offline tool. It can be used when the LMT and the BAM are disconnected. 3.5 Performance Browser Tool of RNC LMT Through the Performance Browser Tool, you can browse the performance measurement results saved on the NE directly at the NE side. You can also manually import the NE measurement files, and then export and browse the performance measurement results for facilitating viewing and arranging the performance files. 3.6 Convert Management System of RNC LMT

Issue 03 (2009-04-25)


3-1

RNC LMT User Guide


The Convert Management System is a subsystem in the RNC LMT application. It is used to convert the alarm information, control information on the alarm box, and status information on the alarm box between the BAM and the alarm box.

3-2


Issue 03 (2009-04-25)

RNC LMT User Guide


3.1 Local Maintenance Terminal of RNC The Local Maintenance Terminal is a subsystem of the LMT application. On the GUI of the Local Maintenance Terminal, you can perform tasks, such as authority management, equipment maintenance, message tracing, and real-time monitoring. The Local Maintenance Terminal supports many Man Machine Language (MML) commands for system configuration and maintenance. In addition, it provides detailed online help. To use the Local Maintenance Terminal for online OM, ensure that the LMT communicates with the BAM server properly.

Interface Figure 3-1 shows the main interface of the Local Maintenance Terminal. Figure 3-1 Main interface of the Local Maintenance Terminal

Table 3-1 describes the numbered interface components of Local Maintenance Terminal. Table 3-1 Main interface of the Local Maintenance Terminal

Issue 03 (2009-04-25)

Num ber

Field

Description

1

Menu bar

Displays menus for system operation.

2

Toolbar

Provides shortcut icons for system operation.


3-3

RNC LMT User Guide


Num ber

Field

Description

3

Navigation pane

Displays the operation objects in the tree structure.

4

Object area

l

Performs system operation.

l

Displays details of operation objects.

l

Displays the MML client when MML Command is active in the navigation tree pane.

5

Status bar

Displays the name of the current user, the connection status, and the virtual external IP address of the BAM server.

Online Help The Local Maintenance Terminal provides two kinds of online help: l

Local Maintenance Terminal system help

l

MML help

Table 3-2 lists the contents and startup modes of the two kinds of help. Table 3-2 Online help of the Local Maintenance Terminal Name

Content

Startup Mode

Local Maintenance Terminal system help

This help provides:

In the Local Maintenance Terminal window,

MML help

3-4

l

l

Meanings of the fields in dialog boxes Function descriptions and operation guidelines of the Local Maintenance Terminal

l

Detailed information on boards

l

Detailed information on alarms

l

Terms and abbreviations

This help provides the following information for each MML command: l

Function

l

Note

l

Parameter

l

Example

l

Output description (only for query commands)

l

press F1 or choose Help > Help Topics.

l

when a dialog box is displayed in the window, press F1 to display the help information for this dialog box.

Input a command on the MML client, and press Enter. The Help Information window displays the help information about this command.


Issue 03 (2009-04-25)

RNC LMT User Guide


3.2 FTP Client of RNC LMT The FTP Client is an FTP tool for the LMT application. It enables the LMT to communicate with the FTP server through the FTP protocol.

Interface Figure 3-2 shows the main interface of the FTP Client. Figure 3-2 Main interface of the FTP Client

Table 3-3 describes the interface components on the main interface of the FTP Client. Table 3-3 Main interface of the FTP Client

Issue 03 (2009-04-25)

Number

Field

Description

1

Menu bar

Provides menus for system operation.

2

Toolbar


3

Local directory list pane

Displays directories that are in use.

4

Server file list pane

Displays the files and folders in the connected FTP server.

5

Local file list pane

Displays the files and folders in the chosen directory.


3-5

RNC LMT User Guide


Number

Field

Description

6

Connection tip pane

Displays the operation information and the status of the connection with the FTP server.

7

Server entry bar

Includes the server name, user name, password, port number, and mode.

Online Help Table 3-4 describes the online help of the FTP Client. Table 3-4 Online help of the FTP Client Content

Startup Method

Instructions about how to use the data management, the file management, and the transfer functions of the FTP Client

On the FTP Client window, press F1 or choose Help > Help Topics.

3.3 Trace Viewer of RNC LMT You can use the Trace Viewer to open tracing files (*.tmf) to view tracing data and recur the tracing situations. The Trace Viewer is an offline tool. It can be used when the LMT and the BAM are disconnected.

Interface Figure 3-3 shows the main interface of the Trace Viewer. Figure 3-3 Main interface of the Trace Viewer

3-6


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 3-5 describes the interface components on the main interface of the Trace Viewer. Table 3-5 Main interface of the Trace Viewer Number

Field

Description

1

Menu bar


2

Toolbar


3

Message browse window

Displays contents of .tmf files.

Online Help Table 3-6 describes the online help of the Trace Viewer. Table 3-6 Online help of the Trace Viewer Content

Startup Method

Instructions about how to use the message browse functions of the Trace Viewer

In the Trace Viewer window, press F1 or choose Help > Help Topics.

3.4 Monitor Viewer of RNC LMT You can use the Monitor Viewer to open monitoring files (*.mrf) to view monitoring data and recur the monitoring situations. The Monitor Viewer is an offline tool. It can be used when the LMT and the BAM are disconnected.

Interface Figure 3-4 shows the main interface of the Monitor Viewer.

Issue 03 (2009-04-25)


3-7

RNC LMT User Guide


Figure 3-4 Main interface of the Monitor Viewer

Table 3-7 describes the interface components on the main interface of the Monitor Viewer. Table 3-7 Main interface of the Monitor Viewer Number

Field

Description

1

Menu bar


2

Toolbar


3

Monitoring data browse pane

Displays the data and information on monitoring tasks.

4

Task information pane

Specifies whether to display the task information and how the graphs and lines are displayed.

Online Help Table 3-8 describes the online help of the Monitor Viewer. Table 3-8 Online help of the Monitor Viewer

3-8

Content

Startup Method

Instructions about how to use the message browse functions of the Monitor Viewer

In the Monitor Viewer window, press F1 or choose Help > Help Topics.


Issue 03 (2009-04-25)

RNC LMT User Guide


3.5 Performance Browser Tool of RNC LMT Through the Performance Browser Tool, you can browse the performance measurement results saved on the NE directly at the NE side. You can also manually import the NE measurement files, and then export and browse the performance measurement results for facilitating viewing and arranging the performance files.

Interface Figure 3-5 shows the main interface of the Performance Browser Tool. Figure 3-5 Main interface of the Performance Browser Tool

Table 3-9 describes the interface components on the main interface of the Performance Browser Viewer. Table 3-9 Main interface of the Performance Browser Tool

Issue 03 (2009-04-25)

Number

Field

Description

1

Menu bar


2

Toolbar


3

Navigation pane

Displays the measurement result files in the tree structure.


3-9

RNC LMT User Guide


Number

Field

Description

4

Detailed information pane

Displays the detailed information on the selected performance item file.

Online Help Table 3-10 describes the online help of the Performance Browser Tool. Table 3-10 Online help of the Performance Browser Tool Content

Startup Method

Explaining how to use performance description files

In the Performance Browser Tool window, press F1 or choose Help > Help Topics.

Performance description files are used to import NEs in the Performance Browser Tool. Explaining how to export and browse result files

3.6 Convert Management System of RNC LMT The Convert Management System is a subsystem in the RNC LMT application. It is used to convert the alarm information, control information on the alarm box, and status information on the alarm box between the BAM and the alarm box.

Function The Convert Management System performs the following functions: l

Enabling the communication between the LMT and the BAM through the Ethernet port

l

Enabling the communication between the LMT and the alarm box through the serial port

l

Forwarding operating instructions to the alarm box. The instructions include: –

Querying status of alarm indicators

–

Querying alarm box version

–

Turning off alarm light

–

Stopping alarm sound

–

Resetting alarm box

In this way, you can operate the alarm box on the LMT. l

Forwarding alarms to the alarm box which displays audio and visual alarms

l

Monitoring the communication between the LMT and the BAM, in addition to the communication between the LMT and the alarm box in real time. When a fault occurs, the Convert Management System reports the fault to the LMT.

Interface Figure 3-6 shows the main interface of the Convert Management System. 3-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 3-6 Main interface of the Convert Management System

Table 3-11 describes the interface components on the main interface of the Convert Management System. Table 3-11 Main interface of the Convert Management System Number

Field

Description

1

Menu bar


2

Toolbar


3

Output pane

Displays the output information on the Convert Management System the in real time.

Online Help Table 3-12 describes the online help of the Convert Management System. Table 3-12 Online help of the Convert Management System

Issue 03 (2009-04-25)

Content

Startup Method

Descriptions of the functions of the Convert Management System and instructions about how to use the functions

In the Convert Management System window, press F1 or choose Help > Help Topics.


3-11

RNC LMT User Guide

4 Installing the RNC LMT Application

4

Installing the RNC LMT Application

This describes how to install the RNC LMT application. This task takes V200R011C00SPC100 as an example.

Prerequisite l

The setup disk and the instructions on the LMT application installation are available. Huawei provides both the disk and the instructions.

l

The valid CD-KEY of the LMT application is available.

l

The PC on which the LMT application will be installed meets all the requirements listed in 2.4 Computer Requirements of the LMT.

Procedure Step 1 Use the administrator account to log in to the Windows XP operating system. Step 2 Insert the setup disk into the CD-ROM drive. l

The setup program runs automatically. A dialog box is displayed, as shown in Figure 4-1.

l

If the setup program fails to run automatically, double-click setup.bat or setup.vbs in the directory of the setup disk. A dialog box is displayed, as shown in Figure 4-1.

Figure 4-1 Selecting a setup language

Issue 03 (2009-04-25)


4-1


RNC LMT User Guide

CAUTION If the setup languages of the LMT and BAM applications are different, some functions are unavailable, for example, managing the RNC LMT operator accounts. It is recommended to keep the two languages consistent. Step 3 Select a language for the installation, and then click OK to start up. Step 4 Click Next. A dialog box is displayed, as shown in Figure 4-2. Figure 4-2 Copyright notice

Step 5 Read the copyright notice. If you accept the agreement terms, select I accept these terms, and then click Next. The installation directory is displayed, as shown in Step 6. If you do not accept the agreement terms, click Cancel to quit the installation. Step 6 Use the default directory or set up a new directory, and then click Next.

4-2

l

If the installation directory does not exist, a dialog box is displayed, prompting whether to create the directory. Click Yes. A dialog box is displayed, as shown in Figure 4-3.

l

If the installation directory exists, A dialog box is displayed, as shown in Figure 4-3.


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 4-3 Selecting software components

NOTE

The default installation path is D:\HW LMT. If the LMT application of other versions or of other Network Elements (NEs) has already been installed, the default installation path is the path of the previous installation and cannot be changed. To change the installation path, you must uninstall the existing LMT application. If an LMT application is running, the Warning dialog box is displayed. If you click Yes, the LMT application is automatically stopped. If you click No, you need to manually stop the LMT application.

Step 7 Select the software components and then click Next. It is recommended that you select all components. A dialog box is displayed for entering the CD-KEY. Step 8 Enter the CD-KEY correctly, and then click Next. A dialog box is displayed for confirming the installation, as shown in Figure 4-4.

Issue 03 (2009-04-25)


4-3


RNC LMT User Guide

Figure 4-4 Confirming installation

Step 9 Confirm the installation parameters and click Next. A dialog box is displayed for copying files. When the task of copying files is complete, a dialog box is displayed for initializing components. When all programs are installed, the dialog box for completing the installation is displayed. Step 10 Click Finish. NOTE

The installation is complete. When the installation is complete, the LMT Service Manager automatically starts.

----End

4-4


Issue 03 (2009-04-25)

RNC LMT User Guide

5 Getting Started with the RNC LMT

5

Getting Started with the RNC LMT

About This Chapter This describes how to start, configure, use, and quit the LMT application. When running the LMT application, ensure that the free space of the hard disk is no less than 1 GB. 5.1 Setting the IP Address of the RNC LMT PC This describes how to set the IP address of the LMT PC. When the network segment where the RNC LMT is located changes, you need to set the IP address of the LMT PC again. This task takes the connection between the LMT and the BAM server as an example to describes how to set the IP address of the LMT PC. 5.2 Connecting the RNC LMT to the BAM This describes how to connect the LMT to the OM network by providing an example of connecting the LMT to the BAM through the LAN. This task is only performed before the LMT is used for the first time. 5.3 Starting the Local Maintenance Terminal of the RNC This describes how to start the LMT and connect it to the specified RNC. This task takes the Local user account as an example to describe how to log in to the RNC on the LMT. 5.4 Setting the Properties of the RNC Local Maintenance Terminal This describes how to set the following related properties of the LMT: maximum output lines, auto locking, MML command timeouts, output to file, and save commands. 5.5 Configuring the Identity Certificate This describes how to configure the identity certificate. You need to configure the identity certificate before you log in to the LMT in encryption mode. 5.6 Setting the Office Information on the RNC LMT This describes how to set the office information in connected mode on the LMT. You can add, modify, or delete an office. 5.7 Locking the Local Maintenance Terminal of the RNC This describes how to lock the RNC Local Maintenance Terminal to avoid any access to the LMT by unauthorized operators. Before you leave the LMT, you are required to manually lock the Local Maintenance Terminal. 5.8 Unlocking the Local Maintenance Terminal of the RNC Issue 03 (2009-04-25)


5-1

RNC LMT User Guide


This describes how to unlock the Local Maintenance Terminal. If the Local Maintenance Terminal is locked, you need to unlock it before using it. 5.9 Exiting the Local Maintenance Terminal of the RNC This describes how to exit the Local Maintenance Terminal after you finish using Local Maintenance Terminal.

5-2


Issue 03 (2009-04-25)

RNC LMT User Guide


5.1 Setting the IP Address of the RNC LMT PC This describes how to set the IP address of the LMT PC. When the network segment where the RNC LMT is located changes, you need to set the IP address of the LMT PC again. This task takes the connection between the LMT and the BAM server as an example to describes how to set the IP address of the LMT PC.

Prerequisite The new IP address, subnet mask, and default gateway of the LMT PC are determined.

Context To set the IP address of the LMT PC, observe the following principles: l

If you connect the LMT to the BAM server through a LAN, the IP address of the LMT and the external virtual IP address of the BAM server must be in the same network segment.

l

If you connect the LMT to the BAM server through a router, the IP address of the LMT and the external virtual IP address of the BAM server can be in different network segments.

Procedure Step 1 On the LMT PC, choose Start > Control Panel and double-click Network Connections. Step 2 Right-click the LMT local area connection and choose Property from the shortcut menu. The Local Area Connection Properties dialog box is displayed, as shown in Figure 5-1.

Issue 03 (2009-04-25)


5-3

RNC LMT User Guide


Figure 5-1 Local Area Connection Properties dialog box

Step 3 Click the General tab, and then select Internet Protocol (TCP/IP). Step 4 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed, as shown in Figure 5-2.

5-4


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 5-2 Internet Protocol (TCP/IP) Properties dialog box

Step 5 Click the General tab, and then select Use the following IP address. Set an IP address that is in the same network segment as the external virtual IP address of the BAM. Set the subnet mask and the default gateway the same as those of the BAM. Step 6 Click OK. The system returns to the Local Area Connection Properties dialog box shown in Figure 5-1. Step 7 Click OK to complete the setting. ----End

5.2 Connecting the RNC LMT to the BAM This describes how to connect the LMT to the OM network by providing an example of connecting the LMT to the BAM through the LAN. This task is only performed before the LMT is used for the first time.

Prerequisite l

The BAM communicates with the RNC host properly.

l

The physical connection between the LMT and the BAM is established and functional.

Issue 03 (2009-04-25)


5-5

RNC LMT User Guide


Context You can connect the LMT to the BAM through a LAN or a router.

Procedure Step 1 To set the IP address of the LMT PC, refer to Setting the IP Address of the RNC LMT PC. Step 2 On the LMT PC, choose Start > Run, enter the cmd command in the Run dialog box, and then press Enter. The cmd.exe window is displayed. Step 3 Enter ping BAM external virtual IP address in the cmd.exe window. If the window displays similar information as follows, the communication between the LMT and the BAM is functional. The task is complete. In this example, the external virtual IP address of the BAM is 10.161.197.206. Pinging 10.161.197.206 with 32 bytes of data: Reply from 10.161.197.206: bytes=32 time<1ms TTL=125 Reply from 10.161.197.206: bytes=32 time<1ms TTL=125 Reply from 10.161.197.206: bytes=32 time<1ms TTL=125 Reply from 10.161.197.206: bytes=32 time<1ms TTL=125 Ping statistics for 10.161.197.206: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

----End

5.3 Starting the Local Maintenance Terminal of the RNC This describes how to start the LMT and connect it to the specified RNC. This task takes the Local user account as an example to describe how to log in to the RNC on the LMT.

Prerequisite l

The physical link connecting the LMT to the BAM is established.

l

The LMT application is installed correctly.

Context

WARNING When the LMT application is running, do not modify the system time. Otherwise, serious errors may occur on the system. If you have to modify the system time, stop all the LMT application first.

Procedure Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Local Maintenance Terminal. The User Login dialog box is displayed, as shown in Figure 5-3. 5-6


Issue 03 (2009-04-25)

RNC LMT User Guide


If this is the first time to start the LMT? Then... Yes

Go to Step 2.

No

Select the office to be connected in the Office drop-down list, and then go to Step 6.

Figure 5-3 User Login dialog box

NOTE

l

Click Offline to log in to the LMT offline. In this way, you do not log in to the BAM, but still can perform part of the functions of the LMT. For example, you can browse the online help.

l

Click Exit to exit the LMT.

Step 2 Click

. The Office Management dialog box is displayed, as shown in Figure 5-4.

Figure 5-4 Office Management dialog box before adding an office

Issue 03 (2009-04-25)


5-7

RNC LMT User Guide


Step 3 Click Add. The Add dialog box is displayed, as shown in Figure 5-5. Figure 5-5 To add an office, perform the following steps:

Step 4 Set the office name and enter the external virtual IP address of the BAM. Click OK. The system returns to the Office Management dialog box shown in Figure 5-6. NOTE

If the LMT PC is installed with the LMTs of other Network Elements (NEs) such as SGSN, you can select one NE from the NE Type drop-down list, and then set the office for the NE.

Figure 5-6 Office Management dialog box after adding an office

Step 5 In the Office Management dialog box, click Close. The system returns to the User Login dialog box, as shown in Figure 5-7. 5-8


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 5-7 User Login dialog box

Step 6 Enter the user name and password, and then click Login. The main interface of the Local Maintenance Terminal is displayed. NOTE

l

Before logging in to an NE as an EMS user on the LMT, you need to set up the connection between the NE and the M2000 server.

l

If the LMT communicates with the BAM through the M2000 Proxy Server, select the Proxy Server in the User Login dialog box and then enter the IP address of the proxy server.

l

Log in with the account of admin for the first login. The password is set during the installation of the BAM application.

l

If you log in to the LMT in Offline mode, you can use only a part of functions, such as viewing MML command help.

----End

5.4 Setting the Properties of the RNC Local Maintenance Terminal This describes how to set the following related properties of the LMT: maximum output lines, auto locking, MML command timeouts, output to file, and save commands.

Prerequisite l

The LMT is started and connected to the RNC.

l

You have logged in to the RNC with an account authorized for this task.

l

Setting maximum output lines

Procedure 1.

Issue 03 (2009-04-25)

In the Local Maintenance Terminal window, choose System > System Setting. The System Setting dialog box is displayed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-9

RNC LMT User Guide


2.

Click the Output Window tab and set Maximum Output Lines. NOTE

When the number of lines reaches the maximum, the system deletes the earliest lines to display new ones.

l

Setting auto locking 1.

In the Local Maintenance Terminal window, choose System > System Setting. The System Setting dialog box is displayed.

2.

Click the Terminal tab, select Automatically locked, and then set the time to automatically lock the client. NOTE

If the terminal stays in the idle state longer than the set time, the system automatically locks the terminal.

l

Setting MML command timeouts 1.

In the Local Maintenance Terminal window, choose System > Command Timeout Setting.

2.

In the Command Timeout Setting dialog box, set MML Command Timeout. NOTE

This property specifies the time limit for the communication between the LMT and the BAM through MML commands. When the time is out, and the LMT still receives no response from the BAM, the system prompts for the delay.

l

Setting output to file 1.

In the Local Maintenance Terminal window, choose System > Output Window Setting.

2.

In the Output Window Setting dialog box, set the parameters. NOTE

Some reports may be too large to be displayed in the output pane. By this property, you can specify a period of time during which the system saves all reports in files for later viewing. The setting is valid only for the current login.

l

Setting save commands 1.

In the Local Maintenance Terminal window, choose System > Save Input Commands.

2.

In the Save Input Commands dialog box, set the parameters. NOTE

By this property, you can set the system to save the successfully-run MML commands, the MML commands that fails to be run, or the both. By default, the system does not automatically save all MML commands.

----End

5.5 Configuring the Identity Certificate This describes how to configure the identity certificate. You need to configure the identity certificate before you log in to the LMT in encryption mode.

5-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

You have logged in to the LMT offline.

l

The identity certificate is ready.

Context

CAUTION You can log in to the LMT in encryption mode only after you log in to the LMT offline and configure the identity certificate.

Procedure Step 1 On the LMT, choose System > Certificate Configuration. The Certificate Configuration dialog box is displayed, as shown in Figure 5-8. Figure 5-8 Certificate Configuration dialog box

Step 2 On the ID Certificate tab page in the Certificate Configuration dialog box, specify File Name or click Issue 03 (2009-04-25)

. The Open dialog box is displayed, as shown in Figure 5-9. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-11

RNC LMT User Guide


Figure 5-9 Open dialog box

Step 3 Select the certificate file, and then click Open. The system returns to the Certificate Configuration dialog box. Specify PFX Password, and then click OK. The certificate is successfully configured. NOTE

PFX Password which is assigned during the application for the certificate is the password of the certificate file.

----End

5.6 Setting the Office Information on the RNC LMT This describes how to set the office information in connected mode on the LMT. You can add, modify, or delete an office.

Prerequisite The LMT is started.

Context By adding an office, you can set up a connected office to operate and maintain the office on the LMT. By modifying an office, you can change the name and IP address of the office. By deleting an office, you can remove the information on an existing office on the LMT.

5-12


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure l

To add an office, perform the following steps: 1.

On the LMT, choose System > Office Management. The Office Management dialog box is displayed, as shown in Figure 5-10.

Figure 5-10 Office Management dialog box

2.

Click Add in the Office Management dialog box. The Add dialog box is displayed, as shown in Figure 5-11. Figure 5-11 Adding an office

Issue 03 (2009-04-25)

3.

Select an NE if necessary, set the office name, and enter the external virtual IP address of the BAM server.

4.

Click OK. The system returns to the Office Management dialog box. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-13

RNC LMT User Guide


5. l

Click Close to end the operation.

To modify an office, perform the following steps: 1.


2.

Select the office to be modified. Click Modify. The Modify dialog box is displayed, as shown in Figure 5-12. Figure 5-12 Modifying an office

l

l

5-14

3.

Change the office name, IP address or NE type as required.

4.

Click OK. The system returns to the Office Management dialog box.

5.


To delete an office, perform the following steps: 1.


2.

Select the office to be deleted, and then click Delete. The Confirm dialog box is displayed.

3.

Click Yes. The system returns to the Office Management dialog box.

4.


To import an office, perform the following steps: 1.


2.

Click Import. The Open dialog box is displayed, as shown in Figure 5-13.


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 5-13 Open dialog box

3. l

l

Select the office information to be imported, and then click Open. A dialog box is displayed, indicating that the office information is successfully imported.

To export an office, perform the following steps: 1.


2.

Select the office to be exported, and then click Export. The Open dialog box is displayed, as shown in Figure 5-13.

3.

Click Save. A dialog box is displayed, indicating that the office information is successfully exported.

To log in to the LMT in encryption mode, perform the following steps: NOTE

Logging in to the LMT in encryption mode is optional.

Issue 03 (2009-04-25)

1.

Log in to the LMT offline, and then configure the identity certificate.

2.

Login in to the LMT online, and then choose System > Office Management. The Office Management dialog box is displayed, as shown in Figure 5-10.

3.

In the Add or Modify dialog box, set Connect Type to SSL, and then log in to the LMT in encryption mode, as shown in Figure 5-14.


5-15

RNC LMT User Guide


Figure 5-14 Adding an office

NOTE

l

Protocol Version can be set to SSLv3, TLSv1, or TLSv1.1.

l

The involved encryption algorithm varies by Algorithm Intensity.

l

Authentication Mode can be set to Authenticate the peer or Do not authenticate the peer.

4.

Click OK. The system returns to the Office Management dialog box.

5.


----End

5.7 Locking the Local Maintenance Terminal of the RNC This describes how to lock the RNC Local Maintenance Terminal to avoid any access to the LMT by unauthorized operators. Before you leave the LMT, you are required to manually lock the Local Maintenance Terminal.


Context Lock the Local Maintenance Terminal in any of the following ways:

Procedure l

Choose System > Lock.

l

Press Ctrl+Alt+M.

l

Click the shortcut icon

.

----End 5-16


Issue 03 (2009-04-25)

RNC LMT User Guide


Result After the LMT is locked, the Terminal Locked dialog box is displayed.

5.8 Unlocking the Local Maintenance Terminal of the RNC This describes how to unlock the Local Maintenance Terminal. If the Local Maintenance Terminal is locked, you need to unlock it before using it.

Prerequisite The LMT is locked and the Terminal Locked dialog box is displayed.

Procedure Step 1 In the Terminal Locked dialog box, press Ctrl+Alt+U. The Unlock Terminal dialog box is displayed. Step 2 Enter the password, and then click OK. ----End

5.9 Exiting the Local Maintenance Terminal of the RNC This describes how to exit the Local Maintenance Terminal after you finish using Local Maintenance Terminal.

Procedure Step 1 To exit the Local Maintenance Terminal, use one of the following methods: l

Choose System > Exit.

l

Press Alt+X.

l

Click

.

Step 2 Click OK in the displayed Confirmation dialog box. You exit the Local Maintenance Terminal. ----End

Issue 03 (2009-04-25)


5-17

RNC LMT User Guide

6 Running RNC MML Commands

6

Running RNC MML Commands

About This Chapter This describes how to run MML commands on the Local Maintenance Terminal to perform comprehensive operations and maintenance on the RNC system. 6.1 Concepts of RNC MML Commands This describes the following concepts of RNC MML commands: the MML commands, MML client, and policies for RNC configuration failure handling. 6.2 Starting the RNC MML Client This describes how to start the RNC MML client. Before running the MML commands, you need to start the MML client. When the LMT is started, the MML client is started by default. If the current interface is not the MML client, refer to the methods described in this task. 6.3 Viewing the Ownership of RNC Data Configuration Right This describes how to check the ownership of the RNC data configuration right. 6.4 Obtaining the RNC Data Configuration Right This describes how to obtain the ownership of the RNC data configuration right. Before you perform the data configuration operations, you need to obtain the ownership of the RNC data configuration right. Only the M2000 users and users of the following levels can obtain the data configuration right: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to use command group G_3 (for data configuration). 6.5 Running a Single MML Command This describes how to run the MML commands one by one on the MML client. The task is performed for the system configuration and routine maintenance. 6.6 Batch Running MML Commands This describes how to run multiple MML commands at a time. By running a batch file of commands, you are freed from manually running MML commands one by one. 6.7 Undoing a Single RNC Data Configuration Action This describes how to undo a single RNC data configuration action. After this task is performed, the RNC system can be restored to the state in which the single data configuration action is not performed. 6.8 Redoing a Single RNC Data Configuration Action Issue 03 (2009-04-25)


6-1

RNC LMT User Guide


This describes how to redo a single RNC data configuration action. After this task is performed, the RNC system can be restored to the state in which the single data configuration action is not undone. 6.9 Undoing Multiple RNC Data Configuration Actions This describes how to undo multiple RNC data configuration actions. After this task is performed, the RNC system is restored to the configuration of a specified rollback point. 6.10 Redoing Multiple RNC Data Configuration Actions This describes how to redo multiple RNC data configuration actions. After this task is performed, the RNC system is restored to the state in which the multiple data configuration actions are not undone.

6-2


Issue 03 (2009-04-25)

RNC LMT User Guide


6.1 Concepts of RNC MML Commands This describes the following concepts of RNC MML commands: the MML commands, MML client, and policies for RNC configuration failure handling. 6.1.1 Introduction to RNC MML Commands The Local Maintenance Terminal provides two operating modes: Graphic User Interface (GUI) and MML commands. The RNC supports many MML commands for system operation and maintenance. 6.1.2 Introduction to the RNC MML Client The MML client is integrated in the subsystem of the LMT. It provides the user interface for running the MML commands. 6.1.3 Policies for RNC Configuration Failure Handling The RNC provides different solutions for the RNC data configuration failures occurring when you run removing, adding, setting, or modifying commands in online mode. 6.1.4 RNC Data Configuration Right Management RNC data configuration right management enables only one user to perform RNC data configuration on only one configuration console at a time. The configuration console may be the LMT or the M2000. 6.1.5 RNC Data Configuration Rollback RNC data configuration rollback is performed to restore configurations when errors occur. If data configuration fails to achieve the expected result or even causes equipment or network faults, you can perform rollback to restore the configurations quickly. This ensures the proper running of the RNC.

6.1.1 Introduction to RNC MML Commands The Local Maintenance Terminal provides two operating modes: Graphic User Interface (GUI) and MML commands. The RNC supports many MML commands for system operation and maintenance. The format of the MML commands is action plus object, for example, ADD OP. Table 6-1 describes the actions of the MML commands. Table 6-1 Actions of the MML commands

Issue 03 (2009-04-25)

Action

Description

ACT

Activate

ADD

Add dialog box

ADT

Audit

BEG

Begin

BKP

Backup

BLK

Block


6-3

RNC LMT User Guide


6-4

Action

Description

CHK

Check

CLR

Clear

CMP

Compare

COL

Collect

CON

Confirm

DEA

Deactivate

DSP

Display

EST

Establish

EXP

Export

FMT

Format

FOC

Forcibly obtain

HO

Handover

INH

Inhibit

INS

Install

LCK

Lock

LOD

Load

LOP

Loop back test

LST

List

MOD

Modify

PING

Ping

REL

Release

REQ

Request

RUN

Run

RMV

Remove

RST

Reset

SET

Set

STR

Start/Open

STP

Stop/Close

STA

Collect statistics

SWP

Swap


Issue 03 (2009-04-25)

RNC LMT User Guide


Action

Description

SYN

Synchronize

TRC

Trace

UBL

Unblock

UIN

Uninhibit

ULD

Upload

ULK

Unlock

6.1.2 Introduction to the RNC MML Client The MML client is integrated in the subsystem of the LMT. It provides the user interface for running the MML commands. Figure 6-1 shows the MML client. Figure 6-1 MML client

Table 6-2 describes the fields identified with numbers.

Issue 03 (2009-04-25)


6-5

RNC LMT User Guide


Table 6-2 Fields on the MML client Number

Field

Description

1

Common Maintenance pane

Displays system feedbacks, for example, the execution results.

2

Operation Record

Displays the MML commands that have been executed and the related parameters.

3

Help Information pane

Displays the help information on a command.

4

Command input area

Displays the currently run command or the selected history command, and their parameter values.

5

History Command box

Displays the commands that the current operator has run after logging in to the system and the related parameters.

6

Command Input box

Displays in the drop-down list all the MML commands available on the system. You can select an MML command from the drop-down list or type in an MML command for execution.

7

Parameter area

Displays the parameters of the current command. You need to set parameter values in the boxes for the execution of the command. The parameters in red are mandatory to be set, and those in black are optional.

NOTE

For details of the MML commands and parameters, see the MML online help.

6.1.3 Policies for RNC Configuration Failure Handling The RNC provides different solutions for the RNC data configuration failures occurring when you run removing, adding, setting, or modifying commands in online mode.

Failure in Running Removing Commands Online When you fail to run a removing command in online mode, you can run the removing command repeatedly until the object data is successfully removed.

Failure in Running Adding Commands Online There are two failures in online running adding commands: l

If the target subrack or board is not in position, you need not to handle the failure.

l

If the target subrack or board is in position, you can online remove the failure data to ensure that the BAM and RNC restore to the state in which the data is not added. Then you can try to add the data again.

Failure in Running Setting or Modifying Commands There are two failures in online running setting or modifying commands: l

6-6

If the target subrack or board is not in position, you need not to handle the failure. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide

6 Running RNC MML Commands l

If the target subrack or board is in position, you can run the setting or modifying command repeatedly until the object data is successfully set or modified.

Policies for RNC Offline Configuration Failure Handling When the RNC fails to be configured in offline mode, you need to modify the configuration data and offline configure the data again.

6.1.4 RNC Data Configuration Right Management RNC data configuration right management enables only one user to perform RNC data configuration on only one configuration console at a time. The configuration console may be the LMT or the M2000. In case of conflicts during data configuration, the BAM manages the configuration right as follows: l

When the data configuration right control switch is ON, only one user has the data configuration right at a time. When the switch is OFF, no data configuration right control is applicable. You can run the SET CMCTRLSW command to set the switch to ON or OFF.

l

Before data configuration, the data configuration right must be obtained. The data configuration right is always occupied unless the user manually releases the right. That is, if the user is logged out and the right is not manually released, he or she can still has the data configuration right at the next login. The ADMINISTRATOR-level operators, however, can obtain the data configuration right by running the FOC CMCTRL command.

With the control, different users cannot configure data for the RNC at the same time. A user can perform data configuration for the RNC only after the user is granted the data configuration right.

6.1.5 RNC Data Configuration Rollback RNC data configuration rollback is performed to restore configurations when errors occur. If data configuration fails to achieve the expected result or even causes equipment or network faults, you can perform rollback to restore the configurations quickly. This ensures the proper running of the RNC.

Definition of Configuration Rollback During data configuration, a rollback point is used to identify a data configuration status. Rollback points can be set by users or automatically allocated by the RNC. Configuration rollback: By setting data configuration status to rollback points, the user can flexibly roll back or forward to any rollback point during the configuration, so as to roll back or forward to the expected data configuration status.

Operations of Configuration Rollback Configuration rollback is applicable when the data configuration right control switch is ON. You can run the SET CMCTRLSW command to set the switch to ON. RNC data configuration rollback consists of the following types of operation: Issue 03 (2009-04-25)


6-7

RNC LMT User Guide


Undoing a single configuration command: After undoing the command, the RNC rolls back to the configuration state that existed before the relevant command was run. This operation is applicable to only the previous ten configuration commands.

l

Redoing a single configuration command: After redoing the command, the RNC returns to the configuration state that existed after the relevant command was run. This operation is applicable to only the previous ten configuration commands that were rolled back.

l

Undoing configuration commands in batches: This operation is performed to undo all the configuration commands that were run after a specified rollback point. After the undoing, the RNC rolls back to the configuration of the specified rollback point.

l

Redoing configuration commands in batches: This operation is performed to redo the configurations that were rolled back in batches. After the redoing, the RNC returns to either the configuration of the specified rollback point or the configuration that existed before the undoing was performed.

6.2 Starting the RNC MML Client This describes how to start the RNC MML client. Before running the MML commands, you need to start the MML client. When the LMT is started, the MML client is started by default. If the current interface is not the MML client, refer to the methods described in this task.


Procedure l

l

Starting the MML client by using the navigation tree 1.

In the Local Maintenance Terminal window, click the MML Command tab below the left navigation tree to display the Navigation Tree pane.

2.

Double-click the MML Command node in the Navigation Tree pane to start the MML client.

Starting the MML client by clicking the icon 1.

Click the MML client icon

on the toolbar to start the RNC MML client.

----End

6.3 Viewing the Ownership of RNC Data Configuration Right This describes how to check the ownership of the RNC data configuration right.

Prerequisite You have logged in to the RNC LMT.

Context The returned result can be NULL, which indicates that no one owns this right currently. 6-8


Issue 03 (2009-04-25)

RNC LMT User Guide


To view the ownership of the data configuration right, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

Click the CM Control state drop-down list box on the toolbar in the Local Maintenance Terminal window. If the user is NULL, as shown in Figure 6-2, you can infer that no user owns the data configuration right currently. Figure 6-2 Data configuration user being NULL

If the user is admin, as shown in Figure 6-3, you can infer that admin owns the data configuration right currently. Figure 6-3 Data configuration user being admin

l

In MML mode 1.

Run the LST CMCTRL command to check the current data configuration user.

----End

6.4 Obtaining the RNC Data Configuration Right This describes how to obtain the ownership of the RNC data configuration right. Before you perform the data configuration operations, you need to obtain the ownership of the RNC data configuration right. Only the M2000 users and users of the following levels can obtain the data configuration right: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to use command group G_3 (for data configuration).

Prerequisite l

The LMT is started.

l


l

The switch of the data configuration right is set to OFF. (You can query this by running LST CMCTRLSW.)

Issue 03 (2009-04-25)


6-9

RNC LMT User Guide


Procedure Step 1 Check whether there are users who have the data configuration right. For details, refer to 6.3 Viewing the Ownership of RNC Data Configuration Right. l

If no users currently have the data configuration right, go to Step 2.

l

If there are users who have the data configuration right, go to Step 2 after the data configuration right is released.

Step 2 Run the REQ CMCTRL command to obtain the data configuration right. Step 3 Click the CM Control Information drop-down list to check the operation result. The data configuration right is owned by admin, as shown in Figure 6-4. Figure 6-4 Data configuration user being admin

NOTE

l

After one LMT user is granted with the data configuration right, other LMT users cannot obtain it. However, if you are admin or an ADMINISTRATOR-level user, you can use the FOC CMCTRL command to forcibly get back the data configuration right.

l

After one LMT user obtains the data configuration right and does not lock it, the right will be obtained by the M2000 user when the M2000 requests the right from the RNC.

----End

6.5 Running a Single MML Command This describes how to run the MML commands one by one on the MML client. The task is performed for the system configuration and routine maintenance.

Prerequisite l

You have logged in to the RNC LMT.

l

The MML client is started.

Context There are the following equivalent methods for running a single MML command: l

Entering an MML command in the command input box

l

Selecting a history command from the history command box

l

Copying a command and its parameter values to the command input area

l

Selecting an MML command from the MML Command navigation tree NOTE

You can set the switch of the data configuration right to ON by running SET CMCTRLSW. You can run only the query commands before you obtain the data configuration right.

6-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure l

Entering an MML command in the command input box 1.

Enter an MML command in the command input box.

2.

Press Enter or click

.

The command parameter area displays all the parameters of this command. 3.

Enter the parameter values in the command parameter area.

4.

Press F9 or click

on the right of the command input box to run the command.

The Common Maintenance pane displays the execution results. l

Selecting a history command from the history command box 1.

Select a history command from the drop-down list of the history command box. (Press F7 or click to select the previous history command. Press F8 or click the next history command.)

to select

The command parameter area displays all the parameters of this command. 2.

Change the parameter values in the command parameter area. This step is optional.

3.

Press F9 or click

to run the command.


Copying a command and its parameter values to the command input area 1.

Copy a command and its parameter values, and then paste them in the command input area.

2.

Press F9 or click

to run the command.


Selecting an MML command from the MML Command navigation tree 1.

Click the MML Command tab, and double-click an MML command in the navigation tree.

2.

Enter the parameter values in the command parameter area.

3.

Press F9 or click

to run the command.

The Common Maintenance pane displays the execution results. ----End

6.6 Batch Running MML Commands This describes how to run multiple MML commands at a time. By running a batch file of commands, you are freed from manually running MML commands one by one.

Prerequisite l


l

The MML client is started.

l

For data configuration, you have obtained the configuration management (CM) control right.

Issue 03 (2009-04-25)


6-11

RNC LMT User Guide


The batch file is ready.

Context The batch file (also called data script file) is a plain text file. It contains a group of command scripts for a special task. The system automatically runs the commands in sequence. The batch running of MML commands is of two types: l

Immediate execution

l

Time execution. You can preset the execution date and time. The system automatically executes the batch file at the preset execution time.

l

Immediate batch running of MML commands

Procedure 1.

In the Local Maintenance Terminal window, choose System > Batch Commands, or press Ctrl+E. The MML Batch pane is displayed, as shown in Figure 6-5.

Figure 6-5 Immediate batch running of MML commands

2.

On the Immediate Batch Command tab page, click New and enter the batch file name, or click Open and select the batch file.

3.

Set the parameters.

4.

Click Go to start running the commands. NOTE

It is recommended that you select Fault Prompt. It is selected by default. The batch running syntax checker helps you find out the wrong commands in the scripts before running the batch file. In this case, the wrong commands can be rectified before they are executed. Thus, errors are less likely to occur in the execution of the commands, and the OM efficiency is improved.

l 6-12

Scheduled batch running of MML commands Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


1.

In the Local Maintenance Terminal window, choose System > Batch Commands, or press Ctrl + E. The MML Batch pane is displayed, as shown in Figure 6-5.

2.

Click the Timer Batch Command tab, as shown in Figure 6-6.

Figure 6-6 Scheduled batch running of MML commands

3.

Click Add. The Add Batch Task dialog box is displayed.

4.

Select the batch file and then set the time batch running parameters.

5.

Click OK. The batch file is imported. Wait for the running. Do not close the MML Batch window. Otherwise, the scheduled task is removed.

----End

6.7 Undoing a Single RNC Data Configuration Action This describes how to undo a single RNC data configuration action. After this task is performed, the RNC system can be restored to the state in which the single data configuration action is not performed.

Prerequisite l


l

You have obtained the data configuration right (see 6.4 Obtaining the RNC Data Configuration Right), and have run one or more configuration commands successfully.

Context NOTE

This task is applicable to only the last 10 configuration commands that are run before the undoing.

Issue 03 (2009-04-25)


6-13

RNC LMT User Guide


Procedure l

In icon mode 1.

l

In the Local Maintenance Terminal window, click latest effective configuration command is undone.

on the toolbar. The

In MML mode 1.

Run the BEG UNDO command on the MML client.

----End

6.8 Redoing a Single RNC Data Configuration Action This describes how to redo a single RNC data configuration action. After this task is performed, the RNC system can be restored to the state in which the single data configuration action is not undone.

Prerequisite l


l

You have obtained the data configuration right (see 6.4 Obtaining the RNC Data Configuration Right), and have undone one or more configuration actions successfully.

Context NOTE

This task is applicable to only the last 10 configuration commands that are undone before the redoing.

Procedure l

In icon mode 1.

l

In the Local Maintenance Terminal window, click The configuration command that has been undone is redone.

on the toolbar.

In MML mode 1.

Run the BEG REDO command on the MML client.

----End

6.9 Undoing Multiple RNC Data Configuration Actions This describes how to undo multiple RNC data configuration actions. After this task is performed, the RNC system is restored to the configuration of a specified rollback point.

Prerequisite

6-14

l


l

You have obtained the data configuration right (see 6.4 Obtaining the RNC Data Configuration Right), and have run multiple configuration commands successfully. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Context NOTE

The initial rollback point is the first rollback point set by the user. The final rollback point is set automatically when the latest configuration command is successfully run. A maximum of 1,000 configuration commands can be undone between the initial and final rollback points. If the system finds more than 1,000 commands between the two rollback points, it does not undo the commands and reports a failure message. You can set at most five rollback points. If you release the configuration right, the BAM active workarea clears the information related to the rollback stack and rollback points.

Procedure Step 1 To undo/redo multiple configuration commands, you can run the ADD ROLLBACKPOINT command to set rollback points as required. Step 2 Run the BEG ROLLBACK command to undo the configuration commands. The RNC system rolls back to the configuration of the specified rollback point. ----End

6.10 Redoing Multiple RNC Data Configuration Actions This describes how to redo multiple RNC data configuration actions. After this task is performed, the RNC system is restored to the state in which the multiple data configuration actions are not undone.

Prerequisite l


l

You have obtained the data configuration right (see 6.4 Obtaining the RNC Data Configuration Right), and have undone multiple configuration actions successfully.

Procedure Run the BEG FORWARD command to redo the multiple configuration actions. You can restore the configuration to the state at the specified rollback point or to the state before the undoing is performed. ----End

Issue 03 (2009-04-25)


6-15

RNC LMT User Guide

7

7 Managing Authorities for RNC Operations

Managing Authorities for RNC Operations

About This Chapter This describes how to manage the authorities for the RNC operations. To manage the authorities for the RNC operations is to manage the operator accounts, operator passwords, and RNC command groups. 7.1 Concepts of RNC Authority Management This describes the following concepts of the RNC authority management: principles of the RNC authority management, command groups, user classes, operator identity, operation authorities, operator password, and operating time limit. 7.2 Managing RNC LMT Operator Accounts This describes how to manage the RNC LMT operator accounts. To manage the operator accounts is to add external operator accounts, modify the properties of the operator accounts, and delete external operator accounts. 7.3 Managing RNC LMT Operator Passwords This describes how to manage the RNC LMT operator passwords. To manage the operator passwords is to set and query the policies for the login passwords, modify the password of the active user, and modify the password of an external operator. 7.4 Managing RNC Command Groups This describes how to manage RNC command groups. To manage RNC command groups is to query group information, set group names, and modify group contents.

Issue 03 (2009-04-25)


7-1


RNC LMT User Guide

7.1 Concepts of RNC Authority Management This describes the following concepts of the RNC authority management: principles of the RNC authority management, command groups, user classes, operator identity, operation authorities, operator password, and operating time limit. 7.1.1 Principles of RNC Authority Management This describes the principles for the RNC authority management from the following aspects: operator identity, operation authority, and operating time limit. 7.1.2 RNC LMT Operator Password This describes the RNC LMT operator password from the following aspects: the definition of the operator password, initial password setting, and authority for changing the password. 7.1.3 RNC Command Groups The RNC system provides 32 command groups (G_0 to G_31). Each group has different functions. 7.1.4 RNC LMT User Types RNC LMT users are of the following types: Local users and EMS users. 7.1.5 RNC LMT Operator Authorities The LMT operators can be divided into the internal operators and external operators. This describes the authorities of these two types of operators individually. 7.1.6 RNC LMT Operating Time Limits This describes the RNC LMT operating time limits from the following aspects: the definition, principle, and authority.

7.1.1 Principles of RNC Authority Management This describes the principles for the RNC authority management from the following aspects: operator identity, operation authority, and operating time limit. The RNC OM subsystem supports multi-user operation. For the system security, the system uses the authority management which includes the following aspects: l

Operator identity. An operator must enter the correct user name and password to log in to the system.

l

Operation authority. Operators of different types are authorized to use different command groups for GUI or MML operations. The RNC categorizes operators into different types and provides different command groups for each type as a way to control operation authority.

l

Operation time limit. An operator can operate the RNC only in an account-specific period.

7.1.2 RNC LMT Operator Password This describes the RNC LMT operator password from the following aspects: the definition of the operator password, initial password setting, and authority for changing the password.

Definition of Operator Password To ensure the system security, each operator account has a password. When starting the LMT, an operator must enter a valid user name and a correct password to log in to the BAM. 7-2


Issue 03 (2009-04-25)

RNC LMT User Guide


The operator authorized for the ADMINISTRATOR-level operations can also set the password complexity through Password Policy Setting.

Initial Password Setting The password of admin is set during the installation of the BAM application. The password of an external operator can be set by the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators during account addition.

Authority for Changing Passwords Any operator can change his or her own password. The admin and the ADMINISTRATORlevel and authorized CUSTOM-level operators can change the passwords of all external operators. Only the admin operator can change the admin password. For details, refer to Changing Your Password and Changing Passwords of External Operator Accounts.

7.1.3 RNC Command Groups The RNC system provides 32 command groups (G_0 to G_31). Each group has different functions. Table 7-1 lists the 32 command groups (G_0 to G_31) that the system provides. Table 7-1 Command groups Command Group

Function

Description

G_0

Used to query system information, including all MML query commands

l

G_1

Used to manage system information, including all MML commands

l

G_2

Used to query data configuration information, for example, to query the cell data or the AAL2 path data

G_3

Used to configure data, for example, to add a cell or an AAL2 path

G_4

Used to query alarm information, for example, to query an alarm log or the alarm box version

G_5

Used to manage alarms, for example, to manually clear alarms or to reset the alarm box

G_6

Used to query performance information, for example, to query a performance measurement task or the type of the measurement object

G_7

Used to manage performance, for example, to create a measurement task or a custom measurement counter

l

Issue 03 (2009-04-25)


Predefined by the system Cannot be changed Can be queried

7-3

RNC LMT User Guide


Command Group

Function

G_8

Used to query equipment statuses and information, for example, to query the statuses of E1/T1 links or the rack information

G_9

Used to manage equipment

G_10

Used to perform the functions of the Tracing node and the Realtime Performance Monitoring node in the Maintenance tab page in the Local Maintenance Terminal window

G_11

Used to perform all the functions in the Integrated Equipment Test tab page in the Local Maintenance Terminal window

G_12–G_31

Set to null initially and can be defined by the following operators: admin, ADMINISTRATORlevel operators, and authorized CUSTOM-level operators

Description

Binary command groups predefined by the system Cannot be changed or queried

Can be queried and changed

For the operations related to command groups, refer to Managing RNC Command Groups.

7.1.4 RNC LMT User Types RNC LMT users are of the following types: Local users and EMS users. l

Local users: refer to the accounts (including the default local account admin) managed by only the RNC LMT. This type of LMT users can log in to the RNC during the RNC system installation and during the disconnection from the M2000.

l

EMS users: refer to the accounts managed by the M2000. The accounts of this type are created, modified, authenticated, and authorized by the M2000. After EMS users are authorized, they can log in to and manage the RNC on the LMT. EMS users can also log in to the M2000 server on the M2000 client to perform management operations.

7.1.5 RNC LMT Operator Authorities The LMT operators can be divided into the internal operators and external operators. This describes the authorities of these two types of operators individually.

Internal Operator The RNC system has a super administration account admin. The password is set during the BAM installation. This account has all operation authorities and cannot be changed or deleted.

External Operators External operators are divided into five levels. Each level has different authorities, as described in Table 7-2. 7-4


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 7-2 External operators of different levels Operator Level

Authorized Command Group

Authority

Description

GUEST

G_0, G_2, G_4, G_6, G_8

Data query

USER

G_0, G_2, G_4, G_6–G_11

l

Authorities of GUEST-level

l

System OM

The authorities are predefined by the system and cannot be changed.

G_0, G_2, G_3– G_11

l

Authorities of USER-level

l

Data configuration

ADMINISTRA TOR

G_1, G_10, G_11

All authorities

CUSTOM

Command groups assigned during account addition

Specified during account addition

OPERATOR

The authorities can be changed. The authorities of different CUSTOM-level operators can be different.

NOTE

l

The admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can add or delete accounts of external operators.

l

An authorized CUSTOM-level operator can perform operations on operator accounts and command groups only in MML mode.

7.1.6 RNC LMT Operating Time Limits This describes the RNC LMT operating time limits from the following aspects: the definition, principle, and authority.

Definition of Operation Time Limit The operation time limit refers to the period during which an operator can operate the system: l

There is no operation time limit for the admin account, which means that the admin operator can operate the system at any time.

l

The operation time limit of an external operator account is set during the account addition. If no time limit is set, the operator can operate the system at any time.

Principle of Operation Time Limit The operation time limit consists of date, day, and time. The allowable operation time is the combination of these settings. Table 7-3 lists some examples of operation time limit settings. Issue 03 (2009-04-25)


7-5

RNC LMT User Guide


Table 7-3 Examples of operation time limit settings SN

Date

Day

Time

Actual Operation Time

Example 1

2004-08-01 to 2005-08-01

Monday to Friday

8:00:00 to 18:00:00

From 8:00:00 to 18:00:00 every Monday to Friday between 2004-08-01 and 2005-08-01

Example 2

-

Saturday and Sunday

-

Any time on Saturday and Sunday

Example 3

-

-

-

No operation time limit, that is, the operator can operate the system at any time.

Authority to Set Operating Time Limit The admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can set or change the operation time limit of all external operator accounts.

7.2 Managing RNC LMT Operator Accounts This describes how to manage the RNC LMT operator accounts. To manage the operator accounts is to add external operator accounts, modify the properties of the operator accounts, and delete external operator accounts. 7.2.1 Adding an RNC LMT External Operator Account This describes how to add an external operator account. You are required to set the password, operator level, command group (for CUSTOM-level operators only), and operation time limit for a new external operator account. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can perform this operation. 7.2.2 Modifying the Properties of an RNC LMT External Operator Account This describes how to modify the properties of external operator accounts. The properties involve operator description, password, operator level, operation authorities, and operation time limit. Except for the password, all the modified information takes effect immediately. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the LMT operator properties. 7.2.3 Deleting an RNC LMT External Operator Account This describes how to delete an external operator account. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can perform this operation.

7.2.1 Adding an RNC LMT External Operator Account This describes how to add an external operator account. You are required to set the password, operator level, command group (for CUSTOM-level operators only), and operation time limit for a new external operator account. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can perform this operation.

Prerequisite l

7-6

The LMT is started. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide

7 Managing Authorities for RNC Operations l


Context To add an external operator account, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Authority > Account > Add. The Operator Management dialog box is displayed, as shown in Figure 7-1.

Figure 7-1 Operator Management dialog box

l

2.

Enter the operator account and password, and select the operator level from the Operator Definition drop-down list. If the level is Custom, select command groups in the Authority Limit pane.

3.

Set the operation time limit as required.

4.

Click OK. If the addition is successful, a dialog box is displayed, asking whether to add other operator accounts.

5.

Click Yes to add another account or click No to exit the setting.

In MML mode 1.

Issue 03 (2009-04-25)

Run the ADD OP command and add an external operator account on the MML client. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

7-7

RNC LMT User Guide


WARNING The newly added external operator account cannot be the same as any existing account. ----End

7.2.2 Modifying the Properties of an RNC LMT External Operator Account This describes how to modify the properties of external operator accounts. The properties involve operator description, password, operator level, operation authorities, and operation time limit. Except for the password, all the modified information takes effect immediately. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the LMT operator properties.

Prerequisite l

The LMT is started.

l


Context To modify the properties of external operator accounts, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Authority > Account > Modify. The Modify Operator dialog box is displayed, as shown in Figure 7-2. Figure 7-2 Modify Operator dialog box

7-8


Issue 03 (2009-04-25)

RNC LMT User Guide


2.

Select an operator account, and then click Modify. The Operator Management dialog box is displayed, as shown in Figure 7-3.

Figure 7-3 Operator Management dialog box

l

3.

Modify the properties as required, and then click OK. The dialog box prompting operation success is displayed.

4.

Click OK. The modification is complete.

In MML mode 1.

Run the MOD OP command and modify the properties of an operator account on the MML client.

----End

7.2.3 Deleting an RNC LMT External Operator Account This describes how to delete an external operator account. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can perform this operation.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


7-9

RNC LMT User Guide


Context To delete an RNC external operator account, you can use either of the following modes: GUI and MML. NOTE

The admin account cannot be deleted by any account because admin is a built-in operator account.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Authority > Account > Delete. The Delete Operator dialog box is displayed, as shown in Figure 7-4. Figure 7-4 Deleting an operator

l

2.

Select the account to be deleted, and then click Delete. The dialog box is displayed, asking whether to delete the account.

3.

Click Yes. The system returns to the Delete Operator dialog box.

4.

If you want to delete other accounts, go back to Step 2. Otherwise, click Close to complete the deletion.

In MML mode 1.

Run the RMV OP command and delete the specified external operator accounts on the MML client.

----End

7.3 Managing RNC LMT Operator Passwords This describes how to manage the RNC LMT operator passwords. To manage the operator passwords is to set and query the policies for the login passwords, modify the password of the active user, and modify the password of an external operator.

7-10


Issue 03 (2009-04-25)

RNC LMT User Guide


7.3.1 Defining Policies for RNC LMT Login Passwords This describes how to define policies for login passwords. The policies for login passwords are the minimum length and complexity of passwords. Only the ADMINISTRATOR-level operator can define the policies for the login passwords. 7.3.2 Querying Policies for RNC LMT Login Passwords This describes how to query the policies for RNC LMT login passwords. To query the policies for the login passwords is to query the standards and rules of the policies for the login passwords. This task helps to set a password that meets the standards of the active password policies. 7.3.3 Changing the Password of the Active RNC LMT Operator Account This describes how to change the password of the active RNC LMT operator account. Every active online operator can change his or her own password. The new password takes effect the next time the operator logs in to the RNC. 7.3.4 Changing the Password of an RNC LMT External Operator Account This describes how to change the password of an RNC external operator by changing the password option. Only the admin and the ADMINISTRATOR-level and authorized CUSTOMlevel operators can change the passwords of external operator accounts.

7.3.1 Defining Policies for RNC LMT Login Passwords This describes how to define policies for login passwords. The policies for login passwords are the minimum length and complexity of passwords. Only the ADMINISTRATOR-level operator can define the policies for the login passwords.

Prerequisite l

The LMT is started.

l

You have logged in to the RNC with an account authorized for ADMINISTRATOR-level operations.

Context To define policies for an RNC LMT login password, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

On the Local Maintenance Terminal, choose Authority > Password Policy Setting. The Password Policy Setting dialog box is displayed, as shown in Figure 7-5. Figure 7-5 Setting password policies

Issue 03 (2009-04-25)


7-11

RNC LMT User Guide


l

2.

In the Password Policy Setting dialog box, set Minimum Length of Password and component types of the password in the Password Complexity area.

3.

Click OK to complete the policy settings for the login password. The newly set password policies only affect the subsequent password settings and password modifications.

In MML mode 1.

Run the SET PWDPOLICY command and set the policies for LMT login passwords on the MML client.

----End

7.3.2 Querying Policies for RNC LMT Login Passwords This describes how to query the policies for RNC LMT login passwords. To query the policies for the login passwords is to query the standards and rules of the policies for the login passwords. This task helps to set a password that meets the standards of the active password policies.


Context This task can be performed only in MML mode.

Procedure Run the LST PWDPOLICY command on the MML client. The active policies for login passwords are listed in the MML command output pane. ----End

7.3.3 Changing the Password of the Active RNC LMT Operator Account This describes how to change the password of the active RNC LMT operator account. Every active online operator can change his or her own password. The new password takes effect the next time the operator logs in to the RNC.


Context NOTE

Change the password of the admin account with caution. If the password is lost, you cannot log in to the system. In that case, contact Huawei for technical support.

7-12


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Step 1 In the Local Maintenance Terminal window, choose Authority > Change Password. The Change Password dialog box is displayed, as shown in Figure 7-6. Figure 7-6 Change Password dialog box

Step 2 Enter the old password for authentication. Enter the new password in the New Password box. Enter the new password again in the Confirm Password box. Step 3 Click OK. The changing is complete. ----End

7.3.4 Changing the Password of an RNC LMT External Operator Account This describes how to change the password of an RNC external operator by changing the password option. Only the admin and the ADMINISTRATOR-level and authorized CUSTOMlevel operators can change the passwords of external operator accounts.

Prerequisite l

The LMT is started.

l


Procedure Run the MOD OP command on the MML client. NOTE

You can also change the passwords of external operator accounts when you modify the operator properties. For details, refer to Modifying the Properties of an RNC LMT External Operator Account.

----End

Issue 03 (2009-04-25)


7-13

RNC LMT User Guide


7.4 Managing RNC Command Groups This describes how to manage RNC command groups. To manage RNC command groups is to query group information, set group names, and modify group contents. 7.4.1 Querying RNC Command Groups This describes how to query the MML commands of all command groups except the two binary groups G_10 and G_11. The system provides 32 command groups from G_0 to G_31. All operators can perform this task. 7.4.2 Renaming an RNC Command Group This describes how to rename an RNC command group. Groups G_0 to G_11 are predefined by the system and cannot be renamed. Groups G_12 to G_31 can be renamed. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can set names for the groups. 7.4.3 Changing Commands in an RNC Command Group This describes how to change commands in an RNC command group. Groups G_0 to G_11 are predefined by the system, and the contents cannot be changed. Operators can add commands to or remove commands from groups G_12 to G_31 as required. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the group contents.

7.4.1 Querying RNC Command Groups This describes how to query the MML commands of all command groups except the two binary groups G_10 and G_11. The system provides 32 command groups from G_0 to G_31. All operators can perform this task.


Procedure Run the LST CCG command on the MML client. ----End

7.4.2 Renaming an RNC Command Group This describes how to rename an RNC command group. Groups G_0 to G_11 are predefined by the system and cannot be renamed. Groups G_12 to G_31 can be renamed. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can set names for the groups.

Prerequisite

7-14

l

The LMT is started.

l

You have logged in to the RNC with an account authorized for this task. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Context To modify the group names, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Authority > Command Group > Set Command Group Name. The Set Command Group Name dialog box is displayed, as shown in Figure 7-7. Figure 7-7 Setting command group names

l

2.

Select the group to be renamed from the Command Group drop-down list, and enter the new name in the Command Group Name box.

3.

Click Set. If the setting is successful, a dialog box prompting success is displayed.

4.

Click OK.

In MML mode 1.

Run the LST CCGN command on the MML client to query the command group names.

2.

Run the SET CCGN command to set the names. NOTE

You can query the names of all the command groups (G_0 to G_31) by running the LST CCGN command.

----End

7.4.3 Changing Commands in an RNC Command Group This describes how to change commands in an RNC command group. Groups G_0 to G_11 are predefined by the system, and the contents cannot be changed. Operators can add commands to or remove commands from groups G_12 to G_31 as required. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the group contents.

Prerequisite l

Issue 03 (2009-04-25)


7-15

RNC LMT User Guide

7 Managing Authorities for RNC Operations l


Context To modify the group contents, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Authority > Command Group > Modify Command Group. The Modify Command Group dialog box is displayed, as shown in Figure 7-8. Figure 7-8 Modifying a command group

l

2.

Select a command group from G_12 to G_31 in the command group drop-down list. In this example, select G_12.

3.

Select or clear the check boxes of commands.

4.

Click OK. The modification is complete.

In MML mode 1.

Run the ADD CCG command on the MML client to add commands to a command group.

2.

Run the RMV CCG command on the MML client to remove commands from a command group.

----End

7-16


Issue 03 (2009-04-25)

RNC LMT User Guide

8 Managing the RNC License

8

Managing the RNC License

About This Chapter This describes how to manage the RNC license, for example, activate and reallocate the RNC license, check the quantity of current RNC operators, the traffic on the RNC, or the alarms related to the RNC license. 8.1 Basic Concepts of the RNC License A license is an authorization agreement between the supplier and the operator in terms of the functions, application scope, and service life of products. Physically, a license consists of a license certificate and a license file. 8.2 Activating the RNC License Activating the RNC license means initially activating the license or changing the RNC license. 8.3 Reallocating the RNC License This describes how to reallocate the RNC license. Reallocating the RNC license to the primary and secondary operators means that the license file does not change but the license allocation policies do. For example, secondary operator A may purchase some RNC capacity from the primary operator. 8.4 Checking RNC Current User Number/Throughput For a running RNC, you can run the MML commands to check the current user number or throughput of the RNC.

Issue 03 (2009-04-25)


8-1

RNC LMT User Guide


8.1 Basic Concepts of the RNC License A license is an authorization agreement between the supplier and the operator in terms of the functions, application scope, and service life of products. Physically, a license consists of a license certificate and a license file. 8.1.1 License File To obtain a valid license file from Huawei and successfully activate it is the prerequisite for the RNC to acquire more capacity and functions. One RNC can activate only one license file and the total capability of the authorized RNC is defined in the license file. If there is no license or the license is invalid, the RNC only provides the minimum capability by default. 8.1.2 License Control for Multiple Operators The RNC supports the RAN sharing function, that is, one primary operator and up to three secondary operators can share one RNC. The RNC with the RAN sharing function still has only one license file, which defines the total capability of the RNC. Each operator uses a unique share of the license and activates the license independently. Therefore, the RNC capacity and functions must be allocated in advance to the primary operator first and then the secondary operators. Then, run the ACT LICENSE command to activate the license for the operators involved. 8.1.3 License Validation Mechanism The activation of the license file accompanies validity check, after which the RNC automatically verifies license data on a daily basis.

8.1.1 License File To obtain a valid license file from Huawei and successfully activate it is the prerequisite for the RNC to acquire more capacity and functions. One RNC can activate only one license file and the total capability of the authorized RNC is defined in the license file. If there is no license or the license is invalid, the RNC only provides the minimum capability by default.

Components of the License File The license file is composed of equipment ID, service life, capacity control items, and control items of optional functions. Component

Description

License file ID

The only identifier of a license file, which makes the license file easy to manage.

Equipment ID

The license file is valid only when the equipment ID is consistent with the ESN of the RNC. Only a valid license file can be activated on the RNC. NOTE The Equipment Serial Number (ESN) identifies only one set of RNC equipment. The ESN of the RNC refers to the encrypted data of three parameters, namely the MNC and MCC of the primary operator, and the RNC ID.

Service life

8-2

Service life of the license file consists of two parameters: service deadline and trial time after service deadline. If the trial time is not defined, it is set to 60 days by default.


Issue 03 (2009-04-25)

RNC LMT User Guide


Component

Description

Equipment capacity

Equipment capacity means the maximum CS user number (unit: Erlang), the maximum PS throughput (unit: kbit/s), the maximum HSDPA throughput (unit: kbit/s), the maximum HSUPA throughput (unit: kbit/s), the maximum MBMS throughput (unit: kbit/s).

Control items of optional functions

The control items involve the authorization of optional functions of the RNC.

License File Management The license file is controlled and issued by Huawei license management center. The primary operator needs to apply for a license file from Huawei in the following situations: l

An RNC is added.

l

The ESN of the RNC is changed.

l

The capacity and functions of the RNC are enhanced due to software upgrade or capacity expansion.

Activating the License l

Activating the license online After the license is activated online, the license information on the operator is applied to the host and the services are immediately influenced.

l

Activating the license offline Activating the license offline only modifies the license information stored on the BAM. The license is activated on the host only after the board is reset or the RNC is reset. NOTE

l

After the RNC is reset, all the subracks are reset and obtain the new licenses.

l

After the boards are reset, only the reset boards can obtain the new licenses.

8.1.2 License Control for Multiple Operators The RNC supports the RAN sharing function, that is, one primary operator and up to three secondary operators can share one RNC. The RNC with the RAN sharing function still has only one license file, which defines the total capability of the RNC. Each operator uses a unique share of the license and activates the license independently. Therefore, the RNC capacity and functions must be allocated in advance to the primary operator first and then the secondary operators. Then, run the ACT LICENSE command to activate the license for the operators involved.

Activating the License of Primary and Secondary Operators Figure 8-1 shows an example interface where the command to activate the license of the primary operator is used.

Issue 03 (2009-04-25)


8-3

RNC LMT User Guide


Figure 8-1 Activating the license of the primary operator

NOTE

When the license of the primary operator is activated, the RANSHARE switch must be set to ON.

Figure 8-2 shows an example interface where the command to activate the license of the secondary operator is used. Figure 8-2 Activating the license of the secondary operator

Allocating RNC Capacity to Primary and Secondary Operators The total maximum number of CS users of primary and secondary operators must be no more than the number defined in the license file. The same is the maximum number of PS users. When the maximum number of CS users or the maximum PS throughput of the primary operator is not set, the value is the same as the license file by default. When the maximum number of CS users or the maximum PS throughput of the secondary operator is not set, the value is zero by default.

Allocating RNC Functions to Primary and Secondary Operators Allocating RNC functions to primary and secondary operators complies with the following principles: 8-4


Issue 03 (2009-04-25)

RNC LMT User Guide

8 Managing the RNC License l

Neither the primary operator nor the secondary operators can activate the functions unauthorized by the license file.

l

Both the primary operator and the secondary operators can activate the functions authorized by the license file.

l

The secondary operators can activate the authorized functions except those totally controlled by the primary operator.

The primary operator fully controls the following functions: l

RAN sharing

l

Enhanced package of RAN sharing

l

ATM/IP dual stack transport over Iub

l

IP transport over Iur

l

Fractional IP

l

Fractional ATM

l

IP Iub overbooking

l

ATM Iub overbooking

l

HUB Iub overbooking

l

Hybrid IP transport over Iur

l

Cell ACR in SPU overloading

l

FP multiplexing

l

Dynamic IP bandwidth control on the Iub interface

l

BFD/ARP-based IP Rerouting NOTE

If the ACT LICENSE command switch is dimmed, it is an indication that the function is consistent with the license file setting.

8.1.3 License Validation Mechanism The activation of the license file accompanies validity check, after which the RNC automatically verifies license data on a daily basis.

Path of the License File Before the activation, the valid license file needs to be imported as a .lic file into the directory BAM active workspace installation directory\FTP\License on the BAM. In this directory, multiple license files can be saved and the files to be activated must be saved here. After successful activation, the file is transferred to the directory of BAM active workspace installation directory\License (license directory for short). This directory stores only one current license file of the RNC.

Legality of the License File If in a license file the equipment ID is consistent with the ESN of the RNC, the license file is legal; otherwise, the license file is illegal. l

Issue 03 (2009-04-25)

To activate a license for a legal license file: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8-5

RNC LMT User Guide


l

–

If the license expires, it cannot be activated; otherwise, the license can be successfully activated.

–

The activated license file is valid during the time period running deadline + trial time. For the time afterwards, the license file becomes invalid and the RNC turns to the default capacity and functions.

–

On 30 days before the running deadline, the RNC reports the alarm 20016 License Will Expire.

–

On the running deadline, the RNC reports the alarm 20017 License Has Expired.

To activate a license for an illegal license file: –

The license file is successfully activated. The activated license file is valid within the trial time. For the time afterwards, the license file becomes invalid and the RNC turns to the default capacity and functions.

–

The RNC reports the alarm 20018 Invalid License On Trial.

Internal Processing of the License Data In addition to the current license file under the license directory, the RNC also saves license data in the BAM database and the DPUb/SPUa at the host. Only the license data at the host takes effect. The activation of a license varies with the data configuration states of the RNC: l

Activating the license online The RNC updates the license data both in the BAM database and in the DPUb/SPUa at the host.

l

Activating the license offline The RNC updates the license data only in the BAM database rather than in the board at the new host.

After the license is activated, the RNC updates the license data in the BAM database and the DPUb/SPUa at the host in the following conditions: l

After being restarted, the BAM updates the license data in its database according to the current license file.

l

After the host is restarted, the DPUb/SPUa updates the license data according the BAM database.

Therefore, the license-related alarms must be cleared as soon as possible to ensure the license validity.

Automatic Verification of the License Data At 00:45 every morning, the RNC automatically verifies the state of current license file under the license directory. If the current license file is faulty, the RNC generates related alarms, for example, 20011 License File Damaged, 20012 License File Does Not Exist, and 20013 Invalid License . At 3:00 every morning, the RNC automatically compares and checks whether the license data in the SCUa/SPUa is consistent with that in the BAM database. If the license data is consistent, the RNC reports the alarm 20020 Host And BAM LICENSE Inconsistency In CMP LICENSE. 8-6


Issue 03 (2009-04-25)

RNC LMT User Guide

8 Managing the RNC License NOTE

When the alarm 20020 Host And BAM LICENSE Inconsistency In CMP LICENSE is reported, handle the alarm according to related help information. The alarm, if not cleared, may affect the running of the RNC.

8.2 Activating the RNC License Activating the RNC license means initially activating the license or changing the RNC license.

Context l

Initially activating the license refers to activating the license when an RNC is set up. A valid license file from Huawei, however, is a prerequisite for setting up the RNC. When installing or commissioning the RNC, you can manually import and activate the license file. For details, refer to the RNC BAM Administration Guide and the RNC Commissioning Guide.

l

Changing the RNC license refers to applying for and activating a new license file for a running RNC due to software upgrade, capacity expansion, and change of the ESN.

CAUTION You need to combine the new license and already-owned license after the application.

Procedure Step 1 Obtain the ESN of the RNC. l

If the ESN remains the same after the license file changes, obtain the ESN of the RNC by referring to Obtaining ESN Information from the RNC.

l

If the ESN changes with the license file, contact Huawei engineers for confirmation.

Step 2 Apply for a new license file from Huawei. Step 3 Upload the new license file to the BAM. Refer to Uploading the License File to the BAM. Step 4 Confirm the basic information about the RNC and check whether the operator information exists. Refer to Checking RNC Basic Information and Operator Information. Step 5 Activate and test the RNC license. Refer to Activating and Verifying the RNC License. ----End

8.2.1 Obtaining ESN Information from the RNC This describes how to query the Equipment Serial Number (ESN) information from the RNC.

Prerequisite l

The RNC is running properly.

l

The LMT is started and you have logged in to the RNC.

Issue 03 (2009-04-25)


8-7

RNC LMT User Guide


Procedure Step 1 Run the LST ESN command on the MML client. Step 2 Obtain the ESN of the RNC from the returned messages, as shown in Figure 8-3. Figure 8-3 ESN in the returned message

----End

8.2.2 Uploading the RNC License File to the BAM This describes how to upload the RNC license file to the BAM through FTP.

Prerequisite l


l


Context Before uploading the license file, you need the following information: l

External IP address of the BAM

l

Name and password of the FTP user

Procedure Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The FTP Client is started. Step 2 Enter the external virtual IP address of the BAM in Server, and then enter the user name and password of the FTP in User and Password. Step 3 Click window.

to connect the BAM. A BAM file directory is displayed on the right of the FTP Client

Step 4 Click in the right of the FTP Client window, locate the BAM file directory under BAM active workspace installation directory\FTP\License. 8-8


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 5 On the left of the FTP Client window, select the license file to be uploaded locally, and then click

.

Step 6 Find the uploaded license file on the right of the window. The uploading is complete. ----End

8.2.3 Checking RNC Basic Information and Operator Information This describes how to check that the basic information about the RNC and the operator information exist.

Prerequisite l


l


Context The RNC ID and the MNC and MCC of the primary operator must be consistent with those in the license file.

Procedure Step 1 Run the LST RNCBASIC command to check whether the basic information about the RNC exists. Step 2 In the absence of the basic information, run the ADD RNCBASIC command to add the basic information about the RNC, as shown in Figure 8-4. Figure 8-4 Adding the basic information about the RNC

Step 3 Run the LST CNOPERATOR command to check whether the basic information about the primary operator exists. Step 4 In the absence of the basic information, run the ADD CNOPERATOR command to add the basic information about the primary operator, as shown in Figure 8-5. Figure 8-5 Adding the basic information about the primary operator

Issue 03 (2009-04-25)


8-9

RNC LMT User Guide


Step 5 (Optional) Run the ADD CNOPERATOR command to add a secondary operator, an external operator, or a common operator. Step 6 Run the LST ESN command to check whether the modified ESN information is consistent with the license file. Figure 8-6 shows the returned message. Figure 8-6 ESN in the returned message

----End

8.2.4 Activating and Verifying the RNC License This describes how to activate the RNC license and verify the license configuration information.

Prerequisite l

The LMT is started and properly communicates with the BAM.

l

The communication between the RNC FAM and the BAM is operational.

l

The license of the local office is in BAM Active Workspace Installation Directory\FTP \License and the file name is license.dat.

Procedure Step 1 On the RNC LMT, run the LST LICENSE command and enter the name of the license file to be activated to query the detailed configuration information of the license file. If...

Then...

The license is consistent with that applied,

Go to Step 2.

The license is inconsistent with that applied,

Contact Huawei for confirmation.

Step 2 Run the LST CFGMODE to query the data configuration of all the subracks. If the subrack is in offline mode, run the SET ONLINE command to set the subrack to the online mode. Step 3 Run the ACT LICENSE command to activate the licenses of all telecom operators. The activation is performed in sequence from the primary telecom operator to the secondary telecom operator. If there are multiple telecom operators, run the command repeatedly. 8-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 4 Run the CMP LICENSE command to check whether the license of the host and that of the BAM are consistent. If...

Then...

The two licenses are consistent,

End this task.

The two licenses are inconsistent,

Go to Step 5.

Step 5 Run the DSP LICENSE command to check whether the license data of the host is consistent with that applied. If...

Then...

The query result is consistent with the actual configuration,

End this task.

The query result is inconsistent with the actual configuration,

Contact Huawei for confirmation.

----End

8.3 Reallocating the RNC License This describes how to reallocate the RNC license. Reallocating the RNC license to the primary and secondary operators means that the license file does not change but the license allocation policies do. For example, secondary operator A may purchase some RNC capacity from the primary operator.

Prerequisite l


l


Procedure Step 1 Determine the primary and secondary operators involved. Step 2 Run the LST LICENSE command to enter the file name of the license to be activated and then query the configuration details of this file. If the configuration information is consistent with what you apply for, go to Step 3. If it is inconsistent, stop this task and contact Huawei for confirmation. Step 3 Run the LST CFGMODE command to check the data configuration status of the RNC. Step 4 If the RNC is offline, run the SET ONLINE command to make it online. Step 5 Run the ACT LICENSE command to activate the license of the primary operator first and then that of the secondary operator. If there are multiple secondary operators, repeat this command. Issue 03 (2009-04-25)


8-11

RNC LMT User Guide


Step 6 Run the CMP LICENSE command to compare and check whether the license data in the DPUb/ SPUa memory is consistent with that in the BAM database. If they are consistent with each other, end this task. If they are inconsistent, go to Step 7. Step 7 Run the DSP LICENSE command to check whether the license data in the DPUb/SPUa memory is consistent with what you apply for. If they are consistent with each other, end this task. If they are inconsistent, go to Step 2. ----End

8.4 Checking RNC Current User Number/Throughput For a running RNC, you can run the MML commands to check the current user number or throughput of the RNC.

Prerequisite l


l


Context When the current CS user number or PS throughput of the RNC approaches or exceeds the limit of the license file, the RNC generates alarms. l

When the current user number or throughput of the RNC approaches the capacity limit, the alarm ALM-1356 Number of Users Over 90% of System Capacity is reported.

l

When the current user number or throughput of the RNC exceeds the capacity limit, the alarm ALM-1357 Number of Users Over 120% of System Capacity is reported.

When the CS user number or PS throughput of the RNC frequently exceeds the limit of the license file, you can infer that the RNC needs capacity expansion.

Procedure Run the DSP USERNUM command on the MML client to check the number of RNC CS users (unit: Erlang) and the PS throughput in the uplink and downlink (unit: kbit/s). NOTE

When the corresponding SPU of the entered subrack number, slot number, and subsystem number is set to the MPU, the CS user numbers and PS throughput of the subrack where the MPU is located are reported. Otherwise, only the CS user number of the subrack where the MPU is located is reported. The PS throughput of the subrack is 0.

----End

8-12


Issue 03 (2009-04-25)

RNC LMT User Guide

9 Managing RNC Alarms

9

Managing RNC Alarms

About This Chapter This describes how to manage RNC alarms. It helps analyze the alarm, locate, and rectify the faults. 9.1 Concepts of RNC Alarm Management This describes the following concepts of the RNC alarm management: alarm types, alarm severity, event types, and the alarm box. 9.2 Setting RNC Alarm Logs This describes how to set RNC alarm logs. Alarm logs are used to record details of alarms. Alarm logs are collected by and stored on the BAM. To prevent the logs from occupying too much space on the hard disk, you need to set the capacity and time limits of alarm logs. 9.3 Masking RNC Alarms This describes how to mask RNC alarms. The alarms that meet the shields are not sent to the LMT or the M2000. To filter alarms, you can set specific alarm shields on the LMT. 9.4 Masking RNC Derived Alarms This describes how to mask RNC derived alarms. The RNC can mask derived alarms. The two alarm mask levels are ON and OFF. 9.5 Monitoring RNC Alarms This describes how to monitor RNC alarms. In the Alarm Browse window of the LMT, you can monitor the alarm information sent to the LMT in real time. 9.6 Managing the Convert Management System This describes how to manage the Convert Management System. The Convert Management System runs on the LMT PC, which is connected to the alarm box through the serial port. The system forwards the alarms and the commands about the alarms from the BAM to the alarm box to manage and monitor the alarm box. When receiving the information, the alarm box provides audible and visible indications. 9.7 Operating the RNC Alarm Box This describes how to operate the RNC alarm box. In the RNC, the LMT is connected to the universal alarm box of Huawei. When the LMT receives alarms sent from the BAM, the alarm box gives audible and visible indications.

Issue 03 (2009-04-25)


9-1

RNC LMT User Guide


9.1 Concepts of RNC Alarm Management This describes the following concepts of the RNC alarm management: alarm types, alarm severity, event types, and the alarm box. 9.1.1 RNC Alarm Type The alarms in the RNC system are of two types: fault alarms and event alarms. 9.1.2 RNC Alarm Level The alarm severity indicates how serious a fault is. The alarm severity for both fault alarms and event alarms can be divided into the four levels: critical, major, minor, and warning. 9.1.3 RNC Event Alarm Types The RNC event alarms can be divided into ten types based on specific alarm event. 9.1.4 RNC Alarm Box The RNC uses the universal alarm box of Huawei. The alarm box provides audible and visible indications based on the alarm severity level. It is optional and the RNC can be configured with only one alarm box. For details, refer to its delivery-attached documents.

9.1.1 RNC Alarm Type The alarms in the RNC system are of two types: fault alarms and event alarms. Table 9-1 describes the two types of alarms. Table 9-1 Fault alarms and event alarms Alarm Type

Description

Fault alarms

Alarms caused by hardware faults or the abnormity of major functions, for example, board failure or link failure. Fault alarms are of higher severity than event alarms. After the faults occur, according to the statuses of the faults, fault alarms are divided into active and recovery alarms.

Event alarms

An event alarm indicates a predefined event that happens during the running of the devices. The alarm represents an instantaneous status of the system and the status may not be a fault. Some event alarms are generated repeatedly and regularly. Event alarms cannot be divided into active and recovery alarms.

After the faults occur, according to the statuses of the faults, fault alarms are divided into active and recovery alarms. l

If the fault is cleared, the status of the alarm changes to Recovery, and the alarm is called a recovery alarm.

l

If the fault is not cleared, the status of the alarm remains Active, and the alarm is called an active alarm.

For example, when congestion occurs in a cell, the system reports a fault alarm of cell congestion. Before the congestion is cleared, the alarm remains an active one. After the congestion is cleared, the alarm becomes a recovery one. 9-2


Issue 03 (2009-04-25)

RNC LMT User Guide

9 Managing RNC Alarms NOTE

The record of a recovery alarm is stored in the BAM database and can be queried.

9.1.2 RNC Alarm Level The alarm severity indicates how serious a fault is. The alarm severity for both fault alarms and event alarms can be divided into the four levels: critical, major, minor, and warning. Table 9-2 describes the four RNC severity levels. Table 9-2 RNC Alarm severity levels RNC Alarm Level

Definition

Solution

Critical alarm

Reporting faults that affect the services provided by the system. These alarms need immediate treatment even during off-work period. For example, some equipment or resource breaks down.

Handle the faults immediately. Otherwise, the system may collapse.

Major alarm

Reporting faults that affect the Quality of Service (QoS). These alarms need treatment during working hours. For example, the performance of some equipment or resource deteriorates.

Handle the faults timely. Otherwise, the system may fail to perform some major functions.

Minor alarm

Reporting faults that are not serious enough to affect the QoS. These alarms need timely treatment or further observation to avoid worsening.

Find and clear any potential fault in time.

Warning alarm

Reporting faults that potentially threaten the system services. These alarms need treatment according to specific situations.

Learn the running state of the system.

9.1.3 RNC Event Alarm Types The RNC event alarms can be divided into ten types based on specific alarm event. l

Power system: alarms related to the power system

l

Environment system: alarms related to the equipment room environment, such as temperature, humidity, and access control

l

Signaling system: alarms related to the signaling system

l

Trunk system: alarms related to the trunk system, including trunk circuits and trunk boards

l

Hardware system: alarms related to a board, such as clock and CPU

l

Software system: alarms related to the software

l

Running system: alarms generated during the running of the system

l

Communication system: alarms related to the communication system, such as the one between the host and the BAM

l

QoS: alarms related to QoS

Issue 03 (2009-04-25)


9-3

RNC LMT User Guide

9 Managing RNC Alarms l

Processing error: alarms caused by other exceptions not listed above

9.1.4 RNC Alarm Box The RNC uses the universal alarm box of Huawei. The alarm box provides audible and visible indications based on the alarm severity level. It is optional and the RNC can be configured with only one alarm box. For details, refer to its delivery-attached documents. The appearance of the alarm box is shown in Figure 9-1. Figure 9-1 Alarm box

The alarm box is driven when the RNC reports a fault alarm to the LMT. The alarm box then provides audible and visible indications based on the alarm severity level. NOTE

The alarm box does not give any indication for event alarms.

When the LMT receives the fault alarm, the alarm box provides audio indications. The sound of the alarm box stops when the alarm is cleared. You can also manually stop the sound on the LMT.

9.2 Setting RNC Alarm Logs This describes how to set RNC alarm logs. Alarm logs are used to record details of alarms. Alarm logs are collected by and stored on the BAM. To prevent the logs from occupying too much space on the hard disk, you need to set the capacity and time limits of alarm logs. 9.2.1 Setting the Capacity and Time Limit of an RNC Alarm Log This describes how to set the maximum of alarms that can be stored in each log and the time limit of the logs. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can set these two items. 9.2.2 Querying the Capacity and Time Limit of an RNC Alarm Log 9-4


Issue 03 (2009-04-25)

RNC LMT User Guide


This describes how to query the maximum of alarms that can be stored in each log and the time limit of the logs.

9.2.1 Setting the Capacity and Time Limit of an RNC Alarm Log This describes how to set the maximum of alarms that can be stored in each log and the time limit of the logs. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can set these two items.

Prerequisite l

The LMT is started.

l


Procedure On the MML client, run the SET ALMCAPACITY command. ----End

9.2.2 Querying the Capacity and Time Limit of an RNC Alarm Log This describes how to query the maximum of alarms that can be stored in each log and the time limit of the logs.


Procedure On the MML client, run the LST ALMCAPACITY command. ----End

9.3 Masking RNC Alarms This describes how to mask RNC alarms. The alarms that meet the shields are not sent to the LMT or the M2000. To filter alarms, you can set specific alarm shields on the LMT. 9.3.1 Adding an RNC Alarm Shield This describes how to add an RNC alarm shield to filter alarms of a DSP or of an E1/T1 port or to filter a specified alarm. Operators of the following levels can add alarm shields: ADMINISTRATOR and OPERATOR. 9.3.2 Deleting an RNC Alarm Shield This describes how to delete an alarm shield or all alarm shields in the RNC. When you do not need the RNC to filter an alarm, you should delete all the shields related to this alarm. Operators of the following levels can delete alarm shields: ADMINISTRATOR and OPERATOR. 9.3.3 Querying RNC Alarm Shields This describes how to query the RNC alarm shields that meets the conditions. Issue 03 (2009-04-25)


9-5

RNC LMT User Guide


9.3.1 Adding an RNC Alarm Shield This describes how to add an RNC alarm shield to filter alarms of a DSP or of an E1/T1 port or to filter a specified alarm. Operators of the following levels can add alarm shields: ADMINISTRATOR and OPERATOR.

Prerequisite l

The LMT is started.

l


Procedure Step 1 Run the ADD OBJALMSHLD command on the MML client to add an alarm shield. The successfully added alarm shield takes effect immediately. NOTE

l

The names of the alarm shields cannot be duplicate. Otherwise, the addition fails.

l

A maximum of 100 alarm shields can be added to each RNC.

l

If the filter status is suspended, the alarms matching the filter are not filtered.

Step 2 Run the LST OBJALMSHLD command and enter the parameters to check whether the alarm shield is successfully added. NOTE

If no querying condition parameter is entered, all the alarm shields are displayed after this MML command is run; if no alarm shield that meets the querying conditions exists or no alarm shield is set on the LMT, the failure information is displayed.

----End

9.3.2 Deleting an RNC Alarm Shield This describes how to delete an alarm shield or all alarm shields in the RNC. When you do not need the RNC to filter an alarm, you should delete all the shields related to this alarm. Operators of the following levels can delete alarm shields: ADMINISTRATOR and OPERATOR.

Prerequisite l

The LMT is started.

l


l

The alarm shield to be deleted exists.

Procedure Step 1 Run the LST OBJALMSHLD command on the MML client to query RNC alarm shields to be deleted.

9-6

If...

Then...

The shield is listed,

Go to Step 2.


Issue 03 (2009-04-25)

RNC LMT User Guide


If...

Then...

The shield is not listed,

End this operation.

Step 2 Run the RMV OBJALMSHLD command to delete the alarm shield. If you need to delete an alarm shield, enter The Shield index of Alarm Object. If you need to delete all the alarm shields, leave The Shield index of Alarm Object blank. NOTE

If The Shield index of Alarm Object is not specified, all alarm shields in the RNC are deleted.

Step 3 If you need to delete multiple alarm shields, go to Step 2. ----End

9.3.3 Querying RNC Alarm Shields This describes how to query the RNC alarm shields that meets the conditions.


Procedure Run the LST OBJALMSHLD command and enter the querying condition parameters on the MML client to query RNC alarm shields. NOTE

l

If the querying condition parameters are specified, the LMT queries the RNC alarm shields that meet the conditions; if no querying condition parameters are specified, the LMT queries all the alarm shields in the LMT.

l

If no alarm shield that meets the querying conditions exists or no alarm shield is set in the LMT, the failure information is displayed.

----End

9.4 Masking RNC Derived Alarms This describes how to mask RNC derived alarms. The RNC can mask derived alarms. The two alarm mask levels are ON and OFF. 9.4.1 Setting the Mask Level of an RNC Derived Alarm This describes how to set the mask level of an RNC derived alarm. You can set the alarm mask level to ON or OFF. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can set the alarm mask. 9.4.2 Querying the Mask Level of an RNC Derived Alarm This describes how to query the mask level of an RNC derived alarm. By performing this task, you can learn about whether the alarm mask switch is on or off.

Issue 03 (2009-04-25)


9-7

RNC LMT User Guide


9.4.1 Setting the Mask Level of an RNC Derived Alarm This describes how to set the mask level of an RNC derived alarm. You can set the alarm mask level to ON or OFF. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can set the alarm mask.

Prerequisite l

The LMT is started.

l


l

The ownership of the RNC data configuration right is obtained. For details, refer to 6.4 Obtaining the RNC Data Configuration Right.

Procedure Run the SET ALMML command on the MML client. ----End

9.4.2 Querying the Mask Level of an RNC Derived Alarm This describes how to query the mask level of an RNC derived alarm. By performing this task, you can learn about whether the alarm mask switch is on or off.


Procedure On the MML client, run the LST ALMML command and enter the parameter as required to query whether the alarm mask switch is on or off. ----End

9.5 Monitoring RNC Alarms This describes how to monitor RNC alarms. In the Alarm Browse window of the LMT, you can monitor the alarm information sent to the LMT in real time. 9.5.1 Setting the Properties of the Alarm Browse Window This describes how to set the display properties of the Alarm Browse window. 9.5.2 Setting the Properties of RNC Fault Alarm Sounds This describes how to specify the severity level(s) and the duration of the audible alarms. The LMT emits audible alarms when it receives fault alarms of specified severity levels. 9.5.3 Browsing Alarms This describes how to browse the fault and event alarms that are sent to the LMT and displayed in the Alarm Browse window in real time. It helps learn about the operating situation of the system. 9.5.4 Querying RNC Alarm Logs 9-8


Issue 03 (2009-04-25)

RNC LMT User Guide


This describes how to query the history alarm information from the BAM database. It helps learn the history operating situation of the system. 9.5.5 Querying RNC Alarm Handling Suggestions This describes how to query RNC alarm handling suggestions. The LMT provides detailed help information for every alarm. 9.5.6 Manually Setting a Cleared RNC Alarm This describes how to manually set a cleared alarm. When a fault is cleared or can be neglected, you can manually set the alarm as a recovery alarm. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can perform the task. 9.5.7 Saving the Information on an RNC Alarm This describes how to save a part or all of the alarm information in the Alarm Browse window or the Query Alarm Log window for later queries. 9.5.8 Setting the Preferences for Printing RNC Alarms in Real Time This describes how to set the requirements for the alarms for printing. After the setting, only the real-time alarms that meet the requirements can be printed. 9.5.9 Manually Printing RNC Alarms This describes how to print a part or all of the alarm information in the Alarm Browse window or the Query Alarm Log window.

9.5.1 Setting the Properties of the Alarm Browse Window This describes how to set the display properties of the Alarm Browse window.


Procedure Table 9-3 lists the display properties of the Alarm Browse window and describes how to set them. Table 9-3 Display properties and setting methods

Issue 03 (2009-04-25)

Display Property

Setting

Description

Alarm colors

Choose Fault Management > Alarm Customization.

Select colors for alarms of different types, severity levels, and status.

Display amount

Choose Fault Management > Alarm Customization.

Set the initial and maximum amounts of alarms to be displayed.

Deletion of recovery alarms from fault alarm browse window

Right-click the fault alarm browse pane and choose Clear All Recovery Alarms from the shortcut menu.

Delete all recovery alarms from the fault alarm browse pane. The records of the recovery alarms are still stored and can be queried.


9-9

RNC LMT User Guide


Display Property

Setting

Description

Manually Refresh

Right-click the fault alarm browse pane and choose Manually Refresh from the shortcut menu.

Refresh the alarm information in the fault alarm window and delete all the cleared alarms.

----End

9.5.2 Setting the Properties of RNC Fault Alarm Sounds This describes how to specify the severity level(s) and the duration of the audible alarms. The LMT emits audible alarms when it receives fault alarms of specified severity levels.


Procedure Step 1 In the Local Maintenance Terminal window, choose Fault Management > Alarm Customization. The Alarm Customization dialog box is displayed, as shown in Figure 9-2. Figure 9-2 Customizing alarms

9-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 Set the alarm severity and sound playing frequency in the Fault Alarm Sound area in the Alarm Customization dialog box. Step 3 Click OK to save the settings. ----End

9.5.3 Browsing Alarms This describes how to browse the fault and event alarms that are sent to the LMT and displayed in the Alarm Browse window in real time. It helps learn about the operating situation of the system.


Procedure Step 1 In the Local Maintenance Terminal window, choose Fault Management > Browse Alarm to display the Alarm Browse window. The upside of the window is the fault alarm browse pane and the downside is the event alarm browse pane. Step 2 Browse alarms in the Alarm Browse windows. Step 3 To learn the details of an alarm, double-click it. The Alarm Detailed Information dialog box is displayed, as shown in Figure 9-3. Figure 9-3 Details about an alarm

Issue 03 (2009-04-25)


9-11

RNC LMT User Guide


Step 4 Click the following buttons as required. Button Name Result Previous

Check the details of the previous alarm

Next

Check the details of the next alarm

Solution

Check the alarm meaning, the impact on the system, the system action, and the alarm handling.

Step 5 Click Close to close the dialog box. ----End

9.5.4 Querying RNC Alarm Logs This describes how to query the history alarm information from the BAM database. It helps learn the history operating situation of the system.


Context You can query the alarms logs by individual or combinations of the following parameters: l

Alarm Type

l

Severity

l

Alarm time

l

Event type

l

Range of alarm IDs

l

Range of alarm serial numbers

l

Module ID

l

Maximum return amount

l

Subrack number of the board generating alarms

l

Slot number of the board generating alarms

To query RNC alarm logs, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Fault Management > Query Alarm Log or click in Figure 9-4.

9-12

. The Query Alarm Log dialog box is displayed, as shown


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 9-4 Querying an alarm log

2.

Set the query parameters.

3.

Click OK. The Query Alarm Log window is displayed, as shown in Figure 9-5.

Figure 9-5 Query Alarm Log window

Issue 03 (2009-04-25)


9-13

RNC LMT User Guide


l

4.

Browse the queried history alarms in the window.

5.

To learn the details of an alarm, double-click it. The displayed Alarm Detailed Information dialog box shows the details of this alarm.

6.

Click

to close the window when the browsing is complete.

In MML mode 1.

Run the LST ALMLOG command on the MML client. NOTE

After running the alarm querying command, right-click in the Query Alarm Log and choose the Dynamically Add. The alarm is automatically appended to the Query Alarm Log window.

----End

9.5.5 Querying RNC Alarm Handling Suggestions This describes how to query RNC alarm handling suggestions. The LMT provides detailed help information for every alarm.


Context The LMT provides detailed help information for every alarm, which includes: l

Alarm meaning

l

Impact on system

l

System action

l

Alarm handling

Procedure Step 1 In the Alarm Browse window or the Query Alarm Logwindow, double-click an alarm. The Alarm Detailed Information dialog box is displayed, as shown in Figure 9-6.

9-14


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 9-6 Details about an alarm

Step 2 In the Alarm Detailed Information dialog box, click Solution. The online help window is displayed, as shown in Figure 9-7. Figure 9-7 Alarm online help

Issue 03 (2009-04-25)


9-15

RNC LMT User Guide


Step 3 Check the information. Step 4 Click Close to close the page when the checking is complete. ----End

9.5.6 Manually Setting a Cleared RNC Alarm This describes how to manually set a cleared alarm. When a fault is cleared or can be neglected, you can manually set the alarm as a recovery alarm. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can perform the task.

Prerequisite l

The LMT is started.

l

You have logged in to the RNC with an account authorized for the setting.

Context To manually recover an alarm, you can use either of the following modes: GUI and MML.

Procedure l

l

In GUI mode 1.

In the fault alarm browse pane, select the alarm to be set to a recovery alarm.

2.

Press Ctrl+Delete or right-click the alarm, and then choose Manually Recover Alarm from the shortcut menu. A dialog box is displayed, prompting whether to clear this alarm.

3.

Click Yes. The color of the alarm changes to that of a recovery one.

In MML mode 1.

On the MML client, run the RMV ALMFLT command and enter Serial No. to manually recover the alarm.

----End

9.5.7 Saving the Information on an RNC Alarm This describes how to save a part or all of the alarm information in the Alarm Browse window or the Query Alarm Log window for later queries.


Context The information is stored in any of the following formats:

9-16

l

.txt

l

.htm

l

.csv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


The files record the following information: alarm serial number, alarm name, alarm severity, raised/clear time, alarm ID, event type, module ID, location information, alarm type, office name, and recovery type.

Procedure Step 1 In the Alarm Browse window or the Query Alarm Log window: l

To save all alarms, right-click and choose Save All Alarms from the shortcut menu.

l

To save part of the alarms, select the alarms (hold Ctrl or Shift to select multiple alarms), right-click them, and then choose Save Selected Alarms from the shortcut menu.

The Save File dialog box is displayed, as shown in Figure 9-8. Figure 9-8 Saving alarms

Step 2 Enter the file name and specify the save path and the file type. NOTE

l

The default save path is Installation directory\client\output\RNC\software version\alarm.

l

The default file name is ALM-year-month-day-hour-minute-second.txt, for example ALM-06-02-23-11-12-58.txt.

Step 3 Click Save. The saving is complete. ----End

9.5.8 Setting the Preferences for Printing RNC Alarms in Real Time This describes how to set the requirements for the alarms for printing. After the setting, only the real-time alarms that meet the requirements can be printed. Issue 03 (2009-04-25)


9-17

RNC LMT User Guide


Prerequisite l

The LMT is started.

l

The LMT is connected to a printer that works properly.

Procedure Step 1 In the Local Maintenance Terminal window, choose Fault Management > Alarm Realtime Print Set. The Alarm Realtime Print Set dialog box is displayed, as shown in Figure 9-9. Figure 9-9 Setting alarm real-time print

Step 2 Set the print requirements. Step 3 Click OK. ----End

9.5.9 Manually Printing RNC Alarms This describes how to print a part or all of the alarm information in the Alarm Browse window or the Query Alarm Log window.

Prerequisite

9-18

l

The LMT is started.

l

The LMT is connected to a printer that works properly. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Step 1 In the Alarm Browse window or the Query Alarm Log window: l

To print all alarms, right-click and choose Print All Alarms from the shortcut menu.

l

To print a part of the alarms, press and hold down Ctrl or Shift and choose the alarms to be printed, right-click them, and then choose Print Selected Alarms from the shortcut menu.

The Print dialog box is displayed, as shown in Figure 9-10. Figure 9-10 Printing alarms

Step 2 Set the print requirements. Step 3 Click Print. ----End

9.6 Managing the Convert Management System This describes how to manage the Convert Management System. The Convert Management System runs on the LMT PC, which is connected to the alarm box through the serial port. The system forwards the alarms and the commands about the alarms from the BAM to the alarm box to manage and monitor the alarm box. When receiving the information, the alarm box provides audible and visible indications. 9.6.1 Starting the RNC Convert Management System Issue 03 (2009-04-25)


9-19

RNC LMT User Guide


This describes how to start the Convert Management System on the LMT PC which is connected to the alarm box. 9.6.2 Setting the Parameters of the RNC Convert Management System This describes how to set the parameters of the Convert Management System to enable the system to perform properly the function of forwarding alarm information. 9.6.3 Saving the Information in the Output Window This describes how to save the information in the output window for the analysis of the operating situation of the Convert Management System. 9.6.4 Exiting the RNC Convert Management System This describes how to exit the Convert Management System on the LMT PC when the audible and visible indications provided by the alarm box are no longer necessary. The LMT PC is connected to the alarm box.

9.6.1 Starting the RNC Convert Management System This describes how to start the Convert Management System on the LMT PC which is connected to the alarm box.

Prerequisite l

The LMT is properly connected to the RNC.

l

The LMT PC is properly connected to the alarm box through the serial port.

Procedure Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Convert Management System to start the Convert Management System. ----End

9.6.2 Setting the Parameters of the RNC Convert Management System This describes how to set the parameters of the Convert Management System to enable the system to perform properly the function of forwarding alarm information.

Prerequisite l

The Convert Management System is successfully started on the LMT PC.

l

The communication between the LMT and the RNC is functional.

l

The communication between the LMT and the alarm box is functional.

Procedure Step 1 Double-click the icon

in the status area on the bottom right of the window (if the

communication on the serial port is abnormal, the icon is System.

) to start the Convert Management

Step 2 Choose Operate > Configuration or click the shortcut icon 9-20


. Issue 03 (2009-04-25)

RNC LMT User Guide


Step 3 The Configuration dialog box is displayed, as shown in Figure 9-11. Figure 9-11 Configuring the Convert Management System

Step 4 In the Host IP box, enter the external virtual IP address of the BAM. Set the COM Port to the serial port that connects the LMT with the alarm box. Step 5 Click OK. If the Convert Management System window displays the following information, the configuration of the parameters for the system is successful. +++Begin2005-11-06 19:47:50 Prompt: Original connection is closed and new connection will be built with new configuration... +++End +++Begin2005-11-06 19:47:50 Prompt: COM communicate normally and connect the host now... +++End +++Begin2005-11-06 19:47:58 Prompt: Connection to host succeeded, alarm transfer begins... +++End

----End

9.6.3 Saving the Information in the Output Window This describes how to save the information in the output window for the analysis of the operating situation of the Convert Management System.

Prerequisite l

The Convert Management System is successfully started. The communication between the LMT and the BAM, and the communication between the LMT and the alarm box are functional.

l

The parameters of the Convert Management System are successfully set.

Procedure Step 1 Choose Operate > Save or click the shortcut icon as.

. You can also choose Operate > Save

Step 2 In the Save As dialog box, enter the file name in the File name box and select the file type from the Save as type drop-down list. Step 3 Click Save to save the information in the output window. ----End Issue 03 (2009-04-25)


9-21

RNC LMT User Guide


9.6.4 Exiting the RNC Convert Management System This describes how to exit the Convert Management System on the LMT PC when the audible and visible indications provided by the alarm box are no longer necessary. The LMT PC is connected to the alarm box.

Prerequisite The Convert Management System is successfully started.

Procedure Step 1 Perform any of the following ways to exit the Convert Management System. l

Choose Operate > Exit.

l

Click

l

Right-click

.

the icon is

in the status area (when the communication on the serial port is abnormal, ) and then choose Exit from the shortcut menu.

Step 2 In the displayed dialog box, click OK to exit the Convert Management System. ----End

9.7 Operating the RNC Alarm Box This describes how to operate the RNC alarm box. In the RNC, the LMT is connected to the universal alarm box of Huawei. When the LMT receives alarms sent from the BAM, the alarm box gives audible and visible indications. 9.7.1 Connecting the RNC Alarm Box to the RNC LMT This describes how to connect the LMT PC to the alarm box and set relevant parameters to enable the alarm box. 9.7.2 Resetting the RNC Alarm Box This describes how to reset the alarm box. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can reset alarm boxes. 9.7.3 Stopping an RNC Alarm Sound This describes how to stop an alarm sound. 9.7.4 Manually Turning Off an RNC Alarm Light This describes how to manually turn off an RNC alarm light. 9.7.5 Querying the Version of the RNC Alarm Box This describes how to query the version of the alarm box. 9.7.6 Querying the State of an RNC Alarm Light This describes how to query the number of alarms that the flashing light indicates. 9.7.7 Setting the Shield Severity of the RNC Alarm Box This describes how to set the shield severity of the alarm box. After the shield severity is set, the LMT does not send any fault alarm below the shield severity to the alarm box. 9.7.8 Querying the Mask Level of the RNC Alarm Box 9-22


Issue 03 (2009-04-25)

RNC LMT User Guide


This describes how to query the mask level of the alarm box.

9.7.1 Connecting the RNC Alarm Box to the RNC LMT This describes how to connect the LMT PC to the alarm box and set relevant parameters to enable the alarm box.

Prerequisite The LMT PC has an idle serial port.

Procedure Step 1 Connect the LMT PC to the alarm box using a serial port cable. Step 2 On the LMT PC, choose Start > All Programs > HUAWEI Local Maintenance Terminal > Convert Management System. The Convert Management System window is displayed, showing the following information: +++Begin2005-11-06 19:45:07 Prompt: COM communication exception, please check the connection. +++End

Step 3 In the Convert Management System window, choose Operate > Configuration. The Configuration dialog box is displayed, as shown in Figure 9-12. Figure 9-12 Configuring the Convert Management System

Step 4 Enter the external virtual IP address of the LMT-connected BAM and select the serial port that connects the LMT with the alarm box. Step 5 Click OK. When the Convert Management System window displays the following information, the connection between the LMT and the alarm box is successful. +++Begin2005-11-06 19:47:50 Prompt: Original connection is closed and new connection will be built with new configuration... +++End +++Begin2005-11-06 19:47:50 Prompt: COM communicate normally and connect the host now... +++End +++Begin2005-11-06 19:47:58 Prompt: Connection to host succeeded, alarm transfer begins... +++End

----End Issue 03 (2009-04-25)


9-23

RNC LMT User Guide


9.7.2 Resetting the RNC Alarm Box This describes how to reset the alarm box. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can reset alarm boxes.

Prerequisite l

The LMT is started.

l


l

The LMT is connected to the alarm box and it communicates with the alarm box normally.

l

The Convert Management System is started, and it communicates with the BAM normally.

Context To reset the alarm box, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Fault Management > Alarm Box Operation > Alarm Box Control or click box is displayed, as shown in Figure 9-13.

. The Alarm Box Control dialog

Figure 9-13 Resetting alarm box

l

2.

Select Reset Alarm Box.

3.

Click OK.

In MML mode 1.

Run the RST ALMBOX command on the MML client.

----End 9-24


Issue 03 (2009-04-25)

RNC LMT User Guide


9.7.3 Stopping an RNC Alarm Sound This describes how to stop an alarm sound.

Prerequisite l

The LMT is started.

l


l

The LMT is connected to the alarm box.

l


Context When the LMT receives fault alarms sent from the BAM, the alarm box emits sound until the fault is rectified. l

After the fault alarm is cleared, the alarm sound automatically stops.

l

If the alarm is not cleared, perform this operation to manually stop the alarm sound.

Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOMlevel operators can stop the alarm sound. To stop the alarm sound, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.



Figure 9-14 Alarm Box Control

Issue 03 (2009-04-25)

2.

Select Stop Alarm Sound in the dialog box.

3.

Click OK. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

9-25

RNC LMT User Guide


l

In MML mode 1.

Run the STP BOXSND command on the MML client.

----End

9.7.4 Manually Turning Off an RNC Alarm Light This describes how to manually turn off an RNC alarm light.

Prerequisite l

The LMT is started.

l


l


l


Context When the LMT receives fault alarms sent from the BAM, the color indicator on the alarm box corresponding to the alarm severity flashes until the fault is rectified. l

After the fault alarm is cleared, the status of the indicator becomes normal.

l

If the alarm is not cleared, perform the operation to manually turn off the alarm light, that is, to change the status of the light from flashing to normal.

Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOMlevel operators can turn off the alarm light. To manually turn off the alarm light, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.



Figure 9-15 Alarm Box Control

9-26


Issue 03 (2009-04-25)

RNC LMT User Guide


l

2.

Select Stop Alarm Status Lamp. Select an alarm severity from the Alarm Severity drop-down list.

3.

Click OK.

In MML mode 1.

Run the CLR BOXLGT command on the MML client.

----End

9.7.5 Querying the Version of the RNC Alarm Box This describes how to query the version of the alarm box.

Prerequisite l


l


l


Context To query the version of the alarm box, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

l

In the Local Maintenance Terminal window, choose Fault Management > Alarm Box Operation > Alarm Box Version.

In MML mode 1.

Run the LST BOXVER command on the MML client.

----End

9.7.6 Querying the State of an RNC Alarm Light This describes how to query the number of alarms that the flashing light indicates.

Prerequisite l


l


l


Context When the LMT receives one or more fault alarms of some severity level from the RNC, the corresponding indicator on the alarm box flashes. The flashing indicator, however, does not indicate the number of alarms. Issue 03 (2009-04-25)


9-27

RNC LMT User Guide


Procedure Run the LST BOXLGT command on the MML client. ----End

9.7.7 Setting the Shield Severity of the RNC Alarm Box This describes how to set the shield severity of the alarm box. After the shield severity is set, the LMT does not send any fault alarm below the shield severity to the alarm box.

Prerequisite l

The LMT is started.

l


Context Only the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOMlevel operators can set alarm shield severity. To set the alarm shield severity, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Fault Management > Alarm Box Operation > Shield Severity Set. The Alarmbox Shield Severity Setting dialog box is displayed, as shown in Figure 9-16. Figure 9-16 Setting the alarm shield severity

l

2.

Select the alarm severity from the Alarm Severity drop-down list.

3.

Click OK.

In MML mode 1.

Run the SET ALMSCRN command on the MML client.

----End

9.7.8 Querying the Mask Level of the RNC Alarm Box This describes how to query the mask level of the alarm box. 9-28


Issue 03 (2009-04-25)

RNC LMT User Guide



Context To set the alarm mask level, you can use either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

In the Local Maintenance Terminal window, choose Fault Management > Alarm Box Operation > Shield Severity Get. The Alarm Box Shield Severity Query dialog box is displayed, as shown in Figure 9-17. Figure 9-17 Querying alarm mask level

2. l

Click OK.

In MML mode 1.

Run the LST ALMSCRN command on the MML client.

----End

Issue 03 (2009-04-25)


9-29

RNC LMT User Guide

10 Managing RNC Logs

10

Managing RNC Logs

About This Chapter This describes how to manage RNC logs. The logs are saved in .txt and .log files. 10.1 Concepts of RNC Log Management This describes the following concepts of the RNC log management: RNC log types and authority of the RNC log operations. 10.2 Setting the Time and Count Limits of the RNC Log This describes how to set the limit for the continuous system run time that an operation or security log records and how to set the limit for the number of items that an operation or security log saves. If the run time or the quantity of saved items exceeds the limit, the BAM database automatically deletes oldest information. 10.3 Querying the Time and Count Limits of the RNC Log This describes how to query the time and quantity limits for the storage of the RNC operation log and RNC security log. 10.4 Querying an RNC Operation Log This describes how to query an operation log from the BAM database. By performing this task, you can learn about the RNC operation information. 10.5 Exporting an RNC Operation Log This describes how to use the FTP Client to download to the LMT an exported operation log that is saved in the directory BAM active workspace installation directory\FTP. 10.6 Querying RNC Security Logs This describes how to query the RNC security logs. The security logs record the results generated when the delivered and authenticated commands are run. By performing this task, you can learn about the information related to RNC operations. 10.7 Exporting an RNC Security Log This describes how to use the FTP Client to download to the LMT an exported security log that is saved in the directory BAM active workspace installation directory/FTP. 10.8 Exporting an RNC Running Log This describes how to use the FTP Client to download to the LMT an exported running log that is uploaded and saved in the directory BAM active workspace installation directory\LoadData \famlog. Issue 03 (2009-04-25)


10-1

RNC LMT User Guide


10.9 Collecting Fault Log Information This describes how to collect fault log information for fault location. Fault log information consists of the host log, BAM log, database log, system event log, operation log, BAM installation log, remote upgrade log, and alarm records.

10-2


Issue 03 (2009-04-25)

RNC LMT User Guide


10.1 Concepts of RNC Log Management This describes the following concepts of the RNC log management: RNC log types and authority of the RNC log operations. 10.1.1 RNC Log Types This describes the following RNC log types: operation log, security log, and running log. 10.1.2 RNC Log Management Authority Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can manage the logs.

10.1.1 RNC Log Types This describes the following RNC log types: operation log, security log, and running log.

RNC Operation Log The RNC operation log refers to all the real-time operation information recorded in the BAM database. The operation log is mainly used to analyze the relationships between device faults and performed operations.

RNC Security Log The RNC security log refers to the NE or EMS information related to security events such as login, logout, and authorization. The security log is used for auditing and tracing security events.

RNC Running Log The RNC running log refers to the system running information the RNC host records in real time. The running log helps you in fault location, routine inspection, and device running monitoring.

10.1.2 RNC Log Management Authority Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can manage the logs. NOTE

For details of the operator levels and the authorities for log management, refer to 7 Managing Authorities for RNC Operations.

10.2 Setting the Time and Count Limits of the RNC Log This describes how to set the limit for the continuous system run time that an operation or security log records and how to set the limit for the number of items that an operation or security log Issue 03 (2009-04-25)


10-3

RNC LMT User Guide


saves. If the run time or the quantity of saved items exceeds the limit, the BAM database automatically deletes oldest information.

Prerequisite l

The LMT is started.

l

You have logged in to the RNC with an account authorized for log management.

Procedure Step 1 Enter SET LOGLIMIT on the MML client, and then press Enter or click

.

Step 2 Set the limits in the Time Limit [Days] and Counts Limit [Items] boxes, and then choose a Log Type. Step 3 Press F9 or click

to run the command.

NOTE

l

Time Limit [Days] ranges from 7 to 365 days and the default setting is 30 days.

l

The range for Counts Limit [Items] is from 10,000 to 50,000 items, and the default setting is 50,000 items.

----End

10.3 Querying the Time and Count Limits of the RNC Log This describes how to query the time and quantity limits for the storage of the RNC operation log and RNC security log.

Prerequisite l

The LMT is started.

l


Procedure Step 1 Enter the LST LOGLIMIT command on the MML client, and press Enter or click Step 2 Choose Log Type, and then press F9 or click

.

to run the command.

----End

10.4 Querying an RNC Operation Log This describes how to query an operation log from the BAM database. By performing this task, you can learn about the RNC operation information.

Prerequisite l

10-4


Issue 03 (2009-04-25)

RNC LMT User Guide

10 Managing RNC Logs l


Procedure Step 1 Enter the LST OPTLOG command on the MML client, and press Enter or click

.

Step 2 Set the following parameters: l

Source

l

Operator

l

Domain Name

l

IP address

l

Start time

l

End time

l

Command name

l

Final

l

Number of records returned

Step 3 Press F9 or click

. The LMT lists the queried information.

NOTE

If no query parameter is set, the LMT lists the latest 64 operation records.

----End

10.5 Exporting an RNC Operation Log This describes how to use the FTP Client to download to the LMT an exported operation log that is saved in the directory BAM active workspace installation directory\FTP.

Procedure Step 1 On the MML client, run the EXP LOG command, set Log Type to OPTLOG(OPERATING LOG), and then set other parameters as required to export the operation log. When exporting operation logs, you can name the file or use the default name provided by the system. The default name of the exported file is RNC-start time-end time-OLOG.txt. l

If Time Mode is set to RELATIVE_T(relative_time), the operation log within N hour(s) before the time point of running the command is exported. N stands for the relative time length. For example, if Relative Time is 72, then the log within the latest 72 hours is exported.

l

If Time Mode is set to ONTIME(fixed_time), the operation log within the absolute time is exported. For example, Start Time for exporting the operation log is 11.06.07 16:57:01 and End Time is 12.06.07 16:57:01. The default file name is RNC-Y2007M06D11H17N32S46Y2007M06D12H17N32S46-OLOG.txt.

The default save path for the exported logs is BAM active workspace installation directory \FTP on the BAM active workspace. Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The FTP Client is started. Issue 03 (2009-04-25)


10-5

RNC LMT User Guide


Step 3 In the server entry bar shown in Figure 10-1, enter the external virtual IP address of the BAM, the FTP user name, and the password. NOTE

The user name and the password are case sensitive.

Figure 10-1 Server entry bar

Step 4 Click

on the toolbar or press Enter. The connection tip pane displays the connection status.

Step 5 After the connection is successful, in the server file list pane, double-click BAM active workspace installation directory\FTP. The server file list pane displays the files in the directory. Step 6 Based on the file name, double-click the operation log file, or select it and then click download it to the LMT.

to

NOTE

By double-clicking a file, you can download only that file. You can also select multiple files and then click to download all the selected files.

Step 7 When the download is complete, choose System > Exit or click the close button to exit the FTP Client. ----End

10.6 Querying RNC Security Logs This describes how to query the RNC security logs. The security logs record the results generated when the delivered and authenticated commands are run. By performing this task, you can learn about the information related to RNC operations.

Prerequisite l

The LMT is started.

l


Procedure Step 1 Enter the LST SECLOG command on the MML client, and press Enter or click

.

Step 2 Set the following parameters:

10-6

l

Source

l

Operator

l

Domain name

l

IP address Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide

10 Managing RNC Logs l

Start time

l

End time

l

Security log type

l

Security log levels

l

Final

l

Return code

l

Records to return

Step 3 Press F9 or click

. The LMT lists the queried information.

NOTE

If no query parameter is set, the LMT lists the security logs of the current day.

----End

10.7 Exporting an RNC Security Log This describes how to use the FTP Client to download to the LMT an exported security log that is saved in the directory BAM active workspace installation directory/FTP.

Procedure Step 1 On the MML client, run the EXP LOG command, set Log Type to SECLOG(SECURITY LOG), and then set other parameters as required to export the security log. When exporting operation logs, you can name the file or use the default name provided by the system. The default name of the exported file is RNC-start time-end time-OLOG.txt. l

If Time Mode is set to RELATIVE_T(relative_time), the security log within N hour(s) before the time point of running the command is exported. N stands for the relative time length. For example, if Relative Time is 72, then the log within the latest 72 hours is exported.

l

If Time Mode is set to ONTIME(fixed_time), the security log within the absolute time is exported. For example, Start Time for exporting the security log is 11.06.07 17:32:46 and End Time is 12.06.07 17:32:46. The default file name is RNC-Y2007M06D11H17N32S46Y2007M06D12H17N32S46-SLOG.txt.

The default save path for the exported logs is BAM active workspace installation directory/ FTP on the BAM active workspace. Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The FTP Client is started. Step 3 In the server entry bar shown in Figure 10-2, enter the external virtual IP address of the BAM, the FTP user name, and the password. NOTE



Issue 03 (2009-04-25)


10-7

RNC LMT User Guide


Step 4 Click


Step 5 After the connection is successful, in the server file list pane, double-click BAM active workspace installation directory/FTP. The server file list pane displays the files in the directory. Step 6 Based on the file name, double-click the security log file, or select it and then click download it to the LMT.

to

NOTE



10.8 Exporting an RNC Running Log This describes how to use the FTP Client to download to the LMT an exported running log that is uploaded and saved in the directory BAM active workspace installation directory\LoadData \famlog.

Procedure Step 1 On the MML client, run the ULD LOGTOBAM command, enter the subrack number, and then export the related running log file. NOTE

l

The format of the file name is subrack number/Log/yyyy/mm/dd/hh/mm/ss.log. For example, for the running log of the No. 3 RBS that is uploaded at 2005-11-07 17:19:47, the file name is 03Log20051107171947.log.

l

The default save path for the uploaded running logs is BAM active workspace installation directory \LoadData\famlog on the BAM active workspace.

Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The FTP Client is started. Step 3 In the server entry bar shown in Figure 10-3, enter the external virtual IP address of the BAM, the user name, and the password. NOTE



10-8


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 4 Click


Step 5 After the connection is successful, in the server file list pane, double-click BAM active workspace installation directory\LoadData\famlog. The server file list pane displays the files in the directory. Step 6 Based on the file name, double-click the running log file, or select it and then click download it to the LMT.

to

NOTE



10.9 Collecting Fault Log Information This describes how to collect fault log information for fault location. Fault log information consists of the host log, BAM log, database log, system event log, operation log, BAM installation log, remote upgrade log, and alarm records.

Procedure Step 1 Enter the COL LOG command on the MML client, and then press Enter or click Step 2 Set the parameters, and then press F9 or click

.

.

----End

Issue 03 (2009-04-25)


10-9

RNC LMT User Guide

11

11 Managing the RNC Equipment by Using the Device Panel and Display Panel

Managing the RNC Equipment by Using the Device Panel and Display Panel

About This Chapter This describes how to manage the RNC equipment by using the device panel and display panel. By performing this task, you can query the information about the boards, board ports, board links, and board alarms in GUI mode. 11.1 Using the RNC Device Panel This describes the RNC device panel. By performing this task, you can learn about how to start and use it, and how to query the status of the RNC boards. 11.2 Using the RNC Display Panel This describes the RNC display panel. By performing this task, you can learn about how to start the display panel and how to query the status of the RNC boards. 11.3 Viewing Active Alarms of an RNC Board This describes how to query the detailed alarm information on boards. It helps learn the working status of boards. 11.4 Querying the Configuration Mode of a Subrack This describes how to query the configuration mode of a subrack. By performing this task, you can learn about the current subrack status.

Issue 03 (2009-04-25)


11-1


RNC LMT User Guide

11.1 Using the RNC Device Panel This describes the RNC device panel. By performing this task, you can learn about how to start and use it, and how to query the status of the RNC boards. 11.1.1 Introduction to the RNC Device Panel The RNC system provides multiple modes for equipment maintenance. In addition to MML commands, the Local Maintenance Terminal provides the graphical device panel that simplifies the equipment maintenance. 11.1.2 Starting the RNC Device Panel This describes how to start the RNC device panel for operations on it. 11.1.3 Showing or Hiding the Legend on the RNC Device Panel This describes how to show and hide the legend on the RNC device panel. The color legend indicates the meanings of colors. It helps to judge the working statuses of boards. By performing this task, you can display or hide the color legend. 11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel When a fault occurs on a board, the failure bar displays the following information on the faulty board: cabinet number, subrack number, slot number, and board name. This task describes how to display or hide the failure bar on the RNC device panel. 11.1.5 Browsing the Status of an RNC Board This describes how to directly browse the status of an RNC board through the device panel. 11.1.6 Querying the Detailed Status of an RNC Board This describes how to query the detailed status of an RNC board. 11.1.7 Querying the CPU/DSP Usage of an RNC Board This describes how to query the CPU/DSP usage of an RNC board. By performing this task, you can learn about the usage of the CPU/DSP resources on a board.

11.1.1 Introduction to the RNC Device Panel The RNC system provides multiple modes for equipment maintenance. In addition to MML commands, the Local Maintenance Terminal provides the graphical device panel that simplifies the equipment maintenance. The device panel is automatically refreshed, showing board status in real time through the board colors, indicators, and failure bar. On the device panel, you can right-click a board in position and choose operations from the shortcut menu. For example, you can query the board status. Figure 11-1 shows the device panel.

11-2


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 11-1 RNC device panel

NOTE

In Figure 11-1, green indicates the normal status of the active board and light blue indicates the normal status of the standby board. You can run the DSP BRD command to query the transport mode of the OUIa shown in Figure 11-1.

Related Tasks 11.1.2 Starting the RNC Device Panel 11.1.3 Showing or Hiding the Legend on the RNC Device Panel 11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel 11.1.5 Browsing the Status of an RNC Board 11.1.6 Querying the Detailed Status of an RNC Board 11.1.7 Querying the CPU/DSP Usage of an RNC Board

11.1.2 Starting the RNC Device Panel This describes how to start the RNC device panel for operations on it.


Procedure Step 1 In the Local Maintenance Terminal window, click the Device Panel tab. Step 2 Expand the Device Management node, as shown in Figure 11-2.

Issue 03 (2009-04-25)


11-3


RNC LMT User Guide

Figure 11-2 Navigation tree of the device panel

Step 3 Double-click a shelf. The device panel of the shelf is displayed in the right pane. ----End

Related Concepts 11.1.1 Introduction to the RNC Device Panel

Related Tasks 11.1.3 Showing or Hiding the Legend on the RNC Device Panel 11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel 11.1.5 Browsing the Status of an RNC Board 11.1.6 Querying the Detailed Status of an RNC Board 11.1.7 Querying the CPU/DSP Usage of an RNC Board

11.1.3 Showing or Hiding the Legend on the RNC Device Panel This describes how to show and hide the legend on the RNC device panel. The color legend indicates the meanings of colors. It helps to judge the working statuses of boards. By performing this task, you can display or hide the color legend.

Prerequisite l


l

The device panel is started.

l

To display the color legend, perform the following step:

Procedure 1. 11-4

Click

on the top right of the device panel, as shown in Figure 11-3. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 11-3 Displaying the color legend

l

To hide the color legend, perform the following step: 1.

Click

on the top right of the device panel, as shown in Figure 11-4.

Figure 11-4 Hiding the color legend

NOTE

By default, the color legend is always displayed.

----End


Related Tasks 11.1.2 Starting the RNC Device Panel

Issue 03 (2009-04-25)


11-5


RNC LMT User Guide

11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel When a fault occurs on a board, the failure bar displays the following information on the faulty board: cabinet number, subrack number, slot number, and board name. This task describes how to display or hide the failure bar on the RNC device panel.

Prerequisite l


l


l

There are one or more faulty boards.

l

To show the failure bar, perform the following step:

Procedure 1.

Right-click the edge of the shelf and then choose Show Failure Bar from the shortcut menu, as shown in Figure 11-5.

Figure 11-5 Showing the failure bar

l

To hide the failure bar, perform the following step: 1.

11-6

Right-click the edge of the shelf and choose Hide Failure Bar from the shortcut menu, as shown in Figure 11-6. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 11-6 Hiding the failure bar

----End



11.1.5 Browsing the Status of an RNC Board This describes how to directly browse the status of an RNC board through the device panel.

Prerequisite l


l


Procedure View the status of an RNC board by referring to the legend on the device panel. ----End Issue 03 (2009-04-25)


11-7


RNC LMT User Guide



11.1.6 Querying the Detailed Status of an RNC Board This describes how to query the detailed status of an RNC board.

Prerequisite l


l

The boards are in position.

Context You can either use the device or display panel or run the MML commands to perform this task.

Procedure l

In GUI mode 1.

Open the device panel or open the display panel.

2.

Right-click a board in position in the device panel or display panel, and then choose Query Board State from the shortcut menu. The Query Board State dialog box is displayed, showing details of the board. Figure 11-7 shows the query result of the SPUa in slot 4 of subrack 0. Figure 11-7 Querying details of boards

11-8


Issue 03 (2009-04-25)

RNC LMT User Guide


l

In MML mode Run the following commands on the MML client to query the detailed information on boards: –

Run DSP BRD to query board details.

–

Run DSP CPUUSAGE to query CPU usage of board subsystems.

–

Run DSP CLK to query clock states of boards.

–

Run DSP DSP to query working states of DSPs on the DPU.

----End



11.1.7 Querying the CPU/DSP Usage of an RNC Board This describes how to query the CPU/DSP usage of an RNC board. By performing this task, you can learn about the usage of the CPU/DSP resources on a board.

Prerequisite l


l


Procedure Step 1 Open the device panel or open the display panel. Step 2 Right-click a board in position in the device panel or display panel, and then choose Display CPU Usage from the shortcut menu. The CPU/DSP Usage window is displayed, showing realtime monitoring results in either list or chart. Figure 11-8 is an example of the output interface (list) of the CPU/DSP Usage window.

Issue 03 (2009-04-25)


11-9


RNC LMT User Guide

Figure 11-8 Output interface of the CPU/DSP Usage window

----End



11.2 Using the RNC Display Panel This describes the RNC display panel. By performing this task, you can learn about how to start the display panel and how to query the status of the RNC boards. 11.2.1 Introduction to the RNC Display Panel The LMT provides the display panel, which bears close resemblance to the panels of the boards. The display panel helps to learn the status of each board. 11.2.2 Starting the RNC Display Panel This describes how to start the display panel that helps learn the running status of the equipment. 11.2.3 Querying the Status of FE Ports on an RNC Board This describes how to query the detailed status of the FE ports on an RNC board. 11.2.4 Querying the Status of GE Ports on an RNC Board 11-10


Issue 03 (2009-04-25)

RNC LMT User Guide


This describes how to query the detailed status of the GE ports on an RNC board. 11.2.5 Querying the Detailed Status of a DSP on the DPUb Board This describes how to view the status of a DSP on the DPUb. The DSP working status includes normal, in place, loading, and faulty. 11.2.6 Querying the Detailed Status of an E1/T1 Link This describes how to query the detailed status of an E1/T1 link on an RNC board. 11.2.7 Querying Alarms through a Board Alarm Light This describes how to query the alarms through a board alarm light.

11.2.1 Introduction to the RNC Display Panel The LMT provides the display panel, which bears close resemblance to the panels of the boards. The display panel helps to learn the status of each board. Through the display panel, you can see the status of each board or port. You can also perform related operations by clicking and right-clicking the display panel, as shown in Figure 11-9. Figure 11-9 RNC display panel

The display panel has the following functions: l

Issue 03 (2009-04-25)

Showing the running status of the device in GUI mode Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

11-11

11 Managing the RNC Equipment by Using the Device Panel and Display Panel l

RNC LMT User Guide

You can perform the following operations from the shortcut menu: querying the detailed status of an RNC board, querying the CPU/DSP usage of an RNC board, and querying the port status of an RNC board.

Related Tasks 11.2.2 Starting the RNC Display Panel 11.2.3 Querying the Status of FE Ports on an RNC Board 11.2.4 Querying the Status of GE Ports on an RNC Board 11.2.5 Querying the Detailed Status of a DSP on the DPUb Board 11.2.6 Querying the Detailed Status of an E1/T1 Link 11.2.7 Querying Alarms through a Board Alarm Light

11.2.2 Starting the RNC Display Panel This describes how to start the display panel that helps learn the running status of the equipment.


Procedure Step 1 In the navigation pane of the Local Maintenance Terminal window, click the Device Panel tab. Expand the Device Management node. Step 2 Double-click a shelf. The device panel is displayed. Step 3 Double-click the edge of a subrack, as shown in Figure 11-10. The display panel is displayed. Figure 11-10 Edge of a subrack

----End

Related Concepts 11.2.1 Introduction to the RNC Display Panel 11-12


Issue 03 (2009-04-25)

RNC LMT User Guide


Related Tasks 11.2.3 Querying the Status of FE Ports on an RNC Board 11.2.4 Querying the Status of GE Ports on an RNC Board 11.2.5 Querying the Detailed Status of a DSP on the DPUb Board 11.2.6 Querying the Detailed Status of an E1/T1 Link 11.2.7 Querying Alarms through a Board Alarm Light

11.2.3 Querying the Status of FE Ports on an RNC Board This describes how to query the detailed status of the FE ports on an RNC board.

Prerequisite l


l


l

The display panel is started.

Procedure On the display panel, right-click the FE port to be queried, choose Display Ethernet Port State. The Display Ethernet Port State dialog box is displayed, as shown in Figure 11-11. Figure 11-11 Status of an FE port

----End

Related Concepts 11.2.1 Introduction to the RNC Display Panel Issue 03 (2009-04-25)


11-13


RNC LMT User Guide

Related Tasks 11.2.2 Starting the RNC Display Panel

11.2.4 Querying the Status of GE Ports on an RNC Board This describes how to query the detailed status of the GE ports on an RNC board.

Prerequisite l


l


l


Procedure On the display panel, right-click the GE port to be queried, choose Display the GE port status of SCUa's board panel. The Display the GE port status of SCUa's board panel dialog box is displayed, as shown in Figure 11-12. Figure 11-12 Status of an GE port

----End

Related Concepts 11.2.1 Introduction to the RNC Display Panel

Related Tasks 11.2.2 Starting the RNC Display Panel 11-14


Issue 03 (2009-04-25)

RNC LMT User Guide


11.2.5 Querying the Detailed Status of a DSP on the DPUb Board This describes how to view the status of a DSP on the DPUb. The DSP working status includes normal, in place, loading, and faulty.

Prerequisite l


l

The board is in the specified slot.

Context You can perform this task in either of the following modes: GUI and MML.

Procedure l

In GUI mode 1.

Perform 11.2.2 Starting the RNC Display Panel.

2.

On the display panel, point to a DPUb port to be viewed and rest on it to see the current DSP status. You can also right-click a DPUb port to be viewed and choose Query DSP State from the shortcut menu. A dialog box showing the DSP status is displayed, as shown in Figure 11-13. Figure 11-13 Query DSP Status

l

In MML mode 1.

Run the DSP DSP MML command to query the working status of a DSP on the DPUb.

----End

Related Concepts 11.2.1 Introduction to the RNC Display Panel Issue 03 (2009-04-25)


11-15


RNC LMT User Guide


11.2.6 Querying the Detailed Status of an E1/T1 Link This describes how to query the detailed status of an E1/T1 link on an RNC board.

Prerequisite l


l


l


Procedure On the display panel, right-click the E1/T1 link to be queried, choose Query E1/T1 Link State. The Query E1/T1 Link State dialog box is displayed, as shown in Figure 11-14. Figure 11-14 Detailed status of an E1/T1 link

----End


Related Tasks 11.2.2 Starting the RNC Display Panel 11-16


Issue 03 (2009-04-25)

RNC LMT User Guide


11.2.7 Querying Alarms through a Board Alarm Light This describes how to query the alarms through a board alarm light.

Prerequisite l


l


l


Procedure On the display panel, right-click the alarm light to be queried, and then choose Query The Alarm Information Of Alarm Lamp. The Query The Alarm Information Of Alarm Lamp dialog box is displayed, as shown in Figure 11-15. Figure 11-15 Querying alarms through an alarm light

----End



11.3 Viewing Active Alarms of an RNC Board This describes how to query the detailed alarm information on boards. It helps learn the working status of boards. Issue 03 (2009-04-25)


11-17


RNC LMT User Guide


Procedure Run the LST ALMAF command on the MML client to query active alarms of boards. ----End

11.4 Querying the Configuration Mode of a Subrack This describes how to query the configuration mode of a subrack. By performing this task, you can learn about the current subrack status.


Procedure In the main window of the Local Maintenance Terminal, click the drop-down list shown in Figure 11-16 on the right of the toolbar to check the configuration mode of each subrack. Figure 11-16 Configuration modes of subracks

----End

11-18


Issue 03 (2009-04-25)

RNC LMT User Guide

12 Tracing and Viewing RNC Messages

12

Tracing and Viewing RNC Messages

About This Chapter This describes how to manage the RNC traced messages. RNC message tracing is implemented through menus. You can use the Trace Viewer to query the tracing data recorded in the files. 12.1 Concepts of RNC Message Tracing Management This describes the basic concepts of the RNC message tracing management. 12.2 Tracing Iu Interface Messages This describes how to trace the signaling messages over the Iu interface, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the fault in the failure of the following procedures: RAB assignment, RAB release, paging, Iu release, security mode control, initial UE message, and relocation. 12.3 Tracing Iur Interface Messages This describes how to trace the signaling messages over the Iur interface, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the fault in the following scenarios: radio link setup failure, radio link addition failure, radio link deletion, resource release failure on common transport channel, DL power control failure, and paging failure. 12.4 Tracing Iub Interface Messages This describes how to trace signaling messages over the Iub interface, that is, NodeB Application Part (NBAP) messages. You can perform this task to identify the fault in the failure of the following procedures: radio link setup, radio link reconfiguration, resource audit, cell setup, cell reconfiguration, common transport channel setup, and system information update. 12.5 Tracing Uu Interface Messages This describes how to trace all or part of the signaling messages over the Uu interface in a specified cell. You can perform this task to locate the fault in the following scenarios: RRC connection setup failure, radio bearer setup failure, physical channel reconfiguration failure, and cell update failure. 12.6 Tracing UE Messages This describes how to monitor the interworking of signaling on the standard interfaces, the interworking of signaling on the user plan, and the uplink and downlink traffic during the call. You can perform this task to locate the signaling problems of the VIP subscribers, in combination with the drive test result. Issue 03 (2009-04-25)


12-1


RNC LMT User Guide

12.7 Tracing IOS Messages This describes how to trace a number of calls that meet the sampling criteria within a specified range of cells. When creating the task, you can specify the number of calls to be traced. You can also specify the messages to be traced by selecting the event type. 12.8 Tracing Cell Messages This describes how to trace the NBAP common messages on the Iub interface of a specified cell. You can perform this task to locate the fault on the common channel, to locate the problem of no access or low access success rate of the cell, and to collect the user volume in the cell. 12.9 Tracing REDIRECT Messages This describes how to redirect messages that are printed through the serial port of a specified subsystem to the message browse window. 12.10 Tracing MNCDT Messages This describes how to trace the missing neighbor cell relations of a cell. The Missing Neighbor Cell Detect Trace (MNCDT) tracing task involves three independent detection types: detection of missing intra-frequency neighboring cell relations, detection of missing inter-frequency neighboring cell relations, and detection of missing inter-RAT neighboring cell relations. 12.11 Tracing OS Messages This describes how to trace messages between the exchange module of the BAM and internal modules of a board or between internal modules of different boards. 12.12 Tracing SCCP Messages This describes how to monitor the interworking of SCCP messages respectively over the Iu and Iur interfaces, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the link setup failure or link release abnormality on the Iu and Iur interfaces. 12.13 Tracing MTP3 Messages This describes how to trace the MTP3 messages, including the MTP3 upper layer (QAAL2 and SCCP) messages, MTP3 signaling link test messages, and MTP3 signaling network management messages. 12.14 Tracing QAAL2 Messages This describes how to monitor the interworking of QAAL2 messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to locate the setup failure or release abnormality of an ATM Adaptation Layer type 2 (AAL2) connection on the user plane respectively on the Iu, Iur, and Iub interfaces. 12.15 Tracing SAAL Messages This describes how to monitor the interworking of SAAL messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to locate the problem of non-availability of SAAL link on the Iu, Iur, and Iub interfaces. 12.16 Tracing SCTP Messages This describes how to trace the SCTP messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to trace the interworking of SCTP messages and to locate the problem of non-availability of SCTP link on the Iu, Iur, and Iub interfaces. 12.17 Tracing M3UA Messages This describes how to trace the M3UA Messages over the Iu and Iur interfaces. You can perform this task to locate the problem that the M3UA link is unavailable while the corresponding IP link is available. 12.18 Tracing Location Messages 12-2


Issue 03 (2009-04-25)

RNC LMT User Guide


This describes how to trace the results of a location tracing initiated by the CN. This task can also simulate the CN to initiate a location tracing and trace the results. 12.19 Basic Operations of RNC Message Tracing This describes how to perform the following operations of RNC message tracing: browsing an RNC traced message online, querying the properties of a tracing task, viewing the translation of a traced message, saving an RNC traced message, pausing an RNC tracing task, resuming an RNC tracing task, stopping an RNC tracing task, and browsing an RNC traced message offline. 12.20 Parameter Reference for RNC Message Tracing and Viewing This describes the parameters used for each message tracing.

Issue 03 (2009-04-25)


12-3

RNC LMT User Guide


12.1 Concepts of RNC Message Tracing Management This describes the basic concepts of the RNC message tracing management. 12.1.1 Functions of RNC Message Tracing Management RNC message tracing management is used to trace interfaces, signaling links, and internal messages. It is applicable to routine equipment maintenance, debugging, and fault location. 12.1.2 Working Principles of RNC Message Tracing Management This describes the working principles of the message tracing. It also describes how to create or close message trace tasks and the internal process for the service module to report traced messages to the LMT. 12.1.3 Authority of RNC Message Tracing Management You can perform the message tracing management operations only when you are authorized.

12.1.1 Functions of RNC Message Tracing Management RNC message tracing management is used to trace interfaces, signaling links, and internal messages. It is applicable to routine equipment maintenance, debugging, and fault location. The RNC provides the following tracing functions: l

RNC Message Tracing on Standard Interfaces

l

UE tracing

l

Call tracing

l

Message tracing at the transport network layer

l

MNCDT tracing

l

Cell tracing

l

OS tracing

l

REDIRECT tracing

l

Location message tracing

12.1.2 Working Principles of RNC Message Tracing Management This describes the working principles of the message tracing. It also describes how to create or close message trace tasks and the internal process for the service module to report traced messages to the LMT.

Working Principles of the Message Tracing Figure 12-1 shows the working principles of the message tracing.

12-4


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-1 Working principles of the message tracing

Internal Process for Creating the Tracing Task 1.

The operator creates a tracing task on the LMT and the LMT sends a binary command to the BAM to create the task.

2.

The BAM assigns an ID to the task and forwards the command to the debugging module of the specified board.

3.

After receiving the command, the debugging module records the filter parameters of the tracing data in the filter table and notifies the service module.

4.

The service module updates the local filter table according to the message from the debugging module.

Internal Process for Closing the Tracing Task 1.

The operator closes a tracing task on the LMT and the LMT sends a binary command to the BAM to delete the task.

2.

The BAM forwards the command to the specified board according to the task ID.

3.

The commissioning module and service module delete the task from the filter table.

Internal Process for the Service Module to Report Traced Messages to the LMT 1.

The service module filters the collected messages according to the filter parameters in the local filter table and reports the messages that meet the requirements to the BAM.

2.

The BAM forwards the traced messages to the LMT that creates the task according to the task ID.

3.

The LMT translates the messages and displays them on the interface.

12.1.3 Authority of RNC Message Tracing Management You can perform the message tracing management operations only when you are authorized. The operators at the following levels can perform the online tracing tasks: admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command group G_10. That is, except operators at GUEST-level and CUSTOM not entitled to use command group G_10, all the others have the authority to perform the online tracing tasks. Issue 03 (2009-04-25)


12-5

RNC LMT User Guide

12 Tracing and Viewing RNC Messages NOTE

Group G_10 contains commands for tracing and query. It is a binary command group, which contains no MML commands.

Related Tasks 12.2 Tracing Iu Interface Messages 12.3 Tracing Iur Interface Messages 12.4 Tracing Iub Interface Messages 12.5 Tracing Uu Interface Messages 12.6 Tracing UE Messages 12.7 Tracing IOS Messages 12.8 Tracing Cell Messages 12.9 Tracing REDIRECT Messages 12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells 12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells 12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells 12.11 Tracing OS Messages 12.12 Tracing SCCP Messages 12.13 Tracing MTP3 Messages 12.14 Tracing QAAL2 Messages 12.15 Tracing SAAL Messages 12.16 Tracing SCTP Messages 12.17 Tracing M3UA Messages 12.18 Tracing Location Messages

12.2 Tracing Iu Interface Messages This describes how to trace the signaling messages over the Iu interface, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the fault in the failure of the following procedures: RAB assignment, RAB release, paging, Iu release, security mode control, initial UE message, and relocation.

Prerequisite l

The LMT is running normally.

l


Context You can start the Iu interface tracing on the LMT to monitor the interworking of signaling messages over the Iu interface. To start a tracing task, you can select the following operations:

12-6

l

Tracing the messages processed by the specified SPU subsystem

l

Tracing the required message types Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide

12 Tracing and Viewing RNC Messages l

Tracing all message types

l

Tracing signaling messages at the transport network layer

For each subsystem, a maximum of six Iu interface tracing tasks can be performed simultaneously. When creating two or more tasks of the same type, do not set their parameters completely the same. Otherwise, only one tracing task can be created successfully.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-2. Figure 12-2 Setting the parameters for Iu interface tracing

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select Iu in the Trace Type area.

Issue 03 (2009-04-25)


12-7


RNC LMT User Guide

Step 3 Click the Iu tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. ----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-3. Figure 12-3 Output of Iu interface tracing

NOTE

In the message browse window of Iu Interface Tracing, the number in the Information Source column represents the DPC of the peer CN equipment. You can query more information about the DPC by running the command LST N7DPC.

Related Concepts 12.1.3 Authority of RNC Message Tracing Management

Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12.19.5 Pausing an RNC Tracing Task 12.19.6 Resuming an RNC Tracing Task 12.19.7 Closing an RNC Tracing Task 12-8


Issue 03 (2009-04-25)

RNC LMT User Guide


Related References 12.20.1 Parameter Reference for Iu Interface Tracing

12.3 Tracing Iur Interface Messages This describes how to trace the signaling messages over the Iur interface, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the fault in the following scenarios: radio link setup failure, radio link addition failure, radio link deletion, resource release failure on common transport channel, DL power control failure, and paging failure.

Prerequisite l


l


Context You can start the Iur interface tracing on the LMT to monitor the interworking of signaling messages over the Iur interface. To start a tracing task, you can select the following operations: l


l

Tracing the required message types

l

Tracing all message types

l


For each subsystem, a maximum of six Iur interface tracing tasks can be performed simultaneously. When creating two or more tasks of the same type, do not set their parameters completely the same. Otherwise, only one tracing task can be created successfully.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Iur. A dialog box is displayed, as shown in Figure 12-4.

Issue 03 (2009-04-25)


12-9


RNC LMT User Guide

Figure 12-4 Setting the parameters for Iur interface tracing

Step 2 In the 12.20.2 Parameter Reference for Iur Interface Tracing dialog box, set the parameters in the Basic tab page. Select Iur in the Trace Type area. Step 3 Click the Iur tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. ----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-5.

12-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-5 Output of Iur interface tracing

NOTE

In the message browse window of Iur Interface Tracing, the number in the Information Source column represents the DPC of the neighboring RNC. You can query more information about the DPC by running the command LST N7DPC.


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12.19.5 Pausing an RNC Tracing Task 12.19.6 Resuming an RNC Tracing Task 12.19.7 Closing an RNC Tracing Task

Related References 12.20.2 Parameter Reference for Iur Interface Tracing

Issue 03 (2009-04-25)


12-11

RNC LMT User Guide


12.4 Tracing Iub Interface Messages This describes how to trace signaling messages over the Iub interface, that is, NodeB Application Part (NBAP) messages. You can perform this task to identify the fault in the failure of the following procedures: radio link setup, radio link reconfiguration, resource audit, cell setup, cell reconfiguration, common transport channel setup, and system information update.

Prerequisite l


l


Context You can start the Iub interface tracing on the LMT to monitor the interworking of signaling messages over the Iub interface. To start a tracing task, you can select the following operations: l

Tracing messages of all the NodeBs

l

Tracing messages on all the ports of the specified NodeB

l

Tracing messages on the specified port of the specified NodeB

l


l

Selecting the types of traced messages

l


For each subsystem, a maximum of six Iub interface tracing tasks can be performed simultaneously. When creating two or more tasks of the same type, do not set their parameters completely the same. Otherwise, only one tracing task can be created successfully.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Iub. A dialog box is displayed, as shown in Figure 12-6.

12-12


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-6 Setting the parameters for Iub interface tracing

Step 2 In the 12.20.3 Parameter Reference for Iub Interface Tracing dialog box, set the parameters in the Basic tab page. Select Iub in the Trace Type area. Step 3 Click the Iub tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. NOTE

l

You can query the NodeB ID and other information about the NodeB by running the command LST NODEB.

l

You can query the NodeB port type and other information about the port by running the command LST IUBCP.

----End


Issue 03 (2009-04-25)


12-13


RNC LMT User Guide

Figure 12-7 Output of Iub interface tracing

NOTE

In the message browse window of the Iub interface tracing task, the number in the Information Source column represents the NodeB ID. You can query more information about the NodeB by running the command LST NODEB.



Related References 12.20.3 Parameter Reference for Iub Interface Tracing

12.5 Tracing Uu Interface Messages This describes how to trace all or part of the signaling messages over the Uu interface in a specified cell. You can perform this task to locate the fault in the following scenarios: RRC connection setup failure, radio bearer setup failure, physical channel reconfiguration failure, and cell update failure. 12-14


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l


l


Context You can start the Uu interface tracing on the LMT to monitor the interworking of signaling messages over the Uu interface. To start a tracing task, you can select the following operations: l

Tracing one or multiple RNCs and cells

l

Tracing all the types of messages on the Uu interface

l

Tracing the specified types of messages

A maximum of six Uu interface tracing tasks can be performed simultaneously in an RNC. Each Uu interface tracing task targets at a maximum of 32 cells. When creating two or more tasks of the same type, do not set their parameters completely the same. Otherwise, only one tracing task can be created successfully.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Uu. A dialog box is displayed, as shown in Figure 12-8. Figure 12-8 Setting the parameters for Uu interface tracing

Issue 03 (2009-04-25)


12-15


RNC LMT User Guide

Step 2 In the 12.20.4 Parameter Reference for Uu Interface Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows the message flow of the interface. ----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-9. Figure 12-9 Output of Uu interface tracing

NOTE

l

In the message browse window of Uu interface tracing task, the RNC ID represents the SRNC ID. If the UE accesses the network through DRNC, the DRNC ID is traced. You can query the RNC ID by running the command LST RNCBASIC.

l

In the message browse window of Uu Interface Tracing task, cell represents the cell that transmits or receives the message. You can query the cell information by running the command LST CELL.


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12-16


Issue 03 (2009-04-25)

RNC LMT User Guide


12.19.5 Pausing an RNC Tracing Task 12.19.6 Resuming an RNC Tracing Task 12.19.7 Closing an RNC Tracing Task

Related References 12.20.4 Parameter Reference for Uu Interface Tracing

12.6 Tracing UE Messages This describes how to monitor the interworking of signaling on the standard interfaces, the interworking of signaling on the user plan, and the uplink and downlink traffic during the call. You can perform this task to locate the signaling problems of the VIP subscribers, in combination with the drive test result.

Prerequisite l


l


Context The UE tracing task is to trace signaling messages of a UE on all the Iu, Iur, Iub and Uu interfaces or specified interfaces. The UE can be specified by IMSI, TMSI, P-TMSI, or IMEI. NOTE

Each RNC supports a maximum of 12 UE tracing tasks simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click UE. A dialog box is displayed, as shown in Figure 12-10.

Issue 03 (2009-04-25)


12-17


RNC LMT User Guide

Figure 12-10 Setting the parameters for UE tracing

Step 2 In the 12.20.5 Parameter Reference for UE Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows the message flow of the UE. ----End

Postrequisite The message browse window displays the serial number, generation time, tracing type, subrack number, slot number, subsystem number, message direction, message type, user ID, and message content, as shown in Figure 12-11.

12-18


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-11 Output of UE tracing

NOTE

l

Assume that you trace a UE by specifying the IMSI and a consistent IMSI is included in the RRC CONNECTION REQUEST message from the UE. Then, the UE tracing task traces all the messages that are sent after the RRC CONNECTION REQUEST message.

l

Assume that you trace a UE by specifying the IMSI and a consistent IMSI is included only in the RANAP COMMON ID message but not in the RRC CONNECTION REQUEST message from the UE. If CDT_MSG_FULL_TRACE is set to ON, the UE tracing task traces the messages that are sent after the RANAP COMMON ID message, and the messages before the RANAP COMMON ID message are buffered and reported to the RNC. If CDT_MSG_FULL_TRACE is set to OFF, the messages before the RANAP COMMON ID message are discarded instead of being buffered.

l

In the tracing result displayed in the message browse window of UE Tracing, the number displayed in the User ID column has different meanings for different interfaces: l

For the Iu interface, the user ID represents DPC ID at the CN side.

l

For the Iu interface, the user ID represents DPC ID at the RNC side.

l

For the Iub interface, the user ID represents NODEB ID.

l

For the Uu interface, the user ID represents CELL ID.


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task Issue 03 (2009-04-25)


12-19

RNC LMT User Guide


12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12.19.5 Pausing an RNC Tracing Task 12.19.6 Resuming an RNC Tracing Task 12.19.7 Closing an RNC Tracing Task

Related References 12.20.5 Parameter Reference for UE Tracing

12.7 Tracing IOS Messages This describes how to trace a number of calls that meet the sampling criteria within a specified range of cells. When creating the task, you can specify the number of calls to be traced. You can also specify the messages to be traced by selecting the event type.

Prerequisite l


l


l

Assume that the specified number of continuous calls is N. If N calls are already being traced, the system does not trace any newly accessed calls. If the number becomes less than N because of the termination of a traced call, the system automatically traces a new call.

l

A maximum of six IOS tracing tasks can be performed simultaneously. Each task targets at a maximum of 30 calls and 32 cells.

l

You need to specify the number of calls to be traced, tracing cell range, sampling criteria, and tracing time. The calls that meet the sampling criteria are traced within the specified period of trace time.

Context

When creating a new call tracing task, you can define the sampling criteria by setting the RAB parameter constraints and the RRC Est Cause. Once the call meets the criteria, the tracing of the call is not stopped even if the RAB parameters of the RRC establishment cause are changed during the call. If the initial settings of the RAB parameters and the RRC establishment cause of a call do not meet the criteria, the RNC does not trace the call even if these parameters are modified to meet the criteria during the call. You can specify the message types to be traced by selecting the event types. You can also select one or more cells to trace.

CAUTION The IOS tracing task involves a large amount of trace information, which affects the system operation. Therefore, Call counts in the IOS Tracing dialog box should not be set too high. In addition, you are advised not to trace all events at a time. Furthermore, you should minimize the frequencies of performing this task.

12-20


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > Interface Trace Task, and then double-click IOS. Step 2 In the 12.20.6 Parameter Reference for IOS Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows the message flow of the interface. NOTE

l

If the RRC establishment cause is specified and the RNC receives an RRC_CONN_REQ message of a call that matches a specified RRC establishment cause in the specified cell, the call is traced.

l

If the RAB parameters are specified and the RNC receives an RAB ASSIGNMENT REQUEST message of a call that matches the specified RAB parameters in the specified cell, the call is traced.

l

If a call sets up multiple RAB services, the call is traced if one of them meets the specified RAB parameters.

----End



Related References 12.20.6 Parameter Reference for IOS Tracing

12.8 Tracing Cell Messages This describes how to trace the NBAP common messages on the Iub interface of a specified cell. You can perform this task to locate the fault on the common channel, to locate the problem of no access or low access success rate of the cell, and to collect the user volume in the cell.

Prerequisite l


l


Issue 03 (2009-04-25)


12-21

RNC LMT User Guide


Context NOTE

l

A maximum of six cell tracing tasks can be created at one time. Each cell tracing task targets at only one cell.

l

Each Cell tracing task targets at only one cell.

l

Each Cell tracing task targets at up to two S-CCPCHs.

l

The cell to be traced must be activated.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Cell. Step 2 In the 12.20.7 Parameter Reference for Cell Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows the message flow of the interface. NOTE

You can query the cell ID and other cell information by running the command LST CELL.

----End



Related References 12.20.7 Parameter Reference for Cell Tracing

12.9 Tracing REDIRECT Messages This describes how to redirect messages that are printed through the serial port of a specified subsystem to the message browse window.

Prerequisite

12-22

l


l


Issue 03 (2009-04-25)

RNC LMT User Guide


Context

CAUTION For a subsystem, only one redirect tracing task can be started. When there are many messages printed through the serial port, the REDIRECT tracing task may affect the performance of the system. REDIRECT tracing is started on the RNC LMT or M2000. You can use the Trace Viewer to view the tracing data recorded in the files. NOTE

A maximum of five REDIRECT tracing can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click REDIRECT. A dialog box is displayed, as shown in Figure 12-12. Figure 12-12 Setting the parameters for REDIRECT tracing

Step 2 In the 12.20.8 Parameter Reference for REDIRECT Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows returned information. ----End

Postrequisite The system displays the details of the traced messages in the message browse window, as shown in Figure 12-13.

Issue 03 (2009-04-25)


12-23


RNC LMT User Guide

Figure 12-13 Output of REDIRECT tracing

Right-click in the message browse window, and then choose Redirection from the shortcut menu. The Save in dialog box is displayed, as shown in Figure 12-14. Figure 12-14 Save dialog box

12-24


Issue 03 (2009-04-25)

RNC LMT User Guide




Related References 12.20.8 Parameter Reference for REDIRECT Tracing

12.10 Tracing MNCDT Messages This describes how to trace the missing neighbor cell relations of a cell. The Missing Neighbor Cell Detect Trace (MNCDT) tracing task involves three independent detection types: detection of missing intra-frequency neighboring cell relations, detection of missing inter-frequency neighboring cell relations, and detection of missing inter-RAT neighboring cell relations. 12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells This describes how to trace messages of missed intra-frequency neighboring cells in the same band. 12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells This describes how to trace messages of missed inter-frequency neighboring cells in different bands. 12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells This describes how to trace messages of missed inter-RAT neighboring cells in different systems.


Issue 03 (2009-04-25)


12-25

RNC LMT User Guide


12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells This describes how to trace messages of missed intra-frequency neighboring cells in the same band.

Prerequisite l

The LMT is started.

l


l

The detect switch of the missed intra-frequency neighboring cell tracing is set to ON. (You can query this by running LST NCELLDETECTSWITCH.)

Procedure Step 1 In the navigation pane, click the Maintenance tab in the Local Maintenance Terminal window, expand the Trace Management node, expand the Interface Trace Task node, and then doubleclick MNCDT. Step 2 In the MNCDT Tracing dialog box, set Detection Type to Intra Freq, as shown in Figure 12-15. 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing describes the parameters for missed intra-frequency neighboring cell tracing. Figure 12-15 Missed intra-frequency neighboring cell tracing

Step 3 Click OK. The information about the missed intra-frequency neighboring cells is displayed. NOTE

For the descriptions of the parameters on the output interface, refer to 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing.

----End


Related References 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing 12-26


Issue 03 (2009-04-25)

RNC LMT User Guide


12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells This describes how to trace messages of missed inter-frequency neighboring cells in different bands.

Prerequisite l

The LMT is started.

l


l

The detect switch of the missed inter-frequency neighboring cell tracing is set to ON. (You can query this by running LST NCELLDETECTSWITCH.)

Procedure Step 1 In the navigation pane, click the Maintenance tab in the Local Maintenance Terminal window, expand the Trace Management node, expand the Interface Trace Task node, and then doubleclick MNCDT. Step 2 In the MNCDT Tracing dialog box, set Detection Type to Inter Freq, and then set the parameters, as shown in Figure 12-16. 12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing describes the parameters for missed inter-frequency neighboring cell tracing. Figure 12-16 Missed inter-frequency neighboring cell tracing

Step 3 Click OK. The information about the missed inter-frequency neighboring cells is displayed.

Issue 03 (2009-04-25)


12-27

RNC LMT User Guide


For the descriptions of the parameters on the output interface, refer to 12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing.

----End


Related References 12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing

12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells This describes how to trace messages of missed inter-RAT neighboring cells in different systems.

Prerequisite l

The LMT is started.

l


l

The detect switch of the missed inter-RAT neighboring cell tracing is set to ON. (You can query this by running LST NCELLDETECTSWITCH.)

Procedure Step 1 In the navigation pane, click the Maintenance tab in the Local Maintenance Terminal window, expand the Trace Management node, expand the Interface Trace Task node, and then doubleclick MNCDT. Step 2 In the MNCDT Tracing dialog box, set Detection Type to Inter RAT, and then set the parameters, as shown in Figure 12-17. 12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing describes the parameters for missed inter-RAT neighboring cell tracing. Figure 12-17 Missed inter-RAT neighboring cell tracing

12-28


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 3 Click OK. The information about the missed inter-RAT neighboring cells is displayed. NOTE

For the descriptions of the parameters on the output interface, refer to 12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing.

----End


Related References 12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing

12.11 Tracing OS Messages This describes how to trace messages between the exchange module of the BAM and internal modules of a board or between internal modules of different boards.

Prerequisite l

The LMT is started.

l


Context In addition to the messages between different modules, this task can be performed to trace messages sent by and to a module itself.

Procedure Step 1 In the navigation pane, click the Maintenance tab in the Local Maintenance Terminal window, expand the Trace Management node, expand the Interface Trace Task node, and then doubleclick OS. Step 2 In the 12.20.12 Parameter Reference for OS Tracing dialog box, set the parameters, and then click OK. The displayed message browse window shows the traced message flow. ----End


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message Issue 03 (2009-04-25)


12-29

RNC LMT User Guide



Related References 12.20.12 Parameter Reference for OS Tracing

12.12 Tracing SCCP Messages This describes how to monitor the interworking of SCCP messages respectively over the Iu and Iur interfaces, including the connection-oriented messages and the connectionless messages. You can perform this task to locate the link setup failure or link release abnormality on the Iu and Iur interfaces.

Prerequisite l


l


Context NOTE

For each subsystem, a maximum of six SCCP tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > Interface Trace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-18.

12-30


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-18 Setting the parameters for Iu interface tracing

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select SCCP in the Trace Type area. The displayed message browse window shows the message flow of the interface. ----End


Issue 03 (2009-04-25)


12-31


RNC LMT User Guide

Figure 12-19 Output of SCCP tracing

NOTE

l

The above SCCP tracing is performed on the Iu interface.

l

The SCCP tracing on the Iur interface is similar to that on the Iu interface.



12.13 Tracing MTP3 Messages This describes how to trace the MTP3 messages, including the MTP3 upper layer (QAAL2 and SCCP) messages, MTP3 signaling link test messages, and MTP3 signaling network management messages.

Prerequisite l

12-32

The LMT is running normally. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide



Context You can perform the MTP3 tracing task to locate the problem that an MTP3B link is unavailable when the corresponding SAAL link is available. The method is to check the consistency of the Originating signaling Point Code (OPC), Destination signaling Point Code (DPC), and Signaling Link Selection code (SLS) in the sent and received SLTM (Signaling Link Test Message) messages with the negotiated data. NOTE

For each subsystem, a maximum of six MTP3 tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-20. Figure 12-20 Setting the parameters for Iu interface tracing

Issue 03 (2009-04-25)


12-33


RNC LMT User Guide

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select MTP3 in the Trace Type area. Step 3 Click the MTP3 tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. ----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-21. Figure 12-21 Output of MTP3 tracing

NOTE

l

The above MTP3 tracing is performed on the Iu interface.

l

The MTP3 tracing on the Iur interface is similar to that on the Iu interface.


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12-34


Issue 03 (2009-04-25)

RNC LMT User Guide



12.14 Tracing QAAL2 Messages This describes how to monitor the interworking of QAAL2 messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to locate the setup failure or release abnormality of an ATM Adaptation Layer type 2 (AAL2) connection on the user plane respectively on the Iu, Iur, and Iub interfaces.

Prerequisite l


l


Context The QAAL2 tracing task helps you to determine whether the near end or the peer end is faulty as follows: l

If the RNC does not send an ESTABLISH_REQUEST message, you can infer that the bandwidth of the near end (RNC) is not enough or the ATM address is not correctly configured.

l

If the RNC sends the ESTABLISH_REQUEST message and receives the RELEASE_CONFIRM message, you can infer that the peer end does not work properly. NOTE

For each subsystem, a maximum of six QAAL2 tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > Interface Trace Task, and then double-click Iu. Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select QAAL2 in the Trace Type area. Step 3 Click the QAAL2 tab, select the QAAL2 trace type, and set the required parameters if any. Click OK. The displayed message browse window shows the related message flow. NOTE

l

The above QAAL2 tracing is performed on the Iu interface.

l

The QAAL2 tracing on the Iur and Iub interfaces is similar to that on the Iu interface.

----End

Related Concepts 12.1.3 Authority of RNC Message Tracing Management Issue 03 (2009-04-25)


12-35

RNC LMT User Guide



12.15 Tracing SAAL Messages This describes how to monitor the interworking of SAAL messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to locate the problem of non-availability of SAAL link on the Iu, Iur, and Iub interfaces.

Prerequisite l


l


Context NOTE

For each subsystem, a maximum of six SAAL tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > Interface Trace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-22.

12-36


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-22 Setting the parameters for Iu interface tracing

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select SAAL in the Trace Type area. Step 3 Click the SAAL tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. NOTE

l

You can query the link No. and more information about the SAAL link by running the command LST SAALLNK.

l

If there are only outgoing but no incoming RNC messages, you can infer that the PVC is disconnected or the peer end is not working normally.

----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-23. Issue 03 (2009-04-25)


12-37


RNC LMT User Guide

Figure 12-23 Output of SAAL tracing

NOTE

l

The above SAAL tracing is performed on the Iu interface.

l

The SAAL tracing on the Iur and Iub interfaces is similar to that on the Iu interface.



12.16 Tracing SCTP Messages This describes how to trace the SCTP messages respectively over the Iu, Iur, and Iub interfaces. You can perform this task to trace the interworking of SCTP messages and to locate the problem of non-availability of SCTP link on the Iu, Iur, and Iub interfaces.

Prerequisite l

12-38

The LMT is running normally. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide



Context The NCP, CCP, or M3UA uses the SCTP link for IP transmission. If the NCP, CCP, or M3UA is not functional, you can start the SCTP tracing task to query the information on the SCTP link concerned. The SCTP link receives and transmits data frequently. Therefore, starting this tracing task may affect the performance of the system. You are not advised to start multiple SCTP tracing tasks simultaneously. NOTE

For each subsystem, a maximum of six SCTP tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > Interface Trace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-24. Figure 12-24 Setting the parameters for Iu interface tracing

Issue 03 (2009-04-25)


12-39


RNC LMT User Guide

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select SCTP in the Trace Type area. Step 3 Click the SCTP tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. NOTE

You can query the link No. and more information about the SCTP link by running the command LST SCTPLNK.

----End

Postrequisite The message browse window displays the details of a tracing message, including the task number, task time, RFN, subrack number, slot number, subsystem number, message direction, message type, message source, user ID, and message content, as shown in Figure 12-25. Figure 12-25 Output of SCTP tracing

NOTE

l

The above SCTP tracing is performed on the Iu interface.

l

The SCTP tracing on the Iur and Iub interfaces is similar to that on the Iu interface.


Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12-40


Issue 03 (2009-04-25)

RNC LMT User Guide


12.19.2 Querying the Properties of the Tracing Task 12.19.3 Viewing a Message Translation 12.19.4 Saving an RNC Traced Message 12.19.5 Pausing an RNC Tracing Task 12.19.6 Resuming an RNC Tracing Task 12.19.7 Closing an RNC Tracing Task

12.17 Tracing M3UA Messages This describes how to trace the M3UA Messages over the Iu and Iur interfaces. You can perform this task to locate the problem that the M3UA link is unavailable while the corresponding IP link is available.

Prerequisite l


l


Context The M3UA tracing is performed to locate the problem that an M3UA link is unavailable when the corresponding IP link is available. The method is to check the consistency of the OPC, DPC, and SLS in the sent and received SLTM messages with the negotiated data. NOTE

For each subsystem, a maximum of six M3UA tracing tasks can be performed simultaneously.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > Interface Trace Task, and then double-click Iu. Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parameters in the Basic tab page. Select M3UA in the Trace Type area. Step 3 Click the M3UA tab, and set the parameters accordingly. Click OK. The displayed message browse window shows the related message flow. NOTE

l

You must configure the SCTP link before configuring the M3UA link to be traced.

l

You can query the linkset index, link No., and more information about the M3UA link by running the command LST M3LNK.

l

The above M3UA tracing is performed on the Iu interface.

l

The M3UA tracing on the Iur interface is similar to that on the Iu interface.

----End

Related Concepts 12.1.3 Authority of RNC Message Tracing Management Issue 03 (2009-04-25)


12-41

RNC LMT User Guide



12.18 Tracing Location Messages This describes how to trace the results of a location tracing initiated by the CN. This task can also simulate the CN to initiate a location tracing and trace the results.

Prerequisite l

The LMT is started.

l


Context Based on different settings, this task can simulate location tracing for different situations.

Procedure Step 1 Click the Maintenance tab in the Local Maintenance Terminal window, expand the Trace Management node, expand the Location Trace node, and then double-click Location Reporting Control. Step 2 In the 12.20.13 Paramter Reference for Location Reporting Control dialog box, set the parameters, and then click OK. The displayed message browse window shows the location monitoring information and location delay information. ----End

Postrequisite After the location request is successfully sent, the Location Monitor Info tab page displays the returned location messages. The Location TimeDelay Info tab page displays the delay from the location tracing initiation to location messages acquisition. NOTE

12-42

l

Right-click on the Location Monitor Info tab page, and then choose Save as Excel to save the location results in an Excel file.

l

The Location TimeDelay Info tab page reflects the variation of the location delay in list and in chart.

l

Right-click in the chart on the Location TimeDelay Info tab page, and then choose Set Y axis display range to adjust the display range of the Y-coordinate.


Issue 03 (2009-04-25)

RNC LMT User Guide




Related References 12.20.13 Paramter Reference for Location Reporting Control

12.19 Basic Operations of RNC Message Tracing This describes how to perform the following operations of RNC message tracing: browsing an RNC traced message online, querying the properties of a tracing task, viewing the translation of a traced message, saving an RNC traced message, pausing an RNC tracing task, resuming an RNC tracing task, stopping an RNC tracing task, and browsing an RNC traced message offline. 12.19.1 Browsing an RNC Traced Message Online This describes how to browse the traced messages online in the message browse window after the tracing task is created. 12.19.2 Querying the Properties of the Tracing Task This describes how to query the properties of the tracing task in the message browse window. 12.19.3 Viewing a Message Translation This describes how to view the translation of a traced message. 12.19.4 Saving an RNC Traced Message This describes how to save an RNC traced message file to the local computer. 12.19.5 Pausing an RNC Tracing Task This describes how to pause an RNC tracing task when the tracing task is not needed for a while. 12.19.6 Resuming an RNC Tracing Task This describes how to resume an RNC tracing task when you want to start the tracing task again. 12.19.7 Closing an RNC Tracing Task This describes how to close a tracing task to release the system resource when the task is not needed. 12.19.8 Browsing an RNC Traced Message Offline This describes how to use the Trace Viewer to browse offline the traced messages that are saved in .tmf format. 12.19.9 Managing All Tracing Tasks Issue 03 (2009-04-25)


12-43

RNC LMT User Guide


This describes how to manage all the tracing tasks after the multiple tasks are created. The management of all the tracing tasks involves stopping all tasks, restarting all tasks, saving all window messages, clearing all window messages, and closing all tasks.

12.19.1 Browsing an RNC Traced Message Online This describes how to browse the traced messages online in the message browse window after the tracing task is created.

Prerequisite l

A tracing task is successfully created.

l

Traced messages are reported.

Procedure Step 1 Browse or query the traced messages in the message browse window in real time. You can rightclick in the message browse window and then choose an item from the shortcut menu to perform the associated operation as described in Table 12-1. Table 12-1 Operations for browsing an RNC traced message online Shortcut

Description

Stop Trace Task

Pause the task.

Restart Trace Task

Resume the task.

Auto Scroll

The messages in the window are automatically refreshed in real time and are scrolled upward.

Clear Messages

Remove all messages from the window.

Close All xxx Message Trace Tasks

Close the tracing tasks. xxx stands for the types of tracing tasks.

Property

Query the task properties.

Step 2 To view the details of a message, double-click it. The Message Browser dialog box is displayed, showing the details of the message, as shown in Figure 12-26.

12-44


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-26 Message Browser window

NOTE

For the location tracing, expand the Trace Management node, and then the Location Trace node. Select Location Reporting Control.

----End

Related Tasks 12.19.8 Browsing an RNC Traced Message Offline

12.19.2 Querying the Properties of the Tracing Task This describes how to query the properties of the tracing task in the message browse window.

Prerequisite l


l


Procedure Step 1 Right-click a tracing task in the message browse window, and then choose Property from the shortcut menu. Step 2 The Trace Property dialog box is displayed, showing the properties of the tracing task. Issue 03 (2009-04-25)


12-45

RNC LMT User Guide


Step 3 Click OK. ----End

12.19.3 Viewing a Message Translation This describes how to view the translation of a traced message.

Prerequisite l


l


Procedure Step 1 In the message browse window, select and double-click the traced message. Step 2 The Message Browser window is displayed. The dialog box displays the details and meaning of the message in protocol translation format. Step 3 Click

on the top right of the window.

----End

12.19.4 Saving an RNC Traced Message This describes how to save an RNC traced message file to the local computer.

Prerequisite l

A tracing task is started.

l


Context The name length (including the extension) of the file storing the tracing results cannot exceed 100 characters. There are two ways of saving tracing results: auto saving and manual saving.

Procedure l

Automatically Saving the Traced Messages When a tracing task is created, the default setting is used to save all messages displayed in the message browse window in .tmf format. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace.

12-46


Issue 03 (2009-04-25)

RNC LMT User Guide


l

l

The LMT saves every 5,000 messages in a file. From the 5001st message, every 5,000 messages are saved in the file whose name has a serial number. For example, the default save name of the 5001st to 10000th MTP3 messages is office name_MTP3_YYYY-MM-DD-HH-MMSS_1.tmf.

l

You can use the Trace Viewer to browse the offline messages saved in .tmf format. For details, see 12.19.8 Browsing an RNC Traced Message Offline.

Manually Saving the Traced Messages When the tracing task is running, you can manually save all or part of the messages in the message browse window in .tmf, .txt, or .csv format. 1.

Right-click in the message browse window and choose Save All Messages from the shortcut menu; or press and hold down Ctrl or Shift, and then choose the messages to be saved in the message browse window. Then right-click them and choose Save Selected Messages from the shortcut menu. The Save dialog box is displayed, as shown in Figure 12-27.

Figure 12-27 Save dialog box

2.

Enter a file name, and specify the file type and save path. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name is office name_tracing type_YYYY-MM-DD-HH-MM-SS.tmf.

3.

Click Save to save the file in the specified path.

----End Issue 03 (2009-04-25)


12-47


RNC LMT User Guide

Related Tasks 12.19.8 Browsing an RNC Traced Message Offline

12.19.5 Pausing an RNC Tracing Task This describes how to pause an RNC tracing task when the tracing task is not needed for a while.

Prerequisite A tracing task is created.

Procedure Right-click in the message browse window, and then choose Stop Trace Task from the shortcut menu to pause the tracing task, as shown in Figure 12-28. Figure 12-28 Pausing a tracing task

----End

Related Tasks 12.19.6 Resuming an RNC Tracing Task

12.19.6 Resuming an RNC Tracing Task This describes how to resume an RNC tracing task when you want to start the tracing task again.

Prerequisite A tracing task is paused.

Procedure Right-click in the message browse window, and choose Restart Trace Task from the shortcut menu to resume the tracing task, as shown in Figure 12-29.

12-48


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 12-29 Resuming a tracing task

----End

Related Tasks 12.19.5 Pausing an RNC Tracing Task

12.19.7 Closing an RNC Tracing Task This describes how to close a tracing task to release the system resource when the task is not needed.

Prerequisite An RNC tracing task is running.

Context You can select either of the following operations to close the task:

Procedure l

Click

l

Right-click in the message browse window, and then choose Close All xxx Message Trace Tasks (xxx stands for specific tracing tasks, for example, Close All MTP3 Message Trace Tasks) from the shortcut menu, as shown in Figure 12-30.

in the top right corner of the message browse window.

Figure 12-30 Clonging a tracing task

Issue 03 (2009-04-25)


12-49

RNC LMT User Guide


----End

12.19.8 Browsing an RNC Traced Message Offline This describes how to use the Trace Viewer to browse offline the traced messages that are saved in .tmf format.

Prerequisite The traced messages are saved in .tmf format.

Context You can find the .txt or .csv files in the save directory. You can double-click them to read the traced messages.

Procedure Step 1 Select either of the following ways to start the Trace Viewer: on the toolbar in the Local Maintenance Terminal window.

l

Click

l

Choose Start > All Programs > Huawei Local Maintenance Terminal > Trace Viewer.

The Open dialog box is displayed, as shown in Figure 12-31. Figure 12-31 Opening a file containing traced messages

12-50


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 Select the file that saves the traced messages. The default save path for the files is LMT installation directory\client\output\RNC\LMT software version number\trace. Step 3 Click Open or double-click the file. The Trace Viewer window displays traced messages in the file, as shown in Figure 12-32. Figure 12-32 Displaying traced messages

NOTE

The time format is YYYY-MM-DD HH:MM:SS (Tick). The unit of Tick is 10 ms.

Step 4 Browse these messages, or double-click one to view its details, as shown in Figure 12-33.

Issue 03 (2009-04-25)


12-51

RNC LMT User Guide


Figure 12-33 Message Browser window

Step 5 To browse other saved messages, choose File > Open. In the Open dialog box, select and open files to read the traced messages that are saved in the files. Step 6 In the Trace Viewer window, you can perform the operations listed in the following table. If...

Then...

You choose Save All Messages from the shortcut menu,

All the messages are saved in the window in .tmf or .txt format.

You choose Save Selected Messages from the shortcut menu,

The selected messages are saved in .tmf or .txt format.

You choose Filter from the shortcut menu, Set the filter to selectively display the information. You choose Filter By Column from the shortcut menu,

Filter the information by column to selectively display the information.

You choose Find from the shortcut menu, Locate the message that you want. You choose Properties from the shortcut menu,

12-52

View the properties of the task that the tracing result corresponds to.


Issue 03 (2009-04-25)

RNC LMT User Guide


If...

Then...

You click any column name,

The messages in the window are sequenced by No., time, subrack No., direction, DPC, or content.

----End

Related Tasks 12.19.1 Browsing an RNC Traced Message Online 12.19.4 Saving an RNC Traced Message

12.19.9 Managing All Tracing Tasks This describes how to manage all the tracing tasks after the multiple tasks are created. The management of all the tracing tasks involves stopping all tasks, restarting all tasks, saving all window messages, clearing all window messages, and closing all tasks.

Prerequisite l

One or more tracing tasks are created.

l


l

Stopping all tracing tasks

Procedure

l

l

l

l

1.

Choose Trace Management > Stop All Tasks. A Confirmation dialog box is displayed.

2.

Click Yes to stop all the tracing tasks.

Restarting all tracing tasks 1.

Choose Trace Management > Restart All Tasks. A Confirmation dialog box is displayed.

2.

Click Yes to restart all the tracing tasks.

Saving all window messages 1.

Choose Trace Management > Save All Window Messages. A Confirmation dialog box is displayed.

2.

Click Yes. A Select Folder dialog box is displayed. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name is office name_tracing type_YYYY-MM-DD-HH-MM-SS.tmf.

Clearing all window messages 1.

Choose Trace Management > Clear All Window Messages. A Confirmation dialog box is displayed.

2.

Click Yes to clear all the window messages.

Closing all tracing tasks 1.

Issue 03 (2009-04-25)

Choose Trace Management > Close All Tasks. A Confirmation dialog box is displayed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

12-53


2.

RNC LMT User Guide

Click Yes to close all the tracing tasks.

----End

12.20 Parameter Reference for RNC Message Tracing and Viewing This describes the parameters used for each message tracing. 12.20.1 Parameter Reference for Iu Interface Tracing This describes the parameters used for Iu interface tracing. 12.20.2 Parameter Reference for Iur Interface Tracing This describes the parameters used for Iur interface tracing. 12.20.3 Parameter Reference for Iub Interface Tracing This describes the parameters used for Iub interface tracing. 12.20.4 Parameter Reference for Uu Interface Tracing This describes the parameters used for Uu interface tracing. 12.20.5 Parameter Reference for UE Tracing This describes the parameters used for UE tracing. 12.20.6 Parameter Reference for IOS Tracing This describes the parameters used for IOS tracing. 12.20.7 Parameter Reference for Cell Tracing This describes the parameters used for cell tracing. 12.20.8 Parameter Reference for REDIRECT Tracing This describes the parameters used for REDIRECT tracing. 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing This describes the parameters on the input and output GUIs of intra-frequency MNCDT tracing. 12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing This describes the parameters on the input and output GUIs of inter-frequency MNCDT tracing. 12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing This describes the parameters on the input and output GUIs of inter-RAT MNCDT tracing. 12.20.12 Parameter Reference for OS Tracing This describes the parameters used for OS tracing. 12.20.13 Paramter Reference for Location Reporting Control This describes the parameters used for location reporting control.

12.20.1 Parameter Reference for Iu Interface Tracing This describes the parameters used for Iu interface tracing.

12-54


Issue 03 (2009-04-25)

RNC LMT User Guide


Item

Field

Description

Basic

Active SPU subsystem (Subrack No.Slot No.Subsystem No.)

In this area, you can select the SPU subsystem whose message flow to be traced.

DPC Configuration

In this area, you can select either All DPC or specified DPC as the DPC trace type. If you select Specified DPC, Destination Point Code is required.

Trace Type

You can select one or multiple tracing types, including Iu, SCCP, MTP3, QAAL2, SAAL, SCTP, and M3UA. If you select SCCP, you need only set the parameters on the Basic tab page.

Iu

MTP3

Autosave to File

In this area, you can set whether to automatically save the trace results.

File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number \trace. The default file name is office name_Iu_YYYY-MMDD-HH-MM-SS.tmf.

Iu Message Type

In this area, you can select the type of Iu messages to be traced.

MTP3 Message Type

In this area, you can select the type of MTP3 messages to be traced.

If you select Iu in the Trace Type area on the Basic tab page, the parameters on the Iu tab page are required.

If you select MTP3 in the Trace Type area on the Basic tab page, the parameters on the MTP3 tab page are required. QAAL2

Trace Configuration

In this area, you can select the QAAL2 trace type and set the required parameters if any. If you select QAAL2 in the Trace Type area on the Basic tab page, the parameters on the QAAL2 tab page are required.

SAAL

Parameter Configuration

In this area, you can specify the number of the SAAL to be traced. The value range of the SAAL link No. is 0 to 699. If you select SAAL in the Trace Type area on the Basic tab page, the parameters on the SCTP tab page are required.

SCTP

SAAL Message Type

In this area, you can select the type of SAAL messages to be traced.


In this area, you can specify the number of the SCTP link to be traced. The value range of the SCTP link No. is 0 to 599. If you select SCTP in the Trace Type area on the Basic tab page, the parameters on the SCTP tab page are required.

Issue 03 (2009-04-25)


12-55

RNC LMT User Guide


Item

M3UA

Field

Description

SCTP Message Type

In this area, you can select the type of SCTP messages to be traced.


In this area, you can select the M3UA trace type. If you trace the M3UA messages of a link set, you must set the linkset No. (value range: 0 to 150). If you trace the M3UA messages of a specified link, you must further set the link No. (value range: 0 to 15). If you select M3UA in the Trace Type area on the Basic tab page, the parameters on the M3UA tab page are required.

M3UA Message Type

In this area, you can select the type of M3UA messages to be traced.

Related Tasks 12.2 Tracing Iu Interface Messages

12.20.2 Parameter Reference for Iur Interface Tracing This describes the parameters used for Iur interface tracing. Item

Field

Description

Basic



DPC Configuration

You can select Trace All DPCs or Trace Specified DPC to perform tracing. When Trace Specified DPC is selected, Destination Point Code is required.

Trace Type

You can select one or multiple tracing types, including Iur, SCCP, MTP3, QAAL2, SAAL, SCTP, and M3UA. If you select SCCP, you need only set the parameters on the Basic tab page.

Iur

12-56

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number \trace. The default file name is office name_Iur_YYYYMM-DD-HH-MM-SS.tmf.

Iur Message Type

In this area, you can select the type of Iur messages to be traced. If you select Iur in the Trace Type area on the Basic tab page, the parameters on the Iur tab page are required.


Issue 03 (2009-04-25)

RNC LMT User Guide


Item

Field

Description

MTP3

MTP3 Message Type

In this area, you can select the type of MTP3 messages to be traced. If you select MTP3 in the Trace Type area on the Basic tab page, the parameters on the MTP3 tab page are required.

QAAL2

Trace Configuration


SAAL



SCTP

SAAL Message Type


Trace DPC configuration


M3UA

SCTP Message Type



In this area, you can select the M3UA trace type. If you trace the M3UA messages of a link set, you must set the linkset No. (value range: 0 to 150). If you trace the M3UA messages of a specified link, you must further set the link No. (value range: 0 to 15). If you select M3UA in the Trace Type area on the Basic tab page, the parameters on the M3UA tab page are required.

M3UA Message Type

In this area, you can select the type of M3UA messages to be traced.

Related Tasks 12.3 Tracing Iur Interface Messages

12.20.3 Parameter Reference for Iub Interface Tracing This describes the parameters used for Iub interface tracing.

Issue 03 (2009-04-25)


12-57

RNC LMT User Guide


Item

Iub

Field

Description



Trace Type

You can select one or multiple tracing types, including Iub, SAAL, and SCTP.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name is office name_Iub_YYYY-MM-DD-HH-MM-SS.tmf.


In this area, you can select the Iub trace type and set the required parameters if any. If you select Iub in the Trace Type area on the Basic tab page, the parameters on the Iub tab page are required.

SAAL

Iub Message Type

In this area, you can select the type of Iub messages to be traced.



SCTP

SAAL Message Type




QAAL2

SCTP Message Type


Trace Configuration


Related Tasks 12.4 Tracing Iub Interface Messages

12-58


Issue 03 (2009-04-25)

RNC LMT User Guide


12.20.4 Parameter Reference for Uu Interface Tracing This describes the parameters used for Uu interface tracing. Parameter

Description

Cell Configuration

In this area, you can specify the RNC ID and cell ID.

Uu Message Type

In this area, you can select the messages to be traced on the Uu interface.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name is office name_Uu_YYYY-MM-DD-HH-MM-SS.tmf.

Related Tasks 12.5 Tracing Uu Interface Messages

12.20.5 Parameter Reference for UE Tracing This describes the parameters used for UE tracing. Field UE

Description IMSI IMEI TMSI P-TMSI

Iur

Issue 03 (2009-04-25)

These are used to identify the UE. You can choose to trace the UE by the IMSI, IMEI, TMSI, or P-TMSI. l If you trace a UE by the TMSI, the Location Area Code (LAC), Mobile Country Code (MCC), and Mobile Network Code (MNC) are required. l If you trace a UE by the P-TMSI, the LAC, Routing Area Code (RAC), MCC, and MNC are required.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name is office name_UE_YYYY-MM-DD-HHMM-SS.tmf.

Iur Message Type

You can select the types of the Iur messages to be traced on this tab page. You may select all types or select some of them.


12-59

RNC LMT User Guide


Field

Description

Iub

Iub Message Type

You can select the types of the Iub messages to be traced on this tab page. You may select all types or select some of them.

Iu

Iu Message Type

You can select the types of the Iu messages to be traced on this tab page. You may select all types or select some of them.

Uu

Uu Message Type

You can select the types of the Uu messages to be traced on this tab page. You may select all types or select some of them.

Monitor

Monitor Config

This is used to select the UE connection performance for monitoring. You can monitor the UL SIR, transmit power, DL block error rate (BLER), DL code transmit power, PCPICH Ec/No and RSCP, AMR mode, received total wideband power (RTWP), and transmit carrier power of a UE identified by the P-TMSI, TMSI, or IMEI.

Related Tasks 12.6 Tracing UE Messages

12.20.6 Parameter Reference for IOS Tracing This describes the parameters used for IOS tracing. Parameter

Description

Basic

Calls count

To set the maximum number of the calls to be traced at the same time after the tracing task is started. Value range: 1 to 30.

Cell ID

You can specify one or more cells to be traced.

Event

To select the events to be traced. These events classify the messages related to the calls. NOTE You can choose to Select All, Select None, or Select Default as required.

RAB

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client \output\RNC\LMT software version number\trace. The default file name is office name_IOS_YYYY-MM-DD-HH-MM-SS.tmf. This is used to set the RAB parameters for IOS tracing, for example, Period of trace time(10s) and those in the Traffic type area. NOTE Period of trace time(10s) is 0 by default, that is, the trace time is not limited.

12-60


Issue 03 (2009-04-25)

RNC LMT User Guide


Parameter

Description

RRC

This is used to set the RRC parameters for IOS tracing, for example, the parameters in the strMeasurePeriods area and in the Traffic type area.

Related Tasks 12.7 Tracing IOS Messages

12.20.7 Parameter Reference for Cell Tracing This describes the parameters used for cell tracing. Field CELL

Description Cell ID

This is used to specify the cell ID.

USER_VO LUME

You can choose the events to be traced: USER_VOLUME or PROPAGATION_DELAY. To trace the UE statistical information including the custom messages, select USER_VOLUME (value range: 1,000 to 10,000; unit: 10 ms). To trace the propagation delays, select PROPAGATION_DELAY (value range: 1 to 80; unit: times).

PROPAGA TION_DE LAY

NOTE l When you create a CELL tracing task, USER_VOLUME is selected

and set to 1000 by default. l When you create a CELL tracing task, PROPAGATION_DELAY

is selected and set to 1 by default.

FMR

IUB

Issue 03 (2009-04-25)

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory \client\output\RNC\LMT software version number\trace. The default file name is office name_CELL_YYYY-MM-DD-HHMM-SS.tmf.

strFMRTrc Event

You can select either Perodically Data Report or CCCH Data Frame Report.

SCCPCH ID

This is used to specify the IDs of the SCCPCHs to be traced. You can choose to trace two SCCPCHs at the same time by specifying two SCCPCH IDs.

Report Period(100 ms)

If you choose Periodically Data Report, you must set the Report Period(100 ms).

Trace Type

This is used to specify the messages to be traced on the Iub interface.


12-61

RNC LMT User Guide


Related Tasks 12.8 Tracing Cell Messages

12.20.8 Parameter Reference for REDIRECT Tracing This describes the parameters used for REDIRECT tracing. Field

Description

Subrack No.

This is used to specify the number of the subrack to be redirected. Value range: 0 to 5.

Slot No.

This is used to specify the number of the slot to be redirected. Value range: 0 to 27.

Subsystem No.

This is used to specify the number of the subsystem to be redirected. Value range: 0 to 3.

CAUTION The OMUa does not support the COM port REDIRECT tracing. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 12.9 Tracing REDIRECT Messages

12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing This describes the parameters on the input and output GUIs of intra-frequency MNCDT tracing.

Parameters on the Input GUI Table 12-2 describes the parameters on the input GUI of intra-frequency MNCDT tracing. Table 12-2 Parameters on the input GUI Field

Description

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output \RNC\LMT software version number\trace. The default file name is office name_MNCDT_YYYY-MM-DD-HH-MM-SS.tmf.

Parameters on the Output GUI Table 12-3 describes the parameters on the output GUI of intra-frequency MNCDT tracing. 12-62


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 12-3 Parameters on the output GUI Field

Description

ulRnti

User ID

ucActSetNum

Number of active sets

ausActCellId

Array of the IDs of the cells in the active set. The first ID in the array corresponds to the best cell.

ucDetectCellNum

Number of missing neighboring cells

ausSrimbleCode

Scrambling code array of the missing neighboring cells

Related Tasks 12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells

12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing This describes the parameters on the input and output GUIs of inter-frequency MNCDT tracing.

Parameters on the Input GUI Table 12-4 describes the parameters on the input GUI of inter-frequency MNCDT tracing. Table 12-4 Parameters on the input GUI Field

Description

Uplink UARFCN

This is used to specify the uplink (UL) frequency of the cell to be traced.

Downlink UARFCN

This is used to specify the downlink (DL) frequency of the cell to be traced.

Start of Primary Scrambling Code

This is used to specify the minimum scrambling code for MNCDT tracing.

End of Primary Scrambling Code

This is used to specify the maximum scrambling code for MNCDT tracing. NOTE The end of the primary scrambling code is not less than the start of the primary scrambling code.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client \output\RNC\LMT software version number\trace. The default file name is office name_MNCDT_YYYY-MM-DD-HH-MM-SS.tmf.

Parameters on the Output GUI Table 12-5 describes the parameters on the output GUI of inter-frequency MNCDT tracing. Issue 03 (2009-04-25)


12-63

RNC LMT User Guide


Table 12-5 Parameters on the output GUI Field

Description

ulRnti

User ID

ucActSetNum

Number of active sets

ausActCellId

Array of the IDs of the cells in the active set. The first ID in the array corresponds to the best cell.

ucDetectCellNum

Number of missing neighboring cells

usUlUarFcn

UL frequency of the missing neighboring cell

usDlUarFcn

DL frequency of the missing neighboring cell

usPsc

Scrambling code of the detected cell

Related Tasks 12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells

12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing This describes the parameters on the input and output GUIs of inter-RAT MNCDT tracing.

Parameters on the Input GUI Table 12-6 describes the parameters on the input GUI for inter-RAT MNCDT tracing. Table 12-6 Parameters on the input GUI

12-64

Field

Description

Start of NCC

Start network color code of the cell to be traced. Value range: 0 to 7.

End of NCC

End network color code of the cell to be traced. Value range: 0 to 7. The value of the start NCC should be greater than that of the end NCC.

Start of BCC

Start BS color code of the cell to be traced. Value range: 0 to 7.

End of BCC

End BS color code of the cell to be traced. Value range: 0 to 7. The value of the start BCC should be greater than that of the end BCC.

Band Indicator

Band in which the ARFCN is used (DCS 1800 or PCS 1900)

Start of BCCH ARFCN

Minimum ARFCN for MNCDT tracing

End of BCCH ARFCN

Maximum ARFCN for MNCDT tracing


Issue 03 (2009-04-25)

RNC LMT User Guide


Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output\RNC \LMT software version number\trace. The default file name is office name_MNCDT_YYYY-MM-DD-HH-MM-SS.tmf.

Parameters on the Output GUI Table 12-7 describes the parameters on the output GUI for inter-RAT MNCDT tracing. Table 12-7 Parameters on the output GUI Field

Description

ucNcc

Network color code of the missing inter-RAT neighboring cell

ucBcc

Base station color code of the missing inter-RAT neighboring cell

ucInterRatBandInd

Band indicator of the missing inter-RAT neighboring cell

usInterRatArfcn

ARFCN of the missing inter-RAT neighboring cell

Related Tasks 12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells

12.20.12 Parameter Reference for OS Tracing This describes the parameters used for OS tracing. Field

Description

Trace Type

You can specify whether to trace the OS messages by the sender or by the receiver.

Sender Parameter

Issue 03 (2009-04-25)

IP Type

l

If you select Trace OS Sender, you can select only a specified IP for the IP type in the Sender Parameter area.

l

If you select Trace OS Receiver, you can select only a specified IP for the IP type in the Receiver Parameter area.

This is used to specify the IP type of the sender. You can select one from the following types: l

All. The receiver traces the messages sent from all the IPs.

l

Bam. The receiver traces only the messages sent from the BAM.

l

Specified IP. The receiver traces only the messages sent from the specified IP.


12-65

RNC LMT User Guide


Field

Receiver Parameter

Description Module Name

This is used to specify the module name of the sender.

IP Type

This is used to specify the IP type of the receiver. You can select one from the following types:

Module Name

l

All. The sender traces the messages sent to all the IPs.

l

Bam. The sender traces only the messages sent to the BAM.

l

Specified IP. The sender traces only the messages sent to the specified IP.

This is used to specify the module name of the receiver.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory \client\output\RNC\LMT software version number\trace. The default file name is office name_OS_YYYY-MM-DD-HHMM-SS.tmf.

Related Tasks 12.11 Tracing OS Messages

12.20.13 Paramter Reference for Location Reporting Control This describes the parameters used for location reporting control.

12-66

Field

Description

IMSI

This is used to specify the IMSI of the UE to be located.

LocRprtingCtrl

If this check box is selected, you can initiate a simulated CN location tracing by setting the following parameters: event type, report area type, horizontal accuracy code, positioning interval, vertical accuracy code, response time type, positioning priority, and client type.

Event

This is used to specify the type of the event to be located.

Report Area

This is used to specify the type of the area to be located.

Horizontal Accuracy Code (m)

This is used to specify the required horizontal accuracy of the reported results. Its value range is: 0 to 1,800,000.

Positioning Interval(10s)

This is used to specify the time interval between two location requests. Its value range is: 0 to 1,440 (unit: 10s).


Issue 03 (2009-04-25)

RNC LMT User Guide


Field

Description

Vertical Accuracy Code (m)

This is used to specify the required vertical accuracy of the reported results. Its value range is: 0 to 990.

Response Time

This is used to specify the type of the response time of the location protection timer.

Positioning Priority

This is used to specify the priority of the UE to be located.

Client Type

This is used to specify the type of the client to be located.

Autosave to File


File name

In this field, you can specify the file name and save path for the trace results. The default save path is LMT installation directory\client\output \RNC\LMT software version number\trace. The default file name is office name_Location_Reporting_Control_YYYY-MM-DD-HHMM-SS.tmf.

Related Tasks 12.18 Tracing Location Messages

Issue 03 (2009-04-25)


12-67

RNC LMT User Guide

13 RNC Real-Time Performance Monitoring

13

RNC Real-Time Performance Monitoring

About This Chapter This describes how to monitor RNC performance in real time. 13.1 Concepts of RNC Real-Time Performance Monitoring This describes the following concepts of RNC real-time performance monitoring: the functions, working principles, and operation authority of RNC real-time performance monitoring. 13.2 Monitoring the RNC CPU/DSP Occupancy This describes how to monitor the RNC CPU/DSP usage. By performing this task, you can learn about the usage of the CPU/DSP resources. 13.3 Monitoring the RNC Connection Performance This describes how to monitor the connection state of the physical links during a conversation of a UE. For the same monitoring item, the LMT can perform a maximum of six monitoring tasks simultaneously. 13.4 Monitoring the RNC Cell Performance This describes how to monitor the cell performance, such as the common measured value and number of common channel users. For the same monitoring item, you can start at most six tasks simultaneously. 13.5 Monitoring the RNC Link Performance This describes how to monitor the RNC link performance. This task applies to the traffic statistics based on IP path/SCTP/OAM stream, statistics based on priority queues. The statistics based on priority queues include the statistics of packet loss rate, number of the sent packets, and number of the sent bytes. For the same monitoring item, you can start up to six tasks. 13.6 Monitoring the RNC Board Resource This describes how to monitor licensed traffic volume for voice services and the PS domain data throughput on the user plane of a specified board in real time. 13.7 Basic RNC Real-Time Performance Monitoring Operations This describes how to perform basic operations after an RNC real-time performance monitoring task is started. 13.8 Parameter Reference for RNC Real-Time Performance Monitoring Issue 03 (2009-04-25)


13-1


RNC LMT User Guide

This describes the parameters used for each performance monitoring.

13-2


Issue 03 (2009-04-25)

RNC LMT User Guide


13.1 Concepts of RNC Real-Time Performance Monitoring This describes the following concepts of RNC real-time performance monitoring: the functions, working principles, and operation authority of RNC real-time performance monitoring. 13.1.1 Introduction to RNC Real-Time Performance Monitoring The RNC real-time performance monitoring function provides the display of CPU/DSP usage monitoring, connection/cell/link performance monitoring, and board resource monitoring in charts and lists to monitor the status of the current system devices and services. During the monitoring, the abnormalities are analyzed to maintain the devices and clear faults. 13.1.2 Working Principles of RNC Real-Time Performance Monitoring The working principle of CPU/DSP usage monitoring is different from that of the other types of real-time monitoring. 13.1.3 Authority of the RNC Real-Time Performance Monitoring You can perform the real-time performance monitoring operations only when you are authorized for these operations.

13.1.1 Introduction to RNC Real-Time Performance Monitoring The RNC real-time performance monitoring function provides the display of CPU/DSP usage monitoring, connection/cell/link performance monitoring, and board resource monitoring in charts and lists to monitor the status of the current system devices and services. During the monitoring, the abnormalities are analyzed to maintain the devices and clear faults. The RNC monitors the following items in real time: l CPU/DSP usage l

Connection performance

l

Cell performance

l

Link performance

l

Board resource

13.1.2 Working Principles of RNC Real-Time Performance Monitoring The working principle of CPU/DSP usage monitoring is different from that of the other types of real-time monitoring.

Working Principle of CPU/DSP Usage Monitoring Figure 13-1 shows the working principle of CPU/DSP usage monitoring. Figure 13-1 CPU/DSP usage monitoring

Issue 03 (2009-04-25)


13-3

RNC LMT User Guide


The internal process of CPU usage monitoring is as follows: 1.

The operator creates a task of CPU/DSP usage monitoring on the LMT, and the LMT sends a binary command querying CPU/DSP usage to the maintenance module of the BAM every five seconds.

2.

The BAM sends the corresponding command to the maintenance and configuration module of the specified board.

3.

The board collects data according to the commands, and reports it to the BAM.

4.

The BAM sends the data to the LMT.

Working Principle of Connection/Cell/Link Performance Monitoring The working principle of connection/cell/link performance monitoring is almost the same. See Figure 13-2. Figure 13-2 Working principle of connection/cell/link performance monitoring

The internal process for creating connection/cell/link performance monitoring tasks is as follows: 1.

The operator creates a monitoring task on the LMT. Then, the LMT sends a binary command to the BAM to create the task.

2.

The BAM assigns a number to the task and sends the command to the debugging module of the specified board.

3.

After receiving the command, the commissioning module records the filter parameters in the filter table and notifies the service module.

4.

The service module updates the local filter table according to the messages from the commissioning module.

The internal process for closing the three monitoring tasks is as follows: 1.

The operator closes a monitoring task on the LMT. Then, the LMT sends a binary command to the BAM to delete the task.

2.

The BAM sends the command to the specified board according to the task number.

3.

The commissioning module and service module delete the task from the filter table.

The internal process for reporting monitoring data is as follows: 13-4


Issue 03 (2009-04-25)

RNC LMT User Guide


1.

The service module filters the collected data according to the filter parameters in the local filter table, and reports the messages meeting the requirements to the BAM.

2.

The BAM forwards the data to the LMT that creates the task according to the task number.

3.

The LMT displays the data in a chart or a list on the interface.

13.1.3 Authority of the RNC Real-Time Performance Monitoring You can perform the real-time performance monitoring operations only when you are authorized for these operations. Operators of the following levels can perform the real-time performance monitoring tasks: admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command group G_10. That is, except GUEST-level and CUSTOM not entitled to use command group G_10, all the other operators have the authority to perform the real-time performance monitoring tasks. NOTE

Group G_10 contains commands for tracing and query. It is a binary command group, which contains no MML commands.

Related Tasks 13.2 Monitoring the RNC CPU/DSP Occupancy 13.3 Monitoring the RNC Connection Performance 13.4 Monitoring the RNC Cell Performance 13.5 Monitoring the RNC Link Performance 13.6 Monitoring the RNC Board Resource

13.2 Monitoring the RNC CPU/DSP Occupancy This describes how to monitor the RNC CPU/DSP usage. By performing this task, you can learn about the usage of the CPU/DSP resources.

Prerequisite l

The LMT is started.

l

You have logged in to the RNC with an account authorized for the real-time performance monitoring.

l

The monitored board works properly.

Context NOTE

The LMT can open only one window for CPU/DSP usage monitoring. If the window is open, you can add monitoring tasks for more boards in this CPU/DSP Usage window. The LMT can perform a maximum of 10 monitoring tasks simultaneously.

In the Local Maintenance Terminal window, check the Window menu to see whether the CPU/DSP Usage window is open or not. If yes, add CPU usage monitoring tasks or delete CPU usage monitoring tasks. If no, starting CPU usage monitoring tasks. Issue 03 (2009-04-25)


13-5


RNC LMT User Guide

Procedure l

Starting CPU/DSP usage monitoring tasks 1.

In the navigation pane, click the Maintenance tab.

2.

Expand the Common Monitoring node, and then double-click CPU/DSP Usage. The 13.8.1 Parameter Reference for RNC CPU Usage Monitoring dialog box is displayed, as shown in Figure 13-3.

Figure 13-3 Add Tasks dialog box

3.

13-6

Set the monitoring parameters in the dialog box, and then click Add. The CPU/DSP Usage window is displayed, showing real-time monitoring results in either list (as shown in Figure 13-4) or chart (as shown in Figure 13-5). You can repeat this step to create monitoring tasks for more boards.


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-4 CPU/DSP Usage monitoring window in a list

Figure 13-5 CPU/DSP Usage monitoring window in a chart

Issue 03 (2009-04-25)


13-7


RNC LMT User Guide

NOTE

In the chart, the X-coordinate represents the time and the Y-coordinate represents the CPU/ DSP usage (%). The range of normal CPU/DSP usage is 0-75%.

4. l

Click Close to close the Add Task dialog box.

Querying properties of CPU/DSP usage monitoring tasks 1.

In the task information pane at the bottom of the CPU/DSP Usage window, select the monitoring task to be queried.

2.

Right-click the monitoring task to be queried in the task information pane and choose Properties from the shortcut menu, as shown in Figure 13-6. The Monitor Properties dialog box is displayed, showing the properties of the task.

Figure 13-6 Querying properties of a CPU/DSP usage monitoring task

----End

Related Concepts 13.1.3 Authority of the RNC Real-Time Performance Monitoring

Related Tasks 13.7.1 Browsing the RNC Monitoring Results Online 13.7.2 Switching the Display Mode 13.7.3 Setting the Default Display Mode 13.7.4 Editing the Display Mode for the Chart 13.7.5 Saving RNC Monitoring Results 13.7.6 Pausing and Resuming an RNC Monitoring Task 13.7.7 Adding an RNC CPU/DSP Monitoring Task 13.7.8 Deleting an RNC CPU/DSP Monitoring Task 13.7.9 Stopping an RNC Monitoring Task 13.7.10 Browsing RNC Monitoring Results Offline

13.3 Monitoring the RNC Connection Performance This describes how to monitor the connection state of the physical links during a conversation of a UE. For the same monitoring item, the LMT can perform a maximum of six monitoring tasks simultaneously. 13-8


Issue 03 (2009-04-25)

RNC LMT User Guide


13.3.1 Monitoring P-CPICH Ec/No and RSCP This describes how to monitor in real time the Primary Common Pilot Channel (P-CPICH) Ec/ No and Received Signal Code Power (RSCP) of the cells in the active set. The monitoring result, including the number of cells in the active set and the signal strength of each cell, is displayed in a chart. By performing this task, you can learn about whether the current connection is at the edge or the center of the cell. 13.3.2 Monitoring the SIR Measurement Values of UL RLSs This describes how to monitor in real time the Signal-Interference Ratio (SIR) measurement values of the UL RLSs of the current connection. By performing this task, you can analyze the quality of UL radio links and the quality variation. 13.3.3 Monitoring the Enhanced Outer Loop Power Control This describes how to monitor the enhanced outer loop power control. Monitoring the enhanced outer loop power control consists of monitoring the following items: the target UL RLS SIR, BER of the UL physical channel, BER filter values of the UL transport channel, BLER of the UL transport channel, E-DCH average times of retransmission, and E-DCH retransmission probability. 13.3.4 Monitoring the SIR Error Values of UL RLSs This describes how to monitor in real time the SIR error values of the UL radio link sets (RLSs) of the current connection. By performing this task, you can observe whether the SIR can keep up with the variation of the target values and estimate the UL inner loop power control function. If the SIR error values vary all the time but converge near 0 dB, you can infer that the UL inner loop power control converges. Otherwise, the UL inner loop power control does not converge. 13.3.5 Monitoring DL Code TX Power This describes how to monitor the variation of the DL code TX power of each radio link of the current connection in real time. By performing this task, you can analyze the DL power consumption. If the downlink code TX power increases, even approximating to the maximum value configured in the signaling message, the quality of this radio link declines. 13.3.6 Monitoring the UE TX Power This describes how to monitor in real time the variation of the UE TX power of the current connection. By performing this task, you can analyze the UL quality. If the UE TX power increases, even reaching the limit of the UE capability, the UL quality declines. 13.3.7 Monitoring UL Traffic This describes how to monitor in real time the UL traffic (that is, data buffer size on the UE side) of the current connection. By performing this task, you can analyze the transmission performance of the UL traffic. The UL traffic is measured by the UE and reported to the RNC per transport channel. 13.3.8 Monitoring DL Traffic This describes how to monitor the DL traffic (that is, data buffer size on the network side) of the current connection. By performing this task, you can analyze the transmission performance of the DL traffic. The DL traffic is measured at the RNC per transport channel. 13.3.9 Monitoring UL Throughput and Bandwidth This describes how to monitor in real time the rate variation of the UL transport access stratum and non-access stratum of the current connection. By performing this task, you can analyze the dynamic channel configuration function and service source rate variation characteristics. 13.3.10 Monitoring DL Throughput and Bandwidth

Issue 03 (2009-04-25)


13-9

RNC LMT User Guide


This describes how to monitor in real time the rate variation of the DL transport access stratum and non-access stratum of the current connection. By performing this task, you can analyze the dynamic channel configuration function and service source rate variation characteristics. 13.3.11 Monitoring Handover Delay This describes how to monitor the handover delay performance. By performing this task, you can observe and obtain the time taken by each handover of the current connection. The handover includes intra-frequency soft handover and inter-frequency handover. 13.3.12 Monitoring the BLER of the DL Transport Channel This describes how to monitor the variation of the BLER on all transport channels of the current connection. By performing this task, you can analyze the DL quality. If the BLER of the DL transport channel increases, you can infer that the DL quality declines. If the BLER decreases, you can infer that the DL quality is improved. 13.3.13 Monitoring the AMR Mode This describes how to monitor the variation of the AMR rate configured by the UE and to record the variation in real time.



13.3.1 Monitoring P-CPICH Ec/No and RSCP This describes how to monitor in real time the Primary Common Pilot Channel (P-CPICH) Ec/ No and Received Signal Code Power (RSCP) of the cells in the active set. The monitoring result, including the number of cells in the active set and the signal strength of each cell, is displayed in a chart. By performing this task, you can learn about whether the current connection is at the edge or the center of the cell.

Prerequisite

13-10

l

The LMT is started.

l



Issue 03 (2009-04-25)

RNC LMT User Guide


Context

CAUTION Before running this monitoring task, you need to perform one of the following operations: l

Run SET CORRMALGOSWITCH to set Handover algorithm switch. Ensure that SOFT_HANDOVER_SWITCH is selected.

l

Run MOD CELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE. NOTE

l

This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel.

l

This task is performed to monitor only the real-time data of the cells in the active set. The data of other cells is not reported. Therefore, the monitoring results reflect the variation of the number of cells in the active set in real time.

l

In the active set, the maximum number of the cells that can be reported is 3.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Connection performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-7. Figure 13-7 Connection performance monitoring dialog box

Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to PCPICH EcNo&RSCP, and then set Monitor period(s) and IMSI. Issue 03 (2009-04-25)


13-11

RNC LMT User Guide

13 RNC Real-Time Performance Monitoring NOTE

If Monitor period(s) is set too short, a large amount of reported data increases the overhead of signaling transport and system processing, which has influence on the CPU usage of the RNC. You are advised to set Monitor period(s) to 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_PCPICH EcNo&RSCP_YYYY-MM-DD-HH-MM-SS_IMSIIMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported P-CPICH Ec/No (unit: dB) and RSCP (unit: dBm). l

RSCP stands for Received Signal Code Power. It is the received power on one code measured on the P-CPICH. The reference point for measurement of the RSCP is at the antenna connector of the UE. If the P-CPICH uses transmit diversity, you need to measure the RSCP of each antenna and sum up all of the RSCP values. Then you can obtain the total RSCP of the P-CPICH.

l

Ec/No refers to the ratio of received energy per chip to noise spectral density. Like RSCP/ RSSI, Ec/No is also measured on the P-CPICH. The reference point for measurement is also at the antenna connector of the UE. If the P-CPICH uses transmit diversity, you need to measure the Ec of each antenna and sum up all of the Ec values. Then, you can calculate the Ec/No.

Related References 13.8.2 Parameter Reference for Connection Performance Monitoring

13.3.2 Monitoring the SIR Measurement Values of UL RLSs This describes how to monitor in real time the Signal-Interference Ratio (SIR) measurement values of the UL RLSs of the current connection. By performing this task, you can analyze the quality of UL radio links and the quality variation.

Prerequisite

13-12

l

The LMT is started.

l



Issue 03 (2009-04-25)

RNC LMT User Guide


Context NOTE

Each task can monitor only one UE. The monitoring result, including the number of cells in the active set and the signal strength of each cell, is displayed in a chart. By performing this task, you can learn about whether the current connection is at the edge or the center of the cell.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to UL SIR, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_UL SIR_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. The monitoring results reflect the variation of the number of the RLSs in real time. Issue 03 (2009-04-25)


13-13

RNC LMT User Guide


In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported SIR of the UL RLSs (unit: dB). The calculation formula of SIR is (RSCP/ISCP) x SF, where: l

RSCP stands for Received Signal Code Power. It is the received power on one code.

l

ISCP stands for Interference Signal Code Power. Only the non-orthogonal part of received interference signals is measured.

l

SF refers to the spreading factor of the DPCCH.

The measurement is performed on the DPCCH selected after radio links are combined on the NodeB. In compressed mode, do not measure the SIR in the transmission gap. The measurement values of UL SIR are reported to the RNC by the NodeB.


13.3.3 Monitoring the Enhanced Outer Loop Power Control This describes how to monitor the enhanced outer loop power control. Monitoring the enhanced outer loop power control consists of monitoring the following items: the target UL RLS SIR, BER of the UL physical channel, BER filter values of the UL transport channel, BLER of the UL transport channel, E-DCH average times of retransmission, and E-DCH retransmission probability.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Connection performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-9.

13-14


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-9 Connection performance monitoring dialog box

Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to OLPC, and then set Monitor period(s) and IMSI. NOTE

l

If Monitor period(s) is set too short, a large amount of reported data increases the overhead of signaling transport and system processing, which has influence on the CPU usage of the RNC. You are advised to set Monitor period(s) to 0.5.

l

If you set Monitor period(s) to OLPC, the measurement periods is consistent with the OLPC adjustment period.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_OLPC_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite The real-time monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). Two small charts are respectively used to describe the five monitoring items. l

The first small chart shows the output interface of the SIR target values of the UL RLSs, BLER of the UL transport channel, and BER of the UL physical channel. The left Ycoordinate represents the SIR target values of the UL RLSs (range: -10 to 18, unit: dB). The right Y-coordinate represents the BLER of the UL transport channel (range: 0 to 1, unit: BLER) and BER of the UL physical channel (range: 0 to 1, unit: BER).

l

The second small chart shows the output interface of the E-DCH average times of retransmission and E-DCH retransmission probability. The left Y-coordinate represents the

Issue 03 (2009-04-25)


13-15

RNC LMT User Guide


E-DCH average times of retransmission (range: 0 to 16, unit: none). The right Y-coordinate represents the E-DCH retransmission probability (range: 0 to 1, unit: none).


13.3.4 Monitoring the SIR Error Values of UL RLSs This describes how to monitor in real time the SIR error values of the UL radio link sets (RLSs) of the current connection. By performing this task, you can observe whether the SIR can keep up with the variation of the target values and estimate the UL inner loop power control function. If the SIR error values vary all the time but converge near 0 dB, you can infer that the UL inner loop power control converges. Otherwise, the UL inner loop power control does not converge.

Prerequisite l


l


Context This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel.


13-16


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to UL SIRerror, and then set Monitor period(s) and IMSI. NOTE

If Monitor period(s) is set too low, a large volume of reported data increases the overhead of signaling transportation and system processing, which affects the CPU usage of the RNC. You are advised to set Monitor period(s) to 0.5.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_UL SIRerror_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. The monitoring results reflect the variation of the number of the RLSs in real time. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported SIR error values (SIRerror) of the UL RLSs. l

SIRerror (unit: dB) is reported to the RNC by the NodeB. The calculation formula is SIRerror = SIR - SIRtarget_ave.

l

Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to the time for calculating the SIR in the above formula of SIRerror.

l

In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave in the transmission gap is not calculated. The average of SIRtarget is an arithmetical average. The unit of SIRtarget_ave is dB.


13.3.5 Monitoring DL Code TX Power This describes how to monitor the variation of the DL code TX power of each radio link of the current connection in real time. By performing this task, you can analyze the DL power consumption. If the downlink code TX power increases, even approximating to the maximum value configured in the signaling message, the quality of this radio link declines.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


13-17


RNC LMT User Guide

Context This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to DL Tx Code Power, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_DL Tx Code Power_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

13-18


Issue 03 (2009-04-25)

RNC LMT User Guide


Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. The monitoring results reflect the variation of the number of the radio links involved in the current connection in real time. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported DL code TX power (unit: dBm). Code TX power refers to the NodeB TX power on one channelization code that is on one given scrambling code on one given carrier. The DL code TX power can be measured on the DPCCH of any radio link outgoing from the UTRAN and indicates the pilot bit power of the DPCCH. The measurement should involve all timeslots, such as transmit timeslots, in compressed mode. The reference point for measurement is at the antenna connector. If transmit diversity is used, you need to measure the code TX power of each diversity and then sum them up to obtain the DL code TX power.


13.3.6 Monitoring the UE TX Power This describes how to monitor in real time the variation of the UE TX power of the current connection. By performing this task, you can analyze the UL quality. If the UE TX power increases, even reaching the limit of the UE capability, the UL quality declines.

Prerequisite l

The LMT is started.

l


Context UE TX power refers to the UE TX power in a carrier. The reference point for measurement of the UE TX power is at the antenna connector of the UE. This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel.


Issue 03 (2009-04-25)


13-19


RNC LMT User Guide


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to UE TxPower, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_UE TxPower_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported UE TX power (unit: dBm).


13.3.7 Monitoring UL Traffic This describes how to monitor in real time the UL traffic (that is, data buffer size on the UE side) of the current connection. By performing this task, you can analyze the transmission performance 13-20


Issue 03 (2009-04-25)

RNC LMT User Guide


of the UL traffic. The UL traffic is measured by the UE and reported to the RNC per transport channel.

Prerequisite l

The LMT is started.

l


Context Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be transmitted or retransmitted from the RLC entity on each logical channel. If RLC is in AM mode, the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmit window and excludes the PDUs transmitted but not acknowledged. This task can monitor the connections of PS domain interactive and background services on both common channels and dedicated channels.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to UL Traffic Vol, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC Issue 03 (2009-04-25)


13-21

RNC LMT User Guide


\LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_UL Traffic Vol_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported UL traffic on the UL physical channel (unit: byte).


13.3.8 Monitoring DL Traffic This describes how to monitor the DL traffic (that is, data buffer size on the network side) of the current connection. By performing this task, you can analyze the transmission performance of the DL traffic. The DL traffic is measured at the RNC per transport channel.

Prerequisite l

The LMT is started.

l


Context Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be transmitted or retransmitted from the RLC entity on each logical channel. If RLC is in AM mode, the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmit window and excludes the PDUs transmitted but not acknowledged. This task can monitor the connections of PS domain interactive and background services on both common channels and dedicated channels.


13-22


Issue 03 (2009-04-25)

RNC LMT User Guide



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to DL Traffic Vol, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_DL Traffic Vol_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported DL traffic (unit: byte).


Issue 03 (2009-04-25)


13-23

RNC LMT User Guide


13.3.9 Monitoring UL Throughput and Bandwidth This describes how to monitor in real time the rate variation of the UL transport access stratum and non-access stratum of the current connection. By performing this task, you can analyze the dynamic channel configuration function and service source rate variation characteristics.

Prerequisite l

The LMT is started.

l


Context Throughput refers to the amount of data transmitted on a transport channel in a unit of time. Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculated according to RLC payload. The bandwidth changes in RB reconfiguration. The throughput measurement involves RLC headers, and therefore, the measured peak throughput is higher than the bandwidth. This task can monitor the connections of PS domain interactive and background services on both common channels and dedicated channels.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to UL Throughput & Bandwidth, and then set Monitor period(s) and IMSI.

13-24


Issue 03 (2009-04-25)

RNC LMT User Guide

13 RNC Real-Time Performance Monitoring NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_UL Throughput & Bandwidth_YYYY-MM-DD-HH-MMSS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported UL throughput and UL bandwidth (unit: bit/s). l

When verifying the dynamic channel configuration function, observe the variation of UL throughput and UL bandwidth. If the UL bandwidth increases or decreases with the UL throughput, you can infer that the dynamic channel configuration function is normal.

l

When the dynamic channel configuration function is not used, you can also learn the rate variation characteristics of UL service source by observing the variation of UL throughput.


13.3.10 Monitoring DL Throughput and Bandwidth This describes how to monitor in real time the rate variation of the DL transport access stratum and non-access stratum of the current connection. By performing this task, you can analyze the dynamic channel configuration function and service source rate variation characteristics.

Prerequisite l

The LMT is started.

l


Context Throughput refers to the amount of data transmitted on a transport channel in a unit of time. Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculated according to RLC payload. The bandwidth changes in RB reconfiguration. The throughput measurement involves RLC headers, and therefore, the measured peak throughput is higher than the bandwidth. Issue 03 (2009-04-25)


13-25


RNC LMT User Guide

This task can monitor the connections of PS domain interactive and background services on both common channels and dedicated channels.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to DL Throughput & Bandwidth, and then set Monitor period(s) and IMSI. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_DL Throughput & Bandwidth_YYYY-MM-DD-HH-MMSS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported DL throughput and DL bandwidth (unit: bit/s). 13-26


Issue 03 (2009-04-25)

RNC LMT User Guide

13 RNC Real-Time Performance Monitoring l

When verifying the dynamic channel configuration function, observe the variation of DL throughput and DL bandwidth. If the DL bandwidth increases or decreases with the DL throughput, you can infer that the dynamic channel configuration function is normal.

l

When the dynamic channel configuration function is not used, you can also learn the rate variation characteristics of DL service source by observing the variation of DL throughput.


13.3.11 Monitoring Handover Delay This describes how to monitor the handover delay performance. By performing this task, you can observe and obtain the time taken by each handover of the current connection. The handover includes intra-frequency soft handover and inter-frequency handover.

Prerequisite l

The LMT is started.

l


Context Handover delay refers to the period during which: the RNC receives a measurement report; the RNC implements a handover decision; the RNC initiates a soft or hard handover; the handover ends. This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel. At most five handover delay monitoring tasks can be started simultaneously. This task can monitor only intra-frequency handover and inter-frequency handover but cannot monitor interRAT handover.


Issue 03 (2009-04-25)


13-27


RNC LMT User Guide


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to HO Delay, and then set IMSI. NOTE

For this task, you need not set Monitor period(s).

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_HO Delay_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite The real-time monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the interval of each successful handover (unit: ms).


13.3.12 Monitoring the BLER of the DL Transport Channel This describes how to monitor the variation of the BLER on all transport channels of the current connection. By performing this task, you can analyze the DL quality. If the BLER of the DL transport channel increases, you can infer that the DL quality declines. If the BLER decreases, you can infer that the DL quality is improved. 13-28


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context The BLER of the DL transport channel is measured at the UE. The BLER is used for outer loop power control. This task applies to only monitoring connections established on dedicated channels. A started task is stopped if the monitored connection is released or transited from the dedicated channel to the common channel. The task is restarted if the monitored connection is transited from the common channel back to the dedicated channel.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to DL BLER, and then set Monitor period(s) and IMSI. NOTE

If Monitor period(s) is set too short, a large amount of reported data increases the overhead of signaling transport on the Uu interface and system processing, which has influence on the CPU usage of the system. You are advised to set Monitor period(s) to 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_DL BLER_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Issue 03 (2009-04-25)


13-29

RNC LMT User Guide


Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. The monitoring results reflect the variation of the number of traffic transport channels in real time. The number of signaling transport channels is always 1. In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is not less than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the reported BLER of the DL transport channel (unit: %).


13.3.13 Monitoring the AMR Mode This describes how to monitor the variation of the AMR rate configured by the UE and to record the variation in real time.

Prerequisite l

The LMT is started.

l


Context The monitoring is valid only when the traced UE has an AMR service in process. The narrowband AMR has 8 available rates, that is, 8 available modes: 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s. The wideband AMR has 9 available rates, that is, 9 available modes: 23.85 kbit/s, 23.05 kbit/s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.60 kbit/s.


13-30


Issue 03 (2009-04-25)

RNC LMT User Guide



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, set Monitor item to AMR Mode, and then set IMSI. NOTE

For this task, you need not set Monitor period(s).

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Connection performance monitoring_AMR Mode_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value. Step 4 Click OK. The monitoring is started. ----End

Postrequisite The real-time monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the maximum mode of the current AMR in UL and DL (unit: KB).


13.4 Monitoring the RNC Cell Performance This describes how to monitor the cell performance, such as the common measured value and number of common channel users. For the same monitoring item, you can start at most six tasks simultaneously. 13.4.1 Monitoring Cell P-CPICH TX Power Issue 03 (2009-04-25)


13-31


RNC LMT User Guide

This describes how to monitor the Primary Common Pilot Channel (P-CPICH) TX power of a specified cell. By performing this task, you can observe and determine in real time whether the pilot power is normal. 13.4.2 Monitoring UL RX Total Wideband Power of a Cell This describes how to monitor the UL RX total wideband power of a specified cell. By performing this task, you can observe the UL load level in real time. The UL RX total wideband power is measured and reported by the related NodeB. 13.4.3 Monitoring DL Carrier TX Power of a Cell This describes how to monitor the DL TX carrier power of a specified cell. By performing this task, you can observe the DL load level in real time. The DL TX carrier power of a cell is measured and reported by the related NodeB. 13.4.4 Monitoring the Number of Cell Users This describes how to monitor the number of users in a specified cell. By performing this task, you can observe in real time the user number of the common channels, dedicated channels, HSDPA services, and HSUPA services in the cell. You can also learn about the distribution of the users in the cell. 13.4.5 Monitoring Node Synchronization This describes how to monitor the time difference between RNC Frame Number (RFN) and NodeB Frame Number (BFN) of the specified cell and the time taken for node synchronization. By performing this task, you can observe the float situations of RFN and BFN in real time. If the difference between RFN and BFN varies too rapidly, you can infer that there are some problems on the transmission between the RNC and the NodeB. 13.4.6 Monitoring the UL CAC This describes how to monitor the UL Call Admission Control (CAC) procedure of a specified cell. By performing this task, you can observe the variation of the predicted values and measured values of UL load so as to measure the predicted accuracy of the UL CAC algorithm. 13.4.7 Monitoring DL CAC This describes how to monitor the DL Call Admission Control (CAC) procedure of a specified cell. By performing this task, you can observe the variation of the predicted values and measured values of the DL load so as to measure the predicted accuracy of the DL CAC algorithm. 13.4.8 Monitoring the Number of UL Equivalent Users This describes how to monitor the number of UL equivalent users in a specified cell. By performing this task, you can observe the variation in the number of UL equivalent users. 13.4.9 Monitoring the Number of DL Equivalent Users This describes how to monitor the number of DL equivalent users in a specified cell. By performing this task, you can observe the variation in the number of DL equivalent users. 13.4.10 Monitoring the Cell Code Tree This describes how to monitor the DL channel OVSF code tree of a specified cell. By performing this task, you can observe the usage of the DL channel code in real time. 13.4.11 Monitoring the Minimum Required Power of the HS-DSCH This describes how to monitor the minimum required power of the HS-DSCH of a specified cell. By performing this task, you can observe the ratio of the minimum required power to the maximum TX power on the HS-DSCH in the cell. 13.4.12 Monitoring the Bit Rate Provided by the HS-DSCH This describes how to monitor the bit rate of the HS-DSCH of a specified cell. By performing this task, you can observe the variation of the transmission rate provided by the HS-DSCH. 13-32


Issue 03 (2009-04-25)

RNC LMT User Guide


13.4.13 Monitoring the Bit Rate Provided by the E-DCH This describes how to monitor the bit rate provided by the E-DCH that is set up for the HSUPA services. By performing this task, you can observe the variation of the transmission rate provided by the E-DCH in real time. 13.4.14 Monitoring UL Throughput of a Cell Throughput refers to the maximum rate of the equipment in the case that no frame is lost. UL throughput of a cell refers to the throughput of the cell in the UL. 13.4.15 Monitoring DL Throughput of a Cell Throughput refers to the maximum rate of the equipment in the case that no frame is lost. DL throughput of a cell refers to the throughput of the cell in the DL. 13.4.16 Monitoring the Cell CE This describes how to monitor the credit and consumption of the local cell, the local cell group, and the corresponding NodeB. Based on the monitoring result, the RNC determines whether to grant an new access request of an MS. 13.4.17 Monitoring the FDPCH SYMBOL This describes how to monitor the condition of the F-DPCH SYMBOL, including the F-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.



13.4.1 Monitoring Cell P-CPICH TX Power This describes how to monitor the Primary Common Pilot Channel (P-CPICH) TX power of a specified cell. By performing this task, you can observe and determine in real time whether the pilot power is normal.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


13-33


RNC LMT User Guide

Context You can query the range of the P-CPICH TX power by running LST PCPICH. If the pilot power exceeds this range, you can infer that the power is abnormal.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Cell performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-20. Figure 13-20 Cell performance monitoring dialog box

Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to PCPICH TxPower, and then set Monitor period(s) and Cell ID. NOTE

The value range of Monitor period(s) is from 0.5 to 120. Its recommended value is 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_PCPICH TxPower_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. Figure 13-21 is an example of the output interface (chart) of cell P-CPICH TX power monitoring. 13-34


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-21 Output interface of cell P-CPICH TX power monitoring

In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the PCPICH power (unit: dBm).

Related References 13.8.3 Parameter Reference for Cell Performance Monitoring

13.4.2 Monitoring UL RX Total Wideband Power of a Cell This describes how to monitor the UL RX total wideband power of a specified cell. By performing this task, you can observe the UL load level in real time. The UL RX total wideband power is measured and reported by the related NodeB.

Prerequisite l

The LMT is started.

l


Context The CAC procedure measures the UL load by the UL load factor, the ratio of (UL RX total wideband power – cell background noise) to UL RX total wideband power. The background noise of the cell approximates to a constant, which can be set through the command ADD CELLCAC or MOD CELLCAC. Therefore, the UL RX total wideband power can also be used to measure the relative level of the UL load of the cell. Issue 03 (2009-04-25)


13-35


RNC LMT User Guide


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to RTWP, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_RTWP_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. Figure 13-23 is an example of the output interface (chart) of UL RX total wideband power monitoring for a cell.

13-36


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-23 Output interface of UL RX total wideband power monitoring for a cell

In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the cell UL RX total wideband power (unit: dBm).


13.4.3 Monitoring DL Carrier TX Power of a Cell This describes how to monitor the DL TX carrier power of a specified cell. By performing this task, you can observe the DL load level in real time. The DL TX carrier power of a cell is measured and reported by the related NodeB.

Prerequisite l

The LMT is started.

l


Context The CAC procedure uses the ratio of the DL TX carrier power to the maximum TX power of the cell to measure the DL load of the cell. When setting up a cell, you can run ADD CELLSETUP to set the maximum TX power. After the cell is set up, you can run MOD CELL to modify it. Issue 03 (2009-04-25)


13-37


RNC LMT User Guide


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Tx Carrier Power, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Tx Carrier Power_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. Figure 13-25 is an example of the output interface (chart) of DL TX carrier power monitoring for a cell.

13-38


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-25 Output interface of DL TX carrier power monitoring for a cell

In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the ratio of the DL TX carrier power to the maximum TX power of the cell (unit: %).


13.4.4 Monitoring the Number of Cell Users This describes how to monitor the number of users in a specified cell. By performing this task, you can observe in real time the user number of the common channels, dedicated channels, HSDPA services, and HSUPA services in the cell. You can also learn about the distribution of the users in the cell.

Prerequisite l


l


Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Cell performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-26. Issue 03 (2009-04-25)


13-39


RNC LMT User Guide

Figure 13-26 Cell performance monitoring dialog box

Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Cell User Num, and then set Monitor period(s) and Cell ID. NOTE

The value range of Monitor period(s) is from 1 to 1,800. Its recommended value is 1.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Cell User Num_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the number of cell users.


13.4.5 Monitoring Node Synchronization This describes how to monitor the time difference between RNC Frame Number (RFN) and NodeB Frame Number (BFN) of the specified cell and the time taken for node synchronization. By performing this task, you can observe the float situations of RFN and BFN in real time. If the difference between RFN and BFN varies too rapidly, you can infer that there are some problems on the transmission between the RNC and the NodeB. 13-40


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

The LMT is started.

l



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Node Sync, and then set Monitor period(s) and Cell ID. NOTE

The value range of Monitor period(s) is from 30 to 300. Its recommended value is 30s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Node Sync_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. Figure 13-28 is an example of the output interface (chart) of node synchronization monitoring. Issue 03 (2009-04-25)


13-41

RNC LMT User Guide


Figure 13-28 Output interface of node synchronization monitoring

In the chart, the X-coordinate represents the time. The time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the time difference between RFN and BFN and the time taken by the NodeB to finish node synchronization (unit: ms).


13.4.6 Monitoring the UL CAC This describes how to monitor the UL Call Admission Control (CAC) procedure of a specified cell. By performing this task, you can observe the variation of the predicted values and measured values of UL load so as to measure the predicted accuracy of the UL CAC algorithm.

Prerequisite l


l


Context The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC algorithm 2). Run MOD CELLALGOSWITCH to set the UL CAC algorithm of a cell. Run LST CELLALGOSWITCH to query the UL CAC algorithm of a cell. 13-42


Issue 03 (2009-04-25)

RNC LMT User Guide

13 RNC Real-Time Performance Monitoring l

CAC algorithm 1 measures the UL load by the UL load factor, the ratio of (UL RX total wideband power - cell background noise) to UL RX total wideband power. You can run the command ADD CELLCAC or MOD CELLCAC to set the cell background noise.

l

CAC algorithm 2 uses the ratio of the current number to the maximum number of UL equivalent users to measure the load of the cell. By default, algorithm 2 is used to measure the UL load of the cell.


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to UL CAC Monitor, and then set Monitor period(s) and Cell ID. NOTE

The value range of Monitor period(s) is from 0.1 to 300. Its recommended value is 0.5.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_UL CAC Monitor_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. Issue 03 (2009-04-25)


13-43

RNC LMT User Guide


In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the PCPICH power (unit: dBm).


13.4.7 Monitoring DL CAC This describes how to monitor the DL Call Admission Control (CAC) procedure of a specified cell. By performing this task, you can observe the variation of the predicted values and measured values of the DL load so as to measure the predicted accuracy of the DL CAC algorithm.

Prerequisite l


l


Context The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC algorithm 2). Run MOD CELLALGOSWITCH to set the UL CAC algorithm of a cell. Run LST CELLALGOSWITCH to query the UL CAC algorithm of a cell. l

CAC algorithm 1 uses the ratio of the DL TX carrier power to the maximum TX power of the cell to measure the DL load of the cell. By default, algorithm 1 is used to measure the DL load of the cell. The maximum TX power is a constant. You can run ADD CELLSETUP to set it.

l

CAC algorithm 2 uses the ratio of the current DL equivalent number of users to the maximum DL equivalent number of users.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Cell performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-30.

13-44


Issue 03 (2009-04-25)

RNC LMT User Guide



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to DL CAC Monitor, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_DL CAC Monitor_YYYY-MM-DD-HH-MM-SS_Cell ID-cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the predicted values and measured values of the load (unit: %).


13.4.8 Monitoring the Number of UL Equivalent Users This describes how to monitor the number of UL equivalent users in a specified cell. By performing this task, you can observe the variation in the number of UL equivalent users. Issue 03 (2009-04-25)


13-45

RNC LMT User Guide


Prerequisite l


l



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to UL Total Equivalent User Num, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_UL Total Equivalent User Num_YYYY-MM-DD-HH-MMSS_Cell ID-Cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, 13-46


Issue 03 (2009-04-25)

RNC LMT User Guide


the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the predicted values and measured values of the number of UL equivalent users.


13.4.9 Monitoring the Number of DL Equivalent Users This describes how to monitor the number of DL equivalent users in a specified cell. By performing this task, you can observe the variation in the number of DL equivalent users.

Prerequisite l


l


Context Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Cell performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-32. Figure 13-32 Cell performance monitoring dialog box

Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to DL Total Equivalent User Num, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC Issue 03 (2009-04-25)


13-47

RNC LMT User Guide


\LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_DL Total Equivalent User Num_YYYY-MM-DD-HH-MMSS_Cell ID-Cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the predicted values and measured values of the number of DL equivalent users.


13.4.10 Monitoring the Cell Code Tree This describes how to monitor the DL channel OVSF code tree of a specified cell. By performing this task, you can observe the usage of the DL channel code in real time.

Prerequisite l

The LMT is started.

l



13-48


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Cell Code Tree Monitor, and then set Cell ID. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Cell Code Tree Monitor_YYYY-MM-DD-HH-MM-SS_Cell IDCell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite The LMT displays a real-time monitoring window with the monitoring task name on the title bar. You can query the usage of the cell code tree in static or dynamic view. l

When querying the usage of the cell code tree in static view, you can obtain the usage of each code in the cell code tree, as shown in Figure 13-34.

l

When querying the usage of the cell code tree in dynamic view, you can view the usage in list or chart. In the chart, the X-coordinate represents the time; the Y-coordinate represents the codes.

Figure 13-34 Output of the cell code tree usage in static view

Issue 03 (2009-04-25)


13-49

RNC LMT User Guide



13.4.11 Monitoring the Minimum Required Power of the HS-DSCH This describes how to monitor the minimum required power of the HS-DSCH of a specified cell. By performing this task, you can observe the ratio of the minimum required power to the maximum TX power on the HS-DSCH in the cell.

Prerequisite l

The LMT is started.

l



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to HS-DSCH Min Power Requirement, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_HS-DSCH Min Power Requirement_YYYY-MM-DD-HH-MMSS_Cell ID-Cell ID. 13-50


Issue 03 (2009-04-25)

RNC LMT User Guide



Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the ratio of the required power to the maximum TX power of the cell (unit: ‰).


13.4.12 Monitoring the Bit Rate Provided by the HS-DSCH This describes how to monitor the bit rate of the HS-DSCH of a specified cell. By performing this task, you can observe the variation of the transmission rate provided by the HS-DSCH.

Prerequisite l

The LMT is started.

l


Context NOTE

Before performing the bit rate monitoring on the HS-DSCH, ensure that the HSDPA_PBR_MEAS of the cell is switched on (that is, set to 1). Otherwise, when you create a monitoring task, a prompt is displayed: Measurement not available. Run the LST CELLALGOSWITCH command on the MML client to query the state of HSDPA_PBR_MEAS switch. If the queried result is HSDPA PBR MEAS ALGORITHM:OFF, run MOD CELLALGOSWITCH to set it to ON.


Issue 03 (2009-04-25)


13-51

RNC LMT User Guide



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to HS-DSCH Provide Bitrate, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_HS-DSCH Provide Bitrate_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the bit rate (unit: bit/s).


13.4.13 Monitoring the Bit Rate Provided by the E-DCH This describes how to monitor the bit rate provided by the E-DCH that is set up for the HSUPA services. By performing this task, you can observe the variation of the transmission rate provided by the E-DCH in real time. 13-52


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context NOTE

Before performing the bit rate monitoring on the E-DCH, ensure that the HSUPA_PBR_MEAS of the cell is switched on (that is, set to 1). Otherwise, when you create a monitoring task, a prompt is displayed: Measurement not available. Run the LST CELLALGOSWITCH command on the MML client to query the state of HSUPA_PBR_MEAS switch. If the queried result is HSUPA PBR MEAS ALGORITHM:OFF, run MOD CELLALGOSWITCH to set it to ON.


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to E-DCH Provide Bitrate, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_E-DCH Provide Bitrate_YYYY-MM-DD-HH-MM-SS_Cell IDCell ID. Issue 03 (2009-04-25)


13-53

RNC LMT User Guide



Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the bit rate (unit: bit/s).


13.4.14 Monitoring UL Throughput of a Cell Throughput refers to the maximum rate of the equipment in the case that no frame is lost. UL throughput of a cell refers to the throughput of the cell in the UL.

Prerequisite l

The LMT is started.

l



13-54


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Cell UL ThroughPut, and then set Monitor period(s) and Cell ID. NOTE

The value of Monitor period(s) can be 0.25, 0.5, 1, 2, 4, or 8. Its recommended value is 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Cell UL ThroughPut_YYYY-MM-DD-HH-MM-SS_Cell IDCell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the UL throughput of the cell.


13.4.15 Monitoring DL Throughput of a Cell Throughput refers to the maximum rate of the equipment in the case that no frame is lost. DL throughput of a cell refers to the throughput of the cell in the DL.

Prerequisite l

The LMT is started.

l



Issue 03 (2009-04-25)


13-55


RNC LMT User Guide


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Cell DL ThroughPut, and then set Monitor period(s) and Cell ID. NOTE

The value of Monitor period(s) can be 0.25, 0.5, 1, 2, 4, or 8. Its recommended value is 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Cell DL ThroughPut_YYYY-MM-DD-HH-MM-SS_Cell IDCell ID. Step 4 Click OK. The monitoring is started. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The title of the window indicates the task name. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the DL throughput of the cell.


13.4.16 Monitoring the Cell CE This describes how to monitor the credit and consumption of the local cell, the local cell group, and the corresponding NodeB. Based on the monitoring result, the RNC determines whether to grant an new access request of an MS. 13-56


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l


l



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to Cell CE, and then set Monitor period(s) and Cell ID. NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_Cell CE_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID. Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time unit is RFN (one RFN corresponds to 10 ms). If the reporting period is greater than 10s, the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents the credit (unit: none) of the local cell, local cell group, and the NodeB corresponding to the cell. Issue 03 (2009-04-25)


13-57

RNC LMT User Guide



13.4.17 Monitoring the FDPCH SYMBOL This describes how to monitor the condition of the F-DPCH SYMBOL, including the F-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.

Prerequisite l


l


Context The F-DPCH channel bears the Transport Power Control (TPC) information of HSDPA services and uses the spreading factor SF256.


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitor item to FDPCH SYMBOL monitoring, and then set Cell ID. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Cell performance monitoring_FDPCH SYMBOL monitoring_YYYY-MM-DD-HH-MMSS_Cell ID-Cell ID. 13-58


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 4 Click OK to start the monitoring. ----End

Postrequisite A monitoring window is displayed, showing the real-time monitoring results in list and chart. The task name is indicated in the title of the window. l

In the static view of the FDPCH SYMBOL monitoring, you can see the condition of the SYMBOL corresponding to the F-DPCH code. The numbers in the grids indicate the timeslot formats.

l

In the dynamic view of the FDPCH SYMBOL monitoring, the X-coordinate represents the time, and the Y-coordinate represents the F-DPCH code, position of the F-DPCH SYMBOL, and timeslot format.


13.5 Monitoring the RNC Link Performance This describes how to monitor the RNC link performance. This task applies to the traffic statistics based on IP path/SCTP/OAM stream, statistics based on priority queues. The statistics based on priority queues include the statistics of packet loss rate, number of the sent packets, and number of the sent bytes. For the same monitoring item, you can start up to six tasks. 13.5.1 Monitoring the IMA Group Traffic This describes how to monitor the traffic on a specified IMA group in real time. The real-time traffic on the current IMA group is displayed in either list or chart. 13.5.2 Monitoring the UNI Link Traffic This describes how to monitor the traffic on a specified UNI link in real time. The real-time traffic on the current UNI link is displayed in either list or chart. 13.5.3 Monitoring the Fractional ATM Link Traffic This describes how to monitor the traffic on a specified fractional ATM link in real time. The real-time traffic on the current fractional ATM link is displayed in either list or chart. 13.5.4 Monitoring the SAAL Link Traffic This describes how to monitor the traffic on a specified SAAL link in real time. The real-time traffic on the current SAAL link is displayed in either list or chart. 13.5.5 Monitoring the IPoA PVC Traffic This describes how to monitor the traffic on a specified IPoA PVC in real time. The real-time traffic on the current IPoA PVC is displayed in either list or chart. 13.5.6 Monitoring the AAL2 Path Traffic This describes how to monitor the traffic on a specified AAL2 path in real time. The real-time traffic on the current AAL2 path is displayed in either list or chart. 13.5.7 Monitoring the FE/GE Traffic This describes how to monitor the traffic on a specified FE/GE port in real time. The real-time traffic on the current FE/GE port is displayed in either list or chart. 13.5.8 Monitoring the PPP Link Traffic Issue 03 (2009-04-25)


13-59


RNC LMT User Guide

This describes how to monitor the traffic on a specified PPP link in real time. The real-time traffic on the current PPP link is displayed in either list or chart. 13.5.9 Monitoring the MLPPP Group Traffic This describes how to monitor the traffic on a specified MLPPP group in real time. The realtime traffic on the current MLPPP group is displayed in either list or chart. 13.5.10 Monitoring the SCTP Link Traffic This describes how to monitor the traffic on a specified SCTP link in real time. The real-time traffic on the current SCTP link is displayed in either list or chart. 13.5.11 Monitoring the IP Path Traffic This describes how to monitor the traffic on a specified IP path in real time. The real-time traffic on the current IP path is displayed in either list or chart. 13.5.12 Monitoring the Logical Ports This describes how to monitor the traffic of the specified logical port in real time. You can monitor an entire port, where the monitoring result displays the real-time traffic of the current logical port. You can also monitor only the specified priority of the port, where the monitoring result displays the TX traffic of the specified priority of the current logical port. 13.5.13 Monitoring OAM Traffic This describes how to monitor the RX and TX traffic of the specified NodeB OM channel. The traffic of the current NodeB OM channel is displayed in either list or chart. 13.5.14 Monitoring Bandwidth of Logical Ports This describes how to monitor the physical bandwidth of logical ports. The bandwidth of the current logical port is displayed in either list or chart.



13.5.1 Monitoring the IMA Group Traffic This describes how to monitor the traffic on a specified IMA group in real time. The real-time traffic on the current IMA group is displayed in either list or chart.

13-60


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context

CAUTION This task only applies to monitoring the IMA group that is successfully configured and connected to its peer end. After the task is started, deleting the monitored IMA group stops the task.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Link performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-42. Figure 13-42 Link performance monitoring dialog box

Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to IMA Group, and then set Subrack No., Slot No., and IMA Group No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_IMA Group_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End Issue 03 (2009-04-25)


13-61

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-43 is an example of the output interface (chart) of IMA group real-time traffic monitoring. Figure 13-43 Output interface of IMA group real-time traffic monitoring

In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic in kbit/s.

Related References 13.8.4 Parameter Reference for Link Performance Monitoring

13.5.2 Monitoring the UNI Link Traffic This describes how to monitor the traffic on a specified UNI link in real time. The real-time traffic on the current UNI link is displayed in either list or chart.

Prerequisite

13-62

l

The LMT is started.

l



Issue 03 (2009-04-25)

RNC LMT User Guide


Context

CAUTION This task only applies to monitoring the UNI link that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to UNI Link, and then set Subrack No., Slot No., and UNI Link No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_UNI Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-45 is an example of the output interface (chart) of UNI link real-time traffic monitoring. Issue 03 (2009-04-25)


13-63

RNC LMT User Guide


Figure 13-45 Output interface of UNI link real-time traffic monitoring



13.5.3 Monitoring the Fractional ATM Link Traffic This describes how to monitor the traffic on a specified fractional ATM link in real time. The real-time traffic on the current fractional ATM link is displayed in either list or chart.

Prerequisite l


l


Context

CAUTION This task only applies to monitoring the fractional ATM link that is successfully configured and connected to its peer end. If you delete the monitored link after the task is started, deleting the monitored link stops the task.

13-64


Issue 03 (2009-04-25)

RNC LMT User Guide



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to FRAC ATM Link, and then set Subrack No., Slot No., and FRAC Link No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_FRAC ATM Link_YYYY-MM-DD-HH-MM-SS_Subrack No.a.txt. Step 4 Click OK to start the monitoring. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The task name and related parameters are indicated in the title of the window. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic (unit: kbit/s).

Related References 13.8.4 Parameter Reference for Link Performance Monitoring Issue 03 (2009-04-25)


13-65

RNC LMT User Guide


13.5.4 Monitoring the SAAL Link Traffic This describes how to monitor the traffic on a specified SAAL link in real time. The real-time traffic on the current SAAL link is displayed in either list or chart.

Prerequisite l

The LMT is started.

l


Context

CAUTION This task only applies to monitoring the SAAL link that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to SAAL Link, and then set Subrack No., Slot No., Subsystem No., and SAAL Link No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC 13-66


Issue 03 (2009-04-25)

RNC LMT User Guide


\LMT software version number\output\realmonitor. The default file name is Link performance monitoring_SAAL Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-48 is an example of the output interface (chart) of SAAL link real-time traffic monitoring. Figure 13-48 Output interface of SAAL link real-time traffic monitoring



13.5.5 Monitoring the IPoA PVC Traffic This describes how to monitor the traffic on a specified IPoA PVC in real time. The real-time traffic on the current IPoA PVC is displayed in either list or chart.

Issue 03 (2009-04-25)


13-67

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context

CAUTION This task only applies to monitoring the IPoA PVC that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to IPOA PVC, and then set Subrack No., IP Address, and Peer IP Address. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_IPOA PVC_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End 13-68


Issue 03 (2009-04-25)

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-50 is an example of the output interface (chart) of IPoA PVC real-time traffic monitoring. Figure 13-50 Output interface of IPoA PVC real-time traffic monitoring



13.5.6 Monitoring the AAL2 Path Traffic This describes how to monitor the traffic on a specified AAL2 path in real time. The real-time traffic on the current AAL2 path is displayed in either list or chart.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


13-69


RNC LMT User Guide

Context

CAUTION This task only applies to monitoring the AAL2 path that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to AAL2 PATH, and then set Subrack No., Neighbor Node ID, and AAL2 PATH ID. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_AAL2 PATH_YYYY-MM-DD-HH-MM-SS_Subrack No.a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related 13-70


Issue 03 (2009-04-25)

RNC LMT User Guide


parameters. Figure 13-52 is an example of the output interface (chart) of AAL2 path real-time traffic monitoring. Figure 13-52 Output interface of AAL2 path real-time traffic monitoring



13.5.7 Monitoring the FE/GE Traffic This describes how to monitor the traffic on a specified FE/GE port in real time. The real-time traffic on the current FE/GE port is displayed in either list or chart.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


13-71


RNC LMT User Guide

Context

CAUTION This task only applies to monitoring the FE/GE port that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to FE&GE, and then set Subrack No., Slot No., strMonitorType, and FE&GE Port No.. NOTE

l

strMonitorType can be Port or QoS.

l

When QoS is selected, specify QoS No. with a value ranging from 0 to 5.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_FE&GE_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End 13-72


Issue 03 (2009-04-25)

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-54 is an example of the output interface (chart) of FE/GE real-time traffic monitoring. Figure 13-54 Output interface of FE/GE real-time traffic monitoring



13.5.8 Monitoring the PPP Link Traffic This describes how to monitor the traffic on a specified PPP link in real time. The real-time traffic on the current PPP link is displayed in either list or chart.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


13-73


RNC LMT User Guide

Context

CAUTION This task only applies to monitoring the PPP link that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to PPP Link, and then set Subrack No., Slot No., strMonitorType, and PPP Link No.. NOTE

l

strMonitorType can be Link or QoS.

l


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_PPP Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End 13-74


Issue 03 (2009-04-25)

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic in kbit/s.


13.5.9 Monitoring the MLPPP Group Traffic This describes how to monitor the traffic on a specified MLPPP group in real time. The realtime traffic on the current MLPPP group is displayed in either list or chart.

Prerequisite l

The LMT is started.

l


Context

CAUTION This task only applies to monitoring the MLPPP group that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Link performance monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-56.

Issue 03 (2009-04-25)


13-75


RNC LMT User Guide

Figure 13-56 Link performance monitoring dialog box

Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to MLPPP Group, and then set Subrack No., Slot No., strMonitorType, and MLPPP Group No.. NOTE

l

strMonitorType can be MLPPP Group or QoS.

l


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_MLPPP Group_YYYY-MM-DD-HH-MM-SS_Subrack No.a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic in kbit/s.


13.5.10 Monitoring the SCTP Link Traffic This describes how to monitor the traffic on a specified SCTP link in real time. The real-time traffic on the current SCTP link is displayed in either list or chart. 13-76


Issue 03 (2009-04-25)

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context

CAUTION This task only applies to monitoring the SCTP link that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to SCTP Link, and then set Subrack No., Slot No., Subsystem No., and SCTP Link No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_SCTP Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End Issue 03 (2009-04-25)


13-77

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-58 is an example of the output interface (chart) of SCTP link real-time traffic monitoring. Figure 13-58 Output interface of SCTP link real-time traffic monitoring



13.5.11 Monitoring the IP Path Traffic This describes how to monitor the traffic on a specified IP path in real time. The real-time traffic on the current IP path is displayed in either list or chart.

Prerequisite

13-78

l

The LMT is started.

l


Issue 03 (2009-04-25)

RNC LMT User Guide


Context

CAUTION This task only applies to monitoring the IP path that is successfully configured and connected to its peer end. After the task is started, deleting the monitored link stops the task.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to IP PATH, and then set Subrack No., Slot No., Subsystem No., Neighbor Node ID, IP PATH ID, IPPATH Type, and PRI. NOTE

l

IPPATH Type can be QOSIPPATH or Other.

l

When QOSIPPATH is selected, PRI can be as follows in descending order: BE: 0, AF1: 1, AF2: 2, AF3: 3, AF4: 4, and EF: 5.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_IP PATH_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End Issue 03 (2009-04-25)


13-79

RNC LMT User Guide


Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-60 is an example of the output interface (chart) of IP path real-time traffic monitoring. Figure 13-60 Output interface of IP path real-time traffic monitoring



13.5.12 Monitoring the Logical Ports This describes how to monitor the traffic of the specified logical port in real time. You can monitor an entire port, where the monitoring result displays the real-time traffic of the current logical port. You can also monitor only the specified priority of the port, where the monitoring result displays the TX traffic of the specified priority of the current logical port.

Prerequisite

13-80

l

The LMT is started.

l


Issue 03 (2009-04-25)

RNC LMT User Guide



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to Logic Port, and then set Subrack No., Slot No., strMonitorType, and Port No.. NOTE

l

strMonitorType can be Port or QoS.

l


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_Logic Port_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the real-time traffic of the current logical port in kbit/s.

Related References 13.8.4 Parameter Reference for Link Performance Monitoring Issue 03 (2009-04-25)


13-81

RNC LMT User Guide


13.5.13 Monitoring OAM Traffic This describes how to monitor the RX and TX traffic of the specified NodeB OM channel. The traffic of the current NodeB OM channel is displayed in either list or chart.

Prerequisite l

The LMT is started.

l



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to OAM, and then set Subrack No. and NodeB ID. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_OAM_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. 13-82


Issue 03 (2009-04-25)

RNC LMT User Guide


In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic of the NodeB OM channel in kbit/ s.


13.5.14 Monitoring Bandwidth of Logical Ports This describes how to monitor the physical bandwidth of logical ports. The bandwidth of the current logical port is displayed in either list or chart.

Prerequisite l

The LMT is started.

l



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, set Monitor item to Logic Port Band Width, and then set Subrack No. and Logic Port. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is Link performance monitoring_Logic Port Band Width_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt. Issue 03 (2009-04-25)


13-83

RNC LMT User Guide



Postrequisite After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the bandwidth of the logical port in kbit/s.


13.6 Monitoring the RNC Board Resource This describes how to monitor licensed traffic volume for voice services and the PS domain data throughput on the user plane of a specified board in real time.

Prerequisite l

The LMT is started.

l


Context NOTE

l

This task can be performed only in GUI mode and applies to only the boards that are in position and running properly.

l

The RNC board resource monitoring supports only the SPUa board.

l

The system supports a maximum of six board monitoring tasks.

Procedure Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance Monitoring node, and then double-click Board resource monitoring. A dialog box for setting the parameters is displayed, as shown in Figure 13-64.

13-84


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-64 Board Resource monitoring dialog box

Step 2 In the displayed 13.8.5 Parameter Reference for Board Resource Monitoring, set Monitor item to License, and then set Monitor period(s) with a value ranging from 0.5 to 128 seconds, Subrack No., Slot No., and Subsystem No.. Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoring records. The default save path is LMT installation directory\adaptor\clientadaptor\RNC \LMT software version number\output\realmonitor. The default file name is monitor type_monitor item_YYYY-MM-DD-HH-MM-SS_Subrack No.-a_Slot No.-b_Subsystem No.-c.txt. Step 4 Click OK. The monitoring is started. ----End

Postrequisite The monitoring window is displayed, showing real-time monitoring results in list and chart. The title of the window indicates the task name and related parameters. Figure 13-65 is an example of the output interface (list) of board resource monitoring.

Issue 03 (2009-04-25)


13-85


RNC LMT User Guide

Figure 13-65 Output interface of board resource monitoring

In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN corresponds to 10 ms). The Y-coordinate represents the RX and TX traffic in KB.



Related References 13.8.5 Parameter Reference for Board Resource Monitoring 13-86


Issue 03 (2009-04-25)

RNC LMT User Guide


13.7 Basic RNC Real-Time Performance Monitoring Operations This describes how to perform basic operations after an RNC real-time performance monitoring task is started. 13.7.1 Browsing the RNC Monitoring Results Online This describes how to online browse and query the monitoring results that are dynamically displayed in the monitoring window in real time. 13.7.2 Switching the Display Mode This describes how to switch the display mode to lineargraph or histogram on the Chart tab page. 13.7.3 Setting the Default Display Mode This describes how to set the default display mode to lineargraph or histogram on the Chart tab page. 13.7.4 Editing the Display Mode for the Chart This describes how to edit the display mode for the chart in the real-time monitoring window, which is displayed after a monitoring task is created and started. Below the Chart tab page in the window, you can set the display parameters, including the color, type, and width of the lines. 13.7.5 Saving RNC Monitoring Results This describes how to save the monitoring results into local files. 13.7.6 Pausing and Resuming an RNC Monitoring Task This describes how to pause the connection/cell/link performance monitoring and board resource monitoring tasks and restart them later when needed. 13.7.7 Adding an RNC CPU/DSP Monitoring Task This describes how to add a required CPU/DSP monitoring item to a CPU/DSP usage monitoring task. 13.7.8 Deleting an RNC CPU/DSP Monitoring Task This describes how to delete an unnecessary CPU/DSP monitoring item from a CPU/DSP usage monitoring task. 13.7.9 Stopping an RNC Monitoring Task This describes how to stop a monitoring task when it is no longer needed. 13.7.10 Browsing RNC Monitoring Results Offline For the results of the connection/cell/link performance monitoring and board resource monitoring, you can double-click the .txt files in which the results are saved and read the details.

13.7.1 Browsing the RNC Monitoring Results Online This describes how to online browse and query the monitoring results that are dynamically displayed in the monitoring window in real time.

Prerequisite l

Issue 03 (2009-04-25)

A real-time performance monitoring task is started. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

13-87


RNC LMT User Guide

l

Monitoring results are reported by the RNC.

l

Right-click on the chart tab page in the real-time performance monitoring window. Then, you can perform the following operations by selecting the corresponding item from the shortcut menu:

Procedure

l

l

–

Setting auto scroll

–

Showing or hiding the grid

–

Set the Y axis display range (only applicable to the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring tasks)

–

Switching the display mode

Right-click on the list tab page in the real-time performance monitoring window. Then, you can perform the following operations by selecting the corresponding item from the shortcut menu: –

Setting auto scroll

–

Saving selected data (only applicable to the connection performance monitoring, cell performance monitoring, and link performance monitoring tasks)

–

Quering the attributes (only applicable to the CPU/DSP usage monitoring task)

Right-click on the task information pane at the bottom of the real-time performance monitoring window. Then, you can perform the following operations by selecting the corresponding item from the shortcut menu: –

Adding or deleting tasks

–

Stopping or restarting monitoring tasks

–

Starting or stopping saving the task data

–

Querying details of tasks (only applicable to the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring tasks)

----End

Related Tasks 13.7.10 Browsing RNC Monitoring Results Offline

13.7.2 Switching the Display Mode This describes how to switch the display mode to lineargraph or histogram on the Chart tab page.

Prerequisite l

A real-time performance monitoring task is started.

l


l

Histogram

Procedure

13-88


Issue 03 (2009-04-25)

RNC LMT User Guide


A histogram displays monitoring results in bar mode. Therefore, you can directly learn the current monitoring results. The X-coordinate represents the task number; the Y-coordinate has different meanings according to different monitoring tasks. For example, for the CPU/DSP usage monitoring task, the Y-coordinate represents the percentage. l

Lineargraph A lineargraph displays monitoring results in curve mode. Therefore, you can learn about the variation of monitoring results in a period of time. The floating curves in the window reflect the variation of monitoring results. The X-coordinate represents the time; the Y-coordinate has different meanings according to different monitoring tasks. For example, for the CPU/DSP usage monitoring task, the Y-coordinate represents the percentage. NOTE

l

The task information pane at the bottom of the window displays related information about monitoring tasks in table. For example, for the CPU/DSP usage monitoring task, the task information pane displays the following information: task ID, whether to display line or not, color setting, line type, line width, subrack number, slot number, usage (%), and task status.

l

You can perform 13.7.4 Editing the Display Mode for the Chart as required in the task information pane at the bottom of the monitoring window.

----End

13.7.3 Setting the Default Display Mode This describes how to set the default display mode to lineargraph or histogram on the Chart tab page.

Prerequisite l


l


Context NOTE

This task is valid only for the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring tasks.

Procedure Step 1 Right-click on the Chart tab page, choose Set Default Display Mode. The Set Default Display Mode dialog box is displayed. Step 2 In the Default Display Mode area, select Line or histogram. ----End

Issue 03 (2009-04-25)


13-89


RNC LMT User Guide

13.7.4 Editing the Display Mode for the Chart This describes how to edit the display mode for the chart in the real-time monitoring window, which is displayed after a monitoring task is created and started. Below the Chart tab page in the window, you can set the display parameters, including the color, type, and width of the lines.

Prerequisite l


l


Procedure Step 1 In the task information pane at the bottom of the window, click the property boxes of the Line Color, Line Type, or Line Width column. Step 2 Select the required properties from the drop-down lists. NOTE

l

The edited display properties of the chart only apply to the real-time monitoring window of the current monitoring task.

l

During the real-time performance monitoring, if data is displayed on the List tab page whereas no chart is displayed on the Chart tab page, you can select one of the following line types by editing the display properties:

l

l

type 1

l

type 2

l

type 3

You can right-click in the real-time monitoring window, choose Set Default Display Mode, select Line or histogram in the Default Display Mode area to change the display mode.

----End

13.7.5 Saving RNC Monitoring Results This describes how to save the monitoring results into local files.

Prerequisite l


l

There is monitoring data reported by the RNC.

l

For the CPU/DSP usage monitoring, the default save path is installation directory\client \output\monitor. The default format of file names is CPU/DSP Reviewyy_mm_dd_hh_mm_ss-task number.mrf.

l

For the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring tasks, the default save path is

Context

13-90


Issue 03 (2009-04-25)

RNC LMT User Guide


installation directory\adaptor\clientadaptor\RNC\LMT software version number \output\realmonitor. The default format of file names is monitoring type_monitoring item_yy-mm-dd-hh-mm-ss.txt. For example, the results of a PCPICH Ec/No and RSCP monitoring task that is started at 15:41:10 on 2005-10-26 are saved under the name Connection performance monitoring_PCPICH EcNo&RSCP_2005-10-26-15-41-10.txt. NOTE

The results of connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring can also be saved in .csv files.

For the CPU/DSP usage monitoring, you can save the monitoring results in either of the following ways:

Procedure l

When creating a monitoring task, click Start Saving in the Add Task dialog box to save the results in real time.

l

After the task is started, right-click in the task information pane in the CPU/DSP Usage pane, and choose Start Save Review Data to save results in real time.

----End

Postrequisite For the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring tasks, the only way for saving monitoring results is to select the Auto Save check box when setting the parameters. The check box is selected by default.

Related Tasks 13.7.10 Browsing RNC Monitoring Results Offline

13.7.6 Pausing and Resuming an RNC Monitoring Task This describes how to pause the connection/cell/link performance monitoring and board resource monitoring tasks and restart them later when needed.

Prerequisite The related monitoring task is started.

Procedure l

To pause a task, right-click in the task information pane, and then choose Stop Task from the shortcut menu.

l

To resume the task, right-click in the task information pane, and then choose Restart Task from the shortcut menu.

----End

Related Tasks 13.7.9 Stopping an RNC Monitoring Task Issue 03 (2009-04-25)


13-91


RNC LMT User Guide

13.7.7 Adding an RNC CPU/DSP Monitoring Task This describes how to add a required CPU/DSP monitoring item to a CPU/DSP usage monitoring task.

Prerequisite l

A real-time CPU/DSP usage monitoring task is started.

l


Procedure Step 1 Right-click in the task information pane in the CPU/DSP Usage window, and choose Add Task from the shortcut menu, as shown in Figure 13-66. Figure 13-66 Adding CPU/DSP usage monitoring tasks

Step 2 In the Add Tasks dialog box, set the information on the CPU/DSP to be monitored. The information includes subrack number and slot number. Step 3 Click Add. The real-time monitoring window displays the results of the new monitoring items. Step 4 Click Close to close the dialog box. ----End

Related Tasks 13.7.8 Deleting an RNC CPU/DSP Monitoring Task

13.7.8 Deleting an RNC CPU/DSP Monitoring Task This describes how to delete an unnecessary CPU/DSP monitoring item from a CPU/DSP usage monitoring task.

Prerequisite

13-92

l


l



Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Step 1 In the task information pane at the bottom of the CPU/DSP Usage monitoring window, select the monitoring task to be deleted. Step 2 Right-click the task to be deleted in the task information pane, and choose Delete Task from the shortcut menu, as shown in Figure 13-67. The Confirmation dialog box is displayed. Figure 13-67 Deleting a CPU/DSP usage monitoring task

Step 3 Click Yes. ----End

Related Tasks 13.7.7 Adding an RNC CPU/DSP Monitoring Task

13.7.9 Stopping an RNC Monitoring Task This describes how to stop a monitoring task when it is no longer needed.

Prerequisite A real-time performance monitoring task is created.

Procedure in the top right corner of the real-time performance monitoring task window to stop Click the task. NOTE

For CPU/DSP usage monitoring, you can also stop a task by deleting it. For details, refer to 13.7.8 Deleting an RNC CPU/DSP Monitoring Task.

----End

13.7.10 Browsing RNC Monitoring Results Offline For the results of the connection/cell/link performance monitoring and board resource monitoring, you can double-click the .txt files in which the results are saved and read the details.

Prerequisite The monitoring results are saved in files. Issue 03 (2009-04-25)


13-93

RNC LMT User Guide


Context You can use the Monitor Viewer to browse offline the results of the CPU/DSP usage monitoring saved in .mrf files to learn the history running situation of the system and locate the faults. The results are saved in the manner specified in Saving RNC Monitoring Results.

Procedure l

Review results of the CPU/DSP usage monitoring. 1.

Select either of the following ways to start the Monitor Viewer: on the toolbar in the Local Maintenance Terminal window.

–

Click

–

Choose Start > All Programs > Huawei Local Maintenance Terminal > Monitor Viewer.

The Open dialog box is displayed, as shown in Figure 13-68. Figure 13-68 Open dialog box

13-94

2.

Open the directory where the results of CPU/DSP usage monitoring are saved. The default save path is installation directory\client\output\monitor. Select a required file that saves the results of CPU/DSP usage monitoring.

3.

Select a file and click Open or double-click the file. The Monitor Viewer window displays the result data in list (as shown in Figure 13-69) or in chart (as shown in Figure 13-70). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 13-69 Displaying monitoring results in a list

Figure 13-70 Displaying monitoring results in a chart

Issue 03 (2009-04-25)


13-95

RNC LMT User Guide


l

4.

Click the List tab or the Chart tab to review the information in different modes.

5.

To review other saved results, choose File > Open. In the Open dialog box, select files to open and then review the information.

To review results of the connection performance monitoring, cell performance monitoring, link performance monitoring, and board resource monitoring, perform the following steps: 1.

Open the file folder that saves the files of monitoring results. The default path for the file folder is installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. To name the files, refer to 13.7.5 Saving RNC Monitoring Results.

2.

Double-click the file to open it.

3.

Review the information.

----End

Related Tasks 13.7.1 Browsing the RNC Monitoring Results Online 13.7.5 Saving RNC Monitoring Results

13.8 Parameter Reference for RNC Real-Time Performance Monitoring This describes the parameters used for each performance monitoring. 13.8.1 Parameter Reference for RNC CPU Usage Monitoring This describes the parameters used for RNC CPU/DSP usage monitoring. 13.8.2 Parameter Reference for Connection Performance Monitoring This describes the parameters for connection performance monitoring. 13.8.3 Parameter Reference for Cell Performance Monitoring This describes the parameters used for cell performance monitoring. 13.8.4 Parameter Reference for Link Performance Monitoring This describes the parameters used for link performance monitoring. 13.8.5 Parameter Reference for Board Resource Monitoring This describes the parameters used for board resource monitoring.

13.8.1 Parameter Reference for RNC CPU Usage Monitoring This describes the parameters used for RNC CPU/DSP usage monitoring.

13-96

Field

Description

Subrack No.

Subrack number of the board to be monitored. Value range: 0 to 5.

Slot No.

Slot number of the board to be monitored. Value range: 0 to 27. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Field

Description

Show line graph or histogram

If this check box is selected, the curve of data variation is displayed on the Chart tab page in real time.

Save Review Data

After a monitoring task is added, click Start Saving to save the monitoring data into the file.

13.8.2 Parameter Reference for Connection Performance Monitoring This describes the parameters for connection performance monitoring. Field

Description

Monitor item

Item to be monitored

Monitor period(s)

Monitoring period. Different monitoring items have different monitoring periods and time units.

IMSI

Matching conditions for the monitoring

Auto Save

If the check box is selected, the monitoring records are automatically saved to the specified path.

Text File Name

Path and name of the automatically saved file

NOTE

The IMSI value can be automatically memorized.

Related Tasks 13.3.1 Monitoring P-CPICH Ec/No and RSCP 13.3.2 Monitoring the SIR Measurement Values of UL RLSs 13.3.3 Monitoring the Enhanced Outer Loop Power Control 13.3.4 Monitoring the SIR Error Values of UL RLSs 13.3.5 Monitoring DL Code TX Power 13.3.6 Monitoring the UE TX Power 13.3.7 Monitoring UL Traffic 13.3.8 Monitoring DL Traffic 13.3.9 Monitoring UL Throughput and Bandwidth 13.3.10 Monitoring DL Throughput and Bandwidth 13.3.11 Monitoring Handover Delay 13.3.12 Monitoring the BLER of the DL Transport Channel 13.3.13 Monitoring the AMR Mode

13.8.3 Parameter Reference for Cell Performance Monitoring This describes the parameters used for cell performance monitoring. Issue 03 (2009-04-25)


13-97


RNC LMT User Guide

Field

Description

Monitor item


Monitor period(s)

Monitoring period. Different monitoring items have different monitoring periods and time units.

Cell ID

ID of the cell to be monitored

Auto Save


Text File Name


NOTE

The Cell ID value can be automatically memorized.

Related Tasks 13.4.1 Monitoring Cell P-CPICH TX Power 13.4.2 Monitoring UL RX Total Wideband Power of a Cell 13.4.3 Monitoring DL Carrier TX Power of a Cell 13.4.4 Monitoring the Number of Cell Users 13.4.5 Monitoring Node Synchronization 13.4.6 Monitoring the UL CAC 13.4.7 Monitoring DL CAC 13.4.8 Monitoring the Number of UL Equivalent Users 13.4.9 Monitoring the Number of DL Equivalent Users 13.4.10 Monitoring the Cell Code Tree 13.4.11 Monitoring the Minimum Required Power of the HS-DSCH 13.4.12 Monitoring the Bit Rate Provided by the HS-DSCH 13.4.13 Monitoring the Bit Rate Provided by the E-DCH 13.4.14 Monitoring UL Throughput of a Cell 13.4.15 Monitoring DL Throughput of a Cell 13.4.16 Monitoring the Cell CE 13.4.17 Monitoring the FDPCH SYMBOL

13.8.4 Parameter Reference for Link Performance Monitoring This describes the parameters used for link performance monitoring.

13-98

Field

Description

Monitor item


Subrack No.

Subrack number of the link to be monitored. Value range: 0 to 5.


Issue 03 (2009-04-25)

RNC LMT User Guide


Field

Description

Slot No.

Slot number of the board whose link is to be monitored. This parameter is valid for only the following monitoring items: IMA Group, UNI Link, FRAC ATM Link, SAAL Link, FE&GE, PPP Link, MLPPP Link, SCTP Link, and IP Path. NOTE For items IMA Group, UNI Link, FRAC ATM Link, FE&GE, PPP Link, MLPPP Group, Port No., and Logic Port, when subrack 0 is selected, slots 20 to 23 are unavailable.

IMA Group No.

Number of the IMA group. This parameter is valid for only the IMA Group monitoring item. You can run LST IMAGRP to query its value.

UNI Link No.

Number of the UNI link. This parameter is valid for only the UNI Link monitoring item. You can run LST UNILNK to query its value.

FRAC Link No.

Number of the fractional ATM link. This parameter is valid for only the FRAC ATM Link monitoring item. You can run LST FRALNK and set Link type to FRAATM to query its value.

SAAL Link No.

Number of the SAAL link. Value range: 0 to 699. This parameter is valid for only the SAAL Link monitoring item. You can run LST SAALLNK to query its value.

IP Address

Local IP address and peer IP address of the IPoA PVC. These parameters are valid for only the IPOA PVC monitoring item. You can run LST IPOAPVC to query their values.

Peer IP address Neighbor Node ID AAL2 PATH ID FE&GE

Number of the FE and GE port. Value range: 0 to 7. These parameters are valid for only the FE&GE monitoring item. You can run DSP ETHPORT to query their values.

PPP Link No.

Number of the PPP link. Value range: 0 to 167. This parameter is valid for only the PPP Link monitoring item. You can run LST PPPLNK to query its value.

MLPPP Group No.

Number of the MLPPP group. Value range: 0 to 63. This parameter is valid for only the MLPPP Group monitoring item. You can run LST MPGRP to query its value.

SCTP Link No.

Number of the SCTP link. Value range: 0 to 599. This parameter is valid for only the SCTP Link monitoring item. You can run LST SCTPLNK to query its value.

Neighbor Node ID

ID of the adjacent node. Value range: 0 to 1999. Number of the IP path. Value range: 0 to 65535. These parameters are valid for only the IP PATH monitoring item. You can run LST IPPATH to query their values.

IP PATH ID

Issue 03 (2009-04-25)

Adjacent node ID and ID of the AAL2 path. These parameters are valid for only the AAL2 PATH monitoring item. You can run LST AAL2PATH to query their values.


13-99

RNC LMT User Guide


Field

Description

Port No.

Number of the logical port. Value range: 0 to 119. This parameter is valid for only the Port No. and Logic Port items.

NodeB ID

Number of the NodeB. Value range: 0 to 65535. This parameter is valid for only the OAM monitoring item. You can run LST NODEB to query its value.

QoS No.

Number of QoS. This parameter is valid only for the QoS monitoring item. The value range is as follows: l

For the FE&GE, PPP, MLPPP, and LGCPORT: 0 to 5.

l

For the UNI, IMAGRP, FRAC-ATM, NCOPT, and VP: 0 to 4.

Auto Save


Text File Name


Related Tasks 13.5.1 Monitoring the IMA Group Traffic 13.5.2 Monitoring the UNI Link Traffic 13.5.3 Monitoring the Fractional ATM Link Traffic 13.5.4 Monitoring the SAAL Link Traffic 13.5.5 Monitoring the IPoA PVC Traffic 13.5.6 Monitoring the AAL2 Path Traffic 13.5.7 Monitoring the FE/GE Traffic 13.5.8 Monitoring the PPP Link Traffic 13.5.9 Monitoring the MLPPP Group Traffic 13.5.10 Monitoring the SCTP Link Traffic 13.5.11 Monitoring the IP Path Traffic 13.5.12 Monitoring the Logical Ports 13.5.13 Monitoring OAM Traffic 13.5.14 Monitoring Bandwidth of Logical Ports

13.8.5 Parameter Reference for Board Resource Monitoring This describes the parameters used for board resource monitoring.

13-100

Field

Description

Monitor item


Monitor period(s)

Select the monitor period. The monitor period and its unit vary with monitor items.


Issue 03 (2009-04-25)

RNC LMT User Guide


Field

Description

Subrack No.

Number of the subrack holding the board to be tested. Value range: 0 to 5.

Slot No.

Number of the slot holding the board to be tested. Value range: 2, 4, 8, 10.

Subsystem No.

Number of the subsystem holding the board to be tested. Value range: 0 to 3.

Auto Save


Text File Name


Related Tasks 13.6 Monitoring the RNC Board Resource

Issue 03 (2009-04-25)


13-101

RNC LMT User Guide

14 Testing RNC Faults

14

Testing RNC Faults

About This Chapter This describes the following concepts of the RNC fault tests: the physical layer test, data link layer test, and other fault tests. 14.1 Testing Faults on the Physical Layer This describes how to test faults at the physical layer, including local E1/T1 loopback test, remote E1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, and SDH loopback test. 14.2 Testing Faults on the Link Layer This describes how to test faults on the link layer. The link layer testing provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrong connection test, NodeB maintenance IPoA test, and Iu-PS IPoA test. 14.3 Testing Other RNC Faults This describes how to test other RNC faults, including the IPC connectivity test, cell common channel test, RFN test, clock test, and board load control test. 14.4 Basic Operations of the RNC Fault Tests This describes how to browse and save the fault testing results and how to stop a fault testing task. 14.5 Parameter Reference for the RNC Fault Tests This describes the parameters used for each RNC fault test.

Issue 03 (2009-04-25)


14-1

RNC LMT User Guide


14.1 Testing Faults on the Physical Layer This describes how to test faults at the physical layer, including local E1/T1 loopback test, remote E1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, and SDH loopback test. 14.1.1 Physical Layer Testing The physical layer testing provides the following tests and queries: local E1/T1 loopback test, remote E1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, SDH loopback test, SDH query, and FE/GE query. 14.1.2 Testing the Local E1/T1 Loopback This describes how to test whether the local E1/T1 link is connected normally. 14.1.3 Testing the Remote E1/T1 Loopback This describes how to test whether the remote E1/T1 link is connected normally. 14.1.4 Testing the E1/T1 BER This describes how to test the BER of the E1/T1 link. 14.1.5 Testing the E1/T1 Loopback This describes how to check whether the E1/T1 loopback exists. 14.1.6 Testing E1/T1 Wrong Connection This describes how to test the E1/T1 wrong connection. 14.1.7 Testing the SDH Loopback This describes how to test whether the SDH link is connected normally. 14.1.8 Querying SDH This describes how to query SDH information including optical port status and performance statistics. 14.1.9 Querying FE/GE This describes how to query the information on FE/GE ports and the Ethernet port status.

14.1.1 Physical Layer Testing The physical layer testing provides the following tests and queries: local E1/T1 loopback test, remote E1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, SDH loopback test, SDH query, and FE/GE query. Table 14-1 describes the items of the physical layer testing. Table 14-1 Items of the physical layer test

14-2

Item

Function

Local E1/T1 loopback

The test is performed to check whether the local E1/T1 link is connected normally.

Remote E1/T1 loopback

The test is performed to check whether the remote E1/T1 link is connected normally.

E1/T1 BER

The test is performed on the BER of the E1/T1 link. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Item

Function

E1/T1 loopback

The test is performed to check whether the E1/T1 loopback exists.

E1/T1 wrong connection

The test is performed on the wrong connection detection function of the tested object, that is, to check whether the E1/T1 wrong connection exists according to the collected RX and TX link information.

SDH loopback

The test is performed to check whether the SDH link is connected normally.

SDH

The test is performed to query the optical port status and performance statistics.

FE/GE

The test is performed to query the Ethernet port status.

14.1.2 Testing the Local E1/T1 Loopback This describes how to test whether the local E1/T1 link is connected normally.

Prerequisite l

The LMT is started.

l


Context

CAUTION l

This fault test may affect services. Do not perform the test on a normal E1/T1 link.

l

This function is applicable to only the AEUa, AOUa, POUa, and PEUa boards.

l

The LMT automatically cancels the loopback when the test is complete.

Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click Local E1/ T1 Loopback Test. Step 2 In the 14.5.1 Parameter Reference for the Local E1/T1 Loopback Test dialog box, set the parameters, and then click OK. The message browse window displays the results and related information in text format. ----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14.4.3 Stopping a Fault Testing Task Issue 03 (2009-04-25)


14-3

RNC LMT User Guide


Related References 14.5.1 Parameter Reference for the Local E1/T1 Loopback Test

14.1.3 Testing the Remote E1/T1 Loopback This describes how to test whether the remote E1/T1 link is connected normally.

Prerequisite l

The LMT is started.

l


Context

CAUTION l

This fault test may affect services. Do not perform the test on a normal E1/T1 link.

l


l

The LMT automatically cancels the loopback when the test is complete.

Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click Remote E1/T1 Loopback Test. Step 2 In the 14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test dialog box, set the parameters, and then click OK. The message browse window displays the results and related information in text format. ----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14.4.3 Stopping a Fault Testing Task

Related References 14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test

14.1.4 Testing the E1/T1 BER This describes how to test the BER of the E1/T1 link.

Prerequisite l

14-4


Issue 03 (2009-04-25)

RNC LMT User Guide

14 Testing RNC Faults l


Context During the BER test, the LMT sends pseudo codes to all timeslots of the specified links. Then it compares the received and sent pseudo codes to obtain the BER. This tool is used to test only the BER severity because it is not a specialized tool for the BER test. Thus the accuracy of testing results is limited. To obtain accurate BER data, use a tool specialized for the BER test.

CAUTION l

Perform this task with caution for it affects current services.

l


l

After the test, you need to cancel the loopback.

l

The LMT automatically stops the BER test when the test is complete.

Procedure Step 1 Before E1/T1 BER Test is started, set remote loopback manually at the peer end or connect the TX end to the RX end by using the loopback equipment. Step 2 In the Fault Test pane, expand the Physical layer tests node, and then double-click E1/T1 BER Test. Step 3 In the 14.5.3 Parameter Reference for the E1/T1 BER Test dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End


Related References 14.5.3 Parameter Reference for the E1/T1 BER Test

14.1.5 Testing the E1/T1 Loopback This describes how to check whether the E1/T1 loopback exists.

Prerequisite l

The LMT is started.

l


Issue 03 (2009-04-25)


14-5

RNC LMT User Guide


Context

CAUTION This function is applicable to only the AEUa, AOUa, POUa, and PEUa boards.

Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click E1/T1 Loopback Test. Step 2 In the 14.5.4 Parameter Reference for the E1/T1 Loopback Test dialog box, set the parameters, and then click OK. The message browse window displays the results and related information in text format. ----End


Related References 14.5.4 Parameter Reference for the E1/T1 Loopback Test

14.1.6 Testing E1/T1 Wrong Connection This describes how to test the E1/T1 wrong connection.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click E1/T1 Wrong Connect Test. Step 2 In the 14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test dialog box, set the parameters, and then click OK. The message browse window displays the results and related information in text format. ----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14-6


Issue 03 (2009-04-25)

RNC LMT User Guide


14.4.3 Stopping a Fault Testing Task

Related References 14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test

14.1.7 Testing the SDH Loopback This describes how to test whether the SDH link is connected normally.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click SDH Loop Test. Step 2 In the 14.5.6 Parameter Reference for the SDH Loopback Test dialog box, set the parameters, and then click OK. The message browse window displays the results and related information in text format. ----End


Related References 14.5.6 Parameter Reference for the SDH Loopback Test

14.1.8 Querying SDH This describes how to query SDH information including optical port status and performance statistics.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click SDH Query. Step 2 In the 14.5.7 Parameter Reference for SDH Query dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End Issue 03 (2009-04-25)


14-7

RNC LMT User Guide



Related References 14.5.7 Parameter Reference for SDH Query

14.1.9 Querying FE/GE This describes how to query the information on FE/GE ports and the Ethernet port status.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click FE/GE Query. Step 2 In the 14.5.8 Parameter Reference for FE/GE Query dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End


Related References 14.5.8 Parameter Reference for FE/GE Query

14.2 Testing Faults on the Link Layer This describes how to test faults on the link layer. The link layer testing provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrong connection test, NodeB maintenance IPoA test, and Iu-PS IPoA test. 14.2.1 Link Layer Testing By performing this task, you can learn about the functions of each link layer test. The link layer testing provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrong connection test, PPP/MLPPP link query, NodeB maintenance IPoA test, Iu-PS IPoA test, and IMA query. 14.2.2 Testing the AAL2 Path This describes how to test the AAL2 path and to report the related data for fault location. 14-8


Issue 03 (2009-04-25)

RNC LMT User Guide


14.2.3 Testing the SAAL Link This describes how to test the SAAL link and to report the related data for fault location. 14.2.4 Testing the SCTP Link This describes how to test the SCTP link and to report the related data for fault location. 14.2.5 Testing PPP/MLPPP Wrong Connection This describes how to test the PPP/MLPPP wrong connection functions and to check whether the terminal description characters between the two link ends are consistent. 14.2.6 Querying an PPP/MLPPP Link This describes how to query the PPP link status, MLPPP group status, and status of the MLPPP links in the MLPPP group. 14.2.7 Testing the NodeB Maintenance IPoA Link This describes how to test the NodeB maintenance IPoA link and to report the related data for fault location. 14.2.8 Testing the Iu-PS IPoA Link This describes how to test the Iu-PS IPoA link and to report the related data for fault location. 14.2.9 Querying IMA The describes how to query the IMA group status and status of the IMA links in the IMA group.

14.2.1 Link Layer Testing By performing this task, you can learn about the functions of each link layer test. The link layer testing provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrong connection test, PPP/MLPPP link query, NodeB maintenance IPoA test, Iu-PS IPoA test, and IMA query. Table 14-2 describes the items of the link layer test. Table 14-2 Items of the link layer test

Issue 03 (2009-04-25)

Item

Function

AAL2 path

The test is performed on the faulty AAL2 link and the related data is reported for fault location and analysis.

SAAL link

The test is performed on the faulty SAAL link and the related data is reported for fault location and analysis.

SCTP link

The test is performed on the SCTP link and the related data is reported for fault location and analysis.

PPP/MLPPP wrong connection

The test is performed on the PPP/MLPPP wrong connection to check whether the terminal description characters between the two link ends are consistent.

PPP/MLPPP link

This describes how to query the PPP link status, MLPPP group status, and status of the MLPPP links in the MLPPP group.

NodeB maintenance IPoA

The test is performed on the NodeB maintenance IPoA link and the related data is reported for fault location and analysis.


14-9

RNC LMT User Guide


Item

Function

Iu-PS IPoA link

The test is performed on the Iu-PS IPoA link and the related data is reported for fault location and analysis.

IMA

The test is performed to query the IMA group status and status of the IMA links in the IMA group.

14.2.2 Testing the AAL2 Path This describes how to test the AAL2 path and to report the related data for fault location.

Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a normal AAL2 path.

Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click AAL2 PATH Test. Step 2 In the 14.5.9 Parameter Reference for the AAL2 Path Test dialog box, set the parameters, and then click OK. NOTE

l

After this task is started, the LMT queries the details of the AAL2 path bearing link (IMA group, UNI, fractional ATM or E1T1/SDH). Then it creates an L2 instance to send and receive data packets. During the test, the LMT collects the traffic statistics of the chips that the AAL2 path passes through. The statistics and the quantities of the data packets received and sent are displayed in the message browse window in text format. Then, the LMT automatically restores itself to the original state, including deleting the L2 instance.

l

If CID loop is selected, you can judge whether the AAL2 path loop is functional by comparing the quantities of received and sent data packets.

----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14.4.3 Stopping a Fault Testing Task 14-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Related References 14.5.9 Parameter Reference for the AAL2 Path Test

14.2.3 Testing the SAAL Link This describes how to test the SAAL link and to report the related data for fault location.

Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a normal SAAL link.

Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click SAAL link test. Step 2 In the 14.5.10 Parameter Reference for SAAL Link Test dialog box, set the parameters, and then click OK. NOTE

After this task is started, the LMT queries the details of the SAAL bearing link (IMA group, UNI, fractional ATM, or E1/T1/SDH), and then collects statistics about the chip traffic passing through the IPoA channel for multiple times. The message browse window displays the collected traffic information on each chip in text format. Then the LMT automatically restores itself to the original state.

----End


Related References 14.5.10 Parameter Reference for SAAL Link Test

14.2.4 Testing the SCTP Link This describes how to test the SCTP link and to report the related data for fault location.

Issue 03 (2009-04-25)


14-11

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a normal SCTP link.

Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click SCTP Link Test. Step 2 In the 14.5.11 Parameter Reference for SCTP Link Test dialog box, set the parameters, and then click OK. NOTE

After this task is started, the LMT queries the details of the SCTP bearing link (IMA group, UNI, fractional ATM, or E1/T1/SDH), and then collects statistics about the chip traffic passing through the IPoA channel for multiple times. The message browse window displays the collected traffic information on each chip in text format. Then the LMT automatically restores itself to the original state.

----End


Related References 14.5.11 Parameter Reference for SCTP Link Test

14.2.5 Testing PPP/MLPPP Wrong Connection This describes how to test the PPP/MLPPP wrong connection functions and to check whether the terminal description characters between the two link ends are consistent.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click PPP/MLPPP Wrong Connect Test. 14-12


Issue 03 (2009-04-25)

RNC LMT User Guide


Step 2 In the 14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End


Related References 14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test

14.2.6 Querying an PPP/MLPPP Link This describes how to query the PPP link status, MLPPP group status, and status of the MLPPP links in the MLPPP group.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click PPP/MLPPP Query. Step 2 In the 14.5.13 Parameter Reference for PPP/MLPPP Query dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End


Related References 14.5.13 Parameter Reference for PPP/MLPPP Query

14.2.7 Testing the NodeB Maintenance IPoA Link This describes how to test the NodeB maintenance IPoA link and to report the related data for fault location.

Issue 03 (2009-04-25)


14-13

RNC LMT User Guide


Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a normal NodeB maintenance IPoA link.

Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click NodeB maintenance IPoA link test. Step 2 In the 14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test dialog box, set the parameters, and then click OK. NOTE

After this task is started, the LMT queries the details of the IPoA bearing link (IMA group, UNI, fractional ATM or E1/T1/SDH), and then collects statistics about the chip traffic passing through the IPoA channel. The message browse window displays the collected traffic information on each chip in text format.

----End


Related References 14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test

14.2.8 Testing the Iu-PS IPoA Link This describes how to test the Iu-PS IPoA link and to report the related data for fault location.

Prerequisite

14-14

l

The LMT is started.

l



Issue 03 (2009-04-25)

RNC LMT User Guide


Context

CAUTION This fault test may affect services. Do not perform the test on a normal Iu-PS IPoA link.

Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click Iu-PS IPoA test. Step 2 In the 14.5.15 Parameter Reference for the Iu-PS IPoA Test dialog box, set the parameters, and then click OK. NOTE

After this task is started, the LMT queries the details of the IPoA bearing link (IMA group, UNI, fractional ATM, or E1/T1/SDH). Then it creates an L2 instance to send and receive data packets. During the test, the LMT collects statistics about the chip traffic passing through the IPoA channel. The message browse window displays the collected traffic information on each chip and the quantities of the data packets received and sent in text format. After the task is complete, the LMT automatically restores itself to the original state, including canceling the TEID loopback and deleting the L2 instance.

----End


Related References 14.5.15 Parameter Reference for the Iu-PS IPoA Test

14.2.9 Querying IMA The describes how to query the IMA group status and status of the IMA links in the IMA group.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click IMA Query. Step 2 In the 14.5.16 Parameter Reference for IMA Query dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End Issue 03 (2009-04-25)


14-15

RNC LMT User Guide



Related References 14.5.16 Parameter Reference for IMA Query

14.3 Testing Other RNC Faults This describes how to test other RNC faults, including the IPC connectivity test, cell common channel test, RFN test, clock test, and board load control test. 14.3.1 Other Tests The RNC provides the following additional tests: the IPC connectivity test, cell common channel test, RFN test, clock test, and board load control test. 14.3.2 Testing IPC Connectivity This describes how to test the IPC connectivity by periodically collecting the statistics about the RX/TX traffic on each port of the IPC node, or collecting traffic statistics and status information on the IPC node. 14.3.3 Testing the Cell Common Channel This describes how to test a faulty common channel of a cell and report the related data to locate the fault. 14.3.4 Testing RFN This describes how to test faulty RNC Frame Numbers (RFNs). The test reports the data related to RFNs of all boards in position except the interface boards in specified subracks to locate the fault. 14.3.5 Testing the Clock This describes how to conduct a test on faulty clocks. All the related data of the clocks of boards in position in the specified subrack is reported for fault location and analysis. 14.3.6 Testing Load Control of a Board This describes how to conduct a test on the board where load control faults occur. The test reports the related data of the specified board with load control faults to locate and analyze the fault.

14.3.1 Other Tests The RNC provides the following additional tests: the IPC connectivity test, cell common channel test, RFN test, clock test, and board load control test. Table 14-3 describes the items of the tests.

14-16


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 14-3 Items of other tests Item

Function

IPC connectivity

The test is performed to periodically collect the statistics about the RX/TX traffic on each port of the IPC node, or to collect traffic statistics and status information on the IPC node. After this task is performed, the IPC connectivity can be tested.

Cell common channel

The test is performed on a faulty common channel of a cell and the related data is reported for fault location and analysis.

RFN

The test is performed on faulty RFNs. The data related to RFNs of all boards in position except the interface boards in specified subracks is reported for fault location and analysis.

Clock

The test is performed on faulty clocks. All the related data of the clocks of boards in position in the specified subrack is reported for fault location and analysis.

Load control of a board

The test is performed on the board where a load control fault occurs. The related data of the specified board with load control faults is reported for fault location and analysis.

14.3.2 Testing IPC Connectivity This describes how to test the IPC connectivity by periodically collecting the statistics about the RX/TX traffic on each port of the IPC node, or collecting traffic statistics and status information on the IPC node.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Other Tests node, and then double-click IPC Test. Step 2 In the 14.5.17 Parameter Reference for the IPC Connectivity Test dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. NOTE

After this task is started, the system periodically collects the statistics about the RX/TX traffic on each port of the IPC node or collects traffic statistics and state messages of the IPC node.

----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14.4.3 Stopping a Fault Testing Task Issue 03 (2009-04-25)


14-17

RNC LMT User Guide


Related References 14.5.17 Parameter Reference for the IPC Connectivity Test

14.3.3 Testing the Cell Common Channel This describes how to test a faulty common channel of a cell and report the related data to locate the fault.

Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a normal cell common channel.

Procedure Step 1 In the Fault Test pane, expand the Other Tests node, and then double-click Cell Common Channel Test. Step 2 In the 14.5.18 Parameter Reference for the Cell Common Channel Test dialog box, set the parameters, and then click OK. NOTE

l

After this task is started, the LMT queries the configuration of this cell. Then it creates an L2 instance to send and receive data packets. During the test, the LMT collects the traffic statistics of the chips that the AAL2 path passes through. The message browse window displays the collected traffic information on each chip and the quantities of the data packets received and sent in text format. Then the LMT automatically restores itself to the original state, including canceling the CID loopback and deleting the L2 instance.

l

If CID Loop is selected, you can judge whether the AAL2 path loop is functional by comparing the quantities of received and transmitted data packets.

----End


Related References 14.5.18 Parameter Reference for the Cell Common Channel Test 14-18


Issue 03 (2009-04-25)

RNC LMT User Guide


14.3.4 Testing RFN This describes how to test faulty RNC Frame Numbers (RFNs). The test reports the data related to RFNs of all boards in position except the interface boards in specified subracks to locate the fault.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Other Tests node, and then double-click RFN Test. Step 2 In the 14.5.19 Parameter Reference for the RFN Test dialog box, set the parameters, and then click OK. NOTE

l

After this task is started, the LMT queries in sequence the related data of RFNs of all boards in position except the interface boards in specified subracks. The message browse window displays the testing results in text format.

l

Only one RBS works as the RFN source subrack in a BSC6810. All the other RBSs work as RFN destination subracks.

----End


Related References 14.5.19 Parameter Reference for the RFN Test

14.3.5 Testing the Clock This describes how to conduct a test on faulty clocks. All the related data of the clocks of boards in position in the specified subrack is reported for fault location and analysis.

Prerequisite l

The LMT is started.

l


Procedure Step 1 In the Fault Test pane, expand the Other Tests node, and then double-click Clock Test. Step 2 In the 14.5.20 Parameter Reference for the Clock Test dialog box, set the parameters, and then click OK. Issue 03 (2009-04-25)


14-19

RNC LMT User Guide

14 Testing RNC Faults NOTE

After the task is started, the LMT queries the related data of the faulty clock on the specified board. The message browse window displays the testing results in text format.

----End


Related References 14.5.20 Parameter Reference for the Clock Test

14.3.6 Testing Load Control of a Board This describes how to conduct a test on the board where load control faults occur. The test reports the related data of the specified board with load control faults to locate and analyze the fault.

Prerequisite l

The LMT is started.

l


Context

CAUTION This fault test may affect services. Do not perform the test on a successfully-loaded board.

Procedure Step 1 In the Fault Test pane, expand the Other Tests node, and then double-click Load Control Test of The Boards. Step 2 In the 14.5.21 Parameter Reference for the Load Control Test of the Boards dialog box, set the parameters, and then click OK. The message browse window displays the testing results in text format. ----End

Related Tasks 14.4.1 Browsing Fault Testing Results 14.4.2 Manually Saving Fault Testing Results 14.4.3 Stopping a Fault Testing Task 14-20


Issue 03 (2009-04-25)

RNC LMT User Guide


Related References 14.5.21 Parameter Reference for the Load Control Test of the Boards

14.4 Basic Operations of the RNC Fault Tests This describes how to browse and save the fault testing results and how to stop a fault testing task. 14.4.1 Browsing Fault Testing Results This describes how to browse fault testing results displayed in text format in the Fault Test window. By performing this task, you can browse the testing results and locate the fault. 14.4.2 Manually Saving Fault Testing Results This describes how to manually save the results of a fault testing task. 14.4.3 Stopping a Fault Testing Task This describes how to stop a fault testing task.

14.4.1 Browsing Fault Testing Results This describes how to browse fault testing results displayed in text format in the Fault Test window. By performing this task, you can browse the testing results and locate the fault.

Prerequisite l


l

A related test item is successfully started.

Procedure Browse the fault testing results in the Fault Test window. ----End

14.4.2 Manually Saving Fault Testing Results This describes how to manually save the results of a fault testing task.

Prerequisite l


l

There are testing results reported by the system.

Procedure Step 1 Right-click the Fault Test pane, and choose Save from the shortcut menu. The Save dialog box is displayed, as shown in Figure 14-1.

Issue 03 (2009-04-25)


14-21

RNC LMT User Guide


Figure 14-1 Saving testing results

Step 2 Specify a path for saving the file, and set a file name. The default save path is installation directory\adaptor\clientadaptor\RNC\LMT software version number\output. Step 3 Click Save to save the results as a .txt file. ----End

14.4.3 Stopping a Fault Testing Task This describes how to stop a fault testing task.

Prerequisite A fault testing task of the test item is started.

Procedure Click

in the top right corner of the fault testing task window to stop the task.

----End

14.5 Parameter Reference for the RNC Fault Tests This describes the parameters used for each RNC fault test. 14.5.1 Parameter Reference for the Local E1/T1 Loopback Test This describes the parameters used for the local E1/T1 loopback test. 14-22


Issue 03 (2009-04-25)

RNC LMT User Guide


14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test This describes the parameters used for the remote E1/T1 loopback test. 14.5.3 Parameter Reference for the E1/T1 BER Test This describes the parameters used for the E1/T1 BER test. 14.5.4 Parameter Reference for the E1/T1 Loopback Test This describes the parameters for the E1/T1 loopback test. 14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test This describes the parameters used for the E1/T1 wrong connection test. 14.5.6 Parameter Reference for the SDH Loopback Test This describes the parameters for the SDH loopback test. 14.5.7 Parameter Reference for SDH Query This describes the parameters used for SDH query. 14.5.8 Parameter Reference for FE/GE Query This describes the parameters used for FE/GE query. 14.5.9 Parameter Reference for the AAL2 Path Test This describes the parameters used for the AAL2 path test. 14.5.10 Parameter Reference for SAAL Link Test This describes the parameters used for the SAAL link test. 14.5.11 Parameter Reference for SCTP Link Test This describes the parameters for the SCTP link test. 14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test This describes the parameters used for the PPP/MLPPP wrong connection test. 14.5.13 Parameter Reference for PPP/MLPPP Query This describes the parameters for PPP/MLPPP query. 14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test This describes the parameters for the NodeB maintenance IPoA test. 14.5.15 Parameter Reference for the Iu-PS IPoA Test This describes the parameters used for the Iu-PS IPoA test. 14.5.16 Parameter Reference for IMA Query This describes the parameters used for IMA query. 14.5.17 Parameter Reference for the IPC Connectivity Test This describes the parameters used for the IPC connectivity test. 14.5.18 Parameter Reference for the Cell Common Channel Test This describes the parameters used for the cell common channel test. 14.5.19 Parameter Reference for the RFN Test This describes the parameters used for the RFN test. 14.5.20 Parameter Reference for the Clock Test This describes the parameters used for the clock test. 14.5.21 Parameter Reference for the Load Control Test of the Boards This describes the parameters used for the load control test of the boards.

Issue 03 (2009-04-25)


14-23

RNC LMT User Guide


14.5.1 Parameter Reference for the Local E1/T1 Loopback Test This describes the parameters used for the local E1/T1 loopback test. Table 14-4 Parameters for the local E1/T1 loopback test Field

Description

Subrack No.

Number of the subrack to be tested. Value range: 0 to 5.

Slot No.

Number of the slot to be tested Only the number of the slot that holds an interface board is required. Value range: 14 to 27.

Port type

Type of port to be tested. The port can be an AEUa/PEUa electrical port or the AOUa optical port.

Link No.

Number of the link to be tested l

For the AEUa/PEUa electrical port, the parameter value ranges from 0 to 31.

l

For the AOUa/POUa optical port, the parameter value ranges from 0 to 167.

CAUTION The OMUa does not support the local E1/T1 loopback test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.2 Testing the Local E1/T1 Loopback

14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test This describes the parameters used for the remote E1/T1 loopback test. Table 14-5 Parameters for the remote E1/T1 loopback test

14-24

Field

Description

Subrack No.


Slot No.

Number of the slot to be tested. Value range: 14 to 27.

Port type

Type of port to be tested. The port can be the AEUa/PEUa electrical port or the AOUa optical port.


Issue 03 (2009-04-25)

RNC LMT User Guide


Field

Description

Link No.

Number of the link to be tested l


l


CAUTION The OMUa does not support the remote E1/T1 loopback test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.3 Testing the Remote E1/T1 Loopback

14.5.3 Parameter Reference for the E1/T1 BER Test This describes the parameters used for the E1/T1 BER test. Table 14-6 Parameters for the E1/T1 BER test Field

Description

Subrack No.


Slot No.


Port type

Type of port to be tested. The port can be an AEUa/PEUa electrical port or the AOUa optical port.

Link No.

Number of the link to be tested

Unit time[ms]

l


l


Unit time of the BER test l

For the AEUa/PEUa electrical port, the value range is 300 to 1000 and the recommended value is 1000.

l

For the AOUa/POUa optical port, the value is permanently set 1000.

CAUTION The OMUa does not support the E1/T1 BER test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Issue 03 (2009-04-25)


14-25

RNC LMT User Guide


Related Tasks 14.1.4 Testing the E1/T1 BER

14.5.4 Parameter Reference for the E1/T1 Loopback Test This describes the parameters for the E1/T1 loopback test. Table 14-7 Parameters for the E1/T1 loopback test Field

Description

Subrack No.


Slot No.


Detect single

To check whether loopback exists on a E1/T1 link, select Detect single. The link number is required.

Detect all

To check whether loopback exists on all the links, select Detect all. The link number is not required.

Link No.

Number of the link to be tested. Value range: 0 to 167. It is valid only when Detect single is selected.

CAUTION The OMUa does not support the E1/T1 loopback test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.5 Testing the E1/T1 Loopback

14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test This describes the parameters used for the E1/T1 wrong connection test. Table 14-8 Parameters for the E1/T1 wrong connection test Field

Description

Subrack No.


Slot No.


Link No.

Number of the link to be tested. Value range: 0 to 167.

CAUTION The OMUa does not support the E1/T1 wrong connection test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

14-26


Issue 03 (2009-04-25)

RNC LMT User Guide


Related Tasks 14.1.6 Testing E1/T1 Wrong Connection

14.5.6 Parameter Reference for the SDH Loopback Test This describes the parameters for the SDH loopback test. Table 14-9 Parameters for the SDH loopback test Field

Description

Subrack No.


Slot No.

Number of the slot to be tested The slot only holds an interface board. Value range: 14 to 27.

Port No.

Number of port to be tested. Value range: 0 to 3.

Test Interval

By default, the test interval is 1,000 ms.

Loopback Type

Type of the SDH loopback. Value range: Local Loop, Remote Loop.

CAUTION The OMUa does not support the SDH loopback test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.7 Testing the SDH Loopback

14.5.7 Parameter Reference for SDH Query This describes the parameters used for SDH query. Table 14-10 Parameters for SDH query

Issue 03 (2009-04-25)

Field

Description

Subrack No.

Number of the subrack where the optical port is located. Value range: 0 to 5.

Slot No.

Number of the slot where the optical port is located. Value range: 14 to 27.

Board Type

Type of the board where the optical port is located. Value range: AOUa/POUa, UOIa.


14-27

RNC LMT User Guide


Field

Description

Port No.

l

When the board type is AOUa/POUa, the port number is 0 or 1.

l

When the board type is UOIa, the port number is 0 or 7.

l

When the performance type is GROUP, the optical port status and performance statistics are displayed.

l

When the performance type is LINK, the link status and performance statistics are displayed.

l

When the multiplexed link on the optical port is an E1 link, the link number ranges from 0 to 62.

l

When the multiplexed link on the optical port is a T1 link, the link number ranges from 0 to 83.

Performance Type

Link No.

CAUTION The OMUa does not support SDH query. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.8 Querying SDH

14.5.8 Parameter Reference for FE/GE Query This describes the parameters used for FE/GE query. Table 14-11 Parameters for FE/GE query

14-28

Field

Description

Subrack No.

Number of the subrack where the FG2a/GOUa board is located. Value range: 0 to 5.

Slot No.

Number of the slot where the FG2a/GOUa board is located. Value range: 14 to 27.

Board Type

Type of the board where the Ethernet port is located. Value range: FG2a, GOUa.

Port No.

l

When the board type is FG2a, the port number ranges from 0 to 7.

l

When the board type is GOUa, the port number is 0 or 1.


Issue 03 (2009-04-25)

RNC LMT User Guide


CAUTION The OMUa does not support FE/GE query. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.1.9 Querying FE/GE

14.5.9 Parameter Reference for the AAL2 Path Test This describes the parameters used for the AAL2 path test. Table 14-12 Parameters for the AAL2 path test Field

Description

Adjacent node ID

ID of the AAL2 adjacent node. Value range: 0 to 1999.

AAL2PATH ID

ID of the AAL2 path between two AAL2 nodes The IDs of the same AAL2 path configured at two adjacent nodes must be the same and must not be 0. Value range: 1 to 4294967295.

test interval

Duration for the L2 instance established for the test to continuously send data packets. Value range: 30 to 3600. Unit: second.

Test Packet Size

Size of the data packets sent by the L2 instance established for the test. Value range: 40 to 1500. Unit: byte.

Test Source Speed

Rate of the data packets sent by the L2 instance established for the test. Value range: 8 to 2048. Unit: bit/s.

Setting loopback

Value range: No Loop, CID Loop, PIU Loop

NOTE

You can query Adjacent node ID and AAL2PATH ID by running LST AAL2PATH.

Related Tasks 14.2.2 Testing the AAL2 Path

14.5.10 Parameter Reference for SAAL Link Test This describes the parameters used for the SAAL link test. Table 14-13 Parameters for the SAAL link test

Issue 03 (2009-04-25)

Field

Description

Subrack No.

Number of the subrack terminating the SAAL link. Value range: 0 to 5. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

14-29

RNC LMT User Guide


Field

Description

Slot No.

Number of the slot terminating the SAAL link. Value range: 0, 2, 4, 8, 10.

Subsystem No.

Number of the subsystem terminating the SAAL link. Value range: 0 to 3.

SAAL Link No.

Number of the SAAL link in the subsystem. Value range: 0 to 699.

Setting loopback

Value range: No Loop, PIU Loop

NOTE

You can query all the parameters mentioned previously by running the LST SAALLNK command.

Related Tasks 14.2.3 Testing the SAAL Link

14.5.11 Parameter Reference for SCTP Link Test This describes the parameters for the SCTP link test. Table 14-14 Parameters for the SCTP link test Field

Description

Subrack No.


Slot No.

Number of the slot to be tested. Value range: 0, 2, 4, 8, 10.

Subsystem No.

Number of the subsystem to be tested. Value range: 0 to 3.

SCTP Link No.

Number of the SCTP link to be tested. Value range: 0 to 599.

Setting loopback

Value range: No Loop, PIU Loop

NOTE

All the parameters mentioned previously can be queried through the LST SCTPLNK command.

Related Tasks 14.2.4 Testing the SCTP Link

14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test This describes the parameters used for the PPP/MLPPP wrong connection test.

14-30


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 14-15 Parameters for the PPP/MLPPP wrong connection test Field

Description

Subrack No.


Slot No.


MLPPP link No.

Number of the link to be tested. Value range: 0 to 127.

CAUTION The OMUa does not support the PPP/MLPPP wrong connection test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.2.5 Testing PPP/MLPPP Wrong Connection

14.5.13 Parameter Reference for PPP/MLPPP Query This describes the parameters for PPP/MLPPP query. Table 14-16 Parameters for PPP/MLPPP Query Field

Description

Subrack No.

Number of the subrack where the PPP link or MLPPP group to be queried is located. Value range: 0 to 5.

Slot No.

Number of the slot where the PPP link or MLPPP group to be queried is located. Value range: 14 to 27.

Query Type

This parameter specifies which to query, a PPP link or an MLPPP group. Value range: PPPLINK, MLPPPGROUP.

PPPLINK No./ MLPPPGROUP No.

When the query type is PPPLINK, the number of the PPP link or the MLPPP group ranges from 0 to 127. When the query type is MLPPPGROUP, the number of the PPP link or the MLPPP group ranges from 0 to 127.

CAUTION The OMUa does not support PPP/MLPPP query. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.2.6 Querying an PPP/MLPPP Link Issue 03 (2009-04-25)


14-31

RNC LMT User Guide


14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test This describes the parameters for the NodeB maintenance IPoA test. Table 14-17 Parameters for the NodeB maintenance IPoA test Field

Description

IPoA client address

Local IP address

Peer IP address

IP address of the peer end

NOTE

You can query all the parameters mentioned previously by running LST IPOAPVC.

Related Tasks 14.2.7 Testing the NodeB Maintenance IPoA Link

14.5.15 Parameter Reference for the Iu-PS IPoA Test This describes the parameters used for the Iu-PS IPoA test. Table 14-18 Parameters for the Iu-PS IPoA test Field

Description

IPoA client address

Local IP address

Peer IP address

IP address of the peer end

Subrack No.

Number of an RNC subrack. Number of an RNC subrack where the DSP runs properly. Value range: 0 to 5.

DPU No.

Number of a DPU slot where the DSP runs properly. Value range: 8 to 19.

DSP No.

To select a properly running DSP. Value range: 0 to 21.

Test Interval


Test Packet Size

Size of the data packets sent by an L2 instance established for the test. Value range: 40 to 1500. Unit: byte.

Test Source Speed

Rate of the data packets sent by an L2 instance established for the test. Value range: 8 to 2048. Unit: bit/s.

NOTE

You can query IPoA client address and Peer IP address by running LST IPOAPVC.

Related Tasks 14.2.8 Testing the Iu-PS IPoA Link 14-32


Issue 03 (2009-04-25)

RNC LMT User Guide


14.5.16 Parameter Reference for IMA Query This describes the parameters used for IMA query. Table 14-19 Parameters for IMA query Field

Description

Subrack No.

Number of the subrack where the IMA link group to be queried is located. Value range: 0 to 5.

Slot No.

Number of the slot where the IMA link group to be queried is located. Value range: 14 to 27.

IMA Group No.

Number of the IMA link group to be queried. Value range: 0 to 83.

CAUTION The OMUa does not support IMA query. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.2.9 Querying IMA

14.5.17 Parameter Reference for the IPC Connectivity Test This describes the parameters used for the IPC connectivity test. Table 14-20 Parameters for the IPC connectivity test Field

Description

IPC low subrack info.

IPC high subrack info.

Issue 03 (2009-04-25)

Subrack No.

Number of the subrack containing the IPC low subrack information to be tested. Value range: 0 to 5.

Slot No.

Number of the slot containing the IPC low subrack information to be tested. Value range: 0, 2, 4, 8,10.

Subsystem No.

Number of the subsystem containing the IPC low subrack information to be tested. Value range: 0 to 3.

Subrack No.

Number of the subrack containing the IPC high subrack information to be tested. Value range: 0 to 5.

Slot No.

Number of the slot containing the IPC high subrack information to be tested. Value range: 0 to 27.

Subsystem No.

Number of the subsystem containing the IPC high subrack information to be tested. Value range: 0 to 21.


14-33

RNC LMT User Guide


CAUTION During the IP high subrack information test, if subrack 0 is selected, slots 20 to 23 are unavailable.

Related Tasks 14.3.2 Testing IPC Connectivity

14.5.18 Parameter Reference for the Cell Common Channel Test This describes the parameters used for the cell common channel test. Table 14-21 Parameters for the cell common channel test Field

Description

Cell ID

ID of a cell. Value range: 0 to 65535.

Cell Name

Name of a cell

Test Interval


Transport Channel ID

ID of the FACH transport channel. Value range: 0 to 255.

Setting loopback

Value range: No Loop, CID Loop, PIU Loop

NOTE

You can query Transport Channel ID by running DSP CELL.

Related Tasks 14.3.3 Testing the Cell Common Channel

14.5.19 Parameter Reference for the RFN Test This describes the parameters used for the RFN test. Table 14-22 Parameters for the RFN test

14-34

Field

Description

RFN Destination Subrack No.

Number of the RFN Destination subrack. Value range: 0 to 5.

Slot No.


Subsystem No.



Issue 03 (2009-04-25)

RNC LMT User Guide


CAUTION The OMUa does not support the RFN test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.3.4 Testing RFN

14.5.20 Parameter Reference for the Clock Test This describes the parameters used for the clock test. Table 14-23 Parameters for the clock test Field

Description

Subrack No.


Slot No.


Subsystem No.


CAUTION The OMUa does not support the clock test. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.3.5 Testing the Clock

14.5.21 Parameter Reference for the Load Control Test of the Boards This describes the parameters used for the load control test of the boards. Table 14-24 Parameters for the load control test of the boards

Issue 03 (2009-04-25)

Field

Description

Subrack No.


Slot No.


Subsystem No.



14-35

RNC LMT User Guide


CAUTION The OMUa does not support the load control test of boards. Therefore, slots 20 to 23 are unavailable when subrack 0 is selected.

Related Tasks 14.3.6 Testing Load Control of a Board

14-36


Issue 03 (2009-04-25)

RNC LMT User Guide

15 Using the RNC LMT Performance Browser Tool

15

Using the RNC LMT Performance Browser Tool

About This Chapter This describes how to start, configure, and exit the RNC LMT Performance Browser Tool. 15.1 Starting the RNC LMT Performance Browser Tool This describes how to start the Performance Browser Tool to browse the performance measurement results which are stored in the RNC. 15.2 Setting the Parameters of the RNC LMT Performance Browser Tool This describes how to set the parameters of the RNC LMT Performance Browser Tool, including setting the measurement description file and the FTP. 15.3 Browsing Description Files This describes how to browse the measurement description files. 15.4 Downloading Performance Measurement Results This describes how to log in to the BAM through FTP and download the performance measurement results. The Performance Browser Tool provides two ways for FTP download: manual mode and automatic mode. 15.5 Querying Performance Measurement Data This describes how to browse the files (in .mrf or .xml format) of performance measurement results in the local computer. 15.6 Filtering Performance Measurement Data This describes how to set the time, objects, counters, and conditions to filter performance measurement data. You can filter the data based on different combination of the filtering requirements. 15.7 Exporting Performance Measurement Data This describes how to export the files of the queried performance measurement data and save the files in the local computer in .csv format. 15.8 Exiting the RNC LMT Performance Browser Tool This describes how to exit the Performance Browser Tool when the browse is complete.

Issue 03 (2009-04-25)


15-1


RNC LMT User Guide

15.1 Starting the RNC LMT Performance Browser Tool This describes how to start the Performance Browser Tool to browse the performance measurement results which are stored in the RNC.

Prerequisite The LMT application is successfully installed.

Procedure On the LMT PC, choose Start > All Programs > HUAWEI Local Maintenance Terminal > Performance Browser Tool to start the tool. ----End

15.2 Setting the Parameters of the RNC LMT Performance Browser Tool This describes how to set the parameters of the RNC LMT Performance Browser Tool, including setting the measurement description file and the FTP.

Prerequisite The Performance Browser Tool is started.

Procedure Step 1 When you start the Performance Browser Tool for the first time, the Select Net dialog box is displayed, as shown in Figure 15-1. Figure 15-1 Select Net dialog box

Click in the displayed dialog box. The Net Configure dialog box is displayed, as shown in Figure 15-2. 15-2


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 15-2 Net Configure dialog box

Table 15-1 describes the parameters. Table 15-1 Parameters in the Net Configure dialog box Name

Description

Net Name

The name of the FTP server. It must consist of 1 to 32 characters.

User

The user name used to log in to the FTP server.

Password

The password used to log in to the FTP server.

IP Address

External virtual IP address of the BAM.

Server Path

The FTP server directory that stores the performance measurement data. The default directory is the root directory of the FTP server. For downloading the performance measurement data later, you are advised to set the directory to /BAM active workspace installation directory/FTP/ MeasResult.

FTP Configuration Test

Issue 03 (2009-04-25)

To test if the parameters in the FTP Config area are configured successfully, click this button. If the configuration is successful, a Test Succeed! message is displayed on the left area. Otherwise, a Test Failed! message is displayed.


15-3

RNC LMT User Guide


Name

Description

Local Result

The directory under which the measurement data downloaded from the FTP server is saved on the local computer. The default directory is LMT installation directory/adaptor/clientadaptor/pfbTool/data. You can set the local destination directory for storing the measurement data downloaded from the server by clicking

Target File

.

To obtain the performance item file, use either of the following methods: l

Click , and select MeasDefinitions.xml in the directory LMT installation directory/adaptor/clientadaptor/RNC/product version/ mml/en_US.

l

Log in to the FTP client, download product version +MeasDefinitions.xml in the directory /BAM active workspace installation directory/FTP/MeasDefinition, and then click the file.

Address List

to select

Address list of FTP servers. Server names must be unique in the list.

Step 2 Set the parameters in the Configure Parameters dialog box. Step 3 Click OK to complete the configuration. Step 4 Click Close to end the operation. ----End

15.3 Browsing Description Files This describes how to browse the measurement description files.

Prerequisite l

You have successfully logged in to the Performance Browser Tool.

l

The parameters of the description files are correctly configured.

Procedure Step 1 In the Performance Browser Tool window, choose System > Browse Description File or click the icon

15-4

. The Browse Description File window is displayed, as shown in Figure 15-3.


Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 15-3 Browsing description files

Step 2 Select the node of the information to be browsed in the left pane. Step 3 Check the details in the right pane MeasDefinitions Detail, as shown in Figure 15-4. Figure 15-4 Checking details

Issue 03 (2009-04-25)


15-5


RNC LMT User Guide

----End

15.4 Downloading Performance Measurement Results This describes how to log in to the BAM through FTP and download the performance measurement results. The Performance Browser Tool provides two ways for FTP download: manual mode and automatic mode.

Prerequisite The parameters of the FTP server are set correctly.

Procedure l

In manual mode 1.

Choose File > Download Measurement Results. The Download Measurement Results dialog box is displayed, as shown in Figure 15-5.

Figure 15-5 Downloading the measurement results

l

2.

Select the file in the FTP Server Directory pane.

3.

Click Download. The Local Directory pane displays the directory under which the downloaded data is stored.

In automatic mode 1.

15-6

Choose System > Auto Download Settings. The Auto Download Settings dialog box is displayed, as shown in Figure 15-6. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Figure 15-6 Auto Download Settings dialog box

2.

Click Add. In the Add dialog box, select one check box under Download Flag to add an automatic download setting, as shown in Figure 15-7. Figure 15-7 Add dialog box

3.

Select the time to start downloading files from a drop-down list under Download Time.

4.

Click OK. The LMT returns to the Auto Download Settings dialog box and displays the download list in sequence of time.

5.

Click OK.

----End

15.5 Querying Performance Measurement Data This describes how to browse the files (in .mrf or .xml format) of performance measurement results in the local computer.

Issue 03 (2009-04-25)


15-7


RNC LMT User Guide

Prerequisite l

The parameters of the FTP server are set correctly.

l

The measurement results are successfully downloaded and stored in the local computer.

Procedure Step 1 In the Performance Browser Tool window, choose System > Query Performance Results. The Query Performance Results dialog box is displayed, as shown in Figure 15-8. Figure 15-8 Querying performance measurement results

Step 2 In the Query Performance Results dialog box, click the Counters Information tab to set counters and click the Time Information tab to set time. Step 3 Click Query to query the performance data. ----End

15.6 Filtering Performance Measurement Data This describes how to set the time, objects, counters, and conditions to filter performance measurement data. You can filter the data based on different combination of the filtering requirements.

Prerequisite The query of performance measurement data is successfully performed and the queried data is available. 15-8


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Step 1 Right-click the imported data table and choose Filter Results from the shortcut menu. Step 2 Set filtering requirements in the displayed Filter Results dialog box, as shown in Figure 15-9. Figure 15-9 Filtering results

Step 3 Click OK to filter the data and refresh the data table. ----End

15.7 Exporting Performance Measurement Data This describes how to export the files of the queried performance measurement data and save the files in the local computer in .csv format.

Prerequisite l

You have successfully logged in to the Performance Browser Tool.

l

The query of performance measurement data is successfully performed and the queried data is available.

Issue 03 (2009-04-25)


15-9

15 Using the RNC LMT Performance Browser Tool l

RNC LMT User Guide

The log file is imported.

Procedure Step 1 Right-click the imported data table and choose Export Data from the shortcut menu. Step 2 In the Save dialog box, set the file name and the directory for saving the data, as shown in Figure 15-10. Figure 15-10 Save dialog box

Step 3 Click Save to save the exported data. ----End

15.8 Exiting the RNC LMT Performance Browser Tool This describes how to exit the Performance Browser Tool when the browse is complete.

Prerequisite The Performance Browser Tool is successfully started.

Context To exit the Performance Browser Tool, you can select either of the following ways:

15-10


Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure l

Choose System > Exit.

l

Click

in the upper right corner of the window.

----End

Issue 03 (2009-04-25)


15-11

RNC LMT User Guide

16 Using the FTP Client of the RNC LMT

16

Using the FTP Client of the RNC LMT

About This Chapter This describes how to use the FTP Client of the RNC LMT. By performing this task, you can use and exit the FTP Client. You can also set and query the encryption mode of the FTP server. 16.1 Logging in to the FTP Server on the LMT FTP Client This describes how to log in to the RNC FTP server on the LMT FTP Client in encryption mode or plaintext mode. 16.2 Uploading Data Files to the RNC FTP Server This describes how to upload data files to the RNC FTP server. By performing this task, you can use the FTP Client to upload data files to the RNC FTP server after the FTP Client connects to the FTP server. 16.3 Downloading Data Files from the RNC FTP Server This describes how to download data files from the RNC FTP server. By performing this task, you can use the FTP Client to download data files from the RNC FTP server after the FTP Client connects to the FTP server. 16.4 Setting the Encryption Mode of the RNC FTP Server This describes how to set the encryption mode of the RNC FTP server. After the setting, you must log in to the LMT FTP Client in the active encryption mode. 16.5 Querying the Encryption Mode of the RNC FTP Server This describes how to query the encryption mode of the RNC FTP server. By performing this task, you can learn about the active encryption mode of the RNC FTP server. 16.6 Disconnecting the LMT FTP Client from the RNC FTP Server This describes how to disconnect the LMT FTP Client from the RNC FTP server.

Issue 03 (2009-04-25)


16-1


RNC LMT User Guide

16.1 Logging in to the FTP Server on the LMT FTP Client This describes how to log in to the RNC FTP server on the LMT FTP Client in encryption mode or plaintext mode.

Prerequisite l

The communication between the LMT and the BAM is functional.

l

The following data is obtained: the external IP address of the BAM active workspace, valid user name and password of the FTP server.

Procedure Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The FTP Client is started, as shown in Figure 16-1. Figure 16-1 Main interface of the FTP Client

Step 2 Enter the external IP address of the BAM active workspace in the Server box, and then enter the user name and password of the RNC FTP server in the User and Password boxes. Step 3 Select a encryption policy. For implementation methods of different encryption policies, refer to Table 16-1.

16-2


Issue 03 (2009-04-25)

RNC LMT User Guide


Table 16-1 Implementation method of encryption Encryption Policy

Implementation Method

Encryption

Only data channel encrypted

Select SSL and CCC.

Data channel encryption and command channel encryption

Select only SSL.

Non-encryption

Step 4 Click

-

or choose System > Connect to connect the RNC FTP server.

If...

Then...

The connection fails

A fault message is displayed. Check whether the server IP address, user name, and password are valid. Go to Step 2.

The connection is successful

The Connection tips pane displays Successfully log onto server.

----End

16.2 Uploading Data Files to the RNC FTP Server This describes how to upload data files to the RNC FTP server. By performing this task, you can use the FTP Client to upload data files to the RNC FTP server after the FTP Client connects to the FTP server.

Prerequisite The LMT FTP Client is started and you have logged in to the RNC FTP server.

Context You can select different encryption policies to upload files to the RNC FTP server. If you choose to upload files in encryption mode, you must log in to the FTP server. For details, refer to 16.1 Logging in to the FTP Server on the LMT FTP Client.

Procedure Step 1 Select the file in the Local File List pane to upload it to the FTP server. Step 2 In the Server List pane, select the destination directory on the RNC FTP server for storing the uploaded file. Step 3 Upload a file by using either of the following methods: l

Click

l

Double-click the file.

Issue 03 (2009-04-25)

.


16-3

16 Using the FTP Client of the RNC LMT l

RNC LMT User Guide

Choose Transfer > Upload To Server. NOTE

After the file is uploaded, the Connection tips pane displays a message, showing that the uploading is successful. The uploaded file is displayed in the Server List pane.

----End

16.3 Downloading Data Files from the RNC FTP Server This describes how to download data files from the RNC FTP server. By performing this task, you can use the FTP Client to download data files from the RNC FTP server after the FTP Client connects to the FTP server.

Prerequisite The LMT FTP Client is started and you have logged in to the RNC FTP server.

Context You can select different encryption policies to download files from the RNC FTP server. If you choose to download files in encryption mode, you must log in to the RNC FTP server. For details, refer to 16.1 Logging in to the FTP Server on the LMT FTP Client.

Procedure Step 1 Select the file in the Server List pane to download it from the RNC FTP server. Step 2 In the Local Folder List pane, select the destination directory for storing the downloaded file. Step 3 Download a file by using either of the following methods: .

l

Click

l

Double-click the file.

l

Choose Transfer > Download From Server. NOTE

After the file is downloaded, the Connection tips pane displays a message, showing that the downloading is successful. The downloaded file is displayed in the Local File List pane.

----End

16.4 Setting the Encryption Mode of the RNC FTP Server This describes how to set the encryption mode of the RNC FTP server. After the setting, you must log in to the LMT FTP Client in the active encryption mode.

Prerequisite

16-4

l

The LMT is started.

l

You have logged in to the RNC as admin or an ADMINISTRATOR-level operator. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

RNC LMT User Guide


Procedure Run the SET FTPSSRV command on the MML client to set the active encryption mode of the RNC FTP server. NOTE

l

After the setting is successful, the RNC FTP server needs to be restarted to validate the new encryption mode.

l

If the encryption mode of the RNC FTP server is set to forcible encryption, the connection may incur a fault when you log in to the RNC FTP server in plaintext mode.

----End

16.5 Querying the Encryption Mode of the RNC FTP Server This describes how to query the encryption mode of the RNC FTP server. By performing this task, you can learn about the active encryption mode of the RNC FTP server.


Procedure Run the LST FTPSSRV command on the MML client to query the active encryption mode of the RNC FTP server. ----End

16.6 Disconnecting the LMT FTP Client from the RNC FTP Server This describes how to disconnect the LMT FTP Client from the RNC FTP server.

Prerequisite The LMT FTP Client is disconnected from the RNC FTP server.

Procedure Step 1 On the toolbar of the LMT FTP Client, use either of the following methods: .

l

Click

l

On the LMT FTP Client, choose System > Disconnect.

Step 2 After a message is displayed, asking that Are you sure to disconnect, click Yes. Step 3 The Connection tips pane displays a message, indicating that the disconnection is complete.

Issue 03 (2009-04-25)


16-5


RNC LMT User Guide

NOTE

After the FTP Client is disconnected from the RNC FTP server, you can only browse local files. You cannot perform other system function operations, including deleting local files, browsing or deleting files on the server, and uploading or downloading files.

----End

16-6


Issue 03 (2009-04-25)

huawei LMT guide

Recommend Documents