bsc mmi commands

68P81132E13-OECCN 5E992

BASE SITE CONTROLLER (BSC)

BSC MMI COMMANDS

System Release R9.8

General Release

COPYRIGHT

Copyright © 2002 Motorola, Inc. All Rights ReservedThis manual may not be reproduced, in whole or in part, in any form whatsoever, without the express written permission ofMotorola, Inc.

NOTICE

The Motorola products described in this manual contain one or more computer programs. The use of these computer programsis governed by the terms and conditions of a corresponding license agreement with Motorola, Inc. In addition, these computerprograms are protected by copyright law and international treaties. Unauthorized reproduction, modification, or distribution ofthese programs, or any part thereof, may result in severe civil and criminal penalties, and will be prosecuted to the maximumextent possible under the law. U.S. and international patents pending.

TRADEMARKS

,

Motorola, and iDEN are trademarks or registered trademarks of Motorola, Inc. in the United States and other countries.

Sun, Sun Microsystems, the Sun Logo, Ultra, and Ultra Enterprise are trademarks or registered trademarks of Sun Microsystems,Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registeredtrademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are basedupon an architecture developed by Sun Microsystems, Inc.

UNIX is a trademark of Novell, Inc. in the United States and other countries.

Open Software Foundation, OSF and Motif are trademarks of Open Software Foundation, Inc. in the United States and othercountries.

X Window System is a trademark of the Massachusetts Institute of Technology in the United States and other countries.

Brio is a registered trademark and BrioQuery is a trademark of Brio Technology, Inc.

LIABILITY

While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resultingfrom any omissions in this document, or from use of the information obtained herein. The information in this document hasbeen carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies. Motorola,Inc. reserves the right to make changes to any products described herein to improve reliability, function, or design, and reservesthe right to revise this document and to make changes from time to time in content hereof with no obligation to notify any personof revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product or circuitdescribed herein; neither does it convey license under its patent rights or the rights of others.

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE

Contents

About This Manual I-1

Chapter 1 Introduction 1-1

Chapter 2 Configuration management 2-1

Chapter 3 Device management 3-1

Chapter 4 Display 4-1

Chapter 5 Fault management 5-1

Chapter 6 Statistics 6-1

Chapter 7 Call trace 7-1

Chapter 8 Miscellaneous 8-1

Appendix A Non-statistical parameters A-1

Appendix B Statistical parameters B-1

Appendix C Device and function definitions C-1

68P81132E13-O

10/3/02GR

i

C

ONTENTS

BSC MMI Commands

This page intentionally left blank.

ii 68P81132E13-O

10/3/02GR

About This Manual

chapter contents

Purpose of Manual

Target Audience

Related Manuals

Organization of this Manual

Documentation Conventions Used in this Manual

Error and Concerns Reporting

This manual describes the Base Site Controller (BSC) MMI

NOTICE

Commands for System Software Release R9.8.

2

2

2

3

4

4

Global Telecom Solutions Sector1301 E. Algonquin Road, Schaumburg, IL 6019668P81132E13-O

10/3/02-GR

I-1

BSC MMI Commands

Purpose of Manual

This manual serves as a reference manual for the MMI commands available to the service technician or installer for control and communications of the iDEN Base Site Controller (BSC). These commands are responsible for the following specific tasks:

• Initialization

• Configuration Management

• Device Management

• Fault Management

• Statistics

• Call Processing

68P81132E13-O

10/3/02-GR

I-2

BSC MMI Commands

Target Audience

The information in this manual is intended for use by the BSC craftsperson(s) in the installation and maintenance of the iDEN Base Site Controller (BSC).

It is assumed that the user of this information has a general understanding of telephony, as used in the operation of the Public Switched Telephone Network (PSTN), and is familiar with these concepts as they are applied in the iDEN Communications System. The user, however, is not expected to have any detailed technical knowledge of the internal operation of the equipment.

68P81132E13-O

10/3/02-GR

I-3

BSC MMI Commands

Related Manuals

The following manuals may be required to supplement the information contained in this manual:

• iDEN Base Site Controller (BSC) Service Manual — 68P81090E70-D

68P81132E13-O

10/3/02-GR

I-4

BSC MMI Commands

Organization of this Manual

This manual is organized as a reference manual for the BSC MMI Commands. The commands are grouped by function (e.g., Configuration Management, Display, etc.) and are separated by tabs corresponding to the function. The following listing describes the major sections of this manual. Also, refer to Chapter 1 Introduction for a detailed explanation of how the commands are presented in this manual.

Chapter Function Description

1 N/AExplains what MMI commands are and the format used to present the command syntax in this manual.

2Configuration Management Commands

Describes commands used to configure the system database. This includes commands used before and after SYSGEN.

3Device

Management Commands

Describes commands used to configure various devices within the system.

4Display

Commands

Describes commands used to display specific information. This provides a method to view the contents of the CM database.

5Fault

Management Commands

Describes commands used to interpret faults.

6Statitics

CommandsDescribes commands used for statistical purposes.

7Call Trace

CommandsDescribes commands relating to monitoring call processing.

8Miscellaneous

CommandsDescribes utility commands for use by the MMI command user.

Appendix A N/AProvides a listing of functional definitions for all non-statistical parameters used to configure the BSC system.

Appendix B N/AProvides a listing of functional definitions for all statistical parameters used to configure the BSC system.

Appendix C N/ADescribes the usage of all devices and functions used with the MMI commands.

68P81132E13-O

10/3/02-GR

I-5

BSC MMI Commands

Documentation Conventions Used in this Manual

The following typographic conventions are used in this manual to present computer terminal input and output and/or UNIX terminology:

UNIX Conventions

• Boldface sans serif characters are used in descriptive text to represent path names or commands.

• Regular sans serif characters are used to indicate files.

• <italic> characters enclosed in <> are used to indicate a token for part of a path name.

68P81132E13-O

10/3/02-GR

I-6

BSC MMI Commands

Error and Concerns Reporting

Any errors or concerns about this manual or its contents should be reported via the survey form provided at the beginning of this manual. Please be sure to add your name and phone number so we can follow up with you.

68P81132E13-O

10/3/02-GR

I-7

BSC MMI Commands

68P81132E13-O

10/3/02-GR

I-8

1

1 Introduction

MMI commands

Man-Machine Interface commands are used for communication between the service technician or installer, and the Base Site Controller (BSC).

In the BSC, MMI commands are responsible for these specific tasks:❐ initialization process❐ on-line configuration change❐ configuration management❐ device management❐ fault management❐ statistics❐ call processing

Initialization process

During the Initialization Process (IP), also known as SYSGEN, code is loaded into the BSC from any one of these sources:

❐ GPROC❐ Operation and Maintenance Center (OMC)❐ TTY port (via service computer)

Code is typically loaded when the BSC is reset, existing code is damaged, or when a new version of code must be loaded.

On-line Configuration Change

On-line Configuration Change is used in order to change the BSC configuration without taking the BSC out-of-service. The script with new configuration is downloaded to the BSC with the use of a background download feature. The BSC configuration is changed by OMC-R commands.


10/3/02-GR

1-1

C

HAPTER

1 - I

NTRODUCTION

BSC MMI Commands

BSC system features

On-line Configuration Change

On-line Configuration Change (OLCC) is invoked by OMC-R commands. OLCC allows the user to change certain BSC parameters without taking the BSC out-of-service. Only commands located in the delta_only and delta_init sections of the configuration script are executed during OLCC.

The section type can be determined by special MMI commands.

During OLCC the BSC parses the configuration script twice.

In the first pass, the BSC executes:❐ the commands which delete resources❐ certain change commands that are executed as corresponding

delete commands

All transactions using the deleted resources will be dropped. Other commands are skipped during this pass.

In the second pass, the BSC executes the commands which either add or change resources. Some change commands are executed as corresponding add commands.

Configuration management

After SYSGEN, MMI commands are used to configure, modify, or display the Configuration Management (CM) database. Not all areas can be modified after SYSGEN.

Device management

In addition, MMI commands may be used to configure, modify, or display the administrative state of various devices and functions.

Information display

Some MMI commands allow you to display specific information about the CM database and other BSC data.

68P81132E13-O

10/3/02-GR

1-2

BSC MMI Commands C

HAPTER

1 - I

NTRODUCTION

Fault management

MMI commands provide useful tools for Fault Management (FM). By configuring the system to monitor specific functions or devices, you may control:

❐ what alarms to report❐ how alarms are reported❐ when alarms are reported

Statistics

Statistical MMI commands provide information about the system. Statistics can be enabled for display or modification of specific cells or devices.

Call tracing

Call trace MMI commands provide a window to the system, allowing the user to monitor or debug specific system operations.

Miscellaneous

Miscellaneous MMI commands are available to the user that provide system utility functions.

68P81132E13-O

10/3/02-GR

1-3

C

HAPTER

1 - I

NTRODUCTION

BSC MMI Commands

Other features

Security management

The BSC implements a three level security management system for strict access control. Each level (1, 2, or 3) is accessed through means of a unique password. This helps ensure only authorized persons are permitted to access, configure, or monitor the system. The security levels are defined as:

Password changes

Passwords may only be changed by users that have a security level of 2 or higher; passwords may not be changed at level 1. Password changes may only be accomplished through the use of the chg_password command.

Security level changes

Authorized users are permitted to change security levels, once in the system, by entering the appropriate password. Security level changes may only be accomplished through the use of the chg_level command.

Level 1 A limited set of basic commands are available to the user, relating mainly to system monitoring capabilities. At this level, users are not permitted to change the security level password.

Level 2 All commands are available to the user, permitting system monitoring and system administration capabilities. This level allows passwords for security levels 1 and 2 to be changed.

Level 3 This level permits access to the same set of commands as security level 2. In addition, users may use the executive monitor to view system diagnostic messages.

68P81132E13-O

10/3/02-GR

1-4

BSC MMI Commands CHAPTER 1 - INTRODUCTION

Command classifications

Various database fields may be affected whenever MMI commands are executed. The types of fields affected are largely dependent on the command classification. Each command’s classification is shown in its description.

SYSGEN This command is only available during system initialization (SYSGEN). SYSGEN commands are used in the configuration script.

RC This command is only available after system initialization (Recent Change).

SYSGEN/RC This command is available both during and after system initialization, but can not be used in OLCC.

OLCC This command is available only during OLCC. OLCC commands are used in the configuration script.

SYSGEN/OLCC This command is available only during the system initialization (SYSGEN) or during On-line Configuration Change (OLCC). SYSGEN/OLCC commands are used in the configuration script.

SYSGEN/RC/OLCC This command is available during and after the system initialization and during OLCC.

68P81132E13-O

10/3/02-GR

1-5

CHAPTER 1 - INTRODUCTION BSC MMI Commands

Typical reference page

The information for each command appearing in this document is presented in a similar manner. The following pages describe the typical format for a command.

68P81132E13-O

10/3/02-GR

1-6


Description

Descriptive text

Each command appearing in this manual contains a brief description. This allows you to quickly flip through the pages to read and understand the function of any MMI command.

Quick-reference table

Immediately following the description is a table that defines the basic features of the command, such as:

❐ availability❐ security level❐ classification❐ related commands

The table below shows an example of a quick-reference table for the chg_level command. The features appearing in this table are described in the text immediately following this example table.

Availability

Availability refers to location from which the command may be executed. This may include the BSC, Enhanced BSC (E-BSC), remote transcoder (RXCDR), and/or Enhanced remote transcoder (E-RXCDR).

Availability BSC RXCDR E-BSC E-RXCDR

✔ ✔ ✔ ✔

Security level level 2

Classification SYSGEN/RC

Related commands disp_level on page 4-62

68P81132E13-O

10/3/02-GR

1-7


Security level

This entry shows the required security level the user must enter to access this command. This is an indication of the minimum level required to access the command. The security levels were defined earlier in this chapter.

If the desired command is available only at a higher security level, users may change security levels to access that command. Although, this assumes the user knows the appropriate password and is authorized to use it.

Classification

The command classification is determined by the availability of the command. This includes pre-SYSGEN and/or post-SYSGEN (recent change).

Related commands

Any commands that display, affect, or modify the conditions of the command described are listed here. Included in the reference is the page number for quick-reference. When there are no related commands, it is noted accordingly.

68P81132E13-O

10/3/02-GR

1-8


Format

The command format, or syntax, is presented for each command. Note the requirements described below relating to command format.

Command keywords

Command keyword strings appear in bold-faced characters. Compound keywords are separated with an underscore (_) and must be typed exactly as they appear within this document.

EXAMPLE: disp_channel

Case sensitive

The format of all MMI commands is case-sensitive. They must be typed in lowercase; exactly as they appear within this document.

Exceptions to this requirement include device names, function names, and statistical parameter names with specific commands (clear_stats/disp_stats). These must be entered in uppercase.

EXAMPLE: disp_device <DEVICE> <device_id1>

68P81132E13-O

10/3/02-GR

1-9


Parameters

Most commands require the entry of parameters that alter or further define the definition of the command. Note the requirements described below relating to parameters.

Parameter conventions

Parameters are presented in italics. When multiple parameters are presented, they are separated by spaces.

Required parameters

Required parameters are enclosed in angle brackets <>.

EXAMPLE: command <parameter>

“Or” parameters

Some commands allow you to choose between one or more parameters. In these cases, the selectable parameters are separated by by the pipe symbol |. Note that the choices are mutually exclusive (i.e., you may choose only one of the parameters, but not both). In the example below, you may choose either parameter_A or parameter_B, but not both.

EXAMPLE: command <parameter_A> | <parameter_B>

Optional parameters

Basic Usage

Optional parameters are enclosed in square brackets [ ].

EXAMPLE: command [param_1]

In the above example, the command may be issued alone or along with the optional param_1.

68P81132E13-O

10/3/02-GR

1-10


"Optionally Required" Parameters

In some cases, optional parameters are enclosed in both square brackets [ ] and angle brackets < >. The combination of square brackets and angle brackets creates a special usage relationship between the parameters.

Three examples follow to illustrate the combination usage of square and angle brackets.

EXAMPLE 1: command <param_1> [<param_2> <param_3> <param_4>]

In Example 1, param_1 is required and must always be entered. param_2, param_3, and param_4 comprise an optional parameter string (since they are enclosed within square brackets). However, since each parameter is also enclosed within angle brackets, if you wish to enter one of the parameters, you must also enter the other two (e.g., if you wish to enter param_3, then you must also enter param_2 and param_4).

EXAMPLE 2: command [<param_1>] [<param_2> <param_3> <param_4>]

In Example 2, param_1 is optional (now enclosed in square brackets) and param_2, param_3, and param_4 comprise an optional parameter string (also enclosed in square brackets). param_1 may be entered alone (optional) or it may be entered along with the optional parameter string (param_2, param_3, and param_4). As in Example 1, if you wish to enter any parameter in the string, you must enter all parameters in the string. Additionally, if you wish to enter the parameter string, you must also enter param_1 (since it is enclosed in square and angle brackets and is positioned to the left of the parameter string).

EXAMPLE 3: command [param_1] [<param_2> <param_3> <param_4>]

In Example 3, note that the angle brackets have been removed from param_1. This means that you may enter param_1 alone, the parameter string alone (param_2, param_3, and param_4), or param_1 and the parameter string together. The elimination of the angle brackets around param_1 removes the requirement of entering param_1 if you wish to enter the parameter string.

68P81132E13-O

10/3/02-GR

1-11


Elements

Some optional parameters may also include entries in angle brackets <>. This means that the entry is optional for some elements, but required by other elements.

EXAMPLE: command [<parameter_1>]

Optional parameters are actually required for the proper use of many of the commands (especially with generic commands like “chg_element”).

EXAMPLE: “cell_number”, “board_id”, index(es), group number (for devices, timeslots, etc.). Use of these parameters depends on the specific element name requirements and /or individual user needs.

Index numbers

Certain parameters require index numbers. The index number is entered along with the parameter/element name. Index numbers can be entered on a command line or in response to a prompt. For the following command example, the second parameter requires an index number:

EXAMPLE: command <parameter_1> [parameter_2]

In this example, the second parameter, which is optional, requires an index number. The user enters:

EXAMPLE: command 27 parameter_2, 5 34

An index number with a value of 5 is entered in this example, along with the second parameter. A comma separates the parameter name from the index number.

Entering numeric values

Numeric values may be entered with MMI commands in the following forms:

❐ binary❐ decimal❐ hexadecimal

68P81132E13-O

10/3/02-GR

1-12


Binary numbers consist of the digits 0 and 1 and must have a “b” or “B” at the end.

Decimal numbers consist of the digits 0-9.

Hexadecimal numbers consist of the digits 0-9 and A-F (upper or lower case) and must have an “h” or “H” at the end. Since all numbers must begin with a numeric character, hexadecimal values that start with A-F must be preceded by a “0”.

For example, if the value was FFh, the user must enter 0FFh (or 0ffh since uppercase is not required).

The maximum allowable ranges for numeric values are:

iDEN cell ID

The iDEN Cell ID uniquely identifies an iDEN cell in the iDEN system. The iDEN Cell ID is broken into the following seven parameters, or tokens:

EXAMPLE: <MCC digit 1> <MCC digit 2> <MCC digit 3> <MNC digit 1> <MNC digit 2> <LAC> <CI>

Where:

MCC = Mobile Country Code or geographic area codes.

MNC = Mobile Network Code assigned to the PLMN

LAC = Location Area Code

CI = Cell Identity

For the following command:

EXAMPLE: <parameter_1> <esmr_cell_id>

Binary 0b-11111111111111111111111111111111b

Decimal 0-4292967295

Hex 0h-0FFFFFFFFh

68P81132E13-O

10/3/02-GR

1-13


The iDEN Cell ID has the following values:

MCC=001

MNC=02

LAC=0003

CI=123

The user enters:

EXAMPLE: command 27 0 0 1 0 2 3 123

The first parameter, 27 is the value for <parameter _1>. The next seven parameters represent the gsm_cell_id. The value 0 is MCC digit 1. The value 2 is MNC digit 2. The LAC is 3. The CI is 123.

68P81132E13-O

10/3/02-GR

1-14


Examples

Provides at least one example of the command entry and system response.

Entry

A typical example, using selected variables, appears. This gives the reader an understanding of typical command usage.

EXAMPLE: add_channel 0 1 0 0 0 1 1 5

Response

Most commands have the following response when successfully executed:

COMMAND ACCEPTED

If a command returns a more detailed response than “COMMAND

ACCEPTED,” it is noted accordingly. Many display commands may not print this response.

68P81132E13-O

10/3/02-GR

1-15


Alphabetical Listing of Commands

add_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2add_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4add_cic_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6add_circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2add_ebts_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9add_span_nail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11add_span_nailpipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13add_xbl_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2auto_vp_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2bsc_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3cage_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4chg_audit_sched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6chg_cell_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17chg_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19chg_channel_olcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21chg_cic_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23chg_cic_conn_olcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25chg_circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4chg_circuit_olcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5chg_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27chg_ebts_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29chg_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31chg_esmr_olcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43chg_ksw_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45chg_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46chg_msi_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47chg_omc_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48chg_password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50chg_subrate_olcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51chg_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54clear_database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56clear_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7clear_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4del_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57del_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

68P81132E13-O

10/3/02-GR

1-16


del_cic_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60del_circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8del_db_script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62del_ebts_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63del_span_nail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64del_subrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66del_xbl_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68device_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9disable_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9disp_act_cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2disp_audit_sched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3disp_auto_vp_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4disp_bsc_stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5disp_bsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7disp_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8disp_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9disp_checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11disp_cic_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12disp_cic_use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15disp_circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17disp_dev_stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18disp_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22disp_dsp_reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35disp_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36disp_ebts_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38disp_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39disp_env_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42disp_equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44disp_func_stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47disp_function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49disp_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52disp_gclk_cal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53disp_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54disp_ksw_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56disp_kswx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58disp_lcf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60disp_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62disp_mcap_gproc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63disp_msi_alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64disp_nail_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65disp_num_ebts_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66

68P81132E13-O

10/3/02-GR

1-17


disp_obj_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67disp_omc_net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68disp_options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69disp_plp_net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70disp_rf_cr_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71disp_span_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72disp_span_tdm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73disp_span_use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75disp_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78disp_stats_intrvl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82disp_subrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83disp_tdm_use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85disp_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87disp_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88disp_vpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89disp_xbl_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92disp_xcdr_bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93disp_xcdr_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94disp_xcdr_use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95enable_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10end_delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5equip_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11equip_function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17fill_subrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70find_sccp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3ftp_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12ftp_query_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13ftp_report_bsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14ftp_report_cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15ftp_report_dev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16ftp_severity_lvl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18ftp_trans_bsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19ftp_trans_cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20ftp_trans_dev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8lock_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21manual_sysgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73phase_locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25query_audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23reset_bsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

68P81132E13-O

10/3/02-GR

1-18


restart_mon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28sar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44set_dsp_reld_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75set_num_ebts_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76set_span_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25set_span_clk_ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77set_span_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78set_xcdr_bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80soft_sysgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81start_db_build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82start_delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48sysgen_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83tdm_conn_test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27test_vp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29time_stamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10trace_call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8unalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11unlock_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30vp_sched_aud_off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

68P81132E13-O

10/3/02-GR

1-19


68P81132E13-O

10/3/02-GR

1-20

2

2 Configurationmanagement

Introduction

The BSC Configuration Management (CM) commands allow:

❐ configuration of the Base Station System

❐ modification of the CM database

❐ population of database during SYSGEN


10/3/02-GR

2-1

CHAPTER 2 - CONFIGURATION MANAGEMENT BSC MMI Commands

add_cell

add_cell

Description

Adds cell information to the CM database.

Format

add_cell <location>

Parameters

NOTE

The location parameter is specified when the command is entered, however other parameters are required which are entered in response to system prompts. For the esmr_cell_id parameter, the first 5 tokens have a range of 0 to 15 (inclusive), and tokens 6 and 7 have a range of 0 to 65,535 (inclusive).

location 1 - 80 Indicates the Enhanced Base Transceiver System (EBTS) at which the new cell is located.


✔ ✔


Classification SYSGEN/OLCC

Related commands chg_cell_id on page 2-17

chg_esmr_olcc on page 2-43

del_cell on page 2-57

disp_cell on page 4-8

68P81132E13-O

10/3/02-GR

2-2

BSC MMI Commands CHAPTER 2 - CONFIGURATION MANAGEMENT

add_cell

Example

This example uses a location parameter value of 1 for the EBTS site. The following prompts appear for the remaining parameter elements. Each prompt requires entry of an element name, an equal sign (=), and the element value.

This command may be aborted by typing done as a response to any prompt.

NOTE

Refer to Appendix A for acceptable ranges for each element name.

add_cell 2

Enter ESMR Cell ID 1: esmr_cell_id_1= 0 0 1 0 1 35 100

Enter ESMR Cel l ID 2 (opt ional) :

Enter ESMR Cel l ID 3 (opt ional) :

Enter the Local Cel l ID: local_cell_id=8

Enter CLM over load steps: overload_step=10

Enter the SSM intra cel l handover a l lowed: intra_cell_handover_allowed=1

Enter the SSM inter cel l handover a l lowed: inter_cell_handover_allowed=1

Enter the SSM external cel l handover a l lowed: extrl_cell_handover_allowed=1

Enter the SSM number of preferred cel ls : number_of_preferred_cells = 6

Enter the SSM handover requi red re ject swi tch: handover_required_reject_switch = 0

Enter the subra te_ t runk ing_f lag : subrate_trunking_flag=on

Enter the SSM t imer value: ssmpc_timer_value, 0=30000

Enter the SCCP common contro l channel conf igurat ion: ccch_conf =1

Enter the SCCP number of paging subchannels: bs_ag_blks_res=3

COMMAND ACCEPTED: status = 0

68P81132E13-O

10/3/02-GR

2-3


add_channel

add_channel

Description

Adds a traffic channel between two sites.

Format

add_channel <msi_id_a> <span_id_a> <timeslot_number_a> <group_number_a> <msi_id_b> <span_id_b> <timeslot_number_b> <circuit_id> <remote_site_id>

Parameters

msi_id_a 0-71 Device ID of the MSI-2 on which the span link “a” is located.

span_id_a 0-1 Device ID of span link “a”.

timeslot_number_a 0-23 (T1) Specifies timeslot on T1 link “a”.

0-31 (E1) Specifies timeslot on E1 link “a”.

group_number_a 0-3 Specifies the group the timeslot is in at the BSC.

msi_id_b 0-71 Device ID of the MSI-2 on which the span link “b” is located.

span_id_b 0-1 Device ID of span link “b”.


✔


Classification SYSGEN/RC/OLCC

Related commands chg_channel on page 2-19

chg_channel_olcc on page 2-21

del_channel on page 2-58

disp_channel on page 4-9

68P81132E13-O

10/3/02-GR

2-4


add_channel

timeslot_number_b 0-23 (T1) Specifies timeslot on span link “b”.

0-31 (E1) Specifies timeslot on span link “b”.

circuit_id 0-65535 Value identifying the ID of the circuit which corresponds to the channel being added.

remote_site_id 1-255 Remote site ID of the CP-BSC site.

Example

This example adds a traffic channel between two sites.

add_channel 0 1 0 0 0 1 10 15 53

This example uses the parameter values listed in the following table:

Parameter: Value:

msi_id_a 0

span_id_a 1

timeslot_number_a 0

group_number_a 0

msi_id_b 0

span_id_b 1

timeslot_number_b 10

circuit_id 15

remote_site_id 53

68P81132E13-O

10/3/02-GR

2-5


add_cic_conn

add_cic_conn

Description

For E-XCDR: Adds trunk circuits to timeslots on a span line in the Configuration Management (CM) database. For E-BSC: Adds trunk circuit IDs to the Configuration Management (CM) database.

Format

For E-BSC System:

add_cic_conn <start_cic> <num_of_cic> <remote_site_id>

For E-RXCDR System:

add_cic_conn <start_cic> <num_of_cic> <remote_site_id> <msi_id><span_id><start_ts>

Parameters

start_cic 0-65535 Starting circuit identity code.

num_of_cic 1-500 Number of cic to equip (for E-BSC)1-32 (E1) Number of cic to equip (for E-RXCDR on E1)1-24 (T1) Number of cic to equip (for E-RXCDR on T1)

remote_site_id 1-255 Remote site ID associated with CIC.

msi_id 0-71 Device ID of the MSI card.

span_id 0-1 Device ID of the SPAN line.

start_ts 0-23 (T1) Starting 64kbps time slot.

0-31 (E1)


✔ ✔



Related commands chg_cic_conn on page 2-23

chg_cic_conn_olcc on page 2-25

del_cic_conn on page 2-60

disp_cic_conn on page 4-12

68P81132E13-O

10/3/02-GR

2-6


add_cic_conn

NOTE

When command is used for an E-RXCDR, all parameters are required. When used for an E-BSC, only start_cic, num_of_cic, and remote_site_id parameters are required.

Example 1

This example adds terrestrial circuits (from 3000 to 3019) in CM database for an E-BSC system.

add_cic_conn 3000 20 50


Example 2

This example adds terrestrial circuits (from 3000 to 3002) to span line 13 0 on timeslots 12, 13, 14 on a remote site ID of 54 for an E-RXCDR system.

add_cic_conn 3000 3 54 13 0 12

Parameter Value

<start_cic> 3000

<num_of_cic> 20

<remote_site_id> 50

68P81132E13-O

10/3/02-GR

2-7


add_cic_conn


Parameter Value

<start_cic> 3000

<num_of_cic> 3

<remote_site_id> 54

<msi_id> 13

<span_id> 0

<start_ts> 12

68P81132E13-O

10/3/02-GR

2-8


add_ebts_dte

add_ebts_dte

Description

Sets the DTE address on the X.25 links that an Enhanced Base Transceiver System (EBTS) uses to communicate with the OMC (via the BSC).

Format

add_ebts_dte <ebts_no> <ebts_addr_length> <address_byte1>. . . <address_byte14> <omc_address_length> <address_byte1> . . . <address_byte14>

Parameters

ebts_no 1-80 EBTS site to use this link.

ebts_addr_length 7 or 14 Number of bytes in the EBTS address.

address_byte 0-255 Value of a particular address byte.

omc_addr_length 7 or 14 Number of bytes in the OMC address.


✔ ✔


Classification SYSGEN

Related commands chg_ebts_dte on page 2-29

chg_omc_dte on page 2-48

disp_ebts_dte on page 4-38

68P81132E13-O

10/3/02-GR

2-9


add_ebts_dte

Example

This example sets a DTE address on the X.25 links that EBTS 2 uses to communicate with the OMC (via the BSC).

add_ebts_dte 2 14 3 1 6 0 1 2 0 0 4 1 0 3 0 2 14 3 1 6 0 1 2 0 0 3 1 0 0 0 3

0 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h

3 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h

5 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h 7 3 1 h 6 0 h 1 0 h 0 1 h 3 1 h 5 1 h 0 0 h


Parameter Value

ebts_no 2

ebts_addr_length 14

address_byte 3 1 6 0 1 2 0 0 4 1 0 3 0 2

omc_addr_length 14

address_byte 3 1 6 0 1 2 0 0 3 1 0 0 0 3

68P81132E13-O

10/3/02-GR

2-10


add_span_nail

add_span_nail

Description

Establishes a span nail connection between two span timeslots.

Format

add_span_nail <msi_id_a> <span_id_a> <timeslot_a> <msi_id_b> <span_id_b> <timeslot_b>

Parameters



timeslot_a 0-23 (T1) Specifies timeslot on span link “a”.

0-31 (E1) Specifies timeslot on span link “a”.



timeslot_b 0-23 (T1) Specifies timeslot on span link “b”.



✔ ✔ ✔ ✔



Related commands del_span_nail on page 2-64

disp_nail_conn on page 4-65

68P81132E13-O

10/3/02-GR

2-11


add_span_nail

Example

This example establishes a nailed connection between two span timeslots.

add_span_nail 0 1 0 1 1 0


Parameter Value

<msi_id_a> 0

<span_id_a> 1

<timeslot_a> 0

<msi_id_b> 1

<span_id_b> 1

<timeslot_b> 0

68P81132E13-O

10/3/02-GR

2-12


add_span_nailpipe

add_span_nailpipe

Description

This command establishes a group of nailed connections between two span links. It is used to nail E-OML channels that have a bandwidth between 128 kbps and 384 kbps. (Use add_span_nail to nail 64 kbps channels.)

Format

add_span_nailpipe <msi_id_a> <span_id_a> <timeslot_a> <msi_id_b> <span_id_b> <timeslot_b> <nail_bandwidth>

Parameters



timeslot_a 0-23 (T1) Specifies timeslot on span link “a”.

0-31 (E1) Specifies timeslot on span link “a”.



timeslot_b 0-23 (T1) Specifies timeslot on span link “b”.


nail_bandwidth 2-6 Specifies number of nail bandwidth, starting from 2 DSOs (128 Kbps) up to 6 DSOs (384 Kbps).


✔



Related commands add_span_nail on page 2-11

68P81132E13-O

10/3/02-GR

2-13


add_span_nailpipe

Example

This example establishes a group of nail connections between two span links.

add_span_nail 1 0 2 3 1 1 6


Parameter Value

<msi_id_a> 1

<span_id_a> 0

<timeslot_a> 2

<msi_id_b> 3

<span_id_b> 1

<timeslot_b> 1

<nail_bandwidth> 6

68P81132E13-O

10/3/02-GR

2-14


add_xbl_conn

add_xbl_conn

Description

Adds XBL connectivity information between the RXCDR and BSCs.

Format

add_xbl_conn <xbl_id> <msi_id> <span_id>

Parameters

xbl_id 0-31 XBL ID for which connectivity information is being added.

msi_id 0-71 Device ID of the MSI-2 on which the following span link is located.

span_id 0-1 Device ID of the span link.


✔ ✔



Related commands del_xbl_conn on page 2-68

disp_xbl_conn on page 4-92

68P81132E13-O

10/3/02-GR

2-15


add_xbl_conn

Example

This example establishes XBL connectivity between the RXCDR and BSC.

add_xbl_conn 0 0 1


Parameter Value

<xbl_id> 0

<msi_id> 0

<span_id> 1

68P81132E13-O

10/3/02-GR

2-16


chg_cell_id

chg_cell_id

Description

This command changes the Cell ID of a specified cell.

NOTE

The Cell ID cannot be changed using the chg_element command.

Format

chg_cell_id <old_esmr_cell_id> <new_esmr_cell_id>

Parameters

old_esmr_cell_id Original Cell ID of the cell.

new_esmr_cell_id New Cell ID of the cell.

NOTE

For old_esmr_cell_id and new_esmr_cell_id, the first 5 tokens have a range of 0 to 15 (inclusive), and tokens 6 and 7 have a range of 0 to 65,535 (inclusive).


✔ ✔



Related commands add_cell on page 2-2


68P81132E13-O

10/3/02-GR

2-17


chg_cell_id

Example

chg_cell_id 3 6 4 0 7 35 100 3 6 4 0 7 100 35


Parameter Value

<old_esmr_cell_id> 3 6 4 0 7 35 100

<new_esmr_cell_id> 3 6 4 0 7 100 35

68P81132E13-O

10/3/02-GR

2-18


chg_channel

chg_channel

Description

Changes a traffic channel associated with a specific remote site at the RXCDR.

Format

chg_channel <old_cic_id> <new_cic_id> <remote_site_id>

Parameters

old_cic_id 0-65535 Existing circuit ID.

new_cic_id 0-65535 New circuit ID.

remote_site_id 1-255 Remote site ID.


✔



Related commands add_channel on page 2-4



68P81132E13-O

10/3/02-GR

2-19


chg_channel

Example

This example changes an existing traffic channel between two sites.

chg_channel 90 9 51

COMMAND ACCEPTED


Parameter Value

<old_cic_id> 90

<new_cic_id> 9

<remote_site_id> 51

68P81132E13-O

10/3/02-GR

2-20


chg_channel_olcc

chg_channel_olcc

Description

This command changes the parameters of the traffic channel between two sites and drops all the transactions which are using this channel.

Format

chg_channel_olcc <msi_id_a> <span_id_a> <timeslot_number_a> <group_number_a> <msi_id_b> <span_id_b> <timeslot_number_b> <circuit_id> <remote_site_id>

Parameters


span_id_a 0 or 1 Device ID of span link “a.”

timeslot_number_a 0-23 (T1) Specifies a timeslot on T1 link “a.”

0-31 (E1) Specifies a timeslot on E1 link “a.”

group_number_a 0-3 Specifies the group in which the timeslot is in the BSC.


span_id_b 0 or 1 Device ID of span link “b.”


✔




chg_channel on page 2-19



68P81132E13-O

10/3/02-GR

2-21


chg_channel_olcc

timeslot_number_b 0-23 (T1) Specifies a timeslot on T1 link “b.”

0-31 (E1) Specifies a timeslot on E1 link “b.”

circuit_id 0-65535 Value identifying the ID of the circuit which corresponds to the channel being added.

remote_site_id 1-255 ID of the BSC that the RXCDR is connected to.

NOTE

The chg_channel_olcc command within the delta_init section of the configuration script provides the same result during the SYSGEN as an add_channel MMI command with the same list of parameters.

Example

This example either adds a traffic channel between two sites during SYSGEN, or changes parameters for the present channel during OLCC.

chg_channel_olcc 0 1 0 0 0 1 10 15 12


Parameter Value

<msi_id_a> 0

<span_id_a> 1

<timeslot_number_a> 0

<group_number_a> 0

<msi_id_b> 0

<span_id_b> 1

<timeslot_number_b> 10

<circuit_id> 15

<remote_site_id> 12

68P81132E13-O

10/3/02-GR

2-22


chg_cic_conn

chg_cic_conn

Description

Changes the terrestrial circuit identifier on a remote site.

Format

chg_cic_conn <circuit_id> <new_circuit_id> <remote_site_id>

Parameters

circuit_id 0-65535 Current circuit ID.

new_circuit_id 0-65535 New circuit ID.



✔ ✔



Related commands add_cic_conn on page 2-6



68P81132E13-O

10/3/02-GR

2-23


chg_cic_conn

Example 1

This example changes a terrestrial circuit with an ID of 3000 to an ID of 3005 for an E-BSC.

chg_cic_conn 3000 3005 50


Example 2

This example changes a terrestrial circuit with an ID of 3000 to an ID of 3005 on remote site ID 54 for an E-RXCDR.

chg_cic_conn 3000 3005 54


Parameter Value

<circuit_id> 3000

<new_circuit_id> 3005

<remote_site_id> 50

Parameter Value

<circuit_id> 3000

<new_circuit_id> 3005

<remote_site_id> 54

68P81132E13-O

10/3/02-GR

2-24


chg_cic_conn_olcc

chg_cic_conn_olcc

Description

This command changes the parameters of the specified CIC and drops all transactions using the CIC.

Format

chg_cic_conn_olcc <start_cic> <num_of_cic> <remote_site_id> <msi_id> <span_id> <start_ts>

Parameters

start_cic 0-65535 Starting circuit identity code.

num_of_cic 1 Only one of the CICs can be changed.


msi_id 0-71 Device ID of the MSI card.


start_ts 0-23 (T1) Starting 64kbps time slot.

0-31 (E1)


✔





chg_cic_conn on page 2-23


68P81132E13-O

10/3/02-GR

2-25


chg_cic_conn_olcc

NOTE

The chg_cic_conn_olcc command within the delta_init section of the configuration script provides the same result during the SYSGEN as an add_cic_conn MMI command with the same list of parameters.

Example

This example either adds a terrestrial circuit (3000) to the span line 13 0 on timeslot 12 on a remote site ID of 54 for an E-RXCDR system in the SYSGEN, or changes the span line and timeslot for this CIC.

chg_cic_conn_olcc 3000 1 54 13 0 12


Parameter Value

<start_cic> 3000

<num_of_cic> 1

<remote_site_id> 54

<msi_id> 13

<span_id> 0

<start_ts> 12

68P81132E13-O

10/3/02-GR

2-26


chg_dte

chg_dte

Description

Sets the specified DTE address of a BSC or OMCR link.

Format

NOTE

Entry of at least one address_byte is required.

chg_dte <link> <link_num> <num_address_bytes> <address_byte1> . . . < address_byte14>

Parameters

link bsc The location of the link for the Base Station Controller (BSC).

omcr The location of the link for the Operations and Maintenance Center Radio Part (OMCR).

link_num 0-3 If the link is at the BSC, this is the range.

0-7 If the link is at the OMCR, this is the range.

num_address_bytes 1-14 The number of valid address bytes that are being added to the list.

address_byte 0-255 Value of a particular address byte. Up to 14 address bytes can be entered.


✔ ✔ ✔ ✔



Related commands disp_dte on page 4-36

68P81132E13-O

10/3/02-GR

2-27


chg_dte

Example

This example changes the specified DTE address.

chg_dte bsc 1 7 31h 60h 10h 01h 31h 55h 00h

BSS DTE addresses:

Add ress #0 : 1 f , 3c ,0a ,01 ,1 f , 38 ,00

A d d r e s s # 1 : 3 1 , 6 0 , 1 0 , 0 1 , 3 1 , 5 5 , 0 0

A d d r e s s # 2 : 3 1 , 6 0 , 1 0 , 0 1 , 3 1 , 5 5 , 0 0

A d d r e s s # 3 : 3 1 , 6 0 , 1 0 , 0 1 , 3 1 , 5 5 , 0 0

OMCR DTE addresses:

A d d r e s s # 0 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 2 7

A d d r e s s # 1 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 2 8

A d d r e s s # 2 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 2 9

A d d r e s s # 3 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 3 0

A d d r e s s # 4 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 4 5

A d d r e s s # 5 : 3 1 , 6 0 , 1 9 , 0 1 , 1 0 , 3 1 , 4 6

Address #6: Zero length address



Parameter Value

<link> bsc

<link_num> 1

<num_address_bytes> 7

<address_byte1> 31

<address_byte2> 60

<address_byte3> 10

<address_byte4> 01

<address_byte5> 31

<address_byte6> 55

<address_byte7> 00

68P81132E13-O

10/3/02-GR

2-28


chg_ebts_dte

chg_ebts_dte

Description

Changes an EBTS DTE address in the CM database.

Format

chg_ebts_dte <ebts_no> <new_addr_length> <address_byte1> . . . <address_byte14>

Parameters

ebts_no 1-80 EBTS site on which this link resides.

new_addr_length 7 or 14 Number of bytes in the new EBTS address.


Example

This example establishes a new DTE address for EBTS #1.

chg_ebts_dte 1 7 31 60 10 01 41 56 01


✔ ✔



Related commands disp_ebts_dte on page 4-38

68P81132E13-O

10/3/02-GR

2-29


chg_ebts_dte


Parameter Value

<ebts_no> 1

<new_addr_length> 7

<byte1-14> 31 60 10 01 41 56 01

68P81132E13-O

10/3/02-GR

2-30


chg_element

chg_element

Description

Modifies non-statistical or statistical elements in the CM database.

Refer to Appendix A – “Non-statistical parameters” and Appendix B – “Statistical parameters” for additional information.

Format

Non Statistical Elements:

chg_element <element_name> [,<index1>][,<index2>] <element_value> [cell_number = <cell_number>] (refer to Note below)

Statistical Elements:

chg_element <element_name> [,<index1>][,<index2>] <element_value>

NOTE

The cell_number parameter is required for elements which have a checkmark (✔) in Table 2-1. For all other elements (without ✔), the cell_number parameter is not required.


✔ ✔ ✔ ✔



Related commands add_ebts_dte on page 2-9

disp_element on page 4-39

68P81132E13-O

10/3/02-GR

2-31


chg_element

Parameters

element_name String identifying the element in the CM database.

index1 Some elements require an index. The value that this index represents varies with the individual element name or parameter. The non-statistical use of index1 may be found in Appendix A. The statistical use of index1 may be found in the Statistics chapter description of “chg_element” in this manual. This parameter requires a comma before the index number.

index2 index2 may only be used with Normal and Weighted Distribution statistical element names. No other parameters require it. For the complete list of statistical element names, refer to the description of the “chg_element” command in the Statistics chapter

element_value New value for the element.

cell_number 0–239 Number of the local cell ID identifying the CM database cell (required for per cell parameters). They are highlighted by a checkmark in the table of element names in the command description of chg_element.

Index

The following table shows the database range of values for the parameter. The database range is usually much larger than the actual supported software range. It is not identical to the actual supported software range. The system will always accept the values from this range, but functionally, they may not generate software activity. For the user’s convenience, Appendix A shows the supported software range when possible.

The Span Line column indicates whether an element name is used for E1 and/or T1 configuration or n/a (not applicable). These element names provide alarms when exceeding their respective thresholds.

Add_cell command

The default values listed below only apply when using the add_cell command.

❐ If the user enters an invalid value while using add_cell, the

68P81132E13-O

10/3/02-GR

2-32


chg_element

MMI displays an error message.

❐ If a default value exists at the prompt, that value is used.

❐ If no default exists at the prompt, the command is aborted.

68P81132E13-O

10/3/02-GR

2-33


chg_element

Table 2-1 All Configurable Elements

Element NameSpanLine

Value

Min. Max. Default

abatement_value,1 & n/a 0 100 60



ais_loss_oos T1 0 65,535 500

all_cells_ins n/a 0 1 0

audio_switch_delay n/a 0 none 0

ber_loss_daily E1 0 65,535 4

ber_loss_hourly E1 0 65,535 6

ber_loss_oos E1 0 65,535 3

ber_loss_restore E1 0 10 1

block_retries_num n/a 0 1 1

bs_ag_blks_res �& n/a 0 11 5

bsc_type ➧ n/a 2 2 2

bss_id n/a 0 255 0

bus_device_type n/a 0 255 0

bus_stat_threshold n/a 0 255 0

called_pci n/a 0 1 0

calling_pci n/a 0 1 0

ccch_conf � n/a 0 6 1

clm_timer_value,0 n/a 0 1,000,000 1,000






68P81132E13-O

10/3/02-GR

2-34


chg_element







cp_option_call_audit n/a 0 1 0

cp_option_call_trace n/a 0 1 1

cp_option_interconnect n/a 0 1 1

cp_option_reset_ckt n/a 0 1 0

cr_lockout_tmr & n/a 0 30,000 10,000

dpc n/a 0 16,383 0

ebts_dte_addr n/a none none none

extrl_handover_allowed� n/a 0 1 1

fm_site_type ➧ ! n/a 1, 3, 4, or 5 none

ftp_failure n/a 0 255 none

gclk_qwarm_flag n/a 0 1 0

gproc_slots ➧ n/a 16 or 32 16 (basic)or32

(enhnc’d)

gsm_cell_id_format n/a 0 2 1

handover_required_reject_switch � n/a 0 1 0

high_watermark_3to1 n/a 0 100 80

high_watermark_6to1 n/a 0 100 80

illegal_cell_id n/a 0 255 255

Table 2-1 All Configurable Elements (continued)


Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-35


chg_element

illegal_circuit_id n/a 0 65,535 0

inter_cell_handover_allowed � n/a 0 1 1

intra_cell_handover_allowed � n/a 0 1 1

local_site_id n/a 0 255 0

low_watermark_3to1 n/a 0 100 75

low_watermark_6to1 n/a 0 100 75

lta_alarm_range n/a 0 255 7

max_rst_ckt_timer_exps n/a 0 100 0

mcap_recover_period n/a 0 1439 2

mfsu_flag^ n/a 0 1 0

mtpl2_timer_value,0 n/a 0 4,294,967,295 45,000



mtpl2_timer_value,3 n/a 0 4,294,967,295 500














Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-36


chg_element





mtpl3_timer_value,12 n/a 0 4,294,967,295 3,600,000



mtpl3_timer_value,17 & n/a 0 4,294,967,295 6,000

mtpl3_timer_value,18 & n/a 0 4,294,967,295 60,000

ni n/a 0 3 0

normal_call_thres n/a 1 90 10

number_of_preferred_cells � n/a 0 255 4

omc_dte_addr n/a none none none

onset_value,1 & n/a 0 100 80



opc n/a 0 16,383 6

overload_steps � n/a 0 255 10

pst_timer_value � n/a 2,000 196,000 65,000

remote_loss_daily E1 / T1 0 65,535 2,500

remote_loss_hourly E1 / T1 0 65,535 1250

remote_loss_oos E1 / T1 0 65,535 5000

remote_loss_restore E1 / T1 0 65,535 1

remote_time_oos E1 / T1 0 65,535 500

remote_time_restore E1 / T1 0 65,535 0



Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-37


chg_element

sap_audit_type n/a 1 20 1

sap_device_type n/a 0 31 none

sap_end_time n/a 00:00 23:59 none

sap_interval n/a 00:00 23:59 none

sap_start_time n/a 00:00 23:59 none

short_call_flag n/a off on on

short_call_inst n/a 1 10 2

short_call_thres n/a 1 60 6

slip_loss_daily E1 / T1 0 65,535 2500

slip_loss_hourly E1 / T1 0 65,535 1250

slip_loss_oos E1 / T1 0 65,535 5000

slip_loss_restore E1 / T1 0 65,535 1

sntp_flag# n/a 0 1 0

sntp_poll_time@ n/a 64 1024 180

s_red_loss_daily T1 0 65,535 16

s_red_loss_hourly T1 0 65,535 16

s_red_loss_oos T1 0 65,535 511

s_red_loss_restore T1 0 65,535 0

ssm_overload_threshold n/a 70 90 80

ssmpc_timer_value � n/a 0 1,000,000 none

ssm_timer_value,0 n/a 0 1,000,000 30,000







Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-38


chg_element












ssm_timer_value,16 n/a 0 1,000,000 350




static_vps_first n/a 0 1 1

stat_interval † n/a 5 60 30

subrate_trunking_flag � n/a off on off

sync_loss_daily E1 0 65,535 2,500

sync_loss_hourly E1 0 65,535 1,250

sync_loss_oos E1 0 65,535 5,000

sync_loss_restore E1 0 65,535 1

sync_time_oos T1 0 65,535 2,500

sync_time_restore T1 0 65,535 2,500

tdm_call_block n/a off on on



Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-39


chg_element

thres_vp_alarms n/a off on on

transcoder_location n/a 0 1 1

transcoder_mode n/a 1 1 1

tty_baudot_flag ! n/a 0 1 0

tty_baudot_rate ! n/a 0 1 0

unblock_retries_num n/a 0 255 5

vp_config_threshold n/a 0 10 2

vpr_vtt_flag n/a off on on

xcdr_bypass_allowed � n/a 0 3 1

† If operator fails to reset the interval to 30-min, the OMC calculations of the Key Stats and Health Indicators are interrupted for the entire period until the interval is reset. See Statistics chapter for procedures/applications of the stat_interval parameter.� A cell_number is required.➧ Changing this element outside of the SYSGEN mode will cause the system to reset.+ Only even values should be entered.- Only odd values should be entered.^ Changing this flag will result in Statistic files not being uploaded to the OMC. # Changing this flag will result in the loss of time synchronization with the OMC. This will

also result in incorrect timestamps in the Stats file to the OMC.@ During SYSGEN off, Min, Max, and default values are in seconds. During SYSGEN on, Min,

Max, and default values are in centiseconds; therefore, they should be multiplied by 100.! Changing this element is only allowed during SYSGEN.& Changing this element is allowed during OLCC mode.� Changing this element is only allowed on BSC and E-BSC Systems.



Value

Min. Max. Default

68P81132E13-O

10/3/02-GR

2-40


chg_element

Exampe 1:

This example changes the value of the handover_required_reject_switch element for cell number 1.

chg_element handover_required_reject_switch 1 cell_number = 1


Example 2:

This example changes the value of the high_watermark_3to1 to 90%.

chg_element high_watermark_3to1 90


Parameter Value

<element_name> <handover_required_reject_switch>

<element_value> [1]

[cell_number = <cell_number>]

cell_number = 1

Parameter Value

<element_name> high_watermark_3to1

<element_value> 90

68P81132E13-O

10/3/02-GR

2-41


chg_element

Exampe 3:

This example changes cell 5’s subrate_trunking_flag to on.

chg_element subrate_trunking_flag on cell_number=5


Parameter Value

<element_name> <subrate_trunking_flag>

<element_value> on

[cell_number = <cell_number>]

cell_number = 5

68P81132E13-O

10/3/02-GR

2-42


chg_esmr_olcc

chg_esmr_olcc

Description

This command sets or changes the primary and secondary Cell ID for a specific cell.

Format

chg_esmr_olcc <local_cell_id>

Parameters

local_cell_id 0-239 Indicates the local cell ID which the changed ESMR Cell ID is related to.

NOTE

The local_cell_id parameter is specified at the moment the command is entered; however, other parameters shall be entered in response to the system prompts. If ESMR Cell ID 2 or 3 is not entered, this ESMR will be set to NULL.

Example

This example uses a local_cell_id value of 1. The following prompts appear for the remaining parameter elements. Each prompt requires entry of an element name, an equal sign (=), and the element value.


✔ ✔


Classification OLCC


chg_cell_id on page 2-17

del_cell on page 2-57


68P81132E13-O

10/3/02-GR

2-43


chg_esmr_olcc

This command may be aborted by typing done as a response to the “Enter ESMR Cell ID 1:” prompt.

NOTE

Refer to Appendix A for acceptable ranges for each element name.

Example

chg_esmr_olcc 1

Enter ESMR Cell ID 1: emsr_cell_id_1=0 0 1 0 1 1 3 1

Enter ESMR Cell ID 2 (optional): emsr_cell_id_2=0 0 1 0 1 1 3 1

Enter ESMR Cell ID 3(optional):

68P81132E13-O

10/3/02-GR

2-44


chg_ksw_config

chg_ksw_config

Description

Used to change the KSW configuration (specifically, the mapping of the TDM highway numbers for a specified KSW pair).

Format

chg_ksw_config <ksw_pair> <tdm_highway0> [<tdm_highway1>] [<tdm_highway2>] [<tdm_highway3>]

Parameters

ksw_pair 0-3 The KSW pair for which the mapping is changing. There is one KSW pair per cage.

tdm_highway_0-3 0-3 The Highway number that is mapped to the first, second, third, or fourth 1024 timeslots.

Example 1

This example changes 2 KSW configurations.

chg_ksw_config 0 0 1

chg_ksw_config 1 3 0

Example 2

This example changes 3 KSW configurations.

chg_ksw_config 0 0 1 2




✔ ✔ ✔ ✔



Related commands disp_ksw_config on page 4-56

68P81132E13-O

10/3/02-GR

2-45


chg_level

chg_level

Description

Changes the current security level.

NOTE

Security level passwords are case-sensitive and require from one to sixteen characters. Password entries are not echoed.

Format

chg_level

Parameters

There are no parameters; a prompt appears for the desired level. Refer to “Security management” in Chapter 1 for additional information on security levels.

Example

chg_level

Enter password for secur i ty leve l you wish to access:

Current secur i ty leve l is 1 .


✔ ✔ ✔ ✔



Related commands disp_level on page 4-62

68P81132E13-O

10/3/02-GR

2-46


chg_msi_mode

chg_msi_mode

Description

Changes the MSI operating mode to either T1 or E1 in the database, based on the span type entered.

Format

chg_msi_mode <string>

Parameters

string (T1 or E1) Operating mode of MSI.

Example

This example changes the mode of the MSI to T1.

chg_msi_mode T1

COMMAND ACCEPTED: SYSGEN mode is ON — reset the site now and regenerate the database.


✔ ✔ ✔ ✔



Related commands none

68P81132E13-O

10/3/02-GR

2-47


chg_omc_dte

chg_omc_dte

Description

Changes the OMC DTE address in the CM database.

Format

chg_omc_dte <ebts_no> <new_addr_length> <address_byte1> . . . <address_byte14>

Parameters

ebts_no 1-80 EBTS on which this link resides.

new_addr_length 7 or 14 Number of bytes in the new EBTS address.



✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

2-48


chg_omc_dte

Example

This example establishes a new OMC DTE address for EBTS #2.

chg_omc_dte 2 14 3 1 6 2 1 2 1 2 3 4 5 6 7 8


Parameter Value

<ebts_no> 2

<new_addr_length> 14

<address_bytes> 3 1 6 2 1 2 1 2 3 4 5 6 7 8

68P81132E13-O

10/3/02-GR

2-49


chg_password

chg_password

Description

Changes the password for a specific security level. Note the following about passwords:

❐ Passwords are case-sensitive.

❐ Passwords must be from one to sixteen characters in length. Passwords longer than this are truncated to sixteen characters.

❐ New passwords must differ from current passwords by at least four characters.

❐ Password entries are not echoed.

Format

chg_password

Parameters

None.

Example

chg_password

Enter password for leve l you wish to change:

Enter new password:

Ver i fy new password:


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

2-50


chg_subrate_olcc

chg_subrate_olcc

Description

This command changes the parameters of the pool of subrates identified by its key parameters and drops all the transactions which are using subrates from the pool.

Format

chg_subrate_olcc <ebts_id> <ebts_span_id> <ebts_start_ts> <ebts_start_grp> <bsc_msi> <bsc_span_id> <bsc_start_ts> <bsc_start_grp> <num_of_subrates> [<remote_site_id>]

Parameters

ebts_id 1-80 Indicates the Enhanced Base Transceiver System (EBTS) ID where the pool of subrates is located.

ebts_span_id 0-1 Device ID of the span link.

ebts_start_ts 0-31 Timeslot on the span link.

ebts_start_grp 0-3 Specifies the group the timeslot is in.

bsc_msi 0-71 Device ID of the MSI card.

bsc_span_id 0-1 Device ID of the Span link.

bsc_start_ts 0-23 (T1) Starting timeslot on the Span link.

0-31 (E1)

bsc_start_grp 0-3 Specifies the starting group the timeslot is in.

num_of_subrates 1-96 Specifies the number of subrated timeslots.

remote_site_id 1-255 ID of the E-BSC the E-RXCDR is connected to. This parameter is required for E-RXCDR only.


✔ ✔



Related commands del_subrate on page 2-66

fill_subrate on page 2-70

disp_subrate on page 4-83

68P81132E13-O

10/3/02-GR

2-51


chg_subrate_olcc

NOTE

The use of chg_subrate_olcc in the delta_init section of the configuration file causes the same result as a fill_subrate MMI command with the same list of parameters. This command is allowed in the delta_init or delta_only sections during the OLCC. It changes the number of subrates in a pool and BSC related parameters in OLCC. The pool is defined by the set of key parameters. These parameters are <ebts_id> <ebts_span_id> <ebts_start_ts> <ebts_start_grp> and <remote_site_id > in the case of E-RXCDR configuration.

Example 1

The following command maps 40 subrated timeslots from EBTS 50 to a BSC during the SYSGEN or changes the number of subrates and the BSC parameters during the OLCC . It maps EBTS span 1 timeslot 0 group 0 to BSC MSI 1 span 0 timeslot 5 group 0 consecutively up to EBTS span 1 timeslot 9 group 3 to BSC MSI 1 span 0 timeslot 14 group 3.

chg_subrate_olcc 50 1 0 0 1 0 5 0 40


Parameter Value †

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

<bsc_msi> 1

<bsc_span_id> 0

<bsc_start_ts> 5

<bsc_start_grp> 0

<num_of_subrates> 40

68P81132E13-O

10/3/02-GR

2-52


chg_subrate_olcc

Example 2

The following example shows the chg_subrate_olcc command issued at an E-RXCDR. This command maps 40 subrated timeslots from EBTS 50 to an E-RXCDR which is connected to E-BSC 20 during the SYSGEN. It maps EBTS span 1 timeslot 0 group 0 to E-RXCDR MSI 10 span 0 timeslot 0 group 0 consecutively up to EBTS span 1 timeslot 9 group 3 to E-RXCDR MSI 10 span 0 timeslot 9 group 3. This command changes the number of subrated timeslots to 40 and changes the BSC parameters during the OLCC.

chg_subrate_olcc 50 1 0 0 10 0 0 0 40 20


Parameter Value †

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

<bsc_msi> 10

<bsc_span_id> 0

<bsc_start_ts> 0

<bsc_start_grp> 0


<remote_site_id> 20

68P81132E13-O

10/3/02-GR

2-53


chg_time

chg_time

Description

Sets the real-time system clock. The user enters the current year, month, day, hour, minute, and second. Once the time synchronization is enabled, the BSC will synchronize its internal clock using SNTP (Simple Network Time Protocol) and will display in UTC (Universal Coordinated Time) format. UTC time is not corrected for geographical time zones, consistent with other Network Elements in the iDEN system. If time synchronization is disabled, the user can set the BSC clock.

Format

chg_time <year> <month> <day> <hour> <minute> <second>

Parameters

year Value identifying the year. Must be a number equal to or greater than 1980.

month Value identifying the month. Must be a number between 1 and 12.

day Value identifying the day. Must be a number between 1 and 31.

hour Value identifying the hour. Must be a number between 0 and 23.

minute Value identifying the minute. Must be a number between 0 and 59.

second Value identifying the second. Must be a number between 0 and 59.


✔ ✔ ✔ ✔



Related commands disp_time on page 4-87

68P81132E13-O

10/3/02-GR

2-54


chg_time

NOTE

The chg_time command will only be enabled when Time Synchronization with the OMC is disabled. Disabling Time Synchronization will cause the BSC clock to lose synchronization with the OMC clock, thus the use of chg_time is discouraged.

Example

This example sets the system date to February 15th, 1996, and the time to 09:23:00 am.

chg_time 1996 2 15 9 23 0

F e b 1 5 1 9 9 6 0 9 : 2 3 : 0 0


Parameter Value †

<year> 1996

<month> 2

<day> 15

<hour> 9

<minute> 23

<second> 0

68P81132E13-O

10/3/02-GR

2-55


clear_database

clear_database

Description

This command clears the contents of the system database (but database script object remains in the system). This command should only be used before a SYSGEN is performed.

Format

clear_database

Parameters

None.

Example

This example clears the entire database.

clear_database


✔ ✔ ✔ ✔



Related commands manual_sysgen on page 2-73

sysgen_mode on page 2-83

reset_bsc on page 3-27

68P81132E13-O

10/3/02-GR

2-56


del_cell

del_cell

Description

This command deletes cell information from the CM database and drops all transactions using this cell.

Format

del_cell <local_cell_id>

Parameters

local_cell_id 0 - 239 Indicates the local cell ID which the deleted cell is related to..

Example

This example deletes a cell with the local_cell_id of 1.

del_cell 1



✔ ✔


Classification OLCC


chg_cell_id on page 2-17

chg_esmr_olcc on page 2-43

disp_act_cells on page 4-2


Parameter: Value:

<local_cell_id> 1

68P81132E13-O

10/3/02-GR

2-57


del_channel

del_channel

Description

Deletes a RXCDR traffic channel connection between two sites. The traffic channel pertaining to circuit_id and corresponding remote_site_id is deleted.

Format

del_channel <circuit_id> <remote_site_id>

Parameters

circuit_id 0-65535 Circuit ID to be deleted.

remote_site_id 1-255 Remote site ID of the CP-BSC site.

Example

This example removes a traffic channel between two sites.

del_channel 6 51


✔





chg_channel_olcc on page 2-21


68P81132E13-O

10/3/02-GR

2-58


del_channel


Parameter Value †

<circuit_id> 6

<remote_site_id> 51

68P81132E13-O

10/3/02-GR

2-59


del_cic_conn

del_cic_conn

Description

Deletes the terrestrial circuit connection on a remote site.

Format

del_cic_conn <circuit_id> <remote_site_id>

Parameters

circuit_id 0-65535 Current circuit ID.



✔ ✔




chg_cic_conn on page 2-23

chg_cic_conn_olcc on page 2-25


68P81132E13-O

10/3/02-GR

2-60


del_cic_conn

Example 1

This example deletes terrestrial circuit ID 3000 on an E-BSC system.

del_cic_conn 3000 50


Example 2

This example deletes terrestrial circuit ID 3000 on remote site ID 54 on an E-RXCDR system.

del_cic_conn 3000 54


Parameter Value

<circuit_id> 3000

<remote_site_id> 50

Parameter Value

<circuit_id> 3000

<remote_site_id> 54

68P81132E13-O

10/3/02-GR

2-61


del_db_script

del_db_script

Description

Deletes a database script object from the system to allow manual SYSGEN or to prepare a database script object download from the OMC.

Note — The database script contains the BSC system configuration.

Format

del_db_script

Parameters

None.

Example

del_db_script

Database scr ip t ob ject de leted f rom 1 GPROC(‘s) .


✔ ✔ ✔ ✔


Classification RC

Related commands sysgen_mode on page 2-83


68P81132E13-O

10/3/02-GR

2-62


del_ebts_dte

del_ebts_dte

Description

Deletes the DTE address used by an EBTS to communicate with the OMC (via the BSC). Both elements of this address (OMC and EBTS) are deleted.

Format

del_ebts_dte <ebts_no>

Parameters

ebts_no 1-80 EBTS site that uses this link.

Example

This example removes the DTE address for EBTS #16.

del_ebts_dte 16



✔ ✔



Related commands add_ebts_dte on page 2-9

chg_ebts_dte on page 2-29

disp_ebts_dte on page 4-38

Parameter Value †

<ebts_no> 16

68P81132E13-O

10/3/02-GR

2-63


del_span_nail

del_span_nail

Description

Removes a nailed connection between two span timeslots.

Format

del_span_nail <msi_id_a> <span_id_a> <timeslot_number_a> <msi_id_b> <span_id_b> <timeslot_number_b>

Parameters



timeslot_number_a 0-23 (T1) Specifies timeslot on span link “a”.

0-31 (E1)



timeslot_number_b 0-23 (T1) Specifies timeslot on span link “b”.

0-31 (E1)


✔ ✔ ✔ ✔




disp_nail_conn on page 4-65

68P81132E13-O

10/3/02-GR

2-64


del_span_nail

Example

This example removes a nailed connection between two span timeslots.

del_span_nail 3 0 4 6 1 4


Parameter Value

<msi_id_a> 3

<span_id_a> 0

<timeslot_number_a> 4

<msi_id_b> 6

<span_id_b> 1

<timeslot_number_b> 4

68P81132E13-O

10/3/02-GR

2-65


del_subrate

del_subrate

Description

Deletes an existing SCI pool and drops the transactions which are using subrates in this pool.

Format

del_subrate <ebts_id> <ebts_span_id> <ebts_start_ts> <ebts_start_grp> [<remote_site_id>]

Parameters

ebts_id 1-80 Indicates the Enhanced Base Transceiver System (EBTS) ID where the subrate is located.




remote_site_id 1-255 ID of the E-BSC the E-RXCDR is connected to. This parameter required for E-RXCDR only.


✔ ✔



Related commands chg_subrate_olcc on page 2-51



68P81132E13-O

10/3/02-GR

2-66


del_subrate

Example 1

This example deletes subrate pool id 50 1 0 0 from a BSC system.

del_subrate 50 1 0 0


Example 2

This example deletes subrate pool id 50 1 0 0 from an E-RXCDR system.

del_subrate 50 1 0 0 20


Parameter Value †

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

Parameter Value †

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

<remote_site_id> 20

68P81132E13-O

10/3/02-GR

2-67


del_xbl_conn

del_xbl_conn

Description

This command removes the XBL connectivity information between the RXCDR and BSC.

Format

del_xbl_conn <xbl_id> <msi_ id> <span_id>

Parameters

xbl_id 0-31 XBL site number.

msi_id 0-71 Device ID of the MSI.

span_id 0-1 Device ID of the SPAN link.


✔ ✔



Related commands add_xbl_conn on page 2-15

disp_xbl_conn on page 4-92

68P81132E13-O

10/3/02-GR

2-68


del_xbl_conn

Example

del_xbl_conn 5 2 1


Parameter Value

<xbl_id> 5

<MSI_id> 2

<SPAN_id> 1

68P81132E13-O

10/3/02-GR

2-69


fill_subrate

fill_subrate

Description

This command adds an SCI pool that maps a subrated EBTS span timeslot to a subrated BSC span timeslot. The number of subrated timeslots to be mapped can be specified by the user.

Format

fill_subrate <ebts_id> <ebts_span_id> <ebts_start_ts> <ebts_start_grp> <bsc_msi> <bsc_span_id> <bsc_start_ts> <bsc_start_grp> <num_of_subrates> [<remote_site_id>]

Parameters

ebts_id 1-80 Indicates the Enhanced Base Transceiver System (EBTS) ID where the subrate is located.




bsc_msi 0-71 Device ID of the MSI card.

bsc_span_id 0-1 Device ID of the Span link.

bsc_start_ts 0-23 (T1) Starting timeslot on the Span link.

0-31 (E1)

bsc_start_grp 0-3 Specifies starting group the timeslot is in.

num_of_subrates 1-96 Specifies the number of subrated timeslots.

remote_site_id 1-255 ID of the E-BSC the E-RXCDR is connected to. This parameter required for E-RXCDR only.


✔ ✔




del_subrate on page 2-66


68P81132E13-O

10/3/02-GR

2-70


fill_subrate

NOTE

EBTS parameters define the SCI pool ID that is used for further operations with this pool.

Example 1

The following command creates the SCI pool and maps 40 subrated timeslots from EBTS 50 to a BSC.

It maps EBTS span 1 timeslot 0 group 0 to BSC MSI 1 span 0 timeslot 5 group 0 consecutively up to EBTS span 1 timeslot 9 group 3 to BSC MSI 1 span 0 timeslot 14 group 3.

fill_subrate 50 1 0 0 1 0 5 0 40


Parameter Value

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

<bsc_msi> 1

<bsc_span_id> 0

<bsc_start_ts> 5

<bsc_start_grp> 0


68P81132E13-O

10/3/02-GR

2-71


fill_subrate

Example 2

The following example shows the fill_subrate command issued at an E-RXCDR. This command creates the SCI pool and maps 40 subrated timeslots from EBTS 50 to an E-RXCDR which is connected to E-BSC 20.

It maps EBTS span 1 timeslot 0 group 0 to E-RXCDR MSI 10 span 0 timeslot 0 group 0 consecutively up to EBTS span 1 timeslot 9 group 3 to E-RXCDR MSI 10 span 0 timeslot 9 group 3.

fill_subrate 50 1 0 0 10 0 0 0 40 20


Parameter Value

<ebts_id> 50

<ebts_span_id> 1

<ebts_start_ts> 0

<ebts_start_grp> 0

<bsc_msi> 10

<bsc_span_id> 0

<bsc_start_ts> 0

<bsc_start_grp> 0


<remote_site_id> 20

68P81132E13-O

10/3/02-GR

2-72


manual_sysgen

manual_sysgen

Description

Allows the user to manually specify a database script to re-initialize the BSC system. The database script object (object 4) is bypassed during this operation.

Once this command is executed with a parameter set to on, the BSC automatically starts a reset.

NOTE

When SYSGEN is turned on, the database is not broadcast to the other GPROCs. When SYSGEN is turned off, the checksum is calculated and the system database is broadcast to other GPROCs.If the user does not specify a database script, the BSC will automatically re-initialize the system with the existing database configuration.This command is allowed only on the master GPROC.

Format

manual_sysgen <action>


✔ ✔ ✔ ✔



Related commands clear_database on page 2-56soft_sysgen on page 2-81sysgen_mode on page 2-83

68P81132E13-O

10/3/02-GR

2-73


manual_sysgen

Parameters

action on Turns SYSGEN on.

off Turns SYSGEN off.

Example

manual_sysgen on


Parameter Value

<action> on

68P81132E13-O

10/3/02-GR

2-74


set_dsp_reld_flag

set_dsp_reld_flag

Description

Sets the DSP reload flag ON or OFF. With flag set to ON, XCDR unlock or enable transition will result in re-downloading the XCDR’s DSP (VP) code. Bypassing of the DSP download procedure reduces the initialization time of the XCDR. However, if there are excessive VP failures detected by Voice Trunk Testing (test_vp) on a particular card, it is recommended to re-download the DSPs during XCDR initialization in an effort to restart VPs which have failed.

NOTE

Perform this command only on the BSP.

Format

set_dsp_reld_flag <mode>

Parameters

mode on Turns download option on

off Turns download option off

Example

set_dsp_reld_flag on


✔ ✔




68P81132E13-O

10/3/02-GR

2-75


set_num_ebts_dl

set_num_ebts_dl

Description

Sets the maximum number of concurrent EBTS download sessions that a BSC is able to perform.

NOTE


Format

set_num_ebts_dl <num _downloads>

Parameters

num _downloads 1-10 Maximum number of concurrent EBTS download sessions allowed.

Example

This example sets the maximum number of concurrent EBTS download sessions allowed to 1.

set_num_ebts_dl 1



✔ ✔



Related commands disp_num_ebts_dl on page 4-66

Parameter Value

<num_downloads> 1

68P81132E13-O

10/3/02-GR

2-76


set_span_clk_ref

set_span_clk_ref

Description

Configures the span used to extract a reference for use by the GCLK for phase locking.

Format

T1 Span Systemset_span_clk_ref <device_id1> <device_id2>

E1 Span Systemset_span_clk_ref <device_id1> <device_id2> <bits_flag>

Parameters

device_id1 0-71 Device ID of the MSI on which the specified span link is located (selected MSI must be in Cage 0).

device_id2 0-1 Device ID of the span link.

bits_flag bits Connect span to BITS (E1 span only)

no_bits Do NOT connect span to BITS (E1 span only)

Example

set_span_clk_ref 2 1

COMMAND ACCEPTED



✔ ✔ ✔ ✔



Related commands phase_locking on page 3-25

Parameter Value

<device_id1> 2

<device_id2> 1

68P81132E13-O

10/3/02-GR

2-77


set_span_length

set_span_length

Description

This command is used to set the equalization level (transmit signal strength) of a specified MSI span.

NOTE

This command is allowed only for T1 systems.

Format

set_span_length <MSI_id> <span_id> <equalization_parameter>

Parameters

MSI_id 0-71 Device ID of the MSI on which the specified span link is located.

span_id 0-1 Device ID of the span link.

equalization_parameter 0-4 Specifies the length (in feet) of the specified span line, as follows:

0 (default) = 0 to 768 feet1 = 131 to 917 feet2 = 262 to 1048 feet3 = 393 to 1179 feet4 = 524 to 1310 feet

Note that these lengths are supported from the MSI. The far-end device needs to also support the span lengths for proper operation.


✔ ✔ ✔ ✔



Related commands disp_device on page 4-22

68P81132E13-O

10/3/02-GR

2-78


set_span_length

Example

This example sets the equalization level of span 0 for MSI 0 to a length of 262 to 1048 feet.

set_span_length 0 0 2

COMMAND ACCEPTED


Parameter Value

<MSI_id> 0

<span_id> 0

<equalization_parameter> 2

68P81132E13-O

10/3/02-GR

2-79


set_xcdr_bypass

set_xcdr_bypass

Description

Sets the XCDR bypass flag values for all configured cells.

Format

set_xcdr_bypass <n>

Parameters

n 0 OFF.

1 Bypass Flag ON.

2 Audit Flag ON.

3 Bypass and Audit Flags ON.

Example

This example sets all the XCDR bypass allowed flags to 1.

set_xcdr_bypass 1

Al l xcdr_bypass_al lowed va lues set to 1 .



✔ ✔



Related commands disp_xcdr_bypass on page 4-93

Parameter Value

<n> 1

68P81132E13-O

10/3/02-GR

2-80


soft_sysgen

soft_sysgen

Description

The system database (database.002 object) is cleared and the Genesis database script object (mmi_spt.004 object) is re–parsed to rebuild the system database. The BSC is initialized after the database has been rebuilt.

NOTE

When SYSGEN is turned on, the database is not broadcast to the other GPROCs. When SYSGEN is turned off, the checksum is calculated and the system database is broadcast to other GPROCs.

Format

soft_sysgen <action>

Parameters

action on Turns SYSGEN on

off Turns SYSGEN off

Example

soft_sysgen on



✔ ✔ ✔ ✔




Parameter Value

<action> on

68P81132E13-O

10/3/02-GR

2-81


start_db_build

start_db_build

Description

Starts the process of building a new database from the Code Object Manager (COM) script file.

Format

start_db_build

Parameters

None.

Example

start_db_build


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

2-82


sysgen_mode

sysgen_mode

Description

Initiates or terminates a SYSGEN session.

Command execution can occur without system delays. There is no interaction with other processes.

NOTE

When SYSGEN is turned on, the database is not broadcast to the other GPROCs. When SYSGEN is turned off, the checksum is calculated and the system database is broadcast to the other GRPOCs.

This command can be used to remove any recent changed parameter values. If the mmi_spt.004 object (the Genesis database script object) resides on the BSC, a sysgen_mode on command followed by a reset_bsc command clears the contents of the database.002 object (the system database object). The mmi_spt.004 object is re-parsed to rebuild the database.002 object and the BSC hardware is re-initialized.

This command can also be used to prepare the BSC for downloading the mmi_spt.004 object from the OMC. If the mmi_spt.004 object is not loaded on the BSC, a sysgen_mode on command followed by a reset_bsc command will start this process. The mmi_spt.004 object is downloaded to the BSC and is parsed to rebuild the database.002 object. The BSC hardware is re-initialized after the database.002 object has been rebuilt.

68P81132E13-O

10/3/02-GR

2-83


sysgen_mode

Format

sysgen_mode <action>

Parameters

action on Turn SYSGEN on.

off Turn SYSGEN off.


✔ ✔ ✔ ✔



Related commands del_db_script on page 2-62

manual_sysgen on page 2-73

soft_sysgen on page 2-81


68P81132E13-O

10/3/02-GR

2-84


sysgen_mode

Example 1:

This example terminates the current SYSGEN session.

If sysgen_mode off command was run during parsing of DB script object, the system will display a summary report containing up to 30 “command rejected” messages.

sysgen_mode off

* * * The Tota l Number o f Re jec ted Commands is : 4 * * *

*** The Fo l lowing are L is t o f the Rejec ted Commands ***

* equip_func LCF

ERROR: Duplicate XBL has been entered.

* equip_device RSL

COMMAND REJECTED: Invalid t imeslot info was specif ied.

* add_c i c_conn 1 51 0 0 6

ERROR: Missing Parameters, only received: 5

* add_ce l l 117

ERROR: Range Error, parameter number: 1

* * * End o f L i s t * * *

Example 2:

This example reinitializes the system.

sysgen_mode on

YOU MUST NOW RE-INIT THE SITE TO START SYSGEN

68P81132E13-O

10/3/02-GR

2-85


sysgen_mode

68P81132E13-O

10/3/02-GR

2-86

3

3 Devicemanagement

Introduction

Device Management (DM) commands allow the administrative state of functions and devices to be displayed or modified.


10/3/02-GR

3-1

CHAPTER 3 - DEVICE MANAGEMENT BSC MMI Commands

add_circuit

add_circuit

Description

Adds a trunk circuit to a timeslot on a span line in the Configuration Management (CM) database.

Format

add_circuit <msi_id> <span_id> <circuit_id> <timeslot_number> <group number>

Parameters

msi_id 0-71 Device ID of the MSI on which the specified span line is located.

span_id 0 or 1 Device ID of the span line to which the circuit is being added.

circuit_id 0-65535 Value identifying the ID of the circuit being added.

timeslot_number T1 (0-23) Specifies the timeslot on the T1 span line on which to add the circuit.

E1 (0-31) Specifies the timeslot on the E1 span line on which to add the circuit.

group_number 0 to 3 Specifies the group in which the timeslot is located.


✔



Related commands chg_circuit on page 3-4

chg_circuit_olcc on page 3-5

del_circuit on page 3-8

disp_circuit on page 4-17

68P81132E13-O

10/3/02-GR

3-2

BSC MMI Commands CHAPTER 3 - DEVICE MANAGEMENT

add_circuit

Example

This example adds a terrestrial circuit, with an ID of 28, to span line 0 0 and timeslot 7.

add_circuit 0 0 28 7 0


Parameter: Value:

<msi_id> 0

<span_id> 0

<circuit_id> 28

<timeslot_number> 7

<group_number> 0

68P81132E13-O

10/3/02-GR

3-3


chg_circuit

chg_circuit

Description

Changes the circuit ID on an existing terrestrial circuit.

Format

chg_circuit <circuit_id> <new_circuit_id>

Parameters

circuit_id 0-65535 Value identifying the ID of the circuit being changed.

new_circuit_id 0-65535 Value identifying the ID to be assigned to the circuit.

Example

This example changes a terrestrial circuit, with an ID of 12, to an ID of 18.

chg_circuit 12 18



✔



Related commands add_circuit on page 3-2



Parameter: Value:

<circuit_id> 12

<new_circuit_id> 18

68P81132E13-O

10/3/02-GR

3-4


chg_circuit_olcc

chg_circuit_olcc

Description

This command changes the parameters of the trunk circuit and drops all the transactions which are using this circuit.

Format

chg_circuit_olcc <msi_id> <span_id> <circuit_id> <timeslot_number> <group_number>

Parameters

msi_id 0-71 Device ID of the MSI on which the specified span line is located.

span_id 0 or 1 Device ID of the span line to which the circuit is being changed.

circuit_id 0-65535 Value identifying the ID of the circuit

timeslot_number 0-23 (T1) Specifies the timeslot on the T1 span line on which the circuit is added.

0-31 (E1) Specifies the timeslot on the E1 span line on which the circuit is added.

group_number 0 to 3 Specifies the group in which the timeslot is located


✔





chg_circuit on page 3-4


68P81132E13-O

10/3/02-GR

3-5


chg_circuit_olcc

NOTE

The chg_circuit_olcc command within the delta_init section of the configuration script provides the same result during the SYSGEN as an add_circuit MMI command with the same list of parameters.

Example

This example either adds a terrestrial circuit with an ID of 28 to span line 0 0 and timeslot 7 during SYSGEN, or changes parameters for the present circuit in OLCC.

chg_circuit_olcc 0 0 28 7 0


Parameter: Value:

<msi_id> 0

<span_id> 0

<circuit_id> 28

<timeslot_number> 7

<group_number> 0

68P81132E13-O

10/3/02-GR

3-6


clear_gclk_avgs

clear_gclk_avgs

Description

This command clears the periodically stored GCLK’s frequency register values from NV RAM.

Format

clear_gclk_avgs <device_id>

Parameters

device_id Number identifying the GCLK first id.

Example

This example clears the periodically stored GCLK’s frequency register values for GCLK 0 0 0.

clear_gclk_avgs 0

COMMAND ACCEPTED: status = 0


✔ ✔ ✔ ✔



Related commands disp_gclk_avgs on page 4-52

disp_gclk_cal on page 4-53

68P81132E13-O

10/3/02-GR

3-7


del_circuit

del_circuit

Description

Deletes a terrestrial circuit from a timeslot on a span line in the CM database and drops the transactions which are using this circuit.

Format

del_circuit <circuit_id>

Parameters

circuit_id 0 - 65535 Value identifying the ID of the circuit being deleted.

Example

This example deletes a terrestrial circuit id 3000.

del_circuit 3000


✔





chg_circuit_olcc on page 3-5


68P81132E13-O

10/3/02-GR

3-8


disable_alarm

disable_alarm

Description

Disables alarm reporting to the customer MMI.

Format

disable_alarm

Parameters

None.

Example

disable_alarm


✔ ✔ ✔ ✔


Classification RC

Related commands enable_alarm on page 3-10

68P81132E13-O

10/3/02-GR

3-9


enable_alarm

enable_alarm

Description

Enables alarm reporting to the customer MMI.

Format

enable_alarm

Parameters

None.

Example:

enable_alarm

*XCDR ALARM: 33 0 0 0: 231: Reserved Alarm Code 0xe7

*SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A

*SEVERITY: Cri t ical Category: Equipment

* W e d 9 / 1 6 / 9 4 2 1 : 4 8 : 1 7 : 4 9 0

*ADDITIONAL INFO

COMMAND ACCEPTED


✔ ✔ ✔ ✔


Classification RC

Related commands disable_alarm on page 3-9

68P81132E13-O

10/3/02-GR

3-10


equip_device

equip_device

Description

Adds a device to the Fault Management (FM) portion of the Configuration Management (CM) database. The devices supported by this command are listed on the following pages.

NOTE

For additional information on supported devices, refer to Appendix C – “Device and function definitions.”

Format

equip_device <DEVICE>


✔ ✔ ✔ ✔



Related commands lock_device on page 3-21

unlock_device on page 3-30

disp_dev_stat on page 4-18

disp_device on page 4-22

68P81132E13-O

10/3/02-GR

3-11


equip_device

Parameters

NOTE

The DEVICE parameter must be entered in uppercase letters.

DEVICE Device name that uniquely identifies the device. (See Appendix C for additional information)

Supported devices

The following table defines the devices supported by this command. Included is the name of the device and the associated literal.

Prompts

Prompts appear for the remaining parameters after the command is entered verified. Since each device has a particular set of parameters, a different set of prompts exists for each device. Table 3-1 lists each device with the associated prompts.

Device Literal

Base Site Processor, BSC BSP

Cabinet CAB

Cage CAGE

Generic Clock GCLK

Generic Processor GPROC

KiloPort Switch KSW

Mutliple Serial Interface MSI

Message Transfer Link MTL

Operations and Maintenance Link OML

Radio System Link RSL

Transcoder BSC Link XBL

Transcoder XCDR

68P81132E13-O

10/3/02-GR

3-12


equip_device

You may abort a command at any time by typing done in response to any prompt. If a parameter is optional, there is no need to enter any data in response to the prompt.

NOTE

The cage number (ID) must be the same as the setting on the LANX card. Valid identifiers for a BSC cage are 0 through 5. The first two BSC cages must be numbered 0 and 1, respectively. If there is only one BSC cage in the system, it must be cage number 0.

Cage numbers 2 through 5 can be used for additional BSC cages.

Table 3-1 Prompts for the equip_device command

Prompt Optional Valid Entry Default

BSP (Base Site Processor, BSC)

Enter the BSP identifier: N 0 none

Enter remote site IDs this BSP may manage: Y 0 none

Enter the maximum MTLs this BSP may manage:

Y 0 none

Enter the XBLs ids this BSP may manage: (Enter carriage return if no XBL to be configured on BSP.)

Y 0-31...0-31 none

CAB (Cabinet)

Enter the CABINET identifier: N 0 to 2 none

CAGE (Cage)

Enter the identifier for the CAGE: N 0 to 5 none

Enter the KSW pair that manages the CAGE: N 0 to 3 none

Enter the KSWX connecting cage to KSW for TDM 0:

Y 0 to 5 none

Enter the KSWX connecting cage to KSW for TDM 1:

Y 0 to 5 none

Enter the cabinet to which the cage belongs: N 0 to 2 none

68P81132E13-O

10/3/02-GR

3-13


equip_device

GCLK (Generic Clock)

(Note: GCLK device identifier 1 is only for enhanced systems.)

Enter the device identifier for the GCLK: N 0 or 1 none

Enter the cage number: N 0 none

Enter the slot number: N 5 or 3 none

GPROC (Generic Processor)

Enter the GPROC identifier: N 0 to 31 none

Enter the cage number: N 0 to 5 none

Enter the slot number: N 18 to 25 none

KSW (Kilo-port Switch)

(Note: If 2nd KSW identifier is 0, slot number must be 27. If 2nd KSW identifier is 1, slot number must be 1.)

Enter the 1st KSW identifier: N 0 to 3 none

Enter the 2nd KSW identifier: N 0 to 1 none


Enter the slot number: N 1 or 27 none

MSI (Multiple Serial Interface Board)

Enter the MSI identifier: N 0 to 71 none



MTL (Message Transfer Link)

Enter the device identification for this MTL: N 0 to 15 none

Enter the MSI ID on which the SPAN link will be located:

N 0 to 71 none

Enter device ID for the SPAN Link: N 0 to 1 none

Enter the timeslot on the SPAN Link where this device appears:

N 0 to 23 (T1)

0 to 31 (E1)

none

Table 3-1 Prompts for the equip_device command (continued)


68P81132E13-O

10/3/02-GR

3-14


equip_device

OML (Operations and Maintenance Link)

(Note: OML type 0 needs to be configured to the MSI in slot 16 of the master cage)

Enter the OML link type: N 0 or 1 none

Enter the MSI ID on which the SPAN Link will be located:

N 0 to 71 none


Enter the timeslot (or starting timeslot) on the SPAN Link where this device appears:

N 0 to 23 (T1)

0 to 31 (E1)

none

Enter channel rate of E-OML. (Enter 1-6 Enhanced, or 1-3 Basic.) (This prompt is for E-OML only). Enter 1 for 64kbps, 2 for 128 kbps, ...6 for 384kbps.

Y 1 to 6 (Enhanced) 1 to 3 (Basic)

1

RSL (Radio System Link)

Enter the EBTS site number for the RSL: N 1 to 80 none

Enter the RSL link type: N 0 to 1 none


N 0 to 71 none


Enter the timeslot (or starting timeslot) on the SPAN Link where this device appears:

N 0 to 23 (T1)

0 to 31 (E1)

none

XBL (Transcoder BSC Link)

CP’s and E-CP’s maximum limit is 8 XBLs.RXCDR’s maximum limit is 32 XBLs.Between each CP/RXCDR (E-CP/E-RXCDR) pair, only 4 XBLs can be equipped.

Enter the device ID for the XBL: N 0 to 31 none


N 0 to 71 none


Enter the timeslot on the SPAN Link where this device appears:

N 0 to 23 (T1)

0 to 31 (E1)

none

Enter the remote site ID:

There can not be more than 5 remote site idsused in oneCP or E-CP.

N 1 to 255 none



68P81132E13-O

10/3/02-GR

3-15


equip_device

ExampleThis example adds the GCLK, a BSC device, to the FM portion of the CM database. equip_device GCLK

Enter dev ice ident i f ica t ion for the GCLK:0Enter cage number:0Enter s lo t number :5

XCDR (Remote Transcoder)

Enter the XCDR identifier: N 0 to 54 none



Enter the XCDR type (3to1/6to1/dual_24/dual_48):

N 3to1 or6to1 ordual_24 or dual_48

none



68P81132E13-O

10/3/02-GR

3-16


equip_function

equip_function

Description

Assigns functionality to a device in the fault management portion of the CM database.

NOTE

For additional information on supported functions, refer to Appendix C – “Device and function definitions.”

Format

equip_function <FUNCTION>


✔ ✔ ✔ ✔



Related commands disp_func_stat on page 4-47

disp_function on page 4-49

disp_lcf on page 4-60

68P81132E13-O

10/3/02-GR

3-17


equip_function

Parameters

NOTE

The FUNCTION parameter must be entered in uppercase letters. LCF function is allowed on E-RXCDR system to equip XBL link(s). LCF cannot be equipped on RXCDR. OMF function must be added in all system configurations.

FUNCTION Name that uniquely identifies the function. Functions that may be equipped are detailed in the following pages.

Supported functions

The following table defines the functions supported by this command. Included is the name of the function and the associated literal.

Prompts

Each function has its own set of parameters; therefore, a different set of prompts exists for each possible function. In the following table, each function name appears in italics, with prompts for that function immediately following.

You may abort this command at any time by typing done in response to any prompt.

Function Literal

Logical Control Function LCF

Operation and Maintenance Function OMF

68P81132E13-O

10/3/02-GR

3-18


equip_function

Prompt OptionalValid Entry

Default

LCF (Link Control Function, BSC)

Enter the function ID for the LCF:

0 to 19 none

Enter the number of MTLs the LCF can manage:

Note: MTL IDs are not prompted on E-RXCDR.

✔ 0 to 2 none

Enter the site IDs for the LCF:

Note: If the number of MTLs entered is 0, then up to 12 (for E-BSC) or 7 (for BSC) site IDs is allowed. If the number of MTLs is 1, only 5 site IDs are allowed. If the number of MTLs is 2, only 3 site IDs is allowed. Site IDs are not prompted on E-RXCDR.

✔ 0-80...0-80 none

Enter the XBL IDs:

(Enter a carriage return if no XBLs will be configured.)

Note: This prompt appears only on E-BSC and E-RXCDR systems.

✔ 0-31...0-31 none

OMF (Operation and Maintenance Function)

Enter XBL IDs:

(Enter a carriage return if no XBLs will be configured.)

Note: If E-OML is configured to 6 DSOs, then no XBLs can be equipped to this function.

✔ 0-31 ... 0-31 none

68P81132E13-O

10/3/02-GR

3-19


equip_function

Example 1

This example adds an LCF to the FM portion of the CM database on a BSC system.

equip_function LCF

Enter the funct ion ID for the LCF: 0

Enter the number of MTLs the LCF can manage: 0

Enter the s i te IDs for the LCF: 0

Example 2

This example adds an LCF function to the FM portion of the CM database on an E-BSC system.

equip_function LCF

Enter the funct ion ID for the LCF: 0

Enter the number of MTLs the LCF can manage: 0

Enter the s i te IDs for the LCF: 0

Enter the XBL IDs (EnterCarriage Return if no XBLs will be configured:2 3

Example 3

This example adds an LCF function to the FM portion of the CM database on an E-RXCDR system.

equip_function LCF

Enter the function ID for the LCF: 1

Enter the XBL IDs (Enter carriagereturn if no XBLs will be configured:2 3

Example 4

This example adds an OMF function to the FM portion of the CM database on either an E-BSC or E-RXCDR system.

equip_function OMF

Enter the XBL IDs (Enter carriagereturn if no XBLs will be configured:2 3

68P81132E13-O

10/3/02-GR

3-20


lock_device

lock_device

Description

Locks the specified device from further use. This command is only valid when the device is in the unlocked state. The devices supported by this command are listed on the following pages.

NOTE


Format

lock_device <DEVICE> <device_id1> <device_id2> <device_id3>


✔ ✔ ✔ ✔


Classification RC

Related commands equip_device on page 3-11




68P81132E13-O

10/3/02-GR

3-21


lock_device

Parameters

NOTE



device_id1 First device identifier; this definition varies with each device. (See Appendix C for additional information)

device_id2 Second device identifier; this definition varies with each device. (See Appendix C for additional information)

device_id3 Third device identifier; this definition varies with each device. (See Appendix C for additional information)

Supported devices


Device Literal

Clock Bus CBUS

Generic Clock GCLK


Kiloport Switch KSW

Local Area Network LAN




68P81132E13-O

10/3/02-GR

3-22


lock_device

Example 1

This example locks an MSI, with an ID of 1, at the BSC from further use.

lock_device MSI 1 0 0


Example 2

This example allows the CBUS device to transition to a lock state.

lock_device CBUS 0 1 0


Individual Span Line SPAN

Time Division Multiplex Bus TBUS


Transcoder XCDR

Parameter: Value:

<DEVICE> MSI

<device_id1> 1

<device_id2> 0

<device_id3> 0

Device Literal

68P81132E13-O

10/3/02-GR

3-23


lock_device


Parameter: Value:

<DEVICE> CBUS

<device_id1> 0

<device_id2> 1

<device_id3> 0

68P81132E13-O

10/3/02-GR

3-24


phase_locking

phase_locking

Description

Turns phase lock on or off, or displays the current status of the GCLK phase lock.

Format

phase_locking <mode>

Parameters

mode on Turns GCLK phase lock on.

off Turns GCLK phase lock off.

query Displays status of GCLK phase lock.

Example 1

This example displays the current status (T1 Mode).

phase_locking query

GCLK Locking Mode Locked T1 Ref.ID Sta tus

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 ON Locked YES RUNNING T 1 1 1 0 ACTIVE

1 ON Locking NO RUNNING T 1 1 1 0 STANDBY


✔ ✔ ✔ ✔



Related commands set_span_clk_ref on page 2-77

68P81132E13-O

10/3/02-GR

3-25


phase_locking


Example 2

This example displays the current status (E1 Mode).

phase_locking query

GCLK Locking Mode Locked Ref. ID Sta tus

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 ON Locking YES RUNNING E1 0 0 0 STDBY

1 ON Locking YES RUNNING E1 0 0 0 ACTIVE

Bits Flag: Span is NOT connected to BITS.


Parameter Value

<mode> query

Parameter Value

<mode> query

68P81132E13-O

10/3/02-GR

3-26


reset_bsc

reset_bsc

DescriptionForces the Initialization Process (IP) to reset the entire BSC. This command can be used after the sysgen_mode on command is executed. See the Note on page 2-83.

This command may also be used in extreme cases to recover a BSC. A sysgen_mode off command followed by a reset_bsc command reinitializes the BSC system, without clearing the system database object nor re–parsing the Genesis database script.

NOTE

If the mmi_spt.004 object (the Genesis database script object) resides on the system, the BSC will rebuild database.002 object (the system database) from the mmi_spt.004 object. If the mmi_spt.004 object does not reside on the system, the BSC will request a download of the mmi_spt.004 object from the OMC.

Format

reset_bsc

ParametersNone.

Example

reset_bsc

WARNING: Si te reboots now! Status = 0


✔ ✔ ✔ ✔



Related commands sysgen_mode on page 2-83

68P81132E13-O

10/3/02-GR

3-27


restart_mon

restart_mon

Description

This command restarts the monitor process either on the local GPROC or a specified GPROC. This command is used to free up locked monitor terminal. If both the MMI and monitor terminals on a particular GPROC are locked up, the command can be issued from any other GPROC’s MMI terminal by specifying a CPU number as the parameter.

Format

restart_mon [cpu_num]

Parameters

cpu_num CPU number (in hexadecimal) of the GPROC on which monitor process needs to be restarted.

Example 1

To free up locked monitor terminal on current GPROC, issue the command without any parameter as follows:

restart_mon


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

3-28


restart_mon

Example 2

To free up locked monitor terminal on BSP GPROC (0115h)from a non-BSP GPROC’s MMI terminal if the BSP’s MMI terminal is locked up, issue the command as follows:

restart_mon 0115h

68P81132E13-O

10/3/02-GR

3-29


unlock_device

unlock_device

Description

Unlocks a specified device from the locked state to free it from use. The devices supported by this command are listed on the following pages.

NOTE


Format

unlock_device <DEVICE> <device_id1> <device_id2> <device_id3>


✔ ✔ ✔ ✔


Classification RC


lock_device on page 3-21



68P81132E13-O

10/3/02-GR

3-30


unlock_device

Parameters

NOTE






Supported devices


Device Literal

Clock Bus CBUS

Generic Clock GCLK


Kiloport Switch KSW







Time Division Multiplex Bus TBUS


Transcoder XCDR

68P81132E13-O

10/3/02-GR

3-31


unlock_device

Example 1

This example unlocks a SPAN device, with an ID of 000, at the BSC.

unlock_device SPAN 0 0 0


Example 2

This example allows the CBUS device to transition to an unlock state.

unlock_device CBUS 0 1 0


Parameter: Value:

<DEVICE> SPAN

<device_id1> 0

<device_id2> 0

<device_id3> 0

Parameter: Value:

<DEVICE> CBUS

<device_id1> 0

<device_id2> 1

<device_id3> 0

68P81132E13-O

10/3/02-GR

3-32

4

4 Display

Introduction

The BSC display commands allow the user to display:

❐ administrat\ive state of devices and various functions

❐ information from the Configuration Management (CM) database

❐ current software version

❐ time

❐ alarms


10/3/02-GR

4-1

CHAPTER 4 - DISPLAY BSC MMI Commands

disp_act_cells

disp_act_cells

Displays all of the configured cells on the BSC and their current Administrative and Operational status. The type of channel mapping mode (trunked or one-to-one) is also displayed.

Format

disp_act_cells

Parameters

None.

Example

disp_act_cells

C e l l U s a g e

EBTS Site Number Local Cel l ID Sta tus subra te

t runk ing_ f lag= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

1 0 BLOCKED ON

2 1 0 BLOCKED ON


✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-2

BSC MMI Commands CHAPTER 4 - DISPLAY

disp_audit_sched

disp_audit_sched

Description

Displays audit information for all scheduled devices.

Format

disp_audit_sched

Parameters

None.

Example

disp_audit_sched

Device Aud i t Type S ta r t End Interva l

GCLK gc lk_s ta tus 0 0 : 0 1 2 3 : 5 9 0 0 : 1 0

KSW safe 0 0 : 0 1 2 3 : 5 9 0 0 : 1 0

MSI safe 0 0 : 0 1 2 3 : 5 9 0 0 : 1 0

XCDR safe 0 0 : 0 1 2 3 : 5 9 0 0 : 1 0

XCDR vp_aud i t 0 1 : 0 0 0 1 : 4 5 0 0 : 3 0

GPROC safe 0 0 : 0 1 2 3 : 5 9 0 1 : 0 0

TBUS ex t_ lpbk 0 3 : 3 5 0 3 : 3 5 0 0 : 0 0

TDM conn_ tes t 0 3 : 0 0 0 3 : 0 0 0 0 : 0 0

CBUS safe 0 0 : 0 1 2 3 : 5 9 0 0 : 0 2


✔ ✔ ✔ ✔



Related commands chg_audit_sched on page 5-6

68P81132E13-O

10/3/02-GR

4-3


disp_auto_vp_flag

disp_auto_vp_flag

Description

Displays the current state of the auto VP audit flag.

Format

disp_auto_vp_flag

Parameters

None.

Example

disp_auto_vp_flag

The auto_vp_f lag is OFF.


✔ ✔ ✔ ✔



Related commands auto_vp_flag on page 5-2

68P81132E13-O

10/3/02-GR

4-4


disp_bsc_stat

disp_bsc_stat

Description

Displays the status for all equipped devices in the BSC, as well as the reasons for disabled/enabled devices.

Format

disp_bsc_stat

Parameters

None.


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-5


disp_bsc_stat

Example

disp_bsc_stat

GPROC 0 0 0 (GPROC) BUSYUNLOCKED

GPROC 1 0 0 (GPROC) ENABLED UNLOCKED No funct ion ass igned

GPROC 2 0 0 (EGPROC) BUSYUNLOCKED

GPROC 3 0 0 (EGPROC) ENABLED LOCKED

BSP 0 0 0 BUSY UNLOCKED

MSI 0 0 0 BUSY UNLOCKED

MSI 1 0 0 BUSY UNLOCKED

MSI 6 0 0 DISABLED UNLOCKED Hardware Board Out

XCDR 0 0 0 (DUAL_48) BUSY UNLOCKED

XCDR 1 0 0 (DUAL_24) BUSY UNLOCKED

XCDR 2 0 0 (3TO1) BUSY UNLOCKED

XCDR 3 0 0 (6TO1) BUSY UNLOCKED

SPAN 0 0 0 BUSY UNLOCKED

SPAN 2 0 0 DISABLED UNLOCKED Alarm de tec ted

SPAN 2 1 0 BUSY UNLOCKED

SPAN 6 0 0 DISABLED UNLOCKED MSI locked or disabled

OML 0 0 0 BUSY UNLOCKED

GCLK 0 0 0 DISABLED UNLOCKED GCLK is warming up

GCLK 1 0 0 BUSY UNLOCKED GLCKis Phase Locked

KSW 0 0 0 BUSY UNLOCKED

CAGE 0 0 0 BUSY UNLOCKED

CAGE 1 0 0 BUSY UNLOCKED

CAB 0 0 0 ENABLED UNLOCKED

SITE 0 0 0 BUSY UNLOCKED

XBL 0 0 0 ENABLED UNLOCKED Wait ing for SABME

XBL 1 0 0 BUSY UNLOCKED

XBL 2 0 0 DISABLED UNLOCKED No GPROC available

OMF 0 0 0 BUSY EQUIPPED

LCF 0 0 0 BUSY EQUIPPED

LCF 1 0 0 ENABLED EQUIPPED

68P81132E13-O

10/3/02-GR

4-6


disp_bsp

disp_bsp

Description

Displays XBL ids equipped on the BSP and the associated GPROC id.

Format

disp_bsp

Parameters

None.

Example

disp_bsp

BSP id GPROC id GPROC Type Cage Slot XBL(s)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 EGPROC 0 2 0 none


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-7


disp_cell

disp_cell

Description

Displays all programmable parameters for a specified cell.

Format

disp_cell <cell_id>

Parameters

cell_id 0-239 local cell ID of the cell to be displayed.

Example

This example shows programming parameters for Cell 0.

disp_cell 0

Primary ESMR Cel l ID = 0 0 1 0 1 1 3 1

Secondary ESMR Cel l ID = 0 0 1 0 1 1 2 1

over load_s teps = 10

in t ra_ce l l_handover_a l lowed = 1

in ter_ce l l_handover_a l lowed = 1

ext r l_handover_a l lowed = 0

number _o f_pre fe r red_ce l l s = 6

handover_requ i red_re jec t_swi tch = 0

subra te_ t runk ing_ f lag = on

ssm_t imer_va lue ,0 = 30000

ccch_con f = 1

bs_ag_b lks_res = 1


✔ ✔




68P81132E13-O

10/3/02-GR

4-8


disp_channel

disp_channel

Description

Displays connections between all sites (MSC and BSC).

Format

disp_channel

Parameters

None.


✔






68P81132E13-O

10/3/02-GR

4-9


disp_channel

Example

disp_channel

S o u r c e Dest inat ion

MSI SPAN TS Grp MSI SPAN TS CIRCUIT_ID REMOTE_SITE_ ID

3 0 3 0 1 0 1 1 5 0 5 5

3 0 3 1 1 0 1 2 5 1 5 5

3 0 3 2 1 0 1 3 5 2 5 5

3 0 3 3 1 0 1 4 5 3 5 5

5 0 3 0 1 0 1 8 6 0 5 5

5 0 3 1 1 0 1 9 6 1 5 5

5 0 3 2 1 0 2 0 6 2 5 5

5 0 3 3 1 0 2 1 6 3 5 5

68P81132E13-O

10/3/02-GR

4-10


disp_checksum

disp_checksum

Description

Displays the ROM checksum, represented as a hexadecimal number. This command is typically used by field technicians or installers.

Format

disp_checksum

Parameters

None.

Example

disp_checksum

U74 : eee f02 U95 : 1922168


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-11


disp_cic_conn

disp_cic_conn

Description

Displays terrestrial circuit status and connection information.

Format

For E-BSC System:

disp_cic_conn <all> | <Remote_site=<remote_site_id>

For E-RXCDR System:

disp_cic_conn <all> | <msi_id> [span] [Remote_site=remote_site_id] | <Remote_site=remote_site_id> | <summary>

Parameters

all Displays information for all circuits.

msi_id 0-71 Device ID of the MSI card

span 0-1 Device ID of the SPAN line

remote_site_id 1-255 Remote site ID associated with CIC

summary Displays the summary of the circuit’s state. This parameter is used only in E-RXCDR systems.


✔ ✔




68P81132E13-O

10/3/02-GR

4-12


disp_cic_conn

Example 1:

This example shows all CICs that are in span link 13 0 associated with remote site id 54 for an E-RXCDR system.

disp_cic_conn 13 0 Remote_site=54

CIRCUIT REMOTE SITE MSI SPAN TS STATE SCCP

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

3 0 0 5 5 4 1 3 0 1 2 BUSY 0 3 0 0 8 4 h

3 0 0 6 5 4 1 3 0 1 3 IDLE f f f f f f h

3 0 0 7 5 4 1 3 0 1 4 IDLE f f f f f f h

Example 2:

This example shows all CICs associated with remote site id 51 for an E-BSC system.

disp_cic_conn Remote_site=51

CIRCUIT REMOTE SITE

= = = = = = = = = = = = = = = = = =

1 2 5 0 1 5 1

1 2 5 0 2 5 1

1 2 5 0 3 5 1

1 2 5 0 4 5 1

1 2 5 0 5 5 1

1 2 5 0 6 5 1

1 2 5 0 7 5 1

1 2 5 0 8 5 1

1 2 5 0 9 5 1

1 2 5 1 0 5 1

68P81132E13-O

10/3/02-GR

4-13


disp_cic_conn

Example 3:

This example shows all CICs that are in span link 0 0 for an E-RXCDR system.

disp_cic_conn 0 0

CIRCUIT REMOTE SITE MSI SPAN TS STATE SCCP

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

1 2 5 0 1 5 1 0 0 5 IDLE f f f f f f h

1 2 5 0 2 5 1 0 0 6 IDLE f f f f f f h

1 2 5 0 3 5 1 0 0 7 IDLE f f f f f f h

1 2 5 0 4 5 1 0 0 8 IDLE f f f f f f h

1 2 5 0 5 5 1 0 0 9 IDLE f f f f f f h

1 2 5 0 6 5 1 0 0 1 0 IDLE f f f f f f h

1 2 5 0 7 5 1 0 0 1 1 IDLE f f f f f f h

1 2 5 0 8 5 1 0 0 1 2 IDLE f f f f f f h

1 2 5 0 9 5 1 0 0 1 3 IDLE f f f f f f h

1 2 5 1 0 5 1 0 0 1 4 IDLE f f f f f f h

1 2 5 1 1 5 1 0 0 1 5 IDLE f f f f f f h

1 2 5 1 2 5 1 0 0 1 6 IDLE f f f f f f h

1 2 5 1 3 5 1 0 0 1 7 IDLE f f f f f f h

1 2 5 1 4 5 1 0 0 1 8 IDLE f f f f f f h

1 2 5 1 5 5 1 0 0 1 9 IDLE f f f f f f h

1 2 5 1 6 5 1 0 0 2 0 IDLE f f f f f f h

1 2 5 1 7 5 1 0 0 2 1 IDLE f f f f f f h

1 2 5 1 8 5 1 0 0 2 2 IDLE f f f f f f h

1 2 5 1 9 5 1 0 0 2 3 IDLE f f f f f f h

Example 4:

This example shows a summary of the states for all circuits.

disp_cic_conn summary

IDLE CIC(s) ACTIVE CIC(s) BLOCKED CIC(s) ACTIVE-RESV CIC(s)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 5 7 0

68P81132E13-O

10/3/02-GR

4-14


disp_cic_use

disp_cic_use

Description

Displays the CIC states of the specified remote site. If a remote site is not specified, then the command is assumed to be entered at a co-located system.

Format

disp_cic_use <remote_site_id>

Parameters

remote_site_id 1-255 Remote site identifier

Example 1:

This example shows the CIC state when executing this command from the CP BSC.

disp_cic_use 50

CIC Identi f ier CIC State SCCP

1 IDLE 0 x f f f f f f h








✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-15


disp_cic_use

Example 2:

This example shows a typical response when executing this command from a remote transcoder (RXCDR).

disp_cic_use 51

CIC Identi f ier

6

7

8

9

1 0

1 1

1 2

NOTE: To f ind out CIC State, run disp_cic_use in CP BSC

68P81132E13-O

10/3/02-GR

4-16


disp_circuit

disp_circuit

Description

Displays all terrestrial circuits for the specified MSI and SPAN line or both SPAN lines on the specified MSI. The devices supported by this command are listed on the following pages.

Format

disp_circuit <msi_id> [<span_id>]

Parameters

msi_id 0-71 Device ID of the MSI on which SPAN line is located.


Example

disp_circuit 13 0

CIC MSI SPAN TS Grp––– ––––– ––––––––– ––––––– –––––––

3 0 0 5 1 3 0 1 2 0

3 0 0 6 1 3 0 1 3 0

3 0 0 7 1 3 0 1 4 0


✔






disp_cic_use on page 4-15

68P81132E13-O

10/3/02-GR

4-17


disp_dev_stat

disp_dev_stat

Description

Displays the state of a specific device and the length of time the device is in that state. It also displays two reasons (console reason and software reason) if this device is out of service.

The devices supported by this command are listed on the following pages.

NOTE

The “time of last transition” in the output should be interpreted as Greenwich Mean Time (GMT). Use the local time zone when interpreting the output times.

NOTE


Format

disp_dev_stat <DEVICE> [<device_id1> <device_id2> <device_id3>]


✔ ✔ ✔ ✔


Classification RC





68P81132E13-O

10/3/02-GR

4-18


disp_dev_stat

Parameters

NOTE

The DEVICE parameter must be entered in uppercase letters. If device_id1 thru device_id3 are not entered, it will default to display the list of device information for that DEVICE LITERAL.

DEVICE Device name that uniquely identifies the device. (Appendix C for additional information)

device_id1 First device identifier. This definition varies with each device.

device_id2 Second device identifier. This definition varies with each device.

device_id3 Third device identifier. This definition varies with each device.

Supported devices


Device Literal

Base Site Processor BSP

Cabinet CAB

Cage CAGE

Clock Bus CBUS

Generic Clock GCLK


KiloPort Switch KSW




68P81132E13-O

10/3/02-GR

4-19


disp_dev_stat

Example 1

This example shows the status of all GPROCs that are cofigured to a BSC/RXCDR system.

disp_dev_stat GPROC

GPROC Cage Slo t S ta te T ime o f l as t t rans i t i on GPROC Type

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 0 2 0 BUSY / UNLOCKED W e d D e c 1 3 1 7 : 3 4 : 3 7 2 0 0 0 GPROC




NOTE

All times are in GMT fomat.




EBTS Site SITE


Cage TDM Bus TBUS


Transcoder XCDR

Parameter: Value:

<DEVICE> GPROC

Device Literal

68P81132E13-O

10/3/02-GR

4-20


disp_dev_stat

Example 2

This example shows the status of all OMLs that are configured to the system.

disp_dev_stat OML

GPROC Time o f l as t OML RateOML Cage/S lo t s t a t e t rans i t i on (Kbps )

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 3 / 0 / 2 3 BUSY/UNLOCKED D e c 1 3 1 7 : 3 5 : 5 2 2 0 0 0 6 4

1 0 0 3 / 0 / 2 3 BUSY/UNLOCKED D e c 1 3 1 7 : 3 5 : 5 2 2 0 0 0 6 4


Example 3

This example shows the status of all XCDRs that are configured to the system.

disp_dev_stat XCDR

XCDR Sta te T ime o f l as t t rans i t i on XCDR Type

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 DISABLED/UNLOCKED M o n A u g 4 2 2 : 2 4 : 5 1 1 9 9 8 DUAL_48

Reason: Wrong XCDR board

Wrong XCDR board

2 0 0 BUSY/UNLOCKED M o n A u g 2 4 1 0 : 0 4 : 4 6 3TO1


Parameter: Value:

<DEVICE> OML

Parameter: Value:

<DEVICE> XCDR

68P81132E13-O

10/3/02-GR

4-21


disp_device

disp_device

Description

Displays the state and configuration information for either all the devices or a specified device. The configuration information represents data entered when the device was equipped. This command also displays the reason if the device is out of service.

Entering an operational or administrative state restricts the list to those devices whose state matches the input state.

The devices supported by this command are listed on the following pages.

NOTE


When some devices are equipped, a device ID is the only information requested. For other devices, no information is requested. When disp_device is executed for a device (where no information is requested), additional data is not displayed.

If a device prompt was displayed (in an equip_device command) and the user entered a carriage return, no data for that (device) prompt is displayed (when using disp_device).


✔ ✔ ✔ ✔


Classification RC





68P81132E13-O

10/3/02-GR

4-22


disp_device

Format

disp_device <all> | <DEVICE> [<device_id1> <device_id2> <device_id3>]

ordisp_device <all | DEVICE> [oper_state] [admin_state]

Parameters

NOTE

The DEVICE parameter must be entered in uppercase letters. If parameter “all” is entered, the BSC will display all of the devices configured in the system. If parameter all is followed by a specific operational state and/or administrative state, then all the devices whose state(s) match the input state(s) will be displayed.

all Displays all of the devices configured in the system.


device_id1 First device identifier; this definition varies with each device.

device_id2 Second device identifier; this definition varies with each device.

device_id3 Third device identifier; this definition varies with each device.

oper_state Operational states are disabled, enabled, or busy. States can be abbreviated to a single character (i.e., “busy” can be busy, bus, bu, or b.

admin_state Administrative statess are locked and unlocked. States can be abbreviated to a single character.

68P81132E13-O

10/3/02-GR

4-23


disp_device

Supported devices


Device Literal

Base Site Processor BSP

Cabinet CAB

Cage CAGE

Clock Bus CBUS

Generic Clock GCLK


Kiloport Switch KSW


Multiple Serial Interface MSI




EBTS Site SITE


Cage TDM Bus TBUS


Remote Transcoder XCDR

68P81132E13-O

10/3/02-GR

4-24


disp_device

Example 1

This example shows state and configuration information on all GPROCs in the system.

disp_device GPROC

GPROC Sta te cage s lo t GPROC Type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED 0 2 0 EGPROC

1 0 0 ENABLED/UNLOCKED 1 1 9 EGPROC Standby device


3 0 0 ENABLED/UNLOCKED 1 1 9 GPROC Standby device


5 0 0 ENABLED/UNLOCKED 2 1 9 GPROC Standby device


Example 2

This example shows state and configuration information on all XCDRs in the system.

disp_device XCDR

XCDR Sta te cage s lo t XCDR type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 DISABLED/UNLOCKED 0 1 8 DUAL_48 Wrong XCDR board

2 0 0 BUSY/UNLOCKED 0 2 2 3TO1

6 0 0 DISABLED/UNLOCKED 1 2 2 3TO1 Hardware board out



Parameter: Value:

<DEVICE> GPROC

Parameter: Value:

<DEVICE> XCDR

68P81132E13-O

10/3/02-GR

4-25


disp_device

Example 3

This example shows state and cofiguration information on all OMLs in the system.

NOTE

If the system is in the SYSGEN mode, the “state” column will display “N/A”.

disp_device OML

OML id OMF/GPROC/ S ta te Rate MSI/SPAN/TS LinkCage/S lo t (Kbps ) Type

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 0 / 3 / 0 / 2 3 BUSY/UNLOCKED 6 4 0 / 0 / 3 B-OML

1 0 0 0 / 3 / 0 / 2 3 BUSY/UNLOCKED 6 4 0 / 0 / 4 E-OML


Example 4

This example shows state and configuration information on all XBLs in the system.

disp_device XBL

XBL id Func/GPROC/ Remote S ta te MSI/SPAN/TSCage/S lo t Si te Id

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 L C F 0 / 4 / 0 / 2 2 5 2 BUSY/UNLOCKED 0 / 0 / 1 2

1 0 0 B S P 0 / 0 / 0 / 2 0 5 2 BUSY/UNLOCKED 0 / 0 / 1 3


Parameter: Value:

<DEVICE> OML

Parameter: Value:

<DEVICE> XBL

68P81132E13-O

10/3/02-GR

4-26


disp_device

Example 5

This example shows state and configuration information on all RSLs in the system.

disp_device RSL

RSL LCF GPROC/ S ta te MSI/SPAN/TS Linkid id Cage/S lo t Type

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

2 0 0 2 none DISABLED/UNLOCKED 4 / 0 / 0 MOBISNo GPROC available




2 1 0 2 none DISABLED/UNLOCKED 4 / 0 / 1 SNMPNo GPROC available


Parameter: Value:

<DEVICE> RSL

68P81132E13-O

10/3/02-GR

4-27


disp_device

Example 6

This example shows state and configuration information on all CAGEs in the system.

disp_device CAGE

cage id KSW KSWX KSWX Cab CardsTDM 0 TDM 1 Id

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 0 0 0 0 GPROC: 0,1,2,3

XCDR: none

MSI : 0 ,1 ,6 ,5

GCLK: 0

KSW: 0

1 0 0 0 0 0 0 GPROC: 7,8,9,4

XCDR: none

MSI: 4

GCLK: none

KSW: none


Parameter: Value:

<DEVICE> CAGE

68P81132E13-O

10/3/02-GR

4-28


disp_device

Example 7

This example shows state and configuration information on all SPANs in the system.

disp_device SPAN

SPAN STATE MSI MSI Reasoncage s lo t L e n g t h ( f t )

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 DISABLED/UNLOCKED 0 1 6 0 - 7 6 8 A la rm de tec ted

0 1 0 DISABLED/UNLOCKED 0 1 6 1 3 1 - 9 1 7 A la rm de tec ted

1 0 0 DISABLED/UNLOCKED 0 1 4 2 6 2 - 1 0 4 8 A la rm de tec ted






NOTE

The output shown in the above example is produced for a T1 system.


Parameter: Value:

<DEVICE> SPAN

68P81132E13-O

10/3/02-GR

4-29


disp_device

Example 8

This example shows all the busy GPROCs and their configuration information on the system.

disp_device GPROC busy

GPROC STATE cage s lo t GPROC Type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


2 0 0 BUSY/UNLOCKED 1 2 0 GPROC


Lis t i s con f ined to “busy ” dev i ces .

Example 9

This example shows all the busy and unlocked GPROCs and their configuration information on the system.

disp_device GPROC busy unlocked

GPROC STATE cage s lo t GPROC Type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =




L is t i s con f i ned to “busy ” & “un locked” dev i ces .

68P81132E13-O

10/3/02-GR

4-30


disp_device

Example 10

This example shows all the busy GPROCs and their configuration information on the system.

disp_device all busy

GPROC Sta te cage s lo t GPROC Type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =




Lis t i s con f ined to “busy ” dev i ces .

BSP ID GPROC ID GPROC Type Cage Slo t Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 EGPROC 0 2 0 none

MSI S ta te cage s lo t Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED 0 1 6




1 2 0 0 BUSY/UNLOCKED 2 1 6


L is t i s con f ined to “busy ” dev i ces .

MSI MSISPAN Sta te cage s lo t Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =








68P81132E13-O

10/3/02-GR

4-31


disp_device

OML id OMF/GPROC/ S ta te MSI/SPAN/TS Rate LinkCage/S lo t (Kbps ) Type

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


GCLK Sta te cage s lo t Rev CLKX_slots Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

1 0 0 BUSY/UNLOCKED 0 3 9 3 GCLK is Phase Locked


KSW Sta te cage s lo t Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =





TBUS IDS Sta te Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED

1 0 0 BUSY/UNLOCKED

2 0 0 BUSY/UNLOCKED


CAGE ID S ta te KSW KSWX KSWX Cab CardsTDM1 Id

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED 0 0 0 0 GPROC: 0,1

XCDR: 0,1,2,3

MSI : 0 ,1 ,2 ,3

4 , 5 , 2 4 , 2 5

2 6 , 2 7

GCLK: 0

KSW: 0


XCDR: 4,5,6,7

MSI : 6 ,7 ,8 ,9

68P81132E13-O

10/3/02-GR

4-32


disp_device

1 0 , 1 1 , 2 8 , 2 9

3 0 , 3 1

GCLK: none

KSW: 1


XCDR: 8 ,9 ,10,11

MSI : 12 ,13 ,14 ,15

1 6 , 2 7 , 3 2 , 3 3

3 4 , 3 5

GCLK: none

KSW: 2


CABINET IDS Sta te Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


SITE ID S ta te Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED


XCDR Sta te cage s lo t XCDR_type Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

1 0 0 BUSY/UNLOCKED 0 2 1 DUAL_24





XBL id Func/GPROC/ Remote S ta te MSI/SPAN/TSCage/S lo t Si te Id

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


68P81132E13-O

10/3/02-GR

4-33


disp_device

CBUS IDS Sta te Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED

1 0 0 BUSY/UNLOCKED

2 0 0 BUSY/UNLOCKED


LAN IDS Sta te Reasons

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 0 BUSY/UNLOCKED


NOTE

The output shown in the example above is produced for an E1 system.

68P81132E13-O

10/3/02-GR

4-34


disp_dsp_reload

disp_dsp_reload

Description

Displays the current status of the DSP reload flag.

Format

disp_dsp_reload

Parameters

None.

Example

disp_dsp_reload

The dsp_reload_f lag is ON.


✔ ✔ ✔ ✔



Related commands set_dsp_reld_flag on page 2-75

68P81132E13-O

10/3/02-GR

4-35


disp_dte

disp_dte

Description

Displays the specified DTE addresses. This command used mainly by field technicians or installers.

Format

disp_dte [<link> <link_number>]

Parameters

link bsc The location of the Base Station Controller (BSC) link.

omcr The location of the Operations and Maintenance Center Radio Part (OMCR) link.

link_num 0-3 If the link is at the BSC, this is the range.

0-7 If the link is at the OMCR, this is the range.

NOTE

If parameters are not specified, all BSC and OMCR data is displayed.


✔ ✔ ✔ ✔



Related commands chg_dte on page 2-27

68P81132E13-O

10/3/02-GR

4-36


disp_dte

Example 1:

This example shows all DTE link addresses (in binary coded decimal).

disp_dte

BSS DTE addresses:

Add ress #0 : 31 , 60 , 10 , 01 , 31 , 51 , 00

Add ress #1 : 31 , 60 , 10 , 01 , 31 , 51 , 00

Add ress #2 : 31 , 60 , 10 , 01 , 31 , 51 , 00

Add ress #3 : 31 , 60 , 10 , 01 , 31 , 51 , 00

OMCR DTE addresses:

Add ress #0 : 31 , 00 , 00 , 00 , 00 , 00 , 27

Add ress #1 : 31 , 00 , 00 , 00 , 00 , 00 , 28

Add ress #2 : 31 , 00 , 00 , 00 , 00 , 00 , 29

Add ress #3 : 31 , 00 , 00 , 00 , 00 , 00 , 30

Add ress #4 : 31 , 00 , 00 , 00 , 00 , 00 , 45

Add ress #5 : 31 , 00 , 00 , 00 , 00 , 00 , 46

Add ress #6 : 31 , 00 , 00 , 00 , 00 , 00 , 47


Example 2:

This example shows the DTE link address and link numbers.

disp_dte bsc 2

DTE address fo r bsc l i nk 2 i s : 31 ,60 ,10 ,01 ,60 ,54 ,00

68P81132E13-O

10/3/02-GR

4-37


disp_ebts_dte

disp_ebts_dte

Description

Displays all EBTS and OMC DTE addresses for existing sites.

Format

disp_ebts_dte

Parameters

None.

Example

disp_ebts_dte

SITE NO. EBTS ADDR OMC ADDR–––––––– ––––––––––– ––––––––––

1 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 1 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

3 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 7 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

5 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 8 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

6 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 1 2 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

7 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 2 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

8 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 9 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

1 6 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 3 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

1 8 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 4 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

2 0 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 5 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

2 6 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 0 6 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

4 1 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 1 0 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h

4 2 3 1 h 6 0 h 1 0 h 0 1 h 4 1 h 5 5 h 1 1 h 3 1 h 6 0 h 1 9 h 0 1 h 1 0 h 4 1 h 6 3 h


✔ ✔



Related commands chg_dte on page 2-27

68P81132E13-O

10/3/02-GR

4-38


disp_element

disp_element

Description

Displays all of the configurable elements or the value of non-statistical or statistical elements in the CM database. Non-statistical elements are presented in the general command description of chg_element (non-statistical) and Appendix A.The statistical elements are presented in the Statistics chapter (in the description of chg_element) and Appendix B.

In these sections of the manual, note requirements for indexes and/or cell numbers.

Format

All Elements:

disp_element all

Non Statistical Elements:

disp_element <element_name> [,<index1>][,<index2>] [ [cell_number=<cell_number>] | [site=<site_number>] ](refer to Note below)

Statistical Elements:

disp_element <element_name> [,<index1>][,<index2>] [site=<site_number>]

NOTE

The cell_number parameter is required for elements which have a checkmark (✔) in Table 2-1 (All Configurable Elements). For all other elements (without ✔), the cell_number parameter is not required.


✔ ✔ ✔ ✔



Related commands chg_element on page 2-31

68P81132E13-O

10/3/02-GR

4-39


disp_element

Parameters

element_name String identifying the element in the CM database.

index1 Some elements require an index; they are highlighted with an asterisk in the table that follows. The value that this index represents, varies with the individual element name/parameter. The non-statistical use of index1 may be found in Appendix A. The statistical use of index1 may be found in the Statistics chapter description of chg_element. Note that this parameter requires a comma before the index number.

index2 Some elements may require a second index; they are highlighted in the Statistics chapter. This index may only be used with statistical element names. Normal and Weighted Distribution statistical element names also require the use of index2. For the complete list of statistical element names refer to the description of the chg_element command in the Statistics chapter.

cell_number 0-239 Number of the local cell I.D. identifying the cell in the CM database. Required for per cell parameters. They are highlighted by a checkmark in the table of element names in the command description of chg_element.

site_number 1-80 EBTS site number (used with omc_dte_addr and ebts_dte_addr only).

site_number 1-80 EBTS site number (used with omc_dte_addr and ebts_dte_addr only).

all String displaying all the configurable elements in alphabetical order.

Example 1:

This example shows the bit error rate loss threshold per day of 16 for site number 1.

disp_element ber_loss_daily site=1

ber loss da i ly = 16

68P81132E13-O

10/3/02-GR

4-40


disp_element

Example 2:

This example shows the high_watermark3to1 value is 90%.

disp_element high_watermark_3to1

h igh_wa te rmark_3 to1 = 90%

Example 3:

This example shows the subrate_trunking_flag for cell 5 is on.

disp_element subrate_trunking_flag cell_number = 5

subra te_ t runk ing_ f lag = on

Example 4:

This example shows all configurable elements being displayed.

disp_element all

ais_loss_oos al l_cel ls_ins

assgn_fa i l_sub_chan_conf ig assgn_fa i l_sub_chan_in_use

assgn_fa i l_sub_chan_unavai l audio_swi tch_delay

backup_bsp_mtp_enable ber_ loss_dai ly

ber_ loss_hour ly ber_ loss_oos

ber_ loss_res tore b lock_re t r ies_num

bs_ag_blks_res bsc_acces_delay

• •

• •

• •

Refer to the BSC Commands Manual for more informat ion.

Element names

Refer to the tables of element names shown in both, non-statistical and statistical applications of the chg_element command.

❐ Refer to Appendix A for additional information on non-statistical parameters.

❐ Refer to Appendix B for additional information on statistical parameters.

68P81132E13-O

10/3/02-GR

4-41


disp_env_alarm

disp_env_alarm

Description

Displays the current alarm status of Fan, Fan Fuse, and Power Supply.

Format

disp_env_alarm

Parameters

None.


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-42


disp_env_alarm

Example

This example shows the current alarm status on all cages in the system.

disp_env_alarm

IAR ALARM STATUS:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ALARM: DPSM No Board, LOC: cage 0, slot: 0, Right Power Supply

ALARM: DPSM No Board, LOC: cage 2, s lot : 0, Left Power Supply

IAR ALARM STATUS:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ALARM: DPSM No Board, LOC: cage 1, slot: 0, Right Power Supply

ALARM: DPSM No Board, LOC: cage 1, s lot : 0, Left Power Supply

NOTE

DPSM Slot Numbering: There are a possible of three DPSMs (Power Supplies) per cage. They are numbered from 0 to 2 with 0 being the right most slot and 2 being the left most slot.

FAN Slot Numbering:There are a possible of 6 Fan and 6 Fan fuses per Cabinet. They are numbered from 0 to 5. Numbers 0 through 2 map to fans in the lower cage and 3 through 5 map to fans in the upper cage. Fans 0 and 3 are the right most fans in their respective cages.

68P81132E13-O

10/3/02-GR

4-43


disp_equipment

disp_equipment

Description

Displays all equipment at a specified location in the CM database.

Format

disp_equipment

Parameters

None.

Devices

The following table describes the devices that may be displayed with the disp_equipment command. Equipment may vary by location. This table contains only devices supported by the current software load.


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-44


disp_equipment

Device Definition

BSP Base Site Processor, BSC

CAB CABinet

CAGE CAGE

GCLK Generic CLocK

GPROC Generic PROCessor, device used for functions

KSW Kilo-port SWitch

MSI Multiple Serial Interface board

MTL Message Transfer Link

OML Operations and Maintenance Link

RSL Radio System Link

XCDR Transcoder

SITE BSC Site

SPAN Span line on Multiple Serial Interface Board

XBL Remote Transcoder to BSC link.

Function Definition

LCF Link Control Function, BSC

OMF Operations and Maintenance Function

68P81132E13-O

10/3/02-GR

4-45


disp_equipment

Example

This example shows all equipment.

disp_equipment

device id cage s lo t- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

GPROC (EGPROC) 2 0 0 0 2 1

GPROC (GPROC) 4 0 0 0 1 8

GPROC (GPROC) 6 0 0 0 1 9

BSP 0 0 0 0 2 0

MSI 1 0 0 0 6

MSI 3 0 0 0 7

MSI 1 4 0 0 0 8

SPAN 1 0 0

SPAN 1 1 0

SPAN 3 0 0

SPAN 1 4 1 0

MTL 0 0 0

MTL 1 0 0

RSL 2 0 0

RSL 2 1 0

RSL 4 0 0

RSL 4 1 0

OML 0 0 0

OML 1 0 0

GCLK 0 0 0 0 3

KSW 0 0 0 0 1

CAGE 0 0 0

CAGE 1 0 0

CAB 0 0 0

SITE 0 0 0

XBL 2 0 0

LCF 0 0 0

LCF 1 0 0

LCF 2 0 0

LCF 3 0 0

68P81132E13-O

10/3/02-GR

4-46


disp_func_stat

disp_func_stat

Description

Displays the current status of the specified function. This helps determine if the specified function is in-service (INS), out-of-service (OOS), locked, etc. Information about the length of time the specified function has been INS, OOS, locked, etc. is also displayed.

NOTE

The “time of last transition” in the output should be interpreted as Greenwich Mean Time (GMT). Use the local time zone when interpreting the output times.

NOTE


Format

disp_func_stat [<FUNCTION>] [<func_id1> <func_id2> <func_id3>]


✔ ✔ ✔ ✔


Classification RC

Related commands equip_function on page 3-17


68P81132E13-O

10/3/02-GR

4-47


disp_func_stat

Parameters

NOTE

The FUNCTION parameter must be entered in uppercase letters.

FUNCTION Literal that uniquely identifies the function. (See Appendix C for additional information)

func_id1 First function identifier; this definition varies with each function. (See Appendix C for additional information)

func_id2 Second function identifier; this definition varies with each function. (See Appendix C for additional information)

func_id3 Third function identifier; this definition varies with each function. (See Appendix C for additional information)

Example

This example shows the status of the LCF and OMF functions.

disp_func_stat

STATUS INFORMATION:OMF ID Sta te T ime o f las t t rans i t ion

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 EQUIPPED/BUSY T u e A u g 2 5 2 2 : 2 4 : 5 1 1 9 9 8

STATUS INFORMATION:LCF ID Sta te T ime o f las t t rans i t ion

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =



2 EQUIPPED/ENABLED T u e A u g 2 5 2 2 : 2 6 : 1 6 1 9 9 8

3 EQUIPPED/ENABLED T u e A u g 2 5 2 2 : 2 6 : 5 7 1 9 9 8

NOTE

All times are in GMT fomat.

68P81132E13-O

10/3/02-GR

4-48


disp_function

disp_function

Description

Displays current activity and status for a specified function.

NOTE


Format

disp_function [<FUNCTION>] [<func_id1> <func_id2> <func_id3>]

Parameters

NOTE

The FUNCTION parameter must be entered in uppercase letters. All parameters are optional. If no parameters are entered, the BSC will display all functions configured in the system.

FUNCTION Literal that uniquely identifies the function. (See Appendix C for additional information)

func_id1 First function identifier; this definition varies with each function. (See Appendix C for additional information)


✔ ✔ ✔ ✔




disp_func_stat on page 4-47

68P81132E13-O

10/3/02-GR

4-49


disp_function

func_id2 Second function identifier; this definition varies with each function. (See Appendix C for additional information)

func_id3 Third function identifier; this definition varies with each function. (See Appendix C for additional information)

Supported functions

The following table defines the functions supported by this command. Included is the name of the function and the associated literal.

Example 1

In following example, all configured functions are displayed.

disp_function

LCF-GPROC-CELL Info

LCF id GPROC/ MCAP MTL(s) s i te id cel l id XBL(s)Cage/S lo t CAGE#

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 1 / 0 / 2 1 none none 2 none none

1 2 / 0 / 1 9 1 none 3 1 1 , 2 , 3 , 4

OMF-GPROC-LINK Info

OMF id GPROC/ MCAP E-OML(Kbp) B-OML(Kbps) XBL(s)Cage/S lo t CAGE#

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 3 / 0 / 1 9 1 6 4 3 8 4 none

Function Literal

Logical Control Function LCF

Operation and Maintenance Function OMF

68P81132E13-O

10/3/02-GR

4-50


disp_function

Example 2

In following example, the function LCF is displayed.

disp_function LCF 0 0 0

LCF GPROC/ MCAP MTL(s) SITE(s) CELL(s) XBL(s)Cage/S lo t CAGE#

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 3 / 0 / 2 1 none - - 2 6 - -

7

8

4 1 0

1 1

1 2

Example 3

In following example, the function OMF is displayed.

disp_function OMF

OMF-GPROC

OMF GPROC/ MCAP E-OML Rate (Kbp) B-OML Rate (Kbps) XBL(s)Cage/S lo t CAGE#

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 1 / 0 / 1 9 none 6 4 6 4 0

68P81132E13-O

10/3/02-GR

4-51


disp_gclk_avgs

disp_gclk_avgs

Description

This command displays (in hex) the periodically stored GCLK’s frequency register values over 24 hours (in 30 minute intervals) from NV RAM.

Format

disp_gclk_avgs <device_id>

Parameters


Example

This example displays (in hex) the periodically stored GCLK’s frequency register values for GCLK 0 0 0.

disp_gclk_avgs 0

The GCLK 0 0 0 Frequency Register values are:

C9 CA CA CA CA C9 CA CA CA C9 CA C9

C9 C9 C9 CA CA CA C9 C9 CA C9 CA CA

CA C9 C9 CA CA C9 C9 CA C9 C9 CA CA

C9 C9 C9 C9 C9 CA C9 C9 C9 CA CA CA

Long Term Average = C9


✔ ✔ ✔ ✔


Classification RC

Related commands clear_gclk_avgs on page 3-7


68P81132E13-O

10/3/02-GR

4-52


disp_gclk_cal

disp_gclk_cal

Description

This command displays (in hex) the GCLK’s frequency register value from a particular GCLK. The output contains the average and lower and upper limits over 24 hours.

Format

disp_gclk_cal <device_id>

Parameters


Example

This example displays (in hex) the stored GCLK’s frequency register value in GCLK 0 0 0.

disp_gclk_cal 0

GCLK 0 0 0 Clock f requency regis ter va lue = C8

Long Term Average: b f

Lower l im i t : 1a

Upper l imi t : e9


✔ ✔ ✔ ✔


Classification RC

Related commands clear_gclk_avgs on page 3-7


68P81132E13-O

10/3/02-GR

4-53


disp_interval

disp_interval

Description

This command allows you to display the intervals of statistics-related time intervals that are used for collecting statistical data.

chg_element stat_interval (a non-statistical parameter) sets the duration of the time interval for the collection of statistical data. disp_interval shows the current interval (0-15) of statistical activity that is being measured. Along with the current interval number, it also shows the start-time of the interval series, and the start-times of each of the 16 intervals.

To set the duration of an interval to a time period other than the default value (30 minutes), see chg_element on page 2-31.

Format

disp_interval

Parameters

None.


✔ ✔ ✔ ✔





disp_stats on page 4-78

disp_stats_intrvl on page 4-82

68P81132E13-O

10/3/02-GR

4-54


disp_interval

Example

In order to determine the current interval of the system, use the disp_interval command. There are 4 available intervals (0-3); once the 4th interval is completed, the system will wrap the interval back around to the first interval (0) and begin again.

The disp_stats command cannot be used without an interval number. (It can only be used if the interval has been completed; current statistics intervals cannot be displayed. See the disp_stats command on page 4-78.)

The “System Response” displays the interval start time, and from there you can determine when this set of intervals began. Also, it helps you determine what the current time interval setting (duration) is for statistics.

disp_interval

In terva l Start Time (HH:MM:SS)

0 2 2 : 3 0 : 0 0

1 2 3 : 0 0 : 0 0

2 2 3 : 3 0 : 0 0

3 0 0 : 0 0 : 0 0

Notes:

1) In th is example, In terva l 3 (which is ACTIVE) is not va l id when us ing d isp_s ta ts . Only the s ta ts for the exp i red in terva ls can be d isp layed.

2) A l l t imes reposted in the “Star t T ime” co lumn are in Greenwich Mean T ime (GMT) format . P lease use the loca l t ime zone when in terpret ing the d isp layed t ime.

68P81132E13-O

10/3/02-GR

4-55


disp_ksw_config

disp_ksw_config

Description

Displays the configuration of all KSWs.

Format

disp_ksw_config

Parameters

None.


✔ ✔ ✔ ✔



Related commands chg_ksw_config on page 2-45

68P81132E13-O

10/3/02-GR

4-56


disp_ksw_config

Example

The following system response displays the configuration of all KSWs.

NOTE

HWY represents TDM highway; 2 TDM highways (HWY0 and HWY1) are used for a 2-cage system.

disp_ksw_config

ksw id HWYO HWY1 HWY2 HWY3 cage #= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 1 NA NA 0

1 3 0 NA NA 1

68P81132E13-O

10/3/02-GR

4-57


disp_kswx

disp_kswx

Description

Displays the status of either all the KSWXs (remote, expanded, and local KSWXs) or a specified KSWX.

Format

disp_kswx [<cage><slot>]

Parameters

cage 0 to 5 Specifies BSC cage where KSWX resides.

slot 0 to 9, 21 to 28 The slot number where KSWX resides.


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-58


disp_kswx

Example 1

The following example shows the status of all KSWXs.

disp_kswx

KSWX cage 0 s lot 0 - No a larms found

KSWX cage 0 s lot 1 - Clock Fiber Alarm, Clock Bus A Alarm

KSWX cage 0 s lo t 21 - No a larms found

KSWX cage 0 s lot 22 - TDM Alarm, Clock Bus A Alarm


KSWX cage 1 s lot 0 - Clock Fiber Alarm, Clock Bus B Alarm

KSWX cage 1 s lot 1 - No a larms found


KSWX cage 1 s lot 22 - TDM Alarm, Clock Bus A Alarm, Clock Bus B Alarm

KSWX cage 1 s lot 23 - TDM Alarm

NOTE

Refer to the BSC Troubleshooting Guide (available on AccessSecure web site) for information on detected alarms.

Example 2

The following example shows the status of a specific KSWX (in cage 0, slot 21). Note that the specified slot must be equipped with a KSWX board.

disp_kswx 0 21


68P81132E13-O

10/3/02-GR

4-59


disp_lcf

disp_lcf

Description

Displays the LCF ID, its assigned GPROC, the cage which the MCAP DLSP process services, and the sites and cells that it controls.

Format

disp_lcf

Parameters

None.


✔ ✔ ✔


Classification RC


disp_func_stat on page 4-47


68P81132E13-O

10/3/02-GR

4-60


disp_lcf

Example 1

The following system response displays all active LCFs:

disp_lcf

LCF - GPROC - CELL Info

LCF GPROC/ MCAP MTL(s) SITE(s) CELL(s) XBL(s)Cage/S lo t CAGE#

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 3 / 0 / 2 1 none - - 2 6 - -

7

8

4 1 0

1 1

1 2

1 4 / 0 / 2 2 none - - 6 1 2 3 - -

8 2 1

2 2

2 3

2 5 / 0 / 2 3 none 0 - - - - - -

3 N / A N / A N / A - - - - - -

4 N / A N / A N / A - - - - - -

7 N / A N / A N / A - - - - - -

Example 2

The following system response displays when no active LCFs:

disp_lcf

* * * There are no ac t ive LCFs * * *

68P81132E13-O

10/3/02-GR

4-61


disp_level

disp_level

Description

Displays the current security level.

Format

disp_level

Parameters

None.

Example

disp_level

Current secur i ty leve l is 1


✔ ✔ ✔ ✔



Related commands chg_level on page 2-46

68P81132E13-O

10/3/02-GR

4-62


disp_mcap_gproc

disp_mcap_gproc

Description

Displays all MCAP GPROCs, their locations, and the assigned functions. If the assigned function shows “N/A”, it indicates that MCAP GPROC is a standby GPROC.

Format

disp_mcap_gproc

Parameters

None.

Example

disp_mcap_gproc

Cage Slot GPROC Function Type

=================================================-

0 20 0 BSP EGPROC

1 20 2 LCF EGPROC

2 20 4 N/A GPROC

3 20 6 OMF GPROC


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-63


disp_msi_alarms

disp_msi_alarms

Description

Displays alarms for a selected MSI or all MSIs in the BSC.

Format

disp_msi_alarms [msi_id]

Parameters

msi_id 0-71 ID of MSI for which alarms are to be displayed.

Example

disp_msi_alarms

MSI: 0 (Cage: 0/Slot 17) SPAN LINES ALARM CHECKMSI Is Not In Unlocked Busy State

MSI: 1 (Cage: 0/Slot 16) SPAN LINES ALARM CHECKSPAN ALARMS––––– –––––––––––––––––––––––––––––––––––––––––––––––––––––––0 Red (Loss of Signal /Frame) Alarms: Cont inuously.

1 Red (Loss of Signal /Frame) Alarms: Cont inuously.

MSI: 2 (Cage: 0/Slot 15) SPAN LINES ALARM CHECKSPAN ALARMS––––– –––––––––––––––––––––––––––––––––––––––––––––––––––––––

MSI: 3 (Cage: 0/Slot 14) SPAN LINES ALARM CHECKMSI Is Not In Unlocked Busy State

Al l MSIs SPAN Line Alarms Report Completed


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-64


disp_nail_conn

disp_nail_conn

Description

Displays all span-to-span nailed connections.

Format

disp_nail_conn

Parameters

None.

Example

disp_nail_conn


✔ ✔ ✔ ✔




del_span_nail on page 2-64

–––––––– S O U R C E ––––––––– ––––– D E S T I N A T I O N –––––

MSI SPAN TDM TS

___Timeslots___

––––––––––––––––––––––––––––––––

111111

000000

514 8546578738770802

910151617

MSI SPAN TDM TS

___Timeslots___

––––––––––––––––––––––––––––––––

333444

000000

4 03668

670

134

12012

68P81132E13-O

10/3/02-GR

4-65


disp_num_ebts_dl

disp_num_ebts_dl

Description

Displays the maximum number of EBTS download sessions that the BSC can perform.

Format

disp_num_ebts_dl

Parameters

None.

Example

disp_num_ebts_dl

Number of EBTS Downloads: 1


✔ ✔



Related commands set_num_ebts_dl on page 2-76

68P81132E13-O

10/3/02-GR

4-66


disp_obj_info

disp_obj_info

Description

Displays object code information including name, version number, creation time, size, and checksum.

Format

disp_obj_info <code_obj_number>

Parameters

code_obj_number 0-255 Number of object for which information is displayed. (Type “objects” on the exec monitor terminal to display a complete listing of valid object numbers.)

Example

disp_obj_info 112

Object : mmi

Version Number: R 02 .00 .26

Checksum: 0x0 Obdcb f f

Flags: 0 x 0 0

Size: 1 5 1 3 5 2 b y t e s

Date: 1 4 : 3 8 4 / 8 / 1 9 9 6


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-67


disp_omc_net

disp_omc_net

Description

Displays all network connections between the EBTS and OMC, with netcon ID.

Format

disp_omc_net

Parameters

None.

Example

disp_omc_net

EBTS --- OMC Connect ion Information

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NETCON EBTS ADDRESS CONNECTION LAN NO MAILBOX RSL STATE

====================================================================

0x 6009D8 31601001415202 SNMP 0219 8104 02 NS_ACTIVE

0x 600A00 31601001415107 SNMP 0219 8106 07 NS_ACTIVE

0x 6009B0 31601001415241 SNMP 0217 8102 41 NS_ACTIVE


✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-68


disp_options

disp_options

Description

Displays the information in the feature option object to customer MMI terminal.

Format

disp_options [all]

Parameters

all If string “all” is entered, give full information.

Example 1:

disp_options

Enhanced XCDR system is Available.

Example 2:

disp_options all

Customer Name: BSC

Market: ILL

Load Vers ion: R 00.00.00

C r e a t i o n D a t e : 2 6 / 0 3 / 9 6

Enhanced XCDR System is Available.


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-69


disp_plp_net

disp_plp_net

Description

Displays all network connections between the BSC and the OMC, with netcon ID.

Format

disp_plp_net

Parameters

None.

Example

disp_plp_net

BSC --- OMC Connect ion Information

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NETCON BSC ADDRESS FUNCTION LAN NO MAILBOX STATE

====================================================================

0x 6009B0 31601001315100 EVENT_REPORT 0115 000D NS_ACTIVE

0x 6007B8 31601001315100 IPC_FUNCTION 0115 000F NS_ACTIVE


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-70


disp_rf_cr_cell

disp_rf_cr_cell

Description

This command displays cells that are in RF congestion relief mode.

Format

disp_rf_cr_cell

Parameters

None.

Example

This example displays cells that are in RF congestion relief mode.

disp_rf_cr_cell

Cell ID Site ID

===== =====

6 2

7 2


✔ ✔


Classification RC

Related commands disp_cell on page 4-8

68P81132E13-O

10/3/02-GR

4-71


disp_span_alarm

disp_span_alarm

Description

Displays the span-alarm for the type of span the BSC is configured for (E1 or T1). Also displayed is whether the alarm is on or off.

Format

disp_span_alarm

Parameters

None.

Example

disp_span_alarm

REMOTE_LOSS_DAILY: ON

REMOTE_LOSS_HOURLY: ON

REMOTE_OOS: ON

SLIP_LOSS_DAILY: ON

SLIP_LOSS_HOURLY: ON

SLIP_LOSS_OOS: ON

REMOTE_TIME_OOS: ON

AIS_TIME_OOS: ON

RED_DAILY: ON

RED_HOURLY: ON

RED_OOS: ON

RED_OOS_TIME: ON


✔ ✔ ✔ ✔


Classification RC

Related commands set_span_alarm on page 5-25

68P81132E13-O

10/3/02-GR

4-72


disp_span_tdm

disp_span_tdm

Description

Displays the mapping of span link time slots to TDM highway timeslots.

Format

disp_span_tdm <msi_id> [span_id]

Parameters

msi_id 0-71 Device ID of the MSI-2 associated with the span link on which information is to be displayed.

span_id 0-1 Device ID of the span link to be displayed.


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-73


disp_span_tdm

Example

disp_span_tdm 0 0

MSI: 00 Span: 0

Span t imeslot TDM t imeslot

0 0 0 0 0 1

0 1 0 0 6 5

0 2 0 1 2 9

0 3 0 1 9 3

0 4 0 2 5 7

0 5 0 3 2 1

0 6 0 3 8 5

0 7 0 4 4 9

0 8 0 5 1 2

0 9 0 5 4 4

1 0 0 5 7 6

1 1 0 6 0 8

1 2 0 6 4 0

1 3 0 6 7 2

1 4 0 7 0 4

1 5 0 7 3 6

1 6 0 7 6 8

1 7 0 8 0 0

1 8 0 8 3 2

1 9 0 8 6 4

2 0 0 8 9 6

2 1 0 9 2 8

2 2 0 9 6 0

2 3 0 9 9 2

68P81132E13-O

10/3/02-GR

4-74


disp_span_use

disp_span_use

Description

Displays the span link timeslot assignments, including RSL, OML, MTL, XBL, radio channel, subrate channel, terrestrial circuit, and nail connection.

Format

disp_span_use <msi_id> [span_id]

Parameters

msi_id 0-71 Device ID of the MSI-2 associated with the span link on which information is to be displayed.

span_id 0-1 Device ID of the span link to be displayed.


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-75


disp_span_use

Example 1

disp_span_use 1 0

MSI: 1 SPAN: 0

Timeslo t Assigned To

1 NAIL

2 OML: 0 0 0

3 NAIL

4 NAIL

5 CCT: 6

6 CCT: 7

7 CCT: 8

8 CCT: 9

9 CCT: 10

1 0 CCT: 11

1 1 CCT: 12

1 2 NAIL

1 3 NAIL

1 4 NAIL

1 6 CCT: 17

1 7 CCT: 18

1 8 CCT: 19

1 9 CCT: 20

2 0 CCT: 21

2 1 CCT: 22

2 2 CCT: 23

2 3 CCT: 24

Example 2

disp_span_use 1 0

MSI: 1 SPAN: 0

T imes lo t Ass igned To

0 RSL: 18 0 0

1 RSL: 18 1 0

5 g r p 0 S C I : E B T S s i t e i d = 5 0 ; E B T S s p a n / t s / g r p = 1 / 0 0 / 0 ( 3 2 2 0 1 8 f f )


5 g rp 2 SC I :EBTS s i t e i d=50 ; EBTS span / t s / g rp=1 /00 /2 ( 32 20 1a f f )

5 g r p 3 S C I : E B T S s i t e i d = 5 0 ; E B T S s p a n / t s / g r p = 1 / 0 0 / 3 ( 3 2 2 0 1 b f f )



6 g rp 2 SC I :EBTS s i t e i d=50 ; EBTS span / t s / g rp=1 /01 /2 ( 32 21 1a f f )

6 g r p 3 S C I : E B T S s i t e i d = 5 0 ; E B T S s p a n / t s / g r p = 1 / 0 1 / 3 ( 3 2 2 1 1 b f f )

68P81132E13-O

10/3/02-GR

4-76


disp_span_use

Example 3

disp_span_use 0

MSI: 0 SPAN: 0


0 NAIL : 0 1 0

1 OML: 0 0 0

2 NAIL : 0 1 2

3 NAIL : 0 1 3

4 NAIL : 0 1 4

5 CCT: 13001

6 CCT: 13002

7 CCT: 13003

8 CCT: 13004

9 CCT: 13005

1 0 CCT: 13006

1 1 CCT: 13007

1 2 CCT: 13008

1 3 CCT: 13009

1 4 CCT: 13010

1 5 CCT: 13011

1 6 CCT: 13012

1 7 CCT: 13013

1 8 CCT: 13014

1 9 CCT: 13015

2 0 CCT: 13016

2 1 CCT: 13017

2 2 CCT: 13018

2 3 CCT: 13019

MSI: 0 SPAN: 1


0 NAIL : 0 0 0

2 NAIL : 0 0 2

3 NAIL : 0 0 3

4 NAIL : 0 0 4

1 2 XBL: 0 0 0

1 3 XBL: 1 0 0

68P81132E13-O

10/3/02-GR

4-77


disp_stats

disp_stats

Description

Displays a specific statistic.

NOTE

Some statistics may require an individual cell or board identifier. A statistic requires a valid (past) interval number for the interval parameter shown in the disp_stats format. See the definition of interval, in the next section.

Format

disp_stats <interval> <statistical_element _name> [cell_number=<cell_number>] | [board_id=<board_id>]

See the list in Table 6-1 for statistics parameters requiring cell_number.

See the list in Table 6-2 for statistics parameters requiring board_id.

The statistical_element_name parameters (and the basis for each of those statistical parameters) are defined in Appendix B.


✔ ✔ ✔ ✔


Classification RC

Related commands chg_element on page 2-31 (statistical and non-statistical)


disp_stats_intrvl on page 4-82

clear_stats on page 6-38

68P81132E13-O

10/3/02-GR

4-78


disp_stats

At system start-up, the statistical time interval (interval) begins at zero. The time interval is stored in the database and can be modified or displayed using the chg_element and disp_element commands. The default value for interval is 30 minutes. Current time interval statistics cannot be displayed. Only statistics from past intervals may be viewed.

The cell_number parameter should only be entered to identify a “per cell” or a “per channel” statistic.

The board_id parameter should only be entered to identify a “per link” statistic.

When using disp_stats to display a “per link” statistic, the output generated will report all links for a specified board.

Parameters

interval 0-3 Specific time period (0-3, the system default is: 0 = the first 30 minute interval following system start-up, 1 = second 30 minute interval following system start-up, etc.). Valid only for a completed interval period (past intervals only). So, when using disp_stats, this parameter is not valid for the current interval. (See disp_stats_intrvl to determine the correct interval to use with the disp_stats command.)

statistical_element_ name Global name of statistics that represents the statistics at the time of creation, deletion, and update. (See Table 6-1 and Table 6-2 to determine need for cell_number and board_id. Also, see Appendix B for definitions). Use uppercase lettering when entering this portion of the command.

non_statistical_element_ name Global name of statistics that represents the statistics at the time of creation, deletion, and update. (See Table 6-1 and Table 6-2 to determine need for cell_number or board_id. Also, see Appendix B for definitions). Use uppercase lettering when entering this portion of the command.

cell_number 0-239 Local cell ID, indicating from which cell to display statistics. Specify for a per cell or a per channel statistic only.

68P81132E13-O

10/3/02-GR

4-79


disp_stats

board_id GPROC CPU ID (for example, 115h) identifying the board from which to display statistics. Specify for a per link statistic only. See list at the end of this chapter.

NOTE

Refer to Table 6-2 to determine if the statistical_ element_name requires a board_id. Also, when entering this command, use upper case lettering for the statistical_element_name described.

Example 1:

Example 1 is a counter statistic that requires a cell_number because it is a “per cell” statistic. The following output will be displayed:

disp_stats 5 TOTAL_CALLS cell_number = 0

SITE: 0 CELL #: 1

MEAS_TYPE: TOTAL_CALLS

Counter : 1

Where:

5 = the interval number

0 = Local cell ID

TOTAL_CALLS = requested statistics

Example 2:

This is an example of a counter statistic that does not require a board_id because it is a “per bss” statistic. The following output will be displayed in the system response:

disp_stats 1 PAGE_REQ_FROM_MSC_FAIL

SITE: 0 BSS #: 1

MEAS_TYPE: PAGE_REQ_FROM_MSC_FAIL

Counter : 13

68P81132E13-O

10/3/02-GR

4-80


disp_stats

Example 3:

The following command entry is a counter statistic that requires a board_id because it is a “per link” statistic. The following output will be displayed in the system response:

disp_stats 0 MTP_SL_FAIL board_id = 0115h

SITE: 0 GPROC Board #: 0115

SITE: 0 MTL Link # : 3

MEAS_TYPE : MTP_SL_FAIL

Counter : 2

Example 4:

The following command entry is a total time (duration) statistic that requires a board_id because it is a “per link” statistic. The following output will be displayed in the system response:

disp_stats 1 MTP_UNAVAILABLE board_id = 0115h



MEAS_TYPE : MTP_UNAVAILABLE

Dura t ion Va lue (ms) : 98245

Dura t ion Mean (ms) : 49122

Dura t ion Max. (ms) : 63720

Dura t ion Min : (ms) : 34525

NOTE

When using disp_stats to display a “per link” statistic, the output generated will report all links for a specified board.

68P81132E13-O

10/3/02-GR

4-81


disp_stats_intrvl

disp_stats_intrvl

Description

Displays the current statistics reporting interval at the BSC.

Format

disp_stats_intrvl

Parameters

None.

Example

disp_stats_intrvl

s ta t_ i n te r va l = 30


✔ ✔ ✔ ✔




disp_interval on page 4-54


68P81132E13-O

10/3/02-GR

4-82


disp_subrate

disp_subrate

Description

Displays the subrate pool identifiers and the subrate channel identifiers (SCI) for a BSC or E-RXCDR system.

Format

For E-BSC System:

disp_subrate <all> | <ebts_id> | <summary>

For E-RXCDR System:

disp_subrate <all> | <Remote_site=remote_site_id> [ebts_id] | <summary>

Parameters

remote_site_id 1-255 ID of the E-BSC the E-RXCDR is connected to. This parameter is only optional for the E-RXCDR system.

ebts_id 1-80 ID of the EBTS

all Displays all subrates information

summary Displays the summary of the SCIs’ state


✔ ✔




del_subrate on page 2-66


68P81132E13-O

10/3/02-GR

4-83


disp_subrate

Example 1

This example shows SCIs for EBTS 2 in a BSC system.

disp_subrate 2

EBTS EBTS: CP-BSC: SCI (hex) STATE SCCPID: SPAN/TS/GRP MSI/SPAN/TS/GRP BLOCKING REASON

===============================================================

2 0/6/0 - SCI pool ID

2 0 / 6 / 0 3 / 0 / 6 / 0 02 06 00 ff IDLE 0xffffffh

2 0 / 6 / 1 3/ 0 / 6 / 1 02 06 01 ff BLKD/BSC 0xffffffh

2 0 / 6 / 2 3 / 0 / 6 / 2 02 06 02 ff BLKD/EBTS 0xffffffh

2 0 / 6 / 3 3 / 0 / 6 / 3 02 06 03 ff BLKD/BSC+EBTS 0xffffffh

2 0 / 7 / 0 3 / 0 / 7 / 0 02 07 00 ff ACTIVE 0x020204h

Example 2

This example shows SCIs on Remote Site 53 on an E-RXCDR system.

disp_subrate Remote_Site=53

EBTS EBTS: E-RXCDR: SCI (hex) REMOTE STATE SCCPID: SPAN/TS/GRP MSI/SPAN/TS/GRP SITE BLOCKING REASON

===============================================================

2 0/6/0 - SCI pool ID

2 0 / 6 / 0 3 / 0 / 6 / 0 02 06 00 ff 53 IDLE 0xffffffh

2 0 / 6 / 1 3 / 0 / 6 / 1 02 06 01 ff 53 BLKD/BSC 0xffffffh

2 0 / 6 / 2 3 / 0 / 6 / 2 02 06 02 ff 53 BLKD/EBTS 0xffffffh

2 0 / 6 / 3 3 / 0 / 6 / 3 02 06 03 ff 53 BLKD/BSC+EBTS 0xffffffh

2 0 / 7 / 0 3 / 0 / 7 / 0 02 07 00 ff 53 ACTIVE 0x020204h

4 0/ 6/0 - SCI pool ID

4 0 / 6 / 0 3 / 1 / 6 / 0 04 06 00 ff 53 IDLE 0xffffffh

4 0 / 6 / 1 3 / 1 / 6 / 1 04 06 01 ff 53 IDLE 0xffffffh

4 0 / 6 / 2 3 / 1 / 6 / 2 04 06 02 ff 53 IDLE 0xffffffh

4 0 / 6 / 3 3 / 1 / 6 / 3 04 06 03 ff 53 IDLE 0xffffffh

4 0 / 7 / 0 3 / 1 / 7 / 0 04 07 00 ff 53 IDLE 0xfffff fh

Example 3

This example shows a summary of the states for all SCIs.

disp_subrate summary

IDLE SCI(s) ACTIVE SCI(s) BLOCKED SCI(s) ACTIVE-RESV SCI(s)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 6 9 6 0

68P81132E13-O

10/3/02-GR

4-84


disp_tdm_use

disp_tdm_use

Description

Displays the allocated timeslots on the specified TDM highway. If a device name is entered following the TDM highway, the timeslots for all devices of that type on the specified TDM highway are displayed. If a device name with a device ID is specified, all allocated timeslots for that device are displayed.

Format

disp_tdm_use <tdm_highway> [DEVICE] | <DEVICE> <device_id1> <device_id2> <device_id3>

Parameters

tdm_highway 0-3 TDM highway number for which timeslot allocation information is to be displayed.

DEVICE Device to be displayed (XCDR, MSI, GPROC)

device_id1 First device identifier; this definition varies with each device

device_id2 Second device identifier; this definition varies with each device

device_id3 Third device identifier; this definition varies with each device


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-85


disp_tdm_use

Example 1

disp_tdm_use 0

Allocated Time Slots of TDM 0

0 1 2 3 4 5 6 7 8 9 10 32 33 34 35 36 37 38 39 40 41 42 64 65 66 67 68 69 70 71 72 73 74 96 97 98 99 100 101 102 103 104 105 106 128 129 130 131 132 133 134 135 136 137 138 160 161 162 163 164 165 166 167 168 169 170 192 193 194 195 196 197 198 199 200 201 202 224 225 226 227 228 229 230 231 232 233 234 256 257 258 259 260 261 262 263 264 265 266 288 289 290 291 292 293 294 295 296 297 298 320 321 322 323 324 325 326 327 328 329 330 352 353 354 355 356 357 358 359 360 361 362 384 385 386 387 388 389 390 391 392 393 394 416 417 418 419 420 421 422 423 424 425 426 448 449 450 451 452 453 454 455 456 457 458 480 481 482 483 484 485 486 487 488 489 490 512 513 514 515 516 517 518 519 520 521 522 544 545 546 547 548 549 550 551 552 553 554 576 577 578 579 580 581 582 583 584 585 586 608 609 610 611 612 613 614 615 616 617 618 640 641 642 643 644 645 646 647 648 649 650 672 673 674 675 676 677 678 679 680 681 682 704 705 706 707 708 709 710 711 712 713 714 736 737 738 739 740 741 742 743 744 745 746 768 769 770 771 772 773 774 775 776 777 778 800 801 802 803 804 805 806 807 808 809 810 832 833 834 835 836 837 838 839 840 841 842 864 865 866 867 868 869 870 871 872 873 874 896 897 898 899 900 901 902 903 904 905 906 928 929 930 931 932 933 934 935 936 937 938 960 961 962 963 964 965 966 967 968 969 970 992 993 994 995 996 997 998 999 10001001 1002

Example 2

disp_tdm_use GPROC 0 0 0

Al located Time Slots of GPROC 0 0 0

0 3 2 6 4 9 6 1 2 8 1 6 0 1 9 2 2 2 4

2 5 6 2 8 8 3 2 0 3 5 2 3 8 4 4 1 6 4 4 8 4 8 0

Example 3

disp_tdm_use 0 GPROC

Al located T ime Slots o f TDM 0

Device Device Id Al located T imeslo ts

GPROC 0 0 0 0 3 2 6 4 9 6 1 2 8 1 6 0 1 9 2 2 2 4

2 5 6 2 8 8 3 2 0 3 5 2 3 8 4 4 1 6 4 4 8 4 8 0

GPROC 1 0 0 5 1 2 5 4 4 5 7 6 6 0 8 6 4 0 6 7 2 7 0 4 7 3 6

7 6 8 8 0 0 8 3 2 8 6 4 8 9 6 9 2 8 9 6 0 9 9 2

68P81132E13-O

10/3/02-GR

4-86


disp_time

disp_time

Description

Displays the current real time of the system in Greenwich Mean Time (GMT) format. The format of the time is day of the week, month, day, hour, minutes, seconds, and year. Once the time synchronization is enabled, the BSC will synchronize its internal clock using SNTP (Simple Network Time Protocol) and will display in UTC (Universal Coordinated Time) format. UTC time is not corrected for geographical time zones, consistent with other Network Elements in the iDEN system.

Format

disp_time

Parameters

None.

Example

This example the current date of Tuesday, January 1st, 1996 and the current system time of 1:33:18 pm.

disp_time

Tue Jan 1 13 :33 :18 1996

NOTE

The time reported is in Greenwich Mean Time (GMT). Use the local time zone when interpreting the times.


✔ ✔ ✔ ✔



Related commands chg_time on page 2-54

68P81132E13-O

10/3/02-GR

4-87


disp_version

disp_version

Description

Displays the version and revision numbers of the current software load.

Format

disp_version

Parameters

None.

Example

disp_version

Load vers ion R.01.04.42, Created MM/DD/YY HH:MM


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

4-88


disp_vpr

disp_vpr

Description

Displays VP Recovery information at XCDR or VP level.

Format

disp_vpr [info] | [xcdr_id]

Parameters

info Displays VP Recovery flags, statistics, and threshold settings on sysgen or non_sysgen mode.

xcdr_id 0-54 Displays Recovery Information of VPs for the specified XCDR on non_sysgen mode.

NOTE

If no parameter is entered, disp_vpr displays Recovery Information for each busy XCDR on non_sysgen mode.


✔ ✔




68P81132E13-O

10/3/02-GR

4-89


disp_vpr

Example 1

disp_vpr info

The values displayed indicate the VP recovery function is enabled with the threshold values set to their defaults. The system has performed five VP recovery attempts with three VPs successfully recovered and one VP passing the initial Voice Trunk Test (VTT); it also implies that one VP did not recover.

Element Name Value

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

shor t_ca l l_ f lag on

v p r _ v t t _ f l a g on

shor t_ca l l_ ins t 2

shor t_ca l l_ th res 1 0

normal_ca l l_ thres 2 0

v p r _ t o t _ a t t e m p t s 5

vpr_success_rec 3

vp r_pass_ in i t _v t t 1

Example 2

disp_vpr

This example displayes Recovery information for each busy XCDR, including number of Successful Recoveries and number of Recovery Attempts.

XCDR Successful Recovery Inservice Time

Recoveries / A t t e m p t s

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 / 0 Thu Sep 24 03 :52 :55 1998

6 2 / 3 Thu Sep 24 03 :51 :07 1998

7 0 / 0 Thu Sep 24 03 :54 :40 1998

9 0 / 0 Thu Sep 24 03 :54 :10 1998

1 0 0 / 0 Thu Sep 24 03 :55 :11 1998

1 1 0 / 0 Thu Sep 24 03 :55 :41 1998

1 5 0 / 0 Thu Sep 24 03 :56 :11 1998

68P81132E13-O

10/3/02-GR

4-90


disp_vpr

Example 3

disp_vpr 6

This example displayes Recovery information of VPs for specified busy XCDR (6), including number of Successful Recoveries, number of Recovery Attempts, and last Recovery Attempt.

VP Successful Recovery Last Recovery

Recoveries / A t t e m p t s A t t e m p t

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 / 0 N / A

1 0 / 0 N / A

2 1 / 1 Thu Sep 24 03 :56 :11 1998

3 0 / 0 N / A

4 0 / 0 N / A

5 1 / 1 Thu Sep 24 03 :56 :11 1998

6 0 / 0 N / A

7 0 / 0 N / A

8 0 / 1 Thu Sep 24 06 :10 :34 1998

9 0 / 0 N / A

1 0 0 / 0 N / A

1 1 0 / 0 N / A

68P81132E13-O

10/3/02-GR

4-91


disp_xbl_conn

disp_xbl_conn

Description

Displays the current MMS connectivity between the RXCDR and the BSCs connected to it. This information is used by XBL links to route fault management information between the RXCDR to the appropriate BSC.

Format

disp_xbl_conn

Parameters

None.

Example

disp_xbl_conn

The RXCDR to BSC connect iv i ty is as fol lows:

MSI 1/SPAN L ine 0 is assoc iated wi th XBL 1 remote s i te id is 54

Finished displaying RXCDR to BSC connect ivi ty for XBL

NOTE

The following response is displayed when there is no RXCDR to BSC connectivity:There is no RXCDR to BSC connect iv i ty in the database


✔ ✔



Related commands add_xbl_conn on page 2-15

del_xbl_conn on page 2-68

68P81132E13-O

10/3/02-GR

4-92


disp_xcdr_bypass

disp_xcdr_bypass

Description

Displays the XCDR-bypass-allowed flags for all configured cells.

Format

disp_xcdr_bypass

Parameters

None.

Example

The following is a typical response for configured cells only.

disp_xcdr_bypass

EBTS Site Number Local Cell ID Bypass Flag= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

1 3 1

8 2 4 1

2 2 5 4 1

NOTE

If there are no cells configured with the XCDR-bypass-allowed flag, the following prompt appears:

There are no conf igured cel ls .


✔ ✔



Related commands disp_xcdr_types on page 4-94

disp_xcdr_use on page 4-95

68P81132E13-O

10/3/02-GR

4-93


disp_xcdr_types

disp_xcdr_types

Description

Displays the types of all XCDRs. This command should be run at the system where XCDR cards are located.

Format

disp_xcdr_types

Parameters

None.

Example

disp_xcdr_types

XCDR 1 0 0 3T01

XCDR 2 0 0 6T01

XCDR 3 0 0 DUAL_24

XCDR 4 0 0 DUAL_48


✔ ✔


Classification RC



68P81132E13-O

10/3/02-GR

4-94


disp_xcdr_use

disp_xcdr_use

Description

Displays the VP states and associated information about a specified XCDR. This command should be run at the system where XCDR cards are located.

Format

disp_xcdr_use <xcdr_id> | <summary>

Parameters

xcdr_id 0-54 XCDR identifier for which information is required.

summary Displays summary of VPs’ state


✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

4-95


disp_xcdr_use

Example 1

disp_xcdr_use 20

XCDR Ident i f ier=20

VP Ident i f ier VP type VP State CIC SCCP Remote_Site_ID

0 3 t o 1 IDLE

1 3 t o 1 IDLE

2 3 t o 1 IDLE

3 3 t o 1 IDLE

4 3 t o 1 IDLE

5 3 t o 1 IDLE

6 3 t o 1 IDLE

7 3 t o 1 IDLE

8 3 t o 1 IDLE

9 3 t o 1 IDLE

1 0 3 t o 1 IDLE

1 1 3 t o 1 IDLE

NOTE

DUAL_24 type XCDR boards contain 24 VPs and DUAL_48 type XCDR boards contain 48 VPs.

Example 2

This example shows a summary of the states for all VPs.

disp_xcdr_use summary

IDLE VP(s) ACTIVE VP(s) BLOCKED VP(s) ACTIVE-RESV VP(s)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

0 0 6 9 6 0

68P81132E13-O

10/3/02-GR

4-96

5

5 Fault management

Introduction

Fault Management (FM) commands make specific functions or devices of the system available for monitoring.


10/3/02-GR

5-1

CHAPTER 5 - FAULT MANAGEMENT BSC MMI Commands

auto_vp_flag

auto_vp_flag

Description

Sets the auto VP audit flag on or off.

With this flag set on, all of the VPs on a XCDR that transitions to the BUSY/UNLOCKED state are audited.

NOTE


Format

auto_vp_flag <mode>

Parameters

mode on Turn the audit on.

off Turn the audit off.

Example

auto_vp_flag on

COMMAND ACCEPTED. auto_vp_flag is set to ON.


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

5-2

BSC MMI Commands CHAPTER 5 - FAULT MANAGEMENT

bsc_audit

bsc_audit

Description

Executes an audit of all devices (whose audits are enabled) at the BSC.

Format

bsc_audit [control]

Parameters

control off Suspends all site audits at the site.

on Resumes all site audits at the site.

Note: If no parameter is entered, audits are performed on all devices.

Example

This example shows how all site audits are suspended.

bsc_audit on

Device: BSC Device id: 0 0 0

Resume Audi t Status: 0

bsc_audit off

Device: BSC Device id: 0 0 0

Suspend Audi t Sta tus: 0


✔ ✔ ✔ ✔


Classification RC

Related commands cage_audit on page 5-4

chg_audit_sched on page 5-6

device_audit on page 5-9

68P81132E13-O

10/3/02-GR

5-3


cage_audit

cage_audit

Description

Suspends/resumes the scheduled auditing of a specific BSC cage. It’s also used to execute an on-demand audit (all or safe) of a specific BSC cage.

Formats

cage_audit <control> <cage_number> | <cage_number> <audit_type>

Parameters

control off Suspends all cage audits at the site.

on Resumes all cage audits at the site.(This parameter not used when audit_type parameter is specified; see examples.)

cage_number 0-5 Specifies BSC cage to be audited.

audit_type safe Specifies safe tests only (i.e., those tests which do not affect service).

all Specifies all tests.


✔ ✔ ✔ ✔


Classification RC

Related commands bsc_audit on page 5-3



68P81132E13-O

10/3/02-GR

5-4


cage_audit

Example 1:

This example executes a safe audit for all devices in cage 0.

cage_audit 0 safe

Example 2:

This example resumes all audits for all devices in cage 1.

cage_audit on 1

68P81132E13-O

10/3/02-GR

5-5


chg_audit_sched

chg_audit_sched

Description

Selectively configures the scheduling of audit execution on a device type and audit type basis.

Format

chg_audit_sched <DEVICE> <audit_type> <start_time> <end_time> <interval>

Parameters

DEVICE Literal that uniquely defines the device type.

audit_type safe Tests which are not service-affecting.

int_lpbk Internal loopback tests.

ext_lpbk External loopback tests.

gclk_status GCLK status tests.

vp_audit VP tests (VPs reside on the XCDR).

conn_test TDM connectivity test.

start_time 00:00-23:59 Time of day (standard military GMT ) when audit is to begin; specified in hours:minutes.

end_time 00:00-23:59 Time of day (standard military GMT) when audit is to end; specified in hours:minutes.

interval 00:00-23:59 Specifies how often during audit window (set by start_time and end_time) audit tests are run).


✔ ✔ ✔ ✔



Related commands disp_audit_sched on page 4-3

68P81132E13-O

10/3/02-GR

5-6


chg_audit_sched

Parameter notes

If start_time and end_time both equal 00:00 and interval does not equal 00:00, the audit window is set for 24 hours a day.

If end_time is greater than start_time and interval time does not equal 00:00, then the audit window is determined by start_time and end_time and audit tests are run according to the interval time.

If start_time equals end_time and interval time is 00:00, then audit tests occur once per day at time specified.

If start_time and interval both equal 00:00 and end_time is non-zero, then the audit is turned off.

NOTE

All times are in Greenwich Mean Time (GMT). Remember to note the local time zone when determining when the audits will be executed.

Example 1:

This example establishes an audit schedule. A safe audit is performed on the XCDR device between 9:30 a.m. GMT and 10:30 p.m. GMT with an interval of once every 15 minutes.

chg_audit_sched XCDR safe 9:30 22:30 0:15


Parameter: Value:

<DEVICE> XCDR

<audit_type> safe

<start_time> 9:30

<end_time> 22:30

<interval> 0:15

68P81132E13-O

10/3/02-GR

5-7


chg_audit_sched

Example 2:

This example establishes an audit schedule. A safe audit is performed on all XCDR devices once per day at 2:00 a.m. GMT.

chg_audit_sched XCDR safe 2:00 2:00 0:0


Audit type availability

The following table lists the audit types currently available for the various hardware boards and buses.

Parameter: Value:

<DEVICE> XCDR

<audit_type> safe

<start_time> 2:00

<end_time> 2:00

<interval> 0:0

Hardware boards & buses

(Literal)

Audit test type categories

Safetests

Externalloopback

Othertests

Cage (CAGE) � � GCLKstatus test

VP test

Clock Bus (CBUS) �

GCLK Board (GCLK) GCLKstatus test

GPROC Board (GPROC) �

KSW Board (KSW) �

MSI-2 Board (MSI) �

TDM Bus (TBUS) �

XCDR Board (XCDR) � VP tests

68P81132E13-O

10/3/02-GR

5-8


device_audit

device_audit

Description

This command is used to resume/suspend all audits for a specified device or to initiate a specific test for a specified device.

Format

device_audit <control> <DEVICE> <device_id1> <device_id2> <device_id3> | <DEVICE> <device_id1> <device_id2> <device_id3> <audit_type>


✔ ✔ ✔ ✔


Classification RC



cage_audit on page 5-4

68P81132E13-O

10/3/02-GR

5-9


device_audit

Parameters

control off Suspends all audits for the specified device.

on Resumes all audits for the specified device.(This parameter not used when audit_type parameter is specified; see examples.)

DEVICE Literal that defines the particular device.




audit_type safe Tests which do not affect service.

ext_lpbk External loopback tests.

gclk_status GCLK status tests.

Example 1:

This example executes a safe audit for a CBUS device with a device ID of 0 0 0.

device_audit CBUS 0 0 0 safe


Parameter: Value:

<DEVICE> CBUS

<device_id1> 0

<device_id2> 0

<device_id3> 0

<audit_type> safe

68P81132E13-O

10/3/02-GR

5-10


device_audit

Example 2:

This example suspends all audits for a KSW device with a device ID of 1 0 0.

device_audit off KSW 1 0 0


Audit type availability

The following table lists the audit types currently available for the various hardware boards and buses.

Parameter: Value:

<control> off

<DEVICE> KSW

<device_id1> 1

<device_id2> 0

<device_id3> 0

Hardware boards & buses

(Literal)

Audit test type categories

Safetests

Externalloopback

Othertests

Cage (CAGE) � � GCLKstatus test

VP tests

Clock Bus (CBUS) �

GCLK Board (GCLK) GCLKstatus test

GPROC Board (GPROC) �

KSW Board (KSW) �

MSI-2 Board (MSI) �

TDM Bus (TBUS) �

XCDR Board (XCDR) � VP tests

68P81132E13-O

10/3/02-GR

5-11


ftp_mode

ftp_mode

Description

Specifies whether all or only translated alarms are reported.

Format

ftp_mode <report_mode>

Parameters

report_mode raw All alarms are reported.

translated Only translated alarms are reported.

Example

This example selects all alarms for reporting.

ftp_mode raw


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-12


ftp_query_alarm

ftp_query_alarm

Description

Displays a list of up to the last 10 alarms for the specified device.

Format

ftp_query_alarm <DEVICE> <device_id1> [device_id2] [device_id3]

Parameters

DEVICE Literal that uniquely identifies the device.




Example

This example displays a list of alarms for the GPROC device.

ftp_query_alarm GPROC 1 0 0

Device: GPROC 1 0 0. Alarm Count: 0. Alarm Info: 1


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-13


ftp_report_bsc

ftp_report_bsc

Description

Sets the FTP fault reporting for the entire BSC on or off.

Format

ftp_report_bsc <rep_request>

Parameters

rep_request resume Reporting turned on.

stop Reporting turned off.

Example

This example turns off the fault reporting for the BSC.

ftp_report_bsc stop


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-14


ftp_report_cage

ftp_report_cage

Description

Sets the FTP fault reporting for the specified cage on or off.

Format

ftp_report_cage <rep_request> <cage_no>

Parameters



cage_no 0-5 Specifies BSC cage number.

Example

This example turns off fault reporting for cage number 0.

ftp_report_cage stop 0


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-15


ftp_report_dev

ftp_report_dev

Description

Sets the FTP fault reporting on or off for the specified device.

Format

ftp_report_dev <rep_request> <sev_level> <DEVICE> <device_id1> <device_id2> <device_id3>


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-16


ftp_report_dev

Parameters



sev_level 0 All (used by both stop and resume report request)

1 Warning (used by resume report request only)

2 Minor (used by resume report request only)

3 Major (used by resume report request only)

4 Critical (used by resume report request only)

DEVICE Literal that uniquely identifies the specified device.




Example

This example turns on fault reporting for critical alarms only for a GPROC device.

ftp_report_dev resume 4 GPROC 1 0 0


Parameter: Value:

<sev_level> 4

<DEVICE> GPROC

68P81132E13-O

10/3/02-GR

5-17


ftp_severity_lvl

ftp_severity_lvl

Description

Sets the threshold for alarm reporting. Only alarms equal to, or more severe than, the specified threshold level are reported.

Format

ftp_severity_lvl <severity_level>

Parameters

severity_level 0 All

1 Warning

2 Minor

3 Major

4 Critical

Example

This example sets the alarm threshold for major alarms. Only major and critical alarms are now reported.

ftp_severity_lvl 3


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-18


ftp_trans_bsc

ftp_trans_bsc

Description

Sets the FTP alarm translation on or off for the entire BSC.

Format

ftp_trans_bsc <trans_request>

Parameters

trans_request resume Translation turned on.

stop Translation turned off.

Example

This example turns off fault translation for the entire BSC.

ftp_trans_bsc stop


✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-19


ftp_trans_cage

ftp_trans_cage

Description

Sets the FTP alarm translation on or off for the specified cage.

Format

ftp_trans_cage <trans_request> <cage_num>

Parameters



cage_num 0-5 Literal that uniquely identifies the specified cage.

Example

This example turns off fault translation for CAGE 1.

ftp_trans_cage stop 1



✔ ✔ ✔ ✔


Classification RC


Parameter: Value:

<trans_request> stop

<cage_num> 1

68P81132E13-O

10/3/02-GR

5-20


ftp_trans_dev

ftp_trans_dev

Description

Sets the FTP alarm translation on or off for the specified device.

Format

ftp_trans_device <translation_request> <DEVICE> <device_id1> [<device_id2>] [<device_id3>]

Parameters








✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-21


ftp_trans_dev

Example

This example turns off fault translation for the GPROC device.

ftp_trans_dev stop GPROC 1 0 0


Parameter: Value:

<trans_request> stop

<DEVICE> GPROC

68P81132E13-O

10/3/02-GR

5-22


query_audits

query_audits

Description

Lists the audit tests in progress for a specific device.

Format

query_audits <audit_type> <DEVICE> <device_id1> <device_id2> <device_id3>

Parameters

audit_type short List all audits for a specific device.

long List all info for all audits for a specific device.






✔ ✔ ✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-23


query_audits

Example

This example requests a short list of audits in progress for a GPROC device with an ID of 0 0 0.

query_audits short GPROC 0 0 0


Parameter: Value:

<audit_type> short

<DEVICE> GPROC

<device_id1> 0

<device_id2> 0

<device_id3> 0

68P81132E13-O

10/3/02-GR

5-24


set_span_alarm

set_span_alarm

Description

This command enables\disables a specific span alarm.

Format

set_span_alarm <all><mode> | <mode><index>

Parameters

mode on Turns the span alarm on.

off Turns the span alarm off.

index n Single alarm index. See “Alarm index definitions.”

all All span alarms.


✔ ✔ ✔ ✔



Related commands disp_span_alarm on page 4-72

68P81132E13-O

10/3/02-GR

5-25


set_span_alarm

Alarm index definitions

This section defines the alarm types and associated index numbers used with this command:

Example

This example disables the span link alarm “REMOTE_LOSS_ HOURLY” for a T1 link.

set_span_alarm off 1

Index

Alarm type

T1 span link E1 span link

0 REMOTE_LOSS_DAILY SYNC_LOSS_DAILY

1 REMOTE_LOSS_HOURLY SYNC_LOSS_HOURLY

2 REMOTE_OSS SYNC_LOSS_OOS

3 SLIP_LOSS_DAILY REMOTE_LOSS_DAILY

4 SLIP_LOSS_HOURLY REMOTE_LOSS_HOURLY

5 SLIP_LOSS_OSS REMOTE_OOS

6 REMOTE_TIME_OOS SLIP_LOSS_DAILY

7 AIS_TIME_OOS SLIP_LOSS_HOURLY

8 RED_DAILY SLIP_LOSS_OOS

9 RED_HOURLY SYNC_TIME_OOS

10 RED_OOS REMOTE_TIME_OOS

11 RED_OOS_TIME ——

68P81132E13-O

10/3/02-GR

5-26


tdm_conn_test

tdm_conn_test

Description

This command is used to request TDM connectivity tests.

Format

tdm_conn_test <all> | <ksw1_pair> <ksw2_pair>

Parameters

ksw1_pair 0-3 Source KSW pair

ksw2_pair 0-3 Destination KSW pair

all String specifying all active KSW pairs.

NOTE

If the parameter “all” is entered, all the active extended KSW paths will be tested. ksw1_pair cannot be equal to ksw2_pair.


✔ ✔


Classification RC


cage_audit on page 5-4



68P81132E13-O

10/3/02-GR

5-27


tdm_conn_test

Example 1

This example executes a TDM connectivity test on all the possible paths on the active TDM highway.

tdm_conn_test all

TDM Connect iv i ty Test

PATH STATUS REASON-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0 to 1PASS1 to 0FAIL Bad KSWX connect ion - Cage x Slot y, Cage xx Slot yy0 to 2FAIL Missing KSWX card - Cage x Slot y, Cage xx Slot yy2 to 0FAIL Bad KSWX connect ion - Cage x Slot y, Cage xx Slot yy0 to 3FAIL Bad KSWX card - Cage x Slot y, Cage xx Slot yy3 to 0 FAIL Bad KSWX connect ion - Cage x Slot y, Cage xx, Slot yy1 to 2PASS2 to 1PASS1 to 3PASS3 to 1PASS

Example 2

This example executes a TDM connectivity test on all the specified extended KSW paths.

tdm_conn_test 0 1

TDM Connect iv i ty Test

PATH STATUS REASON-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0 to 1PASS1 to 0FAIL Bad KSWX connect ion - Cage x Slot y, Cage xx Slot yy

68P81132E13-O

10/3/02-GR

5-28


test_vp

test_vp

Description

Tests the sanity of the specified VPs. This command must be run at the system where XCDR cards are located.

NOTE

This command must be run where transcoder cards are located.

Format

test_vp <all> | <3to1 | 6to1 | dual_24 | dual_48> | <XCDR xcdr_id> | <xcdr_id vp_id>


✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

5-29


test_vp

Parameters

all String “all” should be entered to initiate a test of all VPs on all XCDRs.

3to1 \ 6to1\dual_24|dual_48 Specifies the type of the XCDRs to be audited. Enter string “3to1” to test all VPs on all 3to1 type XCDRs. Each 3to1 type XCDR has 12 VPs. Enter string “6to1” to test all VPs on all “6to1” type XCDR. Each 6to1 type XCDR has 24 VPs. Enter string “dual_24” to test all VPs on all dual_24 type XCDRs. Each dual_24 type XCDR has 24 VPs. Enter string “dual_48” to test all VPs on all dual_48 type XCDRs. Each dual_48 type XCDR has 48 VPs.

XCDR xcdr_id Tests all VPs on a specific XCDR card. This parameter is composed of a string “XCDR,” and the second is the XCDR identifier.

xcdr_id vp_id (0-54| 0-47) Tests a specific VP on a specific XCDR. This parameter consists of two numbers. The first number is the XCDR identifier and the second number is a VP identifier on that XCDR. Enter the VP id depending on the type of that XCDR. Each 3to1 type XCDR has 12 VPs. Each 6to1 type XCDR has 24 VPs. Each dual_24 type XCDR has 24 VPs. Each dual_48 type XCDR has 48 VPs.

Example 1

test_vp 3to1

Tota l CAGEs to be audi ted = 2VP 0 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 1 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 2 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 3 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 4 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 5 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 6 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 7 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 8 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 9 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 1 0 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi tVP 1 1 ( 3 t o 1 ) (XCDR 2 (3TO1) /CAGE 0/SLOT 8) : Passed Audi t

Aud i t comple ted in cage 0 .VP 0 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 1 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi t

68P81132E13-O

10/3/02-GR

5-30


test_vp

VP 2 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 3 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 4 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 5 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 6 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 7 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 8 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 9 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 1 0 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi tVP 1 1 ( 3 t o 1 ) (XCDR 3 (3TO1) /CAGE 1/SLOT 6) : Passed Audi t

Aud i t comple ted in cage 1 .

Example 2test_vp dual_24

Tota l CAGEs to be audi ted = 2VP 0 ( 3 t o 1 ) (XCDR 4(DUAL_24) /CAGE 0/SLOT 4) : Passed AuditVP 1 ( 6 t o 1 ) (XCDR 4(DUAL_24) /CAGE 0/SLOT 4) : Passed AuditVP 2 ( 3 t o 1 ) (XCDR 4(DUAL_24) /CAGE 0/SLOT 4) : Passed Audit..

VP 2 3 ( 6 t o 1 ) (XCDR 4(DUAL_24) /CAGE 1/SLOT 4) : Passed AuditAudi t completed in cage 0.

VP 0 ( 3 t o 1 ) (XCDR 5(DUAL_24) /CAGE 1/SLOT 10) : Passed AuditVP 1 ( 6 t o 1 ) (XCDR 5(DUAL_24) /CAGE 1/SLOT 10) : Passed AuditVP 2 ( 3 t o 1 ) (XCDR 5(DUAL_24) /CAGE 1/SLOT 10) : Passed Audit..

VP 2 3 ( 6 t o 1 ) (XCDR 5(DUAL_24) /CAGE 1/SLOT 10) : Passed AuditAud i t comple ted in cage1.

NOTE

DUAL_48 type XCDR boards contain 48 VPs.

68P81132E13-O

10/3/02-GR

5-31



vp_sched_aud_off

Description

Disables the scheduled VP audit.

Format

vp_sched_aud_off

Parameters

None.

Example

vp_sched_aud_off


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

5-32


vp_sched_aud_off

68P81132E13-O

10/3/02-GR

5-33


vp_sched_aud_off

68P81132E13-O

10/3/02-GR

5-34

6

6 Statistics

Introduction

The statistics commands perform the following tasks:

❐ enable/disble statistics

❐ display/modify statistics for devices or cells

❐ modify statistics time interval for system

❐ monitor active (enabled) statistics for system

❐ report statistics data


10/3/02-GR

6-1

CHAPTER 6 - STATISTICS BSC MMI Commands

Requirements

The statistical element names are used with the following statistics commands:

❐ disp_element on page 4-39 (element literal must be lower case)

❐ disp_stats on page 4-78 (element literal must be upper case)

❐ on page 6-8 (element literal must be lower case)

❐ clear_stats on page 6-38 (element literal must be upper case)

Cell Number and Board IDs

Some statistical element names require use of a cell_number or a board_id. The following tables indicate which element names require entry of a cell_number or board_id . A table is presented for each of the following element categories:

❐ Per cell/per channel elements

❐ Per link

To use disp_stats or clear_stats for individual statistics, cell numbers are required. To change or display an element using chg_ele or disp_ele, no cell number is required.

Calculating Board IDs

Some commands (such as clear_stats) contain a board_id parameter. This parameter is used to identify a particular GPROC board location within the BSC. It is specified as a two-byte hexadecimal number which represents the cage and slot location of the GPROC.

To calculate the board_id number, use the following formula:

Example 1: For a GPROC in Cage 0, Slot 20:

board_id number = (0 + 1) (14 + 1) = (1) (15) = 115HEX

Example 2: For a GPROC in Cage 1, Slot 19:

board_id number = (1 + 1) (13 + 1) = (2) (14) = 214HEX

board_id number = (cage numberHEX +1) (slot numberHEX +1)

Byte 1 Byte 2

68P81132E13-O

10/3/02-GR

6-2

BSC MMI Commands CHAPTER 6 - STATISTICS

Per cell/per channel elements

Table 6-1 lists the elements per cell or per channel which require entry of the cell_number.

Table 6-1 Per cell/per channel elements requiring cell_number

Element literal

chg

_ele

men

t

dis

p_e

lem

ent

clea

r_st

ats

dis

p_s

tats

assgn_fail_sub_chan_config ✔ ✔

assgn_fail_sub_chan_in_use ✔ ✔

assgn_fail_sub_chan_unavail ✔ ✔

bsc_access_delay ✔ ✔

bsc_call_hold_time ✔ ✔

inter_bsc_ho_delay ✔ ✔

initl3_loc_update ✔ ✔

initl3_det_indication ✔ ✔

initl3_service_req ✔ ✔

initl3_page_resp ✔ ✔

clr_req_to_msc_before_ac ✔ ✔

clr_req_to_msc_after_ac ✔ ✔

clr_cmd_from_msc_before_ac ✔ ✔

clr_cmd_from_msc_after_ac ✔ ✔

bsc_switch_failure ✔ ✔

bsc_switch_success ✔ ✔

sccp_conn_refused ✔ ✔

sccp_conn_confirmed ✔ ✔

sccp_conn_released ✔ ✔

unsuccessful_assignment ✔ ✔

68P81132E13-O

10/3/02-GR

6-3


cipher_mode_fail ✔ ✔

clr_req_to_msc ✔ ✔

conn_refused ✔ ✔

conn_req_to_msc ✔ ✔

ho_req_msc_ok ✔ ✔

ho_req_msc_fail ✔ ✔

in_inter_ho ✔ ✔

inter_bsc_ms_fail ✔ ✔

inter_bsc_req_to_msc ✔ ✔

intra_bsc_ho ✔ ✔

intra_bsc_ho_fail ✔ ✔

intra_bsc_ho_lostms ✔ ✔

intra_bsc_ho_pri_blk ✔ ✔

intra_bsc_ho_req ✔ ✔

intra_cell_ho ✔ ✔

intra_cell_ho_fail ✔ ✔

intra_cell_ho_lostms ✔ ✔

intra_cell_ho_req ✔ ✔

ma_req_from_msc ✔ ✔

out_inter_ho ✔ ✔

total_calls ✔ ✔

ho_out_fail_cngst ✔ ✔

ho_in_fail_cngst ✔ ✔

channel_assigned_3to1 ✔ ✔

channel_assigned_6to1 ✔ ✔


Element literal

chg

_ele

men

t

dis

p_e

lem

ent

clea

r_st

ats

dis

p_s

tats

68P81132E13-O

10/3/02-GR

6-4


channel_blocked_3to1 ✔ ✔

channel_blocked_6to1 ✔ ✔

xcdr_bypass_3to1 ✔ ✔

xcdr_bypass_6to1 ✔ ✔

channel_failure_3to1 ✔ ✔

channel_failure_6to1 ✔ ✔

page_req_to_ebts ✔ ✔

sub_chan_blk_1st_try ✔ ✔

sub_chan_blk_inter_bsc_ho ✔ ✔

sub_chan_blk_inter_cell_ho ✔ ✔

sub_chan_blk_intra_cell_ho ✔ ✔

sub_chan_blk_retry ✔ ✔


Element literal

chg

_ele

men

t

dis

p_e

lem

ent

clea

r_st

ats

dis

p_s

tats

68P81132E13-O

10/3/02-GR

6-5


Per link

Table 6-2 lists the elements per link which require entry of the board_id.

Table 6-2 Per link elements requiring board_id

Element literal

chg

_ele

men

t

dis

p_e

lem

ent

clea

r_st

ats

dis

p_s

tats

congestion_lost_msu ✔ ✔

frmr ✔ ✔

i_frames_rx ✔ ✔

i_frames_tx ✔ ✔

invalid_frames_rx ✔ ✔

msu_discarded ✔ ✔

mtp_changeback ✔ ✔

mtp_changeover ✔ ✔

mtp_congestion ✔ ✔

mtp_linkfail ✔ ✔

mtp_link_ins ✔ ✔

mtp_local_busy ✔ ✔

mtp_local_mgt ✔ ✔

mtp_mgt_inhibit ✔ ✔

mtp_mgt_uninhibit ✔ ✔

mtp_msu_tx ✔ ✔

mtp_msu_rx ✔ ✔

mtp_neg_acks ✔ ✔

mtp_remote_mgt ✔ ✔

mtp_remote_proc ✔ ✔

mtp_re_tx ✔ ✔

68P81132E13-O

10/3/02-GR

6-6


mtp_restoration ✔ ✔

mtp_sif_sio_rx ✔ ✔

mtp_sif_sio_tx ✔ ✔

mtp_sl_ack ✔ ✔

mtp_sl_alignment ✔ ✔

mtp_sl_congestion ✔ ✔

mtp_sl_error_rate ✔ ✔

mtp_sl_fail ✔ ✔

mtp_sl_fibr ✔ ✔

mtp_start_rpo ✔ ✔

mtp_stop_rpo ✔ ✔

mtp_su_error ✔ ✔

mtp_unavailable ✔ ✔

n2_expiry ✔ ✔

page_req_from_msc ✔ ✔ ✔ ✔

sabm_tx ✔ ✔

sl_congestion ✔ ✔

sl_stop_congestion ✔ ✔

Table 6-2 Per link elements requiring board_id

Element literal

chg

_ele

men

t

dis

p_e

lem

ent

clea

r_st

ats

dis

p_s

tats

68P81132E13-O

10/3/02-GR

6-7


chg_element

Description

Enables and modifies statistical element names (measurement-type parameters) in the Configuration Management (CM) database. See Appendix B for a detailed list of statistical element name definitions.

Format

There are two separate statistical applications of the chg_element command line. (There are corresponding applications of disp_element). The syntax of each chg_element application varies. Notice the different parameters used in each of them.

A detailed explanation of the parameters is shown beginning on the next page. This section contains descriptions and instructions for each of the three categories of statistical application: Counter, Distribution, and Duration.

Index numbers

Index “0” enables or disables a statistic. Index “2” sets a threshold for an alarm-related statistic.

To set indexes 0 or 2 enter the following parameters:

EXAMPLE: chg_element <statistical_element_name>, <index> <new_value>


✔ ✔ ✔ ✔






clear_stats on page 6-38

68P81132E13-O

10/3/02-GR

6-8


To verify that a statistic has been modified, use disp_element with the following parameters:

EXAMPLE: disp_element <statistical_element_name>,<index>

To set indexes 4 and 5 enter the following parameters:

EXAMPLE: chg_element<statistical_element_name>, <index>, <bin_number> <new_value>

Index “4” sets the minimum value of a bin range. Index “5” sets the maximum value for a bin range. Bin ranges are set only in Distribution (Normal and Weighted) statistics. Maximum and minimum values are always required; default values exist.

To verify that a statistic has been modified, use disp_element with the following parameters:

EXAMPLE: disp_element <statistical_element_name>,<index>,<bin_number>

The < > indicates a required parameter. The required parameters are entered in a position-dependent order.

Refer to “Requirements” at the beginning of this chapter for the statistical commands requiring input of cell_number or board ID parameters.

68P81132E13-O

10/3/02-GR

6-9


Parameters

statistical_element_name String identifying a statistical parameter in the CM database. See parameter tables throughout the chapter and in Appendix B.

index Value that identifies how a specific statistical parameter is being modified. This index tells the system that you are choosing to: enable, disable, set a threshold, set a bin minimum or maximum — to set up an operation.

0 State of parameter (enabled or disabled)

2 Threshold (alarm)

4 Bin minimum (for a specific bin)

5 Bin maximum (for a specific bin)

new_value New value for a specific statistical parameter. The value may enable or disable a statistic. Or, the value may modify a bin maximum, a bin minimum, or an alarm threshold. This value is the component of the chg_element command that causes the command to enable or disable, or provides a new value for a bin or a threshold.

bin_number 0-9 This parameter is used for Distribution Statistics only.(0-9)Specifies the bin whose range is being set. Each bin (or set of bins) may be used to measure an event. There are 10 bins (numbered 0-9). Data is collected (in bins) to monitor events in order to obtain distribution statistics.

68P81132E13-O

10/3/02-GR

6-10


Statistical applications

There are three distinct categories of statistics: Counter, Distribution, and Duration. They are referred to as “measurement-related types” or “object types” which are used for performance measurement. When enabled, each measurement-related type parameter (statistical element name) provides unique statistical data.

Statistical element names are used with each type of statistic. They are literal parameters; each is entered as a string.

Some parameter tables are contained in this chapter. A complete list of statistical element names (parameters) is contained in Appendix B of this manual. Statistical element names shown in this command manual cross-reference those in Appendix A of Performance Management at the OMC.

“Measurement-related type” statistical applications use the chg_element command along with the indexing factor(s) from Table 6-3. Chg_element is used as a generic command. The index values allow the user to perform more than one operation using the same generic (chg_element) command.

For example, an operator may first use chg_element to enable a statistic; then, using the command a second time, to modify the alarm-related threshold for alarm-generating statistics. See “Command Instructions.”

68P81132E13-O

10/3/02-GR

6-11


Command instructions

Enabling a statistic

In the following set of procedures, you will learn how to Enable and Disable a statistic. Each of the three kinds of statistics [Counter, Distribution, and Duration (Total Time)] must be enabled in order to obtain statistical data.

Counter Statistics (without alarm thresholds) and Total Time Statistics are shown in this section because they may only be enabled or disabled. All other statistics may be enabled, disabled and modified. They will be discussed later in this chapter.

Counter statistics

Counter Statistics involve the use of a “counter” which is a value representing the number of occurrences of an event. An event may be monitored using statistical element names (measurement-related type parameter). To identify the Counter statistics which can be enabled, see Appendix B for a complete list.

Duration (total time) statistics

Total Time statistics involve the use of a “timer” to collect a cumulative time value. The timer starts when an event occurs and stops when it ceases. This event is recorded for statistical analysis. The resulting statistics express the total amount of time a particular event occurred, as well as minimum, maximum, and mean durations (in milliseconds).

For a complete list of statistics element names and definitions see Appendix B in this manual. Also, for more information, see Performance Management at the OMC, Chapter 2 and Appendix A .

68P81132E13-O

10/3/02-GR

6-12


Enabling a statistic

In Appendix B, locate the statistical element name that you wish to enable or disable and use the format listed below.


Enter 0 for <index> to indicate that a statistic is being either enabled or disabled.

Enter 1 for <new_value> to enable; enter 0 for <new_value> to disable a statistic.

Examples

Examples 1 and 2 show you how to enable and disable a Duration (Total Time) statistic.

After the statistic is enabled (or disabled), verify it by using the disp_element command. (Remember that disp_element does not require the use of a new_value; however, when using chg_element, a new_value is required.) If the statistic is enabled, the system response will show:

cipher_mode_fail = 1

If the statistic is disabled, the system response will show:

cipher_mode_fail = 0

68P81132E13-O

10/3/02-GR

6-13


Example 1:

To Enable the statistic:

chg_element cipher_mode_fail,0 1

disp_element cipher_mode_fail,0

c ipher_mode_fa i l = 1

Example 2:

To Disable the statistic:

chg_element cipher_mode_fail, 0,0

disp_element cipher_mode_fail,0

c ipher_mode_fa i l = 0

Examples 3 and 4 show you how to enable and disable a Counter statistic.

After the statistic is enabled (or disabled), verify it by using the disp_element command. (Remember that disp_element does not require the use of a new_value; however, when using chg_element, a new_value is required.) If the statistic is enabled, the system response will show:

mtp_sl_fail = 1

If the statistic is disabled, the system response will show:

mtp_sl_fail = 0

Example 3:

To Enable the statistic:

chg_element mtp_sl_fail, 0 1

disp_element mtp_sl_fail, 0

mtp_s l_ fa i l = 1

68P81132E13-O

10/3/02-GR

6-14


Example 4:

To Disable the statistic:

chg_element mtp_sl_fail, 0 0

disp_element mtp_sl_fail, 0

mtp_s l_ fa i l = 0

68P81132E13-O

10/3/02-GR

6-15


Setting a threshold

In the following set of instructions/procedures, you will learn how to set Thresholds for Counter (alarm-related) statistics. Counter Statistics involve the use of a “counter” which is a value representing the number of occurrences of an event. Some of the Counter Statistics require threshold values to be set. When a threshold is reached, an alarm is sent to the Operations and Maintenance Center (OMC). Table 6-3 lists counter statistics which require threshold values to be set.

Setting a counter threshold

Locate the parameter (statistical element name) in Table 6-3 that you wish to modify. Then, enter the command using the format listed below.

To set a threshold, enter the command using the following format:


Enter 2 for <index> to indicate that a threshold is being modified.

Enter the value for <new_value> that you want to use to modify the current threshold to.

68P81132E13-O

10/3/02-GR

6-16


Example 1:

Example 1 shows you how to set the alarm threshold of a Counter statistic. N2_expiry is a “per link” statistical element name.

Using disp_element, display the current value of the threshold. Remember that disp_element does not require the use of a new_value; however, when using chg_element, a new_value is required to determine whether it needs to be modified. If so, use chg_element to modify the threshold to the desired value of 10. After the threshold has been modified, verify it by using the disp_element command a second time. If the threshold has been correctly modified, the system response will show: n2_expiry = 10.

disp_element n2_expiry, 2

n2_exp i ry = 8

chg_element n2_expiry, 2 10

COMMAND ACCEPTED

disp_element n2_expiry,2

n2_expiry = 10

Table 6-3 provides a list of alarm-related counter statistic parameters. All of the counter statistics may be found in Appendix B.

68P81132E13-O

10/3/02-GR

6-17


Table 6-3 Counter statistics threshold parameter

Statistical element nameIndex factor

Valid values Basis

assgn_fail_sub_chan_config 2 min: 0

max: 2147483647

BSC

assgn_fail_sub_chan_in_use 2 min: 0

max: 2147483647

BSC

assgn_fail_sub_chan_unavail 2 min: 0

max: 2147483647

BSC

cipher_mode_fail 2 min: 0

max: 2147483647

BSC

congestion_lost_msu 2 min: 0

max: 2147483647

SS7 link

frmr 2 min: 0 max: 2147483647

X.25 link

ho_req_msc_fail 2 min: 0 max: 2147483647

BSC

inter_bss_ms_fail 2 min: 0 max: 2147483647

BSC

intra_bss_ho_fail 2 min: 0 max: 2147483647

BSC

intra_bss_ho_lostms 2 min: 0 max: 2147483647

BSC

intra_bss_ho_pri_blk 2 min: 0 max: 2147483647

BSC

intra_cell_ho_fail 2 min: 0 max: 2147483647

BSC

intra_cell_ho_lostms 2 min: 0 max: 2147483647

BSC

invalid_frames_rx 2 min: 0 max: 2147483647

X.25 link

msu_discarded 2 min: 0 max: 2147483647

SS7 link

mtp_neg_acks 2 min: 0 max: 2147483647

SS7 link

68P81132E13-O

10/3/02-GR

6-18


mtp_re_tx 2 min: 0 max: 2147483647

SS7 link

mtp_sl_ack 2 min: 0 max: 2147483647

SS7 link

mtp_sl_alignment 2 min: 0 max: 2147483647

SS7 link

mtp_sl_congestion 2 min: 0 max: 2147483647

SS7 link

mtp_sl_error_rate 2 min: 0 max: 2147483647

SS7 link

mtp_sl_fail 2 min: 0 max: 2147483647

SS7 link

mtp_sl_fibr 2 min: 0 max: 2147483647

SS7 link

mtp_start_rpo 2 min: 0 max: 2147483647

SS7 link

mtp_su_error 2 min: 0 max: 2147483647

SS7 link

n2_expiry 2 min: 0 max: 2147483647

X.25 link

routing_syntax 2 min: 0 max: 2147483647

BSS

routing_unknown 2 min: 0 max: 2147483647

BSS

sl_congestion 2 min: 0 max: 2147483647

SS7 link



Valid values Basis

68P81132E13-O

10/3/02-GR

6-19


sub_chan_blk_1st_try 2 min: 0 max: 2147483647

BSC

sub_chan_blk_inter_bsc_ho 2 min: 0 max: 2147483647

BSC

sub_chan_blk_inter_cell_ho 2 min: 0 max: 2147483647

BSC

sub_chan_blk_intra_cell_ho 2 min: 0 max: 2147483647

BSC

sub_chan_blk_retry 2 min: 0 max: 2147483647

BSC



Valid values Basis

68P81132E13-O

10/3/02-GR

6-20


Setting bin ranges

In the following set of procedures, you will learn how to set bin ranges (minimums and maximums for distribution statistics). A bin is a range displaying the number of times an event occurs. A bin, therefore, represents a “pool of data” which is collected in a histogram. Default values (minimum/maximum) for each of the bins are listed in Table 6-4 and Table 6-5.

Normal distribution statistics

Normal Distribution statistics display how often a particular event or state-change occurs. This specific application process reports all events. The value of the event is used to determine which bin will be incremented. (The bin determination is based on the range of each bin.) Then, the value reported (for each bin) will be incremented by each occurrence of an event that falls into the range of a specific bin. The statistical value displayed, will be the cumulative total of the events occurring within that specific bin range.

The bin size may be set relative to the event being measured. You must use 10 bins (0-9) for a statistic that is being measured. The size of each bin is variable. The relative sizes of those bins depends on how you want to focus your analysis.

For example, when measuring a statistic, you may want to size the bins so that the majority of the bins will be placed in the period of the greatest activity. Data can therefore, be collected in more meaningful blocks of statistical information. (By reducing the sizes/ranges of the bins, you can more closely scrutinize a relatively large amount of activity.)

The total number of bins never changes (10), but the relative sizes of the individual bins can be changed (adjusted) by the user in proportion to the activity being measured.

Weighted distribution statistics

Weighted Distribution statistics are similar to “Normal” Distribution statistics. This specific application process begins at a particular value and updates the data (that is being collected) when that value changes. Weighted distributions record the time (in milliseconds) that an

68P81132E13-O

10/3/02-GR

6-21


element is at a specific value. The statistical value displayed, will be the cumulative time of the events occurring within that specific bin range.

Normal distributions count and record the number of times (how often) a statistical element name is at a specific value, but do not relate the value to time.

For a complete list of parameter definitions see Appendix B. For more information, see Performance Management at the OMC.

68P81132E13-O

10/3/02-GR

6-22


Normal distribution bin ranges

In Table 6-4 , locate the parameter (statistical element name) that you wish to modify. Enter the command using the format listed. (The command examples, beginning on the next page, illustrates the application of this procedure.)

Distribution statistics require bin values (bin minimums and bin maximums). Each bin contains one minimum (use index “4”) and one maximum (use index “5”). You must enter the command twice for each bin number; once to set a bin minimum, and a second time to set a bin maximum.

chg_element <statistical_element_name>,<index>, <bin_number> <new_value>

Enter 4 for <index> to indicate that a bin minimum is being modified.

Enter 5 for <index> to indicate that a bin maximum is being modified.

Enter the bin (0-9) for <bin_number> to indicate which bin will be modified.

Enter the bin value for <new_value> to indicate the new minimum value or new maximum value that is being set.

Default ranges apply to both minimum (4) and maximum (5) values for the same bin. See “Default Ranges Per Bin” column in Table 6-4.

Chg_element command must be entered twice; once to set each bin minimum (index 4) and once to set each bin maximum (index 5).

Bin Minimums and Maximums can be set to the same value for the same bin.

68P81132E13-O

10/3/02-GR

6-23


Examples

Set bin ranges for Normal Distribution Statistics as follows:

First display (using the disp_element command) the current values of the 10 bins (both miminum and maximum values). Remember that disp_element does not require the use of a new_value; however, when using chg_element, a new_value is required.

Use the chg_element command to change the current bin values to the desired values.

Use the disp_element command again to display the values and verify that the changes have been made.

disp_element bsc_access_delay,5,0

bsc_access_de lay = 10000





















68P81132E13-O

10/3/02-GR

6-24


















To set the bin ranges for any of the ten bins of a distribution statistic, use chg_element to modify the bin values. Notice that the bin maximums and minimums are set consecutively. For each bin value (0-9) the minimum value (index “4”) is set. Then, on the next line the maximum value (index “5”) for that specific bin is set.

You can set the bin minimums and maximums in any order, but we suggest that you set them as shown below.

chg_element bsc_access_delay,4,0 0









68P81132E13-O

10/3/02-GR

6-25














Verify the new values using the disp_element command a second time. If the bin values have been correctly modified, the system response will show the new value for each tch_delay that has been changed. Contrast this output with the previous output of the disp_element command. Notice the different values that are displayed.


bsc_access_delay = 0













68P81132E13-O

10/3/02-GR

6-26
























disp_element bsc_access_delay, 4,9


disp_element bsc_access_delay, 5,9


Cross-references to the measure-type parameters contained in “Normal Distribution Statistics” may be found in Appendix A of Performance Management at the OMC.

68P81132E13-O

10/3/02-GR

6-27


Table 6-4 Normal distribution statistics parameter

Statistical element name

Indexfactor

Bin num

Valid values per bin

Basis

bsc_access_delay 4

5

0 to 9

0 to 9

min: 0

max:

2147483647

min: 0

max: 2147483647

default: 4294967295

BSC

bsc_call_hold_time 4

5

0 to 9

0 to 9

min: 0

max:

2147483647

min: 0

max: 2147483647

default: 4294967295

BSC

inter_bsc_ho_delay 4

5

0 to 9

0 to 9

min: 0

max:

2147483647

min: 0

max: 2147483647

default: 4294967295

BSC

68P81132E13-O

10/3/02-GR

6-28


Weighted distribution bin ranges

In Table 6-5, locate the parameter (statistical element name) that you wish to modify. Enter the command using the format listed. (The command example, beginning on the next page, illustrates the application of this procedure.)

Distribution statistics require bin values (bin minimums and bin maximums). Each bin contains one minimum (use index “4”) and one maximum (use index “5”). You must enter the command twice for each bin number; once to set a bin minimum, and a second time to set a bin maximum.

EXAMPLE: chg_element <statistical_element_name>,<index>,<bin_number> <new_value>

Default ranges apply to both minimum (4) and maximum (5) values for the same bin. See “Default Ranges Per Bin” column in Table 6-5.

Chg_element command must be entered twice; once to set each bin minimum (index 4) and once to set each bin maximum (index 5).

Bin Minimums and Maximums can be set to the same value for the same bin.

68P81132E13-O

10/3/02-GR

6-29


Examples

Set bin ranges for Weighted Distribution Statistics as follows:

First display (using the disp_element command) the current values of the 10 bins (both miminum and maximum values). Remember that disp_element does not require the use of a new_value; however, when using chg_element, a new_value is required.

Use the chg_element command to change the current bin values to the desired values.

Use the disp_element command again to display the values and verify that the changes have been made.

disp_element cpu_usage,4,0

cpu_usage = 0


cpu_usage = 10


cpu_usage = 11


cpu_usage = 20


cpu_usage = 21

Table 6-5 Weighted distribution statistics parameter

Statisticalelement name

Indexfactor

Binnum

Valid valuesper bin

Basis

cpu_usage 4

5

0 to 9

0 to 9

min: 0

max:

2147483647

min: 0

max: 2147483647

Default: 4294967295

gproc

68P81132E13-O

10/3/02-GR

6-30



cpu_usage = 30


cpu_usage = 31


cpu_usage = 40


cpu_usage = 41


cpu_usage = 50


cpu_usage = 51


cpu_usage = 60


cpu_usage = 61


cpu_usage = 70


cpu_usage = 71


cpu_usage = 80


cpu_usage = 81


pu_usage = 90


cpu_usage = 91


cpu_usage = 100

68P81132E13-O

10/3/02-GR

6-31


To set the bin ranges for any of the ten bins of a distribution statistic, use chg_element to modify the bin values. Notice that the bin maximums and minimums are set consecutively. For each bin value (0-9) the minimum value (index “4”) is set. Then, on the next line the maximum value (index “5”) for that specific bin is set.

You can set the bin minimums and maximums in any order, but we suggest that you set them as shown below.

chg_element cpu_usage,4,0 0




















68P81132E13-O

10/3/02-GR

6-32


Verify the new values using the disp_element command a second time. If the bin values have been correctly modified, the system response should show the new value (in milliseconds) for each cpu_usage that has been changed. Contrast this output with the previous output of the disp_element command.


cpu_usage = 0


cpu_usage = 1


cpu_usage = 2


cpu_usage = 6


cpu_usage = 7


cpu_usage = 11


cpu_usage = 12


cpu_usage = 17


cpu_usage = 18


cpu_usage = 22


cpu_usage = 23


cpu_usage = 27


cpu_usage = 28

68P81132E13-O

10/3/02-GR

6-33



cpu_usage = 32


cpu_usage = 33


cpu_usage = 37


cpu_usage = 38


cpu_usage = 42


cpu_usage = 43


cpu_usage = 47

CROSS-REFERENCES to the measure-type parameters contained in “Weighted Distribution Statistics” may be found in Appendix A of Performance Management at the OMC.

68P81132E13-O

10/3/02-GR

6-34


Setting an interval for stat_interval

Stat_interval is a non-statistical parameter that is used with statistical (measure-type) parameters to aid in generating statistical data. The command chg_element stat_interval is used to configure (set) the frequency (how often) statistical readings are to be performed. See Appendix B for statistical parameter definitions.

You must complete the following steps to properly set the interval duration for the parameter, stat_interval:

❐ Determine the duration of the interval using the disp_element stat_interval command.

❐ Determine whether you want to change the duration of the interval. Use chg_element stat_interval command.

❐ Verify that the change has been completed using the disp_element stat_interval command.

68P81132E13-O

10/3/02-GR

6-35


Procedure for Setting an Interval

The following provides a concise overview of the procedure. Review these examples for important notes and details regarding the proper use of the commands shown.

Below, you will see how to use related commands to set an interval. The commands that are required to perform this procedure are disp_element stat_interval, and chg_element stat_interval.

Remember that disp_element does not require an index. In addition, chg_element stat_interval does not require the use of an index. See the non-statistical applications of chg_element in a previous chapter. In the list of non-statistical parameters, you will see that the element name stat_interval does not require the use of an index.

Also, if necessary see the complete command description of disp_element for instructions regarding use of the command in a previous chapter.

Use disp_element stat_interval to see what the duration of the interval is set to at location 0.

disp_element stat_interval

s ta t_ i n te r va l = 30

(This system response shows that stat_interval is currently set for 30 minutes. Disp_element stat_interval is used to check the interval duration before and after modifying it with chg_element. )

After displaying the duration of the statistical interval, use chg_element stat_interval to change the interval duration to a desired value between 5 and 60 minutes. (The duration of stat_interval may be changed to accommodate a user’s specific needs.)

chg_element stat_interval 6

(This command changes the duration of stat_interval to 6 minutes.)

NOTE

Note that in current implementation OMC accepts statistics in 30-minute intervals only, regardless of the interval setting in this command.

68P81132E13-O

10/3/02-GR

6-36


The following circumstances apply when modifying stat_interval with chg_element:

The default value of stat_interval is 30 (minutes).

The operator may change the interval to a period from 5 to 60 minutes.

Each interval (0-3) will use the same duration (interval time period). You may not set any of the 4 intervals individually.

After modifying the current stat_interval, use disp_element stat_interval to verify that the value has changed. The stat_interval value will equal 6.

disp_element stat_interval

s ta t_ in te r va l = 6

This system response shows that stat_interval has been changed to 6 minutes.) If you change stat_interval from the default value (30), do not forget to reset stat_interval back to 30 (minutes).

NOTE

If operator fails to reset the interval to 30 (min), then, OMC calculations of the Key Statistics and Health operator fails to reset the interval to 30 (min), then, OMC calculations of the Key Statistics and Health Indicators are interrupted for the entire period — until the interval is reset to 30 (mins).

68P81132E13-O

10/3/02-GR

6-37


clear_stats

clear_stats

Description

This command provides you with the ability to reset statistics. When using the clear_stats command, the statistic may require an individual cell identifier or a board identifier (cell_number or board_id).

From the beginning of the current interval, this command clears statistical activity up to the time of the execution of the actual command (clear_stats). After the execution of the clear_stats command, if there is any time remaining in that (current) interval, activity occurring will be shown. (If there is no statistical activity, the statistic will still appear to be completely clear for that interval. See examples.)

Also, it is important to note that each new interval begins from an automatically cleared (or reset) state.

Format

clear_stats <statistical_element_name> [<cell_number=<cell_number>] [<board_id>]


✔ ✔ ✔ ✔






68P81132E13-O

10/3/02-GR

6-38


clear_stats

NOTE

The statistical_element_name parameters (and the basis for each of those statistical parameters) are defined in Appendix B.

The cell_number parameter should only be entered to identify a “per channel” statistic.

The board_id parameter should only be entered to identify a “per link” statistic.

The value of a specific statistical_element_name can only be reset for the current statistical interval.

Parameters

STATISTICAL_ELEMENT_NAME Global name of statistics that represents the statistics at the time of creation, deletion, and update (See Table 6-1 and Table 6-2 to determine need for cell_number or board_id. Also, see Appendix B for definitions). Use upper case lettering when entering this portion of the command.

cell_number 0-239 Local cell ID, indicating from which cell to clear statistics. Specify for per cell counter stats only.

board_id GPROC CPU ID (for example, 115h) identifying the board from which to clear statistics. Specify for a per link statistic only. The board_id is determined from cage and GPROC slot numbers.

Examples

Example 1 is a “per cell” counter statistic that requires a cell_number when clear_stats is used.



Also, when entering this command, use UPPER CASE lettering for the statistical_element_name described.

68P81132E13-O

10/3/02-GR

6-39


clear_stats

However, to verify that clear_stats has worked, a cell_number is required to display the statistc. In the example below, the statistic is being cleared in interval number three (3). When interval three expires, use disp_stats to display the statistical value of the interval (3). (Don’t forget to enter the interval number directly after disp_stats in the command. See specific disp_stats command details later in this chapter.) The following output will be displayed in the system response:

Example 1:

clear_stats TOTAL_CALLS

disp_stats 3 TOTAL_CALLS

SITE: 0

MEAS_TYPE : TOTAL_CALLS

Counter : 0

Where:

3 = the interval numberTOTAL_CALLS = requested statistics

Because the Counter reads 0, no additional activity occurred in interval three after the statistic was cleared (using the clear_stats command. If a statistic is a rapidly occurring event, activity will most likely appear during the time remaining (in the current interval) after using the clear_stats command.)

NOTE

Remember that the statistic will not appear to have cleared/reset until the next statistical interval (stat_interval) begins. So, use disp_stat to verify that the statistic has cleared after the new interval begins.

Example 2 is a “per bsc” counter statistic and does not require a board_id when clear_stats is used.



68P81132E13-O

10/3/02-GR

6-40


clear_stats

To verify that clear_stats has worked, do not enter a cell identifier (cell_number) or a board identifier (board_id) when displaying the statistic. In the example below, the statistic is being cleared in interval number one (1). When interval one expires, use disp_stats to display the statistical value of the interval (1). (Don’t forget to enter the interval number directly after disp_stats in the command. See specific disp_stats command details.) The following output will be displayed in the system response:

Example 2:

clear_stats PAGE_REQ_FROM_MSC_FAIL

disp_stats 1 PAGE_REQ_FROM_MSC_FAIL

SITE: 0 BSS #: 1

MEAS_TYPE : PAGE_REQ_FROM_MSC_FAIL

Counter : 0

Because the Counter reads 0, no additional activity occurred in interval one after the statistic was cleared (using the clear_stats command. If a statistic is a rapidly occurring event, activity will most likely appear during the time remaining (in the current interval) after using the clear_stats command.)

NOTE


Example 3 is a “per link” counter statistic that requires a board_id when the clear_stats command is used.




68P81132E13-O

10/3/02-GR

6-41


clear_stats

Also, to verify that clear_stats has worked for per-link counter statistics, a board_id is required to display the statistic. In the example below, the statistic is being cleared in interval number one (1). When interval one expires, use disp_stats to display the statistical value of the interval (1). (Don’t forget to enter the interval number directly after disp_stats in the command. See specific disp_stats command details.) The following output will be displayed in the system response:

Example 3:

clear_stats MTP_SL_FAIL board_id = 0115h

disp_stats 1 MTP_SL_FAIL board_id = 0115h



MEAS_TYPE : MTP_SL_FAIL

Counter : 0

(Because the Counter reads 0, no additional activity occurred in interval one after the statistic was cleared (using the clear_stats command). If a statistic is a rapidly occurring event, activity will most likely appear during the time remaining (in the current interval) after using the clear_stats command.)

NOTE


Example 4 is a “per link” total time (duration) statistic that requires a board_id when the clear_stats command is used.




68P81132E13-O

10/3/02-GR

6-42


clear_stats

Also, to verify that clear_stats has worked for per-link counter statistics, a board_id is required to display the statistic. In the example below, the statistic is being cleared in interval number one (1). When interval one expires, use disp_stats to display the statistical value of the interval (1). (Don’t forget to enter the interval number directly after disp_stats in the command. See specific disp_stats command details.) The following output will be displayed in the system response:

Example 4:

clear_stats MTP_UNAVAILABLE board_id = 0115h

disp_stats 1 MTP_UNAVAILABLE board_id = 0115h



MEAS_TYPE : MTP_UNAVAILABLE

Durat ion Va lue (ms) : 0

Durat ion Mean (ms) : 0

Durat ion Max. (ms) : 0

Durat ion Min . (ms) : 0

(Because the Duration Value reads 0, no additional activity occurred in interval one after the statistic was cleared (using the clear_stats command). If a statistic is a rapidly occurring event, activity will most likely appear during the time remaining (in the current interval) after using the clear_stats command.)

NOTE


68P81132E13-O

10/3/02-GR

6-43


sar

sar

Description

Depending on which keyword is entered, SAR will execute the following tasks: (a) display CPU utilization of all GPROCS in the BSC, or (b) display/modify the SAR threshold and margin values in the CM database.

Format

sar <threshold <threshold_val> margin <margin_val>> | <margin <margin_val> threshold <threshold_val>> | <threshold <threshold_val>> | <margin <margin_val>> | <values> | <defaults> | <summary>


✔ ✔ ✔ ✔

Security level level 1,2



68P81132E13-O

10/3/02-GR

6-44


sar

Parameters

* threshold_val must be greater than or equal to margin_val + 5

Table 6-6 SAR Keyword/Parameter Summary

KeywordClassifica

tionParameter

Min.Value

Max.Value

DefaultValue

SecurityLevel

threshold RC/SYSGEN

threshold_val*

10% 95% 80% 2

margin RC/SYSGEN

margin_val* 5% 40% 20% 2

defaults RC/SYSGEN

— — — — 2

values RC/SYSGEN

— — — — 1

summary RC — — — — 1

Table 6-7 SAR Command Summary

Command Description

sar threshold <threshold_val> margin <margin_val>

or

sar margin <margin_val> threshold <threshold_val>

Changes both the threshold and margin values in the CM database.

sar threshold <threshold_val> Changes only the threshold value in the CM database.

sar margin <margin_val> Changes only the margin value in the CM database.

sar defaults Returns the threshold and margin to their default values.

sar values Displays the configured threshold and margin values from the CM database.

sar summary Displays a summary of CPU utilization values on all the GPROCS in the BSC, including the GPROC function and the number of links it has.

68P81132E13-O

10/3/02-GR

6-45


sar

Example 1

This example changes the threshold to 70% and margin to 30%.

sar threshold 70 margin 30

or

sar margin 30 threshold 70

Example 2

This example changes only the threshold to 70%; the margin remains unchanged.

sar threshold 70

Example 3

This example changes only the margin to 30%; the threshold remains unchanged.

sar margin 30

Example 4

This example displays the configured threshold/margin values.

sar values

SAR Threshold = 80%

SAR Margin = 20%

Example 5

This example returns the threshold/margin to their default values.

sar defaults

68P81132E13-O

10/3/02-GR

6-46


sar

Example 6

This example displays the CPU utilization on all the GPROCS in the BSC.

sar summary

GPROC# CPU ID FUNCTION GPROC Type #MTLs #XBLs #SITEs CPU% ALARM

-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0 0 1 1 5 BSP EGPROC 0 1 N / A 1% Clear

9 0 2 1 7 LCF 0 GPROC 2 2 0 5% Clear

1 0 0 2 1 a LCF 2 GPROC 0 0 1 2 5% Clear

1 0 1 1 a LCF 3 GPROC 0 0 1 2 4% Clear

1 1 0 2 1 9 LCF 4 EGPROC 0 0 1 2 1% Clear

3 0 1 1 8 LCF 5 EGPROC 0 0 1 2 1% Clear

1 2 0 2 1 8 LCF 6 EGPROC 0 0 1 2 1% Clear

4 0 1 1 7 LCF 7 GPROC 0 0 1 2 4% Clear

1 3 0 2 1 6 LCF 8 EGPROC 0 0 8 1% Clear

5 0 1 1 6 LCF 9 EGPROC 0 0 0 1% Clear

6 0 1 1 4 LCF 10 GPROC 0 0 0 4% Clear

8 0 2 1 5 OMF GPROC N / A 1 N / A 1% Clear

7 0 1 1 3 ENABLED GPROC N / A N / A N / A 4% Clear

1 4 0 2 1 4 ENABLED GPROC N / A N / A N / A 4% Clear

1 5 0 2 1 3 ENABLED GPROC N / A N / A N / A 4% Clear

2 0 1 1 9 DISABLED EGPROC N / A N / A N / A N / A N / A

68P81132E13-O

10/3/02-GR

6-47


stats

stats

Description

Enables or disables statistical reporting.

Format

stats <mode>

Parameters

mode on Enables statistical reporting.

off Disables statistical reporting.

Example

This example enables statistical reporting.

stats on

COMMAND ACCEPTED: all statist ics turned ON


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

6-48

7

7 Call trace

Introduction

The BSC provides call processing functions. The call trace commands described in this chapter may be used for debugging and tracing purposes. This allows the user to debug a specific problem or simply monitor system operations.


10/3/02-GR

7-1

CHAPTER 7 - CALL TRACE BSC MMI Commands

About call trace

Enabling call trace

Before using the call trace feature it must be enabled. Use the chg_element command to enable the cp_option_call_trace element name. Refer to Chapter 2 – “Configuration management” for additional information.

Check the chg_element command output using the disp_element command with the cp_option_call_trace element name. Refer to Chapter 3 – “Display” for additional information.

Call trace commands

Two commands are associated with the call trace feature. A brief description for each is provided below. A more detailed description is provided on the pages to follow, including functions and associated parameters.

❐ find_sccp – used to identify a specific SCCP number used for a particular call key, so that a single call can be traced.

❐ trace_call – used to trace calls by either a specific SCCP number or the whole BSC (based on call rate and trace level).

68P81132E13-O

10/3/02-GR

7-2

BSC MMI Commands CHAPTER 7 - CALL TRACE

find_sccp

find_sccp

Description

Extracts the SCCP number for a specific call. An SCCP number changes whenever an inter-BSC handover occurs. This number is needed when using the command to trace single calls.

Because the SCCP number is random, unique keys are used to define the search criteria and extract the number. The search criteria is entered as parameters to the find_sccp command and are defined below.

Format

find_sccp <key>=<key value>

Parameters

Key called_party Number of destination party

cic Circuit Identity Code

imsi International Mobile Subscriber Identity

rci Radio Channel Identity or Subrate Channel Identity entered in the RCI format.

subrate Subrate Channel Information

tmsi Temporary Mobile Subscriber Identity

Key value 1 - 20 digits Called_party ID represented in BCD.

1 - 15 digits IMSI ID represented in BCD.

1h - ffffh CIC ID represented in hexadecimal.


✔ ✔


Classification RC


68P81132E13-O

10/3/02-GR

7-3


find_sccp

0h - 7fffffffh RCI ID represented in hexadecimal or SCI entered in the RCI format. The disp_rci command can be used to view the RCI format.Subrate Info — The Subrate information should be entered separated by spaces (e.g., <ebts_id> <span> <ts> <grp>). Ranges are: ebts_id = 1-80, span = 0-1, ts = 0-23 for T1 and 0-32 for E1, grp = 0-3. The disp_subrate command can be used to view the Subrate format.

8 digits TMSI ID represented in hexadecimal.

Example 1:

This example returns the SCCP of 2b2345h for the specified Radio Channel Identity (RCI).

find_sccp rci=01000301h

SCCP_NUM = 2b2345h


Example 2:

This example returns the SCCP of 2b2345h for the specified number of the destination party (called party).

find_sccp called_party=17085763000

SCCP_NUM = 2b2345h


Parameter: Value:

<key> rci

<key value> 01000301h

Parameter: Value:

<key> called_party

<key value> 17085763000

68P81132E13-O

10/3/02-GR

7-4


find_sccp

Example 3:

This example returns the SCCP of 2b2345h for the specified Circuit Identity Code.

find_sccp cic=100

SCCP_NUM = 2b2345h


Example 4:

This example returns the SCCP of 2b2345h for the specified Temporary Mobile Subscriber Identity.

find_sccp tmsi=12345678h

SCCP_NUM = 2b2345h


Example 5:

This example returns the SCCP of 2b2345h for the specified International Mobile Subscriber Identity.

find_sccp imsi=3160123456

SCCP_NUM = 2b2345h

Parameter: Value:

<key> cic

<key value> 100

Parameter: Value:

<key> tmsi

<key value> 12345678h

68P81132E13-O

10/3/02-GR

7-5


find_sccp


Example 6:

This example shows the SCCP number is not found (call is not active for a specified circuit identity code) and will display the number of calls that handled 6:1, 3:1, and DCCH types of calls.

find_sccp cic=ffff

SCCP Number not found

6 :1 ca l l s 12

3:1 ca l l s 6

DCCH calls 0


Example 7:

This example returns the SCCP of 2b2345h for the specified Subrate.

find_sccp subrate = 50 0 0 0

SCCP_NUM = 2b2345h

Parameter: Value:

<key> imsi

<key value> 3160123456

Parameter: Value:

<key> cic

<key value> ffff

68P81132E13-O

10/3/02-GR

7-6


find_sccp


Parameter: Value:

<key> subrate

<ebts_id> 50

<span_id> 0

<timeslot> 0

<grp> 0

68P81132E13-O

10/3/02-GR

7-7


trace_call

trace_call

Description

This command is used for debugging and tracing specific calls. A call trace can be performed on a single call, using its specific SCCP number, or on the entire BSC, based upon the call rate and trace level specified.

Format

trace_call <mode> <value> <trace_level>[filter[cell 1][cell 2][cell 3]]

Parameters

Mode

The mode parameter defines the mode of the trace being performed.

mode nth_call Used for tracing a call by call rate.

this_call Used for tracing a specific call by SCCP number.

next_call Traces the next call that matches the input key.

trace_history Displays the current active trace command.

stop Stops current call trace.


✔ ✔


Classification RC

Related commands find_sccp on page 7-3

chg_element on page 2-31

68P81132E13-O

10/3/02-GR

7-8


trace_call

Value

The value parameter supports the mode parameter. The data entered in the value parameter depends on which mode was entered. The value parameter may contain one of three variables: <call_rate>, <sccp_num>, or <key>=<key_value>.

call_rate 0-255 Used only for nth_call mode

sccp_num 1-07fffffh Used only for this_call mode

<key>=<key_value> Used only for next_call mode

key called_party Number of destination party

cic Circuit Identity Code

rci Radio Channel Identity or Subrate Channel Identity entered in RCI format.

subrate Subrate Information

imsi International Mobile Subscriber Identity

tmsi Temporary Mobile Subscriber Identity

key_value 1-20 digits Called_party ID represented in BCD

1h-ffffh CIC ID represented in hexadecimal or decimal

0h - 7fffffffh RCI ID represented in hexadecimal or SCI entered in the RCI format. The disp_rci command can be used to view the RCI format.Subrate Info — The Subrate information should be entered separated by spaces (e.g., <ebts_id> <span> <ts> <grp>). Ranges are: ebts_id = 1-80, span = 0-1, ts = 0-23 for T1 and 0-32 for E1, grp = 0-3. The disp_subrate command can be used to view the Subrate format.

1-15 digits IMSI ID represented in BCD

8 digits TMSI ID represented in hexadecimal

NOTE

Use the find_sccp command to determine the SCCP Num number for a specific call.

68P81132E13-O

10/3/02-GR

7-9


trace_call

Examples:

trace_call nth_call 1<trace_level>

trace_call this_call 2b3456h <trace_level>

trace_call next_call called_party=<called_party#> <trace_level>

trace_call stop (requires no additional parameters)

trace_call trace_history (requires no additional parameters)

Trace level

The call trace feature permits the user to specify what events, or combination of events, to monitor. Higher levels may be used to monitor general actions. Lower levels may be used to monitor specific discrete actions, such as handover failures or terminated calls.

NOTE

The call trace command continues to execute until it is disabled. The trace_call stop command can be used to disable call trace.

The levels associated with the call trace feature are identified in Table 7-1.

Table 7-1 Trace levels

EventTracelevel

Description

Handover success 1 Generate a report for a successful handover event.

Handover failure 2 Generate a report for a failed handover event.

Call terminated 4 Generate a report for a terminated call event.

68P81132E13-O

10/3/02-GR

7-10


trace_call

Multiple trace levels may be used by simply adding the trace level values. If all trace levels are to be used, enter a trace level of 255.

For example, if the handover events are of particular interest, select a trace level of 67 to generate a handover success report, failure report, and debug report.

trace_call nth_call 1 67

Filter

This is an optional parameter used to trace the progress of a specified call(s) in a specified cell(s). Filtering can be done on up to three cells in one trace_call command.

Example

trace_call nth_call 1 <trace_level> filter 1 2 3

Switch Manager (SM) success event

8 Generate a report for a successful SM event.

TCH audit 16 Used at a non-remote transcoder site to generate a report for a TCH audit event.

Timer 32 Generate a report for a timer event.

Handover debug 64 Generate a report for the handover debug event.

SM failure event 128 Generate a report for a failed SM event.

Table 7-1 Trace levels

EventTracelevel

Description

68P81132E13-O

10/3/02-GR

7-11


trace_call

Defined timers

Motorola defined timers

ModuleMSGtype

Timer Timer description

SSM 06 MTG Wait for clear command from MSC.

SSM 07 MTH Wait for radio channel released from RRSM.

SSM 08 MTI Wait for cipher mode complete form RRSM.

SSM 09 MTJ Wait for handover complete from target cell RRSM.

SSM 0A MTK Wait for handover allocation from destination cell RRSM.

SSM 3D MTK_INTRA Wait for internal handover initiated from destination cell RRSM.

SSM 0B MTL Wait for SCCP connection released from MSC.

SSM 0C MTM Wait for response from switch manager.

SSM 0D MTN Wait for assignment complete from RRSM.

SSM 14 MTU Second timer to wait for response from switch manager.

SSM 15 MTV Audit timer for state on dedicated channel.

SSM 17 MTX Wait for response from switch manager.

SSM 30 MTB1 Wait for handover request.

SSM 31 MTC1 Wait for handover allocation.

SSM 1A SSM_AUDIT Wait for audit SSM call response from RRSM.

68P81132E13-O

10/3/02-GR

7-12


trace_call

GSM defined timers

CCITT defined timers

ModuleMSGtype


SSM 1F T3103 Wait for handover complete on destination cell.

SSM 2D T7 Time between handover required messages.

SSM 36 Tqho Wait for resource available pertaining to a handoff request.

ModuleMSGtype


SSM 2E TIAR Inactivity receive timer.

SSM 2F TIAS Inactivity send timer.

SSM 05 TCONN_EST Wait for SCCP connection confirm from MSC.

SSM 32 TREL Wait for SCCP release complete.

68P81132E13-O

10/3/02-GR

7-13


trace_call

Successful Call Establishment

Mobile-to-MobileCall Indication

FilterCell Number 1

Example 1:

This example shows a report for a normal call scenario.

Use the filter option parameter to display only a particular cell number.

The results are presented as a report displayed at the BSP MMI console, which are also available through remote login.

trace_call next_call called_party=14167174755 255 filter 1

CALL TRACE COMMAND ACCEPTED, Data Forthcoming for trace number 104

* * * * TRACE REPORT FOR NUMBER 104 * * * *

t race source MMIca l l t ype t race next ca l lsccp number 1 9 2 f 6 0dl r 2 b 4 2 f ec ic 0 0 0 0new c ic 1 7 7 4XCDR Id 9VP number 0radio channel Id 0 0 0 0 0 0e b t s / s p a n / t s / g r p 0 0 0 0 0 0 0 0new radio channel id 0 1 3 7 0 1n e w e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current local ce l l Id 2 5t ime s tamp May Wed 15 11 :51 :40 :925 1996even t SM Eventt y p e Success

***END OF TRACE REPORT FOR NUMBER 104***


t race source MMIca l l t ype t race next ca l lsccp number 1 9 2 f 6 0dl r 2 b 4 2 f ec ic 1 7 7 4XCDR Id 9VP number 0radio channel Id 0 1 3 7 0 1e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current local ce l l Id 2 5t ime s tamp May Wed 15 11 :51 :52 :930 1996even t TCH Audits ta tus Bypass***END OF TRACE REPORT FOR NUMBER 104***

68P81132E13-O

10/3/02-GR

7-14


trace_call

Successful CallDisconnect

Normal Call Terminationby MSC


t race source MMIca l l t ype t race next ca l lsccp number 1 9 2 f 6 0dl r 2 b 4 2 f ec ic 1 7 7 4XCDR Id 9VP number 0radio channel id 0 1 3 7 0 1e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current loca l ce l l id 2 5t ime s tamp May Wed 15 11 :51 :57 :425 1996even t Cal l Terminatedsource MSCreason Normal



t race source MMIca l l t ype t race next ca l lsccp number 1 9 2 f 6 0dl r 2 b 4 2 f ec ic 1 7 7 4new c ic 0 0 0 0XCDR Id 9VP number 0radio channel id 0 1 3 7 0 1e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0new radio channel id 0 0 0 0 0 0n e w e b t s / s p a n / t s / g r p 0 0 0 0 0 0 0 0current loca l ce l l id 2 5t ime s tamp May Wed 15 11 :51 :57 :755 1996even t SM Eventt y p e Success


68P81132E13-O

10/3/02-GR

7-15


trace_call

Successful CallEstablished

Land-to-Mobile(or Mobile-to-Land)

Call Indication

Example 2:

This example shows a report for a normal call scenario with intra-cell handover.


trace_call next_call called_party=18475769383 255



t race source MMIca l l t ype t race next ca l lsccp number 1 5 7 9 8 0dl r c8 a5 fec ic 0 0 0 0new c ic 0 0 0 7XCDR Id 4VP number 1 8radio channel Id 0 0 0 0 0 0e b t s / s p a n / t s / g r p 0 0 0 0 0 0 0 0new radio channel id 0 4 1 0 0 6n e w e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current local ce l l Id 2 1t ime s tamp Jun Mon 3 20 :18 :00 :335 1996even t SM Eventt y p e Success



t race source MMIca l l t ype t race next ca l lsccp number 1 5 7 9 8 0dl r c8 a5 fec ic 0 0 0 7XCDR Id 4VP number 1 8radio channel id 0 4 1 0 0 6e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current loca l ce l l id 2 1t ime s tamp Jun Mon 3 20 :18 :31 :335 1996even t TCH Audits ta tus PCM


68P81132E13-O

10/3/02-GR

7-16


trace_call

Intra-Cell Handover


Indication


t race source MMIca l l t ype t race next ca l lsccp number 1 5 7 9 8 0dl r c8 a5 fec ic 0 0 0 7XCDR Id 4VP number 1 8radio channel id 0 4 1 0 0 6e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current loca l ce l l id 2 1t ime s tamp Jun Mon 3 20 :18 :31 :335 1996even t Handovert y p e Int ranew radio channel id 0 4 1 0 0 3n e w e b t s / s p a n / t s / g r p 5 0 0 0 0 3 0 0source cel l id 1ta rge t ce l l i d 1***END OF TRACE REPORT FOR NUMBER 102***


t race source MMIca l l t ype t race next ca l lsccp number 1 5 7 9 8 0dl r c8 a5 fec ic 0 0 0 7XCDR Id 4VP number 1 8radio channel Id 0 4 1 0 0 3e b t s / s p a n / t s / g r p 5 0 0 0 0 3 0 0current local ce l l Id 2 1t ime s tamp Jun Mon 3 20 :18 :32 :540 1996even t Cal l Terminatedsource MSCreason Normal


68P81132E13-O

10/3/02-GR

7-17


trace_call

SuccessfulCall Disconnect


t race source MMIca l l t ype t race next ca l lsccp number 1 5 7 9 8 0dl r c8 a5 fec ic 0 0 0 7new c ic 0 0 0 0XCDR Id 4VP number 1 8radio channel id 0 4 1 0 0 3e b t s / s p a n / t s / g r p 5 0 0 0 0 3 0 0new radio channel id 0 0 0 0 0 0n e w e b t s / s p a n / t s / g r p 0 0 0 0 0 0 0 0current loca l ce l l id 2 1t ime s tamp Jun Mon 3 20 :18 :32 :540 1996even t SM Eventt y p e Success


68P81132E13-O

10/3/02-GR

7-18


trace_call


Example 3:

This example shows a report for an unsuccessful call scenario.


trace_call next_call called_party=14167174755 255



t race source MMIca l l t ype t race next ca l lsccp number 0 b 1 8 8 0dl r eb 41 f ec ic 0 0 0 0XCDR Id 0VP number 0radio channel Id 0 3 c 5 0 6e b t s / s p a n / t s / g r p 5 0 0 0 0 0 0 0current local ce l l Id 1 1t ime s tamp May Wed 15 10 :57 :17 :175 1996even t Cal l Terminatedsource MSCreason Normal


68P81132E13-O

10/3/02-GR

7-19


trace_call

68P81132E13-O

10/3/02-GR

7-20

8

8 Miscellaneous

Introduction

This chapter contains commands that provide the user with utility functions while using the MMI commands. These commands do not affect system configuration.


10/3/02-GR

8-1

CHAPTER 8 - MISCELLANEOUS BSC MMI Commands

alias

alias

Description

Creates an alias for an MMI command or lists currently defined aliases.

Format

alias [<alias_name> '<alias_text>']

Parameters

NOTE

A list of active aliases is displayed when no parameters are entered.

alias_name The name of the alias to be defined.

alias_text Any valid MMI command. This may include only the command name or the command name with parameters. The alias text must be enclosed in single quotes.


✔ ✔ ✔ ✔



Related commands unalias on page 8-11

68P81132E13-O

10/3/02-GR

8-2

BSC MMI Commands CHAPTER 8 - MISCELLANEOUS

alias

Example 1:

This example creates an alias called “list” that executes the disp_bsc_stat command:

alias list ‘disp_bsc_stat’

List a l l act ive a l iases:

Example 2:

This example lists all currently defined aliases:

alias

Current Al iases:

l i s t d i sp_bsc_s ta t

68P81132E13-O

10/3/02-GR

8-3


comment

comment

Description

Used to create comment fields. This is not an executable command.

Format

comment [<text>]

Parameters

text Specify any alphanumeric character.

Example

Cust BSS MMI-0115 -> comment # th is is a comment #

Cust BSS MMI-0115 ->comment * beg in to tes t on bsc56 *

Cust BSS MMI-0115 -> comment the end o f the tes t


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

8-4


end_delta

end_delta

Description

This command determines the end of a section in the configuration script.

Format

end_delta

Parameters

none

Example

This example ends the delta section in the configuration script.

end_delta


✔ ✔ ✔ ✔



Related commands start_delta on page 8-9

68P81132E13-O

10/3/02-GR

8-5


help

help

Description

Displays help information about the specified “command” or displays all the commands that include the specified “wildcard.”

Format

help [command] | [wildcard]

Parameters

NOTE

All available commands are displayed when no parameter is specified. If the wildcard is “vp,” it will display all the commands that include “vp” or “xcdr,” (and vice versa).

command The exact name of the MMI command in question. The command name must be entered exactly as indicated in the format string.

wildcard String included in a MMI command; only one wildcard is allowed.


✔ ✔ ✔ ✔



Related commands (refer to index)

68P81132E13-O

10/3/02-GR

8-6


help

Example 1

This example displays help information about the chg_level command:

help chg_level

Command : chg_levelFunct ion : Changes the user ’s current secur i ty leve l . Th is command is complete ly in teract ive.Classi f icat ion : Sysgen/RC

In terac t ion : “Enter password for secur i ty leve l you wish to access: ” User enters password. Echo is turned of f . System Response: “Cur ren t secur i ty leve l i s x ” where x i s e i ther 1 , 2 , o r 3

Example 2

This example displays help information about “vp” wildcard:

help vp

Fol lowing commands are re la ted wi th wi ldcard “vp”

au to_vp_ f lag

d isp_au t_vp_ f lag

d isp_vpr

d isp_xcdr_bypass

d isp_xcdr_ types

disp_xcdr_use

set_xcdr_bypass

t e s t _ v p

vp_sched_aud_of f

68P81132E13-O

10/3/02-GR

8-7


history

history

Description

Displays a numbered list of previously entered commands. Any previously entered command can be executed again by using the exclamation mark (!). Enter man ! for additional information.

Format

history [<num_cmds>]

Parameters

num_cmds Specifies the number of recent commands to display. The default is 23 (if no parameter is entered, the last 23 commands are displayed).

Example

This example displays the last five commands executed:

history 5

11 d isp_ leve l

12 chg_ leve l

13 d i sp_d te

1 4 c h g _ d t e _ o m c r 7 7 7 6 5 4 3 2 1

15 h i s t o r y 5


✔ ✔ ✔ ✔




68P81132E13-O

10/3/02-GR

8-8


start_delta

start_delta

Description

This command determines the beginning of a section and its type in the configuration script.

Format

start_delta <delta_section_type>

Parameters

delta_section_type delta_only Determines the beginning of delta_only section.

delta_init Determines the beginning of delta_init section.

NOTE

The configuration script consists of MMI commands which can be located either inside or outside of delta sections. If a command is located outside of any delta sections, then it belongs to a SYSGEN section. The start_delta command can be executed from SYSGEN sections only.

Example

This example begins the delta_only section in the configuration script.

start_delta delta_only


✔ ✔ ✔ ✔



Related commands end_delta on page 8-5

68P81132E13-O

10/3/02-GR

8-9


time_stamp

time_stamp

Description

This command enables or disables the time-stamping function, which adds a time and a date to the MMI command prompt. The time and date are displayed directly before the customer prompt.

Format

time_stamp <action>

Parameters

action on Turn on time-stamping.

off Turn off time-stamping.

Example

This example turns on the time-stamp feature at the system prompt.

time_stamp on

[ 0 6 / 0 1 / 9 2 0 1 : 0 3 : 3 0 ] C u s t B S S M M I - 0 1 1 5 - >

NOTE

Once the time synchronization is enabled, the BSC will synchronize its internal clock using SNTP (Simple Network Time Protocol). Refer to disp_time on page 4-87.


✔ ✔ ✔ ✔


Classification RC

Related commands chg_time on page 2-54

disp_time on page 4-87

68P81132E13-O

10/3/02-GR

8-10


unalias

unalias

Description

Removes the alias for an MMI command that was created with the alias command.

Format

unalias <alias_name>

Parameters

alias_name The alias name to be removed.

Example

This example removes the alias named “list”:

unalias list


✔ ✔ ✔ ✔



Related commands alias on page 8-2

68P81132E13-O

10/3/02-GR

8-11


unalias

68P81132E13-O

10/3/02-GR

8-12

A

A Non-statisticalparameters

Introduction

This appendix provides a tabular listing of functional definitions for all non-statistical parameters used to configure the BSC system.

EXAMPLE: bsc_type is the database subsystem name for “Base Site Controller (BSC) type.”

Element definitions

Element definitions appear on page -2.

Element usage

Element usage appears on page -23.


10/3/02-GR

A-1

APPENDIX A - NON-STATISTICAL PARAMETERS BSC MMI Commands

Element definitions

Table A-1 contains the following information:

Special usage notes

Chg_element command

If an invalid value is entered when using the chg_element command, the original value for the parameter remains unchanged.

NOTE

Defaults for the chg_element application are not automatically set in the system. See Chapter 2 chg_element section for default values.

Element This column is the element name. It must be typed exactly as it appears.

DescriptionThis column provides a brief description of the element along with other important information.

Valid values This column shows supported software ranges and the definitions for these commands.

68P81132E13-O

10/3/02-GR

A-2

BSC MMI Commands APPENDIX A - NON-STATISTICAL PARAMETERS

Table A-1 Element descriptions

Element DescriptionValid values

Range Rcmn’d

abatement_value,1 This element specifies the abatement threshold CPU utilization for the first congestion level. This abatement value should be strictly less than the value of onset_value,1.

0 to 100 60

abatement_value,2 This element specifies the abatement threshold CPU utilization for the second congestion level. This abatement value should be strictly less than the value of onset_value,2.

0 to 100 60

abatement_value,3 This element specifies the abatement threshold CPU utilization for the third congestion level. This abatement value should be strictly less than the value of onset_value,3.

0 to 100 60

ber_loss_daily Indicates the Bit Error Rate (BER) daily alarm level when the value is reached.

0 to 65535 4

ber_loss_hourly Indicates the Bit Error Rate (BER) hourly alarm level when the value is reached.

1 to 65535 6

bs_ag_blks_res Indicates the number of paging subchannels.

0 to 15 3

bsc_type Sets the Base Station Controller (BSC) configuration type.

22=BSP, LCF, OMF

2

bss_id Identifies a BSC. This parameter is used by the Operations and Maintenance Center (OMC) to identify a BSC during statistics collection.

0 to 255 0

68P81132E13-O

10/3/02-GR

A-3


called_pci Indicates whether point code was included in called party (call receiver) address in the SCCP messages. For more information, see CCITT Q.713.

† Align with MSC.

0 or 1

0=enables point codeincluded

1=disables point code

†

calling_pci Indicates whether point code is included in calling party (call originator) address in the SCCP messages.

† Align with MSC.

0 or 1

0=enables point codeincluded

1=disables point code included

†

clm_timer_value,0 Wait for Reset Acknowledge from BSS sub-systems (Both Global and Circuit resets)

0 to

1,000,000 msec

30,000

(30 sec)

clm_timer_value,1 Periodicity with which Overload messages are sent out (when BSS overloaded)

0 to

1,000,000 msec

30,000

(30 sec)

clm_timer_value,2 Wait for Unblocking Acknowledge Timer

0 to

1,000,000 msec

120,000

(120 sec)

clm_timer_value,3 Time to receipt of Blocking Acknowledge

0 to

1,000,000 msec

30,000

(30 sec)

clm_timer_value,4 Time to return Reset Acknowledgement to MSC

0 to

1,000,000 msec

40,000

(40 sec)

clm_timer_value,5 Time the BSS waits for Reset Ack from MSC before repeating the Reset message

0 to

1,000,000 msec

50,000

(50 sec)

Table A-1 Element descriptions (continued)


Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-4


clm_timer_value,6 Overload Timer 0 to

1,000,000 msec

2,000

(2 sec)

clm_timer_value,7 Overload Timer 0 to

1,000,000 msec

70,000

(70 sec)

clm_timer_value,8 Time to receipt of Reset Circuit Acknowledge

0 to

1,000,000 msec

80,000

(80 sec)

clm_timer_value,9 Wait for Circuit Reset Acknowledge

0 to

1,000,000 msec

10,000

(10 sec)

clm_timer_value,10 Periodicity with which Overload relieved messages must be sent when BSS is overloaded

0 to

1,000,000 msec

10,000

(10 sec)

clm_timer_value,11 Wait for SPI or SSP before initiating internal Reset

0 to

1,000,000 msec

20,000

(20 sec)

cp_option_call_trace Sets the flag to enable or disable call trace.

0 or 1

0=Call Trace disabled

1=Call Trace enabled

0

cp_option_interconnect

Sets the flag to disable or enable interconnect call processing.

NOTE: If the flag is off (0), no interconnect calls will be processed by the BSC.

0 or 1

0=Interconnect call processing disabled

1=Interconnect call processing enabled

1



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-5


cp_option_reset_ckt Sets the flag to enable or disable reset circuit feature.

0 or 1

0=Reset circuit disabled

1=Reset circuit enabled

0

cr_lockout_tmr Timer for locking out neighbor cells from future CR handover requests (millisecs).

0 to 30,000 10,000

dpc Sets the Destination Point Code (dpc). The values for the dpc are stored as a 14-bit binary code. (The field is the same for the Originating Point Code opc.)

NOTE: When entering a value in hexadecimal, letters may be entered in upper or lower case. All numbers (hexadecimal and binary) must begin with a numeric character. So hexadecimals beginning with A-F must be preceded by a “0.” Or, if a number is binary, it must be followed by a “b” or a “B.”

0 to 16383

0 to 3FFFh

(0 . . . 0 (16 bits) to1 . . . 1 (16 bits))

(See Note)

0

ebts_dte_addr Identifies the DTE address associated with the specified EBTS.

length (14 bytes)

-

fm_site_type Defines the site type (which specific entity of the Base System Station (BSS)).

1, 3, 4, 5

1=BSC3=RXCDR4=E-BSC5=E-RXCDR

-

gclk_qwarm_flag Enable/disable a GCLK fast warm-up

0 or 1 0



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-6


gproc_slots Defines the number of timeslots to be allocated to all GPROCs for the TDM highway.

It is possible to configure different functions on each of the 16 channels. The system supports 16 or 32 timeslots for the assignment to the TDM highway.

NOTE: This value must be set before any GPROCs are equipped, and this value should not be changed after GPROCs are equipped.

16 or 32

16=TDM timeslots

32=TDM timeslots

16

esmr_cell_id Identifies a cell in the ESMR system; id is constructed by adding a Cell Identity (CI) onto the Location Area Identification.

length (7 bytes)

esmr_cell_id_format Defines the format of the ESMR cell ID sent by the Call Processor (CP) to the switch.

0 to 2

0=whole Cell Global Identification (CGI)

1=Location Area Code (LAC) and Cell Identity (CI)

2=Cell Identity (CI)

1

handover_required_reject_switch

Disables or enables the delivery of a handover reject message from the MSC to the source BSS in the event that a target cannot be found for a requested handover.

0 or 1

0=reject message not required

1=reject message required

1



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-7


high_watermark_3to1 Defines a configurable threshold that represents a point when a resource (3:1 vp) loading condition is set.

The database configurable parameter is in the form of a percent.

NOTE: The “high_watermark_3to1” is always greater than “low_watermark_3to1”.

0% to 100% 80

high_watermark_6to1 Defines a configurable threshold that represents a point when a resource (6:1 vp) loading condition is set.


NOTE: The “high_watermark_6to1” is always greater than “low_watermark_6to1”.

0% to 100% 16

illegal_circuit_id Defines the terrestrial circuit ID which will never be used as a legal terrestrial circuit ID.

0 to 65535 0

inbound_mux Specifies the source for the KSW expansion highway.

0 or 1

0=Inbound highway “0” selected

1=Time Slot Interchange (TSI) highway selected

0



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-8


inter_cell_handover_allowed

Disables or enables inter-cell handovers. (Multi-cell BSSs are normally expected to support internal inter-cell handover, but it is optional.)

0 or 1

0=intercell hand-over disabled

1=intercell hand-overenabled

1

intra_cell_handover_allowed

Disables or enables intra-cell handovers for two conditions: to begin the handover, or to begin handover when co-channel interference is suspected.

(BSS support is optional. If the BSS does not support internal intra-cell handover, it will be initiated by sending a HANDOVER REQUIRED message.)

See GSM rec 5.08, Appendix A, section 4.1.

0 or 1

0= intra-cell handover not allowed

1= intracell handover allowed

0

ksw_config Defines the mapping of the TDM highway numbers for a specified KSW.

0 to 3 0

local_site_id Sets local BSC site id. 1-255 -

low_watermark_3to1 Defines a configurable threshold that represents a point when a resource (3:1 vp) loading condition is cleared.


NOTE: The “low_watermark_3to1” is always less than “high_watermark_3to1”.

0% to 100% 75



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-9


low_watermark_6to1 Defines a configurable threshold that represents a point when a resource (6:1 vp) loading condition is cleared.


NOTE: The “low_watermark_6to1” is always less than “high_watermark_6to1”.

0% to 100% 75

lta_alarm_range This element is a range, plus or minus, in which a gclk frequency can vary from its LTA before alarm occurs.

0 to 255 7

mcap_recover_period

Specifies the recover period (in minutes) during which the BSC will attempt to recover a disabled MCAP server before resetting the cage.

0 to 1439 minutes

2

mfsu_flag Indicates if Multiple File Statistics Upload is enabled or disabled.

0 (Disabled)or1 (Enabled)

1

mtpl2_timer_value,0 Sets the “alignment ready” timer. Also known as T1_timer_id in the CCITT blue book.

40000 to 50000 msec (1 step= 5msec)

45000

mtpl2_timer_value,1 Sets the “not aligned” timer. Also known as T2_timer_id in the CCITT blue book.


77000

mtpl2_timer_value,2 Sets the “aligned” timer. Also known as T3_timer_id in the CCITT blue book.


1250

mtpl2_timer_value,3 Sets the “emergency proving period” timer; corresponds to Pe=212. Also known as T4_timer_id in the CCITT blue book.

400 to 600msec (1 step= 5msec)

500(.5 sec)



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-10


mtpl2_timer_value,4 Sets the “sending SIB” timer. Also known as T5_timer_id in the CCITT blue book.


100

mtpl2_timer_value,5 Sets the “remote congestion” timer. Also known as T6_timer_id in the CCITT blue book.


4500 (45 sec)

mtpl2_timer_value,6 Sets the “excessive delay of acknowledgement” timer. Also known as T7_timer_id in the CCITT blue book.


1250 (1.25 sec)

mtpl3_timer_value,0 Sets the “delay to avoid mis-sequencing on changeover.” Also known as T1_timer in the CCITT blue book.


850 (.85 sec)

mtpl3_timer_value,1 Sets the “time to wait for changeover acknowledgement” timer. Also known as T2_timer in the CCITT blue book.


1350 (1.35 sec

mtpl3_timer_value,2 Sets the “time controlled diversion-delay to avoid mis-sequencing on changeback” timer. Also known as T3_timer in the CCITT blue book.


850 (.85 sec)

mtpl3_timer_value,3 Sets the “time to wait for uninhibit acknowledgement” timer. Also known as T12_timer in the CCITT blue book.


1150 (1.15 sec

mtpl3_timer_value,4 Sets the “time to wait for force uninhibit” timer. Also known as T13_timer in the CCITT blue book.


1150 (1.15 sec)

mtpl3_timer_value,5 Sets the “time to wait for inhibition acknowledgement” timer. Also known as T14_timer in the CCITT blue book.

2000 to 3000msec(1 step=5msec)

2500 (2.5 sec)



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-11


mtpl3_timer_value,6 Sets the “time to wait to avoid oscillation of initial alignment failure and link restart” timer. Also known as T17_timer in the CCITT blue book.


1150 (1.15 sec)

mtpl3_timer_value,7 Sets the “timer at restarting signalling point, waiting to restart traffic routed through adjacent SP.” Also known as T21_timer in the CCITT blue book.

0 to 30000 (provisional)msec (1 step= 5msec)

30000 (30 sec)

mtpl3_timer_value,8 Sets the “local inhibit test timer.” Also known as T22_timer in the CCITT blue book.

180000 to 360000 (provisional) msec (1 step= 5msec)

270000(270 sec)

mtpl3_timer_value,9 Sets the “remote inhibit test timer.” Also known as T23_timer in the CCITT blue book.

180000 to 360000 (provisional) msec (1 step= 5msec)

270000 (270 sec)

mtpl3_timer_value,10 Sets the “stabilizing timer after removal of local processor outage (used in LPO latching to RPO).” Also known as T24_timer in the CCITT blue book.

0 to 500 (provisional)msec (1 step= 5msec)

500 (.5 sec)

mtpl3_timer_value,11 Sets the “supervision timer for signalling link test acknowledgement.” Also known as SLT_T1_timer in the CCITT blue book.

4000 to 12000 msec(1 step= 5msec)

8000 (8 sec)

mtpl3_timer_value,12 Sets the “interval timer for sending signalling link messages.” Also known as SLT_T2_timer in the CCITT blue book.


60000 (60 sec)

mtpl3_timer_value,13 Sets the “waiting for changeback acknowledgement (first attempt) timer. Also known as T4_timer in the CCITT blue book.


850 (.85 sec)



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-12


mtpl3_timer_value,14 Sets the “waiting for changeback acknowledgement (second attempt) timer. Also known as T5_timer in the CCITT blue book.


850 (.85 sec)

mtpl3_timer_value,17 Minimum time period between Congestion Indications (CIs). CIs arriving within this timer value are ignored. Timer value is in milliseconds.

6,000 to 10,000 msec

6,000 (msec)

mtpl3_timer_value,18 Minimum timer period before abatement can occur. If no CI is received for this timer value, traffic is increased by one step. Timer value is in milliseconds.

13,000 to 60,000 msec

60,000 (msec)

ni Sets the Network Indicator (NI) that establishes a method of differentiation between international and national messages.

0 to 3

0=Internat’l Network

1=Spare (for international use only)

2= National Network

3=Reserv-ed for national use

2

normal_call_thres Defines the high_threshold that classifies a call as a “normal call.” For example, with a threshold set at 20, any call greater than 20 seconds would be classified as a “normal call.”

Note normal_call_thres is always greater than the short_call_thres.

1 to 90 10



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-13


number_of_preferred_cells

Sets the maximum number of target cells to be included in a HANDOVER REQUIRED message.

The preferred list of target cells is a mandatory BSS field. The number of preferred cells is given in order of predicted best performance. See GSM Rec. 8.08, 3.1.5.1.1.

0 to 255preferred cells

6

omc_dte_addr Identifies the DTE address associated with the OMC

length (14 bytes)

0

onset_value,1 This element specifies the onset threshold CPU utilization for the first congestion level.

0 to 100 80

onset_value,2 This element specifies the onset threshold CPU utilization for the second congestion level.

0 to 100 80

onset_value,3 This element specifies the onset threshold CPU utilization for the third congestion level.

0 to 100 80

opc Sets the Originating Point Code (opc). The values for the opc are stored as a 14-bit binary code. See GSM Recommendations, section CCITT Q.708.

0 to 16383originating point code number

0

overload_steps Identifies the number of steps defined for the overload function.

0 to 255 0

pst_timer_value This sets the timer which is used to wait for the RRLP Measure Position Response from the EBTS. This timer value is in milliseconds. This timer is specific to the E911 Feature.

2,000 to 196,000 msec (2 to 196 sec)

65,000 msec (65 sec)

remote_loss_daily Sets the remote alarm, daily alarm level count.

0 to 65535number of alarms

16



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-14


remote_loss_hourly Sets the remote alarm, hourly alarm level count.


20

remote_loss_oos Sets the remote alarm out-of-service (OOS) level count. When the count is exceeded, the 2 Mbps circuit will be taken out-of-service.


511(per day)

remote_loss_restore Sets the remote alarm restorable time limit. If no remote_loss_restore errors occur within this period of time, the 2 Mbps circuit will be allowed to be brought back-in-service.

0 to 65535minutes

10(0 errors per 10 minute interval)

remote_time_oos Sets the remote alarm time. If a remote alarm exists for this amount of time, the 2 Mbps circuit will be taken out-of-service.

0 to 65535100 msec

100

remote_time_restore Sets the remote alarm restorable time. If the remote alarm ceases, for this period of time, the 2 Mbps circuit will be brought back-in-service.

0 to 65535100 msec

100 (0 errors per 10 second interval)

sap_audit_type Defines the audit type(s) associated with a particular device type. Indicates the type of test (e.g., safe test, loopback, etc.)

1 to 20 0

sap_device_type Defines the type of device (board, bus, resource, soft device, optional hardware) that will be audited by the SAP.

0 to 31 0

sap_end_time Defines the end time (in military time) for a scheduled audit.

0000-2359

Upper byte = hours

Lower byte = minutes

0

sap_interval Defines how often (in minutes) audits will be executed.

0000-2359 0



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-15


sap_start_time Defines the start time (in military time) for a scheduled audit.

0000-2359 0

sar_margin The GPPROC CPU utilization drop (below sar_threshold) in order to clear the OMC alarm.

For example, if sar_threshold is 80% and sar_margin is 20%, then an alarm will be sent to the OMC when CPU% exceeds 80%, but will not be cleared until CPU% falls below 60% (i.e., 80-20)

5 to 45 20

sar_threshold The GRPROC CPU utilization which, when exceeded, will cause the BSC to send an alarm to the OMC; see example in sar_margin (previous).

0 to 100 80

short_call_flag Turns on/off short call bookeeping for VP Recovery. Table tracking short call instances for VPs is updated when this flag is turned on.

on or off on

short_call_inst Defines the number of consecutive short call instances a VP encounters to trigger a VP audit.

1 to 10 2

short_call_thres Defines the low_threshold that classifies a call as a “short call.” For example, with a threshold set at 10, any call less than or equal to 1 seconds would be classified as a “short call.”

Note short_call_thres is always less than the normal_call_thres.

1 to 60 7

slip_loss_daily Sets the frame-slip daily alarm level count.


4

slip_loss_hourly Sets the frame-slip hourly alarm level count.


10



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-16


slip_loss_oos Sets the frame-slip out-of-service (OOS) alarm level count. When this count is exceeded, the 2 Mbps circuit will be taken out-of-service.


255 (per day)

slip_loss_restore Sets the frame-slip restorable time limit. If no errors occur during this period, the 2 Mbps circuit will be brought back into service.

0 to 65535number of minutes

10(0 errors per 10 minutes)

sntp_flag Indicates if Time Synchronization is enabled or disabled.

0 (Disabled)or1 (Enabled)

1

sntp_poll_time Indicates the Time Synchronization polling interval of the OMC in seconds.Note During sysgen off, the units are seconds; during sysgen on, the units are centiseconds.

64 to 1024 secs (sysgen off)

6400 to 102400 centiseconds (sysgen on)

180 secs

18000 centiseconds

ssm_overload_threshold

Sets the maximum number of calls handled by a BSC.

70 to 90 0

ssm_timer_value,0 Sets the wait (time) for the SCCP connection Confirm from the MSC. Also known as T (connection established) in CCITT documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,1 Sets the “wait for clear command from the MSC” timer. Also known as ssm_mtg in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,2 Sets the “wait for radio channel released from Radio Resource State Machine (RRSM)” timer. Also known as ssm_mth in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,3 Sets the “wait for cipher mode complete from the RRSM” timer. Also known as ssm_mti in GSM documentation.

0 to 1000000msec

30000 (30 sec)



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-17


ssm_timer_value,4 Sets the “wait for handover complete from target cell Radio Resource State Machine (RRSM)” timer. Also known as ssm_mtj in GSM documentation.

0 to 1000000msec

7000 (7 sec)

ssm_timer_value,5 Sets the “wait for handover allocation from destination cell RRSM” timer. Also known as ssm_mtk in GSM documentation.

0 to 1000000msec

5000 (5 sec)

ssm_timer_value,6 Sets the “wait for SCCP connection released from MSC” timer. Also known as ssm_mtl in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,7 Sets the “wait for response from switch manager” timer. Also known as ssm_mtm in GSM documentation.

0 to 1000000msec

10000 (10 sec)

ssm_timer_value,8 Sets the “wait for assignment complete from RRSM” timer. Also known as ssm_mtn in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,9 Sets the “second timer to wait for response to switch manager” timer. Also known as ssm_mtu in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,10 Sets the “audit timer for state on dedicated-channel” timer. Also known as ssm_mtv in GSM documentation.

0 to 1000000msec

30000 (30 sec)

ssm_timer_value,11 Sets the “wait for audit response from switch manager” timer. Also known as ssm_mtx in GSM documentation.

0 to 1000000msec

30000(30 sec)

ssm_timer_value,12 Sets the “send activity control” timer. Also known as T(ias) in CCITT documentation.

0 to 1000000msec

120,000(120 sec)



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-18


ssm_timer_value,13 Sets the “receive inactivity control” timer.

The length of this timer must be > the “send activity control” timer T(ias). Also known as T(iar) in CCITT documentation.

0 to 1000000msec

125000

ssm_timer_value,14 Sets the “handover required periodicity” (regular recurrence of handover queuing) timer.

This is the minimum time interval between the BSS queuing of handover required messages for the same connection. Also known as T7 in GSM documentation. See GSM Rec. 8.08, 3.1.5 to 3.2.3.

0 to 1000000msec

15000

ssm_timer_value,15 Sets the “wait for audit SSM call response from RRSM” timer. Also known as ssm_audit_timer in GSM documentation.

0 to 1000000msec

30000

ssm_timer_value,16 Time allowed between the DSP training and the first DSP audit.

0 to 1000000msec

350

ssm_timer_value,17 Sets the “wait for handover request” timer. Also known as ssm_mtb1 in GSM documentation.

0 to 1000000msec

30000

ssm_timer_value,18 Sets the “wait for handover allocation” timer. Also known as ssm_mtc1 in GSM documentation.

0 to 1000000msec

30000

ssm_timer_value,19 Sets the (wait) time for SCCP Release complete. Also known as T(rel) in CCITT documentation.

0 to 1000000msec

4000



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-19


ssmpc_timer_value,0 Sets the time that the BSS waits for a handover to complete for an internal handover.

The purpose is to keep the old channels long enough for the MS to retain the ability to return to the old channels when necessary, and to release the channels if the call is dropped.

0 to 1000000 msec

10,000

static_vps_first Specifies if 3:1 or 6:1 XCDRs are used before the dual mode XCDR VPs are used. Value 1 = 3:1 or 6:1 XCDR will be used first; Value 0 = dual mode XCDR VPs will be used first.

0 or 1 1

stat_interval Sets the time period (interval) that will be used by GSM statistics to collect statistical data.

5 to 60minutes

30

s_red_loss_daily Sets the synchronization loss, daily alarm level count.


16 (per day)

s_red_loss_hourly Sets the synchronization loss, hourly alarm level count.


20

s_red_loss_oos Sets the synchronization loss, out-of-service (OOS) daily alarm level count.


511

s_red_loss_restore Sets the synchronization loss, restorable time limit.

If the sync_loss error does not occur within this time period, the 2 Mbps circuit will be brought back into service.

0 to 65535 minutes

10



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-20


subrate_trunking_flag

Indicates the subrate trunking flag of the controlling EBTS. If it is on, it uses trunked subrates (SCI); if it is off, it uses non-trunked mapping (RCI). Each cell in an EBTS should be configured to the same channel mapping mode.

on or off off

sync_time_oos Sets the sychroniztion loss time.

If the synchronization is lost for this time period, the 2 Mbps circuit will be taken out-of-service.

0 to 65535 100

sync_time_restore Sets the sychronization loss restorable time limit. If the synchronization returns for this time period, the 2 Mbps circuit will be brought back into service.

0 to 65535 100

tdm_call_block Disables or enables the call blocking option of the TDM connectivity test.

When this value is “on”, calls will not be set up on TDM paths that have failed the TDM connectivity test.

Note: After changing the tdm_call_block element, a TDM connectivity test must be run before the change becomes effective.

on or off off

thres_vp_alarms Indicates if alarm messages should be sent to the OMC when the high or low watermark has reached for 3to1 or 6to1.

on or off on



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-21


transcoder_location Sets the placement of the transcoder.

(BSC or RXCDR).

0 to 1

0=RXCDR or CP_BSC or E_BSC or E_RXCDR

1 = Colocated_BSC

0

transcoder_mode Defines the type of communication between a CCDSP and the transcoder.

1 =16 Kbps, normal transmission

1

tty_baudot_flag Enables/disables TTY-Baudot 0 = Off

1 = On

Off

tty_baudot_rate Sets the symbols per second rate for TTY Baudot.

0 to 1

0 = 45.45 symbols/sec

1 = 50.00 symbols/sec

0

vp_config_threshold This element is a limit to determine if available VPs from other XCDRs can be borrowed.

0 to 10 2

vpr_vtt_flag Enables/disables VP Recovery during XCDR initialization and scheduled or on-demand VTT. If the flag is on, a VP Recovery is attempted upon a VP failing the initial audit.

on or off on

xcdr_bypass_allowed Sets the XCDR bypass flag values for all configured.

0 to 3

0 = OFF

1 = Bypass flag ON

2 = Audit flag ON

3 = Bypass and Audit flags ON

1



Range Rcmn’d

68P81132E13-O

10/3/02-GR

A-22


Element usage

Commands using a specific parameter are presented in the Element column.

Element

add

_cel

l

chg

_cel

l_id

chg

_ele

men

t

dis

p_e

lem

ent

abatement_value,<1-3> ✔ ✔

ais_loss_oos ✔ ✔

all_cells_ins ✔ ✔

audio_switch_delay ✔ ✔

ber_loss_daily ✔ ✔

ber_loss_hourly ✔ ✔

ber_loss_restore ✔ ✔

block_retries_num ✔ ✔

block_xbl_oos_flag ✔ ✔

bs_ag_blks_res ✔ ✔ ✔

bsc_type ✔ ✔

bss_id ✔ ✔

bus_device_type ✔ ✔

bus_stat_threshold ✔ ✔

called_pci ✔ ✔

calling_pci ✔ ✔

ccch_conf ✔ ✔ ✔

clm_timer_value,<0-11> ✔ ✔

cp_option_call_trace ✔ ✔

cp_option_interconnect ✔ ✔

cp_option_reset_ckt ✔ ✔

68P81132E13-O

10/3/02-GR

A-23


cr_lockout_tmr ✔ ✔

dpc ✔ ✔

ebts_dte_addr ✔ ✔

esmr_cell_id ✔ ✔ ✔

extrl_handover_allowed ✔ ✔

fm_site_type ✔ ✔

ftp_failure ✔ ✔

gclk_qwarm_flag ✔ ✔

gproc_slots ✔ ✔

gsm_cell_id_format ✔ ✔

handover_required_reject_switch ✔ ✔ ✔

high_watermark_3to1 ✔ ✔

high_watermark_6to1 ✔ ✔

illegal_cell_id ✔ ✔

illegal_circuit_id ✔ ✔

inter_cell_handover_allowed ✔

intra_cell_handover_allowed ✔

ksw_config ✔ ✔

local_site_id ✔ ✔

low_watermark_3to1 ✔ ✔

low_watermark_6to1 ✔ ✔

lta_alarm_range ✔ ✔

mcap_recover_period ✔ ✔

mfsu_flag ✔ ✔

mtpl2_timer_value,<0-6> ✔ ✔

Element

add

_cel

l

chg

_cel

l_id

chg

_ele

men

t

dis

p_e

lem

ent

68P81132E13-O

10/3/02-GR

A-24


mtpl3_timer_value,<0-14,17,18> ✔ ✔

ni ✔ ✔

normal_call_thres ✔ ✔

number_of_preferred_cells ✔ ✔ ✔

omc_dte_addr ✔ ✔

onset_value,<1-3> ✔ ✔

opc ✔ ✔

overload_steps ✔ ✔ ✔

pst_timer_value ✔ ✔

remote_loss_daily ✔ ✔

remote_loss_hourly ✔ ✔

remote_loss_oos ✔ ✔

remote_loss_restore ✔ ✔

remote_time_oos ✔ ✔

remote_time_restore ✔ ✔

sap_audit_type ✔ ✔

sap_device_type ✔ ✔

sap_end_time ✔ ✔

sap_interval ✔ ✔

sap_start_time ✔ ✔

sar_margin

(This element must be modified using the sar command described on page 6-44.)

sar_threshold

(This element must be modified using the sar command described on page page 6-44.)

short_call_flag ✔ ✔

Element

add

_cel

l

chg

_cel

l_id

chg

_ele

men

t

dis

p_e

lem

ent

68P81132E13-O

10/3/02-GR

A-25


short_call_inst ✔ ✔

short_call_thres ✔ ✔

slip_loss_daily ✔ ✔

slip_loss_hourly ✔ ✔

slip_loss_oos ✔ ✔

slip_loss_restore ✔ ✔

sntp_flag ✔ ✔

sntp_poll_time ✔ ✔

s_red_loss_daily ✔ ✔

s_red_loss_hourly ✔ ✔

s_red_loss_oos ✔ ✔

s_red_loss_restore ✔ ✔

ssm_overload_threshold ✔ ✔

ssm_timer_value,<0-19> ✔ ✔

ssmpc_timer_value,0 ✔ ✔ ✔

static_vps_first ✔ ✔

stat_interval ✔ ✔

subrate_trunking_flag ✔ ✔ ✔

sync_loss_daily ✔ ✔

sync_loss_hourly ✔ ✔

sync_loss_oos ✔ ✔

sync_loss_restore ✔ ✔

sync_time_oos ✔ ✔

sync_time_restore ✔ ✔

tdm_call_block ✔ ✔

Element

add

_cel

l

chg

_cel

l_id

chg

_ele

men

t

dis

p_e

lem

ent

68P81132E13-O

10/3/02-GR

A-26


thres_vp_alarms ✔ ✔

transcoder_location ✔ ✔

transcoder_mode ✔ ✔

tty_baudot_flag ✔ ✔

tty_baudot_rate ✔ ✔

transport_mod ✔ ✔

unblock_retries_num ✔ ✔

vp_config_threshold ✔ ✔

vpr_vtt_flag ✔ ✔

xcdr_bypass_allowed ✔ ✔ ✔

Element

add

_cel

l

chg

_cel

l_id

chg

_ele

men

t

dis

p_e

lem

ent

68P81132E13-O

10/3/02-GR

A-27


68P81132E13-O

10/3/02-GR

A-28

B

B Statisticalparameters

Introduction

This appendix may be read by deciding the basis of the statistic: per GPROC, per BSC, per class, per link (X.25 or SS7), or per SIO.

Within each basis, the parameters are shown in alphabetical order. The type of command is listed: Counter, Duration (Total Time), Gauge, Normal Distribution, or Weighted Distribution. Also, note that each parameter is listed in lower case, you may use the same parameters in upper case only with the commands disp_stats and clear_stats.

Alarm severity is noted in boldface type in the parameter descriptions of alarm-related statistics. The classifications of the alarms are as follows: Warning. Minor, and Major. (The alarms are listed from least critical (Warning) to most critical (Major).) The notation will only appear if a statistic has an alarm.


10/3/02-GR

B-1

APPENDIX B - STATISTICAL PARAMETERS BSC MMI Commands

BSC parameters

Statistic name (MMI and OMC)

Basis/type

Keystat

Alarm Description

assgn_fail_sub_chan_config

CELL Counter

N/A N/A This statistic is pegged when the ACG indicates the BSC requested subrate is either out of range or on a reserved timeslot.

assgn_fail_sub_chan_in_use

CELL Counter

N/A N/A This statistic is pegged when the ACG indicates a BSC requested subrate is already in use.

assgn_fail_sub_chan_unavail

CELL Counter

N/A N/A This statistic is pegged when the ACG indicates the BSC requested subrate is on a SPAN that is out of service.

bsc_access_delayMean BSC Access Delay

CELLDistribution(Mean)

Access Delay

N/A This statistic measures the elapsed time (in milliseconds) from the reception of the initial layer 3 service request from the EBTS until the assignment complete message is sent to the MSC (for mobile originated calls). Similarly, it also measures the elapsed time from the sending of the page mobile request to the EBTS until the assignment successful message is received from the EBTS (for mobile terminated calls). The statistic used by the OMC is the mean of these measurements.

68P81132E13-O

10/3/02-GR

B-2

BSC MMI Commands APPENDIX B - STATISTICAL PARAMETERS

bsc_call_hold_time

Mean BSC Call Hold Time

CELLDistribution(Mean)

HoldTime

N/A This statistic measures the elapsed time (in milliseconds) from the reception of the assignment complete message (from the MSC, for mobile originated calls) or the assignment successful message (from the EBTS, for mobile terminated calls) until the clear command is received from the MSC. The statistic used by the OMC is the mean of these measurements.

bsc_switch_failBSC Switch Fail

CELL Counter

N/A N/A This statistic is pegged when the requested connection to the Switch Manager by the CP could not be completed.

bsc_switch_successBSC Switch Success

CELL Counter

N/A N/A This statistic is pegged when the requested connection to the Switch Manager by the CP was completed successfully.

cipher_mode_failCipher Mode Commands from MSC Failed

CELL Counter

N/A Minor This statistic is pegged when an internal Motorola-defined timer in the BSC expires to indicate that the MS did not respond to the Cipher Mode Command message with the Cipher Mode Complete message within the allowable time period or responded improperly. It indicates that the MS probably did not switch into correctly encrypted communication mode when commanded to do so.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-3


clr_cmd_from_msc_ after_acClear Request from MSC after Assignment Complete

CELL Counter

Terminations

N/A This statistic is pegged when, for a given connection, a clear command is received from the MSC after an assignment complete or assignment successful message is received from the MSC or EBTS, respectively.

clr_cmd_from_msc_ before_acClear Request from MSC before Assignment Complete

CELL Counter

Connection Failures

N/A This statistic is pegged when, for a given connection attempt, a clear command is received from the MSC before an assignment complete or assignment successful message is received from the MSC or EBTS, respectively.

clr_req_to_mscClear Request to MSC

CELL Counter

N/A N/A This statistic is pegged when the BSC sends a Clear Request message to the MSC. The Clear Request message may be generated due to one of the following: 1) no radio resources available to allocate from the BSC, call queuing is enabled, and the maximum call delay has been exceeded; 2) radio interface message failure; 3) protocol error; and 4) ciphering algorithm not supported.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-4


clr_req_to_msc_after_acClear Request to MSC after Assignment Complete

CELL Counter

Terminations

N/A This statistic is pegged when, for a given connection, a clear request message is sent to the MSC after an assignment complete or assignment successful message has been received from the MSC or EBTS, respectively. This statistic represents an error condition, in that normally terminated calls, whether or not the termination was initiated by the mobile or the MSC, will result in the BSC first receiving the clear command from the MSC.

clr_req_to_msc_before_acClear Request to MSC before Assignment Complete

CELL Counter

Connection Failures

N/A This statistic is pegged when, for a given connection attempt, a clear request message is sent to the MSC before an assignment complete or assignment successful message is received from the MSC or EBTS, respectively.

conn_refusedConnection Refused from MSC

CELL Counter

N/A N/A This statistic is pegged when the MSC refuses SCCP connection establishment to the BSC. The statistic will only be pegged for connection establishments initiated by the BSC. If an association already exists for the identity of the MS requesting connection, the connection request will be refused, and this statistic will peg.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-5


conn_req_to_mscConnection Request to MSC

CELL Counter

N/A N/A This statistic is pegged when the MSC receives a Connection Request message from the BSC. The statistic will only be pegged for connection establishments initiated by the BSC. This message is sent when the mobile is requesting setup of the connections for several types of transaction, namely: location update, connection establishment (including re-establishment on failure, short message transfer, and supplementary service requests), and paging response.

handover_rec_to_bscHandover Recognized to the BSC

CELL Counter

N/A N/A This statistic is pegged when the Handover Recognized command is received at the BSC from the EBTS. This is the first message sent to the BSC when a handover is initiated.

ho_req_msc_failHandover Failure to the MSC due to all errors except no channels

CELL Counter

Handovers

Warning This statistic is pegged when the BSC sends a Handover Failure message to the MSC.This message is sent to notify the MSC that the BSC could not reserve the radio resource that the MSC had asked for (in the Handover Request message).


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-6


ho_req_msc_okHandover Request from the MSC Completed

CELL Counter

N/A N/A This statistic is pegged when the BSC sends a Handover Request Acknowledge message to the MSC. This message is sent to notify the MSC that the BSC has reserved the radio resource that the MSC had asked for in the Handover Request message.

initl3_loc_updateInitial Layer 3 Location Update

CELL Counter

N/A N/A This statistic is pegged when an Initial Layer 3 (Location Update) message is received by the BSC from a mobile. The mobile will send this message when it powers up or moves to a new location area.

initl3_det_indicationInitial Layer 3 Detach Indication

CELL Counter

N/A N/A This statistic is pegged when an Initial Layer 3 (Detach) message is received by the BSC from a mobile. The mobile will send this message when it powers down or leaves all known location area.

initl3_service_reqInitial Layer 3 Service Request

CELL Counter

Connection Attempts

N/A This statistic is pegged when the Initial Layer 3 (Service Request) is received from the EBTS when establishing a mobile originated connection.

initl3_page_respInitial Layer 3 Page Response

CELL Counter

N/A N/A This statistic is pegged when the Initial Layer 3 (Page Response) is received from the EBTS when establishing a mobile terminated connection.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-7


in_inter_hoIncoming Inter-Cell Handovers Within the BSC

CELL Counter

N/A N/A This statistic is pegged when the MS sends a Handover Complete message to the MSC after an inter-BSC handover is successfully completed from the BSC.

inter_bsc_ho_delayInter-BSC Mean Handover Delay

CELL Distribution

N/A N/A This statistic measures the elapsed time (in msec) from reception of the incoming handover request until the handover complete message is sent to the MSC.

inter_bsc_ms_failInter-BSC Handover, MS Handover Failed Message Received

CELL Counter

N/A Warning This statistic is pegged when the MS sends a Handover Failure message to the BSC for a requested handover that required a new BSC. There is no implication of a lost call, as the call might be recovered to the donor BSC. The statistic is pegged on the source cell.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-8


intra_bsc_hoIntra-BSC Handover Completed

CELL Counter

Handovers,Handover Averages

N/A This statistic is pegged when the BSC sends a Handover Performed message to the MSC relating to a handover that occurs across cells. This statistic pegs for all calls that were transferred to a channel provided by a new cell (new EBTS), but not for those calls that were transferred to a channel provided by a new BSC or provided by the old cell (the same EBTS. This event notifies the MSC that the MS and the BSC successfully established the main signaling link on the new channels and cell.

inter_bsc_req_to_mscInter-BSC Handover Required to MSC

CELL Counter

N/A N/A This statistic is pegged at the sourced BSC when the Handover Required message is sent to the MSC for an inter-BSC handover.

intra_bsc_ho_failIntra-BSC Handover Failed and Recovered to Original Call

CELL Counter

Handovers

Warning This statistic is pegged when the Mobile Subscriber (MS) attempts an intra BSC handover operation, but the ACG times out. This statistic is also pegged if the call-in-progress is not lost and is able to revert back to its previous radio resource (original channel).


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-9


intra_bsc_ho_lostmsIntra-BSC Handover Failed and Mobile Lost

CELL Counter

Handovers

Minor This statistic is pegged for all calls that failed to hand over to a new cell and failed to resume the call on the old channel and cell. The call-in-progress was lost, as the MS was unable to recover to its old cell. If the handover was an internally controlled handover, this statistic pegs if a Clear Request is generated for the channel on which the call was proceeding.

intra_bsc_ho_pri_blk Intra-BSC Handover Primary Target Cell Blocked (no chan avail)

CELL Counter

N/A Warning This statistic is pegged when the first choice cell for an intra-BSC handover has no channels available to allocate to an MS. This statistic is only pegged if an intra-BSC handover is blocked; it will not peg on an intra-cell block. This statistic pegs if all channels are used and one more handover attempt arrives, not as soon as all channels are used (that is, before the rejected attempt).

intra_bsc_ho_reqIntra-BSC Handover Required

CELL Counter

Handovers

N/A This statistic records the number of times the BSC sent an Internal Handover Request to the EBTS because a handover is required for a given Mobile subscriber (MS) to change its dedicated channel configuration within the BSC.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-10


intra_cell_hoIntra-cell Handover Completed

CELL Counter


N/A This statistic is pegged when the BSC sends a Handover Performed message to the MSC. (This relates to a handover occurring across channels, but within a single cell.) This event notifies the MSC that the MS and the BSC successfully established the main signalling link on the new channels. This message is generated at the BSC/MSC interface at the completion of an internal intra-cell handover.

intra_cell_ho_failIntra-cell Handover Failed and Recovered to Original Channel

CELL Counter

Handovers

Warning This statistic is pegged when the Mobile Subscriber (MS) attempts an intra cell handover operation, but the ACG times out. This statistic is also pegged if the call-in-progress is not lost and is able to revert back to its previous radio resource (original channel).

intra_cell_ho_lostmsIntra-cell Handover Failed and Mobile Lost

CELL Counter

Handovers

Minor This statistic is pegged when the MS fails to assign to the new channel and fails to return to the original that the BSC knows was intended for an intra-cell handover. If the call-in-progress was lost or if the MS was unable to recover to its old channel, this statistic is pegged.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-11


intra_cell_ho_reqIntra-cell Handover (Channel Assignment) Required

CELL Counter

Handovers

N/A This statistic is pegged if the BSC decides to perform an internal intra-cell handover. This event occurs because of interference or other disturbances on the radio channel carrying the call, or because the radio channel or the equipment carrying the radio channel must be taken out of service for maintenance or other reasons.

ma_req_from_mscMobile Assignment Request from MSC

CELL Counter

N/A N/A This statistic pegs the radio resource request made to a BSC by the MSC. The MSC sends the BSC an Assignment request message containing details of the type of resource required. The type of resource is based on the MSC’s analysis of the call control information received from the mobile. This statistic measures the number of times the MSC asked the BSC to allocate radio resources.

page_req_from_msc_ fail

Paging Request from MSC protocol error

CELLCounter

N/A Warning This statistic is pegged if the validation of the Page Request message fails (wrong message length, IEI, etc.). The Cell Identifier List is not verified until the page is about to be sent to the cells.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-12


out_inter_hoOutgoing Inter-Cell Handovers Within the BSC

CELL Counter


N/A This statistic is pegged when the MSC sends a Clear Command message to the BSC during a handover procedure with a cause of “handover successful.”

routing_syntax

Routing Failure - Syntax error detected

BSCCounter

N/A Warning This statistic is pegged when a syntax error is detected in the routing message.

routing_unknown

Routing Failure - Reason Unknown

BSCCounter

N/A Warning This statistic is pegged whenever there is a routing failure from the MSC.

sccp_conn_confirmedSCCP Connection Confirmed

CELL Counter

N/A N/A This statistic is pegged when the sccp connection at the BSC is successful.

sccp_conn_refusedSCCP Connection Refused

CELL Counter

N/A N/A This statistic is pegged when the sccp connection at the BSC is refused. Either the sccp connection is already in use or some other error has occurred.

sccp_conn_releasedSCCP Connection Refused

CELL Counter

N/A N/A This statistic is pegged when the sccp connection at the BSC is released. This is a normal condition once the connection is no longer required.

sccp_msgs

Total Messages Handled (from local or remote sub system)

BSCCounter

N/A N/A This statistic is pegged when SCCP messages are transmitted or received on the signalling link.

sif_sio_rx_opc

SIF & SIO octets received

BSCCounter

N/A N/A This statistic is pegged each timer Signal Information Fields (SIF) or Service Information Octets (SIO) are received across all signalling links to a BSC.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-13


sif_sio_tx_dpc

SIF & SIO octets transmitted

BSCCounter

N/A N/A This statistic is pegged each timer SIF or SIO octets are transmitted across all signalling links to a BSC.

sub_chan_blk_1st_try CELL Counter

N/A N/A This statistic is pegged when a subrate could not allocate to the site on the initial call attempt.

sub_chan_blk_inter_bsc_ho

CELL Counter

N/A N/A This statistic is pegged when a subrate could not allocate for an inter-BSC handover attempt.

sub_chan_blk_inter_cell_ho

CELL Counter

N/A N/A This statistic is pegged when a subrate could not allocate for an inter-Cell handover attempt.

sub_chan_blk_intra_cell_ho

CELL Counter

N/A N/A This statistic is pegged when a subrate could not allocate for an intra-Cell handover attempt.

sub_chan_blk_retry CELL Counter

N/A N/A This statistic is pegged when a subrate could not allocate for the second (and final) allocation attempt on an initial call attempt.

vpr_pass_init_vtt BSCCounter

N/A N/A Number of Voice Processors (VP) passing the initial Voice Trunk Testing (VTT) prior to a VP Recovery. Since they pass VTT, the recovery procedure is bypassed.

vpr_success_rec BSCCounter

N/A N/A Number of successful Voice Processor (VP) recoveries. These VPs pass the Voice Trunk Testing (VTT) after the VP is recovered due to a series of short calls experienced by the VP.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-14


vpr_total_attempts BSCCounter

N/A N/A Total number of voice processor (VP) recoveries. These VPs are selected to be audited due to a series of short calls.

total_callsTotal Number of Calls

Cell Counter Connection Attempts,Access DelayHold Time,Handover Averages

N/A This statistic shows the total number of calls originated or terminated for each cell on the BSC. It is pegged when Assignment Complete is sent to the MSC. Note that this statistic does not necessarily peg all successful calls. It only pegs calls that have been assigned to the TCH. For example, if the call fails to send a Direct Transfer Application Part (DTAP) Connect Acknowledge, it still looks successful to the BSC.

unsuccessful_assignmentUnsuccessful Assignment

Cell Counter Connection Failures

N/A This statistic is pegged when, for a given connection attempt, an unsuccessful assignment message is received from the EBTS.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-15


GPROC


Basis/type

Keystat

Alarm Description

cpu_usage

Maximum/Minimum/Mean Utilization

GPROCDistribution

N/A N/A This statistic records the maximum, minimum, and mean values of the short-term processor utilization measurement (from which the 30-minute mean, statistic Mean Utilization, is calculated). This statistic is recorded for each GPROC board under the control of a BSC. It is only recorded for GPROC boards.

cpu_util_log GPROCBucket

N/A N/A This statistic records the CPU utililization every 3 minutes throughout the 30 minute interval. This statistic is recorded for each GPROC board under the control of a BSC. It is only recorded for GPROC boards. Each bin represents a 3 minute interval.

68P81132E13-O

10/3/02-GR

B-16


vpr_vp_type GPROCBucket

N/A N/A Number of VP recoveries per transcoder type: 3:1, 6:1, dual_24, dual_48. Bin values are as follows:

Bin 1) Number of 6:1 VP recoveries

Bin 2) Number of 3:1 VP recoveries

Bin 3) Number of dual_24 VP recoveries

Bin 4) Number of dual_48 VP recoveries

Bin 5) Number of 6:1 IOP recoveries

Bin 6) Number of 3:1 IOP recoveries

Bin 7) Number of dual_24 IOP recoveries

Bin 8) Number of dual_48 IOP recoveries

Bin 9) Reserved

Bin 10) Reserved


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-17


X.25 link


Basis/type

Keystat

Alarm Description

frmrFRMR-Frames

X25_LINK/LAPD_LINKCounter

N/A Warning This statistic is pegged for all Frame Reject (FRMR) frames.

i_frames_rxReceived I-Frames


N/A N/A This statistic is pegged when Information Frames (I-Frames) are received.

i_frames_txTransmitted I-Frames


N/A N/A This statistic is pegged when Information Frames (I-Frames) are transmitted.

invalid_frames_rx Invalid Receive Frames


N/A Warning This statistic is pegged whenever an invalid frame is received.X.25: On the OML (BSC-OMC) link.LAPD: On the RSL (BSC-BTS) link.

n2_expiry Expiration of N2 Retry Count


N/A Minor This statistic is pegged when the retry count threshold has been exceeded.

sabm_tx SABM-Frames


N/A N/A This statistic is pegged for all Set Asynchronous Balanced Mode (SABM) frames on the X.25: BSC-OMC interface.

68P81132E13-O

10/3/02-GR

B-18


Class


Basis/type

Keystat

Alarm Description

sccp_msgs_tx Total Messages Sent (by class 0,2)

CLASSCounter

N/A N/A This statistic is pegged when SCCP messages are transmitted on the signalling link.

sccp_msgs_rx Total Messages Received (by class 0,2)

CLASS Counter

N/A N/A This statistic is pegged when SCCP messages are received on the signalling link.

68P81132E13-O

10/3/02-GR

B-19


SS7 link


Basis/type

Keystat

Alarm Description

mtp_changeoverLocal Automatic Changeover

SS7_LINK Counter

N/A N/A This statistic is pegged when MTP traffic is changed over to an alternate signalling link.

mtp_changebackLocal Automatic Changeback

SS7_LINK Counter

N/A N/A This statistic is pegged when MTP traffic that has been changed over to an alternate signalling link is diverted back to the original signalling link.

mtp_link_insDuration of Link in the In-Service State

SS7_LINKTotal Time

N/A N/A This statistic keeps the duration of the total time the signalling link was in service.

mtp_neg_acks SL Number of Negative ack. Received

SS7_LINK Counter

N/A Warning This statistic counts the number of times the BSC detects out of order messages to the MSC and requests that the retransmission occurs.

mtp_restoration SL Restoration

SS7_LINK Counter

N/A N/A This statistic is pegged when the link starts carrying user traffic. This happens when the link comes into service, is uninhibited, or recovers from a remote processor outage.

mtp_sl_ack SL Failure - Excessive delay of Ack

SS7_LINK Counter

N/A Major This statistic pegs each time the link is lost due to a timer that expires when an acknowledgement of an Message Signal Unit (MSU) is not sent.

68P81132E13-O

10/3/02-GR

B-20


mtp_sl_alignment SL alignment failure

SS7_LINK Counter

N/A Minor This statistic is pegged each time the signalling link tries to align with A-interface while it is out of service.

mtp_sl_congestion SL Failure - Excessive duration of congestion

SS7_LINK Counter

N/A Major This statistic is pegged each time the congestion timer expires.

mtp_sl_error_rate SL Failure - Excessive error rate

SS7_LINK Counter

N/A Major This statistic is pegged each time the signalling link is lost due to the Signal Unit Error Rate Monitor timer expiration. (Refer to CCITT specification Q. 703, Section 102.)

mtp_sl_fail SL Failure - All reasons

SS7_LINK Counter

N/A Major This statistic pegs all Conference of European Postal and Telecommunications Operations (CEPT) signalling link failures.

mtp_sl_fibr SL Failure - Abnormal FIBR/BSNR

SS7_LINK Counter

N/A Major This statistic pegs when the signalling link is lost due to the detection of an abnormal Forward Indicator Bit (FIB) caused by the mis-synchronization of the sequence numbers [Backward Sequence Number (BSN) and Forward Sequence Number (FSN)].

mtp_su_error Number of Signal Units in error

SS7_LINK Counter

N/A Warning This statistic is pegged each time erroneous signal units is received on the signalling link failure due to abnormal Forward Indicator Bit Received (FIBR) / Backward Sequence Number Received (BSNR).


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-21


mtp_linkfail Duration of SL unavailability due to link failure

SS7_LINK Total Time

N/A N/A This statistic is pegged each time the signalling link tries to align with the A-interface while it is out of service.

mtp_local_busy Duration of Local Busy

SS7_LINK Total Time

N/A N/A This statistic is started when a congestion situation is detected on a signaling link. The statistic is stopped when normal operation is resumed.

mtp_local_mgt Duration of SL inhibition due to local management actions

SS7_LINK Total Time

N/A N/A This statistic is started each time the signalling link is inhibited due to local management actions and stopped when the link is uninhibited.

mtp_mgt_inhibit Local Management Inhibit

SS7_LINK Counter

N/A N/A This statistic is pegged each time the signalling link is inhibited by the user who is doing a shutdown command to the associated MTP link.

mtp_mgt_uninhibit Local Management Uninhibit

SS7_LINK Counter

N/A N/A This statistic is pegged each time the signalling link is uninhibited by the user who is doing an unlock command on the link that was previously inhibited.

mtp_remote_mgt Duration of SL inhibition due to remote management actions

SS7_LINK Total Time

N/A N/A This statistic pegs the duration of the signalling link inhibited due to remote management action until uninhibited.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-22


mtp_remote_proc Duration of SL unavailability due to remote processor outage

SS7_LINK Total Time

N/A N/A This statistic is pegged when a remote processor outage is identified and stopped when the processor outage condition ceases. It measures the duration of time that a remote processor is out of service.

mtp_start_rpo Start of remote processor outage

SS7_LINK Counter

N/A Warning This statistic is pegged each time a remote processor outage condition is identified.

mtp_stop_rpo Stop of remote processor outage

SS7_LINK Counter

N/A N/A This statistic is pegged each time the remote processor outage is no longer present.

mtp_unavailable Duration of SL unavailability (for any reason)

SS7_LINK Total Time

N/A N/A This statistic records the duration of the CEPT signalling link unavailability.

congestion_lost_msu Number of SL congestion events resulting in loss of MSUs

SS7_LINK Counter

N/A Warning This statistic is pegged for each congestion event which results in Message Signaling Units (MSUs) being lost.

msu_discarded Number of MSUs discarded due to SL congestion

SS7_LINK Counter

N/A Warning This statistic is pegged each time an MSU is discarded while there is congestion on the signalling link.

mtp_congestion Cumulative duration of SL congestion

SS7_LINK Total Time

N/A N/A This statistic measures the duration (of the total time period) that the signalling link is congested.

mtp_msu_rx Number of MSUs received

SS7_LINK Counter

N/A N/A This statistic is pegged each time Message Signal Units (MSU) are received over the signalling link.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-23


mtp_msu_tx Number of MSUs transmitted

SS7_LINK Counter

N/A N/A This statistic is pegged each time Message Signal Units (MSU) are transmitted over the signalling link.

mtp_re_tx Number of octets retransmitted

SS7_LINK Counter

N/A Warning This statistic counts the number of octets that the BSC has to send again to the MSC because the MSC has requested retransmission.

mtp_sif_sio_rx Number of SIF and SIO octets received

SS7_LINK Counter

N/A N/A This statistic is pegged each timer Signal Information Fields(SIF) or Service information Octets (SIO) are received over the signalling link.

mtp_sif_sio_tx Number of SIF and SIO octets transmitted

SS7_LINK Counter

N/A N/A This statistic is pegged each time Signal Information Fields (SIF) or Service Information Octets (SIO) are transmitted over the signalling link.

page_req_from_mscPaging Request from MSC

BSC Counter ConnectionAttempts

N/A This statistic is pegged when a Paging Request is received from the MSC by the BSC but not following broadcast by the BSC. This message is sent by the network when attempting to locate the MS. Each Page request message from MSC to BSC refers to only one MS.

sl_congestion SL congestion indications

SS7_LINK Counter

N/A Warning This statistic is pegged each time a congestion indication is received.

sl_stop_congestion Stop of SL congestion

SS7_LINK Counter

N/A N/A This statistic is pegged each time the signaling link congestion indication stops.


Basis/type

Keystat

Alarm Description

68P81132E13-O

10/3/02-GR

B-24


SIO


Basis/type

Keystat

Alarm Description

sif_sio_type SIF & SIO octets handled with given SIO

SIOCounter

N/A N/A This statistic is pegged each time Signaling Information Field (SIF) or Signaling Information Octets (SIOs) are transmitted or received on each signalling link. This statistic pegs the sum of all signalling links to the BSC.

68P81132E13-O

10/3/02-GR

B-25



68P81132E13-O

10/3/02-GR

B-26

C

C Device andfunction definitions

Introduction

This appendix describes usage of all devices and functions used with the MMI commands. This appendix is organized as follows:

❐ on page C-2

❐ on page C-3

❐ on page C-7


10/3/02-GR

C-1

APPENDIX C - DEVICE AND FUNCTION DEFINITIONS BSC MMI Commands

Dependencies

Due to system dependencies, some devices and functions at lower levels may be equipped only after other devices at higher levels are equipped.

For example, an MSI-2 must be equipped before an MTL can be equipped. Also, XCDRs must be equipped before GPROCs and MSI-2s are equipped.

Figure C-1 shows device and function dependencies.

GCLK GPROC KSWMSI-2

MTL RSL OML XBLBSP

BSC SITE

CABINET CELL

CAGE

DEVICES

Figure C-1 Device and function dependencies

† Not currently supported.

XCDR

OMFLCF

68P81132E13-O

10/3/02-GR

C-2

BSC MMI Commands APPENDIX C - DEVICE AND FUNCTION DEFINITIONS

Device usage

The following table identifies all valid devices affected by device related commands. The columns represent the following information:

❐ DEVICE – A description of the device.

❐ LITERAL – The acceptable literal used with MMI commands.

❐ ID – Three IDs are used for each device. Some commands may use IDs simply as placeholders.

❐ RANGE – The acceptable value range for the specified ID.

❐ DEFINITION – The definition of each ID.

❐ COMMANDS – The MMI commands used with the indicated device.

Commands

The following commands are device related commands. Page numbers are provided for your convenience. Check the table to see which devices may be used with these commands:

❐ equip_device on page 3-11

❐ lock_device on page 3-21

❐ unlock_device on page 3-30

❐ disp_dev_stat on page 4-18

❐ disp_device on page 4-22

Device LiteralID Range Definition

Commands

equ

ip_d

evic

e

lock

_dev

ice

un

lock

_dev

ice

dis

p_d

ev_s

tat

dis

p_d

evic

e

Base Site Processor

BSP 1 0 Active BSP board:

0 = A side

✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

68P81132E13-O

10/3/02-GR

C-3


Cabinet CAB 1 0 to 2 Cabinet location. ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Cage CAGE 1 0 to 5 Value at which the LANX card dial is set.

✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Clock Bus CBUS 1 0 to 5 Cage. ✔ ✔ ✔ ✔

2 0 to 1 Clock Bus.

3 0 Placeholder.

Generic clock GCLK 1 0 or 1 Active GCLK board:

0 = A side

1 = B side

✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Generic processor

GPROC 1 0 to 31 Specific GPROC board.

✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Kiloport switch

KSW 1 0 to 3 Specific KSW ID ✔ ✔ ✔ ✔ ✔

2 0 or 1 KSW resides on:

0 = A side

1 = B side

3 0 Placeholder.


Commands

equ

ip_d

evic

e

lock

_dev

ice

un

lock

_dev

ice

dis

p_d

ev_s

tat

dis

p_d

evic

e

68P81132E13-O

10/3/02-GR

C-4


Local Area Network

LAN 1 0 to 1 Lan Location. ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Multiple Serial Interface

MSI 1 0 to 71 Specific MSI board. ✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Message Transfer Link

MTL 1 0 to 15 Specific MTP link (per ITU-T spec).

✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Operations and Maintenance Link

OML 1 0 or 1 Specific link between BSC and OMC.

✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Radio System Link

RSL 1 1 to 80 EBTS site identification which RSL is connecting.

✔ ✔ ✔ ✔ ✔

2 0 to 1 Specific link set.

3 0 Placeholder.

EBTS site SITE 1 1 to 80 Site identification associated with EBTS

✔

2 0 Placeholder.

3 0 Placeholder.


Commands

equ

ip_d

evic

e

lock

_dev

ice

un

lock

_dev

ice

dis

p_d

ev_s

tat

dis

p_d

evic

e

68P81132E13-O

10/3/02-GR

C-5


Individual Span line

SPAN 1 0 to 71 Associated MSI. ✔ ✔ ✔ ✔

2 0 or 1 Specific megastream.

3 0 Placeholder.

TDM bus TBUS 1 0 to 5 Cage location. ✔ ✔ ✔ ✔

2 0 or 1 TDM Highway Bus ID:

0 = A side

1 = B side

3 0 Placeholder.

Transcoder BSC link

XBL 1 0 to 31 Specific XCDR board.

✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Transcoder XCDR 1 0 to 54 Specific XCDR board.

✔ ✔ ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.


Commands

equ

ip_d

evic

e

lock

_dev

ice

un

lock

_dev

ice

dis

p_d

ev_s

tat

dis

p_d

evic

e

68P81132E13-O

10/3/02-GR

C-6


Function usage

The following table identifies all valid devices affected by device related commands. The columns represent the following information:

❐ FUNCTION – A description of the function.

❐ LITERAL – The acceptable literal used with MMI commands.

❐ ID – Three IDs are used for each function. Some commands may use IDs simply as placeholders.

❐ RANGE – The acceptable value range for the specified ID.

❐ DEFINITION – The definition of each ID.

❐ COMMANDS – The MMI commands used with the indicated function.

Commands

The following commands are function related commands. Page numbers are provided for your convenience. Check the table to see which functions may be used with these commands:

❐ equip_function on page 3-17

❐ disp_func_stat on page 4-47

❐ disp_function on page 4-49

68P81132E13-O

10/3/02-GR

C-7


Function LiteralID Range Definition

Commands

equ

ip_f

un

ctio

n

dis

p_f

un

c_st

at

dis

p_f

un

ctio

n

Link Control Function

LCF 1 0 to 19 Function identification. ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

Operation and Maintenance Function

OMF 1 0 Function identification. ✔ ✔ ✔

2 0 Placeholder.

3 0 Placeholder.

68P81132E13-O

10/3/02-GR

C-8

ACG Access Controller Gateway

AFRP Automatic Fault Recovery Procedure

APD Advanced Packet Duplicator

BR Base Radio

BSC Base Site Controller

BSP Base Site Processor

CBUS Clock Bus

CM Configuration Management

DAP Dispatch Applications Processor

DCC DAP Communication Composite

DL DAP Link

DTE Data Terminal Equipment

EBSC Enhanced Base Site Controller

EGPROC Enhanced General Processor (card)

ERXCDR Enhanced Remote Transcoder

GCLK Generic Clock (card)

GPROC General Processor (card)

GUI Graphical User Interface

HLR Home Location Register

IP Initialization Process

ISO Isolated Site Operation

KSW Kilo-port Switch

LAN Local Area Network

LCF Link Control Function

MSI Multiple Serial Interface (card)

MTL Message Transfer Link

MDG Mobile Data Gateway

MMI Man-Machine Interface

MSC Mobile Switching Center

NE Network Element

OMC Operations and Maintenance Center

OMF Operations and Maintenance Function

OML Operations and Maintenance Link

PSTN Public Switched Telephone Network

RAM Random Access Memory

RC Recent Change

RSL Radio System Link

RXCDR Remote Transcoder

SMFA Specific Management Functional Area

SYSGEN System Generation

TBUS TDM Bus

TDM Time Division Multiplex

XBL Remote Transcoder-to-BSC Link

XCDR Transcoder

ACRONYMS

10/29/01 Acronyms-i68P80801xxx-O

NOTES . . .

10/29/01Acronyms-ii 68P808xxxxx-O

Index

A

add_cell 2-2add_channel 2-4add_cic_conn 2-6add_circuit 3-2add_ebts_dte 2-9add_span_nail 2-11add_span_nailpipe 2-13add_xbl_conn 2-15alias 8-2auto_vp_flag 5-2

B

BSCsystem features 1-2

bsc_access_delay B-2bsc_audit 5-3bsc_call_hold_time B-3bsc_switch_fail B-3bsc_switch_success B-3

C

Call trace 7-1Call tracing 1-3chg_audit_sched 5-6

chg_cell_id 2-17chg_channel 2-19chg_channel_olcc 2-21chg_cic_conn 2-23chg_cic_conn_olcc 2-25chg_circuit 3-4chg_circuit_olcc 3-5chg_dte 2-27chg_ebts_dte 2-29chg_element 2-31chg_ksw_config 2-43, 2-45chg_level 1-4, 2-46chg_msi_mode 2-47chg_omc_dte 2-48chg_password 2-50chg_subrate_olcc 2-51chg_time 2-54cipher_mode_fail B-3classifications 1-5clear_database 2-56clear_gclk_avgs 3-7clear_stats 6-38clr_cmd_from_msc_after_ac B-4clr_cmd_from_msc_before_ac B-4clr_req_to_msc B-4clr_req_to_msc_after_ac B-5clr_req_to_msc_before_ac B-5command classifications

RC 1-5SYSGEN 1-5SYSGEN/RC 1-5

comment 8-4

Index - 1

D - F Index

Configuration management 2-1congestion_lost_msu B-23conn_refused B-5conn_req_to_msc B-6cpu_usage B-16

D

del_cell 2-57del_channel 2-58del_cic_conn 2-60del_circuit 3-8del_db_script 2-62del_ebts_dte 2-63del_span_nail 2-64del_subrate 2-66del_xbl_conn 2-68Dependencies C-2description 1-7Device management 1-2, 3-1Device usage C-3device_audit 5-9disable_alarm 3-9disp_act_cells 4-2disp_audit_sched 4-3disp_auto_vp_flag 4-4disp_bsc_stat 4-5disp_bsp 4-7disp_cell 4-8disp_channel 4-9disp_checksum 4-11disp_cic_conn 4-12disp_cic_use 4-15disp_circuit 4-17disp_dev_stat 4-18disp_device 4-23disp_dsp_reload 4-35disp_dte 4-36disp_ebts_dte 4-38disp_element 4-39disp_env_alarm 4-42disp_equipment 4-44disp_func_stat 4-47disp_function 4-49

disp_gclk_avgs 4-52disp_gclk_cal 4-53disp_interval 4-54disp_ksw_config 4-56disp_kswx 4-58disp_lcf 4-60disp_level 4-62disp_mcap_gproc 4-63disp_msi_alarms 4-64disp_nail_conn 4-65disp_num_ebts_dl 4-66disp_obj_info 4-67disp_omc_net 4-68, 4-69disp_plp_net 4-70disp_rf_cr_cell 4-71disp_span_alarm 4-72disp_span_tdm 4-73disp_span_use 4-75disp_stats 4-78disp_stats_intrvl 4-82disp_subrate 4-83disp_tdm_use 4-85disp_time 4-87disp_version 4-88disp_vpr 4-89disp_xbl_conn 4-92disp_xcdr_bypass 4-93disp_xcdr_types 4-94disp_xcdr_use 4-95Display 4-1

E

enable_alarm 3-10end_delta 8-5equip_device 3-11equip_function 3-17examples 1-15

F

Fault management 1-3, 5-1

Index - 2

Index G - M

fill_subrate 2-70find_sccp 7-3format 1-9frmr B-18ftp_mode 5-12ftp_query_alarm 5-13ftp_report_bsc 5-14ftp_report_cage 5-15ftp_report_dev 5-16ftp_severity_lvl 5-18ftp_trans_bsc 5-19ftp_trans_cage 5-20ftp_trans_device 5-21Function usage C-7

G

GPROC 1-1

H

handover_rec_to_bsc B-6help 8-6history 8-8ho_req_msc_fail B-6ho_req_msc_ok B-7

I

i_frames_rx B-18i_frames_tx B-18in_inter_ho B-8index numbers 1-12Information display 1-2Initialization process 1-1initl3_det_indication B-7initl3_loc_update B-7initl3_page_resp B-7initl3_service_req B-7inter_bsc_ho_delay B-8inter_bsc_ms_fail B-8

inter_bsc_req_to_msc B-9intra_bsc_ho B-9intra_bsc_ho_fail B-9intra_bsc_ho_lostms B-10intra_bsc_ho_pri_blk B-10intra_bsc_ho_req B-10intra_cell_ho B-11intra_cell_ho_fail B-11intra_cell_ho_lostms B-11intra_cell_ho_req B-12Introduction 1-1invalid_frames_rx B-18

L

lock_device 3-21

M

ma_req_from_msc B-12manual

typical pagedescription 1-7examples 1-15format 1-9parameters 1-10

manual_sysgen 2-73Miscellaneous 1-3, 8-1MMI commands

specific tasks 1-1msu_discarded B-23mtp_changeback B-20mtp_changeover B-20mtp_congestion B-23mtp_link_ins B-20mtp_linkfail B-22mtp_local_busy B-22mtp_local_mgt B-22mtp_mgt_inhibit B-22mtp_mgt_uninhibit B-22mtp_msu_rx B-23mtp_msu_tx B-24

Index - 3

N - S Index

mtp_neg_acks B-20mtp_re_tx B-24mtp_remote_mgt B-22mtp_remote_proc B-23mtp_restoration B-20mtp_sif_sio_rx B-24mtp_sif_sio_tx B-24mtp_sl_ack B-20mtp_sl_alignment B-21mtp_sl_congestion B-21mtp_sl_error_rate B-21mtp_sl_fail B-21mtp_sl_fibr B-21mtp_start_rpo B-23mtp_stop_rpo B-23mtp_su_error B-21mtp_unavailable B-23

N

n2_expiry B-18

O

OMC 1-1optional parameters 1-10out_inter_ho B-13

P

page_req_from_msc B-24page_req_from_msc_fail B-12parameters 1-10

elements 1-12index numbers 1-12optional parameters 1-10required parameters 1-10

Password changes 1-4phase_locking 3-25

Q

query_audits 5-23

R

required parameters 1-10reset_bsc 3-27restart_mon 3-28routing_syntax B-13routing_unknown B-13

S

sabm_tx B-18sar 6-44sccp_conn_confirmed B-13sccp_conn_refused B-13sccp_conn_released B-13sccp_msgs B-13sccp_msgs_rx B-19sccp_msgs_tx B-19Security

Level 1 1-4Level 2 1-4Level 3 1-4

Security level changes 1-4Security Management

about 1-4set_dsp_reld_flag 2-75set_num_ebts_download 2-76set_span_alarm 5-25set_span_clk_ref 2-77set_span_length 2-78set_xcdr_bypass 2-80sif_sio_rx_opc B-13sif_sio_tx_dpc B-14sif_sio_type B-25sl_congestion B-24sl_stop_congestion B-24soft_sysgen 2-81start_db_build 2-82

Index - 4

Index S - S

start_delta 8-9Statistic Definition

bsc_access_delay B-2bsc_switch_fail B-3bsc_switch_success B-3cipher_mode_fail B-3clr_cmd_from_msc_after_ac B-4clr_cmd_from_msc_before_ac B-4clr_req_to_msc B-4clr_req_to_msc_after_ac B-5clr_req_to_msc_before_ac B-5congestion_lost_msu B-23conn_refused B-5conn_req_to_msc B-6cpu_usage B-16frmr B-18handover_rec_to_bsc B-6ho_req_msc_fail B-6ho_req_msc_ok B-7i_frames_rx B-18i_frames_tx B-18in_inter_ho B-8initl3_det_indication B-7initl3_loc_update B-7initl3_page_resp B-7initl3_service_req B-7inter_bsc_ho_delay B-8inter_bsc_ms_fail B-8inter_bsc_req_to_msc B-9intra_bsc_ho B-9intra_bsc_ho_fail B-9intra_bsc_ho_lostms B-10intra_bsc_ho_pri_blk B-10intra_bsc_ho_req B-10intra_cell_ho B-11intra_cell_ho_fail B-11intra_cell_ho_lostms B-11intra_cell_ho_req B-12invalid_frames_rx B-18ma_req_from_msc B-12msu_discarded B-23mtp_changeback B-20mtp_changeover B-20mtp_congestion B-23mtp_link_ins B-20

mtp_linkfail B-22mtp_local_busy B-22mtp_local_mgt B-22mtp_mgt_inhibit B-22mtp_mgt_uninhibit B-22mtp_msu_rx B-23mtp_msu_tx B-24mtp_neg_acks B-20mtp_re_tx B-24mtp_remote_mgt B-22mtp_remote_proc B-23mtp_restoration B-20mtp_sif_sio_rx B-24mtp_sif_sio_tx B-24mtp_sl_ack B-20mtp_sl_alignment B-21mtp_sl_congestion B-21mtp_sl_error_rate B-21mtp_sl_fail B-21mtp_sl_fibr B-21mtp_start_rpo B-23mtp_stop_rpo B-23mtp_su_error B-21mtp_unavailable B-23n2_expiry B-18out_inter_ho B-13page_req_from_msc B-24page_req_from_msc_fail B-12routing_syntax B-13routing_unknown B-13sabm_tx B-18sccp_conn_confirmed B-13sccp_conn_refused B-13sccp_conn_released B-13sccp_msgs B-13sccp_msgs_rx B-19sccp_msgs_tx B-19sif_sio_rx_opc B-13sif_sio_tx_dpc B-14sif_sio_type B-25sl_congestion B-24sl_stop_congestion B-24total_calls B-15unsuccessful_assignment B-15

Statistics 1-3, 6-1

Index - 5

T - V Index

stats 6-48sysgen_mode 2-84

T

tdm_conn_test 5-27test_vp 5-29time_stamp 8-10total_calls B-15trace_call 7-8TTY port 1-1

U

unalias 8-11unlock_device 3-30unsuccessful_assignment B-15

V

vp_sched_aud_off 5-32

Index - 6

bsc mmi commands

Documents

united states

sparc trademarks

noticethe motorola products

trademark of brio technology

trademark of novell

device management

document hasbeen

rights reservedthis