SJ-20140527134643-021-ZXUR 9000 GSM (V6.50.202) Status Management Operation Guide

ZXUR 9000 GSM
Base Station Controller
Status Management Operation Guide

Version: V6.50.202
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20140728
The content has been updated (V6.50.202)
Serial Number: SJ-20140527134643-021

Publishing Date: 2014-07-28(R1.0)
SJ-20140527134643-021|2014-07-28(R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Status Management Overview ................................................. 1-1
Chapter 2 Common Status Management Operations ............................. 2-1
2.1 Opening the Status Management Tab .................................................................. 2-1
2.2 Basic Operations................................................................................................ 2-3
2.2.1 Refreshing the Status of a Managed Object ............................................... 2-3
2.2.2 Querying LED Status................................................................................ 2-3
2.2.3 Querying Memory Bank Information........................................................... 2-4
2.2.4 Querying RNC State................................................................................. 2-5
2.2.5 Querying IMSI Local Switch ...................................................................... 2-5
2.2.6 Querying and Synchronizing NTP Time ..................................................... 2-6
2.2.7 Exporting Data to an Excel File ................................................................. 2-7
2.2.8 Saving the Status ..................................................................................... 2-7
Chapter 3 Physical Resources .................................................................. 3-1

3.1 Viewing Information of a Controller Rack.............................................................. 3-1
3.2 Logical CPU....................................................................................................... 3-2
3.2.1 Switching CPU Normally........................................................................... 3-2
3.2.2 Switching CPU Forcibly ........................................................................... 3-2
3.2.3 Resetting CPU Normally ........................................................................... 3-2
3.2.4 Querying CPU Use Rate for Processes in Logical Entities........................... 3-3
3.3 Board ................................................................................................................ 3-3
3.3.1 Switching to a Master/Slave OMM Board ................................................... 3-3
3.3.2 Powering On a Board ............................................................................... 3-4
3.3.3 Powering Off a Board ............................................................................... 3-4
3.3.4 Resetting a Board Normally ...................................................................... 3-4
3.3.5 Resetting a Board Forcibly ........................................................................ 3-5
3.3.6 Performing a Forcible Switchover .............................................................. 3-5
3.3.7 Selecting Board Clock Base...................................................................... 3-6
3.3.8 Sending an APS Request ......................................................................... 3-6
3.3.9 Querying Time ......................................................................................... 3-7
3.3.10 Setting Time........................................................................................... 3-8
3.3.11 Querying CPU Use Rate ......................................................................... 3-8
3.3.12 Querying Process CPU Use Rate ............................................................ 3-8
I
SJ-20140527134643-021|2014-07-28(R1.0)
3.3.13 Querying the CPU Frequency of a Board ................................................. 3-9

3.3.14 Querying Memory Use Rate .................................................................... 3-9
3.3.15 Querying Disk Space ............................................................................ 3-10
3.3.16 Querying PHY CPU Use Rate ............................................................... 3-10
3.3.17 Querying Board GPS Status.................................................................. 3-10
3.3.18 Querying Board Hardware Version..........................................................3-11
3.3.19 Querying Board Running Software Version .............................................3-11
3.3.20 Querying Cell Information According to CMP Module...............................3-11
3.3.21 Querying IMA Using Information ............................................................ 3-12
3.3.22 Querying ATM Optical Using Information................................................ 3-12
3.3.23 Querying Manual Power off Status of All Boards..................................... 3-12
3.3.24 Performing ECMM Operations............................................................... 3-13
3.4 Unit ................................................................................................................. 3-13
3.4.1 Querying Unit State ................................................................................ 3-13
3.4.2 Recovering the Slave of an RUP Unit ...................................................... 3-14
3.4.3 Querying DPI Card Status of an RUP ...................................................... 3-14
3.4.4 Blocking an RUP Unit ............................................................................. 3-14
3.4.5 Unblocking an RUP Unit ......................................................................... 3-15
3.4.6 Querying All Blocked RUP Units.............................................................. 3-15
3.5 Module ............................................................................................................ 3-16
3.5.1 Querying Module State ........................................................................... 3-16
3.5.2 Blocking a DMP Module Manually ........................................................... 3-16
3.5.3 Unblocking a DMP Module Manually ....................................................... 3-16
3.6 E1 Sunit........................................................................................................... 3-17
3.6.1 Querying Subunit State........................................................................... 3-17
3.6.2 Performing Loopback for a Sunit ............................................................. 3-17
3.6.3 Performing Timeslot Loopback of Subunit ................................................ 3-18
3.6.4 Releasing All Loop of a Board ................................................................. 3-19
3.7 T1 Subnit ......................................................................................................... 3-20
3.8 DSP Subunit .................................................................................................... 3-20
3.9 Slave Subunit................................................................................................... 3-20
3.9.1 Manually Blocking a Subunit ................................................................... 3-20
3.9.2 Manually Unblocking a Subunit ............................................................... 3-20
3.9.3 Querying Slave Subunit State ................................................................. 3-21
3.9.4 Querying RUP and Slave Status.............................................................. 3-21
3.9.5 Querying All Blocked Slave Subunits ....................................................... 3-22
Chapter 4 Transmission Resources ......................................................... 4-1

II
SJ-20140527134643-021|2014-07-28(R1.0)
4.1 Association ........................................................................................................ 4-1

4.1.1 Querying SCTP Association Status and Key Information............................. 4-1
4.1.2 Querying SCTP Association Status in Batches ........................................... 4-2
4.1.3 Unblocking an Association ........................................................................ 4-2
4.1.4 Shutting Down an Association ................................................................... 4-2
4.1.5 Aborting an Association ............................................................................ 4-3
4.1.6 Unblocking All Associations (M3UA) .......................................................... 4-3
4.1.7 Shutting Down All Associations (M3UA)..................................................... 4-3
4.1.8 Aborting All Associations (M3UA) .............................................................. 4-4
4.2 M3UA AS .......................................................................................................... 4-4
4.2.1 Querying AS State.................................................................................... 4-4
4.2.2 Querying AS Status in Batches ................................................................. 4-5
4.3 M3UA ASP ........................................................................................................ 4-5
4.3.1 Querying ASP Status................................................................................ 4-5
4.3.2 Querying ASP States in Batches ............................................................... 4-5
4.3.3 Enabling ASP........................................................................................... 4-6
4.3.4 Disabling ASP.......................................................................................... 4-6
4.3.5 Activating ASP ......................................................................................... 4-7
4.3.6 Deactivating ASP ..................................................................................... 4-7
4.4 Signalling Link.................................................................................................... 4-8
4.4.1 Querying MTP3 Link Status (Layer 2) ........................................................ 4-8
4.4.2 Querying MTP3 Link Status (Layer 3) ........................................................ 4-8
4.4.3 Querying the Current Load of MTP3 Link ................................................... 4-9
4.4.4 Inhibiting an MTP3 Link ............................................................................ 4-9
4.4.5 Uninhibiting an MTP3 Link ...................................................................... 4-10
4.4.6 Activating an MTP3 Link ......................................................................... 4-10
4.4.7 Deactivating an MTP3 Link ......................................................................4-11
4.4.8 Activating All MTP3 Links.........................................................................4-11
4.4.9 Deactivating All MTP3 Links.....................................................................4-11
4.4.10 Querying the Link Status in Batches ...................................................... 4-12
4.5 Querying the MTP3 Linkset Status .................................................................... 4-12
4.6 Adjacent No. 7 Office ....................................................................................... 4-13
4.6.1 Querying Status and Key Information of Adjacent No. 7 Office .................. 4-13
4.6.2 Querying Office Status in Batches ........................................................... 4-13
4.6.3 Querying the Status of an SCCP Subsystem............................................ 4-13
4.7 Local SCCP Subsystem.................................................................................... 4-14
4.7.1 Blocking or Unblocking a Local SCCP Subsystem .................................... 4-14
III
SJ-20140527134643-021|2014-07-28(R1.0)
4.7.2 Querying the Status of a Local SCCP Subsystem..................................... 4-14

4.8 Querying MTP2 Link Status .............................................................................. 4-15
4.9 Querying Valid Bandwidth of a Transport Path.................................................... 4-15
4.10 Querying Valid Bandwidth of a Transport Path Group........................................ 4-15
4.11 Querying DHCP Client Configuration Status Query ........................................... 4-16
4.12 RPU Board .................................................................................................... 4-16
4.12.1 Querying Interfaces in RPU................................................................... 4-16
4.12.2 Querying Routes in RPU....................................................................... 4-17
4.12.3 Querying Static ARP............................................................................. 4-18
4.12.4 Querying the ARP List at an Aggregate Port........................................... 4-18
4.12.5 Querying the ARP List at a Super VLAN Port ......................................... 4-19
4.12.6 Querying Channel Group ...................................................................... 4-20
4.12.7 Querying LACP Counters at Group Interface .......................................... 4-20
4.12.8 Querying Channel Group Information..................................................... 4-21
4.12.9 Querying Interfaces Status for Channel Group ....................................... 4-21
4.12.10 Querying BFD DAMP.......................................................................... 4-22
4.12.11 Querying POLICYMAP in RPU ............................................................ 4-22
4.12.12 Querying SUPERVLAN Members ........................................................ 4-22
4.12.13 Querying SUPERVLAN Port IP-PORT Table......................................... 4-23
4.12.14 Querying Relationship Between RUP Interface and 802.3ah Protocol
in RPU ................................................................................................. 4-23
4.12.15 Querying MD Configuration on RPU .................................................... 4-24
4.12.16 Querying MA Configuration on RPU..................................................... 4-24
4.12.17 Querying IPV4 PMTU Items on an RPU ............................................... 4-24
4.12.18 Querying the Switching Type ............................................................... 4-25
4.13 EPU Board..................................................................................................... 4-25
4.13.1 Querying EPU Interface ........................................................................ 4-25
4.13.2 Querying EPU Route ............................................................................ 4-25
4.13.3 Querying ARP Port ............................................................................... 4-25
4.13.4 Querying BFD Sessions Brief Information on EPU .................................. 4-26
4.13.5 Querying BFD Detail Information on EPU............................................... 4-26
4.13.6 Querying Changeover by BFD in EPU ................................................... 4-26
4.13.7 Querying POLICYMAP in EPU .............................................................. 4-27
4.13.8 Querying Relationship Between Interface and 802.3ah Protocol in
EPU ..................................................................................................... 4-27
4.13.9 Querying IPV4 PMTU Items in an EPU .................................................. 4-27
4.13.10 Querying the IPD Session Details in an EPU ........................................ 4-27
4.14 IPv4 ACL Rule ............................................................................................... 4-27
IV
SJ-20140527134643-021|2014-07-28(R1.0)
4.14.1 Querying All ACL4 Tables ..................................................................... 4-27

4.14.2 Querying Specific ACL4 Tables ............................................................. 4-28
4.14.3 Querying ACL4 Group Interface Binding ................................................ 4-29
4.15 MAC ACL Rule............................................................................................... 4-29
4.15.1 Querying All MACL Tables .................................................................... 4-29
4.15.2 Querying Specific MACL Tables ............................................................ 4-29
4.15.3 Querying MACL Group Interface Binding ............................................... 4-30
4.16 802.3ah OAM Configuration ............................................................................ 4-30
4.16.1 Querying Configurations and Status of Ethernet OAM in EPU ................. 4-30
4.16.2 Querying Link Monitoring of Ethernet OAM in EPU ................................. 4-30
4.16.3 Querying Packets of Ethernet OAM in EPU ............................................ 4-31
4.16.4 Querying Configuration of Ethernet OAM in EPU's All Port ...................... 4-31
4.17 PTP Port........................................................................................................ 4-31
4.17.1 Querying Configurations of All PTP Ports ............................................... 4-31
4.17.2 Querying PTP Global Configuration ....................................................... 4-32
4.17.3 Querying State of All PTP Ports............................................................. 4-32
4.17.4 Querying State of Specified PTP Port .................................................... 4-32
4.17.5 Querying PTP Unicast Negotiation......................................................... 4-33
4.17.6 Querying PTP Ebest ............................................................................. 4-33
Chapter 5 GSM Radio Resources ............................................................. 5-1

5.1 PCM at the A Interface ....................................................................................... 5-1
5.1.1 Querying PCM Status at the A Interface..................................................... 5-1
5.1.2 Blocking a PCM Link at the A Interface ...................................................... 5-2
5.1.3 Unblocking a PCM Link at the A Interface .................................................. 5-2
5.1.4 Equipping a PCM Link at the A Interface.................................................... 5-3
5.1.5 Unequipping a PCM Link on the A Interface ............................................... 5-3
5.2 Trunk at the A Interface ...................................................................................... 5-4
5.2.1 Querying the Status of a Trunk at the A Interface........................................ 5-4
5.2.2 Blocking a Trunk at the A Interface ............................................................ 5-4
5.2.3 Unblocking a Trunk at the A Interface ........................................................ 5-5
5.2.4 Starting Trunk Monitoring at the A Interface................................................ 5-5
5.2.5 Stopping Trunk Monitoring at the A Interface .............................................. 5-6
5.3 Resetting a Circuit at the A Interface.................................................................... 5-6
5.4 PCM at the Virtual A Interface ............................................................................. 5-7
5.4.1 Querying PCM Status at the Virtual A Interface .......................................... 5-7
5.4.2 Blocking a PCM Link at the Virtual A Interface............................................ 5-7
5.4.3 Unblocking a PCM Link at the Virtual A Interface ........................................ 5-7
V
SJ-20140527134643-021|2014-07-28(R1.0)
5.4.4 Equipping a PCM Link at the Virtual A Interface.......................................... 5-8

5.5 Trunk at the Virtual A Interface ............................................................................ 5-8
5.5.1 Querying the Status of a Remote Trunk at the A Interface ........................... 5-8
5.5.2 Blocking a Remote Trunk at the A Interface................................................ 5-8
5.5.3 Unblocking a Remote Trunk at the A Interface............................................ 5-8
5.6 PCM at the Ater Interface.................................................................................... 5-8
5.7 Timeslot at the Ater Interface .............................................................................. 5-9
5.7.1 Querying Timeslot Status at the Ater Interface............................................ 5-9
5.7.2 Blocking a Timeslot at the Ater Interface .................................................... 5-9
5.7.3 Unblocking a Timeslot at the Ater Interface ................................................ 5-9
5.8 Resetting an ITC Office..................................................................................... 5-10
5.9 MSC Office ...................................................................................................... 5-10
5.9.1 Querying the Status of an MSC Office ..................................................... 5-10
5.9.2 Enabling an MSC Office.......................................................................... 5-10
5.9.3 Unloading an MSC Office.........................................................................5-11
5.9.4 Disabling an MSC Office ..........................................................................5-11
5.9.5 Resetting an MSC Office .........................................................................5-11
5.9.6 Resetting IPA Resources .........................................................................5-11
5.10 Slave Subunit (GSM) ...................................................................................... 5-12
5.10.1 Querying the Status of IPA Resources ................................................... 5-12
5.10.2 Blocking IPA Resources........................................................................ 5-12
5.10.3 Unblocking IPA Resources .................................................................... 5-12
5.10.4 Querying the Information of Slave Cells ................................................. 5-13
5.10.5 Adjusting the Quantity of Slave Cells ..................................................... 5-13
5.11 NSVC ............................................................................................................ 5-14
5.11.1 Querying the Status of an NSVC............................................................ 5-14
5.11.2 Blocking an NSVC ................................................................................ 5-14
5.11.3 Unblocking an NSVC ............................................................................ 5-14
5.11.4 Resetting an NSVC............................................................................... 5-15
5.12 SGSN Office .................................................................................................. 5-15
5.12.1 Querying the Status of an SGSN ........................................................... 5-15
5.12.2 Enabling an SGSN ............................................................................... 5-15
5.12.3 Disabling an SGSN............................................................................... 5-16
5.12.4 Unloading an SGSN ............................................................................. 5-16
5.13 Querying the Status of the Local End Point ...................................................... 5-16
5.14 NSE .............................................................................................................. 5-17
5.14.1 Querying the Status of an NSE.............................................................. 5-17
VI
SJ-20140527134643-021|2014-07-28(R1.0)
5.14.2 Re-configuring an NSE in Full Mode ...................................................... 5-17

5.14.3 Re-configuring an NSE in Incremental Mode .......................................... 5-17
5.14.4 Querying the Status of an SGSN Dynamic End Node ............................. 5-18
5.15 Cell................................................................................................................ 5-18
5.15.1 Querying the Status of a Cell................................................................. 5-18
5.15.2 Blocking a Cell ..................................................................................... 5-18
5.15.3 Unblocking a Cell ................................................................................. 5-19
5.15.4 Querying the Slave Information of PS Cells ............................................ 5-20
5.15.5 Changing Cells to the Specified Slave ................................................... 5-20
5.15.6 Adjusting Cell Load of Global PCU Resources ....................................... 5-20
5.15.7 Adjusting RUP Slave Load Balance in PLMN ......................................... 5-21
5.15.8 Querying Channel Statistics in a Cell ..................................................... 5-21
5.15.9 Querying the Channel Information in a Cell ............................................ 5-21
5.15.10 Querying the Power of All BCCHs in a Cell........................................... 5-22
5.15.11 Querying the Relationship Between TRX and RRU ............................... 5-22
5.15.12 Querying Uplink Interference Band in Real Time................................... 5-22
5.15.13 Querying the BA List ........................................................................... 5-23
5.15.14 Querying Dynamic TRXs..................................................................... 5-23
5.15.15 Querying the IFTA Information in a Cell ................................................ 5-23
5.15.16 Querying IFTA Historical Interference................................................... 5-24
5.16 Frequency...................................................................................................... 5-24
5.16.1 Querying the Status of a TRX................................................................ 5-24
5.16.2 Blocking an FU TRX ............................................................................. 5-24
5.16.3 Unblocking an FU TRX ......................................................................... 5-25
5.16.4 Blocking a CU TRX............................................................................... 5-25
5.16.5 Unblocking a CU TRX........................................................................... 5-26
5.16.6 Querying the Relationship Between TRX and RRU................................. 5-26
5.16.7 Querying Uplink Interference Band in Real Time..................................... 5-27
5.17 Timeslot......................................................................................................... 5-27
5.17.1 Querying the Status of a Timeslot .......................................................... 5-27
5.17.2 Querying the Statuses of All Radio Channels ......................................... 5-27
5.17.3 Blocking a Timeslot .............................................................................. 5-28
5.17.4 Unblocking a Timeslot........................................................................... 5-28
5.17.5 Performing a Forcible Handover ............................................................ 5-28
5.17.6 Querying Connection Status by Timeslot................................................ 5-29
5.17.7 Querying Connection Status by IMSI ..................................................... 5-29
5.17.8 Querying Connection Status by IMEI ..................................................... 5-30
VII
SJ-20140527134643-021|2014-07-28(R1.0)
5.17.9 Monitoring the Status of a Channel ........................................................ 5-30

5.17.10 Stopping the Channel Monitoring ......................................................... 5-30
5.18 GSM Module.................................................................................................. 5-31
5.18.1 Querying Channel Statistics in a Module ................................................ 5-31
5.18.2 Stopping Flow Control .......................................................................... 5-31
5.18.3 Querying the Information of IFTA External Cells ..................................... 5-31
5.19 BVC .............................................................................................................. 5-32
5.19.1 Querying the Status of a BVC................................................................ 5-32
5.19.2 Blocking a BVC .................................................................................... 5-32
5.19.3 Unblocking a BVC ................................................................................ 5-32
5.19.4 Resetting a BVC................................................................................... 5-33
5.19.5 Performing Signaling Reset for BVCs .................................................... 5-33
5.20 ABIS.............................................................................................................. 5-33
5.20.1 Querying Timeslot Status at the Abis Interface ....................................... 5-33
5.20.2 Blocking a Timeslot at the Abis Interface ................................................ 5-34
5.20.3 Unblocking a Timeslot at the Abis Interface ............................................ 5-34
5.20.4 Starting Timeslot Monitoring at the Abis Interface ................................... 5-34
5.20.5 Stopping Timeslot Monitoring at the Abis Interface.................................. 5-35
5.21 Querying Timeslot Usage at the Abis Interface ................................................. 5-35
5.22 Querying Device Status at the Abis Interface.................................................... 5-35
5.23 Site................................................................................................................ 5-36
5.23.1 Querying the Relationships Between RRUs and TRXs............................ 5-36
5.23.2 Resetting a Site.................................................................................... 5-36
5.23.3 Querying E1 PPP Transmission Status .................................................. 5-37
5.23.4 Querying the Association Status of a Site............................................... 5-37
5.23.5 Querying Transmission Performance of PPP Links ................................. 5-37
5.24 Resetting a Rack ............................................................................................ 5-38
5.25 Querying Ring Network Status ........................................................................ 5-38
Figures............................................................................................................. I
Glossary ........................................................................................................ III
VIII
SJ-20140527134643-021|2014-07-28(R1.0)
About This Manual

Purpose
The ZXUR 9000 GSM is a base station controller of ZTE 2G multi-mode series. It
supports access control, security mode control, mobility management, and radio resource
management and control.
The ZXUR 9000 GSM provides various functions specified in 3GPP R4, R5, R6, and R7
protocols and a series of standard interfaces (such as A, Abis, and Gb) and supports
interconnection among CN, BSC, and BTS provided by different vendors. Based on the
unified all-IP hardware platform of ZTE and the distributed design principle, the ZXUR
9000 GSM is developed to achieve the separation of control plane and user plane and the
separation of interface and application. The ZXUR 9000 GSM supports TDM/IP protocol
stacks and smooth evolution to all-IP GERAN.
This manual provides instructions for status management operations of the ZXUR 9000
GSM.
Intended Audience
This manual is intended for telecommunication engineers.
What Is in This Manual

This manual contains the following chapters.
Chapter 1, Status Management
Provides an overview of status management.
Overview
Chapter 2, Common Status
Describes the GUI for status management and common
Management Operations
status management operations.
Chapter 3, Physical Resources
Describes the status management operations on physical

resources of the ZXUR 9000 GSM.
Chapter 4, Transmission Resources
Describes the status management operations on

transmission resources of the ZXUR 9000 GSM.
Chapter 5, GSM Radio Resources
Describes the status management operations on the GSM

radio resources of the ZXUR 9000 GSM.
Conventions
This manual uses the following conventions.
Bold
Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
I
SJ-20140527134643-021|2014-07-28(R1.0)
Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in
moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
II
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 1
Status Management
Overview
The status management is a function of the operation and maintenance subsystem.
The management function facilitates the up-level service debugging, on-site installation
and debugging and the fault analysis. Through status management, maintenance and
technical personnel can quickly locate faults.
The status management manages the dynamic data in the system, including the functions
of queries, monitoring and operations.
l
l
l
Queries on dynamic data: are implemented in man-machine interactive mode to

obtain status data.
Monitoring on dynamic data: displays the real time changes on dynamic data.
Operations on dynamic data: are implemented in man-machine interactive mode to
perform the following actions: block/unblock, reset/forcible reset, enable/disable and
stop/start.
Status management is a multi-aspect and multi-module function that involves database

operations, MO operations on NEs, communication between NEs and BSCs, and
operations on BSCs. The following needs to be noted in the status management.
l
Status management manages the terrestrial and radio resources with status
properties. The resources without status properties are not shown in the status
management interface.
Status management modifies the status of terrestrial and radio resources with status
properties on a BSC. The operation must be initiated on a BSC. The communication
between the BSC and NEs must operate properly.
The operation of status management may affect the status of terrestrial and radio
resources and thus affect the conversation quality. Be careful when performing the
management operations.
The BSC environment has a great influence on status management. Any error during
the BSC operations may cause failure during status management operations.
1-1
SJ-20140527134643-021|2014-07-28(R1.0)
ZXUR 9000 GSM Status Management Operation Guide
This page intentionally left blank.
1-2
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 2
Common Status Management

Operations
Table of Contents
Opening the Status Management Tab.........................................................................2-1
Basic Operations ........................................................................................................2-3
2.1 Opening the Status Management Tab

This procedure describes how to open the Status Management tab on the EMS client.
Prerequisite
l
l
You have logged in to the EMS client.

The EMS client is successfully connected to the managed network element.
Steps
1. In the client window, select View > Status Management from the menu bar. The
Status Management tab is displayed.
2. Select Root Node > GERAN Subnetwork > Managed Network Element. The
Configuration Resource Tree is expanded, see Figure 2-1.
2-1
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 2-1 Expanding the Configuration Resource Tree
3. Double-click an object in the navigation tree. The corresponding management tab is

displayed. For example, double-click Controller Rack. The Controller Rack tab is
displayed, see Figure 2-2.
Figure 2-2 Controller Rack Tab
4. Select a record and perform an appropriate operation on the corresponding object as

required.
End of Steps
2-2
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 2 Common Status Management Operations
2.2 Basic Operations

2.2.1 Refreshing the Status of a Managed Object
This procedure describes how to obtain the latest configuration data of a managed object
and refresh the information displayed on the status management interface correspondingly.
Steps
1. Select Root Node > GERAN Subnetwork > Managed Network Element and
double-click a managed object node in the expanded navigation tree.
2. Select a data record.
.
3. On the tool bar of the managed object tab, click

End of Steps
2.2.2 Querying LED Status

For the resources that are not operating properly, you can query the LED status to locate
the fault.
Prerequisite
The EMS is operating properly.
The network element is connected to the EMS properly.
Steps
1. On the toolbar, click
. The LED status query dialog box is displayed.
2. Select the query type (

target rack/shelf, see Figure 2-3.
or
), and the
2-3
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 2-3 LED Status Query Dialog Box
3. Click OK. The Batch Operation Result is displayed.

4. Click OK.
5. In RACK tab, move the mouse to a board, the LED status of this board will be
displayed.
End of Steps
2.2.3 Querying Memory Bank Information

For the resources that are not operating properly, you can query memory band information
to locate the fault.
Prerequisite
Steps
. The Memory Information Query dialog box is displayed.
2. Select the query type (

or
), see Figure 2-4.
2-4
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 2-4 Memory Information Query Dialog Box
3. Click OK.
End of Steps
2.2.4 Querying RNC State

This procedure describes how to query the ID and state of an RNC office.
Steps
1. On the tool bar of managed object tab, click
displayed, see Figure 2-5
. A confirmation dialog box is
2. Click Yes.
Figure 2-5 Querying RNC state
End of Steps
2.2.5 Querying IMSI Local Switch

This procedure describes how to query the local switch occupied by services
corresponding to an IMSI.
Steps
box is displayed, see Figure 2-6.
. The IMSI Local Switch Query dialog
2. Input a 15-bit IMSI number.

2-5
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 2-6 Querying IMSI Local Switch
3. Click OK.
End of Steps
2.2.6 Querying and Synchronizing NTP Time

For the resources that are not operating properly, you can extract or synchronize the NTP
clock on a board to locate the fault.
Prerequisite
Steps
. The NTP time operation dialog box is displayed.
2. Select an option, see Figure 2-7.

Figure 2-7 NTP Time Operation Dialog Box
a. Select
displayed.
, and click OK. The Operation result dialog box is
b. Select
is displayed.
, and click OK. The Operation result dialog box
End of Steps
2-6
SJ-20140527134643-021|2014-07-28(R1.0)
2.2.7 Exporting Data to an Excel File

This procedure describes how to export the required data to an excel file.
Steps
1. Expand the root node, and double-click a managed object node.
2. Select a data record.
4. Select a path to save the file, and click OK.

End of Steps
2.2.8 Saving the Status

This procedure describes how to save the board service status of the current user on the
OMP.
Steps
1. On the toolbar of a management object, click
2. Enter a verification code, and click OK.
Note:
A message is displayed when you close the Status Management tab, prompting you
whether to save the status.
End of Steps
2-7
SJ-20140527134643-021|2014-07-28(R1.0)
2-8
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 3
Physical Resources
Table of Contents
Viewing Information of a Controller Rack ....................................................................3-1
Logical CPU ...............................................................................................................3-2
Board .........................................................................................................................3-3
Unit ..........................................................................................................................3-13
Module .....................................................................................................................3-16
E1 Sunit ...................................................................................................................3-17
T1 Subnit..................................................................................................................3-20
DSP Subunit ............................................................................................................3-20
Slave Subunit ...........................................................................................................3-20
3.1 Viewing Information of a Controller Rack

This procedure describes how to view the information of a rack through a graph.
Steps
1. Select Root Node > GERAN Subnetwork > Managed NE > Physical Resource >
Controller Rack. The Controller Rack tab is displayed, see Figure 3-1.
Figure 3-1 Controller Rack Tab
2. Double-click the rack record. The RACK tab is displayed.

3. View the information displayed on the tab.
End of Steps
3-1
SJ-20140527134643-021|2014-07-28(R1.0)
3.2 Logical CPU

3.2.1 Switching CPU Normally
This procedure describes how to switch logical CPUs. It may affect the services. Take this
procedure only during system maintenance.
Context
The network management system sends the normal switching command to CPU.
Steps
Logical CPU. The Logical CPU tab is displayed.
2. Select one or more records.
3. Right-click the selected records and select Normal switch.
4. Click OK.
End of Steps
3.2.2 Switching CPU Forcibly

This procedure describes how to forcibly switch logical CPUs. It may affect the services.
Take this procedure only during system maintenance.
Steps
3. Right-click the selected records and select Forcible switch.
4. Click OK.
End of Steps
3.2.3 Resetting CPU Normally

This procedure describes how to reset a CPU. A normal resetting means that a logical
CPU or physical CPU is reset based on ucLCpuNo. It is used for system maintenance and
may affect the services.
Steps
3-2
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 3 Physical Resources

3. Right-click the selected records and select Normal Reset from the shortcut menu.
4. Enter the verification code.
5. Click OK.
End of Steps
3.2.4 Querying CPU Use Rate for Processes in Logical Entities

This procedure describe how to query the CPU usage of each process in a specified logical
entity. If there is a CPU overload alarm, you can take this procedure to check the CPU
usage.
Steps
3. Right-click the selected records and select the command to execute the CPU use rate
query for processes in logical entities.
End of Steps
3.3 Board
3.3.1 Switching to a Master/Slave OMM Board
This procedure describes how to switch the OMM. OMM active/standby switchover refers
to switching the active OMM board to be standby and the standby OMM board to be active.
Take this procedure when required or the OMM board is faulty.
This function is just supported by OMM boards.
Steps
Board. The Board tab is displayed.
2. Select a record.
3. Right-click the selected record and select OMM backup exchange from the shortcut
menu.
End of Steps
3-3
SJ-20140527134643-021|2014-07-28(R1.0)
3.3.2 Powering On a Board

This procedure describes how to manually power on a non-OMP board. It is used during
site deployment or system maintenance. Perform the operation only when absolutely
required.
Steps
2. Select a record.
3. Right-click the selected record and select Board power on from the shortcut menu.
4. Click OK.
End of Steps
3.3.3 Powering Off a Board

This procedure describes how to manually power off a non-OMP board. It is used during
site deployment or system maintenance. Perform the operation only when absolutely
required.
Warning! .
EGBS, EGFS, and OMP cannot be manually powered off. If EGBS/EGFS is powered off,
the communication of the entire system fails.
Steps
3. Right-click the selected records and select Board power off from the shortcut menu.
5. Click OK.
End of Steps
3.3.4 Resetting a Board Normally

This procedure describes how to normally reset a board that supports logical CPU and
physical CPU.
3-4
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select Normal Reset of board.
5. Click OK.
End of Steps
3.3.5 Resetting a Board Forcibly

This procedure describes how to forcibly stop the services on a board and reset the board.
Caution!
The forcible resetting operation may interrupt the board services.
Steps
3. Right-click the selected records and select Forcible reset of board.
5. Click OK.
End of Steps
3.3.6 Performing a Forcible Switchover

The forcible switchover function is applicable to only logical CPUs of a board. This function
is used during system maintenance. Do not use this function in other scenarios because
services may be affected by this function.
This procedure describes how to perform a forcible switchover of a board.
Steps
2. Select a record.
3-5
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the desired board and select Forcible Switch from the shortcut menu. A
dialog box is displayed.
4. Click OK.
End of Steps
3.3.7 Selecting Board Clock Base

This procedure describes how to select the clock base. It is used for system maintenance.
The operation may affect the services.
Steps
2. Select a record.
3. Right-click the selected record and select Select clock base from the shortcut menu.
A message is displayed, prompting you to enter a verification code.
4. Enter the verification code and click OK. The Select clock base dialog box is
Figure 3-2 Selecting a Clock Base
5. Select a clock base and click OK.

End of Steps
3.3.8 Sending an APS Request

This procedure describes how to send an APS request to a board. This operation can be
performed only during maintenance. APS in the other scenarios can influence services.
3-6
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record (board).
3. Right-click the selected record and select APS Exchange Request from the shortcut
menu. A message is displayed, prompting you to enter the verification code.
4. Enter the verification code and click OK. The APS Exchange Request dialog box is
Figure 3-3 APS Exchange Request Dialog Box
5. Select an APS request, enter a protection group number, and then click OK.
End of Steps
3.3.9 Querying Time

This procedure describes how to query the board time (with the time zone and DST
information), for example, 15.03.14 10:30:30.
l
l
l
After SNTP synchronization, you can take this procedure to check whether the
synchronization is successful.
After setting the NE time, you can take this procedure to check whether the setting is
successful.
This procedure can be used to verify that the board time is correct.
Steps
2. Select a record.
3. Right-click the selected record and select Time Query.
4. View the result.
End of Steps
3-7
SJ-20140527134643-021|2014-07-28(R1.0)
3.3.10 Setting Time

This procedure describes how to set the NE time (with the time zone and DST information).
Take this procedure with care if the system is operating properly. It is used in the following
scenarios:
l
l
Set the system time during commissioning.

Modify the incorrect system time.
After the system time is modified, all functions related to time are affected.
For example, the alarms and performance statistics are subjected to the new
system time. If there is a large difference of time before and after synchronization,
performance statistics accuracy may be affected.
Steps
2. Select a record.
3. Right-click the selected record and select Time Set, the Time Set dialog box is
displayed.
4. Set the time of server and click the OK.
End of Steps
3.3.11 Querying CPU Use Rate

This procedure describes how to query the CPU usage of a board. CPU usage is calculated
on a board basis, regardless of whether the CPU has one core or multiple cores.)
If there is a CPU overload alarm, you can take this procedure to check the CPU usage.
Steps
2. Select a record.
3. Right-click the selected record and select CPU userate query.
4. View the result.
End of Steps
3.3.12 Querying Process CPU Use Rate

This procedure describes how to query the CPU usage of all the processes of the board
within 2 seconds and 10 seconds.
3-8
SJ-20140527134643-021|2014-07-28(R1.0)
CPU usage of a process equals the total operation period / statistical period. The total
operation period means the sum of the operation period on each core.
For example, for a CPU with two cores, a process operates on core 1 for one second and
on core 2 for 1.5 seconds, the total operation period is 2.5 seconds. Within two seconds,
the CPU usage of the process is 125%.
If there is a CPU overload alarm, you can take this procedure to locate the process that
causes the high usage.
Steps
2. Select a record.
3. Right-click the selected record and select Process CPU userate query.
4. View the result.
End of Steps
3.3.13 Querying the CPU Frequency of a Board

This procedure describes how to query the CPU frequency of a board.
Steps
3. Right-click the selected records and select CPU Frequency Query from the shortcut
menu. A dialog box is displayed, indicating the query result.
End of Steps
3.3.14 Querying Memory Use Rate

This procedure describes how to query the memory usage of a board and memory usage
of each process.
If multiple processes share the memory, the memory usage of all processes are summed
and the result may be greater than the memory size.
If there is a memory insufficiency alarm, you can take this procedure to check the memory
usage.
Steps
3-9
SJ-20140527134643-021|2014-07-28(R1.0)
2. Select a record.
3. Right-click the selected record and select Memory userate query.
4. View the result.
End of Steps
3.3.15 Querying Disk Space

This procedure describes how to query the name and status of the hard disk or flash disk
on a board.
If there is a disk space insufficiency alarm, you can take this procedure to verify the storage
device status (including name, capacity, and free space) of the specified board.
Steps
2. Select a record.
3. Right-click the selected record and select Disk query.
4. View the result.
End of Steps
3.3.16 Querying PHY CPU Use Rate

This procedure describes how to check the CPU usage of each core of a specified board.
If there is a CPU overload alarm, you can take this procedure to check the CPU usage.
Steps
2. Select a record.
3. Right-click the selected record and select PHY CPU userate query.
4. View the result.
End of Steps
3.3.17 Querying Board GPS Status

This procedure describes how to query the statuses of the GPS subcard and clock. For V4
RNCs, the GPS subcard is located on the EGFS board. For V3 RNCs, the GPS subcard
is located on the ICM board.
If A-GPS positioning is slow or incorrect on UEs, you can take this procedure to check the
operation of the RNC GPS subcard and antenna.
3-10
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select GPS Status Query.
4. View the result.
End of Steps
3.3.18 Querying Board Hardware Version

This procedure describes how to query the hardware version of a specified board. After a
board is added, you can take this procedure to check the hardware version.
Steps
2. Select a record.
3. Right-click the selected record and select Board Hardware Version Query.
4. View the result.
End of Steps
3.3.19 Querying Board Running Software Version

This procedure describes how to query the current version (including CPU, FPGA, and
DSP versions) of a board.
Users can query the software version running on the board, software size, and the software
installing time.
Steps
2. Select a record.
3. Right-click the selected record and select Board running version query.
End of Steps
3.3.20 Querying Cell Information According to CMP Module

This procedure describes how to query the cell information of the CMP module, including
the cell user IDs,, cell numbers, and module numbers.
3-11
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select Query cell information according to CMP
module.
End of Steps
3.3.21 Querying IMA Using Information

This procedure describes how to query the link status and usage of the IMA port.
Steps
2. Select a record.
3. Right-click the selected record and select Query IMA using information.
End of Steps
3.3.22 Querying ATM Optical Using Information

This procedure describes how to query the usage and status of the ATM optical port.
Steps
2. Select a record.
3. Right-click the selected record and select Query ATM optical using information.
End of Steps
3.3.23 Querying Manual Power off Status of All Boards

This procedure describes how to check the manual power status of a board, including
whether the CPU of each board is started and the power status of each CPU.
Steps
2. Select a record.
3-12
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select All Board Manual Power off Status Query
from the shortcut menu. The All Board Manual Power off Status Query dialog box
is displayed.
4. (Optional) Click the Export to excel button. The query result is exported to an excel
file.
End of Steps
3.3.24 Performing ECMM Operations

The resetting, switchover, status query of the system or boards may affect the service
operation. Perform these operations during site deployment and system maintenance.
Prerequisite
This function is just supported by EGBS boards.
Steps
2. Select a record.
3. Right-click the selected record and perform an appropriate operation as required:
If
Then
SelectECMM Operation > ECMM Status Query
Query ECMM Status.
SelectECMM Operation > Reset ECMM
Reset ECMM.
SelectECMM Operation > Switch ECMM
Switch ECMM.
SelectECMM Operation > ECMM Running
Query ECMM Running Version.
Version Query
End of Steps
3.4 Unit
3.4.1 Querying Unit State
This procedure describes how to query the physical position and operational status of a
logical unit of a specified module. It can be used to confirm the operational status of units
during routine and preventive maintenance.
Steps
Unit. The Unit tab is displayed.
3-13
SJ-20140527134643-021|2014-07-28(R1.0)
2. Select a record.
3. Right-click the selected record and select Unit state query from the shortcut menu.
4. View the result that is displayed in the Unit state column.
End of Steps
3.4.2 Recovering the Slave of an RUP Unit

This procedure describes how to recover and comeback the slave of a specified RUP unit.
It is used uring system maintenance or troubleshooting of the slave of an RUP unit.
Steps
2. Select a record.
3. Right-click the selected record and select Slave recover/comeback of RUP unit.
4. View the result displayed in the Comeback result column.
End of Steps
3.4.3 Querying DPI Card Status of an RUP

This procedure describes how to query the DPI card status with the specified logical
address. It applies to UCIU RUP logical addresses. The query result includes card ID,
slot information, in position or not, PCB ID of LDCC, and version numbers of BOMID and
LDCC EPLD.
Steps
2. Select a record.
3. Right-click the selected record and select DPI card status query of RUP.
4. View the result.
End of Steps
3.4.4 Blocking an RUP Unit

This procedure describes how to manually block a specified logical unit.
Before maintaining a unit, you need to block the unit, and the system transfers the service
from this unit to other units, so that services are not affected during maintenance. It may
increase the loads of other units, affecting the service quality.
3-14
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select RUP unit block.
End of Steps
3.4.5 Unblocking an RUP Unit

This procedure describes how to manually unblock a specified logical unit. After unit
maintenance, you need to unblock the unit so that the unit can operate properly.
Prerequisite
The RUP unit is blocked.
Steps
2. Select a record.
3. Right-click the selected record and select RUP unit unblock.
End of Steps
3.4.6 Querying All Blocked RUP Units

This procedure describes how to query the number of all the manually blocked units and
the unit numbers. A maximum of 300 blocked units can be displayed.
After blocking a unit, you can take this procedure to confirm that the unit is successfully
blocked.
Prerequisite
The selected units are blocked.
Steps
Unit. The Unit tab page is displayed.
2. Select a record.
3. Right-click the selected record and select Query all block RUP unit.
End of Steps
3-15
SJ-20140527134643-021|2014-07-28(R1.0)
3.5 Module
3.5.1 Querying Module State
logical module in the NE. It can be used to confirm the operational status of modules during
routine and preventive maintenance.
Steps
Module. The Module tab is displayed.
2. Select a record.
3. Right-click the selected record and select Module state query from the shortcut menu.
4. View the result displayed in Module state and Module query result columns.
End of Steps
3.5.2 Blocking a DMP Module Manually

This procedure describes how to manually block a DMP module. The DMP module
becomes unavailable after being blocked.
If a DMP module needs to be maintained, this module can be blocked. The system
transfers the services on this module to the other modules to prevent the module
maintenance from affecting the ongoing services. However, blocking a DMP module
increases the load on the other modules and may result in a degrade of service quality.
Steps
2. Select a record.
3. Right-click the selected record and select Manual block DMP module from the
shortcut menu.
End of Steps
3.5.3 Unblocking a DMP Module Manually

This procedure describes how to manually unblock a DMP module. The DMP module
becomes available after being unblocked. After the maintenance of a DMP module is
completed, the DMP module can be unblocked to resume operation.
3-16
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select Manual unblock DMP module from the
shortcut menu.
End of Steps
3.6 E1 Sunit
3.6.1 Querying Subunit State
logical subunit of a specified unit. It can be used to confirm the operational status of units
Steps
E1 Sunit. The E1 Sunit tab is displayed.
2. Select a record.
3. Right-click the selected record and select Sunit state query from the shortcut menu.
4. View the result in Sunit state query column.
End of Steps
3.6.2 Performing Loopback for a Sunit

For subunits that use the TDM for data switching, this procedure can set internal loopback
or external loopback for one or all the time slots, or release loopback for a time slot.
l
l
l
The operation applies to fault diagnosis only. Do not take this procedure when the
system operates properly. For example, if this command is used for a signaling link
on a trunk, the signaling link becomes abnormal.
It is normal that the EMS reports an alarm indicating the stop of connection check
within two minutes after this command is executed. The alarm will be automatically
cleared after all the loopback settings are cancelled.
Loopback can be set for the subunits of the following physical resources: E1/T1, DSP,
DSP_2, ASIC, IWF, and the subunits must use TDM for data switching.
Internal loopback is used to troubleshoot internal faults of a board. External loopback
refers to loopback to the transmission side or the back panel for troubleshooting
external faults.
This operation is applicable to troubleshooting of transmission faults and board faults.
3-17
SJ-20140527134643-021|2014-07-28(R1.0)
For example, oif the new signaling link fails to be established, which may be caused by
improper HDLC processing, you can perform external loopback on the trunk timeslot
of the bearing link and check whether the link changes to normal status. If the link is in
normal status, it indicates that the HDLC processing is proper. You can also perform
internal loopback on the trunk timeslot of the bearing link and check whether the link
changes to normal status at the remote equipment. If the link is in normal status, it
indicates that the transmission link is normal. The loopback of the subunits that bear
services will cause service interruption.
Steps
E1 Sunit. The E1 Sunit tab page is displayed.
2. Select a record.
3. Right-click the selected record and select Sunit loop. The Sunit loop dialog box is
displayed.
Figure 3-4 Sunit Loop
4. Select the timeslot No. of loop. Click OK. The result is displayed in the Loop result
column.
End of Steps
3.6.3 Performing Timeslot Loopback of Subunit

For subunits that use the TDM for data switching, this procedure can set internal loopback
or external loopback for one or all the timeslots, or release loopback for a timeslot.
l
The operation applies to fault diagnosis only. Do not take this procedure when the
system operates properly. For example, if this procedure is used for a signaling link
on a trunk, the signaling link becomes abnormal.
It is normal that the EMS reports an alarm indicating the stop of connection check
within two minutes after this command is executed. The alarm will be automatically
cleared after all the loopback settings are cancelled.
Loopback can be set for the subunits of the following physical resources: E1/T1, DSP,
DSP_2, ASIC, IWF, and the subunits must use TDM for data switching.
3-18
SJ-20140527134643-021|2014-07-28(R1.0)
Internal loopback is used to troubleshoot internal faults of a board. External loopback

refers to loopback to the transmission side or the back panel for troubleshooting
external faults.
This operation is applicable to troubleshooting of transmission faults and board faults.
For example, if the new signaling link fails to be established, which may be caused by
improper HDLC processing, you can perform external loopback on the trunk timeslot
of the bearing link and check whether the link changes to normal status. If the link
is in normal status, it indicates that the HDLC processing is proper. You can also
perform internal loopback on the trunk timeslot of the bearing link and check whether
the link changes to normal status at the remote equipment. If the link is in normal
status, it indicates that the transmission link is normal. The subunit loopback for the
carrier service will cause service interruption. The loopback on the subunits that bear
services will cause service interruption.
Steps
2. Select a record.
3. Right-click the selected record and select Timeslot of sunit loop. The Timeslot of
sunit loop dialog box is displayed.
Figure 3-5 Timeslot of sunit loop
4. Select the Timeslot No. of loop and Loop operate type.

5. Click OK. The query result is displayed in the Loop result column.
End of Steps
3.6.4 Releasing All Loop of a Board

This procedure describes how to release all loops that are set for a specified subunit or
subunit time slot from a board. If the loops are not specific to a subunit or subunit timeslot,
the operation is invalid.
3-19
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select Release all loop.
4. View the result in the Loop result column.
End of Steps
3.7 T1 Subnit
For the operations on the logical T1 subunit, refer to the operations on the E1 subunit.
3.8 DSP Subunit

For the operations on the DSP subunit, refer to the operations on the E1 subunit.
3.9 Slave Subunit

3.9.1 Manually Blocking a Subunit
This procedure describes how to manually block a subunit of a specified unit. Before
maintaining a subunit, you must block the subunit, and the system transfers the service
from this subunit to other subunits, so that services are not affected during maintenance.
It may increase the loads of other units, affecting the service quality.
Steps
Slave Sunit. The Slave Sunit tab is displayed.
2. Select a record.
3. Right-click the selected record and select Manual block sunit from the shortcut menu.
4. View the result in the Sunit manual block/unblock result column.
End of Steps
3.9.2 Manually Unblocking a Subunit

This procedure describes how to manually unblocks a subunit of a specified unit. After unit
maintenance, you need to unblock the unit so that the unit can operate properly.
3-20
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select Manual unblock sunit.
4. View the result in the Sunit manual block/unblock result column.
End of Steps
3.9.3 Querying Slave Subunit State

logical subunit of a specified unit. It can be used to confirm the operational status of units
Steps
2. Select a record.
3. Right-click the selected record and select Sunit state query.
4. View the result in the Sunit State column.
End of Steps
3.9.4 Querying RUP and Slave Status

This procedure describes how to query the states of RUP and the slave subunits. In this
manual version, the SLAVE subunit state is the DSP state. Take this procedure during
system maintenance or when the RUP or SLAVE unit is doubted to be faulty.
Steps
2. Select a record.
3. Right-click the selected record and select RUP and Slave status query.
4. View the result in the pop-up interface.
End of Steps
3-21
SJ-20140527134643-021|2014-07-28(R1.0)
3.9.5 Querying All Blocked Slave Subunits

This procedure describes how to query the information of all manually blocked subunits,
including the number of blocked subunits, the ID of each subunit, and the unit to which
each subunit belongs.
A maximum of 300 blocked subunits can be displayed by the system. After a blocking
operation is performed on a subunit, you can use this function to check whether these
subunits are successfully blocked.
Steps
SLAVE Sunit. The SLAVE Sunit tab is displayed.
3. Right-click the selected records and select All Block SLAVE Sunit Query from the
shortcut menu.
End of Steps
3-22
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 4
Transmission Resources
Table of Contents
Association.................................................................................................................4-1
M3UA AS ...................................................................................................................4-4
M3UA ASP.................................................................................................................4-5
Signalling Link ............................................................................................................4-8
Querying the MTP3 Linkset Status ...........................................................................4-12
Adjacent No. 7 Office ...............................................................................................4-13
Local SCCP Subsystem ...........................................................................................4-14
Querying MTP2 Link Status......................................................................................4-15
Querying Valid Bandwidth of a Transport Path..........................................................4-15
Querying Valid Bandwidth of a Transport Path Group ...............................................4-15
Querying DHCP Client Configuration Status Query ..................................................4-16
RPU Board...............................................................................................................4-16
EPU Board ...............................................................................................................4-25
IPv4 ACL Rule..........................................................................................................4-27
MAC ACL Rule.........................................................................................................4-29
802.3ah OAM Configuration .....................................................................................4-30
PTP Port ..................................................................................................................4-31
4.1 Association
4.1.1 Querying SCTP Association Status and Key Information
This procedure describes how to query SCTP associations status and key information.
The query can be based on:
l
Association number: queries the status and attribute of a single association in the NE
based on the global association number and module number.
For static association query, the global association number is the configured
association number.
IP address and port number: queries the status and attribute of a specified association
based on the IP addresses and port numbers of the local and peer ends.
This operation can check whether a specified association is established.
4-1
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
1. Select Root Node > GERAN Subnetwork > Managed NE > Transmission Resource
> Sctp Association. The Sctp Association tab is displayed.
3. Right-click the selected records and select the command to execute the SCTP
association status and key information query.
End of Steps
4.1.2 Querying SCTP Association Status in Batches

This procedure describes how to query the status of all the SCTP associations. The
operation result shows the number of associations and association status.
Only static association query is supported.
This operation can query the associations that are established for the NE.
Steps
3. Right-click the selected records and select the command to execute the SCTP
association status query in batch.
End of Steps
4.1.3 Unblocking an Association

This procedure describes how to unblock a specified association based on association ID.
The operation result shows the operation result, and protocol type and property of the
association. Take this procedure only when an association needs to be established.
Steps
3. Right-click the selected records and select Establish.
End of Steps
4.1.4 Shutting Down an Association

This procedure describes how to shut down a specified association based on association
ID. The operation result shows the protocol type and property of the association.
4-2
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 4 Transmission Resources
Perform this operation only when absolutely required. The operation may cause service
interruption on the association.
Steps
3. Right-click the selected records and select Shutdown.
End of Steps
4.1.5 Aborting an Association

This procedure describes how to abort a specified association based on association ID.
The operation result shows the protocol type and property of the association.
Perform this operation only when absolutely required.
interruption on the association.
The operation cause service
Steps
3. Right-click the selected records and select Abort.
End of Steps
4.1.6 Unblocking All Associations (M3UA)

This procedure describes how to unblock all associations of a specified protocol type. It
is usually used for testing or establishing associations of a protocol type. Perform this
operation only when absolutely required. .
Steps
3. Right-click the selected records and select Establish all (M3UA).
End of Steps
4.1.7 Shutting Down All Associations (M3UA)

This procedure describes how to shutting down all the associations of a specified protocol
type,
4-3
SJ-20140527134643-021|2014-07-28(R1.0)
This operation is used for testing or shutting down associations of a protocol type. Perform
this operation only when absolutely required.
The shutdown operation may cause the failure of services of a specified protocol.
Steps
3. Right-click the selected records and select Shutting down all (M3UA).
End of Steps
4.1.8 Aborting All Associations (M3UA)

This procedure describes how to aborting all the associations of a specified protocol type,
This operation is used for testing or shutting down associations of a protocol type. Perform
this operation only when absolutely required.
The shutdown operation may cause the failure of services of a specified protocol.
Steps
3. Right-click the selected records and select Abort all(M3UA).
End of Steps
4.2 M3UA AS
4.2.1 Querying AS State
This procedure describes how to query the status, protocol type, number of ASPs, and
ASP status of a specified AS.
If you are uncertain about the status of an AS or need to query the protocol and ASP
information of the AS, you can take this procedure.
Steps
> M3UA AS. The M3UA AS tab page is displayed.
4-4
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select AS state request. The result is displayed
in the Query result column.
End of Steps
4.2.2 Querying AS Status in Batches

This procedure describes how to query the status of all the configured ASs. Take this
procedure when the status of all the configured ASs needs to be verified.
For example, if there is an AS status change notification, you can take this procedure to
check the status of all the ASs.
Steps
> M3UA AS. The M3UA AS tab page is displayed.
3. Right-click the selected records and select Batch AS status query. The result is
displayed in the Query result column.
End of Steps
4.3 M3UA ASP

4.3.1 Querying ASP Status
This procedure describes how to query the protocol type, association, and status of an
ASP on a specified AS. An ASP and the corresponding AS must be specified.
If you are uncertain about the status of an ASP or need to query the protocol and
association information of the ASP, you can take this procedure.
Steps
> M3UA ASP. The M3UA ASP tab is displayed.
3. Right-click the selected records and select ASP state request.
End of Steps
4.3.2 Querying ASP States in Batches

This procedure describes how to query the status of all the configured ASPs. It is applicable
when the statuses of all the configured ASPs need to be verified.
4-5
SJ-20140527134643-021|2014-07-28(R1.0)
For example, if there is an ASP status change notification, you can take this procedure to
check the status of all the ASPs.
Steps
3. Right-click the selected records and select Batch ASP status query.
End of Steps
4.3.3 Enabling ASP

This procedure describes how to perform the UP operation to a specified ASP. The UP
operation cannot directly enable the ASP to be available. A protocol interaction process
with the peer end is required (if the negotiation fails, the ASP is still unavailable). The
DOWN operation directly changes the ASP in any status to DOWN status.
l
l
If you want an ASP to start negotiation, you can perform the UP operation on the ASP.
If an ASP is unavailable, you can perform DOWN and UP operations to request the
ASP to re-initiate negotiation until the ASP is available. The DOWN operation on an
ASP causes that data cannot be transmitted on the ASP.
Steps
3. Right-click the selected records and select ASP up. The result is displayed in the
Up/Down Operation Result column.
End of Steps
4.3.4 Disabling ASP

This procedure describes how to perform the DOWN operation to a specified ASP. The UP
operation cannot directly enable the ASP to be available. A protocol interaction process
with the peer end is required (if the negotiation fails, the ASP is still unavailable). The
DOWN operation directly changes the ASP in any status to DOWN status.
l
l
If an ASP is not required to be in service, you can perform the DOWN operation on
the ASP.
If an ASP is unavailable, you can perform DOWN and UP operations to request the
ASP to re-initiate negotiation until the ASP is available. The DOWN operation on an
ASP causes that data cannot be transmitted on the ASP.
4-6
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select ASP down. The result is displayed in the
Up/Down Operation Result column.
End of Steps
4.3.5 Activating ASP

This procedure describes how to activate an ASP on a specified AS. An ASP and the
corresponding AS must be specified.
l
l
If you want to put an ASP into service, you can take this procedure to activate the
ASP.
If an ASP is not available, you can take this procedure to deactivate and then activate
the ASP so that the ASP is available. The deactivation operation on an ASP causes
that data cannot be transmitted on the ASP.
Steps
3. Right-click the selected records and select ASP active. The result is displayed in the
Active/Inactive Operation Result column.
End of Steps
4.3.6 Deactivating ASP

This procedure describes how to deactivate an ASP on a specified AS. An ASP and the
corresponding AS must be specified.
l
l
If an ASP is not required to be in service, you can deactivate the ASP.

If an ASP is not available, you can take this procedure to deactivate and then activate
the ASP so that the ASP is available. The deactivation operation on an ASP causes
that data cannot be transmitted on the ASP.
Prerequisite
The M3UA ASP tab page is opened.
Steps
4-7
SJ-20140527134643-021|2014-07-28(R1.0)

3. Right-click the selected records and select ASP inactive. The result is displayed in
the Active/Inactive Operation Result column.
End of Steps
4.4 Signalling Link

4.4.1 Querying MTP3 Link Status (Layer 2)
This procedure describes how to query the status and congestion level of a specified link
on the SMP.
A maximum of 32 links can be queried at one time. The global link number is the start link
number for query. Link numbers are displayed in ascending order. If there is only one link,
only the status of this link is queried.
This procedure can check the signaling status of a link on the SMP. For example, if a link
is not written to a routing table as expected, you can use this command to locate the link.
Steps
> Signalling Link. The Signalling Link tab is displayed.
3. Right-click the selected records and select the command to execute the MTP3 link
status query (layer 2).
End of Steps
4.4.2 Querying MTP3 Link Status (Layer 3)

This procedure describes how to query the status of a specified link on the OMP. It is used
to query the MTP3 link status on SMP.
A maximum of 32 links can be queried. The global link number is the start link number for
query. Link numbers are displayed in ascending order.
If there is only one link, the command queries the status of this link. This procedure can
verify the status of a specified signaling link.
Steps
4-8
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select the command to execute the MTP3 link
status query (layer 3).
End of Steps
4.4.3 Querying the Current Load of MTP3 Link

This procedure describes how to query the load of a specified link or specified office.
l
l
If the query type is link query, the link load is displayed. The maximum link number is
the global link number 9000.
If the query type is office query, the total load of all the links to an office is displayed,
and the maximum link number is 2048.
If you are suspicious of the load of a signaling link, for example, no load on the link,
or doubt the accuracy of a signaling link load counter, you can take this procedure to
check the real-time signaling link load.
Steps
3. Right-click the selected records and select To query the current load of MTP3 link.
End of Steps
4.4.4 Inhibiting an MTP3 Link

This procedure describes how to inhibit a specified link.
The last link can be deactivated but cannot be blocked.
Inhibiting a link only adds an inhibition flag to the link but not stop the link. Deactivating a
link requests the MTP2 to stop the link.
If there is only one link to an office, the link cannot be inhibited. The operation is used in
signaling protocol tests.
Link inhibition changes the link status, and the uninhibited links cannot be written to routing
tables, affecting the loads of other available links.
Steps
3. Right-click the selected records and select To inhibit MTP3 link
End of Steps
4-9
SJ-20140527134643-021|2014-07-28(R1.0)
4.4.5 Uninhibiting an MTP3 Link

This procedure describes how to uninhibit a specified link.
The last link can be deactivated but cannot be blocked.
Inhibiting a link only adds an inhibition flag to the link but not stop the link. Deactivating a
link requests the MTP2 to stop the link.
If there is only one link to an office, the link cannot be inhibited. This procedure is used in
signaling protocol tests.
Link inhibition changes the link status, and the uninhibited links cannot be written to routing
tables, affecting the loads of other available links.
Steps
> Signalling Link. The Signalling Link tab page is displayed.
3. Right-click the selected records and select To uninhibit MTP3 link
End of Steps
4.4.6 Activating an MTP3 Link

This procedure describes how to activate a specified link.
l
l
If a link is not required to be in service, you can deactivate the link. If you want to put
the link into service, you can activate the link.
If a specified link cannot be put into service normally, you can deactivate the link and
then activate the link. Link deactivation may affect signaling routes and further affect
services.
Context
This task is performed for test or transmission detection and maintenance. After relevant
operations are performed, the link needs to be activated to ensure normal load sharing of
the service. If the link is activated successfully, it changes to service status and can carry
service messages properly.
Steps
3. Right-click the selected records and select To activate MTP3 link
4. Click OK.
End of Steps
4-10
SJ-20140527134643-021|2014-07-28(R1.0)
4.4.7 Deactivating an MTP3 Link

This procedure describes how to deactivate a specified link.
l
l
If a link is not required to be in service, you can deactivate the link. If you want to put
the link into service, you can activate the link.
If a specified link cannot be put into service normally, you can deactivate the link and
then activate the link. Link deactivation may affect signaling routes and further affect
services.
Context
This task is performed for test or transmission detection and maintenance. It avoids packet
loss due to service routed to this link. In this case, this link is in out-of-service status. The
link is disconnected and does not carry any service message.
Steps
3. Right-click the selected records and select To deactivate MTP3 link
4. Click OK.
End of Steps
4.4.8 Activating All MTP3 Links

This procedure describes how to activate all the MTP3 links. Take care when performing
the operation. It is used during commissioning or reset of the entire system. Link
deactivation changes the link status and causes signaling routes to be unavailable.
Steps
3. Right-click the selected records and select To activate all MTP3 link.
4. Click OK.
End of Steps
4.4.9 Deactivating All MTP3 Links

This procedure describes how to deactivate all the MTP3 links. Take care when
performing the operation. It is used during commissioning or reset of the entire system.
Link deactivation changes the link status and causes signaling routes to be unavailable.
4-11
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select To deactivate all MTP3 link
4. Click OK.
End of Steps
4.4.10 Querying the Link Status in Batches

This procedure describes how to query the status of all the currently configured links. It is
used during commissioning or reset of the entire system.
Steps
3. Right-click the selected records and select the command to execute the link status
query in batch.
End of Steps
4.5 Querying the MTP3 Linkset Status

This procedure describes how to query the office, available links, configured links, and
status of a specified linkset. It is applicable when the actual status of the signaling linkset
needs to be verified.
Steps
1. In the left pane, select Root Node > GERAN Subnetwork > Managed NE >
Transmission Resource > Signaling Linkset. The Signaling Linkset tab is
displayed.
2. Select one or more association records.
3. Right-click the records and select MTP3 Linkset Status Query from the shortcut
menu.
End of Steps
4-12
SJ-20140527134643-021|2014-07-28(R1.0)
4.6 Adjacent No. 7 Office

4.6.1 Querying Status and Key Information of Adjacent No. 7 Office
This procedure describes how to query the type, combined type, and status of a specified
office. If there is an office unavailable alarm, you can take this procedure to query the
office status and key information.
Steps
> Adjacent No. 7 Office. The Adjacent No. 7 Office tab is displayed.
3. Right-click the selected records and select the command to execute the status and
key information query of the Adjacent No. 7 Office.
End of Steps
4.6.2 Querying Office Status in Batches

This procedure describes how to query the status of all the currently configured offices. It
is used during commissioning or reset of the entire system.
Steps
3. Right-click the selected records and select the command to execute the office status
query in batch.
End of Steps
4.6.3 Querying the Status of an SCCP Subsystem

This procedure describes how to query the status of an SCCP subsystem and check
whether the subsystem is available.
This function can be used to query the statuses of SCCP subsystems in case of subsystem
unavailable alarms or service failures.
Steps
4-13
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Query the status of ssn from the shortcut
menu.
End of Steps
4.7 Local SCCP Subsystem

4.7.1 Blocking or Unblocking a Local SCCP Subsystem
This procedure describes how to block or unblock the local SCCP subsystem.
Steps
> Local SCCP Subsystem. The Local SCCP Subsystem tab is displayed.
3. Right-click the selected records and select Block or Unblock from the shortcut menu,
see Figure 4-1.
Figure 4-1 Blocking or Unblocking a Local SCCP Subsystem
End of Steps
4.7.2 Querying the Status of a Local SCCP Subsystem

This procedure describes how to query the status of a local SCCP subsystem and check
whether the subsystem is available.
This function can be used to query the statuses of local SCCP subsystems in case of
subsystem unavailable alarms or service failures.
Steps
> Local SCCP Subsystem. The Local SCCP Subsystem tab is displayed.
4-14
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Query the status of local ssn from the
shortcut menu.
End of Steps
4.8 Querying MTP2 Link Status

This procedure describes how to query the MTP2 link status, including the subsystem
number, unit number, module number, subunit number, and global link number.
Steps
> MTP2 Link. The MTP2 Link tab is displayed.
3. Right-click the selected records and select To query the status of MTP2 Link.
End of Steps
4.9 Querying Valid Bandwidth of a Transport Path

This procedure describes how to query the maximum available bandwidth of a transport
path and the bandwidths occupied by realtime and non-realtime services on the path. If
the path number is 65535, the query result is displayed in batches based on the office
number. You can take this procedure if the call success rate is decreased.
Steps
> Transmission Path. The Transmission Path tab is displayed.
3. Right-click the selected records and select Transport path valid band query.
End of Steps
4.10 Querying Valid Bandwidth of a Transport Path

Group
This procedure describes how to query the maximum available bandwidth of a transport
path group and the bandwidth occupied by each radio system. You can take this procedure
if the call success rate is decreased.
Steps
> Transmission Path Group. The Transmission Path Group tab is displayed.
4-15
SJ-20140527134643-021|2014-07-28(R1.0)

3. Right-click the selected records and select Transport path group band query.
End of Steps
4.11 Querying DHCP Client Configuration Status Query

This procedure describes how to query the DHCP configuration of the client during the
deployment or cutover of a site that supports automatic link establishment, including the
IP address allocated to the base station, the operation and maintenance IP address of the
RNC, and the IP address of the gateway.
Context
You can query the forward and backward valid bandwidth of the transmission path of the
DHCP client.
Steps
> DHCP Client. The DHCP Client tab is displayed.
3. Right-click the selected records and select DHCP client configuration status
information query.
End of Steps
4.12 RPU Board

4.12.1 Querying Interfaces in RPU
This procedure describes how to query all the interface configurations on an NE based on
the logical address of an RPU board. The RPU board operates properly. If an interface
address cannot be pinged successfully, you can take this procedure to query the RPU
interface status.
Steps
> RPU Board. The RPU Board tab is displayed.
2. Select a record.
3. Right-click the selected record and select Interface inquiry in RPU from the shortcut
menu, see Figure 4-2.
4-16
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 4-2 Querying Interfaces in RPU
End of Steps
4.12.2 Querying Routes in RPU

This procedure describes how to query all the route configurations on an NE based on
the logical address of an RPU board. The RPU board operates properly. If an NE cannot
communicate with external NEs, you can use this command to query all the routes on the
NE.
Steps
2. Select a record.
3. Right-click the selected record and select Route inquiry in RPU. The Route inquiry
in RPU result page is displayed.
End of Steps
4-17
SJ-20140527134643-021|2014-07-28(R1.0)
4.12.3 Querying Static ARP

This procedure describes how to query all the configured ARP information of an NE
(including IP addresses and MAC addresses of the ports) based on the logical address of
an RPU board. If an IP address is not accessible and the peer end does not send ARP
packets, you can take this procedure to check whether there are static ARP entries. If
there is no corresponding ARP entry for the IP address, you need to configure a static
ARP entry.
Steps
2. Select a record.
3. Right-click the selected record and select ARP static query. The ARP static query
result page is displayed.
End of Steps
4.12.4 Querying the ARP List at an Aggregate Port

This procedure describes how to query the ARP information at an aggregate port, including
IP addresses and MAC address in the ARP list.
When an IP address in the network connected to an aggregate port is unreachable, you
can use this function to query all ARP entries at the aggregate port and check whether
an entry containing this IP address exists. If no entry containing the IP address, it can be
determined that an ARP fault occurs.
Steps
2. Select a record.
3. Right-click the selected record and select To query port channel ARP from the
shortcut menu. The To query port channel ARP dialog box is displayed, see Figure
4-3.
4-18
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 4-3 To Query Port Channel ARP Dialog Box
4. Enter the aggregate port number and the sub-interface number and then click OK.
End of Steps
4.12.5 Querying the ARP List at a Super VLAN Port

This procedure describes how to query the ARP information at a super VLAN port, including
IP addresses and MAC address in the ARP list.
When an IP address in the network connected to a super VLAN port is unreachable, you
can use this function to query all ARP entries at the super VLAN port and check whether
an entry containing this IP address exists. If no entry containing the IP address, it can be
determined that an ARP fault occurs.
Steps
2. Select a record.
3. Right-click the selected record and select To query SUPERVLAN interface ARP
from the shortcut menu. The To query SUPERVLAN interface ARP dialog box is
Figure 4-4 To Query SuperVLAN Interface ARP Dialog Box
4-19
SJ-20140527134643-021|2014-07-28(R1.0)
4. Enter a super VLAN ID and click OK.

End of Steps
4.12.6 Querying Channel Group

This procedure describes how to query the configuration of an aggregate port (including
system priority, MAC address, and aggregation mode) based on the logical address of an
RPU board and aggregate port number.
If the aggregation of an aggregate port fails, you can take this procedure to check whether
the aggregate port configuration is correct.
Steps
2. Select a record.
3. Right-click the selected record and select the command to execute channel group
query. A dialog box prompts, see Figure 4-5.
Figure 4-5 Entering Channel Group No.
4. Enter a Channel Group No..

5. Click OK.
End of Steps
4.12.7 Querying LACP Counters at Group Interface

This procedure describes how to query the LACP packet statistics on an aggregate
port based on the logical address of an RPU board and aggregate port number. If the
aggregation of an aggregate port fails, you can take this procedure to check whether
LACP packets are properly sent and received on the aggregate port.
Steps
2. Select a record.
4-20
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select the command to execute LACP packet
sending/receiving query at group interface. A dialog box prompts.
4. Enter a Channel Group No.
5. Click OK.
End of Steps
4.12.8 Querying Channel Group Information

This procedure describes how to query the configuration and status of the peer aggregate
port based on the logical address of an RPU board and local aggregate port number. If
the aggregation of an aggregate port fails, you can use this command to check whether
the peer aggregate port configuration matches the local configuration.
Steps
2. Select a record.
3. Right-click the selected record and select the command to query channel group
information. A dialog box prompts
5. Click OK.
End of Steps
4.12.9 Querying Interfaces Status for Channel Group

This procedure describes how to query the statuses of all the aggregate members of an
aggregate port based on the logical address of an RPU board and aggregate port number.
l
l
If an aggregate member is not successfully aggregated, you can take this procedure
to check the statuses of aggregate members.
This operation can check whether all the aggregate members are aggregated to the
aggregate port.
Steps
2. Select a record.
3. Right-click the selected record and select the command to execute the interface status
query for channel group. A dialog box prompts
4-21
SJ-20140527134643-021|2014-07-28(R1.0)
5. Click OK.
End of Steps
4.12.10 Querying BFD DAMP

This procedure describes how to query all the BFD damping configurations on an NE
based on the logical address of an RPU board. The damping configuration can avoid the
effect of frequency status changes of BFD links on upper-layer protocols. If the BFD link
status frequently changes, you can take this procedure to check whether BFD damping is
configured.
Steps
2. Select a record.
3. Right-click the selected record and select BFD Damp Inquiry. The BFD Damp
Inquiry result page is displayed.
End of Steps
4.12.11 Querying POLICYMAP in RPU

This procedure describes how to query all the policy map tables of an NE based on the
logical address of an RPU board. If the packet priority is not as expected, you can take
this procedure to check whether the policy map configuration is correct.
Steps
2. Select a record.
3. Right-click the selected record and select Policymap query in RPU. The result is
displayed in Policymap query in RPU page.
End of Steps
4.12.12 Querying SUPERVLAN Members

This procedure describes how to query SUPERVLAN members based on the
SUPERVLAN number. The RPU board operates properly. It is used to query the
information of all members under the SUPERVLAN.
Steps
4-22
SJ-20140527134643-021|2014-07-28(R1.0)
2. Select a record.
3. Right-click the selected record and select Supervlan Member Inquiry.
4. Enter SUPERVLAN No.
5. Click OK.
End of Steps
4.12.13 Querying SUPERVLAN Port IP-PORT Table

This procedure describes how to query the SUPERVLAN port IP-PORT table.
Steps
2. Select a record.
3. Right-click the selected record and select Supervlan Port IP-PORT Table Inquiry.
4. Enter SUPERVLAN No.
5. Click OK.
End of Steps
4.12.14 Querying Relationship Between RUP Interface and 802.3ah

Protocol in RPU
This procedure describes how to check whether 802.3ah detection and 802.3ah damping
are enabled for all the interface cards of an NE based on the logical address of an RPU
board. If the physical status of a port is different from the status on the RPU, you can take
this procedure to check whether 802.3ah detection is configured.
Steps
2. Select a record.
3. Right-click the selected record and select Interface query relates to 802.3ah
protocol on RPU. The result is displayed in the Interface query related to 802.3ah
protocol on RPU page.
End of Steps
4-23
SJ-20140527134643-021|2014-07-28(R1.0)
4.12.15 Querying MD Configuration on RPU

This procedure describes how to query the configuration of a single or all the MDs of an NE
based on the logical address of an RPU board and MD ID. Take this procedure to check
whether the MD configuration accords with the plan.
Steps
2. Select a record.
3. Right-click the selected record and select the command to execute the MD
configuration query on RPU.
4. Enter the MD mark, and click OK.
End of Steps
4.12.16 Querying MA Configuration on RPU

This procedure describes how to query the configuration of a single or all the MAs of an
NE based on the logical address of an RPU board, MD ID, and MA ID. Take this procedure
to check whether the MA configuration accords with the plan.
Steps
2. Select a record.
3. Right-click the selected record and select the command to execute the MA
configuration query on RPU.
4. Enter the MD mark and MA mark.
5. Click OK.
End of Steps
4.12.17 Querying IPV4 PMTU Items on an RPU

This procedure describes how to query the PMTU information in an interface board. You
can use this function to query the contents in the IPV4 PMTU table.
Steps
2. Select a record.
4-24
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select IPV4 PMTU item information query in RPU
from the shortcut menu. A dialog box is displayed, indicating the query result.
End of Steps
4.12.18 Querying the Switching Type

This procedure describes how to query the type (received packet followed or 802.3AH) of
switching performed on an RPU board. This function is used during maintenance.
Steps
2. Select a record.
3. Right-click the selected record and select Switch type inquiry. A dialog box is
displayed, indicating the query result.
End of Steps
4.13 EPU Board

4.13.1 Querying EPU Interface
For the EPU interface query, refer to the operations of the RPU interface query.
4.13.2 Querying EPU Route

For the EPU route query, refer to the operations of the RPU route query.
4.13.3 Querying ARP Port

This procedure describes how to query the ARP information of a port, including the IP
address and MAC address of the port. You can take this procedure if an IP address is not
accessible.
Steps
> EPU Board. The EPU Board tab is displayed.
2. Select a record.
3. Right-click the selected record and select ARP port query.
4. Enter a port No.
5. Click OK.
End of Steps
4-25
SJ-20140527134643-021|2014-07-28(R1.0)
4.13.4 Querying BFD Sessions Brief Information on EPU

This procedure describes how to query the brief information of BFD sessions on an EPU
board based on the board address. It is used to check whether the BFD link detection
succeeds.
Steps
2. Select a record.
3. Right-click the selected record and select BFD Session Brief Query on EPU.
End of Steps
4.13.5 Querying BFD Detail Information on EPU

This procedure describes how to query the detailed information of BFD sessions on an
EPU board based on the logical address of the board. It is used to check whether the BFD
link detection succeeds.
Steps
2. Select a record.
3. Right-click the selected record and select BFD Session Detail Query on EPU.
End of Steps
4.13.6 Querying Changeover by BFD in EPU

This procedure describes how to check whether the port-based BFD changeover function
is configured for an EPU board and whether there is any port down record based on the
logical address of the board. If a BFD port has a fault, you can take this procedure to check
whether BFD supports port-based switchover.
Steps
2. Select a record.
3. Right-click the selected record and select Do changeover by BFD in EPU.
End of Steps
4-26
SJ-20140527134643-021|2014-07-28(R1.0)
4.13.7 Querying POLICYMAP in EPU

Refer to the related operations in RPU.
4.13.8 Querying Relationship Between Interface and 802.3ah

Protocol in EPU
Refer to the related operations in RPU.
4.13.9 Querying IPV4 PMTU Items in an EPU

This procedure describes how to query the PMTU information in an interface board. This
function is used when you want to query the contents in the IPV4 PMTU table.
Steps
2. Select a record.
3. Right-click the selected record and select IPV4 PMTU item information query in EPU
from the shortcut menu. A dialog box is displayed, indicating the query result.
End of Steps
4.13.10 Querying the IPD Session Details in an EPU

This procedure describes how to query the details of IPD sessions in an interface board.
Steps
2. Select a record.
3. Right-click the selected record and select IPD sessions detail in EPU from the
shortcut menu. A dialog box is displayed, indicating the query result.
End of Steps
4.14 IPv4 ACL Rule

4.14.1 Querying All ACL4 Tables
This procedure describes how to query all the ACL4 tables (including table name, rule
number, IP address and mask, and protocol information) based on the logical address of
an RPU board. The valid logical address of the RPU board must be entered.
l
Take this procedure to verify the ACL4 table information during commissioning.
4-27
SJ-20140527134643-021|2014-07-28(R1.0)
If it is detected that packets are discarded unexpectedly during network operation, you
can take this procedure to query ACL4 table information.
Steps
> IPV4 ACL Rule. The IPV4 ACL Rule tab is displayed.
3. Right-click the selected records and select ACL4 All Table Query, see Figure 4-6.
Figure 4-6 Querying All ACL4 Tables
End of Steps
4.14.2 Querying Specific ACL4 Tables

This procedure describes how to query a specified ACL4 table (including table name, rule
number, IP address and mask, and protocol information) based on the logical address of
an RPU board and the ACL4 table name or table ID. The valid logical address of the RPU
board and the ACL4 name or table number must be entered.
If a port has a transmission fault, you can determine the name or number of the ACL4 table
that is bound to the port and take this procedure to query ACL4 table information based
on the ACL4 table name or number.
Steps
3. Right-click the selected records and select ACL4 Specific Table Query.
End of Steps
4-28
SJ-20140527134643-021|2014-07-28(R1.0)
4.14.3 Querying ACL4 Group Interface Binding

This procedure describes how to query the ACL4 tables that are bound to all the interfaces
of the local office based on the logical address of an RPU board. The valid logical address
of the RPU board must be entered.
l
l
Take this procedure to confirm the binding of ACL4 tables and ports during
commissioning.
If a port has a transmission fault during network operation, you can take this procedure
to determine the name or number of the ACL4 table bound to the port.
Steps
3. Right-click the selected records and select ACL4 Group Query.
End of Steps
4.15 MAC ACL Rule

4.15.1 Querying All MACL Tables
This procedure describes how to query all the configurations of the MAC ACLs in all MACL
tables.
Steps
> MAC ACL Rule. The MAC ACL Rule tab is displayed.
3. Right-click the selected records and select MACL All Table Query.
End of Steps
4.15.2 Querying Specific MACL Tables

This procedure describes how to query all the configurations of the MACL ACLs in a
specific MACL table.
Steps
> MAC ACL Rule. The MAC ACL Rule tab is displayed.
4-29
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select MACL Specific Table Query.
End of Steps
4.15.3 Querying MACL Group Interface Binding

This procedure describes how to query the binding of MAC ACLs in all MACL tables.
Steps
1. Select Root Node > GERAN Subnetwork > Managed NE > Mac ACL Rule. The
Mac ACL Rule tab is displayed.
3. Right-click the selected records and select MACL Group Query.
End of Steps
4.16 802.3ah OAM Configuration

4.16.1 Querying Configurations and Status of Ethernet OAM in EPU
This procedure describes how to query the ETHOAM configuration and status of a port
based on the logical address of an EPU board and port number. If ETHOAM detects that
the state machine cannot complete negotiation, take this procedure to query the ETHOAM
configuration and status of the port.
Steps
> Ethernet OAM. The Ethernet OAM tab is displayed.
3. Right-click the selected records and select ETHOAM Configuration and Status
Query in EPU.
End of Steps
4.16.2 Querying Link Monitoring of Ethernet OAM in EPU

This procedure describes how to query the ETHOAM link event configuration and
monitoring result of a port based on the logical address of an EPU board and port number.
Take this procedure to learn about the ETHOAM link transmission quality.
Steps
4-30
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select ETHOAM Link Query in EPU.
End of Steps
4.16.3 Querying Packets of Ethernet OAM in EPU

This procedure describes how to query the ETHOAM packet statistics of a port based on
the logical address of an EPU board and port number. If ETHOAM detects that the state
machine cannot complete negotiation, take this procedure to query statistics of packets
over ETHOAM links on EPU.
Steps
3. Right-click the selected records and select ETHOAM Link Packet Query in EPU.
End of Steps
4.16.4 Querying Configuration of Ethernet OAM in EPU's All Port

This procedure describes how to query the ETHOAM configuration of all ports on the RPU.
Steps
3. Right-click the selected records and select ETHOAM Configuration Query in EPU's
all port.
End of Steps
4.17 PTP Port

4.17.1 Querying Configurations of All PTP Ports
This procedure describes how to query the configuration of all the PTP ports of an NE
based on the RPU board address. It is used to query the ports on which PTP is configured.
For example, if unicast negotiation of a port fails, you can take this procedure to check
whether unicast negotiation is enabled.
Steps
> PTP Port. The PTP Port tab is displayed.
4-31
SJ-20140527134643-021|2014-07-28(R1.0)

3. Right-click the selected records and select All PTP Ports Configuration Query.
End of Steps
4.17.2 Querying PTP Global Configuration

This procedure describes how to query the global PTP configuration based on the RPU
board address. It is used to check the global PTP configuration.
Steps
3. Right-click the selected records and select PTP Global Configuration Query.
End of Steps
4.17.3 Querying State of All PTP Ports

This procedure describes how to query the status (master, slave, or others) of all the PTP
ports on an EPU board. For example, if one or more clocks cannot synchronize the time,
you can use this command to check whether the ports are in expected status.
Steps
3. Right-click the selected records and select All PTP Ports State Query.
End of Steps
4.17.4 Querying State of Specified PTP Port

This procedure describes how to query the status (master, slave, or others) of a specified
PTP port on an EPU board.
This command can query the status of a specified PTP port on a board. For example, if a
clock cannot synchronize the time, you can take this procedure to check whether the port
is in expected status.
Steps
4-32
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Specified PTP Port State Query.
End of Steps
4.17.5 Querying PTP Unicast Negotiation

This procedure describes how to query all the PTP unicast sessions on an EPU board. The
command output shows the source address and destination address of each PTP unicast
session, negotiation type, and negotiation success or failure.
l
l
This operation helps learn about the number of clocks that use unicast for time
synchronization.
You can check whether unicast negotiation is successful based on the query result.
Steps
3. Right-click the selected records and select PTP Unicast Negotiation Query.
End of Steps
4.17.6 Querying PTP Ebest

This procedure describes how to query the PTP Ebest.
Steps
3. Right-click the selected records and select PTP Ebest Query.
End of Steps
4-33
SJ-20140527134643-021|2014-07-28(R1.0)
4-34
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 5
GSM Radio Resources

Table of Contents
PCM at the A Interface ...............................................................................................5-1
Trunk at the A Interface ..............................................................................................5-4
Resetting a Circuit at the A Interface ..........................................................................5-6
PCM at the Virtual A Interface ....................................................................................5-7
Trunk at the Virtual A Interface ...................................................................................5-8
PCM at the Ater Interface ...........................................................................................5-8
Timeslot at the Ater Interface......................................................................................5-9
Resetting an ITC Office ............................................................................................5-10
MSC Office...............................................................................................................5-10
Slave Subunit (GSM)................................................................................................5-12
NSVC.......................................................................................................................5-14
SGSN Office.............................................................................................................5-15
Querying the Status of the Local End Point ..............................................................5-16
NSE .........................................................................................................................5-17
Cell ..........................................................................................................................5-18
Frequency ................................................................................................................5-24
Timeslot ...................................................................................................................5-27
GSM Module ............................................................................................................5-31
BVC .........................................................................................................................5-32
ABIS.........................................................................................................................5-33
Querying Timeslot Usage at the Abis Interface .........................................................5-35
Querying Device Status at the Abis Interface............................................................5-35
Site ..........................................................................................................................5-36
Resetting a Rack ......................................................................................................5-38
Querying Ring Network Status .................................................................................5-38
5.1 PCM at the A Interface

5.1.1 Querying PCM Status at the A Interface
This procedure describes how to query the status of a PCM link connected to a specific
MSC. This function is used to query the PCM status of a specific A interface when the
corresponding MSC office is disconnected.
5-1
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
1. Select Root Node > GERAN Subnetwork > Managed NE > GSM Radio Resource
> GATRUNKPCM. The GATRUNKPCM tab is displayed.
2. Select a record.
3. Right-click the selected record and select QRY APCM.
End of Steps
5.1.2 Blocking a PCM Link at the A Interface

A PCM link at the A interface can be manually blocked, unblocked, equipped, and
unequipped.
l
A PCM link at the A interface must be blocked or unequipped before PCM

maintenance. After the maintenance is completed, the PCM link must be unblocked
or equipped to resume operation.
A PCM link can be unequipped when simulation of the A interface without PCM
configuration is required. After the simulation is completed, the PCM link can be
equipped. Blocking or unequipping a PCM link results in service interruption on the
link and increases the load on the other resources of the same type.
This procedure describes how to block a PCM link at the A interface.
Steps
2. Select a record.
3. Right-click the selected record and select BLK APCM from the shortcut menu.
4. Click OK.
End of Steps
5.1.3 Unblocking a PCM Link at the A Interface

unequipped.
l

This procedure describes how to unblock a PCM link at the A interface.

5-2
SJ-20140527134643-021|2014-07-28(R1.0)
Chapter 5 GSM Radio Resources
Steps
2. Select a record.
3. Right-click the selected record and select UNB APCM from the shortcut menu.
4. Click OK.
End of Steps
5.1.4 Equipping a PCM Link at the A Interface

unequipped.
l

This procedure describes how to equip a PCM link at the A interface.
Steps
2. Select a record.
3. Right-click the selected record and select EQP APCM from the shortcut menu.
4. Click OK.
End of Steps
5.1.5 Unequipping a PCM Link on the A Interface

unequipped.
l

5-3
SJ-20140527134643-021|2014-07-28(R1.0)
This procedure describes how to unequip a PCM link at the A interface.
Steps
2. Select a record.
3. Right-click the selected record and select UNEQP APCM from the shortcut menu.
End of Steps
5.2 Trunk at the A Interface

5.2.1 Querying the Status of a Trunk at the A Interface
This procedure describes how to query the status of a trunk at the A interface. If the timeslot
number is 255, this operation queries the circuit statuses of all timeslots on the PCM line.
This function can be used to query the trunk status when an alarm relating to trunks at the
A interface occurs.
Steps
> GATRUNKTS. The GATRUNKTS tab is displayed.
2. Select a record.
3. Right-click the selected record and select QRY ATRUNK from the shortcut menu.
End of Steps
5.2.2 Blocking a Trunk at the A Interface

A timeslot on a PCM link at the A interface can be manually blocked or unblocked. The
timeslot becomes unavailable after being blocked and becomes available after being
unblocked.
l
A timeslot on a PCM link at the A interface must be blocked before it is maintained.

After the maintenance is completed, this timesot must be unblocked to resume
operation.
A timeslot can be blocked when a failure occurs in the timeslot. Blocking a timeslot
results in service interruption on the timeslot and increases the load on the other
resources of the same type.
This procedure describes how to block a timeslot at the A interface.
5-4
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select BLK ATRUNK from the shortcut menu.
4. Perform an appropriate operation as required:
Operation
Result
Block and release
The trunk at the A interface is blocked and the

corresponding service is released.
Block and no release
The trunk at the A interface is blocked and the

corresponding service is not released.
End of Steps
5.2.3 Unblocking a Trunk at the A Interface

A timeslot on a PCM link at the A interface can be manually blocked or unblocked. The
timeslot becomes unavailable after being blocked and becomes available after being
unblocked.
l
A timeslot on a PCM link at the A interface must be blocked before it is maintained.

After the maintenance is completed, this timesot must be unblocked to resume
operation.
A timeslot can be blocked when a failure occurs in the timeslot. Blocking a timeslot
results in service interruption on the timeslot and increases the load on the other
resources of the same type.
This procedure describes how to unblock a timeslot at the A interface.
Steps
2. Select a record.
3. Right-click the selected record and select UNB ATRUNK from the shortcut menu.
End of Steps
5.2.4 Starting Trunk Monitoring at the A Interface

The monitoring function allows you to obtain the latest information of an object in real
time. After the monitoring command is sent to the object, the object reports its latest
information once any change occurs. To stop the monitoring, you must send a monitoring
stop command.
5-5
SJ-20140527134643-021|2014-07-28(R1.0)
This procedure describes how to start the monitoring on a trunk at the A interface.
Steps
3. Right-click the selected records and select SPY ATRUNK from the shortcut menu.
End of Steps
5.2.5 Stopping Trunk Monitoring at the A Interface

The monitoring function allows you to obtain the latest information of an object in real
time. After the monitoring command is sent to the object, the object reports its latest
information once any change occurs. To stop the monitoring, you must send a monitoring
stop command.
This procedure describes how to stop the monitoring on a trunk at the A interface.
Steps
3. Right-click the selected records and select STP ATRUNK SPY from the shortcut menu.
End of Steps
5.3 Resetting a Circuit at the A Interface

A subslot at the Ater interface can be blocked or unblocked in case of iTC. When a failure
occurs in a subslot, the subslot can be blocked to prevent impact on the network quality.
After the failure is resolved, this subslot can be unblocked. Resetting a subslot results in
service interruption in the subslot.
Steps
> ACIRC. The ACIRC tab is displayed.
3. Right-click the selected records and select RST ACIRC from the shortcut menu.
4. Click OK.
End of Steps
5-6
SJ-20140527134643-021|2014-07-28(R1.0)
5.4 PCM at the Virtual A Interface

5.4.1 Querying PCM Status at the Virtual A Interface
This procedure describes how to query the status of a PCM link at the virtual A interface.
When a PCM link is unavailable, this function can be used to query the status of the PCM
link at the virtual A interface between the BSC and the MSC.
Steps
> ARESPCM. The ARESPCM tab is displayed.
2. Select a record.
3. Right-click the selected record and select QRY ARESPCM from the shortcut menu.
End of Steps
5.4.2 Blocking a PCM Link at the Virtual A Interface

When a failure occurs on a PCM link at the virtual A interface, this link can be blocked to
prevent the failure from affecting the network quality.
Steps
2. Select a record.
3. Right-click the selected record and select BLK ARESPCM from the shortcut menu.
End of Steps
5.4.3 Unblocking a PCM Link at the Virtual A Interface

When a failure occurs on a PCM link at the virtual A interface, this link can be blocked to
prevent the failure from affecting the network quality. After the link failure is resolved, this
PCM link can be unblocked to resume operation.
Steps
2. Select a record.
3. Right-click the selected record and select UNBLK ARESPCM from the shortcut menu.
End of Steps
5-7
SJ-20140527134643-021|2014-07-28(R1.0)
5.4.4 Equipping a PCM Link at the Virtual A Interface

A PCM link can be unequipped when simulation of the virtual A interface without PCM
configuration is required. After the simulation is completed, this PCM link can be equipped.
Steps
2. Select a record.
3. Right-click the selected record and select EQP ARESPCM from the shortcut menu.
End of Steps
5.5 Trunk at the Virtual A Interface

5.5.1 Querying the Status of a Remote Trunk at the A Interface
Refer to Querying the Status of a Trunk at the A Interface.
5.5.2 Blocking a Remote Trunk at the A Interface

When a remote trunk at the A interface fails, this trunk can be blocked to prevent the failed
trunk from affecting the network quality.
Steps
> ARESTRUNK. The ARESTRUNK tab is displayed.
2. Select a record.
3. Right-click the selected record and select Block Ares Interface Trunk from the
shortcut menu.
4. Select a blocking mode and click OK.
End of Steps
5.5.3 Unblocking a Remote Trunk at the A Interface

Refer to Unblocking a Trunk at the A Interface.
5.6 PCM at the Ater Interface

Refer to PCM at the A Interface.
5-8
SJ-20140527134643-021|2014-07-28(R1.0)
5.7 Timeslot at the Ater Interface

5.7.1 Querying Timeslot Status at the Ater Interface
The operational status of timeslots at the Ater interface can be queried in case of ITC
failure. This procedure describes how to query the status of a timeslot at the Ater interface.
Steps
> ATERTRUNK. The ATERTRUNK tab is displayed.
2. Select a record.
3. Right-click the selected record and select QRY ATERATRUNK from the shortcut
menu.
End of Steps
5.7.2 Blocking a Timeslot at the Ater Interface

When a subslot fails, the corresponding timeslot at the Ater interface can be blocked to
prevent the failure from affecting the network quality.
Steps
2. Select a record.
3. Right-click the selected record and select Block Ater Interface Trunk from the
shortcut menu.
4. Select a blocking mode (Block and Release or Block and NO Release) and click OK.
End of Steps
5.7.3 Unblocking a Timeslot at the Ater Interface

When a subslot fails, the corresponding timeslot at the Ater interface can be blocked to
prevent the failure from affecting the network quality. After the failure is resolved, the
timeslot can be unblocked to resume operation.
Steps
2. Select a record.
5-9
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select Unblock Ater Interface Trunk from the
shortcut menu.
End of Steps
5.8 Resetting an ITC Office

An ITC office can be reset when a failure occurs in the office.
Steps
> ITC. The ITC tab is displayed.
3. Right-click the selected records and select RST TC from the shortcut menu.
End of Steps
5.9 MSC Office

5.9.1 Querying the Status of an MSC Office
This procedure describes how to query the status of an MSC office, such as whether the
office is blocked and whether the office is available.
Steps
> MSC. The MSC tab is displayed.
3. Right-click the selected records and select QRY MSC from the shortcut menu.
End of Steps
5.9.2 Enabling an MSC Office

This procedure describes how to enable an MSC office. The MSC office becomes available
after being manually enabled.
Steps
3. Right-click the selected records and select USE MSC from the shortcut menu.
End of Steps
5-10
SJ-20140527134643-021|2014-07-28(R1.0)
5.9.3 Unloading an MSC Office

An unloaded MSC office does not permit initial MS access requests. MS signaling that is
already assigned to the MSC office is still sent to the MSC for processing.
This procedure describes how to unload an MSC office.
Steps
3. Right-click the selected records and select UNLD MSC from the shortcut menu.
End of Steps
5.9.4 Disabling an MSC Office

An MSC office becomes unavailable after being manually disabled. Load reallocation is
immediately performed for all messages sent to the disabled MSC.
Steps
3. Right-click the selected records and select UNUSE MSC from the shortcut menu.
End of Steps
5.9.5 Resetting an MSC Office

Resetting an MSC office results in a global logical reset of the BSC. The BSC releases
services and notifies the MSC.
Steps
3. Right-click the selected records and select RST MSC from the shortcut menu.
End of Steps
5.9.6 Resetting IPA Resources

Resetting an MSC office results in a global logical reset of the BSC. The BSC releases
services and notifies the MSC.
5-11
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select Reset IP Resource from the shortcut
menu.
End of Steps
5.10 Slave Subunit (GSM)

5.10.1 Querying the Status of IPA Resources
The usage of IPA resources on a GUB board can be queried when the CPU load of the
GUB board is too high or too low.
Steps
> Slave (GSM). The Slave (GSM) tab is displayed.
3. Right-click the selected records and select QRY IPA from the shortcut menu.
End of Steps
5.10.2 Blocking IPA Resources

When a subunit on a GUB board needs to be maintained or a failure occurs in a subunit
of the GUB board, the corresponding IPA resources can be blocked.
Steps
3. Right-click the selected records and select BLK IPA from the shortcut menu.
End of Steps
5.10.3 Unblocking IPA Resources

After the maintenance of a subunit on a GUB board is completed or a subunit failure is
resolved, the corresponding IPA resources can be unblocked.
5-12
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select UNB IPA from the shortcut menu.
End of Steps
5.10.4 Querying the Information of Slave Cells

This procedure describes how to query the information of cells bound to a DSP. This
function can be used to query the information of cells bound to the DSP of a board before
the board is replaced.
Steps
3. Right-click the selected records and select Query Cell By Slave from the shortcut
menu.
End of Steps
5.10.5 Adjusting the Quantity of Slave Cells

This procedure describes how to adjust the quantity of cells bound to a DSP. Only the
quantity can be adjusted. It is not allowed to select specific cells.
l
l
When a small number of cells are bound to a DSP, this function can be used to bind
more cells to the DSP.
When a large number of cells are bound to a DSP, this function can be used to reduce
cells bound to the DSP.
Steps
3. Right-click the selected records and select Adjust Cell in Slave from the shortcut
menu. A message is displayed, prompting you to confirm this operation.
4. Click Yes. The Adjust cells in Slave dialog box is displayed, see Figure 5-1.
5-13
SJ-20140527134643-021|2014-07-28(R1.0)
Figure 5-1 Adjust Cells in Slave Dialog Box
5. Select an adjustment type, enter a new number, and click OK.

End of Steps
5.11 NSVC
5.11.1 Querying the Status of an NSVC
The status of a specific NSVC can be queried during routine maintenance of the system
or when a Gb interface fails to transmit services.
Steps
> NSVC. The NSVC tab is displayed.
3. Right-click the selected records and select QRY NSVC from the shortcut menu.
End of Steps
5.11.2 Blocking an NSVC

An NSVC can be blocked when a failure occurs on the NSVC.
Steps
3. Right-click the selected records and select BLK NSVC from the shortcut menu.
End of Steps
5.11.3 Unblocking an NSVC

An NSVC can be unblocked after the NSVC failure is resolved.
5-14
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select UNB NSVC from the shortcut menu.
End of Steps
5.11.4 Resetting an NSVC

When transmission on anNSVC fails, the NSVC can be reset for status synchronization.
After that, you can check whether service transmission on the NSVC recovers.
Steps
3. Right-click the selected records and select RST NSVC from the shortcut menu.
End of Steps
5.12 SGSN Office

5.12.1 Querying the Status of an SGSN
The status of an SGSN corresponding to a Gb interface can be queried during routine
maintenance and inspection of the system or when the Gb interface fails to transmit
services.
Steps
> SGSN. The SGSN tab is displayed.
3. Right-click the selected records and select QRY SGSN from the shortcut menu.
End of Steps
5.12.2 Enabling an SGSN

This operation can be performed when a failure in an SGSN is resolved or an SGSN is to
be used.
5-15
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select USE SGSN from the shortcut menu.
End of Steps
5.12.3 Disabling an SGSN

This operation can be performed to disable an SGSN when a failure occurs in the SGSN
or the SGSN is not used.
Steps
3. Right-click the selected records and select UNUSE SGSN from the shortcut menu.
End of Steps
5.12.4 Unloading an SGSN

This operation can be performed to unload an SGSN when the SGSN is out of service in
the network.
Steps
3. Right-click the selected records and select UNLOAD SGSN from the shortcut menu.
End of Steps
5.13 Querying the Status of the Local End Point

This procedure describes how to query the status of the local end point, such as the SGSN
office ID, whether synchronization is required, whether the configuration is synchronized,
and whether the modified weight is synchronized.
Steps
> Local End Point. The Local End Point tab is displayed.
5-16
SJ-20140527134643-021|2014-07-28(R1.0)

3. Right-click the selected records and select Query End Point Status from the shortcut
menu.
End of Steps
5.14 NSE
5.14.1 Querying the Status of an NSE
This operation can be performed to check whether an NSE is operating properly during
NSE inspection.
Steps
> NSE. The NSE tab is displayed.
3. Right-click the selected records and select QRY NSE from the shortcut menu.
End of Steps
5.14.2 Re-configuring an NSE in Full Mode

This operation can be performed to re-configure an NSE in full mode when the existing
NSE configuration is ineffective.
Steps
3. Right-click the selected records and select RECFG ALL NSE from the shortcut menu.
End of Steps
5.14.3 Re-configuring an NSE in Incremental Mode

After an NSE is configured, this operation can be performed to re-configure the NSE in
incremental mode if the NSE configuration becomes ineffective again.
Steps
5-17
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select RECFG ADD NSE from the shortcut menu.
End of Steps
5.14.4 Querying the Status of an SGSN Dynamic End Node

This operation can be performed to query the information of the end node assigned at the
remote end when the NSE is dynamic.
Steps
3. Right-click the selected records and select Query Dynamic Endpoint Status from
the shortcut menu.
End of Steps
5.15 Cell
5.15.1 Querying the Status of a Cell
This operation can be performed to query the status of a cell when alarms indicating radio
resource problems occur.
Steps
> BTS. The BTS tab is displayed.
3. Right-click the selected records and select Query Cell Status from the shortcut menu.
End of Steps
5.15.2 Blocking a Cell

This procedure describes how to block a cell. Before cell maintenance, you can perform
this operation to block the corresponding cells.
Steps
5-18
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Block Cell from the shortcut menu. A
dialog box is displayed, see Figure 5-2.
Figure 5-2 Blocking Cells

Operation
Result
Click Force Block.
The cell is blocked and the service is released.
Click Switch Off Block.
The cell is blocked after the service is handed

over to other cells.
Click Release Block.
The cell is actually blocked after there is no

service in the cell.
End of Steps
5.15.3 Unblocking a Cell

This procedure describes how to unblock a cell. After the cell maintenance is completed,
you can perform this operation to unblock the corresponding cells.
Steps
3. Right-click the selected records and select Unblock Cell from the shortcut menu.
End of Steps
5-19
SJ-20140527134643-021|2014-07-28(R1.0)
5.15.4 Querying the Slave Information of PS Cells

When a failure occurs in multiple cells, this operation can be performed to check whether
these faulty cells correspond to the same DSP.
Steps
3. Right-click the selected records and select Query Slave of PS Cells from the shortcut
menu.
End of Steps
5.15.5 Changing Cells to the Specified Slave

If the binding of cells is unbalanced or too many cells are bound to a DSP, you can perform
this operation to adjust the binding relationships of cells, for example, bind one or more
cells to another DSP.
Steps
2. Select a record.
3. Right-click the selected record and select Change Cell To Slave. A message is
displayed, prompting you to confirm this operation.
4. Click Yes. The Change Cell To Slave dialog box is displayed.
5. Select a slave and click Confirm.
End of Steps
5.15.6 Adjusting Cell Load of Global PCU Resources

If the global binding of cells is not balanced due to a certain reason (such as DSP status),
this operation can be performed to adjust the binding relationships between all DSPs of
the BSC and cells to achieve equalized number of cells bound to each DSP.
Steps
2. Select a record.
5-20
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select Cell Load Adjustment of PCU Resources
in Global from the shortcut menu.
End of Steps
5.15.7 Adjusting RUP Slave Load Balance in PLMN

If the global binding of cells belonging to an operator is not balanced due to a certain reason
(such as DSP status), this operation can be performed to adjust the binding relationships
between all DSPs (belonging to the operator) of the BSC and cells to achieve equalized
number of cells bound to each DSP.
Steps
2. Select a record.
3. Right-click the selected record and select Adjust RUP Slave in PLMN from the
shortcut menu.
4. Select the corresponding MCC and MNC of the operator.
5. Click OK.
End of Steps
5.15.8 Querying Channel Statistics in a Cell

This operation can be used to query the statistical information of radio channels in a cell
when a radio resource failure occurs in the cell.
Steps
2. Select a record.
3. Right-click the selected record and select Query Channel Statistics in Cell from the
shortcut menu.
End of Steps
5.15.9 Querying the Channel Information in a Cell

This procedure describes how to query the usage of channels in a cell.
Steps
5-21
SJ-20140527134643-021|2014-07-28(R1.0)
2. Select a record.
3. Right-click the selected record and select Cell Channel Information Query from the
shortcut menu. A dialog box is displayed, containing the query results.
End of Steps
5.15.10 Querying the Power of All BCCHs in a Cell

This operation can be performed to query the power of all BCCHs in a cell when MSs in
the cell fails to connect the network or the signal quality is poor in the cell.
Steps
2. Select a record.
3. Right-click the selected record and select Query Cell BCCH Power.
End of Steps
5.15.11 Querying the Relationship Between TRX and RRU

During routine maintenance and inspection of the system or when a TRX fails, you can
perform this operation to query the information of the RRU corresponding to the TRX and
check whether the RRU is faulty.
Steps
2. Select a record.
3. Right-click the selected record and select Query Relationship Between TRX and
RRU from the shortcut menu. A dialog box is displayed, containing the query results.
End of Steps
5.15.12 Querying Uplink Interference Band in Real Time

During the troubleshooting of service failure, this operation can be performed to query the
level of the real-time uplink interference band in a TRX or a cell.
Steps
2. Select a record.
5-22
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected record and select Query Up Inter Band from the shortcut
menu. A dialog box is displayed, containing the query results.
End of Steps
5.15.13 Querying the BA List

This procedure describes how to query frequency information when the BA is enabled.
Steps
2. Select a record.
3. Right-click the selected record and select Query BAList from the shortcut menu.
End of Steps
5.15.14 Querying Dynamic TRXs

When frequency conflict occurs or a TRX fails, this operation can be performed to query
the information of dynamic TRXs in a specific cell.
Steps
2. Select a record.
3. Right-click the selected record and select Dynamic Trx Query from the shortcut menu.
A dialog box is displayed, containing the query results.
End of Steps
5.15.15 Querying the IFTA Information in a Cell

This procedure describes how to query the IFTA information and carrier-to-interference
ratio in a cell.
Steps
2. Select a record.
3. Right-click the selected record and select IFTA Cell Query from the shortcut menu. A
dialog box is displayed, containing the query results.
End of Steps
5-23
SJ-20140527134643-021|2014-07-28(R1.0)
5.15.16 Querying IFTA Historical Interference

This procedure describes how to query the distribution of recorded levels of neighbor cells,
which can be used to evaluate the interference.
Steps
2. Select a record.
3. Right-click the selected record and select IFTA Cell History Query from the shortcut
menu. A dialog box is displayed, containing the query results.
End of Steps
5.16 Frequency
5.16.1 Querying the Status of a TRX
This procedure describes how to query the status of a TRX, which indicates whether the
TRX is operating properly.
Steps
> TRX. The TRX tab is displayed.
3. Right-click the selected records and select Query TRX Status from the shortcut menu.
End of Steps
5.16.2 Blocking an FU TRX

This operation can be performed to block an FU TRX during the troubleshooting of the FU
TRX.
Caution!
Do not block an FU TRX unless absolutely necessary. Resetting an FU TRX can result in
service failure.
Steps
5-24
SJ-20140527134643-021|2014-07-28(R1.0)

3. Right-click the selected records and select Block FU TRX from the shortcut menu.
Operation
Result
Click Force Block.
The FU is blocked and the service is released.
The FU is blocked after the service is switched to

other carriers.
The FU is actually blocked after there is no

service.
End of Steps
5.16.3 Unblocking an FU TRX

After the troubleshooting of an FU TRX is finished, this operation can be performed to
unblock the FU TRX and recover the corresponding service.
Steps
3. Right-click the selected records and select Unblock FU TRX from the shortcut menu.
End of Steps
5.16.4 Blocking a CU TRX

This operation can be performed to block a CU TRX during the troubleshooting of the CU
TRX.
Caution!
Do not block a CU TRX unless absolutely necessary. Resetting a CU TRX can result in
service failure.
Steps
5-25
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Block CU TRX from the shortcut menu.
Operation
Result
Click Force Block.
The CU (carrier unit) is blocked and the service

is released.
The CU is blocked after the service is switched to

other carriers.
The CU is actually blocked after there is no

service.
End of Steps
5.16.5 Unblocking a CU TRX

After the troubleshooting of a CU TRX is finished, this operation can be performed to
unblock the CU TRX and recover the corresponding service.
Steps
3. Right-click the selected records and select Unblock CU TRX from the shortcut menu.
End of Steps
5.16.6 Querying the Relationship Between TRX and RRU

During routine maintenance and inspection of the system or when a TRX fails, you can
perform this operation to query the information of the RRU corresponding to the TRX and
check whether the RRU is faulty.
Steps
2. Select a record.
3. Right-click the selected record and select Query Relationship Between TRX and
RRU from the shortcut menu.
End of Steps
5-26
SJ-20140527134643-021|2014-07-28(R1.0)
5.16.7 Querying Uplink Interference Band in Real Time

During the troubleshooting of service failure, this operation can be performed to query the
level of the real-time uplink interference band in a TRX or a cell.
Steps
2. Select a record.
3. Right-click the selected record and select Query Up Inter Band from the shortcut
menu.
End of Steps
5.17 Timeslot
5.17.1 Querying the Status of a Timeslot
When a common transport channel setup failure alarm occurs or a cell access indicator
has an unexpected value, this operation can be performed to query the status of the
corresponding channel.
Steps
> TS. The TS tab is displayed.
2. Select a record.
3. Right-click the selected record and select Query TS Status from the shortcut menu.
End of Steps
5.17.2 Querying the Statuses of All Radio Channels

This functions can be used to query the statuses of all radio channels of a TRX if a failure
occurs in the radio resources of the TRX.
Steps
2. Select a record.
3. Right-click the selected record and select Query TS Channel Status from the shortcut
menu.
End of Steps
5-27
SJ-20140527134643-021|2014-07-28(R1.0)
5.17.3 Blocking a Timeslot

You can use this function to block the corresponding timeslot when a channel fails. It
prevents the failed channel from affecting the network quality.
Steps
2. Select a record.
3. Right-click the selected record and select Block TS from the shortcut menu.
Operation
Result
Click Force Block.
The TS is blocked and the service is released.
The TS is blocked after the service is switched to

other carriers.
The TS is actually blocked after there is no

service.
5. Click OK.
End of Steps
5.17.4 Unblocking a Timeslot

You can use this function to unblock the corresponding timeslot when a channel failure is
resolved. After the timeslot is unblocked, the channel resumes operation.
Steps
2. Select a record.
3. Right-click the selected record and select Unblock TS from the shortcut menu.
End of Steps
5.17.5 Performing a Forcible Handover

This procedure describes how to perform a forcible outgoing handover of the service on a
channel.
5-28
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
2. Select a record.
3. Right-click the selected record and select Force Handover TS from the shortcut menu.
4. Select a handover type and fill in the site ID and BTS ID.
5. Click OK. A message is displayed, indicating the handover result.
6. Click OK.
End of Steps
5.17.6 Querying Connection Status by Timeslot

This function is used to query the information of resources occupied by services in a
timeslot of a TRX.
Steps
3. Right-click the selected records and select Query Connect Status by TS from the
shortcut menu. A message is displayed, indicating the query results.
4. Click OK.
End of Steps
5.17.7 Querying Connection Status by IMSI

This procedure describes how to query the NE resources occupied by services
corresponding to the specified IMSI.
Steps
3. Right-click the selected records and select Query Connect by IMSI from the shortcut
menu.
4. Enter the required IMSI.
5. Click OK. A message is displayed, indicating the query results.
6. Click OK.
End of Steps
5-29
SJ-20140527134643-021|2014-07-28(R1.0)
5.17.8 Querying Connection Status by IMEI

This procedure describes how to query the NE resources occupied by services
corresponding to the specified IMEI.
Steps
3. Right-click the selected records and select Query Connect by IMEI from the shortcut
menu.
4. Enter the required IMEI.
5. Click OK. A message is displayed, indicating the query results.
6. Click OK.
End of Steps
5.17.9 Monitoring the Status of a Channel

This operation can be performed when you need to observe a channel and check whether
the channel is operating properly.
Steps
2. Select a record.
3. Right-click the selected record and select SPY TRX from the shortcut menu.
End of Steps
5.17.10 Stopping the Channel Monitoring

This procedure describes how to stop the monitoring on a channel.
Steps
2. Select a record.
3. Right-click the selected record and select STP TRXSPY from the shortcut menu.
End of Steps
5-30
SJ-20140527134643-021|2014-07-28(R1.0)
5.18 GSM Module

5.18.1 Querying Channel Statistics in a Module
If the CPU load of a CMP module is high, this function can be used to query the channel
statistics in the CMP module and check whether too many radio channels are configured
in this module.
This function can also be used to query the statistics of radio channels in the CMP if a
failure occurs in the radio resources.
Steps
> GMODULE. The GMODULE tab is displayed.
3. Right-click the selected records and select Query Channel Statistics in Module from
the shortcut menu.
End of Steps
5.18.2 Stopping Flow Control

If a PCM timeslot at the A interface fails, you can use this function to reset the timeslot.
Steps
3. Right-click the selected records and select Stop Flow Control from the shortcut menu.
A message is displayed, prompting you to confirm this operation.
4. Click Yes.
End of Steps
5.18.3 Querying the Information of IFTA External Cells

This function is used to query the IFTA channel information of the other modules and other
neighbor cells managed by the BSC.
Steps
5-31
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select IFTA Outside Cell Query from the shortcut
menu.
4. Enter the information about the cells and click OK.
End of Steps
5.19 BVC
5.19.1 Querying the Status of a BVC
This functions can be used to query the status of a BVC during routine maintenance and
inspection of the system or when a BVC PS service fails.
Steps
> BVC. The BVC tab is displayed.
3. Right-click the selected records and select Query BVC Status from the shortcut menu.
End of Steps
5.19.2 Blocking a BVC

If a BVC fault occurs (such as high call drop ratio), you can use this function to block the
BVC.
Steps
3. Right-click the selected records and select Block BVC from the shortcut menu.
End of Steps
5.19.3 Unblocking a BVC

If the fault of aBVC is resolved, this function can be used to unblock the BVC.
Steps
5-32
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Unblock BVC from the shortcut menu.
End of Steps
5.19.4 Resetting a BVC

When a BVC is connected to the network, you can use this function to reset the BVC. After
that, the BVC status is synchronized to the CN.
Steps
3. Right-click the selected records and select Reset BVC from the shortcut menu.
End of Steps
5.19.5 Performing Signaling Reset for BVCs

When multiple BVCs are connected to the network, you can use this function to
synchronize the statuses of all BVCs of the BSC to the CN.
Steps
3. Right-click the selected records and select Signalling Reset BVC from the shortcut
menu.
End of Steps
5.20 ABIS
5.20.1 Querying Timeslot Status at the Abis Interface
If Abis resources are unavailable, this operation can be performed to query the statuses
of resources at the Abis interface, including PCM, DSPs, and subslots.
Steps
> ABIS. The ABIS tab is displayed.
5-33
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Query ABIS Status from the shortcut
menu.
End of Steps
5.20.2 Blocking a Timeslot at the Abis Interface

If subslots at the Abis interface are maintained or a subslot fault occurs, you can perform
this operation to block the corresponding timeslot.
Steps
3. Right-click the selected records and select BLOCK ABIS from the shortcut menu.
Operation
Result
Click Block and Release.
The timeslot at the Abis interface is blocked and

the corresponding service is released.
Click Block and No Release.
The timeslot at the Abis interface is blocked and

the corresponding service is not released.
End of Steps
5.20.3 Unblocking a Timeslot at the Abis Interface

After the maintenance of subslots at the Abis interface is completed or the subslot fault is
resolved, this operation can be performed to unblock the corresponding timeslot.
Steps
2. Select one or morel records.
3. Right-click the selected records and select UNBLOCK ABIS from the shortcut menu.
End of Steps
5.20.4 Starting Timeslot Monitoring at the Abis Interface

If continuous observation of a channel is required, this operation can be performed to start
the monitoring on the corresponding timeslot at the Abis interface.
5-34
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select SPY ABISRS from the shortcut menu.
End of Steps
5.20.5 Stopping Timeslot Monitoring at the Abis Interface

This procedure describes how to stop the monitoring on a timeslot at the Abis interface.
Steps
3. Right-click the selected records and select STP ABISRS from the shortcut menu.
End of Steps
5.21 Querying Timeslot Usage at the Abis Interface

This procedure describes how to query the usage of timeslots at the Abis interface and
check whether the timeslots are operating properly with normal statuses.
Steps
> ABISUSE. The ABISUSE tab is displayed.
3. Right-click the selected records and select Query ABIS Usage from the shortcut
menu.
End of Steps
5.22 Querying Device Status at the Abis Interface

If a site or cell is unavailable, this operation can be performed to query the status of the
LAPD link between the site and the BSC.
Steps
> ABIS Device. The ABIS Device tab is displayed.
5-35
SJ-20140527134643-021|2014-07-28(R1.0)
3. Right-click the selected records and select Query ABIS Device Status from the
shortcut menu.
End of Steps
5.23 Site
5.23.1 Querying the Relationships Between RRUs and TRXs
During routine maintenance and inspection of the system, you can perform this operation
to query the relationships between each RRU and TRXs of a site.
This function is only applicable to an SDR site.
Prerequisite
The SDR site is operating properly.
Steps
> GSITE. The GSITE tab is displayed.
3. Right-click the selected records and select Query Relation Between RRU and TRX
from the shortcut menu.
End of Steps
5.23.2 Resetting a Site

If a site needs to be reset during troubleshooting or maintenance, you can perform this
operation to reset the boards in the site.
This function is only applicable to a non-SDR site.
Warning!
Do not reset a site unless absolutely necessary.
interruption.
Resetting a site results in service
Prerequisite
The non-SDR site to be reset is operating properly.
5-36
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select Reset Site from the shortcut menu.
End of Steps
5.23.3 Querying E1 PPP Transmission Status

This operation can be performed to query the E1 PPP transmission status and check
whether the PPP transmission is normal.
Steps
3. Right-click the selected records and select E1 PPP Transmission Status Query from
the shortcut menu.
End of Steps
5.23.4 Querying the Association Status of a Site

This operation can be performed to query the association status of a site and check whether
all associations of the site are normal.
Steps
3. Right-click the selected records and select Site Assoc Status Query from the shortcut
menu.
End of Steps
5.23.5 Querying Transmission Performance of PPP Links

This procedure describes how to query the transmitted and received data on PPP links
of a site and obtain the traffic statistics on the links, which can be used to analyze the
transmission quality.
5-37
SJ-20140527134643-021|2014-07-28(R1.0)
Steps
3. Right-click the selected records and select Query PPP link transmission
performance data from the shortcut menu.
End of Steps
5.24 Resetting a Rack

If a rack on a site needs to be reset during troubleshooting or maintenance, you can perform
this operation to reset the rack.
Warning!
Do not reset a rack unless absolutely necessary. Resetting a rack results in service
interruption on the site.
Steps
> Site Rack List. The Site Rack List tab is displayed.
2. Select a record.
3. Right-click the selected record and select Reset site rack from the shortcut menu.
End of Steps
5.25 Querying Ring Network Status

If a fault occurs in the ring network of base stations (such as LAPD link failure), you can
perform this operation to query the status of the ring network and locate the faulty base
station.
Steps
> RING. The RING tab is displayed.
3. Right-click the selected records and select Ring Network Status Query from the
shortcut menu.
End of Steps
5-38
SJ-20140527134643-021|2014-07-28(R1.0)
Figures
Figure 2-1 Expanding the Configuration Resource Tree ............................................ 2-2
Figure 2-2 Controller Rack Tab ................................................................................. 2-2
Figure 2-3 LED Status Query Dialog Box .................................................................. 2-4
Figure 2-4 Memory Information Query Dialog Box..................................................... 2-5
Figure 2-5 Querying RNC state................................................................................. 2-5
Figure 2-6 Querying IMSI Local Switch ..................................................................... 2-6
Figure 2-7 NTP Time Operation Dialog Box .............................................................. 2-6
Figure 3-1 Controller Rack Tab ................................................................................. 3-1
Figure 3-2 Selecting a Clock Base ............................................................................ 3-6
Figure 3-3 APS Exchange Request Dialog Box......................................................... 3-7
Figure 3-4 Sunit Loop ............................................................................................. 3-18
Figure 3-5 Timeslot of sunit loop ............................................................................. 3-19
Figure 4-1 Blocking or Unblocking a Local SCCP Subsystem ................................. 4-14
Figure 4-2 Querying Interfaces in RPU ................................................................... 4-17
Figure 4-3 To Query Port Channel ARP Dialog Box ................................................ 4-19
Figure 4-4 To Query SuperVLAN Interface ARP Dialog Box.................................... 4-19
Figure 4-5 Entering Channel Group No. .................................................................. 4-20
Figure 4-6 Querying All ACL4 Tables ...................................................................... 4-28
Figure 5-1 Adjust Cells in Slave Dialog Box ............................................................ 5-14
Figure 5-2 Blocking Cells ........................................................................................ 5-19
I
SJ-20140527134643-021|2014-07-28(R1.0)
Figures
II
SJ-20140527134643-021|2014-07-28(R1.0)
Glossary
2G
- The 2nd Generation Mobile Communications
3GPP
- 3rd Generation Partnership Project
APS
- Automatic Protection Switching
ARP
- Address Resolution Protocol
ATM
- Asynchronous Transfer Mode
Abis
- Abis Interface between BSC and BTS
BCCH
- Broadcast Control Channel
BSC
- Base Station Controller
BTS
- Base Transceiver Station
BVC
- BSSGP Virtual Connection
CMP
- Calling Main Processor
CN
- Core Network
CPU
- Central Processing Unit
DSP
- Digital Signal Processing
ECMM
- ETCA Chassis Management Module
EGBS
- ETCA GE Base Switch
EGFS
- ETCA GE Fabric Switch
III
SJ-20140527134643-021|2014-07-28(R1.0)
EMS
- Element Management System
FU
- Frame Unit
GERAN
- GSM/EDGE Radio Access Network
GSM
- Global System for Mobile Communications
GUI
- Graphical User Interface
IFTA
- Intelligent Frequency Timeslot Allocation
IMEI
- International Mobile Equipment Identity
IMSI
- International Mobile Subscriber Identity
IP
- Internet Protocol
IPD
- ICMP Path Detection
LAPD
- Link Access Procedure for D-channel
LED
- Light Emitting Diode
MAC
- Media Access Control
MCC
- Mobile Country Code
MNC
- Mobile Network Code
MSC
- Mobile Switching Center
MTP2
- Message Transfer Part layer 2
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
IV
SJ-20140527134643-021|2014-07-28(R1.0)
Glossary
NTP
- Network Time Protocol
OMM
- Operation & Maintenance Module
OMP
- Operation & maintenance Main Processor
PCM
- Pulse Code Modulation
PMTU
- Path Maximum Transmission Unit
PPP
- Point-to-Point Protocol
PS
- Packet Switched
RNC
- Radio Network Controller
RPU
- Route Process Unit
RRU
- Remote Radio Unit
SCCP
- Signaling Connection Control Part
SDR
- Software Defined Radio
SGSN
- Serving GPRS Support Node
TDM
- Time Division Multiplexing
TRX
- Transceiver
V
SJ-20140527134643-021|2014-07-28(R1.0)

SJ-20140527134643-021-ZXUR 9000 GSM (V6.50.202) Status Management Operation Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SJ-20140527134643-021-ZXUR 9000 GSM (V6.50.202) Status Management Operation Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

ZXUR 9000 GSM

Base Station Controller

Status Management Operation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

The content has been updated (V6.50.202)

Serial Number: SJ-20140527134643-021

ZTE Proprietary and Confidential

Chapter 3 Physical Resources .................................................................. 3-1

ZTE Proprietary and Confidential

3.3.13 Querying the CPU Frequency of a Board ................................................. 3-9

Chapter 4 Transmission Resources ......................................................... 4-1

ZTE Proprietary and Confidential

4.1 Association ........................................................................................................ 4-1

ZTE Proprietary and Confidential

4.7.2 Querying the Status of a Local SCCP Subsystem..................................... 4-14

ZTE Proprietary and Confidential

4.14.1 Querying All ACL4 Tables ..................................................................... 4-27

Chapter 5 GSM Radio Resources ............................................................. 5-1

ZTE Proprietary and Confidential

5.4.4 Equipping a PCM Link at the Virtual A Interface.......................................... 5-8

ZTE Proprietary and Confidential

5.14.2 Re-configuring an NSE in Full Mode ...................................................... 5-17

ZTE Proprietary and Confidential

5.17.9 Monitoring the Status of a Channel ........................................................ 5-30

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Provides an overview of status management.

Describes the GUI for status management and common

status management operations.

Chapter 3, Physical Resources

Describes the status management operations on physical

Chapter 4, Transmission Resources

Describes the status management operations on

Chapter 5, GSM Radio Resources

Describes the status management operations on the GSM

ZTE Proprietary and Confidential

Warning: indicates a potentially hazardous situation. Failure to comply can result in

ZTE Proprietary and Confidential

Queries on dynamic data: are implemented in man-machine interactive mode to

Status management is a multi-aspect and multi-module function that involves database

ZTE Proprietary and Confidential

ZXUR 9000 GSM Status Management Operation Guide

This page intentionally left blank.

ZTE Proprietary and Confidential

Common Status Management

2.1 Opening the Status Management Tab

You have logged in to the EMS client.

ZTE Proprietary and Confidential

ZXUR 9000 GSM Status Management Operation Guide

Figure 2-1 Expanding the Configuration Resource Tree

3. Double-click an object in the navigation tree. The corresponding management tab is

4. Select a record and perform an appropriate operation on the corresponding object as

ZTE Proprietary and Confidential

Chapter 2 Common Status Management Operations

2.2 Basic Operations

3. On the tool bar of the managed object tab, click

2.2.2 Querying LED Status

. The LED status query dialog box is displayed.

2. Select the query type (

ZTE Proprietary and Confidential

ZXUR 9000 GSM Status Management Operation Guide

Figure 2-3 LED Status Query Dialog Box