huawei LMT guide

RNC

V200R011

LMT User Guide

Issue 03

Date 2009-04-25

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People'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 writtenconsent 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. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Changes in RNC LMT User Guide.........................................................................................1-1

2 Introduction to the RNC LMT.................................................................................................2-12.1 Definitions of the LMT...................................................................................................................................2-22.2 Functions of the RNC LMT............................................................................................................................2-22.3 RNC OM Networking.....................................................................................................................................2-22.4 Computer Requirements of the LMT..............................................................................................................2-3

3 Components of the RNC LMT.................................................................................................3-13.1 Local Maintenance Terminal of RNC.............................................................................................................3-33.2 FTP Client of RNC LMT................................................................................................................................3-53.3 Trace Viewer of RNC LMT............................................................................................................................3-63.4 Monitor Viewer of RNC LMT........................................................................................................................3-73.5 Performance Browser Tool of RNC LMT......................................................................................................3-93.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-15.1 Setting the IP Address of the RNC LMT PC..................................................................................................5-35.2 Connecting the RNC LMT to the BAM..........................................................................................................5-55.3 Starting the Local Maintenance Terminal of the RNC....................................................................................5-65.4 Setting the Properties of the RNC Local Maintenance Terminal....................................................................5-95.5 Configuring the Identity Certificate..............................................................................................................5-105.6 Setting the Office Information on the RNC LMT.........................................................................................5-125.7 Locking the Local Maintenance Terminal of the RNC.................................................................................5-165.8 Unlocking the Local Maintenance Terminal of the RNC.............................................................................5-175.9 Exiting the Local Maintenance Terminal of the RNC..................................................................................5-17

6 Running RNC MML Commands............................................................................................6-16.1 Concepts of RNC MML Commands...............................................................................................................6-3

6.1.1 Introduction to RNC MML Commands.................................................................................................6-36.1.2 Introduction to the RNC MML Client....................................................................................................6-56.1.3 Policies for RNC Configuration Failure Handling.................................................................................6-66.1.4 RNC Data Configuration Right Management........................................................................................6-7

RNCLMT User Guide Contents

Issue 03 (2009-04-25) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

6.1.5 RNC Data Configuration Rollback........................................................................................................6-76.2 Starting the RNC MML Client........................................................................................................................6-86.3 Viewing the Ownership of RNC Data Configuration Right...........................................................................6-86.4 Obtaining the RNC Data Configuration Right................................................................................................6-96.5 Running a Single MML Command...............................................................................................................6-106.6 Batch Running MML Commands.................................................................................................................6-116.7 Undoing a Single RNC Data Configuration Action......................................................................................6-136.8 Redoing a Single RNC Data Configuration Action......................................................................................6-146.9 Undoing Multiple RNC Data Configuration Actions...................................................................................6-146.10 Redoing Multiple RNC Data Configuration Actions..................................................................................6-15

7 Managing Authorities for RNC Operations......................................................................... 7-17.1 Concepts of RNC Authority Management......................................................................................................7-2

7.1.1 Principles of RNC Authority Management............................................................................................7-27.1.2 RNC LMT Operator Password ..............................................................................................................7-27.1.3 RNC Command Groups.........................................................................................................................7-37.1.4 RNC LMT User Types...........................................................................................................................7-47.1.5 RNC LMT Operator Authorities............................................................................................................7-47.1.6 RNC LMT Operating Time Limits........................................................................................................7-5

7.2 Managing RNC LMT Operator Accounts.......................................................................................................7-67.2.1 Adding an RNC LMT External Operator Account................................................................................7-67.2.2 Modifying the Properties of an RNC LMT External Operator Account................................................7-87.2.3 Deleting an RNC LMT External Operator Account..............................................................................7-9

7.3 Managing RNC LMT Operator Passwords...................................................................................................7-107.3.1 Defining Policies for RNC LMT Login Passwords.............................................................................7-117.3.2 Querying Policies for RNC LMT Login Passwords............................................................................7-127.3.3 Changing the Password of the Active RNC LMT Operator Account..................................................7-127.3.4 Changing the Password of an RNC LMT External Operator Account................................................7-13

7.4 Managing RNC Command Groups...............................................................................................................7-147.4.1 Querying RNC Command Groups.......................................................................................................7-147.4.2 Renaming an RNC Command Group...................................................................................................7-147.4.3 Changing Commands in an RNC Command Group............................................................................7-15

8 Managing the RNC License..................................................................................................... 8-18.1 Basic Concepts of the RNC License...............................................................................................................8-2

8.1.1 License File............................................................................................................................................8-28.1.2 License Control for Multiple Operators.................................................................................................8-38.1.3 License Validation Mechanism..............................................................................................................8-5

8.2 Activating the RNC License...........................................................................................................................8-78.2.1 Obtaining ESN Information from the RNC...........................................................................................8-78.2.2 Uploading the RNC License File to the BAM.......................................................................................8-88.2.3 Checking RNC Basic Information and Operator Information...............................................................8-98.2.4 Activating and Verifying the RNC License.........................................................................................8-10

8.3 Reallocating the RNC License......................................................................................................................8-11

ContentsRNC

LMT User Guide

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

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

9 Managing RNC Alarms.............................................................................................................9-19.1 Concepts of RNC Alarm Management...........................................................................................................9-2

9.1.1 RNC Alarm Type...................................................................................................................................9-29.1.2 RNC Alarm Level..................................................................................................................................9-39.1.3 RNC Event Alarm Types.......................................................................................................................9-39.1.4 RNC Alarm Box.....................................................................................................................................9-4

9.2 Setting RNC Alarm Logs................................................................................................................................9-49.2.1 Setting the Capacity and Time Limit of an RNC Alarm Log................................................................9-59.2.2 Querying the Capacity and Time Limit of an RNC Alarm Log.............................................................9-5

9.3 Masking RNC Alarms.....................................................................................................................................9-59.3.1 Adding an RNC Alarm Shield...............................................................................................................9-69.3.2 Deleting an RNC Alarm Shield..............................................................................................................9-69.3.3 Querying RNC Alarm Shields................................................................................................................9-7

9.4 Masking RNC Derived Alarms.......................................................................................................................9-79.4.1 Setting the Mask Level of an RNC Derived Alarm...............................................................................9-89.4.2 Querying the Mask Level of an RNC Derived Alarm............................................................................9-8

9.5 Monitoring RNC Alarms.................................................................................................................................9-89.5.1 Setting the Properties of the Alarm Browse Window............................................................................9-99.5.2 Setting the Properties of RNC Fault Alarm Sounds.............................................................................9-109.5.3 Browsing Alarms..................................................................................................................................9-119.5.4 Querying RNC Alarm Logs.................................................................................................................9-129.5.5 Querying RNC Alarm Handling Suggestions......................................................................................9-149.5.6 Manually Setting a Cleared RNC Alarm..............................................................................................9-169.5.7 Saving the Information on an RNC Alarm...........................................................................................9-169.5.8 Setting the Preferences for Printing RNC Alarms in Real Time..........................................................9-179.5.9 Manually Printing RNC Alarms...........................................................................................................9-18

9.6 Managing the Convert Management System................................................................................................9-199.6.1 Starting the RNC Convert Management System..................................................................................9-209.6.2 Setting the Parameters of the RNC Convert Management System......................................................9-209.6.3 Saving the Information in the Output Window....................................................................................9-219.6.4 Exiting the RNC Convert Management System..................................................................................9-22

9.7 Operating the RNC Alarm Box.....................................................................................................................9-229.7.1 Connecting the RNC Alarm Box to the RNC LMT.............................................................................9-239.7.2 Resetting the RNC Alarm Box.............................................................................................................9-249.7.3 Stopping an RNC Alarm Sound...........................................................................................................9-259.7.4 Manually Turning Off an RNC Alarm Light.......................................................................................9-269.7.5 Querying the Version of the RNC Alarm Box.....................................................................................9-279.7.6 Querying the State of an RNC Alarm Light.........................................................................................9-279.7.7 Setting the Shield Severity of the RNC Alarm Box.............................................................................9-289.7.8 Querying the Mask Level of the RNC Alarm Box...............................................................................9-28

10 Managing RNC Logs.............................................................................................................10-1



iii

10.1 Concepts of RNC Log Management...........................................................................................................10-310.1.1 RNC Log Types.................................................................................................................................10-310.1.2 RNC Log Management Authority......................................................................................................10-3

10.2 Setting the Time and Count Limits of the RNC Log..................................................................................10-310.3 Querying the Time and Count Limits of the RNC Log...............................................................................10-410.4 Querying an RNC Operation Log...............................................................................................................10-410.5 Exporting an RNC Operation Log..............................................................................................................10-510.6 Querying RNC Security Logs.....................................................................................................................10-610.7 Exporting an RNC Security Log.................................................................................................................10-710.8 Exporting an RNC Running Log.................................................................................................................10-810.9 Collecting Fault Log Information...............................................................................................................10-9

11 Managing the RNC Equipment by Using the Device Panel and Display Panel.......11-111.1 Using the RNC Device Panel......................................................................................................................11-2

11.1.1 Introduction to the RNC Device Panel...............................................................................................11-211.1.2 Starting the RNC Device Panel..........................................................................................................11-311.1.3 Showing or Hiding the Legend on the RNC Device Panel................................................................11-411.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel..........................................................11-611.1.5 Browsing the Status of an RNC Board...............................................................................................11-711.1.6 Querying the Detailed Status of an RNC Board................................................................................11-811.1.7 Querying the CPU/DSP Usage of an RNC Board..............................................................................11-9

11.2 Using the RNC Display Panel...................................................................................................................11-1011.2.1 Introduction to the RNC Display Panel............................................................................................11-1111.2.2 Starting the RNC Display Panel.......................................................................................................11-1211.2.3 Querying the Status of FE Ports on an RNC Board.........................................................................11-1311.2.4 Querying the Status of GE Ports on an RNC Board........................................................................11-1411.2.5 Querying the Detailed Status of a DSP on the DPUb Board...........................................................11-1511.2.6 Querying the Detailed Status of an E1/T1 Link...............................................................................11-1611.2.7 Querying Alarms through a Board Alarm Light..............................................................................11-17

11.3 Viewing Active Alarms of an RNC Board................................................................................................11-1711.4 Querying the Configuration Mode of a Subrack.......................................................................................11-18

12 Tracing and Viewing RNC Messages................................................................................12-112.1 Concepts of RNC Message Tracing Management......................................................................................12-4

12.1.1 Functions of RNC Message Tracing Management............................................................................12-412.1.2 Working Principles of RNC Message Tracing Management.............................................................12-412.1.3 Authority of RNC Message Tracing Management............................................................................12-5

12.2 Tracing Iu Interface Messages....................................................................................................................12-612.3 Tracing Iur Interface Messages...................................................................................................................12-912.4 Tracing Iub Interface Messages................................................................................................................12-1212.5 Tracing Uu Interface Messages.................................................................................................................12-1412.6 Tracing UE Messages................................................................................................................................12-1712.7 Tracing IOS Messages..............................................................................................................................12-2012.8 Tracing Cell Messages..............................................................................................................................12-21

ContentsRNC

LMT User Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

12.9 Tracing REDIRECT Messages.................................................................................................................12-2212.10 Tracing MNCDT Messages....................................................................................................................12-25

12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells.................................................12-2612.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells.................................................12-2712.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells..........................................................12-28

12.11 Tracing OS Messages..............................................................................................................................12-2912.12 Tracing SCCP Messages.........................................................................................................................12-3012.13 Tracing MTP3 Messages.........................................................................................................................12-3212.14 Tracing QAAL2 Messages......................................................................................................................12-3512.15 Tracing SAAL Messages........................................................................................................................12-3612.16 Tracing SCTP Messages.........................................................................................................................12-3812.17 Tracing M3UA Messages........................................................................................................................12-4112.18 Tracing Location Messages.....................................................................................................................12-4212.19 Basic Operations of RNC Message Tracing...........................................................................................12-43

12.19.1 Browsing an RNC Traced Message Online...................................................................................12-4412.19.2 Querying the Properties of the Tracing Task.................................................................................12-4512.19.3 Viewing a Message Translation.....................................................................................................12-4612.19.4 Saving an RNC Traced Message....................................................................................................12-4612.19.5 Pausing an RNC Tracing Task.......................................................................................................12-4812.19.6 Resuming an RNC Tracing Task...................................................................................................12-4812.19.7 Closing an RNC Tracing Task.......................................................................................................12-4912.19.8 Browsing an RNC Traced Message Offline...................................................................................12-5012.19.9 Managing All Tracing Tasks..........................................................................................................12-53

12.20 Parameter Reference for RNC Message Tracing and Viewing...............................................................12-5412.20.1 Parameter Reference for Iu Interface Tracing................................................................................12-5412.20.2 Parameter Reference for Iur Interface Tracing...............................................................................12-5612.20.3 Parameter Reference for Iub Interface Tracing..............................................................................12-5712.20.4 Parameter Reference for Uu Interface Tracing..............................................................................12-5912.20.5 Parameter Reference for UE Tracing.............................................................................................12-5912.20.6 Parameter Reference for IOS Tracing............................................................................................12-6012.20.7 Parameter Reference for Cell Tracing............................................................................................12-6112.20.8 Parameter Reference for REDIRECT Tracing...............................................................................12-6212.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing.........................................................12-6212.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing.......................................................12-6312.20.11 Parameter Reference for Inter-RAT MNCDT Tracing................................................................12-6412.20.12 Parameter Reference for OS Tracing...........................................................................................12-6512.20.13 Paramter Reference for Location Reporting Control...................................................................12-66

13 RNC Real-Time Performance Monitoring........................................................................13-113.1 Concepts of RNC Real-Time Performance Monitoring..............................................................................13-3

13.1.1 Introduction to RNC Real-Time Performance Monitoring................................................................13-313.1.2 Working Principles of RNC Real-Time Performance Monitoring....................................................13-313.1.3 Authority of the RNC Real-Time Performance Monitoring..............................................................13-5



v

13.2 Monitoring the RNC CPU/DSP Occupancy...............................................................................................13-513.3 Monitoring the RNC Connection Performance...........................................................................................13-8

13.3.1 Monitoring P-CPICH Ec/No and RSCP...........................................................................................13-1013.3.2 Monitoring the SIR Measurement Values of UL RLSs...................................................................13-1213.3.3 Monitoring the Enhanced Outer Loop Power Control.....................................................................13-1413.3.4 Monitoring the SIR Error Values of UL RLSs................................................................................13-1613.3.5 Monitoring DL Code TX Power......................................................................................................13-1713.3.6 Monitoring the UE TX Power..........................................................................................................13-1913.3.7 Monitoring UL Traffic.....................................................................................................................13-2013.3.8 Monitoring DL Traffic.....................................................................................................................13-2213.3.9 Monitoring UL Throughput and Bandwidth....................................................................................13-2413.3.10 Monitoring DL Throughput and Bandwidth..................................................................................13-2513.3.11 Monitoring Handover Delay..........................................................................................................13-2713.3.12 Monitoring the BLER of the DL Transport Channel.....................................................................13-2813.3.13 Monitoring the AMR Mode...........................................................................................................13-30

13.4 Monitoring the RNC Cell Performance....................................................................................................13-3113.4.1 Monitoring Cell P-CPICH TX Power..............................................................................................13-3313.4.2 Monitoring UL RX Total Wideband Power of a Cell......................................................................13-3513.4.3 Monitoring DL Carrier TX Power of a Cell.....................................................................................13-3713.4.4 Monitoring the Number of Cell Users..............................................................................................13-3913.4.5 Monitoring Node Synchronization...................................................................................................13-4013.4.6 Monitoring the UL CAC..................................................................................................................13-4213.4.7 Monitoring DL CAC........................................................................................................................13-4413.4.8 Monitoring the Number of UL Equivalent Users.............................................................................13-4513.4.9 Monitoring the Number of DL Equivalent Users.............................................................................13-4713.4.10 Monitoring the Cell Code Tree......................................................................................................13-4813.4.11 Monitoring the Minimum Required Power of the HS-DSCH........................................................13-5013.4.12 Monitoring the Bit Rate Provided by the HS-DSCH.....................................................................13-5113.4.13 Monitoring the Bit Rate Provided by the E-DCH..........................................................................13-5213.4.14 Monitoring UL Throughput of a Cell.............................................................................................13-5413.4.15 Monitoring DL Throughput of a Cell.............................................................................................13-5513.4.16 Monitoring the Cell CE..................................................................................................................13-5613.4.17 Monitoring the FDPCH SYMBOL................................................................................................13-58

13.5 Monitoring the RNC Link Performance....................................................................................................13-5913.5.1 Monitoring the IMA Group Traffic..................................................................................................13-6013.5.2 Monitoring the UNI Link Traffic.....................................................................................................13-6213.5.3 Monitoring the Fractional ATM Link Traffic..................................................................................13-6413.5.4 Monitoring the SAAL Link Traffic..................................................................................................13-6613.5.5 Monitoring the IPoA PVC Traffic...................................................................................................13-6713.5.6 Monitoring the AAL2 Path Traffic..................................................................................................13-6913.5.7 Monitoring the FE/GE Traffic..........................................................................................................13-7113.5.8 Monitoring the PPP Link Traffic.....................................................................................................13-73

ContentsRNC

LMT User Guide

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

13.5.9 Monitoring the MLPPP Group Traffic.............................................................................................13-7513.5.10 Monitoring the SCTP Link Traffic.................................................................................................13-7613.5.11 Monitoring the IP Path Traffic.......................................................................................................13-7813.5.12 Monitoring the Logical Ports.........................................................................................................13-8013.5.13 Monitoring OAM Traffic...............................................................................................................13-8213.5.14 Monitoring Bandwidth of Logical Ports........................................................................................13-83

13.6 Monitoring the RNC Board Resource.......................................................................................................13-8413.7 Basic RNC Real-Time Performance Monitoring Operations....................................................................13-87

13.7.1 Browsing the RNC Monitoring Results Online...............................................................................13-8713.7.2 Switching the Display Mode............................................................................................................13-8813.7.3 Setting the Default Display Mode....................................................................................................13-8913.7.4 Editing the Display Mode for the Chart...........................................................................................13-9013.7.5 Saving RNC Monitoring Results......................................................................................................13-9013.7.6 Pausing and Resuming an RNC Monitoring Task...........................................................................13-9113.7.7 Adding an RNC CPU/DSP Monitoring Task...................................................................................13-9213.7.8 Deleting an RNC CPU/DSP Monitoring Task.................................................................................13-9213.7.9 Stopping an RNC Monitoring Task.................................................................................................13-9313.7.10 Browsing RNC Monitoring Results Offline...................................................................................13-93

13.8 Parameter Reference for RNC Real-Time Performance Monitoring........................................................13-9613.8.1 Parameter Reference for RNC CPU Usage Monitoring...................................................................13-9613.8.2 Parameter Reference for Connection Performance Monitoring.......................................................13-9713.8.3 Parameter Reference for Cell Performance Monitoring...................................................................13-9713.8.4 Parameter Reference for Link Performance Monitoring..................................................................13-9813.8.5 Parameter Reference for Board Resource Monitoring...................................................................13-100

14 Testing RNC Faults................................................................................................................14-114.1 Testing Faults on the Physical Layer..........................................................................................................14-2

14.1.1 Physical Layer Testing.......................................................................................................................14-214.1.2 Testing the Local E1/T1 Loopback....................................................................................................14-314.1.3 Testing the Remote E1/T1 Loopback.................................................................................................14-414.1.4 Testing the E1/T1 BER......................................................................................................................14-414.1.5 Testing the E1/T1 Loopback..............................................................................................................14-514.1.6 Testing E1/T1 Wrong Connection.....................................................................................................14-614.1.7 Testing the SDH Loopback................................................................................................................14-714.1.8 Querying SDH....................................................................................................................................14-714.1.9 Querying FE/GE.................................................................................................................................14-8

14.2 Testing Faults on the Link Layer................................................................................................................14-814.2.1 Link Layer Testing.............................................................................................................................14-914.2.2 Testing the AAL2 Path.....................................................................................................................14-1014.2.3 Testing the SAAL Link....................................................................................................................14-1114.2.4 Testing the SCTP Link.....................................................................................................................14-1114.2.5 Testing PPP/MLPPP Wrong Connection.........................................................................................14-1214.2.6 Querying an PPP/MLPPP Link........................................................................................................14-13



vii

14.2.7 Testing the NodeB Maintenance IPoA Link....................................................................................14-1314.2.8 Testing the Iu-PS IPoA Link............................................................................................................14-1414.2.9 Querying IMA..................................................................................................................................14-15

14.3 Testing Other RNC Faults.........................................................................................................................14-1614.3.1 Other Tests.......................................................................................................................................14-1614.3.2 Testing IPC Connectivity.................................................................................................................14-1714.3.3 Testing the Cell Common Channel..................................................................................................14-1814.3.4 Testing RFN.....................................................................................................................................14-1914.3.5 Testing the Clock.............................................................................................................................14-1914.3.6 Testing Load Control of a Board......................................................................................................14-20

14.4 Basic Operations of the RNC Fault Tests.................................................................................................14-2114.4.1 Browsing Fault Testing Results.......................................................................................................14-2114.4.2 Manually Saving Fault Testing Results...........................................................................................14-2114.4.3 Stopping a Fault Testing Task..........................................................................................................14-22

14.5 Parameter Reference for the RNC Fault Tests..........................................................................................14-2214.5.1 Parameter Reference for the Local E1/T1 Loopback Test...............................................................14-2414.5.2 Parameter Reference for the Remote E1/T1 Loopback Test............................................................14-2414.5.3 Parameter Reference for the E1/T1 BER Test.................................................................................14-2514.5.4 Parameter Reference for the E1/T1 Loopback Test.........................................................................14-2614.5.5 Parameter Reference for the E1/T1 Wrong Connection Test...........................................................14-2614.5.6 Parameter Reference for the SDH Loopback Test...........................................................................14-2714.5.7 Parameter Reference for SDH Query...............................................................................................14-2714.5.8 Parameter Reference for FE/GE Query............................................................................................14-2814.5.9 Parameter Reference for the AAL2 Path Test..................................................................................14-2914.5.10 Parameter Reference for SAAL Link Test.....................................................................................14-2914.5.11 Parameter Reference for SCTP Link Test......................................................................................14-3014.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test..............................................14-3014.5.13 Parameter Reference for PPP/MLPPP Query................................................................................14-3114.5.14 Parameter Reference for the NodeB Maintenance IPoA Test........................................................14-3214.5.15 Parameter Reference for the Iu-PS IPoA Test................................................................................14-3214.5.16 Parameter Reference for IMA Query.............................................................................................14-3314.5.17 Parameter Reference for the IPC Connectivity Test......................................................................14-3314.5.18 Parameter Reference for the Cell Common Channel Test.............................................................14-3414.5.19 Parameter Reference for the RFN Test..........................................................................................14-3414.5.20 Parameter Reference for the Clock Test.........................................................................................14-3514.5.21 Parameter Reference for the Load Control Test of the Boards......................................................14-35

15 Using the RNC LMT Performance Browser Tool............................................................15-115.1 Starting the RNC LMT Performance Browser Tool...................................................................................15-215.2 Setting the Parameters of the RNC LMT Performance Browser Tool........................................................15-215.3 Browsing Description Files.........................................................................................................................15-415.4 Downloading Performance Measurement Results......................................................................................15-615.5 Querying Performance Measurement Data.................................................................................................15-7

ContentsRNC

LMT User Guide

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

15.6 Filtering Performance Measurement Data..................................................................................................15-815.7 Exporting Performance Measurement Data................................................................................................15-915.8 Exiting the RNC LMT Performance Browser Tool..................................................................................15-10

16 Using the FTP Client of the RNC LMT..............................................................................16-116.1 Logging in to the FTP Server on the LMT FTP Client...............................................................................16-216.2 Uploading Data Files to the RNC FTP Server............................................................................................16-316.3 Downloading Data Files from the RNC FTP Server...................................................................................16-416.4 Setting the Encryption Mode of the RNC FTP Server................................................................................16-416.5 Querying the Encryption Mode of the RNC FTP Server............................................................................16-516.6 Disconnecting the LMT FTP Client from the RNC FTP Server.................................................................16-5



ix

Figures

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

RNCLMT User Guide Figures


xi

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

FiguresRNC

LMT User Guide

xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

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



xiii

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

FiguresRNC

LMT User Guide

xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

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



xv

Tables

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

RNCLMT User Guide Tables


xvii

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

TablesRNC

LMT User Guide

xviii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

About This Document

Purpose

This document describes the installation, functions, and interfaces of the RNC LocalMaintenance 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 operatingsystem, 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 maintenanceterminal, FTP client, trace viewer, monitor viewer, performance browser tool, and convertmanagement system.

4 Installing the RNC LMT Application

RNCLMT User Guide About This Document


1

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

5 Getting Started with the RNC LMT

This describes how to start, configure, use, and quit the LMT application. When running theLMT 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 performcomprehensive 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 authoritiesfor the RNC operations is to manage the operator accounts, operator passwords, and RNCcommand groups.

8 Managing the RNC License

This describes how to manage the RNC license, for example, activate and reallocate the RNClicense, check the quantity of current RNC operators, the traffic on the RNC, or the alarms relatedto the RNC license.

9 Managing RNC Alarms

This describes how to manage RNC alarms. It helps analyze the alarm, locate, and rectify thefaults.

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, boardlinks, 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 implementedthrough 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 linklayer 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 canuse and exit the FTP Client. You can also set and query the encryption mode of the FTP server.

About This DocumentRNC

LMT User Guide

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

ConventionsSymbol 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 notavoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided,could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant 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 inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


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 byvertical bars. One item is selected.

RNCLMT User Guide About This Document


3


[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical 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.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare 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 meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.

About This DocumentRNC

LMT User Guide

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

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

The following table describes the changes in each part.

Parts Changes

14.5.1 Parameter Referencefor the Local E1/T1Loopback Test14.5.2 Parameter Referencefor the Remote E1/T1Loopback Test14.5.3 Parameter Referencefor the E1/T1 BER Test14.5.7 Parameter Referencefor SDH Query14.5.8 Parameter Referencefor FE/GE Query

The name of some boards are modified: FG2 is changed toFG2a, GOU is changed to GOUa, AOU is changed toAOUa, and POU is changed to POUa.The name of UOI board is modified: UOI_ATM/UOI_IP ischanged to UOIa.

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

The following table describes the changes in each part.

RNCLMT User Guide 1 Changes in RNC LMT User Guide


1-1

Parts Changes

12.6 Tracing UE Messages The figure of tracing UE Messages is optimized.

12.5 Tracing Uu InterfaceMessages

Some language mistakes of tracing Uu Interface Messagesare 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 changesdescribed in the following table.

Parts Changes

Obtaining the RNC Data ConfigurationRight

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

Obtaining the RNC Data ConfigurationRight

The switch of the data configuration right ismodified in prerequisites.

1 Changes in RNC LMT User GuideRNC

LMT User Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2009-04-25)

Parts Changes

Tracing Messages of Missed Intra-Frequency Neighboring CellsTracing Messages of Missed Inter-Frequency Neighboring CellsTracing Messages of Missed Inter-RATNeighboring Cells

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

Introduction to the RNC MML Client The History Command pane in the GUI ischanged to the Operation Record pane.

Batch Running MML Commands The description of the syntax analysis in theprocess of batch running is added.

Checking RNC Basic Information andOperator Information

The figures of the MML command GUIs arereplaced.

License Control for Multiple Operators Three optional functions that can becontrolled by the primary operator is added.The figures of the license activation GUIs arereplaced.

Tracing Iu Interface MessagesTracing Iur Interface MessagesTracing Iub Interface Messages

The context information, figures of input andoutput GUIs, procedures, and postrequisiteinformation are modified.

Tracing Uu Interface MessagesTracing IOS Messages

The context information, figures of the inputand output GUIs, and postrequisiteinformation are modified.

Tracing Cell Messages The context information, figures of the inputand output GUIs, procedures, andpostrequisite 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 MessagesTracing MTP3 MessagesTracing QAAL2 MessagesTracing SAAL MessagesTracing SCTP MessagesTracing M3UA Messages

The figures of the input and output GUIs arechanged.

Parameter Reference for RNC MessageTracing and ViewingParameter Reference for RNC Real-TimePerformance MonitoringParameter Reference for the RNC FaultTests

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

RNCLMT User Guide 1 Changes in RNC LMT User Guide


1-3

Parts Changes

Parameter Reference for Iu InterfaceTracingParameter Reference for Iur InterfaceTracingParameter Reference for Iub InterfaceTracingParameter Reference for Uu InterfaceTracingParameter Reference for IOS TracingParameter Reference for Cell TracingParameter Reference for OS Tracing

The descriptions of some parameters aremodified.

1 Changes in RNC LMT User GuideRNC

LMT User Guide


Issue 03 (2009-04-25)

2 Introduction to the RNC LMT

About This Chapter

This describes the definition and functions of the LMT, the topology of the RNC operatingsystem, and the computer configuration requirements for LMT installation.

2.1 Definitions of the LMTWhen 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 LMTThe RNC OM system functions in client/server mode. The LMT acts as a client, and the BackAdministration Module (BAM) acts as the server.

2.3 RNC OM NetworkingThe RNC OM networking provides operation and maintenance for the RNC and NodeB.

2.4 Computer Requirements of the LMTThe computer requirements are categorized into the following: hardware requirements, softwarerequirements, and communication capability requirements.

RNCLMT User Guide 2 Introduction to the RNC LMT


2-1

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

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

LMT PCThe LMT PC is the hardware of the LMT. It refers to the computer to be installed with the LMTapplication.

LMT ApplicationThe LMT application refers to the Huawei proprietary application, the Huawei LocalMaintenance Terminal software group, which is installed on the LMT PC.

2.2 Functions of the RNC LMTThe RNC OM system functions in client/server mode. The LMT acts as a client, and the BackAdministration Module (BAM) acts as the server.

The LMT communicates with the BAM through a Local Area Network (LAN) or a Wide AreaNetwork (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 MMLcommands, query execution results, trace messages, query alarms, and collect performancestatistics.

2.3 RNC OM NetworkingThe RNC OM networking provides operation and maintenance for the RNC and NodeB.

Figure 2-1 shows the RNC OM networking.

2 Introduction to the RNC LMTRNC

LMT User Guide


Issue 03 (2009-04-25)

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 theOM network. The RNC-NodeB OM channel is configurable. Through the OM channel, remotemaintenance of the NodeB can be performed on the Network Management System (NMS),M2000, or NodeB LMT.

2.4 Computer Requirements of the LMTThe computer requirements are categorized into the following: hardware requirements, softwarerequirements, and communication capability requirements.

Hardware RequirementsTable 2-1 lists the hardware requirements for the computer on which the LMT application willbe installed.

Table 2-1 Hardware requirements

Item Quantity RecommendedConfiguration

MinimumConfiguration

CPU 1 2.8 GHz or above 866 MHz

RAM 1 512 MB 256 MB

Hard disk 1 80 GB 10 GB

Display adapterresolution

- 1024 by 768 pixels orabove

800 x 600

RNCLMT User Guide 2 Introduction to the RNC LMT


2-3

Item Quantity RecommendedConfiguration

MinimumConfiguration

CD-ROM drive 1 - -

Ethernet adapter 1 10 Mbit/s or 100 Mbit/s 10 Mbit/s or 100 Mbit/s

Others 5 x 1 Keyboard, mouse,modem, audio adapter,sound box

-

Software RequirementsTable 2-2 lists the software requirements for the computer on which the LMT application willbe installed.

Table 2-2 Software requirements

Item Recommended Configuration

Operating system Microsoft Windows XP Professional

Default language of theoperating system

English (United States)

Web browser Microsoft Internet Explorer 5.5 or later

WARNINGTo guarantee stable system operation, the LMT application should be installed on a computerwith the recommended configurations.

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

2 Introduction to the RNC LMTRNC

LMT User Guide


Issue 03 (2009-04-25)

3 Components of the RNC LMT

About This Chapter

This describes the following software components of the RNC LMT: the local maintenanceterminal, FTP client, trace viewer, monitor viewer, performance browser tool, and convertmanagement system.

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

3.2 FTP Client of RNC LMTThe FTP Client is an FTP tool for the LMT application. It enables the LMT to communicatewith the FTP server through the FTP protocol.

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

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

3.5 Performance Browser Tool of RNC LMTThrough the Performance Browser Tool, you can browse the performance measurement resultssaved on the NE directly at the NE side. You can also manually import the NE measurementfiles, and then export and browse the performance measurement results for facilitating viewingand arranging the performance files.

3.6 Convert Management System of RNC LMT

RNCLMT User Guide 3 Components of the RNC LMT


3-1

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

3 Components of the RNC LMTRNC

LMT User Guide


Issue 03 (2009-04-25)

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

InterfaceFigure 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

Number

Field Description

1 Menu bar Displays menus for system operation.

2 Toolbar Provides shortcut icons for system operation.



3-3

Number

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 inthe navigation tree pane.

5 Status bar Displays the name of the current user, the connection status, andthe virtual external IP address of the BAM server.

Online HelpThe 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

LocalMaintenanceTerminal systemhelp

This help provides:l Meanings of the fields in

dialog boxesl Function descriptions and

operation guidelines of theLocal Maintenance Terminal

l Detailed information onboards

l Detailed information onalarms

l Terms and abbreviations

In the Local Maintenance Terminalwindow,l press F1 or choose Help > Help

Topics.l when a dialog box is displayed in

the window, press F1 to displaythe help information for thisdialog box.

MML help This help provides the followinginformation for each MMLcommand:l Function

l Note

l Parameter

l Example

l Output description (only forquery commands)

Input a command on the MMLclient, and press Enter. The HelpInformation window displays thehelp information about thiscommand.


LMT User Guide


Issue 03 (2009-04-25)

3.2 FTP Client of RNC LMTThe FTP Client is an FTP tool for the LMT application. It enables the LMT to communicatewith 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

Number Field Description

1 Menu bar Provides menus for system operation.


3 Local directory listpane

Displays directories that are in use.

4 Server file list pane Displays the files and folders in the connected FTPserver.

5 Local file list pane Displays the files and folders in the chosen directory.



3-5


6 Connection tip pane Displays the operation information and the status ofthe connection with the FTP server.

7 Server entry bar Includes the server name, user name, password, portnumber, and mode.

Online HelpTable 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 thedata management, the filemanagement, and the transferfunctions of the FTP Client

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

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

InterfaceFigure 3-3 shows the main interface of the Trace Viewer.

Figure 3-3 Main interface of the Trace Viewer


LMT User Guide


Issue 03 (2009-04-25)

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

Table 3-5 Main interface of the Trace Viewer




3 Message browsewindow

Displays contents of .tmf files.

Online HelpTable 3-6 describes the online help of the Trace Viewer.

Table 3-6 Online help of the Trace Viewer


Instructions about how to use the messagebrowse functions of the Trace Viewer

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

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

InterfaceFigure 3-4 shows the main interface of the Monitor Viewer.



3-7

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




3 Monitoring databrowse pane

Displays the data and information on monitoringtasks.

4 Task information pane Specifies whether to display the task information andhow 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


Instructions about how to use the messagebrowse functions of the Monitor Viewer

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


LMT User Guide


Issue 03 (2009-04-25)

3.5 Performance Browser Tool of RNC LMTThrough the Performance Browser Tool, you can browse the performance measurement resultssaved on the NE directly at the NE side. You can also manually import the NE measurementfiles, and then export and browse the performance measurement results for facilitating viewingand 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 BrowserViewer.

Table 3-9 Main interface of the Performance Browser Tool




3 Navigation pane Displays the measurement result files in the treestructure.



3-9


4 Detailed informationpane

Displays the detailed information on the selectedperformance item file.

Online HelpTable 3-10 describes the online help of the Performance Browser Tool.

Table 3-10 Online help of the Performance Browser Tool


Explaining how to use performancedescription filesPerformance description files are used toimport NEs in the Performance BrowserTool.

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

Explaining how to export and browse resultfiles

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

FunctionThe 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 boxIn 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 thecommunication between the LMT and the alarm box in real time. When a fault occurs, theConvert Management System reports the fault to the LMT.

InterfaceFigure 3-6 shows the main interface of the Convert Management System.


LMT User Guide


Issue 03 (2009-04-25)

Figure 3-6 Main interface of the Convert Management System

Table 3-11 describes the interface components on the main interface of the Convert ManagementSystem.

Table 3-11 Main interface of the Convert Management System




3 Output pane Displays the output information on the ConvertManagement System the in real time.

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

Table 3-12 Online help of the Convert Management System


Descriptions of the functions of theConvert Management System andinstructions about how to use the functions

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



3-11

4 Installing the RNC LMT Application

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

Prerequisitel 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 listedin 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 thedirectory of the setup disk. A dialog box is displayed, as shown in Figure 4-1.

Figure 4-1 Selecting a setup language

RNCLMT User Guide 4 Installing the RNC LMT Application


4-1

CAUTIONIf the setup languages of the LMT and BAM applications are different, some functions areunavailable, for example, managing the RNC LMT operator accounts. It is recommended tokeep 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, andthen click Next. The installation directory is displayed, as shown in Step 6. If you do not acceptthe agreement terms, click Cancel to quit the installation.

Step 6 Use the default directory or set up a new directory, and then click Next.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.

4 Installing the RNC LMT ApplicationRNC

LMT User Guide


Issue 03 (2009-04-25)

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 NetworkElements (NEs) has already been installed, the default installation path is the path of the previousinstallation and cannot be changed. To change the installation path, you must uninstall the existing LMTapplication.

If an LMT application is running, the Warning dialog box is displayed. If you click Yes, the LMTapplication 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 allcomponents. 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 theinstallation, as shown in Figure 4-4.

RNCLMT User Guide 4 Installing the RNC LMT Application


4-3

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

----End

4 Installing the RNC LMT ApplicationRNC

LMT User Guide


Issue 03 (2009-04-25)

5 Getting Started with the RNC LMT

About This Chapter

This describes how to start, configure, use, and quit the LMT application. When running theLMT 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 PCThis describes how to set the IP address of the LMT PC. When the network segment where theRNC LMT is located changes, you need to set the IP address of the LMT PC again. This tasktakes the connection between the LMT and the BAM server as an example to describes how toset the IP address of the LMT PC.

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

5.3 Starting the Local Maintenance Terminal of the RNCThis describes how to start the LMT and connect it to the specified RNC. This task takes theLocal 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 TerminalThis 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 CertificateThis describes how to configure the identity certificate. You need to configure the identitycertificate before you log in to the LMT in encryption mode.

5.6 Setting the Office Information on the RNC LMTThis 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 RNCThis describes how to lock the RNC Local Maintenance Terminal to avoid any access to theLMT by unauthorized operators. Before you leave the LMT, you are required to manually lockthe Local Maintenance Terminal.

5.8 Unlocking the Local Maintenance Terminal of the RNC

RNCLMT User Guide 5 Getting Started with the RNC LMT


5-1

This describes how to unlock the Local Maintenance Terminal. If the Local MaintenanceTerminal is locked, you need to unlock it before using it.

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

5 Getting Started with the RNC LMTRNC

LMT User Guide


Issue 03 (2009-04-25)

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

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

ContextTo 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. TheLocal Area Connection Properties dialog box is displayed, as shown in Figure 5-1.



5-3

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, asshown in Figure 5-2.


LMT User Guide


Issue 03 (2009-04-25)

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 isin the same network segment as the external virtual IP address of the BAM. Set the subnetmask 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 inFigure 5-1.

Step 7 Click OK to complete the setting.

----End

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

Prerequisitel The BAM communicates with the RNC host properly.

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



5-5

ContextYou 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 thenpress 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 LMTand the BAM is functional. The task is complete. In this example, the external virtual IP addressof 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=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Ping 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 RNCThis describes how to start the LMT and connect it to the specified RNC. This task takes theLocal user account as an example to describe how to log in to the RNC on the LMT.

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

l The LMT application is installed correctly.

Context

WARNINGWhen the LMT application is running, do not modify the system time. Otherwise, serious errorsmay occur on the system. If you have to modify the system time, stop all the LMT applicationfirst.

Procedure

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


LMT User Guide


Issue 03 (2009-04-25)

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 Officedrop-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 canperform 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



5-7

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 systemreturns 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 selectone 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 dialogbox, as shown in Figure 5-7.


LMT User Guide


Issue 03 (2009-04-25)

Figure 5-7 User Login dialog box

Step 6 Enter the user name and password, and then click Login. The main interface of the LocalMaintenance 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 betweenthe NE and the M2000 server.

l If the LMT communicates with the BAM through the M2000 Proxy Server, select the Proxy Serverin 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 theBAM application.

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

----End

5.4 Setting the Properties of the RNC Local MaintenanceTerminal

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.

Prerequisitel The LMT is started and connected to the RNC.

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

Procedurel Setting maximum output lines

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



5-9

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

l Setting auto locking

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

2. Click the Terminal tab, select Automatically locked, and then set the time toautomatically lock the client.

NOTE

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

l Setting MML command timeouts

1. In the Local Maintenance Terminal window, choose System > Command TimeoutSetting.

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 BAMthrough MML commands. When the time is out, and the LMT still receives no response fromthe BAM, the system prompts for the delay.

l Setting output to file

1. In the Local Maintenance Terminal window, choose System > Output WindowSetting.

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

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, theMML commands that fails to be run, or the both. By default, the system does not automaticallysave all MML commands.

----End

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


LMT User Guide


Issue 03 (2009-04-25)

Prerequisitel You have logged in to the LMT offline.

l The identity certificate is ready.

Context

CAUTIONYou can log in to the LMT in encryption mode only after you log in to the LMT offline andconfigure the identity certificate.

Procedure

Step 1 On the LMT, choose System > Certificate Configuration. The Certificate Configurationdialog 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 . The Open dialog box is displayed, as shown in Figure 5-9.



5-11

Figure 5-9 Open dialog box

Step 3 Select the certificate file, and then click Open. The system returns to the CertificateConfiguration dialog box. Specify PFX Password, and then click OK. The certificate issuccessfully configured.

NOTE

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

----End

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

PrerequisiteThe LMT is started.

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


LMT User Guide


Issue 03 (2009-04-25)

Procedurel To add an office, perform the following steps:

1. On the LMT, choose System > Office Management. The Office Management dialogbox 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

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.



5-13

5. Click Close to end the operation.l To modify an office, perform the following steps:


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

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. Click Close to end the operation.

l To delete 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.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. Click Close to end the operation.

l To import 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.2. Click Import. The Open dialog box is displayed, as shown in Figure 5-13.


LMT User Guide


Issue 03 (2009-04-25)


3. Select the office information to be imported, and then click Open. A dialog box is

displayed, indicating that the office information is successfully imported.l To export an office, perform the following steps:


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

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

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

NOTE

Logging in to the LMT in encryption mode is optional.

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

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

4. Click OK. The system returns to the Office Management dialog box.5. Click Close to end the operation.

----End

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


ContextLock the Local Maintenance Terminal in any of the following ways:

Procedurel Choose System > Lock.l Press Ctrl+Alt+M.

l Click the shortcut icon .

----End


LMT User Guide


Issue 03 (2009-04-25)

ResultAfter the LMT is locked, the Terminal Locked dialog box is displayed.

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

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

Step 2 Enter the password, and then click OK.

----End

5.9 Exiting the Local Maintenance Terminal of the RNCThis describes how to exit the Local Maintenance Terminal after you finish using LocalMaintenance 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



5-17

6 Running RNC MML Commands

About This Chapter

This describes how to run MML commands on the Local Maintenance Terminal to performcomprehensive operations and maintenance on the RNC system.

6.1 Concepts of RNC MML CommandsThis describes the following concepts of RNC MML commands: the MML commands, MMLclient, and policies for RNC configuration failure handling.

6.2 Starting the RNC MML ClientThis describes how to start the RNC MML client. Before running the MML commands, youneed to start the MML client. When the LMT is started, the MML client is started by default. Ifthe current interface is not the MML client, refer to the methods described in this task.

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

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

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

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

6.7 Undoing a Single RNC Data Configuration ActionThis 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 notperformed.

6.8 Redoing a Single RNC Data Configuration Action

RNCLMT User Guide 6 Running RNC MML Commands


6-1

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

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

6.10 Redoing Multiple RNC Data Configuration ActionsThis 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 notundone.

6 Running RNC MML CommandsRNC

LMT User Guide


Issue 03 (2009-04-25)

6.1 Concepts of RNC MML CommandsThis describes the following concepts of RNC MML commands: the MML commands, MMLclient, and policies for RNC configuration failure handling.

6.1.1 Introduction to RNC MML CommandsThe Local Maintenance Terminal provides two operating modes: Graphic User Interface (GUI)and MML commands. The RNC supports many MML commands for system operation andmaintenance.

6.1.2 Introduction to the RNC MML ClientThe MML client is integrated in the subsystem of the LMT. It provides the user interface forrunning the MML commands.

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

6.1.4 RNC Data Configuration Right ManagementRNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

6.1.5 RNC Data Configuration RollbackRNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning of the RNC.

6.1.1 Introduction to RNC MML CommandsThe Local Maintenance Terminal provides two operating modes: Graphic User Interface (GUI)and MML commands. The RNC supports many MML commands for system operation andmaintenance.

The format of the MML commands is action plus object, for example, ADD OP. Table 6-1describes the actions of the MML commands.

Table 6-1 Actions of the MML commands

Action Description

ACT Activate

ADD Add dialog box

ADT Audit

BEG Begin

BKP Backup

BLK Block



6-3

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


LMT User Guide


Issue 03 (2009-04-25)

Action Description

SYN Synchronize

TRC Trace

UBL Unblock

UIN Uninhibit

ULD Upload

ULK Unlock

6.1.2 Introduction to the RNC MML ClientThe MML client is integrated in the subsystem of the LMT. It provides the user interface forrunning the MML commands.

Figure 6-1 shows the MML client.

Figure 6-1 MML client

Table 6-2 describes the fields identified with numbers.



6-5

Table 6-2 Fields on the MML client


1 CommonMaintenance pane

Displays system feedbacks, for example, the executionresults.

2 Operation Record Displays the MML commands that have been executedand the related parameters.

3 Help Informationpane

Displays the help information on a command.

4 Command inputarea

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

5 History Commandbox

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

6 Command Inputbox

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

7 Parameter area Displays the parameters of the current command. Youneed to set parameter values in the boxes for theexecution of the command. The parameters in red aremandatory 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 HandlingThe RNC provides different solutions for the RNC data configuration failures occurring whenyou run removing, adding, setting, or modifying commands in online mode.

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

Failure in Running Adding Commands OnlineThere 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 ensurethat the BAM and RNC restore to the state in which the data is not added. Then you cantry to add the data again.

Failure in Running Setting or Modifying CommandsThere are two failures in online running setting or modifying commands:l If the target subrack or board is not in position, you need not to handle the failure.


LMT User Guide


Issue 03 (2009-04-25)

l If the target subrack or board is in position, you can run the setting or modifying commandrepeatedly 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 dataand offline configure the data again.

6.1.4 RNC Data Configuration Right ManagementRNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

In case of conflicts during data configuration, the BAM manages the configuration right asfollows:

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

l Before data configuration, the data configuration right must be obtained. The dataconfiguration 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 thedata 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 canperform data configuration for the RNC only after the user is granted the data configurationright.

6.1.5 RNC Data Configuration RollbackRNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning 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 canflexibly roll back or forward to any rollback point during the configuration, so as to roll back orforward to the expected data configuration status.

Operations of Configuration Rollback

Configuration rollback is applicable when the data configuration right control switch is ON. Youcan run the SET CMCTRLSW command to set the switch to ON.

RNC data configuration rollback consists of the following types of operation:



6-7

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

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

l Undoing configuration commands in batches: This operation is performed to undo all theconfiguration 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 theconfigurations that were rolled back in batches. After the redoing, the RNC returns to eitherthe configuration of the specified rollback point or the configuration that existed before theundoing was performed.

6.2 Starting the RNC MML ClientThis describes how to start the RNC MML client. Before running the MML commands, youneed to start the MML client. When the LMT is started, the MML client is started by default. Ifthe current interface is not the MML client, refer to the methods described in this task.


Procedurel Starting the MML client by using the navigation tree

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

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

l 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 ConfigurationRight

This describes how to check the ownership of the RNC data configuration right.

PrerequisiteYou have logged in to the RNC LMT.

ContextThe returned result can be NULL, which indicates that no one owns this right currently.


LMT User Guide


Issue 03 (2009-04-25)

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

Procedurel In GUI mode

1. Click the CM Control state drop-down list box on the toolbar in the LocalMaintenance Terminal window.

If the user is NULL, as shown in Figure 6-2, you can infer that no user owns the dataconfiguration 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 dataconfiguration 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 RightThis describes how to obtain the ownership of the RNC data configuration right. Before youperform the data configuration operations, you need to obtain the ownership of the RNC dataconfiguration right. Only the M2000 users and users of the following levels can obtain the dataconfiguration right: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to usecommand group G_3 (for data configuration).

Prerequisitel The LMT is started.


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



6-9

Procedure

Step 1 Check whether there are users who have the data configuration right. For details, refer to 6.3Viewing 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 dataconfiguration 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 dataconfiguration 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 CMCTRLcommand 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 obtainedby the M2000 user when the M2000 requests the right from the RNC.

----End

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

Prerequisitel You have logged in to the RNC LMT.

l The MML client is started.

ContextThere 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 onlythe query commands before you obtain the data configuration right.


LMT User Guide


Issue 03 (2009-04-25)

Procedurel 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 box1. 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 to selectthe next history command.)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.The Common Maintenance pane displays the execution results.

l Copying a command and its parameter values to the command input area1. Copy a command and its parameter values, and then paste them in the command input

area.


l Selecting an MML command from the MML Command navigation tree1. 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.


----End

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


l The MML client is started.

l For data configuration, you have obtained the configuration management (CM) controlright.



6-11

l The batch file is ready.

ContextThe batch file (also called data script file) is a plain text file. It contains a group of commandscripts 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 automaticallyexecutes the batch file at the preset execution time.

Procedurel Immediate batch running of MML commands

1. In the Local Maintenance Terminal window, choose System > Batch Commands, orpress 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 beforerunning 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 isimproved.

l Scheduled batch running of MML commands


LMT User Guide


Issue 03 (2009-04-25)

1. In the Local Maintenance Terminal window, choose System > Batch Commands, orpress 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 MMLBatch window. Otherwise, the scheduled task is removed.

----End

6.7 Undoing a Single RNC Data Configuration ActionThis 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 notperformed.


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

ContextNOTE

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



6-13

Procedurel In icon mode

1. In the Local Maintenance Terminal window, click on the toolbar. Thelatest effective configuration command is undone.

l In MML mode

1. Run the BEG UNDO command on the MML client.

----End

6.8 Redoing a Single RNC Data Configuration ActionThis 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 notundone.


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

ContextNOTE

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

Procedurel In icon mode

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

l In MML mode

1. Run the BEG REDO command on the MML client.

----End

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


l You have obtained the data configuration right (see 6.4 Obtaining the RNC DataConfiguration Right), and have run multiple configuration commands successfully.


LMT User Guide


Issue 03 (2009-04-25)

ContextNOTE

The initial rollback point is the first rollback point set by the user. The final rollback point is setautomatically when the latest configuration command is successfully run. A maximum of 1,000configuration commands can be undone between the initial and final rollback points. If the system findsmore than 1,000 commands between the two rollback points, it does not undo the commands and reportsa failure message.

You can set at most five rollback points. If you release the configuration right, the BAM active workareaclears the information related to the rollback stack and rollback points.

Procedure

Step 1 To undo/redo multiple configuration commands, you can run the ADD ROLLBACKPOINTcommand to set rollback points as required.

Step 2 Run the BEG ROLLBACK command to undo the configuration commands. The RNC systemrolls back to the configuration of the specified rollback point.

----End

6.10 Redoing Multiple RNC Data Configuration ActionsThis 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 notundone.


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

ProcedureRun the BEG FORWARD command to redo the multiple configuration actions. You can restorethe configuration to the state at the specified rollback point or to the state before the undoing isperformed.

----End



6-15

7 Managing Authorities for RNC Operations

About This Chapter

This describes how to manage the authorities for the RNC operations. To manage the authoritiesfor the RNC operations is to manage the operator accounts, operator passwords, and RNCcommand groups.

7.1 Concepts of RNC Authority ManagementThis describes the following concepts of the RNC authority management: principles of the RNCauthority management, command groups, user classes, operator identity, operation authorities,operator password, and operating time limit.

7.2 Managing RNC LMT Operator AccountsThis describes how to manage the RNC LMT operator accounts. To manage the operatoraccounts is to add external operator accounts, modify the properties of the operator accounts,and delete external operator accounts.

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

7.4 Managing RNC Command GroupsThis describes how to manage RNC command groups. To manage RNC command groups is toquery group information, set group names, and modify group contents.

RNCLMT User Guide 7 Managing Authorities for RNC Operations


7-1

7.1 Concepts of RNC Authority ManagementThis describes the following concepts of the RNC authority management: principles of the RNCauthority management, command groups, user classes, operator identity, operation authorities,operator password, and operating time limit.

7.1.1 Principles of RNC Authority ManagementThis 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 PasswordThis describes the RNC LMT operator password from the following aspects: the definition ofthe operator password, initial password setting, and authority for changing the password.

7.1.3 RNC Command GroupsThe RNC system provides 32 command groups (G_0 to G_31). Each group has differentfunctions.

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

7.1.5 RNC LMT Operator AuthoritiesThe LMT operators can be divided into the internal operators and external operators. Thisdescribes the authorities of these two types of operators individually.

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

7.1.1 Principles of RNC Authority ManagementThis 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 usesthe 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 typesand provides different command groups for each type as a way to control operationauthority.

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

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

Definition of Operator PasswordTo 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 Managing Authorities for RNC OperationsRNC

LMT User Guide


Issue 03 (2009-04-25)

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

Initial Password SettingThe password of admin is set during the installation of the BAM application. The password ofan external operator can be set by the admin and the ADMINISTRATOR-level and authorizedCUSTOM-level operators during account addition.

Authority for Changing PasswordsAny operator can change his or her own password. The admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the passwords of all externaloperators. Only the admin operator can change the admin password.

For details, refer to Changing Your Password and Changing Passwords of ExternalOperator Accounts.

7.1.3 RNC Command GroupsThe RNC system provides 32 command groups (G_0 to G_31). Each group has differentfunctions.

Table 7-1 lists the 32 command groups (G_0 to G_31) that the system provides.

Table 7-1 Command groups

CommandGroup

Function Description

G_0 Used to query system information, including allMML query commands

l Predefined bythe system

l Cannot bechanged

l Can be queried

G_1 Used to manage system information, including allMML commands

G_2 Used to query data configuration information, forexample, to query the cell data or the AAL2 pathdata

G_3 Used to configure data, for example, to add a cellor an AAL2 path

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

G_5 Used to manage alarms, for example, to manuallyclear alarms or to reset the alarm box

G_6 Used to query performance information, forexample, to query a performance measurementtask or the type of the measurement object

G_7 Used to manage performance, for example, tocreate a measurement task or a custommeasurement counter



7-3

CommandGroup

Function Description

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

G_9 Used to manage equipment

G_10 Used to perform the functions of the Tracing nodeand the Realtime Performance Monitoring nodein the Maintenance tab page in the LocalMaintenance Terminal window

Binary commandgroupspredefined by thesystem Cannot bechanged orqueriedG_11 Used to perform all the functions in the Integrated

Equipment Test tab page in the LocalMaintenance Terminal window

G_12–G_31 Set to null initially and can be defined by thefollowing operators: admin, ADMINISTRATOR-level operators, and authorized CUSTOM-leveloperators

Can be queriedand changed

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

7.1.4 RNC LMT User TypesRNC 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 byonly the RNC LMT. This type of LMT users can log in to the RNC during the RNC systeminstallation and during the disconnection from the M2000.

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

7.1.5 RNC LMT Operator AuthoritiesThe LMT operators can be divided into the internal operators and external operators. Thisdescribes 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 BAMinstallation.

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 describedin Table 7-2.


LMT User Guide


Issue 03 (2009-04-25)

Table 7-2 External operators of different levels

OperatorLevel

AuthorizedCommand Group

Authority Description

GUEST G_0, G_2, G_4,G_6, G_8

Data query The authoritiesare predefined bythe system andcannot bechanged.

USER G_0, G_2, G_4,G_6–G_11

l Authorities of GUEST-level

l System OM

OPERATOR G_0, G_2, G_3–G_11

l Authorities of USER-level

l Data configuration

ADMINISTRATOR

G_1, G_10, G_11 All authorities

CUSTOM Command groupsassigned duringaccount addition

Specified during accountaddition

The authoritiescan be changed.The authorities ofdifferentCUSTOM-leveloperators can bedifferent.

NOTE

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

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

7.1.6 RNC LMT Operating Time LimitsThis 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 operatorcan 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 thecombination of these settings.

Table 7-3 lists some examples of operation time limit settings.



7-5

Table 7-3 Examples of operation time limit settings

SN Date Day Time Actual Operation Time

Example 1 2004-08-01to2005-08-01

Monday toFriday

8:00:00 to18:00:00

From 8:00:00 to 18:00:00 everyMonday to Friday between2004-08-01 and 2005-08-01

Example 2 - Saturday andSunday

- Any time on Saturday and Sunday

Example 3 - - - No operation time limit, that is, theoperator can operate the system atany time.

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

7.2 Managing RNC LMT Operator AccountsThis describes how to manage the RNC LMT operator accounts. To manage the operatoraccounts 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 AccountThis 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 limitfor a new external operator account. Only the admin and the ADMINISTRATOR-level andauthorized CUSTOM-level operators can perform this operation.

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

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

7.2.1 Adding an RNC LMT External Operator AccountThis 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 limitfor a new external operator account. Only the admin and the ADMINISTRATOR-level andauthorized CUSTOM-level operators can perform this operation.



LMT User Guide


Issue 03 (2009-04-25)


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


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

2. Enter the operator account and password, and select the operator level from theOperator Definition drop-down list. If the level is Custom, select command groupsin 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 toadd other operator accounts.

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

l In MML mode

1. Run the ADD OP command and add an external operator account on the MML client.



7-7

WARNINGThe 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 OperatorAccount

This describes how to modify the properties of external operator accounts. The properties involveoperator description, password, operator level, operation authorities, and operation time limit.Except for the password, all the modified information takes effect immediately. Only the adminand the ADMINISTRATOR-level and authorized CUSTOM-level operators can change theLMT operator properties.

Prerequisite

l The LMT is started.


Context

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


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


LMT User Guide


Issue 03 (2009-04-25)

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

Figure 7-3 Operator Management dialog box

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

4. Click OK. The modification is complete.

l In MML mode

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

----End

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





7-9

ContextTo delete an RNC external operator account, you can use either of the following modes: GUIand MML.

NOTE

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


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

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.l In MML mode

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

----End

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


LMT User Guide


Issue 03 (2009-04-25)

7.3.1 Defining Policies for RNC LMT Login PasswordsThis describes how to define policies for login passwords. The policies for login passwords arethe minimum length and complexity of passwords. Only the ADMINISTRATOR-level operatorcan define the policies for the login passwords.

7.3.2 Querying Policies for RNC LMT Login PasswordsThis describes how to query the policies for RNC LMT login passwords. To query the policiesfor 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 AccountThis describes how to change the password of the active RNC LMT operator account. Everyactive online operator can change his or her own password. The new password takes effect thenext time the operator logs in to the RNC.

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

7.3.1 Defining Policies for RNC LMT Login PasswordsThis describes how to define policies for login passwords. The policies for login passwords arethe minimum length and complexity of passwords. Only the ADMINISTRATOR-level operatorcan define the policies for the login passwords.


l You have logged in to the RNC with an account authorized for ADMINISTRATOR-leveloperations.

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


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



7-11

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

3. Click OK to complete the policy settings for the login password. The newly setpassword policies only affect the subsequent password settings and passwordmodifications.

l In MML mode

1. Run the SET PWDPOLICY command and set the policies for LMT login passwordson the MML client.

----End

7.3.2 Querying Policies for RNC LMT Login PasswordsThis describes how to query the policies for RNC LMT login passwords. To query the policiesfor 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.

Prerequisite

You have logged in to the RNC LMT.

ContextThis task can be performed only in MML mode.

Procedure

Run the LST PWDPOLICY command on the MML client. The active policies for loginpasswords are listed in the MML command output pane.

----End

7.3.3 Changing the Password of the Active RNC LMT OperatorAccount

This describes how to change the password of the active RNC LMT operator account. Everyactive online operator can change his or her own password. The new password takes effect thenext time the operator logs in to the RNC.

Prerequisite

You have logged in to the RNC LMT.

ContextNOTE

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


LMT User Guide


Issue 03 (2009-04-25)

Procedure

Step 1 In the Local Maintenance Terminal window, choose Authority > Change Password. TheChange 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 OperatorAccount

This describes how to change the password of an RNC external operator by changing thepassword option. Only the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operators can change the passwords of external operator accounts.



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



7-13

7.4 Managing RNC Command GroupsThis describes how to manage RNC command groups. To manage RNC command groups is toquery group information, set group names, and modify group contents.

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

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

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

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


Procedure

Run the LST CCG command on the MML client.

----End

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




LMT User Guide


Issue 03 (2009-04-25)

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


1. In the Local Maintenance Terminal window, choose Authority > CommandGroup > Set Command Group Name. The Set Command Group Name dialogbox is displayed, as shown in Figure 7-7.

Figure 7-7 Setting command group names

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.

l In MML mode1. 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 LSTCCGN command.

----End

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




7-15


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


1. In the Local Maintenance Terminal window, choose Authority > CommandGroup > Modify Command Group. The Modify Command Group dialog box isdisplayed, as shown in Figure 7-8.

Figure 7-8 Modifying a command group

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.

l In MML mode1. 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


LMT User Guide


Issue 03 (2009-04-25)

8 Managing the RNC License

About This Chapter

This describes how to manage the RNC license, for example, activate and reallocate the RNClicense, check the quantity of current RNC operators, the traffic on the RNC, or the alarms relatedto the RNC license.

8.1 Basic Concepts of the RNC LicenseA license is an authorization agreement between the supplier and the operator in terms of thefunctions, application scope, and service life of products. Physically, a license consists of alicense certificate and a license file.

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

8.3 Reallocating the RNC LicenseThis describes how to reallocate the RNC license. Reallocating the RNC license to the primaryand secondary operators means that the license file does not change but the license allocationpolicies do. For example, secondary operator A may purchase some RNC capacity from theprimary operator.

8.4 Checking RNC Current User Number/ThroughputFor a running RNC, you can run the MML commands to check the current user number orthroughput of the RNC.

RNCLMT User Guide 8 Managing the RNC License


8-1

8.1 Basic Concepts of the RNC LicenseA license is an authorization agreement between the supplier and the operator in terms of thefunctions, application scope, and service life of products. Physically, a license consists of alicense certificate and a license file.

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

8.1.2 License Control for Multiple OperatorsThe RNC supports the RAN sharing function, that is, one primary operator and up to threesecondary operators can share one RNC. The RNC with the RAN sharing function still has onlyone license file, which defines the total capability of the RNC. Each operator uses a unique shareof the license and activates the license independently. Therefore, the RNC capacity and functionsmust 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 MechanismThe activation of the license file accompanies validity check, after which the RNC automaticallyverifies license data on a daily basis.

8.1.1 License FileTo obtain a valid license file from Huawei and successfully activate it is the prerequisite for theRNC to acquire more capacity and functions. One RNC can activate only one license file andthe total capability of the authorized RNC is defined in the license file. If there is no license orthe 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 controlitems of optional functions.

Component Description

License file ID The only identifier of a license file, which makes the license file easy tomanage.

Equipment ID The license file is valid only when the equipment ID is consistent with theESN 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. TheESN of the RNC refers to the encrypted data of three parameters, namely the MNCand MCC of the primary operator, and the RNC ID.

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

8 Managing the RNC LicenseRNC

LMT User Guide


Issue 03 (2009-04-25)

Component Description

Equipmentcapacity

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

Control itemsof optionalfunctions

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

License File ManagementThe 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 capacityexpansion.

Activating the Licensel Activating the license online

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

l Activating the license offlineActivating 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 OperatorsThe RNC supports the RAN sharing function, that is, one primary operator and up to threesecondary operators can share one RNC. The RNC with the RAN sharing function still has onlyone license file, which defines the total capability of the RNC. Each operator uses a unique shareof the license and activates the license independently. Therefore, the RNC capacity and functionsmust 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 OperatorsFigure 8-1 shows an example interface where the command to activate the license of the primaryoperator is used.



8-3

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 thesecondary 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 morethan 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 primaryoperator is not set, the value is the same as the license file by default. When the maximum numberof CS users or the maximum PS throughput of the secondary operator is not set, the value is zeroby default.

Allocating RNC Functions to Primary and Secondary Operators

Allocating RNC functions to primary and secondary operators complies with the followingprinciples:


LMT User Guide


Issue 03 (2009-04-25)

l Neither the primary operator nor the secondary operators can activate the functionsunauthorized by the license file.

l Both the primary operator and the secondary operators can activate the functions authorizedby the license file.

l The secondary operators can activate the authorized functions except those totallycontrolled 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 withthe license file setting.

8.1.3 License Validation MechanismThe activation of the license file accompanies validity check, after which the RNC automaticallyverifies license data on a daily basis.

Path of the License FileBefore the activation, the valid license file needs to be imported as a .lic file into the directoryBAM 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 workspaceinstallation directory\License (license directory for short). This directory stores only one currentlicense file of the RNC.

Legality of the License FileIf in a license file the equipment ID is consistent with the ESN of the RNC, the license file islegal; otherwise, the license file is illegal.

l To activate a license for a legal license file:



8-5

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

– 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 defaultcapacity and functions.

– On 30 days before the running deadline, the RNC reports the alarm 20016 License WillExpire.

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

l To activate a license for an illegal license file:

– The license file is successfully activated. The activated license file is valid within thetrial time. For the time afterwards, the license file becomes invalid and the RNC turnsto 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 datain the BAM database and the DPUb/SPUa at the host. Only the license data at the host takeseffect.

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

l Activating the license offline

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

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

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

l After the host is restarted, the DPUb/SPUa updates the license data according the BAMdatabase.

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

Automatic Verification of the License Data

At 00:45 every morning, the RNC automatically verifies the state of current license file underthe license directory. If the current license file is faulty, the RNC generates related alarms, forexample, 20011 License File Damaged, 20012 License File Does Not Exist, and 20013 InvalidLicense .

At 3:00 every morning, the RNC automatically compares and checks whether the license datain 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 CMPLICENSE.


LMT User Guide


Issue 03 (2009-04-25)

NOTE

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

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

Contextl 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. Wheninstalling or commissioning the RNC, you can manually import and activate the licensefile. For details, refer to the RNC BAM Administration Guide and the RNC CommissioningGuide.

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

CAUTIONYou 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 RNCThis describes how to query the Equipment Serial Number (ESN) information from the RNC.

Prerequisitel The RNC is running properly.

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



8-7

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 BAMThis describes how to upload the RNC license file to the BAM through FTP.



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. TheFTP Client is started.

Step 2 Enter the external virtual IP address of the BAM in Server, and then enter the user name andpassword of the FTP in User and Password.

Step 3 Click to connect the BAM. A BAM file directory is displayed on the right of the FTP Clientwindow.

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


LMT User Guide


Issue 03 (2009-04-25)

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 InformationThis describes how to check that the basic information about the RNC and the operatorinformation exist.

Prerequisitel The RNC is running properly.l The LMT is started and you have logged in to the RNC.

ContextThe RNC ID and the MNC and MCC of the primary operator must be consistent with those inthe license file.

ProcedureStep 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 basicinformation 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 theprimary operator exists.

Step 4 In the absence of the basic information, run the ADD CNOPERATOR command to add thebasic information about the primary operator, as shown in Figure 8-5.

Figure 8-5 Adding the basic information about the primary operator



8-9

Step 5 (Optional) Run the ADD CNOPERATOR command to add a secondary operator, an externaloperator, or a common operator.

Step 6 Run the LST ESN command to check whether the modified ESN information is consistent withthe 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 LicenseThis describes how to activate the RNC license and verify the license configuration information.

Prerequisitel 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 tobe 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 isin 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. Theactivation is performed in sequence from the primary telecom operator to the secondary telecomoperator. If there are multiple telecom operators, run the command repeatedly.


LMT User Guide


Issue 03 (2009-04-25)

Step 4 Run the CMP LICENSE command to check whether the license of the host and that of theBAM 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 consistentwith that applied.

If... Then...

The query result is consistent with the actualconfiguration,

End this task.

The query result is inconsistent with the actualconfiguration,

Contact Huawei for confirmation.

----End

8.3 Reallocating the RNC LicenseThis describes how to reallocate the RNC license. Reallocating the RNC license to the primaryand secondary operators means that the license file does not change but the license allocationpolicies do. For example, secondary operator A may purchase some RNC capacity from theprimary operator.



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 thenquery the configuration details of this file. If the configuration information is consistent withwhat you apply for, go to Step 3. If it is inconsistent, stop this task and contact Huawei forconfirmation.

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 thenthat of the secondary operator. If there are multiple secondary operators, repeat this command.



8-11

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 memoryis consistent with what you apply for. If they are consistent with each other, end this task. If theyare inconsistent, go to Step 2.

----End

8.4 Checking RNC Current User Number/ThroughputFor a running RNC, you can run the MML commands to check the current user number orthroughput of the RNC.



ContextWhen the current CS user number or PS throughput of the RNC approaches or exceeds the limitof 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 thelicense file, you can infer that the RNC needs capacity expansion.

ProcedureRun 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 setto 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 throughputof the subrack is 0.

----End


LMT User Guide


Issue 03 (2009-04-25)

9 Managing RNC Alarms

About This Chapter

This describes how to manage RNC alarms. It helps analyze the alarm, locate, and rectify thefaults.

9.1 Concepts of RNC Alarm ManagementThis describes the following concepts of the RNC alarm management: alarm types, alarmseverity, event types, and the alarm box.

9.2 Setting RNC Alarm LogsThis describes how to set RNC alarm logs. Alarm logs are used to record details of alarms. Alarmlogs are collected by and stored on the BAM. To prevent the logs from occupying too muchspace on the hard disk, you need to set the capacity and time limits of alarm logs.

9.3 Masking RNC AlarmsThis describes how to mask RNC alarms. The alarms that meet the shields are not sent to theLMT or the M2000. To filter alarms, you can set specific alarm shields on the LMT.

9.4 Masking RNC Derived AlarmsThis describes how to mask RNC derived alarms. The RNC can mask derived alarms. The twoalarm mask levels are ON and OFF.

9.5 Monitoring RNC AlarmsThis describes how to monitor RNC alarms. In the Alarm Browse window of the LMT, you canmonitor the alarm information sent to the LMT in real time.

9.6 Managing the Convert Management SystemThis describes how to manage the Convert Management System. The Convert ManagementSystem runs on the LMT PC, which is connected to the alarm box through the serial port. Thesystem forwards the alarms and the commands about the alarms from the BAM to the alarm boxto manage and monitor the alarm box. When receiving the information, the alarm box providesaudible and visible indications.

9.7 Operating the RNC Alarm BoxThis describes how to operate the RNC alarm box. In the RNC, the LMT is connected to theuniversal alarm box of Huawei. When the LMT receives alarms sent from the BAM, the alarmbox gives audible and visible indications.

RNCLMT User Guide 9 Managing RNC Alarms


9-1

9.1 Concepts of RNC Alarm ManagementThis describes the following concepts of the RNC alarm management: alarm types, alarmseverity, event types, and the alarm box.

9.1.1 RNC Alarm TypeThe alarms in the RNC system are of two types: fault alarms and event alarms.

9.1.2 RNC Alarm LevelThe alarm severity indicates how serious a fault is. The alarm severity for both fault alarms andevent alarms can be divided into the four levels: critical, major, minor, and warning.

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

9.1.4 RNC Alarm BoxThe RNC uses the universal alarm box of Huawei. The alarm box provides audible and visibleindications based on the alarm severity level. It is optional and the RNC can be configured withonly one alarm box. For details, refer to its delivery-attached documents.

9.1.1 RNC Alarm TypeThe 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, forexample, board failure or link failure. Fault alarms are of higher severitythan event alarms. After the faults occur, according to the statuses of thefaults, fault alarms are divided into active and recovery alarms.

Event alarms An event alarm indicates a predefined event that happens during therunning of the devices. The alarm represents an instantaneous status of thesystem and the status may not be a fault. Some event alarms are generatedrepeatedly and regularly. Event alarms cannot be divided into active andrecovery alarms.

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

l If the fault is cleared, the status of the alarm changes to Recovery, and the alarm is calleda recovery alarm.

l If the fault is not cleared, the status of the alarm remains Active, and the alarm is called anactive alarm.

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

9 Managing RNC AlarmsRNC

LMT User Guide


Issue 03 (2009-04-25)

NOTE

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

9.1.2 RNC Alarm LevelThe alarm severity indicates how serious a fault is. The alarm severity for both fault alarms andevent 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 AlarmLevel

Definition Solution

Critical alarm Reporting faults that affect the services providedby the system. These alarms need immediatetreatment even during off-work period. Forexample, some equipment or resource breaksdown.

Handle the faultsimmediately.Otherwise, thesystem may collapse.

Major alarm Reporting faults that affect the Quality of Service(QoS). These alarms need treatment duringworking hours. For example, the performance ofsome equipment or resource deteriorates.

Handle the faultstimely. Otherwise,the system may fail toperform some majorfunctions.

Minor alarm Reporting faults that are not serious enough toaffect the QoS. These alarms need timelytreatment or further observation to avoidworsening.

Find and clear anypotential fault intime.

Warning alarm Reporting faults that potentially threaten thesystem services. These alarms need treatmentaccording to specific situations.

Learn the runningstate of the system.

9.1.3 RNC Event Alarm TypesThe 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 astemperature, 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 onebetween the host and the BAM

l QoS: alarms related to QoS



9-3

l Processing error: alarms caused by other exceptions not listed above

9.1.4 RNC Alarm BoxThe RNC uses the universal alarm box of Huawei. The alarm box provides audible and visibleindications based on the alarm severity level. It is optional and the RNC can be configured withonly 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 thenprovides 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 soundof the alarm box stops when the alarm is cleared. You can also manually stop the sound on theLMT.

9.2 Setting RNC Alarm LogsThis describes how to set RNC alarm logs. Alarm logs are used to record details of alarms. Alarmlogs are collected by and stored on the BAM. To prevent the logs from occupying too muchspace 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 LogThis describes how to set the maximum of alarms that can be stored in each log and the timelimit of the logs. Only the admin, the OPERATOR-level, ADMINISTRATOR-level, andauthorized CUSTOM-level operators can set these two items.

9.2.2 Querying the Capacity and Time Limit of an RNC Alarm Log


LMT User Guide


Issue 03 (2009-04-25)

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

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



Procedure

On the MML client, run the SET ALMCAPACITY command.

----End

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


Procedure

On the MML client, run the LST ALMCAPACITY command.

----End

9.3 Masking RNC AlarmsThis describes how to mask RNC alarms. The alarms that meet the shields are not sent to theLMT or the M2000. To filter alarms, you can set specific alarm shields on the LMT.

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

9.3.2 Deleting an RNC Alarm ShieldThis describes how to delete an alarm shield or all alarm shields in the RNC. When you do notneed the RNC to filter an alarm, you should delete all the shields related to this alarm. Operatorsof the following levels can delete alarm shields: ADMINISTRATOR and OPERATOR.

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



9-5

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



Procedure

Step 1 Run the ADD OBJALMSHLD command on the MML client to add an alarm shield. Thesuccessfully 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 alarmshield is successfully added.

NOTE

If no querying condition parameter is entered, all the alarm shields are displayed after this MML commandis 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 ShieldThis describes how to delete an alarm shield or all alarm shields in the RNC. When you do notneed the RNC to filter an alarm, you should delete all the shields related to this alarm. Operatorsof the following levels can delete alarm shields: ADMINISTRATOR and OPERATOR.



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

If... Then...

The shield is listed, Go to Step 2.


LMT User Guide


Issue 03 (2009-04-25)

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 analarm 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 ShieldsThis 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 theMML client to query RNC alarm shields.

NOTE

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

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

----End

9.4 Masking RNC Derived AlarmsThis describes how to mask RNC derived alarms. The RNC can mask derived alarms. The twoalarm mask levels are ON and OFF.

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

9.4.2 Querying the Mask Level of an RNC Derived AlarmThis 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.



9-7

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



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

ProcedureRun the SET ALMML command on the MML client.

----End

9.4.2 Querying the Mask Level of an RNC Derived AlarmThis 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.


ProcedureOn the MML client, run the LST ALMML command and enter the parameter as required toquery whether the alarm mask switch is on or off.

----End

9.5 Monitoring RNC AlarmsThis describes how to monitor RNC alarms. In the Alarm Browse window of the LMT, you canmonitor the alarm information sent to the LMT in real time.

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

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

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

9.5.4 Querying RNC Alarm Logs


LMT User Guide


Issue 03 (2009-04-25)

This describes how to query the history alarm information from the BAM database. It helps learnthe history operating situation of the system.

9.5.5 Querying RNC Alarm Handling SuggestionsThis describes how to query RNC alarm handling suggestions. The LMT provides detailed helpinformation for every alarm.

9.5.6 Manually Setting a Cleared RNC AlarmThis 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 AlarmThis describes how to save a part or all of the alarm information in the Alarm Browse windowor the Query Alarm Log window for later queries.

9.5.8 Setting the Preferences for Printing RNC Alarms in Real TimeThis describes how to set the requirements for the alarms for printing. After the setting, only thereal-time alarms that meet the requirements can be printed.

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

9.5.1 Setting the Properties of the Alarm Browse WindowThis 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 setthem.

Table 9-3 Display properties and setting methods

Display Property Setting Description

Alarm colors Choose Fault Management >Alarm Customization.

Select colors for alarms ofdifferent types, severitylevels, and status.

Display amount Choose Fault Management >Alarm Customization.

Set the initial and maximumamounts of alarms to bedisplayed.

Deletion of recoveryalarms from fault alarmbrowse window

Right-click the fault alarmbrowse pane and choose ClearAll Recovery Alarms from theshortcut menu.

Delete all recovery alarmsfrom the fault alarm browsepane. The records of therecovery alarms are stillstored and can be queried.



9-9

Display Property Setting Description

Manually Refresh Right-click the fault alarmbrowse pane and chooseManually Refresh from theshortcut menu.

Refresh the alarminformation in the faultalarm window and delete allthe cleared alarms.

----End

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


ProcedureStep 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


LMT User Guide


Issue 03 (2009-04-25)

Step 2 Set the alarm severity and sound playing frequency in the Fault Alarm Sound area in the AlarmCustomization dialog box.

Step 3 Click OK to save the settings.

----End

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


Procedure

Step 1 In the Local Maintenance Terminal window, choose Fault Management > Browse Alarmto display the Alarm Browse window. The upside of the window is the fault alarm browse paneand 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 boxis displayed, as shown in Figure 9-3.

Figure 9-3 Details about an alarm



9-11

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, andthe alarm handling.

Step 5 Click Close to close the dialog box.

----End

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


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


1. In the Local Maintenance Terminal window, choose Fault Management > Query

Alarm Log or click . The Query Alarm Log dialog box is displayed, as shownin Figure 9-4.


LMT User Guide


Issue 03 (2009-04-25)

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



9-13

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.l 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 theDynamically Add. The alarm is automatically appended to the Query Alarm Log window.

----End

9.5.5 Querying RNC Alarm Handling SuggestionsThis describes how to query RNC alarm handling suggestions. The LMT provides detailed helpinformation for every alarm.


ContextThe 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. TheAlarm Detailed Information dialog box is displayed, as shown in Figure 9-6.


LMT User Guide


Issue 03 (2009-04-25)

Figure 9-6 Details about an alarm

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

Figure 9-7 Alarm online help



9-15

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


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

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


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

3. Click Yes. The color of the alarm changes to that of a recovery one.l In MML mode

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

----End

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


ContextThe information is stored in any of the following formats:l .txt

l .htm

l .csv


LMT User Guide


Issue 03 (2009-04-25)

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, officename, 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 exampleALM-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 TimeThis describes how to set the requirements for the alarms for printing. After the setting, only thereal-time alarms that meet the requirements can be printed.



9-17


l The LMT is connected to a printer that works properly.

Procedure

Step 1 In the Local Maintenance Terminal window, choose Fault Management > Alarm RealtimePrint 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 AlarmsThis describes how to print a part or all of the alarm information in the Alarm Browse windowor the Query Alarm Log window.


l The LMT is connected to a printer that works properly.


LMT User Guide


Issue 03 (2009-04-25)

ProcedureStep 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 beprinted, 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 SystemThis describes how to manage the Convert Management System. The Convert ManagementSystem runs on the LMT PC, which is connected to the alarm box through the serial port. Thesystem forwards the alarms and the commands about the alarms from the BAM to the alarm boxto manage and monitor the alarm box. When receiving the information, the alarm box providesaudible and visible indications.

9.6.1 Starting the RNC Convert Management System



9-19

This describes how to start the Convert Management System on the LMT PC which is connectedto the alarm box.

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

9.6.3 Saving the Information in the Output WindowThis describes how to save the information in the output window for the analysis of the operatingsituation of the Convert Management System.

9.6.4 Exiting the RNC Convert Management SystemThis describes how to exit the Convert Management System on the LMT PC when the audibleand visible indications provided by the alarm box are no longer necessary. The LMT PC isconnected to the alarm box.

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

Prerequisitel The LMT is properly connected to the RNC.

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

ProcedureChoose Start > All Programs > HUAWEI Local Maintenance Terminal > ConvertManagement System to start the Convert Management System.

----End

9.6.2 Setting the Parameters of the RNC Convert ManagementSystem

This describes how to set the parameters of the Convert Management System to enable the systemto perform properly the function of forwarding alarm information.

Prerequisitel 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 ) to start the Convert ManagementSystem.

Step 2 Choose Operate > Configuration or click the shortcut icon .


LMT User Guide


Issue 03 (2009-04-25)

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 theserial 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:50Prompt: Original connection is closed and new connection will be built with new configuration...+++End+++Begin2005-11-06 19:47:50Prompt: COM communicate normally and connect the host now...+++End+++Begin2005-11-06 19:47:58Prompt: Connection to host succeeded, alarm transfer begins...+++End

----End

9.6.3 Saving the Information in the Output WindowThis describes how to save the information in the output window for the analysis of the operatingsituation of the Convert Management System.

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

l The parameters of the Convert Management System are successfully set.

Procedure

Step 1 Choose Operate > Save or click the shortcut icon . You can also choose Operate > Saveas.

Step 2 In the Save As dialog box, enter the file name in the File name box and select the file type fromthe Save as type drop-down list.

Step 3 Click Save to save the information in the output window.

----End



9-21

9.6.4 Exiting the RNC Convert Management SystemThis describes how to exit the Convert Management System on the LMT PC when the audibleand visible indications provided by the alarm box are no longer necessary. The LMT PC isconnected to the alarm box.

PrerequisiteThe 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 in the status area (when the communication on the serial port is abnormal,

the icon is ) 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 BoxThis describes how to operate the RNC alarm box. In the RNC, the LMT is connected to theuniversal alarm box of Huawei. When the LMT receives alarms sent from the BAM, the alarmbox gives audible and visible indications.

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

9.7.2 Resetting the RNC Alarm BoxThis 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 SoundThis describes how to stop an alarm sound.

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

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

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

9.7.7 Setting the Shield Severity of the RNC Alarm BoxThis 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


LMT User Guide


Issue 03 (2009-04-25)

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

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

PrerequisiteThe 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. TheConfiguration 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 thatconnects the LMT with the alarm box.

Step 5 Click OK. When the Convert Management System window displays the followinginformation, the connection between the LMT and the alarm box is successful.+++Begin2005-11-06 19:47:50Prompt: Original connection is closed and new connection will be built with new configuration...+++End+++Begin2005-11-06 19:47:50Prompt: COM communicate normally and connect the host now...+++End+++Begin2005-11-06 19:47:58Prompt: Connection to host succeeded, alarm transfer begins...+++End

----End



9-23

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



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.


1. In the Local Maintenance Terminal window, choose Fault Management > Alarm

Box Operation > Alarm Box Control or click . The Alarm Box Control dialogbox is displayed, as shown in Figure 9-13.

Figure 9-13 Resetting alarm box

2. Select Reset Alarm Box.

3. Click OK.

l In MML mode

1. Run the RST ALMBOX command on the MML client.

----End


LMT User Guide


Issue 03 (2009-04-25)

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



l The LMT is connected to the alarm box.


ContextWhen the LMT receives fault alarms sent from the BAM, the alarm box emits sound until thefault 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 CUSTOM-level operators can stop the alarm sound. To stop the alarm sound, you can use either of thefollowing modes: GUI and MML.




Figure 9-14 Alarm Box Control

2. Select Stop Alarm Sound in the dialog box.3. Click OK.



9-25

l In MML mode1. Run the STP BOXSND command on the MML client.

----End

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





ContextWhen the LMT receives fault alarms sent from the BAM, the color indicator on the alarm boxcorresponding 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, thatis, to change the status of the light from flashing to normal.

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




Figure 9-15 Alarm Box Control


LMT User Guide


Issue 03 (2009-04-25)

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

3. Click OK.

l In MML mode

1. Run the CLR BOXLGT command on the MML client.

----End

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




ContextTo query the version of the alarm box, you can use either of the following modes: GUI andMML.


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

l In MML mode

1. Run the LST BOXVER command on the MML client.

----End

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




ContextWhen the LMT receives one or more fault alarms of some severity level from the RNC, thecorresponding indicator on the alarm box flashes. The flashing indicator, however, does notindicate the number of alarms.



9-27

ProcedureRun the LST BOXLGT command on the MML client.

----End

9.7.7 Setting the Shield Severity of the RNC Alarm BoxThis 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.



ContextOnly the admin, the OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level operators can set alarm shield severity. To set the alarm shield severity, you can use eitherof the following modes: GUI and MML.


1. In the Local Maintenance Terminal window, choose Fault Management > AlarmBox Operation > Shield Severity Set. The Alarmbox Shield Severity Setting dialogbox is displayed, as shown in Figure 9-16.

Figure 9-16 Setting the alarm shield severity

2. Select the alarm severity from the Alarm Severity drop-down list.3. Click OK.

l In MML mode1. Run the SET ALMSCRN command on the MML client.

----End

9.7.8 Querying the Mask Level of the RNC Alarm BoxThis describes how to query the mask level of the alarm box.


LMT User Guide


Issue 03 (2009-04-25)


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


1. In the Local Maintenance Terminal window, choose Fault Management > AlarmBox Operation > Shield Severity Get. The Alarm Box Shield Severity Querydialog box is displayed, as shown in Figure 9-17.

Figure 9-17 Querying alarm mask level

2. Click OK.

l In MML mode1. Run the LST ALMSCRN command on the MML client.

----End



9-29

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 ManagementThis describes the following concepts of the RNC log management: RNC log types and authorityof the RNC log operations.

10.2 Setting the Time and Count Limits of the RNC LogThis describes how to set the limit for the continuous system run time that an operation or securitylog records and how to set the limit for the number of items that an operation or security logsaves. If the run time or the quantity of saved items exceeds the limit, the BAM databaseautomatically deletes oldest information.

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

10.4 Querying an RNC Operation LogThis 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 LogThis describes how to use the FTP Client to download to the LMT an exported operation logthat is saved in the directory BAM active workspace installation directory\FTP.

10.6 Querying RNC Security LogsThis describes how to query the RNC security logs. The security logs record the results generatedwhen the delivered and authenticated commands are run. By performing this task, you can learnabout the information related to RNC operations.

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

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

RNCLMT User Guide 10 Managing RNC Logs


10-1

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

10 Managing RNC LogsRNC

LMT User Guide


Issue 03 (2009-04-25)

10.1 Concepts of RNC Log ManagementThis describes the following concepts of the RNC log management: RNC log types and authorityof the RNC log operations.

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

10.1.2 RNC Log Management AuthorityOnly the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operatorscan manage the logs.

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

RNC Operation LogThe RNC operation log refers to all the real-time operation information recorded in the BAMdatabase.

The operation log is mainly used to analyze the relationships between device faults andperformed operations.

RNC Security LogThe RNC security log refers to the NE or EMS information related to security events such aslogin, logout, and authorization.

The security log is used for auditing and tracing security events.

RNC Running LogThe RNC running log refers to the system running information the RNC host records in realtime.

The running log helps you in fault location, routine inspection, and device running monitoring.

10.1.2 RNC Log Management AuthorityOnly the admin and the ADMINISTRATOR-level and authorized CUSTOM-level operatorscan manage the logs.

NOTE

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

10.2 Setting the Time and Count Limits of the RNC LogThis describes how to set the limit for the continuous system run time that an operation or securitylog records and how to set the limit for the number of items that an operation or security log



10-3

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


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 aLog 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 LogThis describes how to query the time and quantity limits for the storage of the RNC operationlog and RNC security log.



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 LogThis describes how to query an operation log from the BAM database. By performing this task,you can learn about the RNC operation information.



LMT User Guide


Issue 03 (2009-04-25)


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 LogThis describes how to use the FTP Client to download to the LMT an exported operation logthat 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(OPERATINGLOG), and then set other parameters as required to export the operation log. When exportingoperation logs, you can name the file or use the default name provided by the system. The defaultname 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 timelength. 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 isexported. For example, Start Time for exporting the operation log is 11.06.07 16:57:01 andEnd Time is 12.06.07 16:57:01. The default file name is RNC-Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-OLOG.txt.

The default save path for the exported logs is BAM active workspace installation directory\FTP on the BAM active workspace.




10-5

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 activeworkspace 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 todownload it to the LMT.

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

----End

10.6 Querying RNC Security LogsThis describes how to query the RNC security logs. The security logs record the results generatedwhen the delivered and authenticated commands are run. By performing this task, you can learnabout the information related to RNC operations.



Procedure

Step 1 Enter the LST SECLOG 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


LMT User Guide


Issue 03 (2009-04-25)

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 LogThis describes how to use the FTP Client to download to the LMT an exported security log thatis 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(SECURITYLOG), and then set other parameters as required to export the security log. When exportingoperation logs, you can name the file or use the default name provided by the system. The defaultname 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 timelength. 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 isexported. For example, Start Time for exporting the security log is 11.06.07 17:32:46 andEnd Time is 12.06.07 17:32:46. The default file name is RNC-Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-SLOG.txt.

The default save path for the exported logs is BAM active workspace installation directory/FTP on the BAM active workspace.


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





10-7


Step 5 After the connection is successful, in the server file list pane, double-click BAM activeworkspace 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 todownload it to the LMT.

NOTE




----End

10.8 Exporting an RNC Running LogThis describes how to use the FTP Client to download to the LMT an exported running log thatis 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 thenexport 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, forthe running log of the No. 3 RBS that is uploaded at 2005-11-07 17:19:47, the file name is03Log20051107171947.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 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




LMT User Guide


Issue 03 (2009-04-25)


Step 5 After the connection is successful, in the server file list pane, double-click BAM activeworkspace installation directory\LoadData\famlog. The server file list pane displays the filesin the directory.

Step 6 Based on the file name, double-click the running log file, or select it and then click todownload it to the LMT.

NOTE




----End

10.9 Collecting Fault Log InformationThis describes how to collect fault log information for fault location. Fault log informationconsists of the host log, BAM log, database log, system event log, operation log, BAMinstallation 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



10-9

11 Managing the RNC Equipment by Usingthe 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, boardlinks, and board alarms in GUI mode.

11.1 Using the RNC Device PanelThis describes the RNC device panel. By performing this task, you can learn about how to startand use it, and how to query the status of the RNC boards.

11.2 Using the RNC Display PanelThis describes the RNC display panel. By performing this task, you can learn about how to startthe display panel and how to query the status of the RNC boards.

11.3 Viewing Active Alarms of an RNC BoardThis describes how to query the detailed alarm information on boards. It helps learn the workingstatus of boards.

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

RNCLMT User Guide

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


11-1

11.1 Using the RNC Device PanelThis describes the RNC device panel. By performing this task, you can learn about how to startand use it, and how to query the status of the RNC boards.

11.1.1 Introduction to the RNC Device PanelThe RNC system provides multiple modes for equipment maintenance. In addition to MMLcommands, the Local Maintenance Terminal provides the graphical device panel that simplifiesthe equipment maintenance.

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

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

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

11.1.5 Browsing the Status of an RNC BoardThis 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 BoardThis describes how to query the detailed status of an RNC board.

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

11.1.1 Introduction to the RNC Device PanelThe RNC system provides multiple modes for equipment maintenance. In addition to MMLcommands, the Local Maintenance Terminal provides the graphical device panel that simplifiesthe equipment maintenance.

The device panel is automatically refreshed, showing board status in real time through the boardcolors, indicators, and failure bar.

On the device panel, you can right-click a board in position and choose operations from theshortcut menu. For example, you can query the board status. Figure 11-1 shows the device panel.


RNCLMT User Guide


Issue 03 (2009-04-25)

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 normalstatus 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 Tasks11.1.2 Starting the RNC Device Panel11.1.3 Showing or Hiding the Legend on the RNC Device Panel11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel11.1.5 Browsing the Status of an RNC Board11.1.6 Querying the Detailed Status of an RNC Board11.1.7 Querying the CPU/DSP Usage of an RNC Board

11.1.2 Starting the RNC Device PanelThis 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.

RNCLMT User Guide



11-3

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 Concepts11.1.1 Introduction to the RNC Device Panel

Related Tasks11.1.3 Showing or Hiding the Legend on the RNC Device Panel11.1.4 Showing or Hiding the Failure Bar on the RNC Device Panel11.1.5 Browsing the Status of an RNC Board11.1.6 Querying the Detailed Status of an RNC Board11.1.7 Querying the CPU/DSP Usage of an RNC Board

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


l The device panel is started.

Procedurel To display the color legend, perform the following step:

1. Click on the top right of the device panel, as shown in Figure 11-3.


RNCLMT User Guide


Issue 03 (2009-04-25)

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 Tasks11.1.2 Starting the RNC Device Panel

RNCLMT User Guide



11-5

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



l There are one or more faulty boards.

Procedurel To show the failure bar, perform the following step:

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

Figure 11-5 Showing the failure bar

l To hide the failure bar, perform the following step:

1. Right-click the edge of the shelf and choose Hide Failure Bar from the shortcut menu,as shown in Figure 11-6.


RNCLMT User Guide


Issue 03 (2009-04-25)

Figure 11-6 Hiding the failure bar

----End



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



Procedure

View the status of an RNC board by referring to the legend on the device panel.

----End

RNCLMT User Guide



11-7



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


l The boards are in position.

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


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 isdisplayed, 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


RNCLMT User Guide


Issue 03 (2009-04-25)

l In MML mode

Run the following commands on the MML client to query the detailed information onboards:

– 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 BoardThis describes how to query the CPU/DSP usage of an RNC board. By performing this task, youcan learn about the usage of the CPU/DSP resources on a board.



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 DisplayCPU Usage from the shortcut menu. The CPU/DSP Usage window is displayed, showing real-time monitoring results in either list or chart. Figure 11-8 is an example of the output interface(list) of the CPU/DSP Usage window.

RNCLMT User Guide



11-9

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

----End



11.2 Using the RNC Display PanelThis describes the RNC display panel. By performing this task, you can learn about how to startthe display panel and how to query the status of the RNC boards.

11.2.1 Introduction to the RNC Display PanelThe 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 PanelThis 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 BoardThis 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


RNCLMT User Guide


Issue 03 (2009-04-25)

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 BoardThis describes how to view the status of a DSP on the DPUb. The DSP working status includesnormal, in place, loading, and faulty.

11.2.6 Querying the Detailed Status of an E1/T1 LinkThis 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 LightThis describes how to query the alarms through a board alarm light.

11.2.1 Introduction to the RNC Display PanelThe 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 performrelated 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 Showing the running status of the device in GUI mode

RNCLMT User Guide



11-11

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

Related Tasks11.2.2 Starting the RNC Display Panel11.2.3 Querying the Status of FE Ports on an RNC Board11.2.4 Querying the Status of GE Ports on an RNC Board11.2.5 Querying the Detailed Status of a DSP on the DPUb Board11.2.6 Querying the Detailed Status of an E1/T1 Link11.2.7 Querying Alarms through a Board Alarm Light

11.2.2 Starting the RNC Display PanelThis 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 Paneltab. 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 Concepts11.2.1 Introduction to the RNC Display Panel


RNCLMT User Guide


Issue 03 (2009-04-25)

Related Tasks11.2.3 Querying the Status of FE Ports on an RNC Board11.2.4 Querying the Status of GE Ports on an RNC Board11.2.5 Querying the Detailed Status of a DSP on the DPUb Board11.2.6 Querying the Detailed Status of an E1/T1 Link11.2.7 Querying Alarms through a Board Alarm Light

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



l The display panel is started.

Procedure

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

Figure 11-11 Status of an FE port

----End


RNCLMT User Guide



11-13

Related Tasks11.2.2 Starting the RNC Display Panel

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




Procedure

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

Figure 11-12 Status of an GE port

----End




RNCLMT User Guide


Issue 03 (2009-04-25)

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


l The board is in the specified slot.

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


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


RNCLMT User Guide



11-15


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




Procedure

On the display panel, right-click the E1/T1 link to be queried, choose Query E1/T1 LinkState. 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




RNCLMT User Guide


Issue 03 (2009-04-25)

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




ProcedureOn the display panel, right-click the alarm light to be queried, and then choose Query TheAlarm Information Of Alarm Lamp. The Query The Alarm Information Of AlarmLamp 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 BoardThis describes how to query the detailed alarm information on boards. It helps learn the workingstatus of boards.

RNCLMT User Guide



11-17


ProcedureRun the LST ALMAF command on the MML client to query active alarms of boards.

----End

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


ProcedureIn the main window of the Local Maintenance Terminal, click the drop-down list shown inFigure 11-16 on the right of the toolbar to check the configuration mode of each subrack.

Figure 11-16 Configuration modes of subracks

----End


RNCLMT User Guide


Issue 03 (2009-04-25)

12 Tracing and Viewing RNC Messages

About This Chapter

This describes how to manage the RNC traced messages. RNC message tracing is implementedthrough menus. You can use the Trace Viewer to query the tracing data recorded in the files.

12.1 Concepts of RNC Message Tracing ManagementThis describes the basic concepts of the RNC message tracing management.

12.2 Tracing Iu Interface MessagesThis describes how to trace the signaling messages over the Iu interface, including theconnection-oriented messages and the connectionless messages. You can perform this task tolocate 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 MessagesThis describes how to trace the signaling messages over the Iur interface, including theconnection-oriented messages and the connectionless messages. You can perform this task tolocate 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 controlfailure, and paging failure.

12.4 Tracing Iub Interface MessagesThis describes how to trace signaling messages over the Iub interface, that is, NodeB ApplicationPart (NBAP) messages. You can perform this task to identify the fault in the failure of thefollowing procedures: radio link setup, radio link reconfiguration, resource audit, cell setup, cellreconfiguration, common transport channel setup, and system information update.

12.5 Tracing Uu Interface MessagesThis describes how to trace all or part of the signaling messages over the Uu interface in aspecified cell. You can perform this task to locate the fault in the following scenarios: RRCconnection setup failure, radio bearer setup failure, physical channel reconfiguration failure, andcell update failure.

12.6 Tracing UE MessagesThis describes how to monitor the interworking of signaling on the standard interfaces, theinterworking 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 combinationwith the drive test result.

RNCLMT User Guide 12 Tracing and Viewing RNC Messages


12-1

12.7 Tracing IOS MessagesThis describes how to trace a number of calls that meet the sampling criteria within a specifiedrange of cells. When creating the task, you can specify the number of calls to be traced. You canalso specify the messages to be traced by selecting the event type.

12.8 Tracing Cell MessagesThis 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 ofno access or low access success rate of the cell, and to collect the user volume in the cell.

12.9 Tracing REDIRECT MessagesThis describes how to redirect messages that are printed through the serial port of a specifiedsubsystem to the message browse window.

12.10 Tracing MNCDT MessagesThis describes how to trace the missing neighbor cell relations of a cell. The Missing NeighborCell Detect Trace (MNCDT) tracing task involves three independent detection types: detectionof missing intra-frequency neighboring cell relations, detection of missing inter-frequencyneighboring cell relations, and detection of missing inter-RAT neighboring cell relations.

12.11 Tracing OS MessagesThis describes how to trace messages between the exchange module of the BAM and internalmodules of a board or between internal modules of different boards.

12.12 Tracing SCCP MessagesThis describes how to monitor the interworking of SCCP messages respectively over the Iu andIur 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 Iuand Iur interfaces.

12.13 Tracing MTP3 MessagesThis describes how to trace the MTP3 messages, including the MTP3 upper layer (QAAL2 andSCCP) messages, MTP3 signaling link test messages, and MTP3 signaling network managementmessages.

12.14 Tracing QAAL2 MessagesThis 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 abnormalityof an ATM Adaptation Layer type 2 (AAL2) connection on the user plane respectively on theIu, Iur, and Iub interfaces.

12.15 Tracing SAAL MessagesThis 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 SAALlink on the Iu, Iur, and Iub interfaces.

12.16 Tracing SCTP MessagesThis 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 problemof non-availability of SCTP link on the Iu, Iur, and Iub interfaces.

12.17 Tracing M3UA MessagesThis describes how to trace the M3UA Messages over the Iu and Iur interfaces. You can performthis task to locate the problem that the M3UA link is unavailable while the corresponding IPlink is available.

12.18 Tracing Location Messages

12 Tracing and Viewing RNC MessagesRNC

LMT User Guide


Issue 03 (2009-04-25)

This describes how to trace the results of a location tracing initiated by the CN. This task canalso simulate the CN to initiate a location tracing and trace the results.

12.19 Basic Operations of RNC Message TracingThis describes how to perform the following operations of RNC message tracing: browsing anRNC traced message online, querying the properties of a tracing task, viewing the translation ofa traced message, saving an RNC traced message, pausing an RNC tracing task, resuming anRNC tracing task, stopping an RNC tracing task, and browsing an RNC traced message offline.

12.20 Parameter Reference for RNC Message Tracing and ViewingThis describes the parameters used for each message tracing.



12-3

12.1 Concepts of RNC Message Tracing ManagementThis describes the basic concepts of the RNC message tracing management.

12.1.1 Functions of RNC Message Tracing ManagementRNC message tracing management is used to trace interfaces, signaling links, and internalmessages. It is applicable to routine equipment maintenance, debugging, and fault location.

12.1.2 Working Principles of RNC Message Tracing ManagementThis describes the working principles of the message tracing. It also describes how to create orclose message trace tasks and the internal process for the service module to report tracedmessages to the LMT.

12.1.3 Authority of RNC Message Tracing ManagementYou can perform the message tracing management operations only when you are authorized.

12.1.1 Functions of RNC Message Tracing ManagementRNC message tracing management is used to trace interfaces, signaling links, and internalmessages. 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 ManagementThis describes the working principles of the message tracing. It also describes how to create orclose message trace tasks and the internal process for the service module to report tracedmessages to the LMT.

Working Principles of the Message TracingFigure 12-1 shows the working principles of the message tracing.


LMT User Guide


Issue 03 (2009-04-25)

Figure 12-1 Working principles of the message tracing

Internal Process for Creating the Tracing Task1. 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 moduleof the specified board.

3. After receiving the command, the debugging module records the filter parameters of thetracing data in the filter table and notifies the service module.

4. The service module updates the local filter table according to the message from thedebugging module.

Internal Process for Closing the Tracing Task1. 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 LMT1. 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 thetask ID.

3. The LMT translates the messages and displays them on the interface.

12.1.3 Authority of RNC Message Tracing ManagementYou 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 groupG_10, all the others have the authority to perform the online tracing tasks.



12-5

NOTE

Group G_10 contains commands for tracing and query. It is a binary command group, which contains noMML commands.

Related Tasks12.2 Tracing Iu Interface Messages12.3 Tracing Iur Interface Messages12.4 Tracing Iub Interface Messages12.5 Tracing Uu Interface Messages12.6 Tracing UE Messages12.7 Tracing IOS Messages12.8 Tracing Cell Messages12.9 Tracing REDIRECT Messages12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells12.11 Tracing OS Messages12.12 Tracing SCCP Messages12.13 Tracing MTP3 Messages12.14 Tracing QAAL2 Messages12.15 Tracing SAAL Messages12.16 Tracing SCTP Messages12.17 Tracing M3UA Messages12.18 Tracing Location Messages

12.2 Tracing Iu Interface MessagesThis describes how to trace the signaling messages over the Iu interface, including theconnection-oriented messages and the connectionless messages. You can perform this task tolocate the fault in the failure of the following procedures: RAB assignment, RAB release, paging,Iu release, security mode control, initial UE message, and relocation.

Prerequisitel The LMT is running normally.


ContextYou can start the Iu interface tracing on the LMT to monitor the interworking of signalingmessages over the Iu interface.

To start a tracing task, you can select the following operations:l Tracing the messages processed by the specified SPU subsystem

l Tracing the required message types


LMT User Guide


Issue 03 (2009-04-25)

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 performedsimultaneously. When creating two or more tasks of the same type, do not set their parameterscompletely 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 > InterfaceTrace 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 parametersin the Basic tab page. Select Iu in the Trace Type area.



12-7

Step 3 Click the Iu tab, and set the parameters accordingly. Click OK. The displayed message browsewindow shows the related message flow.

----End

PostrequisiteThe message browse window displays the details of a tracing message, including the tasknumber, 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 columnrepresents the DPC of the peer CN equipment. You can query more information about the DPC by runningthe command LST N7DPC.

Related Concepts12.1.3 Authority of RNC Message Tracing Management

Related Tasks12.19.1 Browsing an RNC Traced Message Online12.19.2 Querying the Properties of the Tracing Task12.19.3 Viewing a Message Translation12.19.4 Saving an RNC Traced Message12.19.5 Pausing an RNC Tracing Task12.19.6 Resuming an RNC Tracing Task12.19.7 Closing an RNC Tracing Task


LMT User Guide


Issue 03 (2009-04-25)

Related References12.20.1 Parameter Reference for Iu Interface Tracing

12.3 Tracing Iur Interface MessagesThis describes how to trace the signaling messages over the Iur interface, including theconnection-oriented messages and the connectionless messages. You can perform this task tolocate 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 controlfailure, and paging failure.



ContextYou can start the Iur interface tracing on the LMT to monitor the interworking of signalingmessages over the Iur interface.

To start a tracing task, you can select the following operations:l Tracing the messages processed by the specified SPU subsystem

l Tracing the required message types

l Tracing all message types


For each subsystem, a maximum of six Iur interface tracing tasks can be performedsimultaneously. When creating two or more tasks of the same type, do not set their parameterscompletely 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 > InterfaceTrace Task, and then double-click Iur. A dialog box is displayed, as shown in Figure 12-4.



12-9

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 parametersin 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 browsewindow shows the related message flow.

----End



LMT User Guide


Issue 03 (2009-04-25)

Figure 12-5 Output of Iur interface tracing

NOTE

In the message browse window of Iur Interface Tracing, the number in the Information Source columnrepresents the DPC of the neighboring RNC. You can query more information about the DPC by runningthe command LST N7DPC.



Related References12.20.2 Parameter Reference for Iur Interface Tracing



12-11

12.4 Tracing Iub Interface MessagesThis describes how to trace signaling messages over the Iub interface, that is, NodeB ApplicationPart (NBAP) messages. You can perform this task to identify the fault in the failure of thefollowing procedures: radio link setup, radio link reconfiguration, resource audit, cell setup, cellreconfiguration, common transport channel setup, and system information update.



ContextYou can start the Iub interface tracing on the LMT to monitor the interworking of signalingmessages 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 Tracing the messages processed by the specified SPU subsystem

l Selecting the types of traced messages


For each subsystem, a maximum of six Iub interface tracing tasks can be performedsimultaneously. When creating two or more tasks of the same type, do not set their parameterscompletely 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 > InterfaceTrace Task, and then double-click Iub. A dialog box is displayed, as shown in Figure 12-6.


LMT User Guide


Issue 03 (2009-04-25)

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 parametersin 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 browsewindow shows the related message flow.

NOTE

l You can query the NodeB ID and other information about the NodeB by running the command LSTNODEB.

l You can query the NodeB port type and other information about the port by running the commandLST IUBCP.

----End




12-13

Figure 12-7 Output of Iub interface tracing

NOTE

In the message browse window of the Iub interface tracing task, the number in the InformationSource column represents the NodeB ID. You can query more information about the NodeB by runningthe command LST NODEB.



Related References12.20.3 Parameter Reference for Iub Interface Tracing

12.5 Tracing Uu Interface MessagesThis describes how to trace all or part of the signaling messages over the Uu interface in aspecified cell. You can perform this task to locate the fault in the following scenarios: RRCconnection setup failure, radio bearer setup failure, physical channel reconfiguration failure, andcell update failure.


LMT User Guide


Issue 03 (2009-04-25)



Context

You can start the Uu interface tracing on the LMT to monitor the interworking of signalingmessages 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. EachUu interface tracing task targets at a maximum of 32 cells. When creating two or more tasks ofthe same type, do not set their parameters completely the same. Otherwise, only one tracing taskcan be created successfully.

Procedure

Step 1 In the navigation pane, click the Maintenance tab, expand the Trace Management > InterfaceTrace 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



12-15

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

----End


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. Ifthe UE accesses the network through DRNC, the DRNC ID is traced. You can query the RNC ID byrunning the command LST RNCBASIC.

l In the message browse window of Uu Interface Tracing task, cell represents the cell that transmits orreceives the message. You can query the cell information by running the command LST CELL.


Related Tasks12.19.1 Browsing an RNC Traced Message Online12.19.2 Querying the Properties of the Tracing Task12.19.3 Viewing a Message Translation12.19.4 Saving an RNC Traced Message


LMT User Guide


Issue 03 (2009-04-25)

12.19.5 Pausing an RNC Tracing Task12.19.6 Resuming an RNC Tracing Task12.19.7 Closing an RNC Tracing Task

Related References12.20.4 Parameter Reference for Uu Interface Tracing

12.6 Tracing UE MessagesThis describes how to monitor the interworking of signaling on the standard interfaces, theinterworking 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 combinationwith the drive test result.



ContextThe UE tracing task is to trace signaling messages of a UE on all the Iu, Iur, Iub and Uu interfacesor 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 > InterfaceTrace Task, and then double-click UE. A dialog box is displayed, as shown in Figure 12-10.



12-17

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 thenclick OK. The displayed message browse window shows the message flow of the UE.

----End

PostrequisiteThe message browse window displays the serial number, generation time, tracing type, subracknumber, slot number, subsystem number, message direction, message type, user ID, and messagecontent, as shown in Figure 12-11.


LMT User Guide


Issue 03 (2009-04-25)

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 RRCCONNECTION REQUEST message from the UE. Then, the UE tracing task traces all the messagesthat 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 theRANAP COMMON ID message but not in the RRC CONNECTION REQUEST message from theUE. If CDT_MSG_FULL_TRACE is set to ON, the UE tracing task traces the messages that are sentafter the RANAP COMMON ID message, and the messages before the RANAP COMMON IDmessage are buffered and reported to the RNC. If CDT_MSG_FULL_TRACE is set to OFF, themessages 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 displayedin 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 Tasks12.19.1 Browsing an RNC Traced Message Online12.19.2 Querying the Properties of the Tracing Task



12-19

12.19.3 Viewing a Message Translation12.19.4 Saving an RNC Traced Message12.19.5 Pausing an RNC Tracing Task12.19.6 Resuming an RNC Tracing Task12.19.7 Closing an RNC Tracing Task

Related References12.20.5 Parameter Reference for UE Tracing

12.7 Tracing IOS MessagesThis describes how to trace a number of calls that meet the sampling criteria within a specifiedrange of cells. When creating the task, you can specify the number of calls to be traced. You canalso specify the messages to be traced by selecting the event type.



Contextl 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 thanN 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 targetsat 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 specifiedperiod of trace time.

When creating a new call tracing task, you can define the sampling criteria by setting theRAB parameter constraints and the RRC Est Cause.

Once the call meets the criteria, the tracing of the call is not stopped even if the RABparameters of the RRC establishment cause are changed during the call. If the initial settingsof 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 criteriaduring 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.

CAUTIONThe IOS tracing task involves a large amount of trace information, which affects the systemoperation. Therefore, Call counts in the IOS Tracing dialog box should not be set too high. Inaddition, you are advised not to trace all events at a time. Furthermore, you should minimize thefrequencies of performing this task.


LMT User Guide


Issue 03 (2009-04-25)

Procedure

Step 1 In the navigation pane, click the Maintenance tab, expand Trace Management > InterfaceTrace Task, and then double-click IOS.

Step 2 In the 12.20.6 Parameter Reference for IOS Tracing dialog box, set the parameters, and thenclick 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 ofa 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 REQUESTmessage 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 RABparameters.

----End



Related References12.20.6 Parameter Reference for IOS Tracing

12.8 Tracing Cell MessagesThis 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 ofno access or low access success rate of the cell, and to collect the user volume in the cell.





12-21

ContextNOTE

l A maximum of six cell tracing tasks can be created at one time. Each cell tracing task targets at onlyone 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 > InterfaceTrace Task, and then double-click Cell.

Step 2 In the 12.20.7 Parameter Reference for Cell Tracing dialog box, set the parameters, and thenclick 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 References12.20.7 Parameter Reference for Cell Tracing

12.9 Tracing REDIRECT MessagesThis describes how to redirect messages that are printed through the serial port of a specifiedsubsystem to the message browse window.




LMT User Guide


Issue 03 (2009-04-25)

Context

CAUTIONFor a subsystem, only one redirect tracing task can be started. When there are many messagesprinted through the serial port, the REDIRECT tracing task may affect the performance of thesystem.

REDIRECT tracing is started on the RNC LMT or M2000. You can use the Trace Viewer toview 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 > InterfaceTrace Task, and then double-click REDIRECT. A dialog box is displayed, as shown in Figure12-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

PostrequisiteThe system displays the details of the traced messages in the message browse window, as shownin Figure 12-13.



12-23

Figure 12-13 Output of REDIRECT tracing

Right-click in the message browse window, and then choose Redirection from the shortcutmenu. The Save in dialog box is displayed, as shown in Figure 12-14.

Figure 12-14 Save dialog box


LMT User Guide


Issue 03 (2009-04-25)



Related References12.20.8 Parameter Reference for REDIRECT Tracing

12.10 Tracing MNCDT MessagesThis describes how to trace the missing neighbor cell relations of a cell. The Missing NeighborCell Detect Trace (MNCDT) tracing task involves three independent detection types: detectionof missing intra-frequency neighboring cell relations, detection of missing inter-frequencyneighboring cell relations, and detection of missing inter-RAT neighboring cell relations.

12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring CellsThis describes how to trace messages of missed intra-frequency neighboring cells in the sameband.

12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring CellsThis describes how to trace messages of missed inter-frequency neighboring cells in differentbands.

12.10.3 Tracing Messages of Missed Inter-RAT Neighboring CellsThis describes how to trace messages of missed inter-RAT neighboring cells in different systems.




12-25

12.10.1 Tracing Messages of Missed Intra-Frequency NeighboringCells

This describes how to trace messages of missed intra-frequency neighboring cells in the sameband.



l The detect switch of the missed intra-frequency neighboring cell tracing is set to ON. (Youcan 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 double-click MNCDT.

Step 2 In the MNCDT Tracing dialog box, set Detection Type to Intra Freq, as shown in Figure12-15. 12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing describes theparameters 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 forIntra-Frequency MNCDT Tracing.

----End


Related References12.20.9 Parameter Reference for Intra-Frequency MNCDT Tracing


LMT User Guide


Issue 03 (2009-04-25)

12.10.2 Tracing Messages of Missed Inter-Frequency NeighboringCells

This describes how to trace messages of missed inter-frequency neighboring cells in differentbands.



l The detect switch of the missed inter-frequency neighboring cell tracing is set to ON. (Youcan 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 double-click MNCDT.

Step 2 In the MNCDT Tracing dialog box, set Detection Type to Inter Freq, and then set theparameters, as shown in Figure 12-16. 12.20.10 Parameter Reference for Inter-FrequencyMNCDT 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.



12-27

NOTE

For the descriptions of the parameters on the output interface, refer to 12.20.10 Parameter Reference forInter-Frequency MNCDT Tracing.

----End


Related References12.20.10 Parameter Reference for Inter-Frequency MNCDT Tracing

12.10.3 Tracing Messages of Missed Inter-RAT Neighboring CellsThis describes how to trace messages of missed inter-RAT neighboring cells in different systems.



l The detect switch of the missed inter-RAT neighboring cell tracing is set to ON. (You canquery this by running LST NCELLDETECTSWITCH.)

ProcedureStep 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 double-click MNCDT.

Step 2 In the MNCDT Tracing dialog box, set Detection Type to Inter RAT, and then set theparameters, as shown in Figure 12-17. 12.20.11 Parameter Reference for Inter-RATMNCDT Tracing describes the parameters for missed inter-RAT neighboring cell tracing.

Figure 12-17 Missed inter-RAT neighboring cell tracing


LMT User Guide


Issue 03 (2009-04-25)

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 forInter-RAT MNCDT Tracing.

----End


Related References12.20.11 Parameter Reference for Inter-RAT MNCDT Tracing

12.11 Tracing OS MessagesThis describes how to trace messages between the exchange module of the BAM and internalmodules of a board or between internal modules of different boards.



ContextIn addition to the messages between different modules, this task can be performed to tracemessages 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 double-click OS.

Step 2 In the 12.20.12 Parameter Reference for OS Tracing dialog box, set the parameters, and thenclick OK. The displayed message browse window shows the traced message flow.

----End





12-29


Related References12.20.12 Parameter Reference for OS Tracing

12.12 Tracing SCCP MessagesThis describes how to monitor the interworking of SCCP messages respectively over the Iu andIur 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 Iuand Iur interfaces.



ContextNOTE

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 > InterfaceTrace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-18.


LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin the Basic tab page. Select SCCP in the Trace Type area. The displayed message browsewindow shows the message flow of the interface.

----End




12-31

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 MessagesThis describes how to trace the MTP3 messages, including the MTP3 upper layer (QAAL2 andSCCP) messages, MTP3 signaling link test messages, and MTP3 signaling network managementmessages.



LMT User Guide


Issue 03 (2009-04-25)


Context

You can perform the MTP3 tracing task to locate the problem that an MTP3B link is unavailablewhen the corresponding SAAL link is available. The method is to check the consistency of theOriginating signaling Point Code (OPC), Destination signaling Point Code (DPC), and SignalingLink 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 > InterfaceTrace Task, and then double-click Iu. A dialog box is displayed, as shown in Figure 12-20.




12-33

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin 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 messagebrowse window shows the related message flow.

----End


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.




LMT User Guide


Issue 03 (2009-04-25)


12.14 Tracing QAAL2 MessagesThis 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 abnormalityof an ATM Adaptation Layer type 2 (AAL2) connection on the user plane respectively on theIu, Iur, and Iub interfaces.



Context

The QAAL2 tracing task helps you to determine whether the near end or the peer end is faultyas follows:

l If the RNC does not send an ESTABLISH_REQUEST message, you can infer that thebandwidth of the near end (RNC) is not enough or the ATM address is not correctlyconfigured.

l If the RNC sends the ESTABLISH_REQUEST message and receives theRELEASE_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 > InterfaceTrace Task, and then double-click Iu.

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin 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. ClickOK. 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




12-35


12.15 Tracing SAAL MessagesThis 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 SAALlink on the Iu, Iur, and Iub interfaces.



ContextNOTE

For each subsystem, a maximum of six SAAL tracing tasks can be performed simultaneously.

Procedure



LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin 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 messagebrowse 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 LSTSAALLNK.

l If there are only outgoing but no incoming RNC messages, you can infer that the PVC is disconnectedor the peer end is not working normally.

----End




12-37

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 MessagesThis 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 problemof non-availability of SCTP link on the Iu, Iur, and Iub interfaces.



LMT User Guide


Issue 03 (2009-04-25)


ContextThe NCP, CCP, or M3UA uses the SCTP link for IP transmission. If the NCP, CCP, or M3UAis not functional, you can start the SCTP tracing task to query the information on the SCTP linkconcerned.

The SCTP link receives and transmits data frequently. Therefore, starting this tracing task mayaffect the performance of the system. You are not advised to start multiple SCTP tracing taskssimultaneously.

NOTE

For each subsystem, a maximum of six SCTP tracing tasks can be performed simultaneously.

Procedure





12-39

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin 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 messagebrowse window shows the related message flow.

NOTE

You can query the link No. and more information about the SCTP link by running the command LSTSCTPLNK.

----End


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 Tasks12.19.1 Browsing an RNC Traced Message Online


LMT User Guide


Issue 03 (2009-04-25)

12.19.2 Querying the Properties of the Tracing Task12.19.3 Viewing a Message Translation12.19.4 Saving an RNC Traced Message12.19.5 Pausing an RNC Tracing Task12.19.6 Resuming an RNC Tracing Task12.19.7 Closing an RNC Tracing Task

12.17 Tracing M3UA MessagesThis describes how to trace the M3UA Messages over the Iu and Iur interfaces. You can performthis task to locate the problem that the M3UA link is unavailable while the corresponding IPlink is available.



ContextThe M3UA tracing is performed to locate the problem that an M3UA link is unavailable whenthe 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 > InterfaceTrace Task, and then double-click Iu.

Step 2 In the 12.20.1 Parameter Reference for Iu Interface Tracing dialog box, set the parametersin 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 messagebrowse 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 thecommand 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




12-41


12.18 Tracing Location MessagesThis describes how to trace the results of a location tracing initiated by the CN. This task canalso simulate the CN to initiate a location tracing and trace the results.



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 TraceManagement node, expand the Location Trace node, and then double-click LocationReporting Control.

Step 2 In the 12.20.13 Paramter Reference for Location Reporting Control dialog box, set theparameters, and then click OK. The displayed message browse window shows the locationmonitoring information and location delay information.

----End

Postrequisite

After the location request is successfully sent, the Location Monitor Info tab page displays thereturned location messages. The Location TimeDelay Info tab page displays the delay fromthe location tracing initiation to location messages acquisition.

NOTE

l Right-click on the Location Monitor Info tab page, and then choose Save as Excel to save the locationresults 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 displayrange to adjust the display range of the Y-coordinate.


LMT User Guide


Issue 03 (2009-04-25)



Related References12.20.13 Paramter Reference for Location Reporting Control

12.19 Basic Operations of RNC Message TracingThis describes how to perform the following operations of RNC message tracing: browsing anRNC traced message online, querying the properties of a tracing task, viewing the translation ofa traced message, saving an RNC traced message, pausing an RNC tracing task, resuming anRNC tracing task, stopping an RNC tracing task, and browsing an RNC traced message offline.

12.19.1 Browsing an RNC Traced Message OnlineThis describes how to browse the traced messages online in the message browse window afterthe tracing task is created.

12.19.2 Querying the Properties of the Tracing TaskThis describes how to query the properties of the tracing task in the message browse window.

12.19.3 Viewing a Message TranslationThis describes how to view the translation of a traced message.

12.19.4 Saving an RNC Traced MessageThis describes how to save an RNC traced message file to the local computer.

12.19.5 Pausing an RNC Tracing TaskThis 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 TaskThis describes how to resume an RNC tracing task when you want to start the tracing task again.

12.19.7 Closing an RNC Tracing TaskThis describes how to close a tracing task to release the system resource when the task is notneeded.

12.19.8 Browsing an RNC Traced Message OfflineThis describes how to use the Trace Viewer to browse offline the traced messages that are savedin .tmf format.

12.19.9 Managing All Tracing Tasks



12-43

This describes how to manage all the tracing tasks after the multiple tasks are created. Themanagement of all the tracing tasks involves stopping all tasks, restarting all tasks, saving allwindow messages, clearing all window messages, and closing all tasks.

12.19.1 Browsing an RNC Traced Message OnlineThis describes how to browse the traced messages online in the message browse window afterthe tracing task is created.

Prerequisitel 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 right-click in the message browse window and then choose an item from the shortcut menu to performthe 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 automaticallyrefreshed 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 oftracing 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.


LMT User Guide


Issue 03 (2009-04-25)

Figure 12-26 Message Browser window

NOTE

For the location tracing, expand the Trace Management node, and then the Location Trace node. SelectLocation Reporting Control.

----End

Related Tasks12.19.8 Browsing an RNC Traced Message Offline

12.19.2 Querying the Properties of the Tracing TaskThis describes how to query the properties of the tracing task in the message browse window.



Procedure

Step 1 Right-click a tracing task in the message browse window, and then choose Property from theshortcut menu.

Step 2 The Trace Property dialog box is displayed, showing the properties of the tracing task.



12-45

Step 3 Click OK.

----End

12.19.3 Viewing a Message TranslationThis describes how to view the translation of a traced message.



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 meaningof the message in protocol translation format.

Step 3 Click on the top right of the window.

----End

12.19.4 Saving an RNC Traced MessageThis describes how to save an RNC traced message file to the local computer.

Prerequisitel A tracing task is started.


Context

The name length (including the extension) of the file storing the tracing results cannot exceed100 characters.

There are two ways of saving tracing results: auto saving and manual saving.

Procedurel Automatically Saving the Traced Messages

When a tracing task is created, the default setting is used to save all messages displayed inthe message browse window in .tmf format.

The default save path is LMT installation directory\client\output\RNC\LMT softwareversion number\trace.


LMT User Guide


Issue 03 (2009-04-25)

NOTE

l The LMT saves every 5,000 messages in a file. From the 5001st message, every 5,000 messagesare saved in the file whose name has a serial number. For example, the default save name of the5001st to 10000th MTP3 messages is office name_MTP3_YYYY-MM-DD-HH-MM-SS_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.

l Manually Saving the Traced Messages

When the tracing task is running, you can manually save all or part of the messages in themessage browse window in .tmf, .txt, or .csv format.

1. Right-click in the message browse window and choose Save All Messages from theshortcut menu; or press and hold down Ctrl or Shift, and then choose the messagesto be saved in the message browse window. Then right-click them and choose SaveSelected Messages from the shortcut menu. The Save dialog box is displayed, asshown in Figure 12-27.


2. Enter a file name, and specify the file type and save path.

The default save path is LMT installation directory\client\output\RNC\LMTsoftware version number\trace. The default file name is office name_tracingtype_YYYY-MM-DD-HH-MM-SS.tmf.

3. Click Save to save the file in the specified path.

----End



12-47

Related Tasks12.19.8 Browsing an RNC Traced Message Offline

12.19.5 Pausing an RNC Tracing TaskThis describes how to pause an RNC tracing task when the tracing task is not needed for a while.

PrerequisiteA tracing task is created.

Procedure

Right-click in the message browse window, and then choose Stop Trace Task from the shortcutmenu to pause the tracing task, as shown in Figure 12-28.

Figure 12-28 Pausing a tracing task

----End

Related Tasks12.19.6 Resuming an RNC Tracing Task

12.19.6 Resuming an RNC Tracing TaskThis 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 shortcutmenu to resume the tracing task, as shown in Figure 12-29.


LMT User Guide


Issue 03 (2009-04-25)

Figure 12-29 Resuming a tracing task

----End

Related Tasks12.19.5 Pausing an RNC Tracing Task

12.19.7 Closing an RNC Tracing TaskThis describes how to close a tracing task to release the system resource when the task is notneeded.

PrerequisiteAn RNC tracing task is running.

ContextYou can select either of the following operations to close the task:

Procedurel Click in the top right corner of the message browse window.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 TraceTasks) from the shortcut menu, as shown in Figure 12-30.

Figure 12-30 Clonging a tracing task



12-49

----End

12.19.8 Browsing an RNC Traced Message OfflineThis describes how to use the Trace Viewer to browse offline the traced messages that are savedin .tmf format.

PrerequisiteThe traced messages are saved in .tmf format.

ContextYou can find the .txt or .csv files in the save directory. You can double-click them to read thetraced messages.

Procedure

Step 1 Select either of the following ways to start the Trace Viewer:

l Click on the toolbar in the Local Maintenance Terminal window.

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


LMT User Guide


Issue 03 (2009-04-25)

Step 2 Select the file that saves the traced messages. The default save path for the files is LMTinstallation 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 thefile, 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.



12-51

Figure 12-33 Message Browser window

Step 5 To browse other saved messages, choose File > Open. In the Open dialog box, select and openfiles 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 theshortcut menu,

All the messages are saved in the windowin .tmf or .txt format.

You choose Save Selected Messages fromthe shortcut menu,

The selected messages are saved in .tmf or .txtformat.

You choose Filter from the shortcut menu, Set the filter to selectively display theinformation.

You choose Filter By Column from theshortcut menu,

Filter the information by column to selectivelydisplay the information.

You choose Find from the shortcut menu, Locate the message that you want.

You choose Properties from the shortcutmenu,

View the properties of the task that the tracingresult corresponds to.


LMT User Guide


Issue 03 (2009-04-25)

If... Then...

You click any column name, The messages in the window are sequenced byNo., time, subrack No., direction, DPC, orcontent.

----End

Related Tasks12.19.1 Browsing an RNC Traced Message Online12.19.4 Saving an RNC Traced Message

12.19.9 Managing All Tracing TasksThis describes how to manage all the tracing tasks after the multiple tasks are created. Themanagement of all the tracing tasks involves stopping all tasks, restarting all tasks, saving allwindow messages, clearing all window messages, and closing all tasks.

Prerequisitel One or more tracing tasks are created.


Procedurel Stopping all tracing tasks

1. Choose Trace Management > Stop All Tasks. A Confirmation dialog box isdisplayed.

2. Click Yes to stop all the tracing tasks.l Restarting all tracing tasks

1. Choose Trace Management > Restart All Tasks. A Confirmation dialog box isdisplayed.

2. Click Yes to restart all the tracing tasks.l Saving all window messages

1. Choose Trace Management > Save All Window Messages. A Confirmation dialogbox is displayed.

2. Click Yes. A Select Folder dialog box is displayed. The default save path is LMTinstallation directory\client\output\RNC\LMT software version number\trace. Thedefault file name is office name_tracing type_YYYY-MM-DD-HH-MM-SS.tmf.

l Clearing all window messages1. Choose Trace Management > Clear All Window Messages. A Confirmation

dialog box is displayed.2. Click Yes to clear all the window messages.

l Closing all tracing tasks1. Choose Trace Management > Close All Tasks. A Confirmation dialog box is

displayed.



12-53

2. Click Yes to close all the tracing tasks.

----End

12.20 Parameter Reference for RNC Message Tracing andViewing

This describes the parameters used for each message tracing.

12.20.1 Parameter Reference for Iu Interface TracingThis describes the parameters used for Iu interface tracing.

12.20.2 Parameter Reference for Iur Interface TracingThis describes the parameters used for Iur interface tracing.

12.20.3 Parameter Reference for Iub Interface TracingThis describes the parameters used for Iub interface tracing.

12.20.4 Parameter Reference for Uu Interface TracingThis describes the parameters used for Uu interface tracing.

12.20.5 Parameter Reference for UE TracingThis describes the parameters used for UE tracing.

12.20.6 Parameter Reference for IOS TracingThis describes the parameters used for IOS tracing.

12.20.7 Parameter Reference for Cell TracingThis describes the parameters used for cell tracing.

12.20.8 Parameter Reference for REDIRECT TracingThis describes the parameters used for REDIRECT tracing.

12.20.9 Parameter Reference for Intra-Frequency MNCDT TracingThis describes the parameters on the input and output GUIs of intra-frequency MNCDT tracing.

12.20.10 Parameter Reference for Inter-Frequency MNCDT TracingThis describes the parameters on the input and output GUIs of inter-frequency MNCDT tracing.

12.20.11 Parameter Reference for Inter-RAT MNCDT TracingThis describes the parameters on the input and output GUIs of inter-RAT MNCDT tracing.

12.20.12 Parameter Reference for OS TracingThis describes the parameters used for OS tracing.

12.20.13 Paramter Reference for Location Reporting ControlThis describes the parameters used for location reporting control.

12.20.1 Parameter Reference for Iu Interface TracingThis describes the parameters used for Iu interface tracing.


LMT User Guide


Issue 03 (2009-04-25)

Item Field Description

Basic Active SPUsubsystem(Subrack No.-Slot No.-Subsystem No.)

In this area, you can select the SPU subsystem whose messageflow to be traced.

DPCConfiguration

In this area, you can select either All DPC or specified DPCas 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 theBasic tab page.

Autosave toFile

In this area, you can set whether to automatically save the traceresults.

File name In this field, you can specify the file name and save path forthe trace results. The default save path is LMT installationdirectory\client\output\RNC\LMT software version number\trace. The default file name is office name_Iu_YYYY-MM-DD-HH-MM-SS.tmf.

Iu Iu MessageType

In this area, you can select the type of Iu 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.

MTP3 MTP3 MessageType

In this area, you can select the type of MTP3 messages to betraced.If you select MTP3 in the Trace Type area on the Basic tabpage, the parameters on the MTP3 tab page are required.

QAAL2 TraceConfiguration

In this area, you can select the QAAL2 trace type and set therequired parameters if any.If you select QAAL2 in the Trace Type area on the Basic tabpage, the parameters on the QAAL2 tab page are required.

SAAL ParameterConfiguration

In this area, you can specify the number of the SAAL to betraced. The value range of the SAAL link No. is 0 to 699.If you select SAAL in the Trace Type area on the Basic tabpage, the parameters on the SCTP tab page are required.

SAAL MessageType

In this area, you can select the type of SAAL messages to betraced.

SCTP ParameterConfiguration

In this area, you can specify the number of the SCTP link tobe 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 tabpage, the parameters on the SCTP tab page are required.



12-55


SCTP MessageType

In this area, you can select the type of SCTP messages to betraced.

M3UA ParameterConfiguration

In this area, you can select the M3UA trace type. If you tracethe M3UA messages of a link set, you must set the linkset No.(value range: 0 to 150). If you trace the M3UA messages of aspecified 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 tabpage, the parameters on the M3UA tab page are required.

M3UAMessage Type

In this area, you can select the type of M3UA messages to betraced.

Related Tasks12.2 Tracing Iu Interface Messages

12.20.2 Parameter Reference for Iur Interface TracingThis describes the parameters used for Iur interface tracing.


Basic Active SPUsubsystem(Subrack No.-Slot No.-Subsystem No.)


DPCConfiguration

You can select Trace All DPCs or Trace Specified DPC toperform 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 theBasic tab page.

Autosave toFile


File name In this field, you can specify the file name and save path forthe trace results. The default save path is LMT installationdirectory\client\output\RNC\LMT software version number\trace. The default file name is office name_Iur_YYYY-MM-DD-HH-MM-SS.tmf.

Iur Iur MessageType

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.


LMT User Guide


Issue 03 (2009-04-25)


MTP3 MTP3 MessageType

In this area, you can select the type of MTP3 messages to betraced.If you select MTP3 in the Trace Type area on the Basic tabpage, the parameters on the MTP3 tab page are required.





SAAL MessageType


SCTP Trace DPCconfiguration


SCTP MessageType


M3UA ParameterConfiguration

In this area, you can select the M3UA trace type. If you tracethe M3UA messages of a link set, you must set the linkset No.(value range: 0 to 150). If you trace the M3UA messages of aspecified 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 tabpage, the parameters on the M3UA tab page are required.

M3UAMessage Type

In this area, you can select the type of M3UA messages to betraced.

Related Tasks12.3 Tracing Iur Interface Messages

12.20.3 Parameter Reference for Iub Interface TracingThis describes the parameters used for Iub interface tracing.



12-57


Active SPUsubsystem(Subrack No.-Slot No.-Subsystem No.)


Trace Type You can select one or multiple tracing types, including Iub,SAAL, and SCTP.

Autosave to File In this area, you can set whether to automatically save the traceresults.

File name In this field, you can specify the file name and save path forthe trace results. The default save path is LMT installationdirectory\client\output\RNC\LMT software versionnumber\trace. The default file name is officename_Iub_YYYY-MM-DD-HH-MM-SS.tmf.

Iub ParameterConfiguration

In this area, you can select the Iub trace type and set therequired 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.

Iub MessageType

In this area, you can select the type of Iub messages to betraced.



SAAL MessageType


SCTP ParameterConfiguration


SCTP MessageType




Related Tasks12.4 Tracing Iub Interface Messages


LMT User Guide


Issue 03 (2009-04-25)

12.20.4 Parameter Reference for Uu Interface TracingThis 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 theUu interface.

Autosave to File In this area, you can set whether to automatically save thetrace results.

File name In this field, you can specify the file name and save path forthe trace results. The default save path is LMT installationdirectory\client\output\RNC\LMT software versionnumber\trace. The default file name is officename_Uu_YYYY-MM-DD-HH-MM-SS.tmf.

Related Tasks12.5 Tracing Uu Interface Messages

12.20.5 Parameter Reference for UE TracingThis describes the parameters used for UE tracing.

Field Description

UE IMSI These are used to identify the UE. You can choose totrace 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), andMobile Network Code (MNC) are required.

l If you trace a UE by the P-TMSI, the LAC, RoutingArea Code (RAC), MCC, and MNC are required.

IMEI

TMSI

P-TMSI

Autosave to File In this area, you can set whether to automatically savethe trace results.

File name In this field, you can specify the file name and savepath for the trace results. The default save path is LMTinstallation directory\client\output\RNC\LMTsoftware version number\trace. The default filename is office name_UE_YYYY-MM-DD-HH-MM-SS.tmf.

Iur Iur Message Type You can select the types of the Iur messages to betraced on this tab page. You may select all types orselect some of them.



12-59

Field Description

Iub Iub Message Type You can select the types of the Iub messages to betraced on this tab page. You may select all types orselect some of them.

Iu Iu Message Type You can select the types of the Iu messages to betraced on this tab page. You may select all types orselect some of them.

Uu Uu Message Type You can select the types of the Uu messages to betraced on this tab page. You may select all types orselect some of them.

Monitor Monitor Config This is used to select the UE connection performancefor monitoring. You can monitor the UL SIR, transmitpower, DL block error rate (BLER), DL code transmitpower, PCPICH Ec/No and RSCP, AMR mode,received total wideband power (RTWP), and transmitcarrier power of a UE identified by the P-TMSI,TMSI, or IMEI.

Related Tasks12.6 Tracing UE Messages

12.20.6 Parameter Reference for IOS TracingThis describes the parameters used for IOS tracing.


Basic Callscount

To set the maximum number of the calls to be traced at the same timeafter 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 messagesrelated to the calls.NOTE

You can choose to Select All, Select None, or Select Default as required.

Autosaveto 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 traceresults. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default filename is office name_IOS_YYYY-MM-DD-HH-MM-SS.tmf.

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


LMT User Guide


Issue 03 (2009-04-25)


RRC This is used to set the RRC parameters for IOS tracing, for example,the parameters in the strMeasurePeriods area and in the Traffictype area.

Related Tasks12.7 Tracing IOS Messages

12.20.7 Parameter Reference for Cell TracingThis describes the parameters used for cell tracing.

Field Description

CELL Cell ID This is used to specify the cell ID.

USER_VOLUMEPROPAGATION_DELAY

You can choose the events to be traced: USER_VOLUME orPROPAGATION_DELAY. To trace the UE statisticalinformation including the custom messages, selectUSER_VOLUME (value range: 1,000 to 10,000; unit: 10 ms).To trace the propagation delays, selectPROPAGATION_DELAY (value range: 1 to 80; unit: times).NOTE

l When you create a CELL tracing task, USER_VOLUME is selectedand set to 1000 by default.

l When you create a CELL tracing task, PROPAGATION_DELAYis selected and set to 1 by default.

Autosave toFile


File name In this field, you can specify the file name and save path for thetrace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. Thedefault file name is office name_CELL_YYYY-MM-DD-HH-MM-SS.tmf.

FMR strFMRTrcEvent

You can select either Perodically Data Report or CCCH DataFrame Report.

SCCPCHID

This is used to specify the IDs of the SCCPCHs to be traced. Youcan choose to trace two SCCPCHs at the same time by specifyingtwo SCCPCH IDs.

ReportPeriod(100ms)

If you choose Periodically Data Report, you must set theReport Period(100 ms).

IUB Trace Type This is used to specify the messages to be traced on the Iubinterface.



12-61

Related Tasks12.8 Tracing Cell Messages

12.20.8 Parameter Reference for REDIRECT TracingThis describes the parameters used for REDIRECT tracing.

Field Description

Subrack No. This is used to specify the number of thesubrack to be redirected. Value range: 0 to 5.

Slot No. This is used to specify the number of the slotto be redirected. Value range: 0 to 27.

Subsystem No. This is used to specify the number of thesubsystem to be redirected. Value range: 0 to3.

CAUTIONThe OMUa does not support the COM port REDIRECT tracing. Therefore, slots 20 to 23 areunavailable when subrack 0 is selected.

Related Tasks12.9 Tracing REDIRECT Messages

12.20.9 Parameter Reference for Intra-Frequency MNCDT TracingThis 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 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 traceresults. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name isoffice name_MNCDT_YYYY-MM-DD-HH-MM-SS.tmf.

Parameters on the Output GUITable 12-3 describes the parameters on the output GUI of intra-frequency MNCDT tracing.


LMT User Guide


Issue 03 (2009-04-25)

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 firstID in the array corresponds to the best cell.

ucDetectCellNum Number of missing neighboring cells

ausSrimbleCode Scrambling code array of the missing neighboring cells

Related Tasks12.10.1 Tracing Messages of Missed Intra-Frequency Neighboring Cells

12.20.10 Parameter Reference for Inter-Frequency MNCDT TracingThis describes the parameters on the input and output GUIs of inter-frequency MNCDT tracing.


Table 12-4 describes the parameters on the input GUI of inter-frequency MNCDT tracing.


Field Description

Uplink UARFCN This is used to specify the uplink (UL) frequency of the cell to be traced.

DownlinkUARFCN

This is used to specify the downlink (DL) frequency of the cell to betraced.

Start of PrimaryScrambling Code

This is used to specify the minimum scrambling code for MNCDTtracing.

End of PrimaryScrambling Code

This is used to specify the maximum scrambling code for MNCDTtracing.NOTE

The end of the primary scrambling code is not less than the start of the primaryscrambling code.


File name In this field, you can specify the file name and save path for the traceresults. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default filename 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.



12-63


Field Description

ulRnti User ID

ucActSetNum Number of active sets

ausActCellId Array of the IDs of the cells in the active set. The firstID 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 Tasks12.10.2 Tracing Messages of Missed Inter-Frequency Neighboring Cells

12.20.11 Parameter Reference for Inter-RAT MNCDT TracingThis describes the parameters on the input and output GUIs of inter-RAT MNCDT tracing.


Table 12-6 describes the parameters on the input GUI for inter-RAT MNCDT tracing.


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 valueof 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 ofthe start BCC should be greater than that of the end BCC.

BandIndicator

Band in which the ARFCN is used (DCS 1800 or PCS 1900)

Start ofBCCHARFCN

Minimum ARFCN for MNCDT tracing

End ofBCCHARFCN

Maximum ARFCN for MNCDT tracing


LMT User Guide


Issue 03 (2009-04-25)

Autosave toFile

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


Field Description

ucNcc Network color code of the missing inter-RATneighboring cell

ucBcc Base station color code of the missing inter-RATneighboring cell

ucInterRatBandInd Band indicator of the missing inter-RAT neighboringcell

usInterRatArfcn ARFCN of the missing inter-RAT neighboring cell

Related Tasks12.10.3 Tracing Messages of Missed Inter-RAT Neighboring Cells

12.20.12 Parameter Reference for OS TracingThis describes the parameters used for OS tracing.

Field Description

Trace Type You can specify whether to trace the OS messages by the senderor by the receiver.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.

SenderParameter

IP Type This is used to specify the IP type of the sender. You can selectone 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 theBAM.

l Specified IP. The receiver traces only the messages sent fromthe specified IP.



12-65

Field Description

ModuleName

This is used to specify the module name of the sender.

ReceiverParameter

IP Type This is used to specify the IP type of the receiver. You can selectone from the following types: 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 thespecified IP.

ModuleName

This is used to specify the module name of the receiver.

Autosave to File In this area, you can set whether to automatically save the traceresults.

File name In this field, you can specify the file name and save path for thetrace results. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. Thedefault file name is office name_OS_YYYY-MM-DD-HH-MM-SS.tmf.

Related Tasks12.11 Tracing OS Messages

12.20.13 Paramter Reference for Location Reporting ControlThis describes the parameters used for location reporting control.

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

HorizontalAccuracy Code(m)

This is used to specify the required horizontal accuracy of the reportedresults. Its value range is: 0 to 1,800,000.

PositioningInterval(10s)

This is used to specify the time interval between two location requests. Itsvalue range is: 0 to 1,440 (unit: 10s).


LMT User Guide


Issue 03 (2009-04-25)

Field Description

VerticalAccuracy 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 locationprotection timer.

PositioningPriority

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.


File name In this field, you can specify the file name and save path for the traceresults. The default save path is LMT installation directory\client\output\RNC\LMT software version number\trace. The default file name isoffice name_Location_Reporting_Control_YYYY-MM-DD-HH-MM-SS.tmf.

Related Tasks12.18 Tracing Location Messages



12-67

13 RNC Real-Time PerformanceMonitoring

About This Chapter

This describes how to monitor RNC performance in real time.

13.1 Concepts of RNC Real-Time Performance MonitoringThis 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 OccupancyThis describes how to monitor the RNC CPU/DSP usage. By performing this task, you can learnabout the usage of the CPU/DSP resources.

13.3 Monitoring the RNC Connection PerformanceThis describes how to monitor the connection state of the physical links during a conversationof a UE. For the same monitoring item, the LMT can perform a maximum of six monitoringtasks simultaneously.

13.4 Monitoring the RNC Cell PerformanceThis describes how to monitor the cell performance, such as the common measured value andnumber of common channel users. For the same monitoring item, you can start at most six taskssimultaneously.

13.5 Monitoring the RNC Link PerformanceThis describes how to monitor the RNC link performance. This task applies to the traffic statisticsbased on IP path/SCTP/OAM stream, statistics based on priority queues. The statistics based onpriority queues include the statistics of packet loss rate, number of the sent packets, and numberof the sent bytes. For the same monitoring item, you can start up to six tasks.

13.6 Monitoring the RNC Board ResourceThis describes how to monitor licensed traffic volume for voice services and the PS domain datathroughput on the user plane of a specified board in real time.

13.7 Basic RNC Real-Time Performance Monitoring OperationsThis describes how to perform basic operations after an RNC real-time performance monitoringtask is started.

13.8 Parameter Reference for RNC Real-Time Performance Monitoring

RNCLMT User Guide 13 RNC Real-Time Performance Monitoring


13-1

This describes the parameters used for each performance monitoring.

13 RNC Real-Time Performance MonitoringRNC

LMT User Guide


Issue 03 (2009-04-25)

13.1 Concepts of RNC Real-Time Performance MonitoringThis 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 MonitoringThe RNC real-time performance monitoring function provides the display of CPU/DSP usagemonitoring, connection/cell/link performance monitoring, and board resource monitoring incharts and lists to monitor the status of the current system devices and services. During themonitoring, the abnormalities are analyzed to maintain the devices and clear faults.13.1.2 Working Principles of RNC Real-Time Performance MonitoringThe working principle of CPU/DSP usage monitoring is different from that of the other typesof real-time monitoring.13.1.3 Authority of the RNC Real-Time Performance MonitoringYou can perform the real-time performance monitoring operations only when you are authorizedfor these operations.

13.1.1 Introduction to RNC Real-Time Performance MonitoringThe RNC real-time performance monitoring function provides the display of CPU/DSP usagemonitoring, connection/cell/link performance monitoring, and board resource monitoring incharts and lists to monitor the status of the current system devices and services. During themonitoring, the abnormalities are analyzed to maintain the devices and clear faults.

The RNC monitors the following items in real time:l CPU/DSP usagel Connection performancel Cell performancel Link performancel Board resource

13.1.2 Working Principles of RNC Real-Time PerformanceMonitoring

The working principle of CPU/DSP usage monitoring is different from that of the other typesof real-time monitoring.

Working Principle of CPU/DSP Usage MonitoringFigure 13-1 shows the working principle of CPU/DSP usage monitoring.

Figure 13-1 CPU/DSP usage monitoring



13-3

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 sendsa binary command querying CPU/DSP usage to the maintenance module of the BAM everyfive seconds.

2. The BAM sends the corresponding command to the maintenance and configuration moduleof 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 MonitoringThe working principle of connection/cell/link performance monitoring is almost the same. SeeFigure 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 asfollows:

1. The operator creates a monitoring task on the LMT. Then, the LMT sends a binarycommand to the BAM to create the task.

2. The BAM assigns a number to the task and sends the command to the debugging moduleof the specified board.

3. After receiving the command, the commissioning module records the filter parameters inthe filter table and notifies the service module.

4. The service module updates the local filter table according to the messages from thecommissioning 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 commandto 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:


LMT User Guide


Issue 03 (2009-04-25)

1. The service module filters the collected data according to the filter parameters in the localfilter 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 MonitoringYou can perform the real-time performance monitoring operations only when you are authorizedfor these operations.

Operators of the following levels can perform the real-time performance monitoring tasks:admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use commandgroup G_10.

That is, except GUEST-level and CUSTOM not entitled to use command group G_10, all theother 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 noMML commands.

Related Tasks13.2 Monitoring the RNC CPU/DSP Occupancy13.3 Monitoring the RNC Connection Performance13.4 Monitoring the RNC Cell Performance13.5 Monitoring the RNC Link Performance13.6 Monitoring the RNC Board Resource

13.2 Monitoring the RNC CPU/DSP OccupancyThis describes how to monitor the RNC CPU/DSP usage. By performing this task, you can learnabout the usage of the CPU/DSP resources.


l You have logged in to the RNC with an account authorized for the real-time performancemonitoring.

l The monitored board works properly.

ContextNOTE

The LMT can open only one window for CPU/DSP usage monitoring. If the window is open, you can addmonitoring tasks for more boards in this CPU/DSP Usage window. The LMT can perform a maximum of10 monitoring tasks simultaneously.

In the Local Maintenance Terminal window, check the Window menu to see whether theCPU/DSP Usage window is open or not. If yes, add CPU usage monitoring tasks or delete CPUusage monitoring tasks. If no, starting CPU usage monitoring tasks.



13-5

Procedurel 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 isdisplayed, as shown in Figure 13-3.

Figure 13-3 Add Tasks dialog box

3. 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 (asshown in Figure 13-4) or chart (as shown in Figure 13-5). You can repeat this stepto create monitoring tasks for more boards.


LMT User Guide


Issue 03 (2009-04-25)

Figure 13-4 CPU/DSP Usage monitoring window in a list

Figure 13-5 CPU/DSP Usage monitoring window in a chart



13-7

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. Click Close to close the Add Task dialog box.l Querying properties of CPU/DSP usage monitoring tasks

1. In the task information pane at the bottom of the CPU/DSP Usage window, select themonitoring task to be queried.

2. Right-click the monitoring task to be queried in the task information pane and chooseProperties from the shortcut menu, as shown in Figure 13-6. The MonitorProperties dialog box is displayed, showing the properties of the task.

Figure 13-6 Querying properties of a CPU/DSP usage monitoring task

----End

Related Concepts13.1.3 Authority of the RNC Real-Time Performance Monitoring

Related Tasks13.7.1 Browsing the RNC Monitoring Results Online13.7.2 Switching the Display Mode13.7.3 Setting the Default Display Mode13.7.4 Editing the Display Mode for the Chart13.7.5 Saving RNC Monitoring Results13.7.6 Pausing and Resuming an RNC Monitoring Task13.7.7 Adding an RNC CPU/DSP Monitoring Task13.7.8 Deleting an RNC CPU/DSP Monitoring Task13.7.9 Stopping an RNC Monitoring Task13.7.10 Browsing RNC Monitoring Results Offline

13.3 Monitoring the RNC Connection PerformanceThis describes how to monitor the connection state of the physical links during a conversationof a UE. For the same monitoring item, the LMT can perform a maximum of six monitoringtasks simultaneously.


LMT User Guide


Issue 03 (2009-04-25)

13.3.1 Monitoring P-CPICH Ec/No and RSCPThis 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 displayedin a chart. By performing this task, you can learn about whether the current connection is at theedge or the center of the cell.

13.3.2 Monitoring the SIR Measurement Values of UL RLSsThis describes how to monitor in real time the Signal-Interference Ratio (SIR) measurementvalues of the UL RLSs of the current connection. By performing this task, you can analyze thequality of UL radio links and the quality variation.

13.3.3 Monitoring the Enhanced Outer Loop Power ControlThis describes how to monitor the enhanced outer loop power control. Monitoring the enhancedouter 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 theUL transport channel, E-DCH average times of retransmission, and E-DCH retransmissionprobability.

13.3.4 Monitoring the SIR Error Values of UL RLSsThis 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 keepup 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 innerloop power control converges. Otherwise, the UL inner loop power control does not converge.

13.3.5 Monitoring DL Code TX PowerThis describes how to monitor the variation of the DL code TX power of each radio link of thecurrent connection in real time. By performing this task, you can analyze the DL powerconsumption. If the downlink code TX power increases, even approximating to the maximumvalue configured in the signaling message, the quality of this radio link declines.

13.3.6 Monitoring the UE TX PowerThis describes how to monitor in real time the variation of the UE TX power of the currentconnection. By performing this task, you can analyze the UL quality. If the UE TX powerincreases, even reaching the limit of the UE capability, the UL quality declines.

13.3.7 Monitoring UL TrafficThis 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 performanceof the UL traffic. The UL traffic is measured by the UE and reported to the RNC per transportchannel.

13.3.8 Monitoring DL TrafficThis describes how to monitor the DL traffic (that is, data buffer size on the network side) ofthe current connection. By performing this task, you can analyze the transmission performanceof the DL traffic. The DL traffic is measured at the RNC per transport channel.

13.3.9 Monitoring UL Throughput and BandwidthThis describes how to monitor in real time the rate variation of the UL transport access stratumand non-access stratum of the current connection. By performing this task, you can analyze thedynamic channel configuration function and service source rate variation characteristics.

13.3.10 Monitoring DL Throughput and Bandwidth



13-9

This describes how to monitor in real time the rate variation of the DL transport access stratumand non-access stratum of the current connection. By performing this task, you can analyze thedynamic channel configuration function and service source rate variation characteristics.

13.3.11 Monitoring Handover DelayThis describes how to monitor the handover delay performance. By performing this task, youcan observe and obtain the time taken by each handover of the current connection. The handoverincludes intra-frequency soft handover and inter-frequency handover.

13.3.12 Monitoring the BLER of the DL Transport ChannelThis describes how to monitor the variation of the BLER on all transport channels of the currentconnection. By performing this task, you can analyze the DL quality. If the BLER of the DLtransport 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 ModeThis describes how to monitor the variation of the AMR rate configured by the UE and to recordthe variation in real time.



13.3.1 Monitoring P-CPICH Ec/No and RSCPThis 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 displayedin a chart. By performing this task, you can learn about whether the current connection is at theedge or the center of the cell.




LMT User Guide


Issue 03 (2009-04-25)

Context

CAUTIONBefore running this monitoring task, you need to perform one of the following operations:

l Run SET CORRMALGOSWITCH to set Handover algorithm switch. Ensure thatSOFT_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 isstopped if the monitored connection is released or transited from the dedicated channel to the commonchannel. The task is restarted if the monitored connection is transited from the common channel backto 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 othercells is not reported. Therefore, the monitoring results reflect the variation of the number of cells inthe 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 PerformanceMonitoring node, and then double-click Connection performance monitoring. A dialog boxfor 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, setMonitor item to PCPICH EcNo&RSCP, and then set Monitor period(s) and IMSI.



13-11

NOTE

If Monitor period(s) is set too short, a large amount of reported data increases the overhead of signalingtransport and system processing, which has influence on the CPU usage of the RNC. You are advised toset Monitor period(s) to 0.5s.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_PCPICH EcNo&RSCP_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.

Step 4 Click OK. The monitoring is started.

----End

PostrequisiteA 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, thetime 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 reportedP-CPICH Ec/No (unit: dB) and RSCP (unit: dBm).

l RSCP stands for Received Signal Code Power. It is the received power on one codemeasured on the P-CPICH. The reference point for measurement of the RSCP is at theantenna connector of the UE. If the P-CPICH uses transmit diversity, you need to measurethe RSCP of each antenna and sum up all of the RSCP values. Then you can obtain thetotal 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 isalso at the antenna connector of the UE. If the P-CPICH uses transmit diversity, you needto measure the Ec of each antenna and sum up all of the Ec values. Then, you can calculatethe Ec/No.

Related References13.8.2 Parameter Reference for Connection Performance Monitoring

13.3.2 Monitoring the SIR Measurement Values of UL RLSsThis describes how to monitor in real time the Signal-Interference Ratio (SIR) measurementvalues of the UL RLSs of the current connection. By performing this task, you can analyze thequality of UL radio links and the quality variation.




LMT User Guide


Issue 03 (2009-04-25)

ContextNOTE

Each task can monitor only one UE. The monitoring result, including the number of cells in the active setand the signal strength of each cell, is displayed in a chart. By performing this task, you can learn aboutwhether the current connection is at the edge or the center of the cell.

Procedure



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_UL SIR_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End

PostrequisiteA 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 ofthe number of the RLSs in real time.



13-13

In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedSIR 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 receivedinterference 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 theNodeB. In compressed mode, do not measure the SIR in the transmission gap. The measurementvalues of UL SIR are reported to the RNC by the NodeB.


13.3.3 Monitoring the Enhanced Outer Loop Power ControlThis describes how to monitor the enhanced outer loop power control. Monitoring the enhancedouter 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 theUL transport channel, E-DCH average times of retransmission, and E-DCH retransmissionprobability.



Procedure



LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 signalingtransport and system processing, which has influence on the CPU usage of the RNC. You are advisedto set Monitor period(s) to 0.5.

l If you set Monitor period(s) to OLPC, the measurement periods is consistent with the OLPCadjustment period.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_OLPC_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End

Postrequisite

The real-time monitoring window is displayed, showing real-time monitoring results in list andchart. 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 correspondsto 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 Y-coordinate 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 ofretransmission and E-DCH retransmission probability. The left Y-coordinate represents the



13-15

E-DCH average times of retransmission (range: 0 to 16, unit: none). The right Y-coordinaterepresents the E-DCH retransmission probability (range: 0 to 1, unit: none).


13.3.4 Monitoring the SIR Error Values of UL RLSsThis 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 keepup 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 innerloop power control converges. Otherwise, the UL inner loop power control does not converge.



ContextThis task applies to only monitoring connections established on dedicated channels. A startedtask is stopped if the monitored connection is released or transited from the dedicated channelto the common channel. The task is restarted if the monitored connection is transited from thecommon channel back to the dedicated channel.

Procedure




LMT User Guide


Issue 03 (2009-04-25)

Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 signalingtransportation and system processing, which affects the CPU usage of the RNC. You are advised to setMonitor period(s) to 0.5.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance 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 variationof 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, thetime 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 reportedSIR error values (SIRerror) of the UL RLSs.

l SIRerror (unit: dB) is reported to the RNC by the NodeB. The calculation formula isSIRerror = SIR - SIRtarget_ave.

l Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to thetime for calculating the SIR in the above formula of SIRerror.

l In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave in the transmissiongap is not calculated. The average of SIRtarget is an arithmetical average. The unit ofSIRtarget_ave is dB.


13.3.5 Monitoring DL Code TX PowerThis describes how to monitor the variation of the DL code TX power of each radio link of thecurrent connection in real time. By performing this task, you can analyze the DL powerconsumption. If the downlink code TX power increases, even approximating to the maximumvalue configured in the signaling message, the quality of this radio link declines.





13-17

ContextThis task applies to only monitoring connections established on dedicated channels. A startedtask is stopped if the monitored connection is released or transited from the dedicated channelto the common channel. The task is restarted if the monitored connection is transited from thecommon channel back to the dedicated channel.

Procedure



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_DL Tx Code Power_YYYY-MM-DD-HH-MM-SS_IMSI-IMSIvalue.


----End


LMT User Guide


Issue 03 (2009-04-25)

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 ofthe 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, thetime 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 reportedDL code TX power (unit: dBm).

Code TX power refers to the NodeB TX power on one channelization code that is on one givenscrambling code on one given carrier. The DL code TX power can be measured on the DPCCHof 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 theDL code TX power.


13.3.6 Monitoring the UE TX PowerThis describes how to monitor in real time the variation of the UE TX power of the currentconnection. By performing this task, you can analyze the UL quality. If the UE TX powerincreases, even reaching the limit of the UE capability, the UL quality declines.



Context

UE TX power refers to the UE TX power in a carrier. The reference point for measurement ofthe UE TX power is at the antenna connector of the UE.

This task applies to only monitoring connections established on dedicated channels. A startedtask is stopped if the monitored connection is released or transited from the dedicated channelto the common channel. The task is restarted if the monitored connection is transited from thecommon channel back to the dedicated channel.

Procedure




13-19


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_UE TxPower_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End


In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedUE TX power (unit: dBm).


13.3.7 Monitoring UL TrafficThis 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


LMT User Guide


Issue 03 (2009-04-25)

of the UL traffic. The UL traffic is measured by the UE and reported to the RNC per transportchannel.



ContextTraffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to betransmitted 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 transmitwindow and excludes the PDUs transmitted but not acknowledged.

This task can monitor the connections of PS domain interactive and background services on bothcommon channels and dedicated channels.

Procedure



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC



13-21

\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_UL Traffic Vol_YYYY-MM-DD-HH-MM-SS_IMSI-IMSIvalue.


----End


In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedUL traffic on the UL physical channel (unit: byte).


13.3.8 Monitoring DL TrafficThis describes how to monitor the DL traffic (that is, data buffer size on the network side) ofthe current connection. By performing this task, you can analyze the transmission performanceof the DL traffic. The DL traffic is measured at the RNC per transport channel.



ContextTraffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to betransmitted 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 transmitwindow and excludes the PDUs transmitted but not acknowledged.


Procedure



LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_DL Traffic Vol_YYYY-MM-DD-HH-MM-SS_IMSI-IMSIvalue.


----End


In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedDL traffic (unit: byte).




13-23

13.3.9 Monitoring UL Throughput and BandwidthThis describes how to monitor in real time the rate variation of the UL transport access stratumand non-access stratum of the current connection. By performing this task, you can analyze thedynamic channel configuration function and service source rate variation characteristics.



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 calculatedaccording to RLC payload. The bandwidth changes in RB reconfiguration. The throughputmeasurement involves RLC headers, and therefore, the measured peak throughput is higher thanthe bandwidth.


Procedure



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor item to UL Throughput & Bandwidth, and then set Monitor period(s) and IMSI.


LMT User Guide


Issue 03 (2009-04-25)

NOTE


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_UL Throughput & Bandwidth_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----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, thetime 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 reportedUL throughput and UL bandwidth (unit: bit/s).

l When verifying the dynamic channel configuration function, observe the variation of ULthroughput and UL bandwidth. If the UL bandwidth increases or decreases with the ULthroughput, 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 ratevariation characteristics of UL service source by observing the variation of UL throughput.


13.3.10 Monitoring DL Throughput and BandwidthThis describes how to monitor in real time the rate variation of the DL transport access stratumand non-access stratum of the current connection. By performing this task, you can analyze thedynamic channel configuration function and service source rate variation characteristics.



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 calculatedaccording to RLC payload. The bandwidth changes in RB reconfiguration. The throughputmeasurement involves RLC headers, and therefore, the measured peak throughput is higher thanthe bandwidth.



13-25


ProcedureStep 1 In the navigation pane, click the Maintenance tab, expand the Realtime Performance

Monitoring node, and then double-click Connection performance monitoring. A dialog boxfor setting the parameters is displayed, as shown in Figure 13-16.


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_DL Throughput & Bandwidth_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End


In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedDL throughput and DL bandwidth (unit: bit/s).


LMT User Guide


Issue 03 (2009-04-25)

l When verifying the dynamic channel configuration function, observe the variation of DLthroughput and DL bandwidth. If the DL bandwidth increases or decreases with the DLthroughput, 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 ratevariation characteristics of DL service source by observing the variation of DL throughput.


13.3.11 Monitoring Handover DelayThis describes how to monitor the handover delay performance. By performing this task, youcan observe and obtain the time taken by each handover of the current connection. The handoverincludes intra-frequency soft handover and inter-frequency handover.



ContextHandover delay refers to the period during which: the RNC receives a measurement report; theRNC implements a handover decision; the RNC initiates a soft or hard handover; the handoverends.


At most five handover delay monitoring tasks can be started simultaneously. This task canmonitor only intra-frequency handover and inter-frequency handover but cannot monitor inter-RAT handover.

Procedure




13-27


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_HO Delay_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End

Postrequisite

The real-time monitoring window is displayed, showing real-time monitoring results in list andchart. 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 correspondsto 10 ms). The Y-coordinate represents the interval of each successful handover (unit: ms).


13.3.12 Monitoring the BLER of the DL Transport ChannelThis describes how to monitor the variation of the BLER on all transport channels of the currentconnection. By performing this task, you can analyze the DL quality. If the BLER of the DLtransport channel increases, you can infer that the DL quality declines. If the BLER decreases,you can infer that the DL quality is improved.


LMT User Guide


Issue 03 (2009-04-25)



Context

The BLER of the DL transport channel is measured at the UE. The BLER is used for outer looppower control.


Procedure



Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 signalingtransport 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_DL BLER_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.



13-29


----End

PostrequisiteA 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 ofthe number of traffic transport channels in real time. The number of signaling transport channelsis always 1.

In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, thetime 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 reportedBLER of the DL transport channel (unit: %).


13.3.13 Monitoring the AMR ModeThis describes how to monitor the variation of the AMR rate configured by the UE and to recordthe variation in real time.



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

Procedure



LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 13.8.2 Parameter Reference for Connection Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Connectionperformance monitoring_AMR Mode_YYYY-MM-DD-HH-MM-SS_IMSI-IMSI value.


----End

PostrequisiteThe real-time monitoring window is displayed, showing real-time monitoring results in list andchart. 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 correspondsto 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 PerformanceThis describes how to monitor the cell performance, such as the common measured value andnumber of common channel users. For the same monitoring item, you can start at most six taskssimultaneously.

13.4.1 Monitoring Cell P-CPICH TX Power



13-31

This describes how to monitor the Primary Common Pilot Channel (P-CPICH) TX power of aspecified cell. By performing this task, you can observe and determine in real time whether thepilot power is normal.

13.4.2 Monitoring UL RX Total Wideband Power of a CellThis describes how to monitor the UL RX total wideband power of a specified cell. Byperforming this task, you can observe the UL load level in real time. The UL RX total widebandpower is measured and reported by the related NodeB.

13.4.3 Monitoring DL Carrier TX Power of a CellThis describes how to monitor the DL TX carrier power of a specified cell. By performing thistask, you can observe the DL load level in real time. The DL TX carrier power of a cell ismeasured and reported by the related NodeB.

13.4.4 Monitoring the Number of Cell UsersThis 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 ofthe users in the cell.

13.4.5 Monitoring Node SynchronizationThis describes how to monitor the time difference between RNC Frame Number (RFN) andNodeB 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. Ifthe difference between RFN and BFN varies too rapidly, you can infer that there are someproblems on the transmission between the RNC and the NodeB.

13.4.6 Monitoring the UL CACThis describes how to monitor the UL Call Admission Control (CAC) procedure of a specifiedcell. By performing this task, you can observe the variation of the predicted values and measuredvalues of UL load so as to measure the predicted accuracy of the UL CAC algorithm.

13.4.7 Monitoring DL CACThis describes how to monitor the DL Call Admission Control (CAC) procedure of a specifiedcell. By performing this task, you can observe the variation of the predicted values and measuredvalues 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 UsersThis describes how to monitor the number of UL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of UL equivalent users.

13.4.9 Monitoring the Number of DL Equivalent UsersThis describes how to monitor the number of DL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of DL equivalent users.

13.4.10 Monitoring the Cell Code TreeThis describes how to monitor the DL channel OVSF code tree of a specified cell. By performingthis 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-DSCHThis describes how to monitor the minimum required power of the HS-DSCH of a specifiedcell. By performing this task, you can observe the ratio of the minimum required power to themaximum TX power on the HS-DSCH in the cell.

13.4.12 Monitoring the Bit Rate Provided by the HS-DSCHThis describes how to monitor the bit rate of the HS-DSCH of a specified cell. By performingthis task, you can observe the variation of the transmission rate provided by the HS-DSCH.


LMT User Guide


Issue 03 (2009-04-25)

13.4.13 Monitoring the Bit Rate Provided by the E-DCHThis describes how to monitor the bit rate provided by the E-DCH that is set up for the HSUPAservices. By performing this task, you can observe the variation of the transmission rate providedby the E-DCH in real time.

13.4.14 Monitoring UL Throughput of a CellThroughput refers to the maximum rate of the equipment in the case that no frame is lost. ULthroughput of a cell refers to the throughput of the cell in the UL.

13.4.15 Monitoring DL Throughput of a CellThroughput refers to the maximum rate of the equipment in the case that no frame is lost. DLthroughput of a cell refers to the throughput of the cell in the DL.

13.4.16 Monitoring the Cell CEThis 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 togrant an new access request of an MS.

13.4.17 Monitoring the FDPCH SYMBOLThis describes how to monitor the condition of the F-DPCH SYMBOL, including the F-DPCHcode, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.



13.4.1 Monitoring Cell P-CPICH TX PowerThis describes how to monitor the Primary Common Pilot Channel (P-CPICH) TX power of aspecified cell. By performing this task, you can observe and determine in real time whether thepilot power is normal.





13-33

Context

You can query the range of the P-CPICH TX power by running LST PCPICH. If the pilot powerexceeds this range, you can infer that the power is abnormal.

Procedure

Step 1 In the navigation pane, click the Maintenance tab, expand the Realtime PerformanceMonitoring node, and then double-click Cell performance monitoring. A dialog box forsetting 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 Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_PCPICH TxPower_YYYY-MM-DD-HH-MM-SS_Cell ID-CellID.


----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 outputinterface (chart) of cell P-CPICH TX power monitoring.


LMT User Guide


Issue 03 (2009-04-25)

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 P-CPICH power (unit: dBm).

Related References13.8.3 Parameter Reference for Cell Performance Monitoring

13.4.2 Monitoring UL RX Total Wideband Power of a CellThis describes how to monitor the UL RX total wideband power of a specified cell. Byperforming this task, you can observe the UL load level in real time. The UL RX total widebandpower is measured and reported by the related NodeB.

Prerequisitel The LMT is started.l You have logged in to the RNC with an account authorized for this task.

ContextThe CAC procedure measures the UL load by the UL load factor, the ratio of (UL RX totalwideband power – cell background noise) to UL RX total wideband power. The backgroundnoise of the cell approximates to a constant, which can be set through the command ADDCELLCAC or MOD CELLCAC. Therefore, the UL RX total wideband power can also beused to measure the relative level of the UL load of the cell.



13-35

Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_RTWP_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End

PostrequisiteA 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 outputinterface (chart) of UL RX total wideband power monitoring for a cell.


LMT User Guide


Issue 03 (2009-04-25)

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 cellUL RX total wideband power (unit: dBm).


13.4.3 Monitoring DL Carrier TX Power of a CellThis describes how to monitor the DL TX carrier power of a specified cell. By performing thistask, you can observe the DL load level in real time. The DL TX carrier power of a cell ismeasured and reported by the related NodeB.



ContextThe CAC procedure uses the ratio of the DL TX carrier power to the maximum TX power ofthe cell to measure the DL load of the cell. When setting up a cell, you can run ADDCELLSETUP to set the maximum TX power. After the cell is set up, you can run MODCELL to modify it.



13-37

Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Tx Carrier Power_YYYY-MM-DD-HH-MM-SS_Cell ID-CellID.


----End

PostrequisiteA 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 outputinterface (chart) of DL TX carrier power monitoring for a cell.


LMT User Guide


Issue 03 (2009-04-25)

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 ratioof the DL TX carrier power to the maximum TX power of the cell (unit: %).


13.4.4 Monitoring the Number of Cell UsersThis 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 ofthe users in the cell.



Procedure




13-39


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Cell User Num_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End

PostrequisiteA 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 numberof cell users.


13.4.5 Monitoring Node SynchronizationThis describes how to monitor the time difference between RNC Frame Number (RFN) andNodeB 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. Ifthe difference between RFN and BFN varies too rapidly, you can infer that there are someproblems on the transmission between the RNC and the NodeB.


LMT User Guide


Issue 03 (2009-04-25)



Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Node Sync_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----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 outputinterface (chart) of node synchronization monitoring.



13-41

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 correspondsto 10 ms). The Y-coordinate represents the time difference between RFN and BFN and the timetaken by the NodeB to finish node synchronization (unit: ms).


13.4.6 Monitoring the UL CACThis describes how to monitor the UL Call Admission Control (CAC) procedure of a specifiedcell. By performing this task, you can observe the variation of the predicted values and measuredvalues of UL load so as to measure the predicted accuracy of the UL CAC algorithm.



Context

The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CACalgorithm 2). Run MOD CELLALGOSWITCH to set the UL CAC algorithm of a cell. RunLST CELLALGOSWITCH to query the UL CAC algorithm of a cell.


LMT User Guide


Issue 03 (2009-04-25)

l CAC algorithm 1 measures the UL load by the UL load factor, the ratio of (UL RX totalwideband power - cell background noise) to UL RX total wideband power. You can runthe 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 ULequivalent users to measure the load of the cell. By default, algorithm 2 is used to measurethe UL load of the cell.

Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_UL CAC Monitor_YYYY-MM-DD-HH-MM-SS_Cell ID-CellID.


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



13-43

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 P-CPICH power (unit: dBm).


13.4.7 Monitoring DL CACThis describes how to monitor the DL Call Admission Control (CAC) procedure of a specifiedcell. By performing this task, you can observe the variation of the predicted values and measuredvalues of the DL load so as to measure the predicted accuracy of the DL CAC algorithm.



ContextThe methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CACalgorithm 2). Run MOD CELLALGOSWITCH to set the UL CAC algorithm of a cell. RunLST 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 ofthe cell to measure the DL load of the cell. By default, algorithm 1 is used to measure theDL load of the cell. The maximum TX power is a constant. You can run ADDCELLSETUP to set it.

l CAC algorithm 2 uses the ratio of the current DL equivalent number of users to themaximum DL equivalent number of users.

Procedure



LMT User Guide


Issue 03 (2009-04-25)


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_DL CAC Monitor_YYYY-MM-DD-HH-MM-SS_Cell ID-cellID.


----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 thepredicted values and measured values of the load (unit: %).


13.4.8 Monitoring the Number of UL Equivalent UsersThis describes how to monitor the number of UL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of UL equivalent users.



13-45



Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_UL Total Equivalent User Num_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End


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,


LMT User Guide


Issue 03 (2009-04-25)

the time unit is TICK (one TICK corresponds to 10 ms). The Y-coordinate represents thepredicted values and measured values of the number of UL equivalent users.


13.4.9 Monitoring the Number of DL Equivalent UsersThis describes how to monitor the number of DL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of DL equivalent users.



Context


Monitoring node, and then double-click Cell performance monitoring. A dialog box forsetting the parameters is displayed, as shown in Figure 13-32.


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem to DL Total Equivalent User Num, and then set Monitor period(s) and Cell ID.

NOTE





13-47

\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_DL Total Equivalent User Num_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End


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 thepredicted values and measured values of the number of DL equivalent users.


13.4.10 Monitoring the Cell Code TreeThis describes how to monitor the DL channel OVSF code tree of a specified cell. By performingthis task, you can observe the usage of the DL channel code in real time.

Prerequisitel The LMT is started.l You have logged in to the RNC with an account authorized for this task.





LMT User Guide


Issue 03 (2009-04-25)

Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Cell Code Tree Monitor_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End

Postrequisite

The LMT displays a real-time monitoring window with the monitoring task name on the titlebar. 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 ofeach 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 inlist or chart. In the chart, the X-coordinate represents the time; the Y-coordinate representsthe codes.

Figure 13-34 Output of the cell code tree usage in static view



13-49


13.4.11 Monitoring the Minimum Required Power of the HS-DSCHThis describes how to monitor the minimum required power of the HS-DSCH of a specifiedcell. By performing this task, you can observe the ratio of the minimum required power to themaximum TX power on the HS-DSCH in the cell.



Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_HS-DSCH Min Power Requirement_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


LMT User Guide


Issue 03 (2009-04-25)


----End


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 ratioof the required power to the maximum TX power of the cell (unit: ‰).


13.4.12 Monitoring the Bit Rate Provided by the HS-DSCHThis describes how to monitor the bit rate of the HS-DSCH of a specified cell. By performingthis task, you can observe the variation of the transmission rate provided by the HS-DSCH.



ContextNOTE

Before performing the bit rate monitoring on the HS-DSCH, ensure that the HSDPA_PBR_MEAS of thecell 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 ofHSDPA_PBR_MEAS switch. If the queried result is HSDPA PBR MEAS ALGORITHM:OFF, run MODCELLALGOSWITCH to set it to ON.

Procedure




13-51


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_HS-DSCH Provide Bitrate_YYYY-MM-DD-HH-MM-SS_CellID-Cell ID.


----End


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 bitrate (unit: bit/s).


13.4.13 Monitoring the Bit Rate Provided by the E-DCHThis describes how to monitor the bit rate provided by the E-DCH that is set up for the HSUPAservices. By performing this task, you can observe the variation of the transmission rate providedby the E-DCH in real time.


LMT User Guide


Issue 03 (2009-04-25)



ContextNOTE

Before performing the bit rate monitoring on the E-DCH, ensure that the HSUPA_PBR_MEAS of the cellis 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 ofHSUPA_PBR_MEAS switch. If the queried result is HSUPA PBR MEAS ALGORITHM:OFF, run MODCELLALGOSWITCH to set it to ON.

Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_E-DCH Provide Bitrate_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.



13-53


----End


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 bitrate (unit: bit/s).


13.4.14 Monitoring UL Throughput of a CellThroughput refers to the maximum rate of the equipment in the case that no frame is lost. ULthroughput of a cell refers to the throughput of the cell in the UL.



Procedure




LMT User Guide


Issue 03 (2009-04-25)

Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Cell UL ThroughPut_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End


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 ULthroughput of the cell.


13.4.15 Monitoring DL Throughput of a CellThroughput refers to the maximum rate of the equipment in the case that no frame is lost. DLthroughput of a cell refers to the throughput of the cell in the DL.



Procedure




13-55


Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Cell DL ThroughPut_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End


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 DLthroughput of the cell.


13.4.16 Monitoring the Cell CEThis 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 togrant an new access request of an MS.


LMT User Guide


Issue 03 (2009-04-25)






Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_Cell CE_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


----End


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.



13-57


13.4.17 Monitoring the FDPCH SYMBOLThis describes how to monitor the condition of the F-DPCH SYMBOL, including the F-DPCHcode, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.



ContextThe F-DPCH channel bears the Transport Power Control (TPC) information of HSDPA servicesand uses the spreading factor SF256.

Procedure



Step 2 In the 13.8.3 Parameter Reference for Cell Performance Monitoring dialog box, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Cellperformance monitoring_FDPCH SYMBOL monitoring_YYYY-MM-DD-HH-MM-SS_Cell ID-Cell ID.


LMT User Guide


Issue 03 (2009-04-25)


----End


l In the static view of the FDPCH SYMBOL monitoring, you can see the condition of theSYMBOL corresponding to the F-DPCH code. The numbers in the grids indicate thetimeslot formats.

l In the dynamic view of the FDPCH SYMBOL monitoring, the X-coordinate represents thetime, and the Y-coordinate represents the F-DPCH code, position of the F-DPCHSYMBOL, and timeslot format.


13.5 Monitoring the RNC Link PerformanceThis describes how to monitor the RNC link performance. This task applies to the traffic statisticsbased on IP path/SCTP/OAM stream, statistics based on priority queues. The statistics based onpriority queues include the statistics of packet loss rate, number of the sent packets, and numberof the sent bytes. For the same monitoring item, you can start up to six tasks.

13.5.1 Monitoring the IMA Group TrafficThis describes how to monitor the traffic on a specified IMA group in real time. The real-timetraffic on the current IMA group is displayed in either list or chart.

13.5.2 Monitoring the UNI Link TrafficThis describes how to monitor the traffic on a specified UNI link in real time. The real-timetraffic on the current UNI link is displayed in either list or chart.

13.5.3 Monitoring the Fractional ATM Link TrafficThis describes how to monitor the traffic on a specified fractional ATM link in real time. Thereal-time traffic on the current fractional ATM link is displayed in either list or chart.

13.5.4 Monitoring the SAAL Link TrafficThis describes how to monitor the traffic on a specified SAAL link in real time. The real-timetraffic on the current SAAL link is displayed in either list or chart.

13.5.5 Monitoring the IPoA PVC TrafficThis describes how to monitor the traffic on a specified IPoA PVC in real time. The real-timetraffic on the current IPoA PVC is displayed in either list or chart.

13.5.6 Monitoring the AAL2 Path TrafficThis describes how to monitor the traffic on a specified AAL2 path in real time. The real-timetraffic on the current AAL2 path is displayed in either list or chart.

13.5.7 Monitoring the FE/GE TrafficThis describes how to monitor the traffic on a specified FE/GE port in real time. The real-timetraffic on the current FE/GE port is displayed in either list or chart.

13.5.8 Monitoring the PPP Link Traffic



13-59

This describes how to monitor the traffic on a specified PPP link in real time. The real-timetraffic on the current PPP link is displayed in either list or chart.

13.5.9 Monitoring the MLPPP Group TrafficThis describes how to monitor the traffic on a specified MLPPP group in real time. The real-time traffic on the current MLPPP group is displayed in either list or chart.

13.5.10 Monitoring the SCTP Link TrafficThis describes how to monitor the traffic on a specified SCTP link in real time. The real-timetraffic on the current SCTP link is displayed in either list or chart.

13.5.11 Monitoring the IP Path TrafficThis describes how to monitor the traffic on a specified IP path in real time. The real-time trafficon the current IP path is displayed in either list or chart.

13.5.12 Monitoring the Logical PortsThis describes how to monitor the traffic of the specified logical port in real time. You canmonitor an entire port, where the monitoring result displays the real-time traffic of the currentlogical port. You can also monitor only the specified priority of the port, where the monitoringresult displays the TX traffic of the specified priority of the current logical port.

13.5.13 Monitoring OAM TrafficThis describes how to monitor the RX and TX traffic of the specified NodeB OM channel. Thetraffic of the current NodeB OM channel is displayed in either list or chart.

13.5.14 Monitoring Bandwidth of Logical PortsThis describes how to monitor the physical bandwidth of logical ports. The bandwidth of thecurrent logical port is displayed in either list or chart.



13.5.1 Monitoring the IMA Group TrafficThis describes how to monitor the traffic on a specified IMA group in real time. The real-timetraffic on the current IMA group is displayed in either list or chart.


LMT User Guide


Issue 03 (2009-04-25)



Context

CAUTIONThis task only applies to monitoring the IMA group that is successfully configured and connectedto 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 PerformanceMonitoring node, and then double-click Link performance monitoring. A dialog box forsetting 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, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_IMA Group_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End



13-61

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-43 is an example of the output interface (chart) of IMA group real-timetraffic 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 correspondsto 10 ms). The Y-coordinate represents the RX and TX traffic in kbit/s.

Related References13.8.4 Parameter Reference for Link Performance Monitoring

13.5.2 Monitoring the UNI Link TrafficThis describes how to monitor the traffic on a specified UNI link in real time. The real-timetraffic on the current UNI link is displayed in either list or chart.




LMT User Guide


Issue 03 (2009-04-25)

Context

CAUTIONThis task only applies to monitoring the UNI link that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_UNI Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End

PostrequisiteAfter the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-45 is an example of the output interface (chart) of UNI link real-timetraffic monitoring.



13-63

Figure 13-45 Output interface of UNI link real-time traffic monitoring



13.5.3 Monitoring the Fractional ATM Link TrafficThis describes how to monitor the traffic on a specified fractional ATM link in real time. Thereal-time traffic on the current fractional ATM link is displayed in either list or chart.



Context

CAUTIONThis task only applies to monitoring the fractional ATM link that is successfully configured andconnected to its peer end. If you delete the monitored link after the task is started, deleting themonitored link stops the task.


LMT User Guide


Issue 03 (2009-04-25)

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to FRAC ATM Link, and then set Subrack No., Slot No., and FRAC LinkNo..

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_FRAC ATM Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The task name and related parameters are indicated in thetitle of the window.

In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN correspondsto 10 ms). The Y-coordinate represents the RX and TX traffic (unit: kbit/s).




13-65

13.5.4 Monitoring the SAAL Link TrafficThis describes how to monitor the traffic on a specified SAAL link in real time. The real-timetraffic on the current SAAL link is displayed in either list or chart.



Context

CAUTIONThis task only applies to monitoring the SAAL link that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to SAAL Link, and then set Subrack No., Slot No., Subsystem No., and SAALLink No..



LMT User Guide


Issue 03 (2009-04-25)

\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_SAAL Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-48 is an example of the output interface (chart) of SAAL link real-timetraffic monitoring.

Figure 13-48 Output interface of SAAL link real-time traffic monitoring



13.5.5 Monitoring the IPoA PVC TrafficThis describes how to monitor the traffic on a specified IPoA PVC in real time. The real-timetraffic on the current IPoA PVC is displayed in either list or chart.



13-67



Context

CAUTIONThis task only applies to monitoring the IPoA PVC that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_IPOA PVC_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End


LMT User Guide


Issue 03 (2009-04-25)

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-50 is an example of the output interface (chart) of IPoA PVC real-timetraffic monitoring.

Figure 13-50 Output interface of IPoA PVC real-time traffic monitoring



13.5.6 Monitoring the AAL2 Path TrafficThis describes how to monitor the traffic on a specified AAL2 path in real time. The real-timetraffic on the current AAL2 path is displayed in either list or chart.





13-69

Context

CAUTIONThis task only applies to monitoring the AAL2 path that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to AAL2 PATH, and then set Subrack No., Neighbor Node ID, and AAL2PATH ID.

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_AAL2 PATH_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End

PostrequisiteAfter the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and related


LMT User Guide


Issue 03 (2009-04-25)

parameters. Figure 13-52 is an example of the output interface (chart) of AAL2 path real-timetraffic monitoring.

Figure 13-52 Output interface of AAL2 path real-time traffic monitoring



13.5.7 Monitoring the FE/GE TrafficThis describes how to monitor the traffic on a specified FE/GE port in real time. The real-timetraffic on the current FE/GE port is displayed in either list or chart.





13-71

Context

CAUTIONThis task only applies to monitoring the FE/GE port that is successfully configured andconnected to its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to FE&GE, and then set Subrack No., Slot No., strMonitorType, and FE&GEPort 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_FE&GE_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End


LMT User Guide


Issue 03 (2009-04-25)

PostrequisiteAfter the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-54 is an example of the output interface (chart) of FE/GE real-time trafficmonitoring.

Figure 13-54 Output interface of FE/GE real-time traffic monitoring



13.5.8 Monitoring the PPP Link TrafficThis describes how to monitor the traffic on a specified PPP link in real time. The real-timetraffic on the current PPP link is displayed in either list or chart.





13-73

Context

CAUTIONThis task only applies to monitoring the PPP link that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to PPP Link, and then set Subrack No., Slot No., strMonitorType, and PPPLink No..

NOTE

l strMonitorType can be Link or QoS.


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_PPP Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End


LMT User Guide


Issue 03 (2009-04-25)

PostrequisiteAfter the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters.



13.5.9 Monitoring the MLPPP Group TrafficThis describes how to monitor the traffic on a specified MLPPP group in real time. The real-time traffic on the current MLPPP group is displayed in either list or chart.



Context

CAUTIONThis task only applies to monitoring the MLPPP group that is successfully configured andconnected to its peer end. After the task is started, deleting the monitored link stops the task.

Procedure




13-75


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to MLPPP Group, and then set Subrack No., Slot No., strMonitorType, andMLPPP Group No..

NOTE

l strMonitorType can be MLPPP Group or QoS.


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_MLPPP Group_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End




13.5.10 Monitoring the SCTP Link TrafficThis describes how to monitor the traffic on a specified SCTP link in real time. The real-timetraffic on the current SCTP link is displayed in either list or chart.


LMT User Guide


Issue 03 (2009-04-25)



Context

CAUTIONThis task only applies to monitoring the SCTP link that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.


Monitoring node, and then double-click Link performance monitoring. A dialog box forsetting the parameters is displayed, as shown in Figure 13-57.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to SCTP Link, and then set Subrack No., Slot No., Subsystem No., and SCTPLink No..

Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_SCTP Link_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End



13-77

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-58 is an example of the output interface (chart) of SCTP link real-timetraffic monitoring.

Figure 13-58 Output interface of SCTP link real-time traffic monitoring



13.5.11 Monitoring the IP Path TrafficThis describes how to monitor the traffic on a specified IP path in real time. The real-time trafficon the current IP path is displayed in either list or chart.




LMT User Guide


Issue 03 (2009-04-25)

Context

CAUTIONThis task only applies to monitoring the IP path that is successfully configured and connectedto its peer end. After the task is started, deleting the monitored link stops the task.

Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to IP PATH, and then set Subrack No., Slot No., Subsystem No., NeighborNode 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_IP PATH_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End



13-79

Postrequisite

After the monitoring task is started, a monitoring window is displayed, showing real-timemonitoring results in list and chart. The title of the window indicates the task name and relatedparameters. Figure 13-60 is an example of the output interface (chart) of IP path real-time trafficmonitoring.

Figure 13-60 Output interface of IP path real-time traffic monitoring



13.5.12 Monitoring the Logical PortsThis describes how to monitor the traffic of the specified logical port in real time. You canmonitor an entire port, where the monitoring result displays the real-time traffic of the currentlogical port. You can also monitor only the specified priority of the port, where the monitoringresult displays the TX traffic of the specified priority of the current logical port.




LMT User Guide


Issue 03 (2009-04-25)


Monitoring node, and then double-click Link performance monitoring. A dialog box forsetting the parameters is displayed, as shown in Figure 13-61.


Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor item to Logic Port, and then set Subrack No., Slot No., strMonitorType, and PortNo..

NOTE

l strMonitorType can be Port or QoS.


Step 3 Select the Auto Save check box if you want the LMT to automatically save the monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_Logic Port_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End


In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN correspondsto 10 ms). The Y-coordinate represents the real-time traffic of the current logical port in kbit/s.




13-81

13.5.13 Monitoring OAM TrafficThis describes how to monitor the RX and TX traffic of the specified NodeB OM channel. Thetraffic of the current NodeB OM channel is displayed in either list or chart.



Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_OAM_YYYY-MM-DD-HH-MM-SS_Subrack No.-a.txt.


----End



LMT User Guide


Issue 03 (2009-04-25)

In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN correspondsto 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 PortsThis describes how to monitor the physical bandwidth of logical ports. The bandwidth of thecurrent logical port is displayed in either list or chart.



Procedure



Step 2 In the 13.8.4 Parameter Reference for Link Performance Monitoring dialog box, setMonitor 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is Linkperformance monitoring_Logic Port Band Width_YYYY-MM-DD-HH-MM-SS_SubrackNo.-a.txt.



13-83


----End


In the chart, the X-coordinate represents the time. The time unit is RFN (one RFN correspondsto 10 ms). The Y-coordinate represents the bandwidth of the logical port in kbit/s.


13.6 Monitoring the RNC Board ResourceThis describes how to monitor licensed traffic volume for voice services and the PS domain datathroughput on the user plane of a specified board in real time.



ContextNOTE

l This task can be performed only in GUI mode and applies to only the boards that are in position andrunning 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 PerformanceMonitoring node, and then double-click Board resource monitoring. A dialog box for settingthe parameters is displayed, as shown in Figure 13-64.


LMT User Guide


Issue 03 (2009-04-25)

Figure 13-64 Board Resource monitoring dialog box

Step 2 In the displayed 13.8.5 Parameter Reference for Board Resource Monitoring, set Monitoritem 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 monitoringrecords. The default save path is LMT installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default file name is monitortype_monitor item_YYYY-MM-DD-HH-MM-SS_Subrack No.-a_Slot No.-b_SubsystemNo.-c.txt.


----End

PostrequisiteThe monitoring window is displayed, showing real-time monitoring results in list and chart. Thetitle of the window indicates the task name and related parameters. Figure 13-65 is an exampleof the output interface (list) of board resource monitoring.



13-85

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 correspondsto 10 ms). The Y-coordinate represents the RX and TX traffic in KB.



Related References13.8.5 Parameter Reference for Board Resource Monitoring


LMT User Guide


Issue 03 (2009-04-25)

13.7 Basic RNC Real-Time Performance MonitoringOperations

This describes how to perform basic operations after an RNC real-time performance monitoringtask is started.

13.7.1 Browsing the RNC Monitoring Results OnlineThis describes how to online browse and query the monitoring results that are dynamicallydisplayed in the monitoring window in real time.

13.7.2 Switching the Display ModeThis describes how to switch the display mode to lineargraph or histogram on the Chart tabpage.

13.7.3 Setting the Default Display ModeThis describes how to set the default display mode to lineargraph or histogram on the Chart tabpage.

13.7.4 Editing the Display Mode for the ChartThis 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 inthe window, you can set the display parameters, including the color, type, and width of the lines.

13.7.5 Saving RNC Monitoring ResultsThis describes how to save the monitoring results into local files.

13.7.6 Pausing and Resuming an RNC Monitoring TaskThis describes how to pause the connection/cell/link performance monitoring and board resourcemonitoring tasks and restart them later when needed.

13.7.7 Adding an RNC CPU/DSP Monitoring TaskThis describes how to add a required CPU/DSP monitoring item to a CPU/DSP usage monitoringtask.

13.7.8 Deleting an RNC CPU/DSP Monitoring TaskThis describes how to delete an unnecessary CPU/DSP monitoring item from a CPU/DSPusage monitoring task.

13.7.9 Stopping an RNC Monitoring TaskThis describes how to stop a monitoring task when it is no longer needed.

13.7.10 Browsing RNC Monitoring Results OfflineFor the results of the connection/cell/link performance monitoring and board resourcemonitoring, 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 OnlineThis describes how to online browse and query the monitoring results that are dynamicallydisplayed in the monitoring window in real time.

Prerequisitel A real-time performance monitoring task is started.



13-87

l Monitoring results are reported by the RNC.

Procedurel 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 theshortcut menu:– Setting auto scroll

– Showing or hiding the grid

– Set the Y axis display range (only applicable to the connection performancemonitoring, cell performance monitoring, link performance monitoring, and boardresource monitoring tasks)

– Switching the display mode

l 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 theshortcut menu:– Setting auto scroll

– Saving selected data (only applicable to the connection performance monitoring, cellperformance monitoring, and link performance monitoring tasks)

– Quering the attributes (only applicable to the CPU/DSP usage monitoring task)

l Right-click on the task information pane at the bottom of the real-time performancemonitoring window. Then, you can perform the following operations by selecting thecorresponding 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 resourcemonitoring tasks)

----End

Related Tasks13.7.10 Browsing RNC Monitoring Results Offline

13.7.2 Switching the Display ModeThis describes how to switch the display mode to lineargraph or histogram on the Chart tabpage.



Procedurel Histogram


LMT User Guide


Issue 03 (2009-04-25)

A histogram displays monitoring results in bar mode. Therefore, you can directly learn thecurrent monitoring results.

The X-coordinate represents the task number; the Y-coordinate has different meaningsaccording to different monitoring tasks. For example, for the CPU/DSP usagemonitoring task, the Y-coordinate represents the percentage.

l Lineargraph

A lineargraph displays monitoring results in curve mode. Therefore, you can learn aboutthe 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 accordingto different monitoring tasks. For example, for the CPU/DSP usage monitoring task, theY-coordinate represents the percentage.

NOTE

l The task information pane at the bottom of the window displays related information aboutmonitoring tasks in table. For example, for the CPU/DSP usage monitoring task, the taskinformation pane displays the following information: task ID, whether to display line or not, colorsetting, 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 taskinformation pane at the bottom of the monitoring window.

----End

13.7.3 Setting the Default Display ModeThis describes how to set the default display mode to lineargraph or histogram on the Chart tabpage.



ContextNOTE

This task is valid only for the connection performance monitoring, cell performance monitoring, linkperformance monitoring, and board resource monitoring tasks.

Procedure

Step 1 Right-click on the Chart tab page, choose Set Default Display Mode. The Set Default DisplayMode dialog box is displayed.

Step 2 In the Default Display Mode area, select Line or histogram.

----End



13-89

13.7.4 Editing the Display Mode for the ChartThis 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 inthe window, you can set the display parameters, including the color, type, and width of the lines.



Procedure

Step 1 In the task information pane at the bottom of the window, click the property boxes of the LineColor, 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 currentmonitoring task.

l During the real-time performance monitoring, if data is displayed on the List tab page whereas no chartis displayed on the Chart tab page, you can select one of the following line types by editing thedisplay properties:

l type 1

l type 2

l type 3

l You can right-click in the real-time monitoring window, choose Set Default Display Mode, selectLine or histogram in the Default Display Mode area to change the display mode.

----End

13.7.5 Saving RNC Monitoring ResultsThis describes how to save the monitoring results into local files.


l There is monitoring data reported by the RNC.

Contextl For the CPU/DSP usage monitoring, the default save path is installation directory\client

\output\monitor. The default format of file names is CPU/DSPReviewyy_mm_dd_hh_mm_ss-task number.mrf.

l For the connection performance monitoring, cell performance monitoring, linkperformance monitoring, and board resource monitoring tasks, the default save path is


LMT User Guide


Issue 03 (2009-04-25)

installation directory\adaptor\clientadaptor\RNC\LMT software version number\output\realmonitor. The default format of file names is monitoring type_monitoringitem_yy-mm-dd-hh-mm-ss.txt.For example, the results of a PCPICH Ec/No and RSCP monitoring task that is started at15:41:10 on 2005-10-26 are saved under the name Connection performancemonitoring_PCPICH EcNo&RSCP_2005-10-26-15-41-10.txt.

NOTE

The results of connection performance monitoring, cell performance monitoring, link performancemonitoring, 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 thefollowing ways:

Procedurel 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

PostrequisiteFor the connection performance monitoring, cell performance monitoring, link performancemonitoring, and board resource monitoring tasks, the only way for saving monitoring results isto select the Auto Save check box when setting the parameters. The check box is selected bydefault.

Related Tasks13.7.10 Browsing RNC Monitoring Results Offline

13.7.6 Pausing and Resuming an RNC Monitoring TaskThis describes how to pause the connection/cell/link performance monitoring and board resourcemonitoring tasks and restart them later when needed.

PrerequisiteThe related monitoring task is started.

Procedurel 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 Tasks13.7.9 Stopping an RNC Monitoring Task



13-91

13.7.7 Adding an RNC CPU/DSP Monitoring TaskThis describes how to add a required CPU/DSP monitoring item to a CPU/DSP usage monitoringtask.

Prerequisitel A real-time CPU/DSP usage monitoring task is started.


Procedure

Step 1 Right-click in the task information pane in the CPU/DSP Usage window, and choose AddTask 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. Theinformation 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 Tasks13.7.8 Deleting an RNC CPU/DSP Monitoring Task

13.7.8 Deleting an RNC CPU/DSP Monitoring TaskThis describes how to delete an unnecessary CPU/DSP monitoring item from a CPU/DSPusage monitoring task.




LMT User Guide


Issue 03 (2009-04-25)

Procedure

Step 1 In the task information pane at the bottom of the CPU/DSP Usage monitoring window, selectthe monitoring task to be deleted.

Step 2 Right-click the task to be deleted in the task information pane, and choose Delete Task fromthe 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 Tasks13.7.7 Adding an RNC CPU/DSP Monitoring Task

13.7.9 Stopping an RNC Monitoring TaskThis describes how to stop a monitoring task when it is no longer needed.

PrerequisiteA real-time performance monitoring task is created.

Procedure

Click in the top right corner of the real-time performance monitoring task window to stopthe task.

NOTE

For CPU/DSP usage monitoring, you can also stop a task by deleting it. For details, refer to 13.7.8 Deletingan RNC CPU/DSP Monitoring Task.

----End

13.7.10 Browsing RNC Monitoring Results OfflineFor the results of the connection/cell/link performance monitoring and board resourcemonitoring, you can double-click the .txt files in which the results are saved and read the details.

PrerequisiteThe monitoring results are saved in files.



13-93

ContextYou can use the Monitor Viewer to browse offline the results of the CPU/DSP usage monitoringsaved in .mrf files to learn the history running situation of the system and locate the faults. Theresults are saved in the manner specified in Saving RNC Monitoring Results.

Procedurel Review results of the CPU/DSP usage monitoring.

1. Select either of the following ways to start the Monitor Viewer:

– Click on the toolbar in the Local Maintenance Terminal window.

– Choose Start > All Programs > Huawei Local Maintenance Terminal >Monitor Viewer.

The Open dialog box is displayed, as shown in Figure 13-68.


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 requiredfile that saves the results of CPU/DSP usage monitoring.

3. Select a file and click Open or double-click the file. The Monitor Viewer windowdisplays the result data in list (as shown in Figure 13-69) or in chart (as shown inFigure 13-70).


LMT User Guide


Issue 03 (2009-04-25)

Figure 13-69 Displaying monitoring results in a list

Figure 13-70 Displaying monitoring results in a chart



13-95

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.l To review results of the connection performance monitoring, cell performance

monitoring, link performance monitoring, and board resource monitoring, perform thefollowing 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 softwareversion number\output\realmonitor. To name the files, refer to 13.7.5 Saving RNCMonitoring Results.

2. Double-click the file to open it.3. Review the information.

----End

Related Tasks13.7.1 Browsing the RNC Monitoring Results Online13.7.5 Saving RNC Monitoring Results

13.8 Parameter Reference for RNC Real-Time PerformanceMonitoring

This describes the parameters used for each performance monitoring.

13.8.1 Parameter Reference for RNC CPU Usage MonitoringThis describes the parameters used for RNC CPU/DSP usage monitoring.

13.8.2 Parameter Reference for Connection Performance MonitoringThis describes the parameters for connection performance monitoring.

13.8.3 Parameter Reference for Cell Performance MonitoringThis describes the parameters used for cell performance monitoring.

13.8.4 Parameter Reference for Link Performance MonitoringThis describes the parameters used for link performance monitoring.

13.8.5 Parameter Reference for Board Resource MonitoringThis describes the parameters used for board resource monitoring.

13.8.1 Parameter Reference for RNC CPU Usage MonitoringThis describes the parameters used for RNC CPU/DSP usage monitoring.

Field Description

Subrack No. Subrack number of the board to be monitored. Value range: 0 to5.

Slot No. Slot number of the board to be monitored. Value range: 0 to 27.


LMT User Guide


Issue 03 (2009-04-25)

Field Description

Show line graph orhistogram

If this check box is selected, the curve of data variation isdisplayed on the Chart tab page in real time.

Save Review Data After a monitoring task is added, click Start Saving to save themonitoring data into the file.

13.8.2 Parameter Reference for Connection PerformanceMonitoring

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 differentmonitoring periods and time units.

IMSI Matching conditions for the monitoring

Auto Save If the check box is selected, the monitoring records are automaticallysaved to the specified path.

Text File Name Path and name of the automatically saved file

NOTE

The IMSI value can be automatically memorized.

Related Tasks13.3.1 Monitoring P-CPICH Ec/No and RSCP13.3.2 Monitoring the SIR Measurement Values of UL RLSs13.3.3 Monitoring the Enhanced Outer Loop Power Control13.3.4 Monitoring the SIR Error Values of UL RLSs13.3.5 Monitoring DL Code TX Power13.3.6 Monitoring the UE TX Power13.3.7 Monitoring UL Traffic13.3.8 Monitoring DL Traffic13.3.9 Monitoring UL Throughput and Bandwidth13.3.10 Monitoring DL Throughput and Bandwidth13.3.11 Monitoring Handover Delay13.3.12 Monitoring the BLER of the DL Transport Channel13.3.13 Monitoring the AMR Mode

13.8.3 Parameter Reference for Cell Performance MonitoringThis describes the parameters used for cell performance monitoring.



13-97

Field Description


Monitor period(s) Monitoring period. Different monitoring items have differentmonitoring periods and time units.

Cell ID ID of the cell to be monitored



NOTE

The Cell ID value can be automatically memorized.

Related Tasks13.4.1 Monitoring Cell P-CPICH TX Power13.4.2 Monitoring UL RX Total Wideband Power of a Cell13.4.3 Monitoring DL Carrier TX Power of a Cell13.4.4 Monitoring the Number of Cell Users13.4.5 Monitoring Node Synchronization13.4.6 Monitoring the UL CAC13.4.7 Monitoring DL CAC13.4.8 Monitoring the Number of UL Equivalent Users13.4.9 Monitoring the Number of DL Equivalent Users13.4.10 Monitoring the Cell Code Tree13.4.11 Monitoring the Minimum Required Power of the HS-DSCH13.4.12 Monitoring the Bit Rate Provided by the HS-DSCH13.4.13 Monitoring the Bit Rate Provided by the E-DCH13.4.14 Monitoring UL Throughput of a Cell13.4.15 Monitoring DL Throughput of a Cell13.4.16 Monitoring the Cell CE13.4.17 Monitoring the FDPCH SYMBOL

13.8.4 Parameter Reference for Link Performance MonitoringThis describes the parameters used for link performance monitoring.

Field Description


Subrack No. Subrack number of the link to be monitored. Value range: 0 to 5.


LMT User Guide


Issue 03 (2009-04-25)

Field Description

Slot No. Slot number of the board whose link is to be monitored. This parameter isvalid for only the following monitoring items: IMA Group, UNI Link,FRAC ATM Link, SAAL Link, FE&GE, PPP Link, MLPPP Link, SCTPLink, and IP Path.NOTE

For items IMA Group, UNI Link, FRAC ATM Link, FE&GE, PPP Link, MLPPPGroup, Port No., and Logic Port, when subrack 0 is selected, slots 20 to 23 areunavailable.

IMA GroupNo.

Number of the IMA group. This parameter is valid for only the IMAGroup 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 Linkmonitoring item. You can run LST UNILNK to query its value.

FRAC LinkNo.

Number of the fractional ATM link. This parameter is valid for only theFRAC ATM Link monitoring item. You can run LST FRALNK and setLink type to FRAATM to query its value.

SAAL LinkNo.

Number of the SAAL link. Value range: 0 to 699. This parameter is valid foronly the SAAL Link monitoring item. You can run LST SAALLNK toquery its value.

IP Address Local IP address and peer IP address of the IPoA PVC. These parameters arevalid for only the IPOA PVC monitoring item. You can run LSTIPOAPVC to query their values.Peer IP

address

NeighborNode ID

Adjacent node ID and ID of the AAL2 path. These parameters are valid foronly the AAL2 PATH monitoring item. You can run LST AAL2PATH toquery their values.

AAL2 PATHID

FE&GE Number of the FE and GE port. Value range: 0 to 7. These parameters arevalid for only the FE&GE monitoring item. You can run DSPETHPORT to query their values.

PPP Link No. Number of the PPP link. Value range: 0 to 167. This parameter is valid foronly the PPP Link monitoring item. You can run LST PPPLNK to queryits value.

MLPPPGroup No.

Number of the MLPPP group. Value range: 0 to 63. This parameter is validfor only the MLPPP Group monitoring item. You can run LST MPGRPto query its value.

SCTP LinkNo.

Number of the SCTP link. Value range: 0 to 599. This parameter is valid foronly the SCTP Link monitoring item. You can run LST SCTPLNK to queryits value.

NeighborNode ID

ID of the adjacent node. Value range: 0 to 1999. Number of the IP path. Valuerange: 0 to 65535. These parameters are valid for only the IP PATHmonitoring item. You can run LST IPPATH to query their values.

IP PATH ID



13-99

Field Description

Port No. Number of the logical port. Value range: 0 to 119. This parameter is validfor only the Port No. and Logic Port items.

NodeB ID Number of the NodeB. Value range: 0 to 65535. This parameter is valid foronly the OAM monitoring item. You can run LST NODEB to query itsvalue.

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 If the check box is selected, the monitoring records are automatically savedto the specified path.

Text FileName

Path and name of the automatically saved file

Related Tasks13.5.1 Monitoring the IMA Group Traffic13.5.2 Monitoring the UNI Link Traffic13.5.3 Monitoring the Fractional ATM Link Traffic13.5.4 Monitoring the SAAL Link Traffic13.5.5 Monitoring the IPoA PVC Traffic13.5.6 Monitoring the AAL2 Path Traffic13.5.7 Monitoring the FE/GE Traffic13.5.8 Monitoring the PPP Link Traffic13.5.9 Monitoring the MLPPP Group Traffic13.5.10 Monitoring the SCTP Link Traffic13.5.11 Monitoring the IP Path Traffic13.5.12 Monitoring the Logical Ports13.5.13 Monitoring OAM Traffic13.5.14 Monitoring Bandwidth of Logical Ports

13.8.5 Parameter Reference for Board Resource MonitoringThis describes the parameters used for board resource monitoring.

Field Description


Monitor period(s) Select the monitor period. The monitor period and its unit vary withmonitor items.


LMT User Guide


Issue 03 (2009-04-25)

Field Description

Subrack No. Number of the subrack holding the board to be tested. Value range: 0to 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.



Related Tasks13.6 Monitoring the RNC Board Resource



13-101

14 Testing RNC Faults

About This Chapter

This describes the following concepts of the RNC fault tests: the physical layer test, data linklayer test, and other fault tests.

14.1 Testing Faults on the Physical LayerThis describes how to test faults at the physical layer, including local E1/T1 loopback test, remoteE1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, andSDH loopback test.

14.2 Testing Faults on the Link LayerThis describes how to test faults on the link layer. The link layer testing provides the followingtests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrongconnection test, NodeB maintenance IPoA test, and Iu-PS IPoA test.

14.3 Testing Other RNC FaultsThis describes how to test other RNC faults, including the IPC connectivity test, cell commonchannel test, RFN test, clock test, and board load control test.

14.4 Basic Operations of the RNC Fault TestsThis describes how to browse and save the fault testing results and how to stop a fault testingtask.

14.5 Parameter Reference for the RNC Fault TestsThis describes the parameters used for each RNC fault test.

RNCLMT User Guide 14 Testing RNC Faults


14-1

14.1 Testing Faults on the Physical LayerThis describes how to test faults at the physical layer, including local E1/T1 loopback test, remoteE1/T1 loopback test, E1/T1 BER test, E1/T1 loopback test, E1/T1 wrong connection test, andSDH loopback test.

14.1.1 Physical Layer TestingThe 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 connectiontest, SDH loopback test, SDH query, and FE/GE query.

14.1.2 Testing the Local E1/T1 LoopbackThis describes how to test whether the local E1/T1 link is connected normally.

14.1.3 Testing the Remote E1/T1 LoopbackThis describes how to test whether the remote E1/T1 link is connected normally.

14.1.4 Testing the E1/T1 BERThis describes how to test the BER of the E1/T1 link.

14.1.5 Testing the E1/T1 LoopbackThis describes how to check whether the E1/T1 loopback exists.

14.1.6 Testing E1/T1 Wrong ConnectionThis describes how to test the E1/T1 wrong connection.

14.1.7 Testing the SDH LoopbackThis describes how to test whether the SDH link is connected normally.

14.1.8 Querying SDHThis describes how to query SDH information including optical port status and performancestatistics.

14.1.9 Querying FE/GEThis describes how to query the information on FE/GE ports and the Ethernet port status.

14.1.1 Physical Layer TestingThe 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 connectiontest, 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

Item Function

Local E1/T1loopback

The test is performed to check whether the local E1/T1 link is connectednormally.

Remote E1/T1loopback

The test is performed to check whether the remote E1/T1 link isconnected normally.

E1/T1 BER The test is performed on the BER of the E1/T1 link.

14 Testing RNC FaultsRNC

LMT User Guide


Issue 03 (2009-04-25)

Item Function

E1/T1 loopback The test is performed to check whether the E1/T1 loopback exists.

E1/T1 wrongconnection

The test is performed on the wrong connection detection function of thetested object, that is, to check whether the E1/T1 wrong connectionexists according to the collected RX and TX link information.

SDH loopback The test is performed to check whether the SDH link is connectednormally.

SDH The test is performed to query the optical port status and performancestatistics.

FE/GE The test is performed to query the Ethernet port status.

14.1.2 Testing the Local E1/T1 LoopbackThis describes how to test whether the local E1/T1 link is connected normally.



Context

CAUTIONl 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 theparameters, and then click OK. The message browse window displays the results and relatedinformation in text format.

----End

Related Tasks14.4.1 Browsing Fault Testing Results14.4.2 Manually Saving Fault Testing Results14.4.3 Stopping a Fault Testing Task



14-3

Related References14.5.1 Parameter Reference for the Local E1/T1 Loopback Test

14.1.3 Testing the Remote E1/T1 LoopbackThis describes how to test whether the remote E1/T1 link is connected normally.



Context

CAUTIONl This fault test may affect services. Do not perform the test on a normal E1/T1 link.


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 RemoteE1/T1 Loopback Test.

Step 2 In the 14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test dialog box, set theparameters, and then click OK. The message browse window displays the results and relatedinformation in text format.

----End


Related References14.5.2 Parameter Reference for the Remote E1/T1 Loopback Test

14.1.4 Testing the E1/T1 BERThis describes how to test the BER of the E1/T1 link.



LMT User Guide


Issue 03 (2009-04-25)


Context

During the BER test, the LMT sends pseudo codes to all timeslots of the specified links. Thenit 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 BERtest. Thus the accuracy of testing results is limited. To obtain accurate BER data, use a toolspecialized for the BER test.

CAUTIONl Perform this task with caution for it affects current services.


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

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 References14.5.3 Parameter Reference for the E1/T1 BER Test

14.1.5 Testing the E1/T1 LoopbackThis describes how to check whether the E1/T1 loopback exists.





14-5

Context

CAUTIONThis 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/T1Loopback Test.

Step 2 In the 14.5.4 Parameter Reference for the E1/T1 Loopback Test dialog box, set theparameters, and then click OK. The message browse window displays the results and relatedinformation in text format.

----End


Related References14.5.4 Parameter Reference for the E1/T1 Loopback Test

14.1.6 Testing E1/T1 Wrong ConnectionThis describes how to test the E1/T1 wrong connection.



Procedure

Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click E1/T1Wrong Connect Test.

Step 2 In the 14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test dialog box, set theparameters, and then click OK. The message browse window displays the results and relatedinformation in text format.

----End

Related Tasks14.4.1 Browsing Fault Testing Results14.4.2 Manually Saving Fault Testing Results


LMT User Guide


Issue 03 (2009-04-25)

14.4.3 Stopping a Fault Testing Task

Related References14.5.5 Parameter Reference for the E1/T1 Wrong Connection Test

14.1.7 Testing the SDH LoopbackThis describes how to test whether the SDH link is connected normally.



ProcedureStep 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 intext format.

----End


Related References14.5.6 Parameter Reference for the SDH Loopback Test

14.1.8 Querying SDHThis describes how to query SDH information including optical port status and performancestatistics.



ProcedureStep 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 thenclick OK. The message browse window displays the testing results in text format.

----End



14-7


Related References14.5.7 Parameter Reference for SDH Query

14.1.9 Querying FE/GEThis describes how to query the information on FE/GE ports and the Ethernet port status.



Procedure

Step 1 In the Fault Test pane, expand the Physical layer tests node, and then double-click FE/GEQuery.

Step 2 In the 14.5.8 Parameter Reference for FE/GE Query dialog box, set the parameters, and thenclick OK. The message browse window displays the testing results in text format.

----End


Related References14.5.8 Parameter Reference for FE/GE Query

14.2 Testing Faults on the Link LayerThis describes how to test faults on the link layer. The link layer testing provides the followingtests and queries: the AAL2 path test, SAAL link test, SCTP link test, PPP/MLPPP wrongconnection test, NodeB maintenance IPoA test, and Iu-PS IPoA test.

14.2.1 Link Layer TestingBy performing this task, you can learn about the functions of each link layer test. The link layertesting provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP linktest, PPP/MLPPP wrong connection test, PPP/MLPPP link query, NodeB maintenance IPoAtest, Iu-PS IPoA test, and IMA query.

14.2.2 Testing the AAL2 PathThis describes how to test the AAL2 path and to report the related data for fault location.


LMT User Guide


Issue 03 (2009-04-25)

14.2.3 Testing the SAAL LinkThis describes how to test the SAAL link and to report the related data for fault location.

14.2.4 Testing the SCTP LinkThis describes how to test the SCTP link and to report the related data for fault location.

14.2.5 Testing PPP/MLPPP Wrong ConnectionThis describes how to test the PPP/MLPPP wrong connection functions and to check whetherthe terminal description characters between the two link ends are consistent.

14.2.6 Querying an PPP/MLPPP LinkThis describes how to query the PPP link status, MLPPP group status, and status of the MLPPPlinks in the MLPPP group.

14.2.7 Testing the NodeB Maintenance IPoA LinkThis describes how to test the NodeB maintenance IPoA link and to report the related data forfault location.

14.2.8 Testing the Iu-PS IPoA LinkThis describes how to test the Iu-PS IPoA link and to report the related data for fault location.

14.2.9 Querying IMAThe describes how to query the IMA group status and status of the IMA links in the IMA group.

14.2.1 Link Layer TestingBy performing this task, you can learn about the functions of each link layer test. The link layertesting provides the following tests and queries: the AAL2 path test, SAAL link test, SCTP linktest, PPP/MLPPP wrong connection test, PPP/MLPPP link query, NodeB maintenance IPoAtest, 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

Item Function

AAL2 path The test is performed on the faulty AAL2 link and the related data isreported for fault location and analysis.

SAAL link The test is performed on the faulty SAAL link and the related data isreported for fault location and analysis.

SCTP link The test is performed on the SCTP link and the related data is reported forfault location and analysis.

PPP/MLPPPwrongconnection

The test is performed on the PPP/MLPPP wrong connection to checkwhether the terminal description characters between the two link ends areconsistent.

PPP/MLPPPlink

This describes how to query the PPP link status, MLPPP group status, andstatus of the MLPPP links in the MLPPP group.

NodeBmaintenanceIPoA

The test is performed on the NodeB maintenance IPoA link and the relateddata is reported for fault location and analysis.



14-9

Item Function

Iu-PS IPoA link The test is performed on the Iu-PS IPoA link and the related data isreported for fault location and analysis.

IMA The test is performed to query the IMA group status and status of the IMAlinks in the IMA group.

14.2.2 Testing the AAL2 PathThis describes how to test the AAL2 path and to report the related data for fault location.



Context

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

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. Duringthe test, the LMT collects the traffic statistics of the chips that the AAL2 path passes through. Thestatistics and the quantities of the data packets received and sent are displayed in the message browsewindow in text format. Then, the LMT automatically restores itself to the original state, includingdeleting the L2 instance.

l If CID loop is selected, you can judge whether the AAL2 path loop is functional by comparing thequantities of received and sent data packets.

----End



LMT User Guide


Issue 03 (2009-04-25)

Related References14.5.9 Parameter Reference for the AAL2 Path Test

14.2.3 Testing the SAAL LinkThis describes how to test the SAAL link and to report the related data for fault location.



Context

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

Step 2 In the 14.5.10 Parameter Reference for SAAL Link Test dialog box, set the parameters, andthen click OK.

NOTE

After this task is started, the LMT queries the details of the SAAL bearing link (IMA group, UNI, fractionalATM, or E1/T1/SDH), and then collects statistics about the chip traffic passing through the IPoA channelfor multiple times. The message browse window displays the collected traffic information on each chip intext format. Then the LMT automatically restores itself to the original state.

----End


Related References14.5.10 Parameter Reference for SAAL Link Test

14.2.4 Testing the SCTP LinkThis describes how to test the SCTP link and to report the related data for fault location.



14-11



Context

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

Step 2 In the 14.5.11 Parameter Reference for SCTP Link Test dialog box, set the parameters, andthen click OK.

NOTE

After this task is started, the LMT queries the details of the SCTP bearing link (IMA group, UNI, fractionalATM, or E1/T1/SDH), and then collects statistics about the chip traffic passing through the IPoA channelfor multiple times. The message browse window displays the collected traffic information on each chip intext format. Then the LMT automatically restores itself to the original state.

----End


Related References14.5.11 Parameter Reference for SCTP Link Test

14.2.5 Testing PPP/MLPPP Wrong ConnectionThis describes how to test the PPP/MLPPP wrong connection functions and to check whetherthe terminal description characters between the two link ends are consistent.



Procedure

Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click PPP/MLPPPWrong Connect Test.


LMT User Guide


Issue 03 (2009-04-25)

Step 2 In the 14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test dialogbox, set the parameters, and then click OK. The message browse window displays the testingresults in text format.

----End


Related References14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection Test

14.2.6 Querying an PPP/MLPPP LinkThis describes how to query the PPP link status, MLPPP group status, and status of the MLPPPlinks in the MLPPP group.



Procedure

Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click PPP/MLPPPQuery.

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 References14.5.13 Parameter Reference for PPP/MLPPP Query

14.2.7 Testing the NodeB Maintenance IPoA LinkThis describes how to test the NodeB maintenance IPoA link and to report the related data forfault location.



14-13



Context

CAUTIONThis fault test may affect services. Do not perform the test on a normal NodeB maintenanceIPoA link.

Procedure

Step 1 In the Fault Test pane, expand the Link layer tests node, and then double-click NodeBmaintenance IPoA link test.

Step 2 In the 14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test dialog box, setthe parameters, and then click OK.

NOTE

After this task is started, the LMT queries the details of the IPoA bearing link (IMA group, UNI, fractionalATM 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 References14.5.14 Parameter Reference for the NodeB Maintenance IPoA Test

14.2.8 Testing the Iu-PS IPoA LinkThis describes how to test the Iu-PS IPoA link and to report the related data for fault location.




LMT User Guide


Issue 03 (2009-04-25)

Context

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

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, fractionalATM, or E1/T1/SDH). Then it creates an L2 instance to send and receive data packets. During the test, theLMT collects statistics about the chip traffic passing through the IPoA channel. The message browsewindow displays the collected traffic information on each chip and the quantities of the data packetsreceived and sent in text format. After the task is complete, the LMT automatically restores itself to theoriginal state, including canceling the TEID loopback and deleting the L2 instance.

----End


Related References14.5.15 Parameter Reference for the Iu-PS IPoA Test

14.2.9 Querying IMAThe describes how to query the IMA group status and status of the IMA links in the IMA group.



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 thenclick OK. The message browse window displays the testing results in text format.

----End



14-15


Related References14.5.16 Parameter Reference for IMA Query

14.3 Testing Other RNC FaultsThis describes how to test other RNC faults, including the IPC connectivity test, cell commonchannel test, RFN test, clock test, and board load control test.

14.3.1 Other TestsThe RNC provides the following additional tests: the IPC connectivity test, cell common channeltest, RFN test, clock test, and board load control test.

14.3.2 Testing IPC ConnectivityThis describes how to test the IPC connectivity by periodically collecting the statistics about theRX/TX traffic on each port of the IPC node, or collecting traffic statistics and status informationon the IPC node.

14.3.3 Testing the Cell Common ChannelThis describes how to test a faulty common channel of a cell and report the related data to locatethe fault.

14.3.4 Testing RFNThis describes how to test faulty RNC Frame Numbers (RFNs). The test reports the data relatedto RFNs of all boards in position except the interface boards in specified subracks to locate thefault.

14.3.5 Testing the ClockThis describes how to conduct a test on faulty clocks. All the related data of the clocks of boardsin position in the specified subrack is reported for fault location and analysis.

14.3.6 Testing Load Control of a BoardThis describes how to conduct a test on the board where load control faults occur. The test reportsthe related data of the specified board with load control faults to locate and analyze the fault.

14.3.1 Other TestsThe RNC provides the following additional tests: the IPC connectivity test, cell common channeltest, RFN test, clock test, and board load control test.

Table 14-3 describes the items of the tests.


LMT User Guide


Issue 03 (2009-04-25)

Table 14-3 Items of other tests

Item Function

IPC connectivity The test is performed to periodically collect the statistics about theRX/TX traffic on each port of the IPC node, or to collect trafficstatistics and status information on the IPC node. After this task isperformed, the IPC connectivity can be tested.

Cell common channel The test is performed on a faulty common channel of a cell and therelated data is reported for fault location and analysis.

RFN The test is performed on faulty RFNs. The data related to RFNs ofall boards in position except the interface boards in specified subracksis reported for fault location and analysis.

Clock The test is performed on faulty clocks. All the related data of theclocks of boards in position in the specified subrack is reported forfault location and analysis.

Load control of aboard

The test is performed on the board where a load control fault occurs.The related data of the specified board with load control faults isreported for fault location and analysis.

14.3.2 Testing IPC ConnectivityThis describes how to test the IPC connectivity by periodically collecting the statistics about theRX/TX traffic on each port of the IPC node, or collecting traffic statistics and status informationon the IPC node.



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 theparameters, and then click OK. The message browse window displays the testing results in textformat.

NOTE

After this task is started, the system periodically collects the statistics about the RX/TX traffic on each portof the IPC node or collects traffic statistics and state messages of the IPC node.

----End




14-17

Related References14.5.17 Parameter Reference for the IPC Connectivity Test

14.3.3 Testing the Cell Common ChannelThis describes how to test a faulty common channel of a cell and report the related data to locatethe fault.



Context

CAUTIONThis 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 CommonChannel Test.

Step 2 In the 14.5.18 Parameter Reference for the Cell Common Channel Test dialog box, set theparameters, and then click OK.

NOTE

l After this task is started, the LMT queries the configuration of this cell. Then it creates an L2 instanceto send and receive data packets. During the test, the LMT collects the traffic statistics of the chips thatthe AAL2 path passes through. The message browse window displays the collected traffic informationon each chip and the quantities of the data packets received and sent in text format. Then the LMTautomatically restores itself to the original state, including canceling the CID loopback and deletingthe L2 instance.

l If CID Loop is selected, you can judge whether the AAL2 path loop is functional by comparing thequantities of received and transmitted data packets.

----End


Related References14.5.18 Parameter Reference for the Cell Common Channel Test


LMT User Guide


Issue 03 (2009-04-25)

14.3.4 Testing RFNThis describes how to test faulty RNC Frame Numbers (RFNs). The test reports the data relatedto RFNs of all boards in position except the interface boards in specified subracks to locate thefault.



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

NOTE

l After this task is started, the LMT queries in sequence the related data of RFNs of all boards in positionexcept the interface boards in specified subracks. The message browse window displays the testingresults in text format.

l Only one RBS works as the RFN source subrack in a BSC6810. All the other RBSs work as RFNdestination subracks.

----End


Related References14.5.19 Parameter Reference for the RFN Test

14.3.5 Testing the ClockThis describes how to conduct a test on faulty clocks. All the related data of the clocks of boardsin position in the specified subrack is reported for fault location and analysis.



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, andthen click OK.



14-19

NOTE

After the task is started, the LMT queries the related data of the faulty clock on the specified board. Themessage browse window displays the testing results in text format.

----End


Related References14.5.20 Parameter Reference for the Clock Test

14.3.6 Testing Load Control of a BoardThis describes how to conduct a test on the board where load control faults occur. The test reportsthe related data of the specified board with load control faults to locate and analyze the fault.



Context

CAUTIONThis 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 Testof The Boards.

Step 2 In the 14.5.21 Parameter Reference for the Load Control Test of the Boards dialog box, setthe parameters, and then click OK. The message browse window displays the testing results intext format.

----End



LMT User Guide


Issue 03 (2009-04-25)

Related References14.5.21 Parameter Reference for the Load Control Test of the Boards

14.4 Basic Operations of the RNC Fault TestsThis describes how to browse and save the fault testing results and how to stop a fault testingtask.

14.4.1 Browsing Fault Testing ResultsThis describes how to browse fault testing results displayed in text format in the Fault Testwindow. By performing this task, you can browse the testing results and locate the fault.

14.4.2 Manually Saving Fault Testing ResultsThis describes how to manually save the results of a fault testing task.

14.4.3 Stopping a Fault Testing TaskThis describes how to stop a fault testing task.

14.4.1 Browsing Fault Testing ResultsThis describes how to browse fault testing results displayed in text format in the Fault Testwindow. By performing this task, you can browse the testing results and locate the fault.


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 ResultsThis describes how to manually save the results of a fault testing task.


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 boxis displayed, as shown in Figure 14-1.



14-21

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 installationdirectory\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 TaskThis describes how to stop a fault testing task.

PrerequisiteA 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 TestsThis describes the parameters used for each RNC fault test.

14.5.1 Parameter Reference for the Local E1/T1 Loopback TestThis describes the parameters used for the local E1/T1 loopback test.


LMT User Guide


Issue 03 (2009-04-25)

14.5.2 Parameter Reference for the Remote E1/T1 Loopback TestThis describes the parameters used for the remote E1/T1 loopback test.

14.5.3 Parameter Reference for the E1/T1 BER TestThis describes the parameters used for the E1/T1 BER test.

14.5.4 Parameter Reference for the E1/T1 Loopback TestThis describes the parameters for the E1/T1 loopback test.

14.5.5 Parameter Reference for the E1/T1 Wrong Connection TestThis describes the parameters used for the E1/T1 wrong connection test.

14.5.6 Parameter Reference for the SDH Loopback TestThis describes the parameters for the SDH loopback test.

14.5.7 Parameter Reference for SDH QueryThis describes the parameters used for SDH query.

14.5.8 Parameter Reference for FE/GE QueryThis describes the parameters used for FE/GE query.

14.5.9 Parameter Reference for the AAL2 Path TestThis describes the parameters used for the AAL2 path test.

14.5.10 Parameter Reference for SAAL Link TestThis describes the parameters used for the SAAL link test.

14.5.11 Parameter Reference for SCTP Link TestThis describes the parameters for the SCTP link test.

14.5.12 Parameter Reference for the PPP/MLPPP Wrong Connection TestThis describes the parameters used for the PPP/MLPPP wrong connection test.

14.5.13 Parameter Reference for PPP/MLPPP QueryThis describes the parameters for PPP/MLPPP query.

14.5.14 Parameter Reference for the NodeB Maintenance IPoA TestThis describes the parameters for the NodeB maintenance IPoA test.

14.5.15 Parameter Reference for the Iu-PS IPoA TestThis describes the parameters used for the Iu-PS IPoA test.

14.5.16 Parameter Reference for IMA QueryThis describes the parameters used for IMA query.

14.5.17 Parameter Reference for the IPC Connectivity TestThis describes the parameters used for the IPC connectivity test.

14.5.18 Parameter Reference for the Cell Common Channel TestThis describes the parameters used for the cell common channel test.

14.5.19 Parameter Reference for the RFN TestThis describes the parameters used for the RFN test.

14.5.20 Parameter Reference for the Clock TestThis describes the parameters used for the clock test.

14.5.21 Parameter Reference for the Load Control Test of the BoardsThis describes the parameters used for the load control test of the boards.



14-23

14.5.1 Parameter Reference for the Local E1/T1 Loopback TestThis 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 testedOnly 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 electricalport or the AOUa optical port.

Link No. Number of the link to be testedl 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.

CAUTIONThe OMUa does not support the local E1/T1 loopback test. Therefore, slots 20 to 23 areunavailable when subrack 0 is selected.

Related Tasks14.1.2 Testing the Local E1/T1 Loopback

14.5.2 Parameter Reference for the Remote E1/T1 Loopback TestThis describes the parameters used for the remote E1/T1 loopback test.

Table 14-5 Parameters for the remote E1/T1 loopback test

Field Description


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 portor the AOUa optical port.


LMT User Guide


Issue 03 (2009-04-25)

Field Description

Link No. Number of the link to be testedl 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.

CAUTIONThe OMUa does not support the remote E1/T1 loopback test. Therefore, slots 20 to 23 areunavailable when subrack 0 is selected.

Related Tasks14.1.3 Testing the Remote E1/T1 Loopback

14.5.3 Parameter Reference for the E1/T1 BER TestThis describes the parameters used for the E1/T1 BER test.

Table 14-6 Parameters for the E1/T1 BER test

Field Description



Port type Type of port to be tested. The port can be an AEUa/PEUa electricalport or the AOUa optical port.

Link No. Number of the link to be testedl 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.

Unit time[ms] Unit time of the BER testl 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.

CAUTIONThe OMUa does not support the E1/T1 BER test. Therefore, slots 20 to 23 are unavailable whensubrack 0 is selected.



14-25

Related Tasks14.1.4 Testing the E1/T1 BER

14.5.4 Parameter Reference for the E1/T1 Loopback TestThis describes the parameters for the E1/T1 loopback test.

Table 14-7 Parameters for the E1/T1 loopback test

Field Description



Detect single To check whether loopback exists on a E1/T1 link, select Detect single. Thelink number is required.

Detect all To check whether loopback exists on all the links, select Detect all. The linknumber 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.

CAUTIONThe OMUa does not support the E1/T1 loopback test. Therefore, slots 20 to 23 are unavailablewhen subrack 0 is selected.

Related Tasks14.1.5 Testing the E1/T1 Loopback

14.5.5 Parameter Reference for the E1/T1 Wrong Connection TestThis describes the parameters used for the E1/T1 wrong connection test.

Table 14-8 Parameters for the E1/T1 wrong connection test

Field Description



Link No. Number of the link to be tested. Value range: 0 to 167.

CAUTIONThe OMUa does not support the E1/T1 wrong connection test. Therefore, slots 20 to 23 areunavailable when subrack 0 is selected.


LMT User Guide


Issue 03 (2009-04-25)

Related Tasks14.1.6 Testing E1/T1 Wrong Connection

14.5.6 Parameter Reference for the SDH Loopback TestThis describes the parameters for the SDH loopback test.

Table 14-9 Parameters for the SDH loopback test

Field Description


Slot No. Number of the slot to be testedThe 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, RemoteLoop.

CAUTIONThe OMUa does not support the SDH loopback test. Therefore, slots 20 to 23 are unavailablewhen subrack 0 is selected.

Related Tasks14.1.7 Testing the SDH Loopback

14.5.7 Parameter Reference for SDH QueryThis describes the parameters used for SDH query.

Table 14-10 Parameters for SDH query

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. Valuerange: 14 to 27.

Board Type Type of the board where the optical port is located. Valuerange: AOUa/POUa, UOIa.



14-27

Field Description

Port No. l When the board type is AOUa/POUa, the port number is0 or 1.

l When the board type is UOIa, the port number is 0 or 7.

Performance Type l When the performance type is GROUP, the optical portstatus and performance statistics are displayed.

l When the performance type is LINK, the link status andperformance statistics are displayed.

Link No. l When the multiplexed link on the optical port is an E1link, 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.

CAUTIONThe OMUa does not support SDH query. Therefore, slots 20 to 23 are unavailable when subrack0 is selected.

Related Tasks14.1.8 Querying SDH

14.5.8 Parameter Reference for FE/GE QueryThis describes the parameters used for FE/GE query.

Table 14-11 Parameters for FE/GE query

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. Valuerange: FG2a, GOUa.

Port No. l When the board type is FG2a, the port number ranges from0 to 7.

l When the board type is GOUa, the port number is 0 or 1.


LMT User Guide


Issue 03 (2009-04-25)

CAUTIONThe OMUa does not support FE/GE query. Therefore, slots 20 to 23 are unavailable whensubrack 0 is selected.

Related Tasks14.1.9 Querying FE/GE

14.5.9 Parameter Reference for the AAL2 Path TestThis 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 nodesThe IDs of the same AAL2 path configured at two adjacent nodes mustbe the same and must not be 0. Value range: 1 to 4294967295.

test interval Duration for the L2 instance established for the test to continuouslysend 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 Tasks14.2.2 Testing the AAL2 Path

14.5.10 Parameter Reference for SAAL Link TestThis describes the parameters used for the SAAL link test.

Table 14-13 Parameters for the SAAL link test

Field Description

Subrack No. Number of the subrack terminating the SAAL link. Value range:0 to 5.



14-29

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. Valuerange: 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 Tasks14.2.3 Testing the SAAL Link

14.5.11 Parameter Reference for SCTP Link TestThis describes the parameters for the SCTP link test.

Table 14-14 Parameters for the SCTP link test

Field Description


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 Tasks14.2.4 Testing the SCTP Link

14.5.12 Parameter Reference for the PPP/MLPPP Wrong ConnectionTest

This describes the parameters used for the PPP/MLPPP wrong connection test.


LMT User Guide


Issue 03 (2009-04-25)

Table 14-15 Parameters for the PPP/MLPPP wrong connection test

Field Description



MLPPP link No. Number of the link to be tested. Value range: 0 to 127.

CAUTIONThe OMUa does not support the PPP/MLPPP wrong connection test. Therefore, slots 20 to 23are unavailable when subrack 0 is selected.

Related Tasks14.2.5 Testing PPP/MLPPP Wrong Connection

14.5.13 Parameter Reference for PPP/MLPPP QueryThis 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 bequeried is located. Value range: 0 to 5.

Slot No. Number of the slot where the PPP link or MLPPP group to be queriedis located. Value range: 14 to 27.

Query Type This parameter specifies which to query, a PPP link or an MLPPPgroup. Value range: PPPLINK, MLPPPGROUP.

PPPLINK No./MLPPPGROUP No.

When the query type is PPPLINK, the number of the PPP link or theMLPPP group ranges from 0 to 127.When the query type is MLPPPGROUP, the number of the PPP linkor the MLPPP group ranges from 0 to 127.

CAUTIONThe OMUa does not support PPP/MLPPP query. Therefore, slots 20 to 23 are unavailable whensubrack 0 is selected.

Related Tasks14.2.6 Querying an PPP/MLPPP Link



14-31

14.5.14 Parameter Reference for the NodeB Maintenance IPoA TestThis 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 Tasks14.2.7 Testing the NodeB Maintenance IPoA Link

14.5.15 Parameter Reference for the Iu-PS IPoA TestThis 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 wherethe DSP runs properly. Value range: 0 to 5.

DPU No. Number of a DPU slot where the DSP runs properly. Valuerange: 8 to 19.

DSP No. To select a properly running DSP. Value range: 0 to 21.

Test Interval Duration for the L2 instance established for the test tocontinuously send data packets. Value range: 30 to 3600. Unit:second.

Test Packet Size Size of the data packets sent by an L2 instance established forthe test. Value range: 40 to 1500. Unit: byte.

Test Source Speed Rate of the data packets sent by an L2 instance established forthe 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 Tasks14.2.8 Testing the Iu-PS IPoA Link


LMT User Guide


Issue 03 (2009-04-25)

14.5.16 Parameter Reference for IMA QueryThis 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 tobe queried is located. Value range: 0 to 5.

Slot No. Number of the slot where the IMA link group to bequeried is located. Value range: 14 to 27.

IMA Group No. Number of the IMA link group to be queried. Valuerange: 0 to 83.

CAUTIONThe OMUa does not support IMA query. Therefore, slots 20 to 23 are unavailable when subrack0 is selected.

Related Tasks14.2.9 Querying IMA

14.5.17 Parameter Reference for the IPC Connectivity TestThis describes the parameters used for the IPC connectivity test.

Table 14-20 Parameters for the IPC connectivity test

Field Description

IPC low subrackinfo.

Subrack No. Number of the subrack containing the IPC low subrackinformation to be tested. Value range: 0 to 5.

Slot No. Number of the slot containing the IPC low subrackinformation to be tested. Value range: 0, 2, 4, 8,10.

Subsystem No. Number of the subsystem containing the IPC lowsubrack information to be tested. Value range: 0 to 3.

IPC high subrackinfo.

Subrack No. Number of the subrack containing the IPC highsubrack information to be tested. Value range: 0 to 5.

Slot No. Number of the slot containing the IPC high subrackinformation to be tested. Value range: 0 to 27.

Subsystem No. Number of the subsystem containing the IPC highsubrack information to be tested. Value range: 0 to 21.



14-33

CAUTIONDuring the IP high subrack information test, if subrack 0 is selected, slots 20 to 23 are unavailable.

Related Tasks14.3.2 Testing IPC Connectivity

14.5.18 Parameter Reference for the Cell Common Channel TestThis 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 Duration for the L2 instance established for the test to continuouslysend data packets. Value range: 30 to 3600. Unit: second.

Transport ChannelID

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 Tasks14.3.3 Testing the Cell Common Channel

14.5.19 Parameter Reference for the RFN TestThis describes the parameters used for the RFN test.

Table 14-22 Parameters for the RFN test

Field Description

RFN Destination Subrack No. Number of the RFN Destination subrack.Value range: 0 to 5.

Slot No. Number of the slot to be tested. Value range:0 to 27.

Subsystem No. Number of the subsystem to be tested. Valuerange: 0 to 3.


LMT User Guide


Issue 03 (2009-04-25)

CAUTIONThe OMUa does not support the RFN test. Therefore, slots 20 to 23 are unavailable when subrack0 is selected.

Related Tasks14.3.4 Testing RFN

14.5.20 Parameter Reference for the Clock TestThis describes the parameters used for the clock test.

Table 14-23 Parameters for the clock test

Field Description

Subrack No. Number of the subrack to be tested. Valuerange: 0 to 5.

Slot No. Number of the slot to be tested. Value range:0 to 27.

Subsystem No. Number of the subsystem to be tested. Valuerange: 0 to 3.

CAUTIONThe OMUa does not support the clock test. Therefore, slots 20 to 23 are unavailable when subrack0 is selected.

Related Tasks14.3.5 Testing the Clock

14.5.21 Parameter Reference for the Load Control Test of the BoardsThis describes the parameters used for the load control test of the boards.

Table 14-24 Parameters for the load control test of the boards

Field Description

Subrack No. Number of the subrack to be tested. Value range: 0to 5.


Subsystem No. Number of the subsystem to be tested. Value range:0 to 3.



14-35

CAUTIONThe OMUa does not support the load control test of boards. Therefore, slots 20 to 23 areunavailable when subrack 0 is selected.

Related Tasks14.3.6 Testing Load Control of a Board


LMT User Guide


Issue 03 (2009-04-25)

15 Using the RNC LMT PerformanceBrowser 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 ToolThis describes how to start the Performance Browser Tool to browse the performancemeasurement results which are stored in the RNC.

15.2 Setting the Parameters of the RNC LMT Performance Browser ToolThis describes how to set the parameters of the RNC LMT Performance Browser Tool, includingsetting the measurement description file and the FTP.

15.3 Browsing Description FilesThis describes how to browse the measurement description files.

15.4 Downloading Performance Measurement ResultsThis describes how to log in to the BAM through FTP and download the performancemeasurement results. The Performance Browser Tool provides two ways for FTP download:manual mode and automatic mode.

15.5 Querying Performance Measurement DataThis describes how to browse the files (in .mrf or .xml format) of performance measurementresults in the local computer.

15.6 Filtering Performance Measurement DataThis describes how to set the time, objects, counters, and conditions to filter performancemeasurement data. You can filter the data based on different combination of the filteringrequirements.

15.7 Exporting Performance Measurement DataThis describes how to export the files of the queried performance measurement data and savethe files in the local computer in .csv format.

15.8 Exiting the RNC LMT Performance Browser ToolThis describes how to exit the Performance Browser Tool when the browse is complete.

RNCLMT User Guide 15 Using the RNC LMT Performance Browser Tool


15-1

15.1 Starting the RNC LMT Performance Browser ToolThis describes how to start the Performance Browser Tool to browse the performancemeasurement results which are stored in the RNC.

PrerequisiteThe 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 PerformanceBrowser Tool

This describes how to set the parameters of the RNC LMT Performance Browser Tool, includingsetting the measurement description file and the FTP.

PrerequisiteThe Performance Browser Tool is started.

Procedure

Step 1 When you start the Performance Browser Tool for the first time, the Select Net dialog box isdisplayed, 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 shownin Figure 15-2.

15 Using the RNC LMT Performance Browser ToolRNC

LMT User Guide


Issue 03 (2009-04-25)

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 advisedto set the directory to /BAM active workspace installation directory/FTP/MeasResult.

FTPConfigurationTest

To test if the parameters in the FTP Config area are configured successfully,click this button. If the configuration is successful, a Test Succeed! messageis displayed on the left area. Otherwise, a Test Failed! message is displayed.



15-3

Name Description

Local Result The directory under which the measurement data downloaded from the FTPserver is saved on the local computer. The default directory is LMTinstallation directory/adaptor/clientadaptor/pfbTool/data. You can setthe 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 LMTinstallation 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 to selectthe file.

Address List 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 FilesThis describes how to browse the measurement description files.

Prerequisitel 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 . The Browse Description File window is displayed, as shown in Figure 15-3.


LMT User Guide


Issue 03 (2009-04-25)

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



15-5

----End

15.4 Downloading Performance Measurement ResultsThis describes how to log in to the BAM through FTP and download the performancemeasurement results. The Performance Browser Tool provides two ways for FTP download:manual mode and automatic mode.

PrerequisiteThe parameters of the FTP server are set correctly.

Procedurel In manual mode

1. Choose File > Download Measurement Results. The Download MeasurementResults dialog box is displayed, as shown in Figure 15-5.

Figure 15-5 Downloading the measurement results

2. Select the file in the FTP Server Directory pane.

3. Click Download. The Local Directory pane displays the directory under which thedownloaded data is stored.

l In automatic mode

1. Choose System > Auto Download Settings. The Auto Download Settings dialogbox is displayed, as shown in Figure 15-6.


LMT User Guide


Issue 03 (2009-04-25)

Figure 15-6 Auto Download Settings dialog box

2. Click Add. In the Add dialog box, select one check box under Download Flag to addan 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 DownloadTime.

4. Click OK. The LMT returns to the Auto Download Settings dialog box and displaysthe download list in sequence of time.

5. Click OK.

----End

15.5 Querying Performance Measurement DataThis describes how to browse the files (in .mrf or .xml format) of performance measurementresults in the local computer.



15-7

Prerequisitel 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 setcounters and click the Time Information tab to set time.

Step 3 Click Query to query the performance data.

----End

15.6 Filtering Performance Measurement DataThis describes how to set the time, objects, counters, and conditions to filter performancemeasurement data. You can filter the data based on different combination of the filteringrequirements.

PrerequisiteThe query of performance measurement data is successfully performed and the queried data isavailable.


LMT User Guide


Issue 03 (2009-04-25)

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 Figure15-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 DataThis describes how to export the files of the queried performance measurement data and savethe files in the local computer in .csv format.

Prerequisitel You have successfully logged in to the Performance Browser Tool.

l The query of performance measurement data is successfully performed and the querieddata is available.



15-9

l 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 Figure15-10.


Step 3 Click Save to save the exported data.

----End

15.8 Exiting the RNC LMT Performance Browser ToolThis describes how to exit the Performance Browser Tool when the browse is complete.

PrerequisiteThe Performance Browser Tool is successfully started.

ContextTo exit the Performance Browser Tool, you can select either of the following ways:


LMT User Guide


Issue 03 (2009-04-25)

Procedurel Choose System > Exit.

l Click in the upper right corner of the window.

----End



15-11

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 canuse 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 ClientThis describes how to log in to the RNC FTP server on the LMT FTP Client in encryption modeor plaintext mode.

16.2 Uploading Data Files to the RNC FTP ServerThis describes how to upload data files to the RNC FTP server. By performing this task, youcan use the FTP Client to upload data files to the RNC FTP server after the FTP Client connectsto the FTP server.

16.3 Downloading Data Files from the RNC FTP ServerThis 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 Clientconnects to the FTP server.

16.4 Setting the Encryption Mode of the RNC FTP ServerThis describes how to set the encryption mode of the RNC FTP server. After the setting, youmust log in to the LMT FTP Client in the active encryption mode.

16.5 Querying the Encryption Mode of the RNC FTP ServerThis describes how to query the encryption mode of the RNC FTP server. By performing thistask, you can learn about the active encryption mode of the RNC FTP server.

16.6 Disconnecting the LMT FTP Client from the RNC FTP ServerThis describes how to disconnect the LMT FTP Client from the RNC FTP server.

RNCLMT User Guide 16 Using the FTP Client of the RNC LMT


16-1

16.1 Logging in to the FTP Server on the LMT FTP ClientThis describes how to log in to the RNC FTP server on the LMT FTP Client in encryption modeor plaintext mode.

Prerequisitel 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, validuser name and password of the FTP server.

Procedure

Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. TheFTP 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 enterthe 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, referto Table 16-1.

16 Using the FTP Client of the RNC LMTRNC

LMT User Guide


Issue 03 (2009-04-25)

Table 16-1 Implementation method of encryption

Encryption Policy Implementation Method

Encryption Only data channelencrypted

Select SSL and CCC.

Data channel encryptionand command channelencryption

Select only SSL.

Non-encryption -

Step 4 Click or choose System > Connect to connect the RNC FTP server.

If... Then...

The connectionfails

A fault message is displayed. Check whether the server IP address, username, and password are valid. Go to Step 2.

The connection issuccessful

The Connection tips pane displays Successfully log ontoserver.

----End

16.2 Uploading Data Files to the RNC FTP ServerThis describes how to upload data files to the RNC FTP server. By performing this task, youcan use the FTP Client to upload data files to the RNC FTP server after the FTP Client connectsto 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 chooseto upload files in encryption mode, you must log in to the FTP server. For details, refer to 16.1Logging 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 theuploaded file.

Step 3 Upload a file by using either of the following methods:

l Click .

l Double-click the file.



16-3

l Choose Transfer > Upload To Server.

NOTE

After the file is uploaded, the Connection tips pane displays a message, showing that the uploading issuccessful. The uploaded file is displayed in the Server List pane.

----End

16.3 Downloading Data Files from the RNC FTP ServerThis 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 Clientconnects to the FTP server.

PrerequisiteThe 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 youchoose 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 downloadingis successful. The downloaded file is displayed in the Local File List pane.

----End

16.4 Setting the Encryption Mode of the RNC FTP ServerThis describes how to set the encryption mode of the RNC FTP server. After the setting, youmust log in to the LMT FTP Client in the active encryption mode.


l You have logged in to the RNC as admin or an ADMINISTRATOR-level operator.


LMT User Guide


Issue 03 (2009-04-25)

Procedure

Run the SET FTPSSRV command on the MML client to set the active encryption mode of theRNC FTP server.

NOTE

l After the setting is successful, the RNC FTP server needs to be restarted to validate the new encryptionmode.

l If the encryption mode of the RNC FTP server is set to forcible encryption, the connection may incura fault when you log in to the RNC FTP server in plaintext mode.

----End

16.5 Querying the Encryption Mode of the RNC FTP ServerThis describes how to query the encryption mode of the RNC FTP server. By performing thistask, you can learn about the active encryption mode of the RNC FTP server.

Prerequisite

The LMT is started.

Procedure

Run the LST FTPSSRV command on the MML client to query the active encryption mode ofthe RNC FTP server.

----End

16.6 Disconnecting the LMT FTP Client from the RNC FTPServer

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.



16-5

NOTE

After the FTP Client is disconnected from the RNC FTP server, you can only browse local files. You cannotperform other system function operations, including deleting local files, browsing or deleting files on theserver, and uploading or downloading files.

----End


LMT User Guide


Issue 03 (2009-04-25)

Documents

huawei LMT guide