68P02900W22

System Information: DataGen
68P02900W22-R
Mar 2008
GMR-02
1996-2008 Motorola, Inc.
All Rights Reserved
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modied in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Trafc Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specically disclaim any expressed or implied warranty of tness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Ofce. All other product or service
names are the property of their respective owners.
The CE mark conrms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Ofce.
GMR-02
Mar 2008
Table
of
Contents
Contents

Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
In EU countries . . . . . . . . . .
In non-EU countries . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner denitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
10
11
11
11
11
. . .
MIB
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-2
1-2
1-3
1-4
1-4
1-5
1-7
1-7
1-7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: Overview of DataGen

Overview of DataGen . . . . . . . . . . .
Introduction to DataGen and the Ofine
Overview of DataGen . . . . . . . . .
DataGen functionality . . . . . . . . .
Overview of the Ofine MIB . . . . . .
Ofine MIB functionality . . . . . . . .
DataGen/Ofine MIB integration. . . .
The DataGen and OLM platform . . . .
DataGen database structure . . . . . . . .
Introduction . . . . . . . . . . . . . .
BSS database . . . . . . . . . . . . .
68P02900W22-R
Mar 2008
GMR-02
Contents
DataGen and the OMC . . . . . . . . . . . . . . . .

Loading network information into DataGen . . . . . . .
Introduction to loading network information . . . . .
Gathering network information . . . . . . . . . . .
The DataGen Directory Structure (DDS) . . . . . . .
Main structure of the DDS . . . . . . . . . . . . . .
Sub structure . . . . . . . . . . . . . . . . . . . .
The Ofine MIB directory structure . . . . . . . . .
The Ofine MIB le structure . . . . . . . . . . . .
Main structure of the Ofine MIB directory structure
Supported platforms . . . . . . . . . . . . . . . . . . .
Overview of supported platforms . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-7
1-9
1-9
1-10
1-11
1-12
1-13
1-13
1-13
1-14
1-15
1-15
Chapter 2: User and Group management using the usertool

User and Group management using the usertool.
Introduction to usertool . . . . . . . . . . .
Common Desktop Environment Manager . .
Usertool - Overview . . . . . . . . . . . . .
Procedure list . . . . . . . . . . . . . . . .
DataGen User management using the usertool. .
Introduction to user management . . . . . .
User management parameters . . . . . . . .
User administration utility . . . . . . . . . .
Add a new user account . . . . . . . . . . .
Modify a user account . . . . . . . . . . . .
Rename a user account . . . . . . . . . . .
Delete a user account . . . . . . . . . . . .
DataGen Group management using the usertool .
Introduction to group management . . . . .
Group management parameters . . . . . . .
Group Administration Utility . . . . . . . . .
Add a group . . . . . . . . . . . . . . . . .
Modify group information . . . . . . . . . .
Rename a group . . . . . . . . . . . . . . .
Delete a group . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-2
2-2
2-2
2-3
2-3
2-3
2-4
2-7
2-9
2-10
2-11
2-13
2-13
2-13
2-13
2-13
2-15
2-16
2-17
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
table
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-2
3-2
3-4
3-4
3-4
3-5
3-5
3-5
3-6
3-6
3-7
3-7
3-8
3-8
3-9
3-9
3-9
3-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 3: Operating DataGen

Overview of operating DataGen . . . . .
About this chapter . . . . . . . . . .
Procedures for operating DataGen . .
Dening environment variables . . . . .
Overview of environment variables .
HEX or decimal representation . . .
Version list order. . . . . . . . . . .
Time slot order equipage . . . . . .
Automate running of Revgen. . . . .
Default le import path . . . . . . .
Default export path . . . . . . . . .
Dene default text editor . . . . . .
Override area lock . . . . . . . . . .
Output all elements in a script . . . .
Display only generic algorithm details
DataGen - startup and shutdown . . . . .
Introduction to startup and shutdown
Startup. . . . . . . . . . . . . . . .
Shutdown . . . . . . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
in alg.mcd
. . . . . .
. . . . . .
. . . . . .
. . . . . .
ii
68P02900W22-R
GMR-02
Mar 2008
Contents
Administration tasks . . . . . . . . . . . . . . . . . . . .
Overview of tasks . . . . . . . . . . . . . . . . . . .
Changing permissions . . . . . . . . . . . . . . . . .
Optimizing the database . . . . . . . . . . . . . . . .
Viewing the log le . . . . . . . . . . . . . . . . . .
Customizing parameters . . . . . . . . . . . . . . . .
Installing the Options Object. . . . . . . . . . . . . .
Database administration tasks . . . . . . . . . . . . . . .
Monitoring le and database capacities . . . . . . . .
Running usage script as a cronjob . . . . . . . . . . .
Verifying usage cronjob . . . . . . . . . . . . . . . .
Running usage script manually . . . . . . . . . . . .
Warning messages issued . . . . . . . . . . . . . . .
Reloading the database . . . . . . . . . . . . . . . .
Dropping and recreating the db_dg Informix database.
Importing existing CM database objects . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . .
Creating a new country/network . . . . . . . . . . . . . .
Overview of creating a new country/network . . . . .
Country Admin option . . . . . . . . . . . . . . . . .
Country Administration window - An Overview . . . .
Creating a new country . . . . . . . . . . . . . . . .
Editing a country . . . . . . . . . . . . . . . . . . .
Creating a new network . . . . . . . . . . . . . . . .
Deleting a country/network . . . . . . . . . . . . . . . .
Overview of deleting a country/network . . . . . . . .
Deleting the network. . . . . . . . . . . . . . . . . .
Deleting the country . . . . . . . . . . . . . . . . . .
Creating a BSS area . . . . . . . . . . . . . . . . . . . .
Overview of creating a BSS area . . . . . . . . . . . .
New BSS Area window. . . . . . . . . . . . . . . . .
Creating a BSS area . . . . . . . . . . . . . . . . . .
Opening a BSS area . . . . . . . . . . . . . . . . . . . .
Opening a BSS area . . . . . . . . . . . . . . . . . .
Copying a BSS area . . . . . . . . . . . . . . . . . . . .
Copying a BSS area procedure. . . . . . . . . . . . .
Deleting a BSS area . . . . . . . . . . . . . . . . . . . .
Deleting an existing BSS area . . . . . . . . . . . . .
Conguring BSS area(s) . . . . . . . . . . . . . . . . . .
Introduction to conguring the BSS . . . . . . . . . .
Explanation of terms . . . . . . . . . . . . . . . . . .
Functions and MCDF table relationships. . . . . . . .
Basic BSS with TS switch - Expansion . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . .
Copying a BSS area . . . . . . . . . . . . . . . . . .
Expanding the BSS. . . . . . . . . . . . . . . . . . .
Daisy Chain conguration with TS switch . . . . . . . . .
Overview of Daisy Chain conguration. . . . . . . . .
Preparation . . . . . . . . . . . . . . . . . . . . . .
Daisy chain conguration . . . . . . . . . . . . . . .
The Service window . . . . . . . . . . . . . . . . . . . .
Functions of the Service window. . . . . . . . . . . .
Service window toolbar . . . . . . . . . . . . . . . .
Service window menu bar . . . . . . . . . . . . . . .
File menu . . . . . . . . . . . . . . . . . . . . . . .
Edit menu . . . . . . . . . . . . . . . . . . . . . . .
Services menu . . . . . . . . . . . . . . . . . . . . .
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-11
3-11
3-12
3-13
3-14
3-15
3-16
3-19
3-19
3-19
3-19
3-20
3-20
3-20
3-21
3-25
3-25
3-25
3-26
3-26
3-26
3-27
3-29
3-30
3-31
3-32
3-32
3-32
3-33
3-34
3-34
3-34
3-36
3-39
3-39
3-41
3-41
3-43
3-43
3-45
3-45
3-45
3-45
3-47
3-47
3-48
3-48
3-52
3-52
3-52
3-53
3-56
3-56
3-56
3-58
3-58
3-62
3-63
iii
GMR-02
Contents
Converting a CM database object le to a script le

Introduction to creating a script le . . . . . .
Invoking Revgen . . . . . . . . . . . . . . . .
Revgen window description . . . . . . . . . .
File menu . . . . . . . . . . . . . . . . . . .
Information area . . . . . . . . . . . . . . . .
Data area . . . . . . . . . . . . . . . . . . .
Toolbar. . . . . . . . . . . . . . . . . . . . .
Activating Revgen . . . . . . . . . . . . . . .
Activating auto Revgen . . . . . . . . . . . .
Completion of Revgen process . . . . . . . . .
Generating a database script le. . . . . . . . . .
Overview of database script les. . . . . . . .
Running the script le generator . . . . . . .
Viewing a database script le . . . . . . . . .
xedit window description . . . . . . . . . . .
Using the toolbars . . . . . . . . . . . . . . .
File information areas . . . . . . . . . . . . .
File display area . . . . . . . . . . . . . . . .
Alternative text editor . . . . . . . . . . . . .
Viewing and editing DataGen les . . . . . . . . .
Overview of editing DataGen les . . . . . . .
Table Controller . . . . . . . . . . . . . . . .
Generic Table Editor . . . . . . . . . . . . . .
Topology Viewer . . . . . . . . . . . . . . . .
Upgrader . . . . . . . . . . . . . . . . . . .
Using the Table Controller . . . . . . . . . . . . .
Running the Table Controller . . . . . . . . .
Table Controller functions . . . . . . . . . . .
User controls . . . . . . . . . . . . . . . . .
Menu bar . . . . . . . . . . . . . . . . . . .
Command buttons . . . . . . . . . . . . . . .
File select buttons . . . . . . . . . . . . . . .
File status display area . . . . . . . . . . . .
MCDF table les . . . . . . . . . . . . . . . .
Creating MCDF les . . . . . . . . . . . . . .
MCDF le procedures . . . . . . . . . . . . .
MCDF table editing . . . . . . . . . . . . . .
File status icons . . . . . . . . . . . . . . . .
Using the Generic Table Editor (GTE) . . . . . . .
Introduction to the Generic Table Editor . . . .
The File menu . . . . . . . . . . . . . . . . .
The Edit menu . . . . . . . . . . . . . . . . .
Fill Cells window. . . . . . . . . . . . . . . .
Format menu. . . . . . . . . . . . . . . . . .
MCDF key equivalents . . . . . . . . . . . . .
Using the Topology Viewer. . . . . . . . . . . . .
Introduction to the Topology Viewer . . . . . .
Invoking the Topology Viewer . . . . . . . . .
Using the Topology Viewer. . . . . . . . . . .
Cage hardware conguration button. . . . . .
The MMI button . . . . . . . . . . . . . . . .
Path File button . . . . . . . . . . . . . . . .
Increase magnication button . . . . . . . . .
Decrease magnication button. . . . . . . . .
Generating a hardware report . . . . . . . . . . .
Overview of hardware reports . . . . . . . . .
Procedure for generating a hardware report. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-65
3-65
3-65
3-65
3-66
3-66
3-66
3-66
3-67
3-68
3-69
3-70
3-70
3-70
3-71
3-72
3-73
3-73
3-73
3-73
3-76
3-76
3-76
3-76
3-76
3-77
3-78
3-78
3-79
3-79
3-79
3-79
3-80
3-80
3-80
3-83
3-83
3-85
3-87
3-89
3-89
3-89
3-95
3-96
3-98
3-103
3-104
3-104
3-105
3-106
3-106
3-108
3-108
3-108
3-108
3-109
3-109
3-109
68P02900W22-R
GMR-02
Mar 2008
Contents
Converting a database script le to a CM database object le .

Overview of conversion . . . . . . . . . . . . . . . . . .
Producing a CM database object using SYSGEN mode. . .
Producing a CM database object using the DataGen binary
Exporting object les to the OMC . . . . . . . . . . . . . . .
Overview of exporting object les . . . . . . . . . . . . .
Exporting multiple binary object les . . . . . . . . . . .
Exporting a single binary object le . . . . . . . . . . . .
Exporting OLM binary object les to the OMC . . . . . . .
Difference Reporter . . . . . . . . . . . . . . . . . . . . . .
Introduction to the Difference Reporter . . . . . . . . . .
The Difference Reporter window. . . . . . . . . . . . . .
Select BSS Area Details window . . . . . . . . . . . . . .
Difference Reporter Information window . . . . . . . . .
Difference Reporter Report window . . . . . . . . . . . .
Upgrader . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the Upgrade function . . . . . . . . . . . . .
Upgrade BSS Area window . . . . . . . . . . . . . . . .
Upgrading a BSS Area . . . . . . . . . . . . . . . . . . .
Upgrade multiple BSS areas . . . . . . . . . . . . . . . .
Resolving upgrade problems . . . . . . . . . . . . . . . .
Overview of DARBC and Enhanced XBL . . . . . . . . . .
Batch processing of binary object les . . . . . . . . . . . . .
Overview of batch processing . . . . . . . . . . . . . . .
Revgen multiple binary object les . . . . . . . . . . . .
Upgrade multiple binary object les . . . . . . . . . . . .
Compile multiple MMI scripts . . . . . . . . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
object compiler .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-111
3-111
3-111
3-111
3-114
3-114
3-114
3-115
3-116
3-117
3-117
3-117
3-118
3-120
3-121
3-122
3-122
3-122
3-124
3-126
3-126
3-128
3-129
3-129
3-130
3-133
3-134
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-2
4-2
4-3
4-3
4-3
4-4
4-4
4-4
4-5
4-6
4-6
4-6
4-6
4-9
4-9
4-9
4-12
4-12
4-15
4-15
4-15
4-15
4-15
4-16
4-16
4-16
4-16
Chapter 4: Operating the Ofine MIB

Introduction to the Ofine MIB . . . . .
Overview of the Ofine MIB . . . . .
Task list prior to using OLM GUI. . .
Task list for using the OLM GUI . . .
Further information . . . . . . . . .
Additional OLM tasks . . . . . . . .
Levels of users . . . . . . . . . . . .
Troubleshooting and other tasks . . .
OLM environment variables . . . . .
Using the cmutil.olm command . . .
Starting/creating a network conguration
Introduction to network conguration
Starting the OLM . . . . . . . . . .
Creating a network conguration . .
Starting/exiting the OLM GUI . . . . . .
Introduction . . . . . . . . . . . . .
Starting the OLM GUI . . . . . . . .
Exiting the OLM GUI. . . . . . . . .
Shutting down the OLM . . . . . . .
Front panel icons . . . . . . . . . . . .
Ofine MIB front panel . . . . . . .
About the Ofine MIB . . . . . . . .
Conguration management . . . . .
Administration . . . . . . . . . . . .
Find . . . . . . . . . . . . . . . . .
Help . . . . . . . . . . . . . . . . .
Xterm . . . . . . . . . . . . . . . .
Exit . . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
in the OLM .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
GMR-02
Contents
Expert Ofine MIB front panel . . . . . . . . . . . . . . .

Finding devices and attributes . . . . . . . . . . . . . . . . .
Overview of the Find function . . . . . . . . . . . . . . .
Finding a Network Element, PCU, Site, or Cell. . . . . . . . .
Finding an NE, PCU, Site, or Cell . . . . . . . . . . . . .
Examples of using Find . . . . . . . . . . . . . . . . . .
Finding an attribute . . . . . . . . . . . . . . . . . . . . . .
Overview of nding attributes . . . . . . . . . . . . . . .
Using the Navigation Tree: Overview . . . . . . . . . . . . .
Procedure list . . . . . . . . . . . . . . . . . . . . . . .
Further information . . . . . . . . . . . . . . . . . . . .
Opening and closing a Navigation Tree . . . . . . . . . . . .
Opening the Navigation Tree . . . . . . . . . . . . . . .
Warning window invalid NE . . . . . . . . . . . . . . . .
Resolving inconsistencies . . . . . . . . . . . . . . . . .
Closing the Navigation Tree . . . . . . . . . . . . . . . .
Moving levels on a Navigation Tree . . . . . . . . . . . . . .
Prerequisite to moving levels . . . . . . . . . . . . . . .
Procedure for moving levels . . . . . . . . . . . . . . . .
Panner and porthole . . . . . . . . . . . . . . . . . . . .
Creating a BSS/RXCDR from the Navigation Tree . . . . . . .
Introduction to creating an NE. . . . . . . . . . . . . . .
Procedure for creating a BSS or RXCDR . . . . . . . . . .
Audit: overview . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to auditing . . . . . . . . . . . . . . . . . .
Ways to audit . . . . . . . . . . . . . . . . . . . . . . .
Running an audit from the Navigation Tree . . . . . . . . . .
Introduction to auditing from the Navigation Tree . . . . .
Audit from the Navigation Tree . . . . . . . . . . . . . .
Modifying the network conguration from the Navigation Tree
Device management . . . . . . . . . . . . . . . . . . . .
Conguring cells . . . . . . . . . . . . . . . . . . . . . .
CellXchange: overview. . . . . . . . . . . . . . . . . . . . .
Introduction to CellXchange . . . . . . . . . . . . . . . .
Overwrite a BSS/RXCDR binary object le . . . . . . . . . . .
Overview of overwrite feature . . . . . . . . . . . . . . .
Procedure for overwriting a BSS Binary object le. . . . .
Verify and save: overview . . . . . . . . . . . . . . . . . . .
Introduction to applying changes . . . . . . . . . . . . .
Verify and save NE database . . . . . . . . . . . . . . . . . .
Verify a network element . . . . . . . . . . . . . . . . .
Save a network element . . . . . . . . . . . . . . . . . .
Verify and save network . . . . . . . . . . . . . . . . . . . .
Verify network . . . . . . . . . . . . . . . . . . . . . . .
Aborting a verify network in progress . . . . . . . . . . .
Saving a network . . . . . . . . . . . . . . . . . . . . .
Aborting a save network in progress . . . . . . . . . . . .
Deleting a network conguration in the OLM . . . . . . . . .
Introduction to deleting a network . . . . . . . . . . . . .
Delete network conguration . . . . . . . . . . . . . . .
Network Expansion: overview . . . . . . . . . . . . . . . . .
Overview of Network Expansion . . . . . . . . . . . . . .
Additional OLM features . . . . . . . . . . . . . . . . . . . .
List of additional tasks . . . . . . . . . . . . . . . . . . .
Using the autoclose function . . . . . . . . . . . . . . . . . .
Overview of autoclose feature . . . . . . . . . . . . . . .
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . .
Procedure for using autoclose . . . . . . . . . . . . . . .
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-17
4-18
4-18
4-19
4-19
4-22
4-24
4-24
4-27
4-27
4-27
4-28
4-28
4-29
4-29
4-29
4-30
4-30
4-30
4-31
4-32
4-32
4-32
4-34
4-34
4-34
4-35
4-35
4-35
4-37
4-37
4-37
4-38
4-38
4-39
4-39
4-39
4-42
4-42
4-43
4-43
4-45
4-46
4-46
4-50
4-51
4-52
4-53
4-53
4-53
4-55
4-55
4-56
4-56
4-57
4-57
4-57
4-57
68P02900W22-R
GMR-02
Mar 2008
Contents
Deleting a BSS or RXCDR from the Navigation Tree . . . . . .

Introduction to deleting BSS or RXCDR network elements.
Deleting BSS or RXCDR network elements . . . . . . . .
Scheduling an audit . . . . . . . . . . . . . . . . . . . . . .
List of procedures . . . . . . . . . . . . . . . . . . . . .
Creating a scheduled audit . . . . . . . . . . . . . . . .
Modifying a scheduled audit . . . . . . . . . . . . . . . .
Deleting a scheduled audit . . . . . . . . . . . . . . . . .
Auditing logs . . . . . . . . . . . . . . . . . . . . . . . . . .
List of procedures . . . . . . . . . . . . . . . . . . . . .
Viewing an audit log list . . . . . . . . . . . . . . . . . .
Aborting an audit in progress . . . . . . . . . . . . . . .
Inconsistency reports . . . . . . . . . . . . . . . . . . .
Viewing an audit inconsistency report . . . . . . . . . . .
Deleting an audit log. . . . . . . . . . . . . . . . . . . .
Audit log management . . . . . . . . . . . . . . . . . . . . .
Overview of audit log management . . . . . . . . . . . .
Setting the delete period. . . . . . . . . . . . . . . . . .
Reload NE database . . . . . . . . . . . . . . . . . . . . . .
Introduction to reloading an NE database . . . . . . . . .
Procedure for reloading an NE database. . . . . . . . . .
Realign a network . . . . . . . . . . . . . . . . . . . . . . .
Introduction to realigning a network. . . . . . . . . . . .
Procedure for realigning a network . . . . . . . . . . . .
Compress or uncompress an OLM network . . . . . . . . . .
Overview of compress and uncompress . . . . . . . . . .
Compress a network procedure . . . . . . . . . . . . . .
Uncompress a network procedure . . . . . . . . . . . . .
Troubleshooting the OLM . . . . . . . . . . . . . . . . . . .
Introduction to troubleshooting the OLM . . . . . . . . .
Error OLM fails to start . . . . . . . . . . . . . . . . . .
Database errors . . . . . . . . . . . . . . . . . . . . . .
General errors . . . . . . . . . . . . . . . . . . . . . . .
Specic operation fails. . . . . . . . . . . . . . . . . . .
Import errors . . . . . . . . . . . . . . . . . . . . . . .
Introduction to the force shutdown feature . . . . . . . .
Force shutdown OLM procedure . . . . . . . . . . . . . .
Reinitialize database procedure . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-58
4-58
4-58
4-60
4-60
4-60
4-65
4-67
4-68
4-68
4-68
4-69
4-70
4-71
4-72
4-73
4-73
4-73
4-75
4-75
4-75
4-77
4-77
4-77
4-79
4-79
4-79
4-80
4-81
4-81
4-81
4-82
4-83
4-83
4-84
4-84
4-85
4-86
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-3
5-3
5-5
5-5
5-5
5-5
5-5
5-6
5-6
5-6
5-7
5-7
5-7
5-7
5-7
Chapter 5: Command line tools

Overview of command line tools . . .
Command line functions . . . . .
General information . . . . . . .
User options . . . . . . . . . . .
Copy Area (ca) command . . . . . .
Name . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . .
Description . . . . . . . . . . .
Command line options . . . . . .
Requirements . . . . . . . . . .
Output . . . . . . . . . . . . . .
Example Copy Area usage . . . .
MMI Combiner (combine) command .
Name . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . .
Description . . . . . . . . . . .
Output . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vii
GMR-02
Contents
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Compile MMI script (compile) command . . . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Auto-compile MMI script command . . . . . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Command line options . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . . . . .
Example auto_compile usage . . . . . . . .
Running cron jobs . . . . . . . . . . . . . .
Compress/uncompress binary object les . . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Delete database object (del) command . . . . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
MCDF lter command . . . . . . . . . . . . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
MMI command generator (gcmd) command . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . . . . .
Optimize DataGen database (dbaccess) command
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Lock/unlock BSS area (lock_adm) command . . .
Name . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-8
5-8
5-9
5-9
5-9
5-9
5-9
5-9
5-10
5-10
5-10
5-10
5-10
5-11
5-11
5-11
5-11
5-13
5-13
5-13
5-13
5-14
5-14
5-15
5-15
5-15
5-15
5-15
5-16
5-16
5-17
5-17
5-17
5-17
5-17
5-18
5-19
5-20
5-20
5-20
5-20
5-20
5-21
5-21
5-21
5-22
5-22
5-22
5-22
5-22
5-22
5-23
5-23
5-23
5-23
5-23
5-24
5-24
68P02900W22-R
GMR-02
Mar 2008
Contents
Output . . . . . . . . . . . . . . . . .
Revgen command . . . . . . . . . . . . .
Name . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . .
Command line options . . . . . . . . .
Example . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . .
Auto-Revgen command. . . . . . . . . . .
Name . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . .
Toggle permissions (tp) command . . . . .
Name . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . .
Version upgrader (upg) command . . . . .
Name . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . .
Example of upgrading . . . . . . . . .
Auto-upgrader command. . . . . . . . . .
Name . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . .
Country administration . . . . . . . . . .
Introduction to country administration.
Command Line Interface (CLI) . . . . .
Invoking xcadm . . . . . . . . . . . .
Using the xcadm GUI . . . . . . . . .
Menus . . . . . . . . . . . . . . . . .
Data elds . . . . . . . . . . . . . . .
Action buttons . . . . . . . . . . . . .
CADM utilities . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-24
5-25
5-25
5-25
5-25
5-25
5-27
5-27
5-27
5-28
5-28
5-28
5-28
5-28
5-29
5-29
5-29
5-30
5-30
5-30
5-30
5-30
5-30
5-30
5-31
5-31
5-31
5-31
5-31
5-32
5-32
5-32
5-33
5-33
5-33
5-33
5-33
5-34
5-34
5-34
5-36
5-36
5-36
5-36
5-37
5-38
5-39
5-39
5-40
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-2
6-2
6-5
6-5
6-9
Chapter 6: MCDF tables

Overview of MCDF tables . . . .
Scope of MCDF tables . . . .
MCDF BSS and RXCDR tables
BSS table . . . . . . . . . . . .
Description of BSS table . . .
Site (BTS specic) table . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W22-R
Mar 2008
ix
GMR-02
Contents
Description of Site (BTS specic) table . . .

Cabinet table. . . . . . . . . . . . . . . . . . .
Description of Cabinet table . . . . . . . . .
Hardware table . . . . . . . . . . . . . . . . .
Description of Hardware table . . . . . . . .
Generics table . . . . . . . . . . . . . . . . . .
Description of Generics table . . . . . . . .
Layout of elements in the MCDF Generics table .
Timer table. . . . . . . . . . . . . . . . . . . .
Description of Timer table . . . . . . . . . .
Layout of timer elements in the MCDF Timer
Modify Value table . . . . . . . . . . . . . . . .
Description of Modify Value table . . . . . .
Circuit table . . . . . . . . . . . . . . . . . . .
Description of Circuit table . . . . . . . . .
Channel table . . . . . . . . . . . . . . . . . .
Description of Channel table . . . . . . . . .
Links table . . . . . . . . . . . . . . . . . . . .
Description of Links table . . . . . . . . . .
Paths table . . . . . . . . . . . . . . . . . . . .
Description of Paths table . . . . . . . . . .
LAPD table . . . . . . . . . . . . . . . . . . . .
Description of LAPD table . . . . . . . . . .
Cell table. . . . . . . . . . . . . . . . . . . . .
Description of Cell table . . . . . . . . . . .
Statistics table . . . . . . . . . . . . . . . . .
Description of Statistics table . . . . . . . .
Layout of elements in the MCDF Statistics table .
Specics table . . . . . . . . . . . . . . . . . .
Description of Specics table . . . . . . . .
Layout of elements in the MCDF Specics table .
RTF table . . . . . . . . . . . . . . . . . . . .
Description of RTF table . . . . . . . . . . .
DRI table. . . . . . . . . . . . . . . . . . . . .
Description of DRI table . . . . . . . . . . .
Algorithm data table . . . . . . . . . . . . . . .
Description of Algorithm data table . . . . .
Neighbor table . . . . . . . . . . . . . . . . . .
Description of Neighbor table . . . . . . . .
Throttles table . . . . . . . . . . . . . . . . . .
Description of Throttles table . . . . . . . .
EAS table . . . . . . . . . . . . . . . . . . . .
Description of EAS table . . . . . . . . . . .
Daughter table . . . . . . . . . . . . . . . . . .
Description of Daughter table . . . . . . . .
PIX table . . . . . . . . . . . . . . . . . . . . .
Description of PIX table . . . . . . . . . . .
KSW table . . . . . . . . . . . . . . . . . . . .
Description of KSW table . . . . . . . . . .
NSVC table . . . . . . . . . . . . . . . . . . .
Description of NSVC table . . . . . . . . . .
Hop table . . . . . . . . . . . . . . . . . . . .
Description of Hop table . . . . . . . . . . .
ACS table . . . . . . . . . . . . . . . . . . . .
Description of ACS table . . . . . . . . . . .
Test Neighbor table . . . . . . . . . . . . . . .
Description of the Test Neighbor table . . . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
table
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-9
6-12
6-12
6-15
6-15
6-26
6-26
6-27
6-46
6-46
6-46
6-52
6-52
6-55
6-55
6-58
6-58
6-60
6-60
6-63
6-63
6-65
6-65
6-67
6-67
6-78
6-78
6-79
6-109
6-109
6-111
6-155
6-155
6-161
6-161
6-165
6-165
6-168
6-168
6-175
6-175
6-176
6-176
6-177
6-177
6-178
6-178
6-179
6-179
6-181
6-181
6-182
6-182
6-187
6-187
6-195
6-195
68P02900W22-R
GMR-02
Mar 2008
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1: DataGen GUI . . . . . . . . . . . . . . . . . . . . . . .

1-2: Ofine MIB - Front Panel . . . . . . . . . . . . . . . . .
1-3: DataGen/Ofine MIB functions . . . . . . . . . . . . . .
1-4: DataGen in a GSM environment . . . . . . . . . . . . . .
1-5: DataGen-OMC integration . . . . . . . . . . . . . . . . .
1-6: Loading network information into DataGen . . . . . . . .
1-7: Creating MCDF les . . . . . . . . . . . . . . . . . . . .
1-8: DataGen directory structure . . . . . . . . . . . . . . . .
1-9: Example of Ofine MIB directory structure . . . . . . . .
1-10: Example of Ofine MIB le structure. . . . . . . . . . .
2-1: CDE desktop - front panel . . . . . . . . . . . . . . . . .
2-2: The usertool icon . . . . . . . . . . . . . . . . . . . . .
2-3: CDE desktop front panel with open OMC Admin drawer. .
2-4: Usertool menu window . . . . . . . . . . . . . . . . . .
3-1: DataGen main menu . . . . . . . . . . . . . . . . . . . .
3-2: Administration menu - omcadmin user. . . . . . . . . . .
3-3: Permissions window . . . . . . . . . . . . . . . . . . . .
3-4: Conrm permissions . . . . . . . . . . . . . . . . . . . .
3-5: Administration menu - non-omcadmin user . . . . . . . .
3-6: Example of a logle . . . . . . . . . . . . . . . . . . . .
3-7: Preferences window . . . . . . . . . . . . . . . . . . . .
3-8: Options Object Tool window . . . . . . . . . . . . . . . .
3-9: Country Administration window . . . . . . . . . . . . . .
3-10: CADM Country File window . . . . . . . . . . . . . . .
3-11: CADM message window . . . . . . . . . . . . . . . . .
3-12: CADM Network File window . . . . . . . . . . . . . . .
3-13: New BSS Area window . . . . . . . . . . . . . . . . . .
3-14: Warning message: name exceeds maximum valid length .
3-15: Overwrite BSS Area conrmation window . . . . . . . .
3-16: The Service window . . . . . . . . . . . . . . . . . . .
3-17: Open BSS Area window . . . . . . . . . . . . . . . . .
3-18: Locked information window . . . . . . . . . . . . . . .
3-19: Copy BSS Area window. . . . . . . . . . . . . . . . . .
3-20: Delete BSS Area window . . . . . . . . . . . . . . . . .
3-21: Information window . . . . . . . . . . . . . . . . . . .
3-22: Basic BSS with TS Switch - expanded . . . . . . . . . .
3-23: Service window. . . . . . . . . . . . . . . . . . . . . .
3-24: Database Object window . . . . . . . . . . . . . . . . .
3-25: Import Object - information window . . . . . . . . . . .
3-26: Export Object - information window . . . . . . . . . . .
3-27: History - information window. . . . . . . . . . . . . . .
3-28: Revgen window. . . . . . . . . . . . . . . . . . . . . .
3-29: Running Revgen . . . . . . . . . . . . . . . . . . . . .
3-30: Invalid Options Object message . . . . . . . . . . . . .
3-31: Viewing a database script le . . . . . . . . . . . . . .
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-3
1-5
1-6
1-8
1-10
1-11
1-12
1-13
1-13
2-5
2-5
2-5
2-6
3-9
3-12
3-12
3-13
3-14
3-14
3-15
3-17
3-26
3-29
3-30
3-31
3-34
3-36
3-37
3-37
3-39
3-40
3-41
3-43
3-44
3-51
3-56
3-59
3-60
3-61
3-62
3-67
3-68
3-71
3-72
xi
GMR-02
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
3-32: Viewing an MMI script with vi . . . . . . . . . . . . . . . . . . .

3-33: Partial view of typical Table Controller display . . . . . . . . . .
3-34: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-35: New MCDF input le message . . . . . . . . . . . . . . . . . . .
3-36: MCDF Input File - Open option . . . . . . . . . . . . . . . . . . .
3-37: Save To File window . . . . . . . . . . . . . . . . . . . . . . . .
3-38: Print Setup window . . . . . . . . . . . . . . . . . . . . . . . .
3-39: Print Table window . . . . . . . . . . . . . . . . . . . . . . . . .
3-40: Fill Cells window . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41: Find window . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-42: Goto Cell window. . . . . . . . . . . . . . . . . . . . . . . . . .
3-43: Replace window . . . . . . . . . . . . . . . . . . . . . . . . . .
3-44: Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . .
3-45: Topology Viewer menu bar . . . . . . . . . . . . . . . . . . . . .
3-46: The Cage Number window . . . . . . . . . . . . . . . . . . . . .
3-47: The Cage Description window . . . . . . . . . . . . . . . . . . .
3-48: Viewing a hardware report . . . . . . . . . . . . . . . . . . . . .
3-49: Binary Object Compiler window . . . . . . . . . . . . . . . . . .
3-50: Difference Reporter window . . . . . . . . . . . . . . . . . . . .
3-51: Select BSS Area Details window . . . . . . . . . . . . . . . . . .
3-52: Difference Reporter - Information window . . . . . . . . . . . . .
3-53: Difference Reporter - Report window. . . . . . . . . . . . . . . .
3-54: Upgrade BSS Area window . . . . . . . . . . . . . . . . . . . . .
3-55: Locked information window . . . . . . . . . . . . . . . . . . . .
3-56: Successful upgrade Status window . . . . . . . . . . . . . . . . .
3-57: Batch Tool window with Revgen selected. . . . . . . . . . . . . .
3-58: Revgen batch conrmation window . . . . . . . . . . . . . . . .
3-59: Revgen Batch monitor window . . . . . . . . . . . . . . . . . . .
3-60: Compile Batch monitor window . . . . . . . . . . . . . . . . . .
4-1: Ofine MIB Network Congurations window . . . . . . . . . . . .
4-2: OLM Network conguration creation window . . . . . . . . . . . .
4-3: Starting the OLM - conrmation window . . . . . . . . . . . . . .
4-4: Opening a network conguration - status window . . . . . . . . . .
4-5: Ofine MIB front panel . . . . . . . . . . . . . . . . . . . . . . .
4-6: GUI exit - conrmation window . . . . . . . . . . . . . . . . . . .
4-7: OLM shutdown conrmation window . . . . . . . . . . . . . . . .
4-8: Binary Database errors and warning window for a Network Element
4-9: Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-10: Find window . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-11: Find window with a Cell and Navigation Tree selected . . . . . . .
4-12: Find Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13: Navigation Tree window . . . . . . . . . . . . . . . . . . . . . .
4-14: Invalid NEs window . . . . . . . . . . . . . . . . . . . . . . . .
4-15: Navigation Tree window - showing panner . . . . . . . . . . . . .
4-16: BSS Binary congurations creation window . . . . . . . . . . . .
4-17: Information window . . . . . . . . . . . . . . . . . . . . . . . .
4-18: Audit Inconsistency List window . . . . . . . . . . . . . . . . . .
4-19: BSS Binary congurations window . . . . . . . . . . . . . . . . .
4-20: Information window . . . . . . . . . . . . . . . . . . . . . . . .
4-21: Binary Database error and warnings window. . . . . . . . . . . .
4-22: Ofine MIB Database Operations window . . . . . . . . . . . . .
4-23: Ofine MIB Verify Operation Monitor window . . . . . . . . . . .
4-24: Binary Database error and warnings window. . . . . . . . . . . .
4-25: Ofine MIB Save Operation Monitor window . . . . . . . . . . . .
4-26: Delete network Conrmation window . . . . . . . . . . . . . . .
4-27: Deleting a BSS or RXCDR - Conrmation window . . . . . . . . .
4-28: Admin Options window . . . . . . . . . . . . . . . . . . . . . . .
4-29: Audit Scheduler window . . . . . . . . . . . . . . . . . . . . . .
xii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-75
3-78
3-86
3-90
3-90
3-92
3-93
3-94
3-96
3-99
3-100
3-101
3-105
3-106
3-106
3-107
3-110
3-112
3-117
3-118
3-120
3-121
3-122
3-124
3-125
3-130
3-131
3-132
3-135
4-7
4-7
4-10
4-11
4-11
4-12
4-13
4-13
4-17
4-19
4-21
4-24
4-28
4-29
4-31
4-32
4-33
4-36
4-40
4-41
4-44
4-47
4-48
4-49
4-51
4-54
4-58
4-61
4-62
68P02900W22-R
GMR-02
Mar 2008
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
4-30: auSchedule Detailed View <Create> window . .

4-31: Audit Scheduler window . . . . . . . . . . . . .
4-32: Audit Logs window . . . . . . . . . . . . . . . .
4-33: Audit Logs abort conrmation window . . . . . .
4-34: Audit Log Management window in Edit mode . .
4-35: Reload Conrmation window . . . . . . . . . . .
4-36: Information window . . . . . . . . . . . . . . .
4-37: Compress from the OLM Network Congurations
4-38: Conrmation window. . . . . . . . . . . . . . .
4-39: Reinitialize DataBase - Conrmation window. . .
5-1: Country Admin in use conrmation window . . . .
5-2: The xcadm GUI . . . . . . . . . . . . . . . . . .
6-1: Non-collocated BSS hierarchy . . . . . . . . . . .
6-2: RXCDR Hierarchy . . . . . . . . . . . . . . . . .
68P02900W22-R
Mar 2008
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
window
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-63
4-66
4-69
4-70
4-74
4-76
4-78
4-80
4-85
4-86
5-37
5-37
6-3
6-4
xiii
GMR-02
List of Figures
xiv
68P02900W22-R
GMR-02
Mar 2008
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1-1: Supported platforms in GSR8 . . . . . . . . . . . .

3-1: Main menu options . . . . . . . . . . . . . . . . .
3-2: Function - MCDF table relationships . . . . . . . .
3-3: Revgen window le menu options. . . . . . . . . .
3-4: Revgen window le menu options. . . . . . . . . .
3-5: Table Controller - menu bar File and Select options.
3-6: File status icons. . . . . . . . . . . . . . . . . . .
3-7: File menu options . . . . . . . . . . . . . . . . . .
3-8: Printer setup - menu buttons . . . . . . . . . . . .
3-9: Printer setup - data elds . . . . . . . . . . . . . .
3-10: Printer setup - action buttons . . . . . . . . . . .
3-11: Edit menu options . . . . . . . . . . . . . . . . .
3-12: Fill cells - data elds . . . . . . . . . . . . . . . .
3-13: Fill cells - options . . . . . . . . . . . . . . . . .
3-14: Fill cells - action buttons. . . . . . . . . . . . . .
3-15: Format menu options . . . . . . . . . . . . . . .
3-16: Find window - enable buttons . . . . . . . . . . .
3-17: Action button denitions. . . . . . . . . . . . . .
3-18: Goto Cell - data elds . . . . . . . . . . . . . . .
3-19: Goto Cell - action buttons . . . . . . . . . . . . .
3-20: Replace window - data elds. . . . . . . . . . . .
3-21: Replace window - enable buttons . . . . . . . . .
3-22: Replace window - option buttons . . . . . . . . .
3-23: Replace window - actions . . . . . . . . . . . . .
3-24: Hot keys for MCDF . . . . . . . . . . . . . . . .
3-25: Upgrader - list boxes . . . . . . . . . . . . . . .
3-26: Upgrader - action buttons . . . . . . . . . . . . .
4-1: Administrative tasks and user types . . . . . . . .
4-2: Reported inconsistencies or errors . . . . . . . . .
4-3: Realign a network - cases . . . . . . . . . . . . . .
4-4: OLM fails to start . . . . . . . . . . . . . . . . . .
4-5: Database Errors . . . . . . . . . . . . . . . . . .
4-6: General operating errors . . . . . . . . . . . . . .
4-7: Specic operation error . . . . . . . . . . . . . . .
4-8: Importing NE software errors. . . . . . . . . . . .
5-1: Command line tools . . . . . . . . . . . . . . . . .
5-2: Command line options (ca command) . . . . . . . .
5-3: Command line options (auto_compile command) .
5-4: Command line options (del command) . . . . . . .
5-5: Command line options (lter command) . . . . . .
5-6: Valid le names . . . . . . . . . . . . . . . . . . .
5-7: Command line options (gcmd command) . . . . . .
5-8: Command Line options (lock_adm command) . . .
5-9: Command line options (revgen command) . . . . .
5-10: Command line options (auto_revgen command) .
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-15
3-9
3-46
3-66
3-66
3-79
3-87
3-89
3-93
3-93
3-94
3-96
3-97
3-97
3-97
3-98
3-99
3-99
3-100
3-100
3-102
3-102
3-102
3-102
3-103
3-123
3-123
4-4
4-71
4-77
4-81
4-82
4-83
4-84
4-84
5-2
5-5
5-10
5-15
5-17
5-18
5-20
5-23
5-25
5-28
xv
GMR-02
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
5-11: Command line options (tp command) . . . . . . .

5-12: Command line options (upg command) . . . . . .
5-13: Command line options (auto_upgrade command).
5-14: Action buttons denitions . . . . . . . . . . . . .
6-1: BSS specic table . . . . . . . . . . . . . . . . . .
6-2: Valid Frequency Blocks . . . . . . . . . . . . . . .
6-3: BTS specic table . . . . . . . . . . . . . . . . . .
6-4: Cabinet table . . . . . . . . . . . . . . . . . . . .
6-5: Frequency Types . . . . . . . . . . . . . . . . . .
6-6: Option dependencies . . . . . . . . . . . . . . . .
6-7: Hardware table . . . . . . . . . . . . . . . . . . .
6-8: Generics table . . . . . . . . . . . . . . . . . . .
6-9: Generics table - elements . . . . . . . . . . . . . .
6-10: Timer table . . . . . . . . . . . . . . . . . . . .
6-11: Timer table - elements . . . . . . . . . . . . . . .
6-12: Modify Value table . . . . . . . . . . . . . . . . .
6-13: Circuit table . . . . . . . . . . . . . . . . . . . .
6-14: Channel table . . . . . . . . . . . . . . . . . . .
6-15: Links table . . . . . . . . . . . . . . . . . . . . .
6-16: Paths table. . . . . . . . . . . . . . . . . . . . .
6-17: LAPD table . . . . . . . . . . . . . . . . . . . .
6-18: Cell table . . . . . . . . . . . . . . . . . . . . .
6-19: Statistics table . . . . . . . . . . . . . . . . . . .
6-20: Statistics table - elements . . . . . . . . . . . . .
6-21: Specics table . . . . . . . . . . . . . . . . . . .
6-22: Specics table - elements . . . . . . . . . . . . . .
6-23: RTF table . . . . . . . . . . . . . . . . . . . . .
6-24: Range and values for rtf_ds0_count . . . . . . . .
6-25: DRI table . . . . . . . . . . . . . . . . . . . . .
6-26: Algorithm data table . . . . . . . . . . . . . . . .
6-27: Neighbor table. . . . . . . . . . . . . . . . . . .
6-28: Throttles table . . . . . . . . . . . . . . . . . . .
6-29: EAS table . . . . . . . . . . . . . . . . . . . . .
6-30: Daughter table. . . . . . . . . . . . . . . . . . .
6-31: PIX table. . . . . . . . . . . . . . . . . . . . . .
6-32: KSW table . . . . . . . . . . . . . . . . . . . . .
6-33: NSVC table . . . . . . . . . . . . . . . . . . . .
6-34: Hop table . . . . . . . . . . . . . . . . . . . . .
6-35: ACS table . . . . . . . . . . . . . . . . . . . . .
6-36: Test Neighbor table . . . . . . . . . . . . . . . .
xvi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-30
5-31
5-34
5-39
6-5
6-8
6-9
6-12
6-14
6-14
6-15
6-26
6-27
6-46
6-46
6-52
6-55
6-58
6-60
6-63
6-65
6-67
6-78
6-79
6-109
6-111
6-155
6-160
6-161
6-165
6-168
6-175
6-176
6-177
6-178
6-179
6-181
6-182
6-187
6-195
68P02900W22-R
GMR-02
Mar 2008
About
This
Manual
What is covered in this manual?

The DataGen product provides the user with the capabilities for performing ofine conguration
management of Motorola GSM network entities (NEs). It is a collection of software tools used
to produce, edit, and update BSS databases.
The Ofine MIB (OLM) can create new networks and visualize and validate networks before
deployment into a live network. It has a common User Interface (UI) with the online Operations
and Maintenance Centre (OMC). BSS binary les are used to create the network which is
displayed in the hierarchical structure called the Navigation Tree.
Chapter 1 Overview of DataGen, provides the user with the capabilities for performing ofine
conguration management of Motorola GSM network entities (NEs).
Chapter 2 User and Group management using the usertool, contains information on user and
group management using the OMC usertool. In addition, information is also available in the
following manuals:
DataGen/OLM Clean Install Guide provides information about installation procedures.
DataGen/OLM Upgrade and Migration Guide provides information about upgrade and
migration procedures.
Both guides are included in the manual Software Release Notes: DataGen (68P02900W76).
Chapter 3 Operating DataGen, describes the procedures used for operating DataGen and its
associated administrative tools.
Chapter 4 Operating the Ofine MIB, describes the procedures used for operating the Ofine
MIB.
Information on performing Cell Xchange and Network Expansion from the Ofine MIB is
provided in the manual Installation Conguration: GSM System Conguration (68P02901W17)
from GSR7.
Chapter 5 Command line tools, provides information on Command line tools.
Chapter 6 MCDF tables, provides description on Motorola Customer Data Format (MCDF)
tables.
For detailed information about the ranges, default values and dependencies of the parameters
in the MCDF tables, refer to the manual Technical Description: BSS Command Reference
(68P02901W23).
Users should pay particular attention to any cautions given in this manual and follow the
instructions exactly. Failure to do so could result in problems running the software.
68P02900W22-R
Mar 2008
GMR-02
Revision history
Revision history
The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Table 1 Manual version history

Issue
Date of issue
Remarks
Nov 2003
GSM Software Release 7
Sep 2004
GSM Software Release 7 Half-Rate
Nov 2006
GSM Software Release 8 GMR-02
Mar 2008
GSM Software Release 8 FP
Resolution of service requests

The following Service Requests are resolved in this document:
Table 2
Service requests resolved in this manual

Remarks
Service Request
CMBP Number
2003333
N/A
Updated the default values of remote_loss_daily

and remote_loss_hourly in the Generics table.
2104801
N/A
The download information for the option

object les for the BSS Software is updated in
Chapter 3 Operating DataGen.
Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:
Table 3
CDCNs incorporated in this manual
CN Date
CN Number
Title
N/A
N/A
N/A
68P02900W22-R
GMR-02
Mar 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02900W22-R
Mar 2008
GMR-02
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences

Special key sequences are represented as follows:
CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or
CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02900W22-R
GMR-02
Mar 2008
Contacting Motorola
Contacting Motorola
Motorola appreciates feedback from the users of our documents.
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Ofce.
Questions and comments

Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number with the error
A detailed description of the error and if possible the proposed solution
68P02900W22-R
Mar 2008
GMR-02
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator congures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
condentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specic recommendations regarding security practices.
The implementation of these recommendations and nal responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Ofce.
68P02900W22-R
GMR-02
Mar 2008
Warnings, cautions, and notes
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
68P02900W22-R
Mar 2008
GMR-02
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment:
The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Power down or unplug the equipment before servicing.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic elds (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic elds) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02900W22-R
GMR-02
Mar 2008
Caring for the environment
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Ofce.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landll sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landll sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02900W22-R
Mar 2008
GMR-02
CMM labeling and disclosure table
CMM labeling and disclosure table
The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identied in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identied in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
eld-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10
68P02900W22-R
GMR-02
Mar 2008
Motorola document set
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Ofce or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner denitions

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02900W22-R
Mar 2008
11
GMR-02
Data encryption
12
68P02900W22-R
GMR-02
Mar 2008
Chapter
1
Overview of DataGen
68P02900W22-R
Mar 2008
1-1
GMR-02
Overview of DataGen
Overview of DataGen
Introduction to DataGen and the Ofine MIB

The DataGen tool provides the user with the capabilities for performing ofine conguration
management of Motorola GSM network entities (NEs). It comprises of a collection of software
tools used to produce, edit, and update BSS databases. The database is a binary le containing
details specic to a BSS and its conguration.
DataGen is a exible tool that reduces the time and effort required to produce accurate BSS
databases. The concept is that of front ofce or back ofce data management system. The
OMC (front ofce) incorporates the live data on the GSM network entities, and the back ofce
(DataGen) incorporates the ofine data. Changes to the network can be carried out and veried
through the Ofine MIB (OLM) before deployment to the network.
Overview of DataGen
DataGen converts BSS binary database objects into a specic database format (Informix). The
Informix database contains the following information:
A representation of the information required to create a SYSGEN script for all supported
Base Station System (BSS) Releases.
Included in this information are details relating to the syntax, parameters, and their
associated range values for the Man Machine Interface (MMI) commands in the SYSGEN
script.
Conguration information for a specic BSS area. These areas are identied by
Country/Network, Name, Software Release, and Conguration Number. The Conguration
Number allows multiple versions to exist within the database.
DataGen functionality
DataGen consists of a suite of tools that operate on BSS databases (refer to Figure 1-1).
Figure 1-1 DataGen GUI
1-2
68P02900W22-R
GMR-02
Mar 2008
Overview of the Ofine MIB
The following functions can be performed using these tools:
Upload BSS parameter data from an operational network (using the OMC-R).
Dene global defaults.
Modify parameters across part or all of a network.
Manage software loads.
Generate SYSGEN databases.
Generate commands for the Operations and Maintenance Centre (OMC) to apply changes.
Describe a cellular network in both physical and logical structure.

The Ofine MIB (OLM) can create new networks, visualize, and validate networks before
deployment into a live network. It has a common User Interface with the online OMC. The OLM
front panel is accessed from the DataGen main menu (refer to Figure 1-2).
BSS binary les are used to create the network which is displayed as a tree-like representation
called the Navigation Tree. It is possible to update multiple BSS binary les simultaneously, for
example, by propagating neighbor changes from one BSS binary le to another.
Figure 1-2 Ofine MIB - Front Panel
68P02900W22-R
1-3
GMR-02
Mar 2008
Ofine MIB functionality
Ofine MIB functionality

The Ofine MIB enables users to perform the following tasks:
Provide a graphical representation of a network.
Edit conguration management parameters.
Propagate cell and neighbor parameters.
Interface to Radio Frequency (RF) planning tools.
DataGen/Ofine MIB integration

DataGen and the Ofine MIB work together. The following functions can be performed (refer
to Figure 1-3):
Import binary database object les from the OMC.
Carry out upgrade using DataGen.
Import multiple binary object les into the OLM and thus carry out the radio frequency
planning.
1-4
68P02900W22-R
GMR-02
Mar 2008
Figure 1-3
The DataGen and OLM platform
DataGen/Ofine MIB functions

Upgrader
Input
Ta ble control
MCDF
tables
DataGen Data Store
BSS
database object file
from OMC
Revgen
MMI generator
(Informix)
Output
Delete
Sysgen
script
Compiler
Copy
Admin
Difference Reporter
Netwo rk Topology
Report
Display
Cage layout
Display
BSS
database object file
from OMC
Audit
Database Operations
OLM
Help Find
OMC-R GUI
Admin
ti-GSM-DataGen_Of fline MIB functions-00003-ai-sw

DataGen and the OLM is implemented on either a Sun Netra 440 platform or the 'Flexible
Platform'. For more information about the supported platforms, refer to Supported platforms
on page 1-15. DataGen and the OLM use many of the same software tools as the OMC-R, thus
maximizing compatibility between the two systems. DataGen should be deployed on a shared
Ethernet LAN with the OMC-R to facilitate data interchange.
68P02900W22-R
1-5
GMR-02
Mar 2008
Hardware
DataGen and the OLM is congured to run on a standalone processor with its own disk storage,
tape drive, and DVD drive. The system uses Sun UltraSPARC processor; CPU speed and RAM
are subject to change.
Standard peripherals include a DAT tape drive, a DVD-ROM drive and monitor. The standard
system is congured for LAN Ethernet support.
Software
DataGen and OLM are built around the industry-standard INFORMIX online database engine.
This runs on top of the Solaris UNIX Operating System. The user interface uses the OSF/Motif
windowing system. DataGen software is distributed on DVD-ROM together with all third party
products.
Figure 1-4 DataGen in a GSM environment
NMC
Da ta Ge n
OMC-R
OS I
Loca l Are a Ne twork
S ys te m
S e rve r
GUI S e rve r
BSC
OS I Proce s s or
Ope ra tor
Works ta tions
X.25
BSC
BSC
BSC
ti-GS M-Da ta Ge n_in_GS M_e nvironme nt-0004-a i-s w
1-6
68P02900W22-R
GMR-02
Mar 2008
DataGen database structure
DataGen database structure
Introduction
DataGen is a collection of software tools used to produce, edit, and update BSS databases.
BSS database
A BSS database contains many parameters which describe the conguration of the BSS
hardware and software. A BSS database can have two forms, a database script le and a
Conguration Management (CM) database object.
Database script le
A database script le is an ASCII le. The user can read from or write into the database script
le. It can be produced manually by entering the text into an ASCII le. This process is slow
and is likely to introduce errors. The le must be formatted precisely to contain the correct
number of line feeds and spaces. DataGen provides a faster, more accurate way to produce a
Database Script File.
Conguration Management (CM) database object

A CM Database Object (Binary Object) is the compiled database script le and cannot be read or
edited. The CM Database Object is produced by downloading a database script le into a BSC.
This object can then be uploaded and stored on a disk or at the OMC.
DataGen and the OMC

The code used by the BSS to convert the SYSGEN script into a binary object is ported to the
DataGen platform and generates a binary object which can be then downloaded to the OMC
(refer to Figure 1-5).
For DataGen applications which are on the same Ethernet network as an OMC, the transfer of
the new binary object is initiated from the OMC using the load_db script. It is also possible for
DataGen to access the binary objects which are stored on the OMC. This allows binary objects
which are uploaded, to be imported into DataGen using Revgen.
68P02900W22-R
1-7
GMR-02
Mar 2008
DataGen and the OMC
Figure 1-5 DataGen-OMC integration

Datagen Platform
OMC Platform
GUI
GUI
DATAGEN
CM
RDB
LOAD
MANAGEMENT
MIB
Topology
BSS MMI SCRIPT
DATABASE
BSS CM
DB Root
BSS
Databases
Binary
object
OLM
cobh
bss_cork
BINARY
Binary
objects
bss_cobh
GENERATION
CellXchange
DATAGEN SYSTEM PROCESSOR

PLATFORM
OMC SYSTEM PROCESSOR

PLATFORM
ti-GS M-Da ta Ge n-OMC inte gra tion-00005-a i-s w
1-8
68P02900W22-R
GMR-02
Mar 2008
Loading network information into DataGen
Loading network information into DataGen
Introduction to loading network information

The process for loading network information into DataGen is illustrated in Figure 1-6. To load
network information and import existing input les into DataGen, perform the following steps:
Gather or create input les.
Start up DataGen.
Create a new BSS area.
Import input les into the new BSS area.
Import binary object les into the Ofine MIB.
68P02900W22-R
1-9
GMR-02
Mar 2008
Gathering network information
Figure 1-6 Loading network information into DataGen
Hardware
Configuration
Software
Configuration
NETWORK
Input
Files
DATAGEN
Start-up
DataGen
Create
new BSS
Area
Import
Input Files
ti-GS M-Loa ding_ne twork_informa tion_into_Da ta Ge n-00006-a i-s w
Gathering network information

The rst task is to gather network conguration information for the network. This information
is then used to produce the input les which can be read by DataGen. The input les can be
entered directly into either of the two computer-based tools:
The DataGen Table Controller
Files conforming to the Motorola Customer Data File (MCDF) format
Both methods involve entering the information into a computer using a custom designed
software package.
1-10
68P02900W22-R
GMR-02
Mar 2008
The DataGen Directory Structure (DDS)
Figure 1-7 shows a graphical representation of the two methods for creating MCDF les.
Figure 1-7 Creating MCDF les
DataGen
Network
Information
MCDF Files
MCDF
format
ti-GS M-Cre a ting_MCDF_file s -00007-a i-s w
The DataGen Directory Structure (DDS)

All DataGen input and output les are stored in an area called the DataGen Directory Structure
(DDS). The starting point of the DDS is the directory dg. The directories below dg are then
named according to the country and BSS area being stored.
A further (lower) directory level identies the conguration number for the BSS area. This
allows the storage of more than one set of database information for each BSS area. The next
level down contains the DataGen input and output le directories. An example of the DataGen
directory structure is shown in Figure 1-8.
CAUTION
Directories within the DataGen Directory Structure should not be created manually.
DataGen creates the directories automatically, thus ensuring that there are no syntax
errors in the directory names.
68P02900W22-R
1-11
GMR-02
Mar 2008
Main structure of the DDS
Figure 1-8 DataGen directory structure

dg
Belgium
Norway
UK
Manchester
London
conf0
Qatar
Birmingham
conf1
Output File
Directories
Input File
Directories
command
MCDF
002
UPG
ti-GS M-Da ta Ge n_dire ctory_s tructure s -00008-a i-s w
Main structure of the DDS

The DDS is structured as follows:
/usr/gsm/DataGen/dg/<country>/<bss>/conf<N>
Where
Is
country
replaced by the name of the country
bss
replaced by the name of the base

site
replaced by the conguration
For example:
$HOME/dg/UK/testbss/conf0
All directories must be created by DataGen for each BSS area. Users are advised to leave the
directory creation to DataGen in order to avoid problems with capitalization.
1-12
68P02900W22-R
GMR-02
Mar 2008
Sub structure
Sub structure
Inside the conf<N> directory there are a number of other directories as follows:
/command contains SYSGEN scripts created by DataGen.
/002 contains les for use with Revgen.
/UPG contains les created by Upgrader.
/MCDF contains les converted by MCDF, which can be edited.
The Ofine MIB directory structure

The directories below the OLM are created when a user creates a new network conguration in
the Ofine MIB, as in Figure 1-9. When a BSS or RXCDR is created, a copy of the binary object
le in the Conf<N> directory is placed in the network directory (refer to Figure 1-8).
Figure 1-9
Example of Ofine MIB directory structure
olm
Network 1
Network 2
Network 3
Network 4
ti-GS M-Exa mple _Offline _MIB_dire ctory_s tructure -00009-a i-s w
The Ofine MIB le structure

Each network conguration can contain up to 256 binary object (.002) les. An example of
Ofine MIB network structure is displayed in Figure 1-10.
Figure 1-10 Example of Ofine MIB le structure

Network 2
London .002
Manchester .002
Birmingham .002
Liverpool .002
ti-GS M-Exa mple _Offline _MIB_file _s tructure -00010-a i-s w
68P02900W22-R
1-13
GMR-02
Mar 2008

The Ofine MIB directory structure is organized as follows:
/usr/gsm/DataGen/olm/<network_configuration>
Where
Is
network_conguration
replaced by the network conguration name,

which contains .002 les.
1-14
68P02900W22-R
GMR-02
Mar 2008
Supported platforms
Supported platforms
Overview of supported platforms

DataGen is congured to run as a standalone processor with its own disk storage, tape drive,
and DVD-ROM drive. Table 1-1 lists the hardware congurations supported.
Table 1-1
Supported platforms in GSR8
Processor
Internal mirrored disks
Netra 440
(2 X 72 Gb) X 2
NOTE
The same conguration is used for Clean Install and Upgrade platforms.
DataGen GSR8 is supported on a new 'Flexible Platform'. Customers can use

any Sun UltraSPARC machine, provided that it meets a minimum specication
set by Motorola. For more details, refer to Bulletin number GSM_G_OMCR_056.
68P02900W22-R
Mar 2008
1-15
GMR-02
Overview of supported platforms
1-16
68P02900W22-R
GMR-02
Mar 2008
Chapter
2
User and Group management using the
usertool
68P02900W22-R
Mar 2008
2-1
GMR-02
User and Group management using the usertool
User and Group management using the usertool
{24380}
Introduction to usertool
This chapter describes the procedures to manage users and groups on the DataGen processor
using the usertool utility.
Common Desktop Environment Manager

The Common Desktop Environment (CDE) Manager provides a desktop environment which can
be customized on a per user basis. It reduces window clutter and provides a graphical front
end to the UNIX le system. It provides an industry standard desktop manager and is available
for different SUN workstations. A batch scheduler is also provided which allows the user to
schedule cron jobs from the CDE.
The OMC Admin menu available from the CDE provides a Graphical User Interface (GUI) for
performing routine system administration tasks. It provides access from the front panel of the
desktop to the different SUN administration tools that support Solaris 8.
Usertool - Overview
Usertool is a utility that is used for managing users and groups on the DataGen processor.
Usertool can be accessed either from the command line (/var/install/bin/usertool) or from
the OMC Admin menu available in the Common Desktop Environment (CDE).
Usertool can be used to perform the following management tasks:
Manage user accounts
Manage groups
Procedure list
This chapter details the following procedures:
DataGen User management using the usertool on page 2-3
DataGen Group management using the usertool on page 2-13
2-2
68P02900W22-R
GMR-02
Mar 2008
DataGen User management using the usertool
DataGen User management using the usertool
{24380}
Introduction to user management

Usertool is a utility that enables the management of user accounts on a local system. A user
account enables a user to log on to a system and provides access to a home directory.
Usertool can be used to perform the following user management tasks:
Add a new user account
Modify a user account
Delete a user account
Copy a user account to a new user name
Before assigning the users to specic groups, ensure that the groups rst exist. Before adding
user accounts, use usertool to add any groups to which users will be assigned. Refer to DataGen
Group management using the usertool on page 2-13 for more information.
User management parameters

The following parameters are available under User Administration in Usertool:
User Name
This species the login name the operating system uses to identify an individual user. A
user name must be a unique name, composed of lowercase alphabetical characters (a-z) or
digits (0-9). The rst character of a user name must be a letter.
Full Name
This can be any text string. It is generally a short description of the login, and is used as
the eld for the user's full name.
NOTE
The users full name is displayed on the OLM GUI.
Home Directory
The home directory of the user. It defaults to /home/<username>, where <username>
is the login name, for example: /home/bloggs1.
68P02900W22-R
2-3
GMR-02
Mar 2008
User administration utility
User ID (UID)
This species the unique number by which the operating system can identify a user.
The maximum value is 2147483647. It is recommended that UIDs be kept below 60000
to minimize the amount of software incompatibilities. Reserved UIDs include 60001
(nobody) and 65534 (nobody4).
Group
This parameter species the primary group to which the user belongs. A group ID
number or group name can be specied. Group 110 (omc) is the default primary group
for DataGen users.
Secondary Groups
This optional parameter species one or more groups to which the user also belongs. A
group ID number or group name can be specied. If more than one group is specied,
separate them from the other group(s) with commas.
Account Locked
If the account is locked then the user will not be able to log in until the account is unlocked
by the System Administrator.
Change Password
The parameter forces the user to change the password on the next login. This occurs only
once. Having chosen a new password, the user is not prompted for password change on
subsequent logins.
Shell
This is the full path name of the programme used as the user's shell on login. It is
recommended that the C-shell (/bin/csh) is used for DataGen users.

Procedure 2-1 Starting the Usertool
Usertool is the user administration utility. Usertool can be started from the
OMC Admin menu in the Common Desktop Environment (CDE) or from
the command line.
To start the usertool from the Common Desktop Environment (CDE), log on
to the CDE environment with user name: root.
Continued
2-4
68P02900W22-R
GMR-02
Mar 2008
Procedure 2-1 Starting the Usertool (Continued)

3
From the front panel of the CDE Desktop (Figure 2-1), click the arrow on the
usertool icon (Figure 2-2) to open the OMC Admin drawer (Figure 2-3).
Figure 2-1
CDE desktop - front panel
Figure 2-2 The usertool icon
Figure 2-3 CDE desktop front panel with open OMC Admin drawer
The OMC Admin drawer provides access to administration applications as

in Figure 2-3. To start usertool, click on the usertool icon. The usertool
menu is launched in a separate window as in Figure 2-4. Click the arrow
again to close the OMC Admin drawer.
Continued
68P02900W22-R
2-5
GMR-02
Mar 2008
Procedure 2-1
5
Starting the Usertool (Continued)
To start usertool from the command line run the following command:
/var/install/bin/usertool. The usertool menu is displayed as in
Figure 2-4.
Figure 2-4 Usertool menu window
The following user operations and group operations are available:
Add user
Modify user
Rename user
Delete user
Add group
Modify group
Rename group
Delete group
2-6
68P02900W22-R
GMR-02
Mar 2008

To add a new user to a group, perform the following procedure.
Procedure 2-2
1
Start the usertool utility using the steps in User administration

utility on page 2-4. The usertool menu is displayed as in Figure 2-4.
Administration utility
---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Add User option by entering its corresponding number (1).
The User Administration window is displayed as follows:
--------------------------Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
On this window, one eld is highlighted with a bar which can be moved with
the cursor keys. The highlighted eld can be modied by typing or deleting
as required. A help message is provided for each eld. If any of the elds is
in conict, a message to that effect is displayed.
NOTE
Refer to the section User management parameters on page 2-3
for more information about data elds.
Continued
68P02900W22-R
2-7
GMR-02
Mar 2008
Procedure 2-2
3
Add a new user account (Continued)
Enter the required data into the Username eld. Many of the other elds are
automatically lled out with the default values for DataGen users as in the
following example:
--------------------------Username : bloggs1
Full Name :
Home directory : /home/bloggs1
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
Modify the Full Name, Home Directory, UID, Group, and Shell as
appropriate. It is recommended that the default values (where provided) are
accepted when using usertool to create DataGen user accounts.
For DataGen users, ensure that the Group is set to OMC.
For DataGen users, ensure that the Shell is set to /bin/csh.
Select Done to save changes and create the new user.
Enter required data into Path and click OK.

The List of user accounts displayed in the main window is updated to include
the new user account. A prompt is displayed requiring a password be chosen
for the new user.
Choose and conrm the password for the new user account. This password
must be communicated to the user to allow the new user to log in. The
new user will have the appropriate environment settings automatically
congured for DataGen. The usertool utility exits automatically upon
completion of the requested operation.
2-8
68P02900W22-R
GMR-02
Mar 2008

To modify a user account, perform the following procedure.
Procedure 2-3
Start the Usertool utility using the steps in User administration

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Modify User option by entering its corresponding number (2).
--------------------------Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
In this window, one eld is highlighted with a bar which can be moved with
as required. A help message is provided for each eld. If any of the elds
are in conict, a message to that effect will be displayed.
NOTE
Continued
68P02900W22-R
2-9
GMR-02
Mar 2008
Rename a user account
Procedure 2-3
3
Modify a user account (Continued)
Enter the user name to be modied into the Username eld, the other
elds are automatically lled with the current settings for the user.
--------------------------Username : bloggs1
Full Name : Joe Bloggs
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
Highlight each data eld to be modied and enter the new data.
Select Done to save changes and modify the user account. The usertool utility
exits automatically upon completion of the requested operation.

To rename a user account, that is, to change the username or login associated with the user ID,
perform the following procedure.
Procedure 2-4
Start the usertool utility using the steps in User administration utility on
page 2-4. The usertool menu is displayed as in Figure 2-4.
---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Rename user option by entering its corresponding number (3).
When prompted, enter the existing username of the account.
When prompted, enter the new username of the account. The usertool utility
2-10
68P02900W22-R
GMR-02
Mar 2008

To delete a user account, perform the following steps.
CAUTION
Deleting a user account permanently removes the home directory of the user and all
les contained within it.
Procedure 2-5 Delete a user account

1

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Delete User option by entering its corresponding number (4).
--------------------------Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
are in conict, a message to that effect will be displayed.
Continued
68P02900W22-R
2-11
GMR-02
Mar 2008
Procedure 2-5 Delete a user account (Continued)
NOTE
3
Enter the user name to be deleted into the Username eld, the other
elds are automatically lled with the current settings for the user.
--------------------------Username : bloggs1
Full Name : Joe Bloggs
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
Select Done to delete the user account.
Select Done to save changes and modify the user account.

The usertool utility exits automatically upon completion of the requested
operation.
2-12
68P02900W22-R
GMR-02
Mar 2008
DataGen Group management using the usertool
DataGen Group management using the usertool
{24380}
Introduction to group management

Usertool is a utility that enables the management of groups on the local system. Usertool is
used to perform the following group management tasks:
Add a new group
Modify a group
Rename a group
Delete a group
Group management parameters

The following parameters are available under Group Administration in usertool:
Group Name
Group Name species a name used to identify a user group. A group name contains
lowercase alphabetical characters (a-z) and digits (0-9). A group name can be 1 to
8 characters long.
Group ID (GID)
Group ID species a group identication number used to identify a user's primary group.
The maximum value is 2147483647. To minimize the amount of software incompatibilities,
GIDs should be kept below 60000. Reserved GIDs include 60002 (noaccess) and 65534
(nogroup).
Group Administration Utility

The Group Administration Utility is usertool, which is the same utility used for user
administration. Usertool can be started from the OMC Admin menu in the Common Desktop
Environment (CDE) or from the command line. Refer to the section User administration utility
on page 2-4 which contains detailed instructions for starting the usertool utility.
Add a group
To add a new group, perform the following procedure.
68P02900W22-R
2-13
GMR-02
Mar 2008
Add a group
Procedure 2-6 Add a group

1
Start the Usertool utility using the steps in User administration

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Add Group option by entering the corresponding number (5).
The Group Administration window is displayed as follows:
Group administration utility
---------------------------Group :
GID : 0
Done
Cancel
are in conict, a message to that effect is displayed.
NOTE
Refer to the section Group management parameters on page 2-13
3
Enter the required group name into the Group eld:

---------------------------Group : group1
GID : 500
Done
Cancel
Modify the GID as appropriate. An unused Group ID is automatically

inserted into the GID eld. This can be changed, if desired.
Select Done to save changes and create the new group. The usertool utility
2-14
68P02900W22-R
GMR-02
Mar 2008
Modify group information
Modify group information

To modify group information, perform the following procedure.
Procedure 2-7 Modify group information

1

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Modify Group option by entering the corresponding number (6).
---------------------------Group :
GID : 0
Done
Cancel
NOTE
3
Enter the name of the group to be modied in the Group eld. The GID data
eld displays the current settings for the group, by default as given in the
example below.
---------------------------Group : group1
GID : 500
Done
Cancel
Highlight the GID data eld and enter the new data.
Select Done to save the changes and modify the group. The usertool utility
68P02900W22-R
2-15
GMR-02
Mar 2008
Rename a group
Rename a group
To rename a group, perform the following procedure.
Procedure 2-8 Rename a group

1

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Rename Group option by entering the corresponding number (7).
When prompted, enter the existing Groupname.
When prompted, enter the new Groupname.
Select Done to save the changes and rename the group. The usertool utility
2-16
68P02900W22-R
GMR-02
Mar 2008
Delete a group
Delete a group
To delete a group, perform the following procedure.
Procedure 2-9 Delete a group

1

---------------------1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Select the Delete group option by entering the corresponding number.

---------------------------Group :
GID : 0
Done
Cancel
NOTE
3
Enter the name of the group to be deleted in the Group eld.

The GID data eld displays the current settings for the group,
by default as given in the example below.
---------------------------Group : group1
GID : 500
Done
Cancel
Select Done to delete the group. The usertool utility exits automatically
upon completion of the requested operation.
68P02900W22-R
Mar 2008
2-17
GMR-02
Delete a group
2-18
68P02900W22-R
GMR-02
Mar 2008
Chapter
3
Operating DataGen
68P02900W22-R
Mar 2008
3-1
GMR-02
Overview of operating DataGen
Overview of operating DataGen
About this chapter

This chapter provides an introduction to the DataGen menu structure and a detailed view
of the operational sequences involved in running DataGen. It should be used in conjunction
with Chapter 6 MCDF tables.
The information in this chapter is aimed primarily at new users of DataGen and the routines are
set out in the order in which they would normally be performed.
The functionality of DataGen revolves around an Informix database. To create this database
from scratch would be an unnecessary waste of existing resources. Therefore, it is assumed
that the user will work with an existing database and perform a variety of DataGen functions to
generate a working database.
If the user is successful in editing or creating new information in the database, then the
database should compile successfully and create a viable BSS script.
Procedures for operating DataGen

To operate the DataGen, perform the listed procedures in the following order:
Importing existing CM database objects on page 3-25.
Converting a CM database object le to a script le on page 3-65 - Using Revgen.
Generating a database script le on page 3-70 - Using the MMI tool.
Viewing and editing DataGen les on page 3-76 - Using the Service Window, Table
Controller, Generic Table Editor, and Topology viewer.
Converting a database script le to a CM database object le on page 3-111 - Using the

Binary Object Compiler.
3-2
68P02900W22-R
GMR-02
Mar 2008
Procedures for operating DataGen
Other procedures for operating DataGen can be performed as required, including:
Administration tasks on page 3-11
Creating a BSS area on page 3-34
Opening a BSS area on page 3-39
Copying a BSS area on page 3-41
Deleting a BSS area on page 3-43
Conguring BSS area(s) on page 3-45
Difference Reporter on page 3-117
Upgrader on page 3-122
Batch processing of binary object les on page 3-129
For information on operating the ofine MIB, refer to Chapter 4 Operating the Ofine MIB.
68P02900W22-R
3-3
GMR-02
Mar 2008
Dening environment variables
Dening environment variables
Overview of environment variables

Environment variables are variables that the shell or any other program can access in order
to get information unique to a specic user. Several environment variables can be created
and used by DataGen.
Certain variables can be set from the DataGen main menu by using the ADMIN - Preferences
option. Refer to Administration tasks on page 3-11 for more details.
NOTE
These standard C shell environment variables must be set up prior to running
DataGen.
HEX or decimal representation

Two environment variables can be set up to allow the users to decide at run time whether
they want HEX or DECIMAL representation.
DG_HEX_CELL_IDS determines in what format GSM cell ids are displayed.
DG_HEX_POINT_CODES determines in what format the elements opc and dpc are
displayed. The format applies to the MMI script and to MCDF.
The variables should be set to yes to display the values in HEX. This can be achieved using the
following commands in the C shell:
setenv DG_HEX_CELL_IDS yes
setenv DG_HEX_POINT_CODES yes
NOTE
These variables can also be set from the DataGen main menu using the ADMIN Preferences option. Refer to Administration tasks on page 3-11 for more details.
3-4
68P02900W22-R
GMR-02
Mar 2008
Version list order
Version list order

DG_VERSION_ORDER determines the ordering of the version list in both the Open and New
BSS dialogue boxes. If this variable is not set, then DataGen displays the list in ascending
order by default. To display the list in descending order, set DG_VERSION_ORDER to YES by
executing the following command in the C shell:
setenv DG_VERSION_ORDER yes
Time slot order equipage

This feature is optional and allows the user greater exibility in the allocation of time slots. If
enabled, RSL and RTF time slots are retained when modifying a binary object le, otherwise,
the default values are applied.
Retain time slot order equipage is enabled, by default. If retaining the order is not required,
then disabling this function gives a signicant performance improvement.
To enable the time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS yes
To disable the time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS no
NOTE
This variable can also be set from the DataGen main menu using the ADMIN Preferences option. Refer to Administration tasks on page 3-11 for more details.
Automate running of Revgen

Revgen converts a Binary Object File into an Informix format. Revgen can be invoked by
selecting the Services option from the Services menu, or by selecting the Revgen button.
To automate the functioning of Revgen from the Service menu or Revgen button, enter the
following command in the C shell:
setenv DG_AUTO_REVGEN yes
To disable the automated functioning of Revgen from the Service menu or Revgen button,
enter the following command in the C shell:
setenv DG_AUTO_REVGEN no
NOTE
This variable can also be set from the DataGen main menu using the ADMIN Preferences option. Refer to Administration tasks on page 3-11 for details.
68P02900W22-R
3-5
GMR-02
Mar 2008
Default le import path
Default le import path

From the Service window, it is possible to import binary object les. The default directory
path is /usr/omc. The variable DG_IMPORT_PATH allows a user dened import path. If the
variable is set and import object is selected, then the DG_IMPORT_PATH is displayed, regardless
of previous paths selected.
To dene an import path, enter the following command in the C shell:
setenv DG_IMPORT_PATH <directory_path>
For example:
setenv DG_IMPORT_PATH /usr/omc/import
NOTE
Default export path

The variable DG_EXPORT_PATH allows binary object les to be exported from the Service
window to an export directory.
To dene an export directory, enter the following command in the C shell:
setenv DG_EXPORT_PATH <directory_path>
For example:
setenv DG_EXPORT_PATH /usr/omc/export
NOTE
3-6
68P02900W22-R
GMR-02
Mar 2008
Dene default text editor
Dene default text editor

From the Service window it is possible to view MMI scripts and compilation logs. The variable
DG_EDITOR allows the user to dene which editor to launch when viewing MMI scripts or
compilation logs.
To dene a text editor, enter the following command in the C shell:
setenv DG_EDITOR <text_editor>
Where
Is
text editor
textedit, vi, or xedit
NOTE
To dene another editor other than the three standard editors, refer to
Generating a database script le on page 3-70.
Override area lock

When a BSS area that is already in use is accessed, a warning message is displayed. This
allows the user to unlock the area or cancel it.
To automatically unlock the locked area without displaying the warning message, enter
the following command:
setenv DG_OVERRIDE_LOCK yes
To return to the default state and present the warning message when accessing a locked
area, enter the following command:
setenv DG_OVERRIDE_LOCK no
NOTE
68P02900W22-R
3-7
GMR-02
Mar 2008
Output all elements in a script
Output all elements in a script

From the Service window, it is possible to generate a database script le by clicking the MMI
button or by selecting the Generate Script option from the Service menu.
By default, certain elements which are set to their default value are not output to the script.
To output all elements, whether default or not, execute the following command:
setenv DG_ALL_CHG_ELEMENT yes
To return to the default state, enter the following command:

setenv DG_ALL_CHG_ELEMENT no
NOTE
Setting the value to Yes may result in compilation failures and should be used
only to view default values.
Display only generic algorithm details in alg.mcd table

The MCDF Algorithm data table (alg.mcd) has hundreds of rows of data for all cells, each cell
specied by the Location Area Code (LAC) and Cell Identier (CI) in the table.
The ALG_TABLE_NEW environment variable is used to display only generic algorithm details
(the most repeating value for a particular algorithm) for cells with no Mobile Country Code
(MCC), Mobile Network Code (MNC), LAC and CI details specied. That is, any cells with
algorithm details which differ from the generic, are listed in the alg.mcd table, with complete
MCC, MNC, LAC, and CI information.
Execute the following command to set this variable:

setenv ALG_TABLE_NEW TRUE
To return to the default state, execute the following command:

unsetenv ALG_TABLE_NEW
3-8
68P02900W22-R
GMR-02
Mar 2008
DataGen - startup and shutdown
DataGen - startup and shutdown
Introduction to startup and shutdown

DataGen has a comprehensive Graphical User Interface (GUI). It is accessed through a main
window which has seven menu options, providing complete DataGen functionality.
This section describes how to start DataGen, access the main window and shut down DataGen.
Startup
Procedure 3-1
Starting the DataGen GUI
To start the DataGen GUI, open an Xterm window and enter the following
command:
DataGen
The DataGen main menu is displayed as in Figure 3-1.
Figure 3-1
DataGen main menu
The following options can be selected from this menu: NEW, OPEN, UPG, COPY, DEL, DIFF,
BATCH, ADMIN, OLM, HELP, and EXIT (refer to Table 3-1).
Table 3-1
Main menu options

To
Select
NEW
Display a window where a new BSS area can be created.
OPEN
Display a window where an existing BSS area can be viewed or

edited.
UPG
Display a window where an existing BSS area can be upgraded

to a later version.
COPY
Display a window where BSS areas can be copied.
Continued
68P02900W22-R
3-9
GMR-02
Mar 2008
Shutdown
Table 3-1 Main menu options (Continued)

To
Select
DEL
Display a window where an existing BSS area can be deleted.
DIFF
Display a window where difference reports between sites and site

elements for BSS areas can be generated.
BATCH
Display a window where multiple binary object les can be

Revgened, upgraded, or compiled.
ADMIN
Display a window where a range of Administration tasks can be

carried out. For example, Country administration.
OLM
Display a window where an Ofine MIB (OLM) can be launched.

RF planning and modications to multiple BSS binary les can
be carried out.
HELP
View the following Help message:
'For DataGen Help please refer to the DataGen manual

supplied,
OLM On-Line help is available through the OLM GUI'
EXIT
Shut down DataGen.
Shutdown
DataGen can be shut down either from an Xterm window or from the main menu as follows:
Xterm
To shut down DataGen from an Xterm window, rst close all DataGen windows. In the Xterm
window from which DataGen was started, execute the following command:
exit
DataGen is then shut down and the main menu window is removed.
Main menu
To shut down DataGen from the main menu, select the EXIT option.
All open DataGen windows, including the main menu, are then removed and DataGen is shut
down.
3-10
68P02900W22-R
GMR-02
Mar 2008
Administration tasks
Administration tasks
Overview of tasks
Following is a list of tasks that can be carried out by selecting the ADMIN option from the
DataGen main menu:
Country Admin
This option can be used to create a new country or network conguration.
Refer to Creating a BSS area on page 3-34 for more details.
Permissions
The DataGen user has a standard set of access permissions. This option allows the user to
set the status to access permitted or access denied.
Defragment
To maximize free disk space, it is advisable to defragment or optimize the DataGen
database.
Logle
Each task carried out within DataGen is monitored and the results are stored in a logle.
This utility displays the logle.
Preferences
Several environment variables can be activated from within the Preferences menu. For
example, the default editor and import path for importing binary object les can be dened.
Options
Once the binary option object les are copied from tape (or downloaded electronically
from the GSM Software Distribution and Licensing Centre) and uncompressed, they can
be installed by using this feature.
NOTE
The following privileges are available for a user logged into the DataGen
processor as omcadmin: Permissions, Defragment, and Options.
68P02900W22-R
3-11
GMR-02
Mar 2008
Changing permissions
Changing permissions
To change or toggle access permissions for a user, perform the following procedure.
Procedure 3-2 Change permissions
Log on to the DataGen processor as omcadmin.
Start DataGen from an Xterm window and select ADMIN from the DataGen
main menu. Refer to DataGen - startup and shutdown on page 3-9 for details.
The Administration menu is displayed as shown in Figure 3-2.
Figure 3-2 Administration menu - omcadmin user
Select the Permissions option. The Permissions window is then displayed

as in Figure 3-3.
Figure 3-3 Permissions window
Enter the Username and click Toggle to grant or withhold permissions.
NOTE
Enter valid users only, such as omcadmin, informix and so on.
Continued
3-12
68P02900W22-R
GMR-02
Mar 2008
Optimizing the database
Procedure 3-2 Change permissions (Continued)

5
A Conrmation window is displayed, as shown in Figure 3-4.
Figure 3-4 Conrm permissions
Click OK to return to the Administration menu.
NOTE
Refer to the section Viewing the log le on page 3-14 for more
details.
Optimizing the database

To defragment or optimize the DataGen database, perform the following procedure.
Procedure 3-3 Optimize the database
main menu. Refer to DataGen - startup and shutdown on page 3-9 for
details. The Administration menu is displayed (refer to Figure 3-5).
Select the Defragment button. A status window is displayed stating:

Defragmenting the database, Please Wait ...
When the defragmentation is complete, a conrmation window is displayed.
Click OK to return the Administration menu.
NOTE
After performing a defragmentation, exit the GUI and then
re-open it to access the previously created areas.
68P02900W22-R
3-13
GMR-02
Mar 2008
Viewing the log le
Viewing the log le

To view the log le, perform the following procedure.
Procedure 3-4 View the log le
Log on to the DataGen processor.
Start DataGen from an Xterm window and select the ADMIN option from
the DataGen main menu.
Select Logle from the Administration menu (refer to Figure 3-5).
Figure 3-5 Administration menu - non-omcadmin user
NOTE
Figure 3-5 displays the default menu for non-omcadmin users.
4
The DataGen logle is displayed, showing a history of all the commands

issued in DataGen. If the logle is open, the progress of a task can be viewed
as it is executed. An example of a logle is displayed in Figure 3-6.
Figure 3-6 Example of a logle
Enter Ctrl+C to exit the logle and return to the Administration menu.
3-14
68P02900W22-R
GMR-02
Mar 2008
Customizing parameters
Customizing parameters
From the Preferences menu, several different parameters can be customized. To view the
preferences available, perform the following procedure.
NOTE
It is not essential to select any of these criteria. If they are not required, simply omit
these steps and DataGen applies default values.
Procedure 3-5 Customizing parameters
main menu. Refer to DataGen - startup and shutdown on page 3-9 for details.
The Administration menu is displayed as shown in Figure 3-5.
Select Preferences from the menu. The Preferences window is displayed

as in Figure 3-7. Several environment variables can be turned on from the
Preferences window for the current session.
Figure 3-7 Preferences window
Continued
68P02900W22-R
3-15
GMR-02
Mar 2008
Installing the Options Object
Procedure 3-5
4
Customizing parameters (Continued)
Click the appropriate option buttons to enable the required environment

variables. Refer to Dening environment variables on page 3-4 for a detailed
description.
NOTE
Retain Timeslot Order equipage is enabled, by default. This
retains RSL and RTF timeslots when modifying the binary le. If
retaining the order is not required, then disable this function to
give a signicant performance improvement.
5
To select which editor to use when viewing MMI scripts or compilation logs,
enter one of the following in the Editor eld:
textedit or vi or xedit
NOTE
If an alternative editor is available, enter the name of the text
editor. Refer to Generating a database script le on page 3-70
for details.
6
To dene the import path when importing binary object les, enter the path
in the Import Path eld.
To dene a directory where the binary object les will be exported to, enter
the path in the Export Path eld.
Click Save Defaults to save the settings. Click Close to return to the
Administration menu.
NOTE
Set Preferences every time DataGen is closed and reopened.
9
To retain the standard DataGen default settings, shut down DataGen from
an Xterm window and restart DataGen. Refer to DataGen - startup and
shutdown on page 3-9 for details.
NOTE
An alternative to shutting down DataGen is to execute the following
command in the Xterm window from which DataGen was started:
source.cshrc
NOTE
The Option Object les must be copied from tape (or downloaded electronically from
the GSM Software Distribution and Licensing Centre) uncompressed and stored in a
directory on the DataGen processor. Refer to the section Upgrade procedures in the
DataGen/OLM Upgrade/Migration Guide in the Software Release Notes: DataGen
(68P02900W76) for details.
3-16
68P02900W22-R
GMR-02
Mar 2008
To install Options Object les, perform the following procedure.
Procedure 3-6 Install the Options Object
main menu. The Administration menu is displayed as shown in Figure 3-5.
Select Options from the menu. The Options Object Tool window is
displayed as in Figure 3-8.
Figure 3-8 Options Object Tool window
To locate the directory where the Options Object les are located, enter the
path in the Filter eld and select the Filter button.
Select the Options Object le and click OK.
Select a country from the Country Name list.
Select a software version from the Software Version list.

Continued
68P02900W22-R
3-17
GMR-02
Mar 2008
Procedure 3-6 Install the Options Object (Continued)

8
Click the Install button. A Conrmation window is displayed.

Click OK to continue. When the installation is complete,
a Conrmation window is displayed stating:
Object copied and linked. Refer to the Log File for

verification.
9
Click OK to continue. Refer to Viewing the log le on page 3-14 for details
on how to read the log le.
3-18
68P02900W22-R
GMR-02
Mar 2008
Database administration tasks
Database administration tasks
Monitoring le and database capacities

The usage script is designed to monitor le system and Informix database capacities. The
omcadmin account has control of the script. The usage script can be executed manually or as
a cronjob.
NOTE
If the usage script is executed as a cronjob, it must be restarted after any upgrade
activity is carried out on DataGen.
Running usage script as a cronjob
To run the usage script as a cronjob, log on to the DataGen processor as omcadmin.
Execute the following command:
cd /usr/omc/DataGen/current/cron
To run the script, enter the following command:

crontab usage.cron
Verifying usage cronjob

To check if the usage script is activated as a cronjob, log on to the DataGen processor as
omcadmin.
Execute the following command:
crontab -l
68P02900W22-R
3-19
GMR-02
Mar 2008
Running usage script manually
Running usage script manually
To run the usage script manually, log on to the DataGen processor as omcadmin. Execute
cd /usr/omc/DataGen/current/cron
To run the script, enter the following command:

usage
Warning messages issued

If either the le system or the Informix database reach 85% capacity, the usage script sends a
report to all open DataGen sessions on the DataGen processor. If the error message Broken Pipe
is received, then system administration should be undertaken to protect DataGen integrity.
NOTE
If the usage script is running as a cronjob, a check is performed every two hours.
Reloading the database

It is possible to reload the Informix database and retain the current areas. This procedure
deletes and then recreates the tables within the DataGen Informix database (db_dg) that store
the area data. Upon completion of the procedure, it is necessary to run Revgen again for all
areas.
Example of when to reload the database

If all the MCDF tables are not displayed in the Table Controller (for example, the table only
displays up to the Specics table), or if gcmd fails with an error relating to parameters not
found in the Informix database, then there may be a problem with the integrity of the database.
3-20
68P02900W22-R
GMR-02
Mar 2008
Dropping and recreating the db_dg Informix database
To resolve the problem, perform the following procedure.
Procedure 3-7 Reload the database
Log on to DataGen processor as omcadmin.
Enter the following command to verify that no-one is accessing DataGen:

whodo
Close all open DataGen GUIs.
Start DGAdmin by entering:

DGAdmin
Execute the following commands:

cd /usr/omc/DataGen/current/install
dbaccess db_dg upgrade.sql
Enter the following commands to validate the tables and MCDF les:
cd /usr/omc/DataGen/current/bin
valid_load -o c_tables.dat
valid_load -o mcdf.dat
Exit from the omcadmin account.

It is possible to destroy and recreate the DataGen Informix database (db_dg). This procedure
should be carried out if the procedure for Reloading the database above was not successful
or when the data within the db_dg database is no longer required and a new database needs
to be created.
CAUTION
This procedure will permanently erase the dg_db Informix database and should be
used with caution.
To drop and recreate the db_dg Informix database, perform the following procedure.
Procedure 3-8 Drop and recreate the db_dg Informix database
Unload the OLM netwk_conf table.
Unload the DataGen conguration tables.

Continued
68P02900W22-R
3-21
GMR-02
Mar 2008
Procedure 3-8 Drop and recreate the db_dg Informix database (Continued)
3
Prepare to drop and recreate the Informix database.
Drop the database.
Create a database.
Load the OLM netwk_conf table.
Load DataGen conguration tables.
Unloading the OLM netwk_conf table

The netwk_conf table exists in the DataGen Informix database (db_dg). It stores information
about OLM network congurations. This table must be unloaded to a le so that OLM network
conguration information can be recovered after dropping the db_dg database.
To unload the netwk_conf table, log on to DataGen processor as omcadmin. Enter the
following command (in the same line):
echo "unload to /usr/tmp/netwk_conf.unl select * from netwk_conf" | DGAdmin
dbaccess db_dg
Unloading the DataGen conguration tables

The country, network, bss_conf, bss_list, and conf_list tables exist in the DataGen Informix
database (db_dg). They contain conguration information for the DataGen BSS areas. These
tables must be unloaded to a le so that DataGen BSS area information can be recovered
after dropping the db_dg database.
To unload the tables, log on to DataGen processor as omcadmin. Enter the following commands
(all in one line):
echo "unload to /usr/tmp/country.unl select * from country" | DGAdmin dbaccess
db_dg
echo "unload to /usr/tmp/network.unl select * from network" | DGAdmin dbaccess
db_dg
echo "unload to /usr/tmp/bss_conf.unl select * from bss_conf" | DGAdmin dbaccess
db_dg
echo "unload to /usr/tmp/bss_list.unl select * from bss_list" | DGAdmin dbaccess
db_dg
echo "unload to /usr/tmp/conf_list.unl select * from conf_list" | DGAdmin
dbaccess db_dg
3-22
68P02900W22-R
GMR-02
Mar 2008
Preparing to drop and recreate the Informix database

Before dropping and recreating the Informix database, perform the following procedure.
Procedure 3-9
Prepare to drop and recreate the Informix database
Back up the Informix database. For details, refer to the section Backup
Procedures in the DataGen/OLM Clean Install Guide that is printed with
Software Release Notes: DataGen (68P02900W76).
Log on to DataGen processor as omcadmin.
Enter the following command to verify that no-one is accessing DataGen:

whodo
Close all open DataGen GUIs.
Start DGAdmin by entering:

DGAdmin
To display the INFORMIX-SQL main menu, type:

dbaccess
Dropping the database

To drop and recreate the Informix database, perform the following procedure.
Procedure 3-10 Drop the Informix database
Select Database from the main menu.
Select Drop from the Database menu.
Select the database to drop:

db_dg@<DataGen hostname>
Where DataGen hostname is the name of the DataGen processor.
A conrmation menu is displayed.
Select Yes to continue.
Select Exit and in all subsequent menus to return to the Admin prompt.
68P02900W22-R
3-23
GMR-02
Mar 2008
Creating a new database

To recreate the Informix db_dg database, perform the following procedure.
Procedure 3-11
Recreate the Informix db_dg database
Execute the following commands to create a database:

/usr/omc/DataGen/current/install/CreateDatabase
To activate each user on the new Informix database, type:

tp -u <username>
Where username is the name of the DataGen user.
Exit from the omcadmin account.
Loading the OLM netwk_conf table

To recover the OLM network conguration information, the netwk_conf table previously
unloaded to a le must now be loaded into the DataGen Informix (db_dg) database.
To load the netwk_conf table, log on to DataGen processor as omcadmin. Execute the
command (in the same line):
echo "load from /usr/tmp/netwk_conf.unl insert into netwk_conf" | DGAdmin
dbaccess db_dg
The OLM network congurations should now be visible in the OLM GUI.
Loading the DataGen conguration tables

In order to recover the conguration information for the DataGen BSS areas, the country,
network, bss_conf, bss_list, and conf_list tables, previously unloaded to a le, must now be
loaded into the DataGen Informix (db_dg) database.
To load the tables, log on to DataGen processor as omcadmin. Execute the commands (in
the same line):
echo "load from /usr/tmp/country.unl insert into country" | DGAdmin dbaccess
db_dg
echo "load from /usr/tmp/network.unl insert into network" | DGAdmin dbaccess
db_dg
echo "load from /usr/tmp/bss_conf.unl insert into bss_conf" | DGAdmin dbaccess
db_dg
echo "load from /usr/tmp/bss_list.unl insert into bss_list" | DGAdmin dbaccess
db_dg
echo "load from /usr/tmp/conf_list.unl insert into conf_list" | DGAdmin dbaccess
db_dg
The DataGen BSS areas should now be visible in the DataGen GUI.
3-24
68P02900W22-R
GMR-02
Mar 2008
Importing existing CM database objects
Importing existing CM database objects
Overview
A Conguration Management (CM) database object is a binary format le. Prior to the
development of DataGen, such le could be created only by downloading an ASCII format script
le into a BSC in SYSGEN mode.
DataGen has the ability to convert script les into CM database objects and vice versa.
Procedure
Importing a CM database object comprises three separate routines, performed in a dened
sequence.
For this procedure
Perform the following
Create a Country and Network, if not already

done.
Use the ADMIN option in the main menu

and select Country Admin to set up new
Country and Network denitions.
Create a New BSS Area.
Use the New BSS Area window to dene the

new BSS Area.
Import a CM database object.
Use the Service window.
68P02900W22-R
3-25
GMR-02
Mar 2008
Creating a new country/network
Creating a new country/network
Overview of creating a new country/network

Existing DataGen users with an earlier DataGen version can use this database to maintain
previously created country or network data. Refer to the section Restore procedures in
Software Release Notes: DataGen (68P02900W76) for information about restoring a database.
New DataGen users must create the required country or network data from the beginning. The
procedure for creating countries and networks in DataGen uses the Country Admin option
which is obtained by selecting ADMIN from the main menu.
Country Admin option

Perform the following procedure to access the Country Admin option.
Procedure 3-12 Accessing the Country Admin option
To access the Country Admin option for a new country or network, start
DataGen from an Xterm window and select ADMIN from the DataGen main
menu. The Administration menu is displayed as shown in Figure 3-5.
Select Country Admin from the Administration menu. The Country

Administration window is displayed as shown in Figure 3-9.
If the Country Admin option is already in use, a warning message is

displayed. Click OK to return to the Administration menu.
Figure 3-9 Country Administration window
3-26
68P02900W22-R
GMR-02
Mar 2008
Country Administration window - An Overview

The Country Administration window (as in Figure 3-9) enables users to create, update, and
edit Country and Network Administration les as follows.
File menu
The user option is Exit. The Exit option is used to exit from the Country Administration
window.
Country menu
The user options are:
Edit
Select to use GTE to edit the default Country.
Generate
Select to generate a Country Administration le from the DataGen database.
Update
Select to update the DataGen database with the default Country Administration le.
NOTE
For NEW users where no country.std le exists, select Generate from the Country
menu to automatically generate a country.std le in the /omcadmin/dg/ADMIN/country directory. This also applies to the network.std le.
68P02900W22-R
3-27
GMR-02
Mar 2008
Network menu
Edit
Select to use GTE to edit the default Network Administration le.
Generate
Select to generate a Network Administration le from the DataGen database.
Update
Select to update the DataGen database with the default Network Administration le.
NOTE
Country and Network menu options may be greyed out, according to which operations
are permitted at the time.
Data elds
Country File
Displays the default Country Administration le name when the CADM GUI window
is opened.
Network File
Displays the default Network Administration le name when the CADM GUI window is
opened.
3-28
68P02900W22-R
GMR-02
Mar 2008
Creating a new country
Creating a new country

To create a new country using Country Admin option, perform the following procedure.
Procedure 3-13
Create a new country using Country Admin
Select the Edit option from the Country menu in the Country
Administration window (as in Figure 3-9). The CADM Country File window
shown in Figure 3-10 is displayed.
Figure 3-10 CADM Country File window
From the Edit menu in the CADM Country File window, select Insert. Select
Insert to display a submenu with Before entry and After entry options.
These options allow the new entry is to be placed before, or after, an existing
entry in the displayed list of countries (if existing).
Type the name of the new country, press the Tab key, and then type the MCC
number followed by CR.
Select Store in DDS from the File menu in the CADM Country File window.
NOTE
The new data is saved only locally at this point.
5
Select Exit from the File menu to close the CADM Country File window.
Continued
68P02900W22-R
3-29
GMR-02
Mar 2008
Editing a country
Procedure 3-13
6
Create a new country using Country Admin (Continued)
In the Country Administration window, select Country - Update to save the

updated Country list in the Informix database.
A Message window requesting conrmation is displayed as in Figure 3-11.
Figure 3-11 CADM message window
Conrm the update by clicking the OK button. A message is displayed

showing that the update has taken place.
NOTE
The new data is now permanently stored.
Editing a country
Once a country is created, it can be edited using the Edit option from the Country menu on the
Country Administration window.
3-30
68P02900W22-R
GMR-02
Mar 2008
Creating a new network
Creating a new network

A new network entry is created and edited in the same way as a new country entry, using the
following procedure.
Procedure 3-14 Create a new network
Select Edit from the Network menu in the Country Administration

window as in Figure 3-9. The CADM Network File window is displayed
as in Figure 3-12.
Perform step 2 as for Country, and enter the required data in the MNC,
NCC, Network Name, and Operator Name data elds.
Figure 3-12 CADM Network File window
Select Store in DDS from the File menu in the CADM Network File
window.
NOTE
The new data is saved locally.
4
Select Exit from the File menu to close the window.
In the Country Administration window, select Network-Update

to save the updated Network data in the Informix database. A Message
window requesting conrmation is displayed as in Figure 3-11.
Conrm the update by clicking the OK button. A message is displayed

showing that the update has taken place.
NOTE
The new data is now permanently stored.
68P02900W22-R
3-31
GMR-02
Mar 2008
Deleting a country/network
Deleting a country/network
Overview of deleting a country/network

To delete a country using the Country Administration Tool, the associated BSS area(s) and
network must rst be deleted.
The BSS area(s), network, and country must be deleted in the following order:
BSS area(s)
Network
Country
To delete a BSS area(s), refer to the section Deleting a BSS area on page 3-43 for details.
Deleting the network

After deleting the BSS area(s), the network can also be deleted using the following procedure.
Procedure 3-15 Delete the network
From the DataGen main menu, select the ADMIN option.
Select Country Admin from the Administration menu bar. The Country
Administration window is displayed as in Figure 3-9.
Select Edit from the Network menu. The CADM Network File window is
displayed as in Figure 3-12, which shows a list of networks.
Click on the number adjacent to the network to be deleted.
From the Edit menu, select Delete.
From the File menu, select Store in DDS.
From the File menu, select Exit to return to the Country Administration
window.
From the Country Administration window, select Update from the

Network menu. A Message window is displayed requesting conrmation of
the update.
Click OK to update the database.
3-32
68P02900W22-R
GMR-02
Mar 2008
Deleting the country
Deleting the country

After the BSS area(s) and its network is deleted, the country can be deleted using the same
sequence of steps as described above for the network.
In the Country Administration window, select the Edit option from the Country menu and
follow step 4 to step 9 of Procedure 3-15 to delete the country.
68P02900W22-R
3-33
GMR-02
Mar 2008
Creating a BSS area
Creating a BSS area
Overview of creating a BSS area

This section describes the New BSS Area window and the procedure for creating a new BSS area.
New BSS Area window

From the DataGen main menu, select NEW (refer to Figure 3-1). The New BSS Area window is
displayed as shown in Figure 3-13.
Figure 3-13 New BSS Area window
The New BSS Area window has the following layout:

User input
areas
Country Name (automatically entered)

BSS Area
Software Version
Conguration number
Data eld
Area Comment
Action buttons
Create
Close
Country Name
The list of available countries is already present in the window. All other columns are blank at
this time.
3-34
68P02900W22-R
GMR-02
Mar 2008
New BSS Area window
BSS Area
When a Country Name is selected, any BSS areas currently congured for that country are
displayed.
Users can select an existing BSS area or else create a new BSS area by typing the name of the
new BSS area in the text box below the BSS Area column.
Software Version
Once a Country Name is selected, the software versions available are listed in the Software
Version column. Select the appropriate software version.
Conguration number
When the software version is selected, the conguration numbers that already exist are listed in
the Conguration number column. Three user options are available:
Enter a new conguration number by typing the number in the text box below the
Conguration number column.
Reuse an existing number by selecting from the list of numbers.
No selection. If no conguration number is selected, the lowest conguration number

available is allocated to the new BSS area, by default.
Area Comment
The Area Comment data eld allows the users to add useful information or comments, which
are displayed every time the BSS area is selected.
When all entries are made, click Create. DataGen checks the entries and opens the
Service Window.
Click Close to exit without creating a new BSS area.
68P02900W22-R
3-35
GMR-02
Mar 2008
Creating a BSS area
Creating a BSS area

To create a BSS area, perform the following procedure.
Procedure 3-16 Create a BSS area
Select a country from the Country Name list in the New BSS Area window
(refer to Figure 3-13).
Click in the text box under the BSS Area column and enter the name of the
new BSS area. The name can have a maximum of 30 characters. If more than
30 characters are entered, a Warning window is displayed as Figure 3-14.
Click OK to continue and then enter a BSS Area name limited to the maximum
length.
Figure 3-14 Warning message: name exceeds maximum valid

length
To obtain a conguration number automatically, do not select a number

but skip to step 6.
NOTE
If no conguration number is entered or selected, the lowest
conguration number available is assigned to the new BSS area.
Continued
3-36
68P02900W22-R
GMR-02
Mar 2008
Procedure 3-16
5
Creating a BSS area
Create a BSS area (Continued)
Select a Conguration number from the list or enter a number in the data
eld below the Conguration number list box. A Conrmation window is
displayed as in Figure 3-15, if an existing number is reused.
Figure 3-15 Overwrite BSS Area conrmation window
Click OK to overwrite the existing BSS area or Cancel to return to the New
BSS Area window, and re-enter an alternative number.
6
Click the Create button. After a short delay while the new BSS is being
created, the Service window is displayed. Refer to Figure 3-16.
Figure 3-16 The Service window
Continued
68P02900W22-R
3-37
GMR-02
Mar 2008
Creating a BSS area
Procedure 3-16 Create a BSS area (Continued)

7
The Service window remains open on the DataGen desktop, allowing the
user to carry out most of the remaining DataGen functions. The Area
Comment data eld allows the user to add useful comments which are
displayed each time the BSS area is selected. The functions of the greyed
toolbar icons are available only at a later stage. The following section
describes the layout and functionality of the Service window.
3-38
68P02900W22-R
GMR-02
Mar 2008
Opening a BSS area
Opening a BSS area
Opening a BSS area
NOTE
The maximum number of BSS areas that can be opened at a time is 10.
To open an existing BSS area from the DataGen Main window, perform the following procedure.
Procedure 3-17 Open a BSS area
From the DataGen main menu, select Open. The Open BSS Area window is
Figure 3-17 Open BSS Area window
Select a country from the Country Name list in the Open BSS area window.
Select a BSS area from the BSS Area list.
Select the software version from the Software Version list.
Select the conguration number from the Conguration number list.
NOTE
Select multiple conguration numbers to open multiple
congurations simultaneously as shown in Figure 3-17.
Continued
68P02900W22-R
3-39
GMR-02
Mar 2008
Opening a BSS area
Procedure 3-17
6
Open a BSS area (Continued)
Click Open. After a short delay, the Service window is displayed. Refer to
The Service window on page 3-56 for details. The Service window provides
options which enable the users to view and edit DataGen input les. If the
BSS area is locked by another user, an Information window is displayed as
shown in Figure 3-18.
Figure 3-18 Locked information window
NOTE
If the Override Lock parameter is enabled then the conguration
is unlocked automatically. Refer to Administration tasks on page
3-11 for details.
7
Click OK to override the lock or Cancel to return to the Open BSS Area
window.
NOTE
Information on the user holding the lock is found in the
DataGen.log le. Refer to Administration tasks on page 3-11 for
details.
3-40
68P02900W22-R
GMR-02
Mar 2008
Copying a BSS area
Copying a BSS area
Copying a BSS area procedure

The Copy function allows a BSS area to be copied to a new area with a new or specied
conguration number. To aid traceability when an area is copied, a default area comment is
inserted identifying the origin of the copied area.
To copy a BSS area, perform the following procedure.
Procedure 3-18 Copy a BSS area
From the DataGen main menu, select Copy. The Copy BSS Area window is
Figure 3-19 Copy BSS Area window
Select a Conguration number from the Conguration number list.
Enter the name of new BSS area in the eld below the Target BSS list.
NOTE
To overwrite an existing BSS area, select the BSS area from the
Target BSS list.
Continued
68P02900W22-R
3-41
GMR-02
Mar 2008
Copying a BSS area procedure
Procedure 3-18 Copy a BSS area (Continued)

7
Enter a Conguration number in the eld below the Target Cong list. If
the number already exists, DataGen assigns the next available number.
NOTE
If a conguration number is not entered, then DataGen
automatically assigns the lowest conguration number available.
The Area Comment eld, by default, contains the following information:
Copied from <BSS Area><Configuration No>
Where, BSS area is the name of the original BSS area and Conguration
No is the conguration number of the original BSS area.
8
Click Copy to copy the selected BSS area to a new area.
NOTE
All columns in the Table Controller window for the new area are
blank because the structure is copied but not the input tables.
3-42
68P02900W22-R
GMR-02
Mar 2008
Deleting a BSS area
Deleting a BSS area
Deleting an existing BSS area
NOTE
The maximum number of BSS areas that can be deleted at a time is 10.
To delete an existing BSS area, perform the following procedure.
Procedure 3-19 Delete a BSS area
From the DataGen main menu select DEL. The Delete BSS Area is
Figure 3-20 Delete BSS Area window
Select a country from the Country Name list in the Delete BSS Area window.

Continued
68P02900W22-R
3-43
GMR-02
Mar 2008
Deleting an existing BSS area
Procedure 3-19 Delete a BSS area (Continued)

5
Select the Conguration number from the Conguration number list.
NOTE
Select multiple conguration numbers to delete BSS areas
simultaneously. Locked areas are automatically unlocked.
6
Click Delete. An Information window is displayed briey as shown in

Figure 3-21.
Figure 3-21 Information window
NOTE
It is possible to return the to DataGen main menu while the delete
process is running. If the same BSS area is selected, the following
message is displayed:
This area is already being deleted.
When the BSS area is deleted, a second Information window displays the
name of the deleted BSS area.
7
Click OK to continue. The Delete BSS area window is now updated.
Click Close to return to the DataGen main menu.
3-44
68P02900W22-R
GMR-02
Mar 2008
Conguring BSS area(s)
Conguring BSS area(s)
Introduction to conguring the BSS

This section provides two examples on BSS conguration:
Expansion of a basic BSS and its TS by the addition of another Basic Transceiver Site (BTS).
Daisy chaining BTSs with a TS.
For information about the Motorola Customer Data Format (MCDF) tables referenced in this
section, refer to Chapter 6 MCDF tables which comprises a complete list of all the DataGen
MCDF tables, including parameter values and ranges.
Explanation of terms
BSS area
The BSS area means both the GSM Base Station System (BSS) and the GSM Remote Transcoder
(RXCDR). These two sub systems run the same software.
BTS and BTS Site

The Motorola implementation of the GSM Base Transceiver System (BTS) differs from
the GSM specications in that a Motorola BTS can support more than one cell. The GSM
recommendations specify that a BTS will support only one cell. In this section, the terms BTS
and BTS site refer to the Motorola BTS.
Functions and MCDF table relationships

Each conguration or equip function for a BSS uses an MCDF table that is populated with
parameters which are generic or specied by the user. Table 3-2 lists these functions and their
equivalent MCDF table(s).
68P02900W22-R
3-45
GMR-02
Mar 2008
Functions and MCDF table relationships
Table 3-2
Function - MCDF table relationships
Function
Equivalent MCDF table(s)
Equip Site (modify or add

new site)
Site
Equip Cabinet
Cabinet
Equip Cage
(Automatically done when device is

equipped)
Site Conguration
BTS, Generics and Statistics
Add Cell
Cell, Generics, Timers and Specics
Equip Devices
Hardware, Modify Value and

Daughter
Equip Functions
Path
RTF
BSP, DHP, BTP, LCF,
MTL, Circuits, Path, RSL,
OML
Hardware
Paths and Links
RTF
DRI
Hardware
Circuits
KSW
PIX Card
Daughter and PIX
Neighbor and Source
Neighbor
Equip DRIM
Hardware RTF
Handovers
Algorithm
Equip Pen
Hardware
Equip NSVC
NSVC
3-46
68P02900W22-R
GMR-02
Mar 2008
Basic BSS with TS switch - Expansion
Basic BSS with TS switch - Expansion
Overview
This section describes the procedures used to add another BTS site to the basic BSS. To expand
the basic network, it is necessary to modify the following MCDF tables:
The bss.mcd table (Site table)
The cab.mcd table
The hw.mcd table
The modv.mcd table
The link.mcd table
The path.mcd table
The lapd.mcd table
The cell.mcd table
The rtf.mcd table
The dri.mcd table
The ngbr.mcd table
The dgtr.mcd table
The pix.mcd table
To add another BTS site to a BSS area, perform the following procedure.
Procedure 3-20 Add a BTS site to a BSS area
Copy an existing BSS area to a new BSS area with a different conguration
number.
From the Table Controller window, open each of the tables listed above
in turn and modify their contents.
Save the le in the DDS, then validate and insert the les.
Open a Topology window to check whether the additional site is added by

the system.
68P02900W22-R
3-47
GMR-02
Mar 2008
Copying a BSS area
Copying a BSS area

To copy an existing BSS area, perform the following procedure.
NOTE
A BSS area can be copied by selecting Copy from the DataGen main menu. Refer to
Copying a BSS area on page 3-41 for details.
Procedure 3-21 Copy a BSS area
Open an Xterm window, and enter the command to obtain the DGAdmin
prompt: DGAdmin
Copy an existing BSS area to a new BSS area having the

same <BSS Area name> but with a different <cong> number
by executing the following command in the Xterm window:
ca -source <country name>:<BSS area name>:<configuration number>
[-area <new BSS area name> [-id <new BSS area id>]] [-config
<new configuration number>] [-title <new configuration title
string>]
For example:
ca -source Austria:Area1800:17 -area Area1800 -cong 18
A message similar to the following is displayed:
New area successfully copied
Country: Austria
BSS Area name: Area1800
Configuration Number: 18
NOTE
The BSS area to be copied should be the BSS area that was built
using the procedure in the previous section.
3
Select Open from the DataGen main menu to display a BSS Area window.
A list of available countries is displayed.
Select the Country Name of the new BSS area. Then select the new BSS
Area name to display a list of software versions.
Select the correct Software Version and the new Conguration Number
in the list boxes.
Click the Open button. DataGen then checks the entries and opens a
Service window for the new BSS area. For more information about the
Service window, refer to The Service window on page 3-56.
Expanding the BSS

The procedure for entering reconguration parameters in the tables to expand the basic BSS is
the same for each table. The tables to be modied are listed in the overview of this section.
3-48
68P02900W22-R
GMR-02
Mar 2008
Expanding the BSS
Recongure for expansion

To recongure the necessary MCDF tables, perform the following procedure.
Procedure 3-22 Recongure MCDF tables for expanding the BSS
From the Service window, select the Service menu, then select Table
Controller to open a Table Controller window. Refer to the section Using
the Table Controller on page 3-78 for more information.
Select a <lename> check box, then click the File button in the Table
Controller window to display the <Filename.mcd> table window.
If new columns need to be added before the data can be modied, go to
step 3; else go to step 5.
Highlight the top right-hand cell of the table, then select Insert from the
Edit menu. Select After entry from the submenu displayed to add another
column to the table.
Repeat step 3 if more columns need to be added; otherwise go to step 5.
Enter the appropriate values in the data elds. Use the Return key to step to
the next data eld. Refer to Chapter 6 MCDF tables for information about
values and ranges.
Continue to enter data until all the relevant data elds have been edited.
In the window which has been edited, open the File menu and select the
Store in DDS option.
Select Exit from the File menu to close the edited MCDF table.
Clear the current <lename> check box in the Table Controller window
and then select the next required <Filename> check box.
Repeat step 2 to step 8 until all the relevant MCDF tables have been edited.
68P02900W22-R
3-49
GMR-02
Mar 2008
Expanding the BSS
Insert and validate the recongured MCDF tables

To insert and validate the recongured MCDF table(s), perform the following procedure.
Procedure 3-23 Insert and validate the MCDF tables

1
In the Table Controller window, open the Select menu.
Select the Select All Files option, then click Validate. The MCDF les being
validated are displayed in a Message window.
A second window then displays the following message:
Filtering of file(s) has completed.
Close the Message window, then open the Select menu again. Choose the
Select All Files option, then click Insert. The MCDF les being
inserted are displayed in a Message window.
A second window then displays the message:
Filtering of file(s) was successful database has been
updated.
To conrm that the BSS conguration is as expected, select the Topology icon in the Service
window or the Topology option from the Services menu in the Service window to display
the conguration. Refer to the section Using the Topology Viewer on page 3-104 for more
information.
Figure 3-22 shows the topology of the new BSS area with the additional site added.
3-50
68P02900W22-R
GMR-02
Mar 2008
Expanding the BSS
Figure 3-22 Basic BSS with TS Switch - expanded
68P02900W22-R
3-51
GMR-02
Mar 2008
Daisy Chain conguration with TS switch
Daisy Chain conguration with TS switch
Overview of Daisy Chain conguration

This section describes the procedures used to recongure the expanded basic network as
a Daisy Chain.
Perform the following steps:
Copy an existing BSS area and assign a different conguration number to the copied
BSS area.
From the Table Controller window, open each of the tables listed above in turn and
modify their contents.
Save the le in the DDS, then validate and insert the les.
Open a Topology window to check that the additional site has been added by the system.
Preparation
To congure a BSS area as a Daisy Chain, it is easier to use an existing BSS area (such as the
expanded BSS conguration or another similar existing BSS conguration) by copying the area
and then assigning a different conguration number to the copied BSS area.
A BSS area can be copied using the procedure outlined in the section Basic BSS with TS
switch - Expansion or by selecting Copy from the DataGen Main menu. Refer to Copying a
BSS area on page 3-41 for details.
Procedure 3-24 Preparation
Once the BSS area is copied, select Open from the DataGen main menu to
display the BSS Area window.
The list of available countries is displayed. Select the following: Country

Name, BSS Area Name, Software Version and enter the new conguration
number.
Continued
3-52
68P02900W22-R
GMR-02
Mar 2008
Daisy chain conguration
Procedure 3-24 Preparation (Continued)

3
Click the Open button. DataGen then checks the entries and opens a
Service window for the new BSS area.
NOTE
For more information about the Service window, refer to The
Service window on page 3-56.

This procedure is used to the modify MCDF tables in order to recongure (as a Daisy Chain) the
copied version of the expanded BSS (or another BSS version). The les to be modied are:
The link.mcd table
The path.mcd table
The lapd.mcd table
The cell.mcd table

To recongure the necessary MCDF tables, perform the following procedure.
Procedure 3-25 Modify MCDF tables for Daisy Chain conguration
From the Service window, open the Service menu.
Select Table Controller to open a Table Controller window. Refer to the

section Using the Table Controller on page 3-78 for more information.
68P02900W22-R
3-53
GMR-02
Mar 2008
Links table
To modify each table, perform the following procedure.
Procedure 3-26 Modify the Links table
Select the Link check box, then select the File button in the Table
Controller window to display the <link.mcd> table window.
Use the cursor to highlight column 3, then open the Edit menu and select
Delete to delete the highlighted column.
Starting at the top of column 2 in the MCDF table window, change the
data in each data eld as required. For more information about values and
ranges, refer to the Links table in Chapter 6 MCDF tables.
Continue to enter data until all the relevant elds are edited, then move the
cursor away from the edited data elds.
Open the File menu and select the Store in DDS option. Select Exit from
the File menu to close the edited MCDF table.
Paths table
To modify the Paths table, perform the following procedure.
Procedure 3-27 Modify the Paths table
Clear the check box in the Table Controller window, and select the Path
button to display the <path.mcd> table.
Use the cursor to highlight column 3, then select the Edit menu and choose
Starting at the top of column 2 in the Paths table window, change the data
in each data eld each data eld as required. For more information about
values and ranges, refer to the Paths table in Chapter 6 MCDF tables.
Continue to enter data until all the relevant data elds are edited, then
move the cursor away from the edited data elds.
3-54
68P02900W22-R
GMR-02
Mar 2008
LAPD table
To modify the LAPD table, perform the following procedure.
Procedure 3-28
Modify the LAPD table
Clear the Paths check box in the Table Controller window and select the
Lapd button to display the <lapd.mcd> table.
Use the cursor to highlight column 4, then select the Edit menu and choose
Starting at the top of column 3 in the Lapd table window, change the data in
each data eld as required. For more information about values and ranges,
refer to the LAPD table in Chapter 6 MCDF tables.
Continue to enter data until all the relevant data elds are edited, then using
the Return key, move the cursor away from the edited data elds.
Cell table
To modify the Cell table, perform the following procedure.
Procedure 3-29 Modify the Cell table
Clear the Lapd check box in the Table Controller window and select the
RTF button to display the <rtf.mcd> table.
Change the data in each data eld in the row Primary Path ID as required.
For more information about values and ranges, refer to the RTF table in
Chapter 6 MCDF tables.
Continue to enter data until all the relevant data elds are edited, then
move the cursor away from the edited data elds.
Clear the RTF check box in the Table Controller window and continue
with the procedure for inserting and validating MCDF tables. Refer to
Procedure 3-23.
To conrm that the BSS conguration is as expected, select the Topology icon in the Service
window or the Topology option from the Services menu in the Services window to display
the conguration. Refer to the section Using the Topology Viewer on page 3-104 for more
information.
68P02900W22-R
3-55
GMR-02
Mar 2008
The Service window
The Service window
Functions of the Service window

The Service window provides several options which enables the users to view and edit DataGen
input les. When the Service window opens, details of the current BSS Area selected are
displayed as in Figure 3-23. The Service window contains a menu bar and a toolbar.
The toolbar contains the options which are used most frequently, allowing quicker access.
Figure 3-23 Service window
Service window toolbar

The Service window toolbar contains six buttons which have the following functionality:
3-56
68P02900W22-R
GMR-02
Mar 2008
Service window toolbar
Table Controller
The Table Controller button enables the user to create and edit BSS area data les. This
button has the same functionality as the Table Controller option in the Services menu.
Revgen/Compile
The Revgen/Compile button has dual functionality. When there is no data in the BSS area, the
Revgen function is displayed. When there is data in the BSS area, the Binary Object Compiler
function is enabled.
The Revgen button has the same functionality as the Revgen option, and the Compile button
has the same functionality as the Object Compiler option in the Services menu.
Topology
The Topology button enables the user to view a graphical representation of a BSS area. The
Topology button has the same functionality as the Topology option in the Services menu.
MMI
The MMI button creates a set of MMI command les for the selected area and concatenates
them. The MMI button has the same functionality as the Generate Script option in the
Services menu.
68P02900W22-R
3-57
GMR-02
Mar 2008
Service window menu bar
Exit
The Exit button closes the Service window and takes the user back to the DataGen main menu.
Help
The Help button displays the following message: 'For DataGen Help please refer to the
DataGen manual supplied, OLM On-Line help is available through the OLM GUI'.
Service window menu bar

The menu bar provides access to all options available whereas the toolbar provides access to
those tools which are used frequently. There are four main menus:
File
Edit
Services
Help
File menu
The following options are available from the File menu on the Service window:
Import Object
Export Object
Make Directories
Save
History
Exit
3-58
68P02900W22-R
GMR-02
Mar 2008
File menu
Import object
Select the Import Object from the File menu in the Service window. The Database Object
window is displayed as shown in Figure 3-24. This window enables the users to import .002
object les into DataGen.
To import a le into a BSS area, select the required directory from the Directories scroll box.
By default, the directory Filter is set to /usr/omc.
NOTE
If the path is changed, the directory Filter is set to the last path used for
the current session, unless DG_IMPORT_PATH is dened. Refer to Dening
environment variables on page 3-4 for details.
To import binary object les from an integrated OMC, the import path is:
/usr/omc/ne_data.
Figure 3-24 Database Object window
Click Filter to display the entries in the Files scroll box. Select the required le and click OK.
An Information window (as shown in Figure 3-25) is displayed when the le is imported to
the BSS area.
68P02900W22-R
3-59
GMR-02
Mar 2008
File menu
NOTE
The binary object creation Date and Time stamp is displayed in the Information
window.
Figure 3-25 Import Object - information window
Export Object
The Export object option displays the default path, where the binary objects are exported.
To transfer binary object les from DataGen to a BSS, perform the following procedure.
Procedure 3-30 Transfer binary object les from Datagen to a BSS

1
Transfer the binary objects les to the OMC. Refer to Exporting object les
to the OMC on page 3-114 for more details.
Download the binary object les from the OMC to the BSS.
Continued
3-60
68P02900W22-R
GMR-02
Mar 2008
File menu
Procedure 3-30 Transfer binary object les from Datagen to a BSS (Continued)
3
Selecting Export Object from the File menu on the Service window
identies the le path for the OMC operator. The following Information
window is displayed.
Figure 3-26 Export Object - information window
NOTE
To dene an alternative path to export the binary object les (002), refer to
Administration tasks on page 3-11 for details.
Make Directories
If an area exists in the DataGen database but does not have the corresponding directory
structure, for example, ~dg/country_name/area_name/conf_no/, the Make Directories
option can be used to create the directory structure.
Save
This option enables the DataGen user to save the current state of DataGen in case of
interruptions.
68P02900W22-R
3-61
GMR-02
Mar 2008
Edit menu
History
This option provides the following details of a BSS area as shown in Figure 3-27:
Title
If a new BSS area is created, the title contains the following information: Country, BSS
area, Conguration Number, and Software version. The title reects if the area is copied
or upgraded.
Owner
Creation Date
Modied By
Modication Date
Figure 3-27
History - information window
Exit
Select the Exit option to close the Service window and return to the DataGen main window.
This option is the same as clicking the X button in the Service window.
Edit menu
The following options are available in the Edit menu of the Service window:
Script
Compile log
Upgrade log
Hardware report
3-62
68P02900W22-R
GMR-02
Mar 2008
Services menu
Script
This option enables the user to view an MMI Script le using the X-Windows editor xedit. Refer
to the section Generating a database script le on page 3-70.
Compile log
This option enables the user to view the compile log le, using the X-Windows editor xedit,
running the object compiler. Refer to the section Generating a database script le on page
3-70 for details.
Upgrade log
This option enables the user to view the upgrade log le, using a text editor. The upgrade log
le is available for upgrades carried out through the GUI. The log le is not created if the
upgrade is carried out from the command line. Refer to Upgrader on page 3-122 for details on
how to upgrade a software release.
NOTE
Users can dene the default editor for editing scripts or viewing the compile or
upgrade logs. Refer to Administration tasks on page 3-11 for details.
Hardware Report
This option enables the user to view a hardware report a text editor. Refer to Generating a
hardware report on page 3-109 for details.
Services menu
The following options are available in the Services menu of the Service window:
Table Control
Revgen
Object Compiler
Topology (after Revgen)
Generate Script (after Revgen)
Recombine Script
Generate Hardware Report (after Revgen)
68P02900W22-R
3-63
GMR-02
Mar 2008
Services menu
Table Control
Select this option to open a Table Controller window, view, and edit the BSS tables. Refer to
Using the Table Controller on page 3-78 for details.
Revgen
Select the Revgen option to activate the Revgen process and converts the selected object le
into a DataGen script le. The binary object le can be compressed or uncompressed. Refer to
Converting a CM database object le to a script le on page 3-65 for details.
Object Compiler
The Object Compiler enables the user to generate a .002 Object le from the MMI Script. The
.002 object les are automatically compressed if the software version is 1.6.0.0 or higher.
Recombine Script
Select the Recombine Script option to enable the concatenation of a number of MMI script
les into a single le. This also generates individual site based MMI script les, for example:
SITEXXX, where XXX is replaced by the site number.
Topology
The Topology option becomes available after the Revgen process is complete. Selecting this
option enables the users to view a graphical representation of a BSS area.
Generate Script
The option becomes available after the Revgen process is complete. Selecting this option
enables the user to generate an MMI script le and individual site les.
Generate Hardware Report

The option becomes available after the Revgen process is complete. Selecting this option
enables the users to generate a hardware report which contains a list of all the devices names,
function names, slot numbers, and Id devices within each cage. Refer to Generating a hardware
report on page 3-109 for details.
3-64
68P02900W22-R
GMR-02
Mar 2008
Introduction to creating a script le

Converting a CM Database Object to a Database Script File enables upgrading to a later
software version, or changing some parameters in the existing software version. It also enables
the user to view the topology of a BSS area.
Invoking Revgen
Revgen is invoked either by selecting REVGEN from the Services menu or clicking the Revgen
button on the toolbar.
Depending on how the environment variable setenv DG_AUTO_REVGEN is set, selecting Revgen
may result in the following:
The Revgen window opens.
The Revgen window opens and Revgen starts automatically.
Refer to Dening environment variables on page 3-4 for details on how to set the environment
variable DG_AUTO_REVGEN. By default, this environment variable is not enabled.
The software version of the new BSS area MUST be the same as the imported CM database
object.
NOTE
Revgen can only be run successfully on a NEW BSS area. The CM database binary
object le can be compressed or uncompressed.
Revgen window description

The Revgen window (refer to Figure 3-28) is divided into four areas as follows:
File menu on page 3-66
Information area on page 3-66
Data area on page 3-66
Toolbar on page 3-66
68P02900W22-R
3-65
GMR-02
Mar 2008
File menu
File menu
Table 3-3 describes the File menu options in the Revgen window.
Table 3-3 Revgen window le menu options

To
Select
Import BSS Object
Run Revgen
Start the Object conversion.
Remove Lock File

Exit
Specify and import a CM Database

object.
Unlock a BSS area.

Exit and close the Revgen windows.
Information area
The information area in the Revgen window contains three data elds as described in
Table 3-4.
Table 3-4 Revgen window le menu options

Information area
Denition
BSS Area
BSS area into which CM Database Object is to

be loaded, and the software version.
Status
Informs the user of the status of Revgen.
Object
Displays the path to the object which is to be

converted.
Data area
The data area displays information about the progress of the object conversion.
Toolbar
There are two buttons on the toolbar:
Run Revgen - Select this option to start the object conversion.
Exit - Select this option to exit from the Revgen Tool.
3-66
68P02900W22-R
GMR-02
Mar 2008
Activating Revgen
Activating Revgen
If the setenv DG_AUTO_REVGEN environment variable is not set to Yes, run Revgen as follows.
Procedure 3-31 Activate Revgen
Select the REVGEN button or select Revgen from the Services menu.
The Revgen window is displayed as in Figure 3-28.
Figure 3-28 Revgen window
From the File menu, select Import BSS Object.
Select the required directory from the Directories list.
Click the Filter button to display the entries in the Files list.
Select the binary object le in the Files list.
Select Import. A Conrmation window is displayed when the import is

complete. Click OK.
Continued
68P02900W22-R
3-67
GMR-02
Mar 2008
Activating auto Revgen
Procedure 3-31
Activate Revgen (Continued)
The initial display of Revgen shows the BSS area and the software version of
the imported object. Check these details before running Revgen.
Click Run Revgen. The information and data areas display the details and
progress of the object conversion. An example is shown in Table 3-4.
Figure 3-29 Running Revgen
Click Exit to return to the Service window when the process is complete.
NOTE
If the Exit button is selected before Revgen is complete, the
actual conversion of the 002 object will not be terminated,
because it is running as a background task. The Revgen tool is
monitoring the status of the logle, and when Revgen is invoked
again, the current status of the logle is displayed.
Activating auto Revgen

If the setenv DG_AUTO_REVGEN environment variable is set to Yes, run Revgen as follows:
3-68
68P02900W22-R
GMR-02
Mar 2008
Completion of Revgen process
Select the REVGEN button or select Services - Revgen from the menu bar. This displays
the Revgen window and starts the Revgen process. The Information window displays the
details and progress of the object conversion. Table 3-4 displays an example of the window
on completion of Revgen.
Select the Exit button to return to the Service window when the process is complete.
NOTE
If the Exit button is selected before Revgen is complete, the actual conversion of the
.002 object will NOT be terminated, because it is running as a background task. The
Revgen tool is monitoring the status of the logle, and when Revgen is invoked again,
the current status of the logle is displayed.
Completion of Revgen process

As the process is completing, the following message is displayed:
Loading BSS Area. Please wait. . .
Completion of the Revgen process may take several minutes for a large BSS area. On
completion, a new Service window is displayed with a full complement of tools.
NOTE
If the prompt BSS Area is locked, when trying to open a BSS area, for more
information, refer to the section Lock/Unlock BSS area in Chapter 5 Command
line tools.
Alternatively, use the Remove Lock File option in the File menu of the Watch
window.
68P02900W22-R
3-69
GMR-02
Mar 2008
Generating a database script le
Generating a database script le
Overview of database script les

After the Revgen process is completed successfully, it produces a database script le in the
DataGen output le directory.
The system also issues a report stating that the database tables are populated.
Running the script le generator

Generating a database script can be performed from the Services window (refer to Figure 3-30)
either by clicking the MMI button or selecting the Generate Script option in the Services menu.
The database script generator uses the le data in the Service window (Country, BSS Area,
Software Version, and Conguration number) to identify the correct le. The user is
informed when the script has been successfully created.
The database script le is stored in the output le directory of DataGen.
NOTE
Each time a combined script is generated the original script is backed up with a Date
and Time stamp. For example COMBINED.BACKUP072498123425. This allows
the original script to be compared against the new script. Individual site les are
created, for example; SITE<XXX>, where XXX is replaced by the site number.
NOTE
If the Options Object le is found to be missing or corrupt, an error message as
shown in Figure 3-30 is displayed. Refer to Administration tasks on page 3-11 for
details of reinstalling the Options object le.
3-70
68P02900W22-R
GMR-02
Mar 2008
Figure 3-30
Viewing a database script le
Invalid Options Object message

After a database script le has been created, it can be viewed by selecting the Script option in
the Edit menu of the Service Window.
The script le is displayed within a xedit window as shown in Figure 3-31. The script le can
be edited at this point, although this is not recommended unless an error has occurred as a
result of the compiler process. If the database script le is edited, DataGen does not hold any
record of changes which are made.
68P02900W22-R
3-71
GMR-02
Mar 2008
xedit window description
To dene which editor to launch when viewing scripts, refer to Dening environment variables
on page 3-4 for details.
Figure 3-31
xedit window description

The xedit window comprises three main areas:
Toolbars
File information areas
File display area
3-72
68P02900W22-R
GMR-02
Mar 2008
Using the toolbars
Using the toolbars

There are three toolbars on the xedit window:
quit exits the xedit process.
save saves the combined script le to a specied location or name.
load loads a specied combined script le.
File information areas

The le information areas show the full path of the script le presented in the display area
of the xedit window.
File display area

This area in the xedit window displays the combined script le contents which can be edited
and saved with a new BSS name. The window can be scrolled using the Up and Down arrow
keys on the keyboard.
NOTE
A script le can also be generated and edited using an editor in an Xterm window,
for example, the UNIX editor vi.
Alternative text editor

Procedure 3-32 describes the steps involved in dening a text editor to view MMI scripts or
compilation logs other than the standard editors.
NOTE
When adding a new editor, verify that the editor runs on the system processor. This
can be done by entering the editor name from the command line and ensuring that it
launches correctly.
68P02900W22-R
3-73
GMR-02
Mar 2008
Procedure 3-32 Dene a text editor

1
Log on to the DataGen processor as user: root.
Copy the selected editor to the /usr/bin directory using the following
commands:
cp <text_editor> /usr/bin
Where text_editor is the name of the text editor.
Change the permissions on the text editor to allow all users access to the le:
chmod 555 /usr/bin/<text_editor>
Continued
3-74
68P02900W22-R
GMR-02
Mar 2008
Procedure 3-32 Dene a text editor (Continued)

4
If all users need to use the editor, add the following line to the le:
/usr/omc/DataGen/current/config/local/cshrc.datagen:
setenv DG_EDITOR <text_editor>
Where text_editor is the name of the text editor.
NOTE
If only specic users wish to use the editor, edit the .cshrc in
the user's home directory.
For example, if setenv DG_EDITOR vi is entered, when the script le

is invoked from the Edit menu, it is displayed with the vi editor
as shown in Figure 3-32.
Figure 3-32 Viewing an MMI script with vi
68P02900W22-R
3-75
GMR-02
Mar 2008
Viewing and editing DataGen les
Viewing and editing DataGen les
Overview of editing DataGen les

After a CM database object has been uploaded and converted using the Revgen option in
the Service window, it can be manipulated and edited into a new format using the DataGen
tools. These tools comprise:
Table Controller
Generic Table Editor
Topology Viewer
Upgrader
Difference Reporter
Table Controller
The Table Controller enables users to create MCDF (Motorola Customer Data Format) input
les by exporting le information from the Informix database.
It also enables users to validate input les and insert the le parameters back into the Informix
database.
Generic Table Editor

The Generic Table Editor enables MCDF les to be displayed and edited from the Table
Controller.
Topology Viewer
The Topology Viewer provides users with a graphical representation of the topology of the
complete BSS area and a view of all the cage hardware in a BSS area.
3-76
68P02900W22-R
GMR-02
Mar 2008
Upgrader
Upgrader
The Upgrader is a window-based tool which is invoked by selecting the UPG button from
the DataGen main menu.
The Upgrader creates a new BSS area in the Informix database. The new BSS area is an exact
copy of the BSS area in the database which is to be upgraded.
The upgrade of the BSS area is then carried out on the copy of the area so that the original
area is unchanged.
Upgrader can also be invoked using the Command Line. Refer to Chapter 5 Command line
tools Version upgrader (upg) command for details.
NOTE
If any parameters in the BSS area are to be changed prior to the upgrade they should
be done by altering the MCDF les. Refer to Using the Generic Table Editor (GTE)
68P02900W22-R
3-77
GMR-02
Mar 2008
Using the Table Controller
Running the Table Controller

To open the Table Controller window (as in Figure 3-33) from the Service window, either
select the Table Control option from the Services menu or click the Table Controller button.
Figure 3-33 Partial view of typical Table Controller display
3-78
68P02900W22-R
GMR-02
Mar 2008
Table Controller functions
Table Controller functions

The Table Controller has two functions:
Editing input les using the Generic Table Editor and inserting them into the DataGen
database.
Exporting data to create a new set of MCDF les for the BSS area.
User controls
The Table Controller comprises four main areas:
Menu bar on page 3-79
Command buttons on page 3-79
File select buttons on page 3-80
File status display area on page 3-80
Menu bar
The menu bar provides the following options to manipulate DataGen input les as described in
Table 3-5 below.
Table 3-5 Table Controller - menu bar File and Select options
Option
Exit
Select all Files
Deselect all
Files
Denition
When selected, exits and closes the Table controller
window.
Selects all the displayed le types in the Table
controller window.
Clears all le types in the Table Controller window.
Command buttons
The command buttons are used to perform File, Validate, Insert, Export, and Report functions
on the les imported into the Table Controller.
File
Click File to open or create an input le. A check mark shown in the File column opposite an
input le button indicates that the le exists in the DataGen input le directory.
68P02900W22-R
3-79
GMR-02
Mar 2008
File select buttons
Validate
Click Validate to check that the parameters held in an input le are valid. A report is produced
informing the user of the result of validation. If the report le contains any warnings, then a
W appears in this column against the particular parameter.
Insert
Click Insert to insert the input les into the DataGen Informix Database. Files are validated
automatically as they are inserted and a report is produced informing the user of the result
of the insertion.
Export
Click Export to export data from the Informix database into the DataGen Table Controller.
Report
Click Report to display the reports produced after using the Validate and Insert options.
There is one table report per input le. The table reports must be read before another operation
is carried out on that table. A W character in the Validate or Insert column indicates the
presence of a warning in the report le which should be checked.
File select buttons

Each check box on the left-hand side of the Table Controller is used to select or clear a DataGen
input le (table le) containing BSS database parameters. The name next to the check box
identies the contents of the le.
File status display area

This area of the Table Controller window displays icons identifying the status of each table
during each type of operation. For example, a tick shown in the le column opposite a le
select button indicates that the le has been correctly imported. Table 3-6 shows examples of
each of these icons.
MCDF table les

The following description provides a general introduction to the contents of each table le in
the Table Controller.
3-80
68P02900W22-R
GMR-02
Mar 2008
MCDF table les
For more detailed information, refer to Chapter 6 MCDF tables.
BSS (bss) - The BSS table is at the top of the MCDF hierarchy and contains BSS specic
information.
SITE (bts) - The SITE table contains specic information regarding each site in the BSS
area.
Hardware (hw) - The Hardware table contains information regarding all cages, default
cabinets, and full-height cards throughout the BSS area. Each entry in the table contains
details of one device, with respect to the site, cabinet, cage, and slot in which the device
resides.
NOTE
The cabinets and cages are not explicitly noted in the table; further information
is included within the details of the cards.
Cabinet (cab) - The Cabinet (optional) table contains information about all the non-default
type cabinets throughout the BSS area.
Generics (gene) - The Generics table contains a list of elements, including Motorola
specic elements. For convenience, the Timer and Statistics elements have been placed
in separate les. Either the value from the value eld (if present) or the Motorola
recommended value is set BSS-wide but can be overridden for a site or cell by values in the
specics and cell tables. Also, values for the commands dnlk_vad_qtx, and msc_qt are
inserted using the Generics Table.
Timer (time) - The Timer table contains a list of timer elements, including Motorola
specic elements. Either the value from the value eld (if present) or the Motorola
recommended value is set BSS-wide but can be overridden for a site or cell by values in
the Specics table.
Circuit (acct) - The Circuit table contains all MTL, LMTL, and OML signalling links. It
also contains the terrestrial circuits to time slots at the BSC for radio trafc channels.
Channel (chan) - The Channel table is only required for Remote Transcoders and contains
the OML and MTL signalling links through the remote transcoder. It also contains details
of the trafc channels between the MSC and BSC on the remote transcoder. The MSIs and
MMSs required are given in detail in the Hardware table.
Link (link) - The Link table is used for two different tasks:
Non-RXCDR area - contains details of the links between MMSs required by the paths.
RXCDR area - contains details of the links between the RXCDR and its BSCs used
by the XBL feature.
In both cases, the MSIs and the MMSs required are given in detail in the Hardware table.
Modify Value (modv) - The Modify Value table details all the modify_value commands
related to MMS/LCF device functions within the area.
PATHs (path) - The Paths table gives the details of all the paths within the BSS area
(providing signalling and trafc communication between the BSC and the BTSs), using the
links detailed in the Links table. Details of RSLs are also contained in this table.
68P02900W22-R
3-81
GMR-02
Mar 2008
MCDF table les
LAPD (lapd) - The LAPD table contains details of the LAPD values for the RSLs and XBLs
in the area. The RSLs and XBLs required are given in detail in the Circuits and Paths tables.
Cell (cell) - The Cell table contains the details of all the cells across the OMC or network
and also the external neighbors used by the specied cells. The optional elds in this table
contain information which override the defaults specied in the Generics table.
RTF (rtf) - The RTF table contains details of the RTFs contained in the BSS area.
DRI (dri) - The DRI table contains details of the DRIs specied in the Hardware table for
the BSS area. The DRI must have its cage and slot number detailed in the Hardware table.
Statistics (stat) - The Statistics table contains a list of statistical elements. Either the
value from the value eld (if present) or the Motorola recommended value is set BSS-wide,
but can be overridden for a site or cell by values in the Specics table.
Specics (spec) - The Specics table enables the user to dene specic values for
chg_element and add_cell elements for a particular site or cell overriding the parameters
specied in the Generics, Timers, and Statistics tables.
NOTE
Elements that can exist in the Cell table are not shown in the Specics table.
Neighbor (ngbr) - The Neighbor table identies the cell pairings network-wide, using
the bss_id to identify the BSS area containing the cell marked as the source. The bsic
and the bssh frequency are detailed in the Cell table. The elds classed as optional may
contain values overriding those specied in the Cell table.
Algorithm (alg) - The Algorithm table species the algorithm data to be used across the
BSS area. These entries do not use the lac and ci elds. It also enables the user to dene
specic algorithm data for dened cells identied by their lac and ci.
Throttles (thro) - The Throttles table species throttles to be applied to device types for
the whole BSS area and links them to alarm numbers.
EAS (eas) - The EAS table is used to specify alarm strings for alarm numbers used with
the BSS area.
Daughter (dgtr) - The Daughter table is used to identify the half-height cards at a site in
the same way as the Hardware table species the full-height cards.
PIX (pix) - The PIX Table species the hardware circuits that activate specic alarms in
an EAS device.
KSW (ksw) - The KSW table species the data for the KSW conguration commands
(chg_ksw_cong). This table only has entries for sites that implement expanded KSW
cards. Also, this table only contains entries that differ from the default values generated
within the BSS and BTS tables.
NSVC (nsvc) - The NSVC table is used to specify all the parameters of the add_nsvc
command. This is used to allow the user to map an NS-VCI and DLCI to a specic GBL.
Hop (hop) - The Hop table is used to specify the parameters of the chg_hop_params
command.
3-82
68P02900W22-R
GMR-02
Mar 2008
Creating MCDF les
ACS (acs) - The Active Codec Set (ACS) table is used to specify the parameters for any
chg_acs_params commands.
Test Neighbor (testngbr) - The Test Neighbor table species test neighbor details that
allow the cell to add frequencies to the bcch allocation list without having that frequency
considered for a hand over.
Creating MCDF les

MCDF les can either be created, using blank templates, or regenerated, using an existing
database.
MCDF le procedures
File creation procedure
To create les in MCDF format, it is necessary to Export the les from the Informix database.
NOTE
The term Export means that the functions carried out in the Table Controller serve to
Export the les out of the Informix database, perform any editing required (or simply
view the tables), and then Insert the table back into the database.
NOTE
If a conguration area has been imported and was created using an earlier
version of DataGen, it is necessary to re-export the MCDF les owing to changes
in the DataGen 1.6.0.0 MCDF tables.
Warning messages may appear during the Export process, these can be safely
ignored as the Export continues successfully.
68P02900W22-R
3-83
GMR-02
Mar 2008
MCDF le procedures
To create MCDF les, perform the following procedure.
Procedure 3-33 Create les in MCDF format
After the Object le has been converted to a Script le by the Revgen

process, select Table Control from the Services menu in the Services
window.
In the displayed Table Controller window, choose Select All Files from
the Select menu.
In the Table Controller window, select the Export button. A Message

window is displayed showing the progress of the Export function for each
le.
When the Message window indicates that all les are exported, click the
OK button. Each le, when correctly exported, is indicated by a check mark
in the File column.
File validation procedure

After the les are created, and/or edited using the GTE, the les must be validated and then
inserted back into the Informix database.
Validation can be carried out separately on each le or the whole le set can be validated in
one process. Validation comprises the following procedures:
A check for missing elds
A check for superuous elds
A check for illegal values
To validate all les, perform the following procedure.
Procedure 3-34 Validate all les
Open an Xterm window and enter the following command:

DGAdmin DGLog
The Validation Log window opens and displays errors and warnings about
the progress of the validation and insert process. This information is also
available by viewing the log le from the Administration menu. Refer to
In the Table Controller window, choose Select All Files from the Select
menu.
Click the Validate button. A Message window showing the progress of the
Validate function for each le is displayed.
When the Message window indicates that all les are validated, click OK.
Each correctly validated le is indicated by a check mark in the File column.
3-84
68P02900W22-R
GMR-02
Mar 2008
MCDF table editing
File insertion procedure

After successful validation, the les must be inserted back into the Informix database. To insert
the les, perform the following procedure.
Procedure 3-35 Insert validated les into the Informix database
Open an Xterm window and enter the following command:

DGAdmin DGLog
The Validation Log window opens and displays errors and warnings about
the progress of the validation and insert process. This information is also
available by viewing the log le from the Administration menu. Refer to
In the Table Controller window, choose Select All Files from the Select
menu.
Click the Insert button. A message window showing the progress of the
Insert function for each le is displayed.
When the Message window indicates that all les have been inserted,
click OK. Each correctly inserted le is indicated by a check mark in the
File column.
NOTE
As each le is validated and inserted into the database, a report
is generated, the results of which can be viewed by selecting the
le and clicking Report.
Instead of carrying out separate Validate and Insert tasks on the selected les, users can
select the les and carry out the Insert task ONLY which automatically validates the les
before insertion.
However, creating a new le or making a large number of edits to an old le increases
the likelihood of errors, particularly as many of the input les are interdependent. It is
recommended that, in such cases, separate validate and insert operations are performed.
The interdependency of the input les also means that a le can only be validated if all its
dependent les are validated and inserted or are currently selected.
MCDF table editing

After the MCDF les are created from the Informix database, they can be edited using the
Generic Table Editor (GTE). The following procedure uses a Generics table, which requires a
change to the Generics parameter ber_loss_daily, as an example of table editing.
68P02900W22-R
3-85
GMR-02
Mar 2008
MCDF table editing
Table editing procedure - example

To edit an MCDF table, perform the following procedure.
Procedure 3-36 Edit an MCDF table using the Generic Table Editor
In the Table Controller window, select the Generics Radio button, then
select the File button.
A Generics table (gene.mcd) is displayed as in Figure 3-34.
Figure 3-34 Generics table
Highlight the data eld containing the value for ber_loss_daily.
Enter the value 4, then press CR to save the entry.
From the Generics Table File menu, select Store in DDS, then select Exit.
The Generics Table window closes and the relevant Validate and Insert
columns in the Table Controller contain an asterisk (*).
Select the Generics le select button. A Report window displays the

message that the ber_loss_daily value was successfully updated in the
database.
3-86
68P02900W22-R
GMR-02
Mar 2008
File status icons
NOTE
If an invalid entry is made to the MCDF tables, a report le is generated

informing the user of an error. In certain cases, a warning icon is displayed
in the Validate column and no further editing is allowed until the error is
corrected. Some input les, however, do not display a warning icon (for example,
out of range values). It is important therefore to read the Report le every time
a parameter is edited and inserted otherwise, the error may not be apparent to
the user until the le has been through the Binary Compiler process.
If the validation log (DGLog) window is open, it is possible to monitor and

identify the problems as they occur.
File status icons

The File Status icons on the Table Controller window are dened as follows (refer to Table 3-6).
Table 3-6
Symbol
File status icons

File Meaning
File does not
exist in DDS.
Validate
Meaning
File has
not been
validated.
Insert
Meaning
File has
not been
inserted.
Export
Meaning
N/A
Report
Meaning
Report le
does not
exist.
File is being
edited.
N/A
N/A
N/A
File is
available for
editing.
File has been

validated
successfully.
File has
been
inserted
successfully.
N/A
File is being
edited.
File is being
edited.
N/A
N/A
Error
occurred
during
validation.
Error
occurred
during
insert.
N/A
N/A
N/A
N/A
N/A
File is
unreadable.
File cannot
be written
to, that is,
Locked.
N/A
N/A
N/A
Report le
has been
read.
Continued
68P02900W22-R
3-87
GMR-02
Mar 2008
File status icons
Table 3-6 File status icons (Continued)

Symbol
Validate
Meaning
Insert
Meaning
Export
Meaning
N/A
Current
le is
incomplete.
Validation
needs more
information.
Insert
operation
needs more
information
N/A
N/A
Warnings
produced
in report
le during
validation.
Warnings
produced
in report
le during
insertion.
N/A
File Meaning
3-88
Report
Meaning
Report le
is unread.
N/A
68P02900W22-R
GMR-02
Mar 2008
Using the Generic Table Editor (GTE)
Using the Generic Table Editor (GTE)
Introduction to the Generic Table Editor

The Generic Table Editor (GTE) allows the user to display and edit the MCDF input les.
An MCDF input le has three selections on its menu bar:
File
Edit
Format
The File menu

Table 3-7 describes the File menu options.
Table 3-7
File menu options

To
Select
New
Create a new (empty) MCDF input le.
Open
Open an existing le.
Store in DDS
Save As
Print Setup
Print
Restart
Exit
Save the current state of an edited le in the DataGen Directory

Structure (DDS).
Save a le with a different, or new lename, using the Save As option
in the File menu.
Set up printing parameters.
Print the current le to one of the available printers.
Restore the le to its last saved version, before any modications
were made.
Close the input le.
68P02900W22-R
3-89
GMR-02
Mar 2008
The File menu
New option
To create an (empty) MCDF input le, select New from File menu in the MCDF input (.mcd)
le. A New message window is displayed as in Figure 3-35.
Figure 3-35 New MCDF input le message
Click OK to create an (empty) MCDF input le.
Open option
To open an MCDF input le, Select the Open option from the File menu in the MCDF input le
window. The Open File window is displayed as shown in Figure 3-36.
Figure 3-36 MCDF Input File - Open option
3-90
68P02900W22-R
GMR-02
Mar 2008
The File menu
This window has the following functionality:
Filter
This data eld enables the user to specify a directory path, and the name of the le which
is to be opened. The wildcard character * can be used to display ALL les in a directory.
Directories
This scrolled list box displays directories and sub directories which can be selected by
double-clicking an entry, or highlighting an entry and pressing the Filter button.
Files
This scrolled list box displays the les contained in the selected directory. To open a le,
highlight the le using the mouse button and press the OK button.
Selection
This data eld shows the selected path and lename.
Buttons
The following buttons are available:
OK - Initiates the File Open function.
Filter - Initiates the search process on the path displayed in the lter box, and display
the results in the Directories and Files list boxes.
Cancel - Cancels an operation.
Help - Help is not available in this version of DataGen. The following message is
displayed: 'For DataGen Help please refer to the DataGen manual supplied,
OLM On-Line help is available through the OLM GUI'.
Store in DDS option

After editing an MCDF Input le, perform the following procedure to store the le in the
DataGen Directory Structure (DDS).
Procedure 3-37 Store MCDF Input le in the DataGen Directory Structure
Select the Store in DDS option from the File menu in the edited MCDF
Input le menu bar.
Select Exit to close the edited le.
In the Table Controller window, select the Insert button. A message

window is displayed showing the results of the Insert process. The le is
validated automatically.
If the Insert was successful, click the OK button in the message window.
A check mark is placed in the Insert column of the le type indicating
successful insertion.
68P02900W22-R
3-91
GMR-02
Mar 2008
The File menu
Save As option
Figure 3-37 shows the Save To File window which is displayed when the Save As option is
selected in the MCDF Input File File menu. Using this option, existing les can be saved with a
different lename, or a new le can be saved with a new lename.
Figure 3-37
Save To File window
Print Setup option

Figure 3-38 shows the Printer Setup window which is displayed when Print Setup is selected
from the File menu.
NOTE
The default page size is A4.
3-92
68P02900W22-R
GMR-02
Mar 2008
The File menu
Figure 3-38 Print Setup window
The Printer Setup window enables the user to specify printing parameters using:
Two menu buttons for page size and orientation
Four data elds for print area parameters
Four action buttons
The various printing parameters are dened in Table 3-8, Table 3-9 and Table 3-10.
Table 3-8 Printer setup - menu buttons

Select
To
Page Size
Display a drop down menu of available page sizes for printing. Select A4
page size from the menu to enter the default values into the data elds.
Orientation
Display a drop down menu of page layout types.
Table 3-9 Printer setup - data elds

Select
Resolution
To
Display the default DPI for printing.
Height
Display the default page width for printing.
Width
Display the default page height for printing.
Scaling factor
Display the default scaling factor, normally zero.
68P02900W22-R
3-93
GMR-02
Mar 2008
The File menu
Table 3-10 Printer setup - action buttons

Select
To
OK
Conrm the displayed parameters and close the Printer Setup window.
Apply
Accept the displayed parameters.
Cancel
Cancel the current operation.
Help
Display the following Help message:

supplied, OLM On-Line help is available through the
OLM GUI'
Print option
The Print Table window is displayed when the Print option is selected from the File menu.
Figure 3-39 Print Table window
NOTE
The print command selects the appropriate command for postscript or text only
printer as in Figure 3-39. If no printer is set up, then none is displayed in the printer
list.
3-94
68P02900W22-R
GMR-02
Mar 2008
The Edit menu
The Print Table window allows the user to specify the printer output parameters. This window
has:
Two option buttons allowing the following format selection:

Postscript - generates the printer output as a postscript le.
Text - generates the printer output as ASCII text.
The Printers list box which displays the available printer names.
NOTE
For more information about installing printers, refer to Conguring the
printer in Software Release Notes: DataGen (68P02900W76).
The Printer command data eld allows the user to enter a print command for a printer
which is not included in the Printers list box as follows:
Print - sends the MCDF input le to the printer selected in the Printers list.
Cancel - cancels the current operation.
Help - not available in this version of DataGen. The following message is
displayed:
'For DataGen Help please refer to the DataGen manual supplied,
The Edit menu

The Edit menu enables the user to perform general editing operations on the data contained in
the cells of an MCDF le.
Table 3-11 describes the Edit menu options.
NOTE
Before Copying and Pasting cells, create the requisite number of columns and/or
rows needed to contain the data.
68P02900W22-R
3-95
GMR-02
Mar 2008
Fill Cells window
Table 3-11
Edit menu options
Select
To
Cut
Cut the contents of the currently selected cell(s) with the data being retained
in a buffer. However, subsequent cut operations will overwrite the contents of
the buffer. The cut cells are left empty.
Copy
Copy the contents of the currently selected cell(s) into a buffer.
Paste
Copy the contents of the buffer into the currently selected cell(s).
Clear
Delete the contents of the currently selected cell(s). The data is NOT saved
into the buffer.
Fill
Rapidly ll a range of cells with numerical data. For details, refer to the next
section Fill Cells window.
Insert
Insert a new (empty) element (row/column) into the table, either before or
after the currently selected cell or row.
Delete
Delete the contents of an entire row or column, when the appropriate

row/column has been selected.
Undo
Undo the last operation: Cut, Copy, Paste, Clear, Fill, Insert, Delete, Undo,
or Replace.
NOTE
There is a single buffer for Cut or Copy operations. Only the last Cut or Copy
operation is retained in the buffer.
Fill Cells window

Figure 3-40 show the Fill Cells window which is displayed when the Fill option is selected
from the Edit menu in the MCDF input le.
Figure 3-40 Fill Cells window
3-96
68P02900W22-R
GMR-02
Mar 2008
Fill Cells window
The Fill Cells window allows the user to change the contents of multiple cells using:
Four data elds for the cell parameters (refer to Table 3-12).
Four option buttons in a Calculate area (refer to Table 3-13).
Three action buttons (refer to Table 3-14).
Table 3-12 Fill cells - data elds

To
Select
Start
Specify the number of the starting cell.
Increment
Specify the cell number increment (normally 1).
End
Specify the end cell number.
Number of Cells
Table 3-13
Specify the number of cells to be lled.
Fill cells - options

To
Clear
Start
Allow its associated data eld to be modied.
Increment
End
Cell count
Table 3-14
Fill cells - action buttons

To
Select
OK
Cancel
Help
Conrm the displayed parameters and close the Fill Cells window.
Cancel the current operation.
Display the following message:
OLM GUI'
Procedure for lling cells

To modify an MCDF input le using the Fill Cells window, perform the following procedure.
Procedure 3-38
Fill cells
Highlight the rst cell to be lled.
Continued
68P02900W22-R
3-97
GMR-02
Mar 2008
Format menu
Procedure 3-38 Fill cells (Continued)

2
Enter data into the rst cell.
Move the cursor off the cell.
Highlight the rst and succeeding cells to be lled. The data elds in the
Fill Cells window now contain values relating to the highlighted cells, For
example: Start and End.
Select Fill from the Edit menu.
The value from the rst highlighted cell is copied into all the highlighted
cells.
Repeat step 1 to step 6 for the remaining rows or columns to be lled.
Format menu
The Format menu enables the user to perform general search and replace operations.
Table 3-15 shows the denitions of the Format menu options.
Table 3-15 Format menu options

To
Select
Find
Search for the occurrence of a specic character string.
Goto
Go to a specic cell.
Replace
Sort
Unlock
Search for a specic character string and replace with another

string.
Sort certain MCDF tables.
Edit locked MCDF les.
3-98
68P02900W22-R
GMR-02
Mar 2008
Format menu
Find option
Enter the string to search for and select the appropriate search criteria (Exact match or Case
sensitive) for the search. Figure 3-41 shows the Format Find window.
Figure 3-41 Find window
The Find window has:
One data eld
Two Enable buttons
Four Action buttons
The Search For data eld allows the user to specify the character string to nd.
Table 3-16 and Table 3-17 describe the Enable buttons and the Action buttons.
Table 3-16
Find window - enable buttons
Select
To
Exact match
Specify that the string to be searched must be an exact match of the

string entered in the Search For data eld.
Case Sensitive
Specify that the search must be in the same case as the string
entered in the Search For data eld.
Table 3-17 Action button denitions

To
Select
Find First
Find the rst occurrence of the search string.
Find Next
Find the next occurrence of the search string.
Cancel
Cancel the operation.

Continued
68P02900W22-R
3-99
GMR-02
Mar 2008
Format menu
Table 3-17 Action button denitions (Continued)

To
Select
Help

OLM GUI'.
Goto option
Figure 3-42 shows the Goto Cell window which enables the user to move to a specic cell by
entering the appropriate column and row numbers. If the column or row selected lies outside of
the table, the last cell in that row or column is highlighted.
Figure 3-42 Goto Cell window
The Goto Cell window has:
Two data elds (refer to Table 3-18).
Table 3-18
Goto Cell - data elds
Field
Column
Row
Enter
Column number
Row number
Table 3-19 Goto Cell - action buttons

To
Select
OK
Conrm the displayed parameters and close the Goto Cell window.
Continued
3-100
68P02900W22-R
GMR-02
Mar 2008
Format menu
Table 3-19 Goto Cell - action buttons (Continued)

To
Select
Cancel
Help
Cancel the operation and close the Fill Cell window.

OLM GUI'.
Replace option
This option enables the user to perform a search and replace operation on the contents of an
MCDF le using the Replace window shown in Figure 3-43.
Figure 3-43 Replace window
The Replace window has:
Two data elds (refer to Table 3-20).
Two enable buttons (refer to Table 3-21).
Three option buttons (refer to Table 3-22).
68P02900W22-R
3-101
GMR-02
Mar 2008
Format menu
Table 3-20 Replace window - data elds

Field
Enter
Search for
Replace with
The specic character string for

searching.
The replacement character string.
Table 3-21 Replace window - enable buttons

Select
To
Exact match
Specify that the string to be searched must be an exact match of the string
entered in the Search For data eld.
Case sensitive
Specify that the search must be in the same case as the string entered in
the Search For data eld.
Table 3-22 Replace window - option buttons

Select
To
Replace Single
Specify that only the rst occurrence of the search string is to be replaced.
Replace All
Replace Query
Specify that all occurrences of the search string should be replaced.

Display a query message for each search and replace action.
Table 3-23 Replace window - actions

To
Select
OK
Cancel
Help
Conrm the displayed parameters and close the Replace window.

Cancel the operation and close the Replace window.
'For DataGen Help please refer to the DataGen manual supplied,

Sort option
The contents of some tables can be sorted. If a table cannot be sorted, this option is greyed out.
Unlock option
Some of the BSS area denition les contain locked data which must not be altered, although
the DataGen GUI provides the functionality to alter the data.
The Unlock button enables the user to unlock a table and change the locked values. A warning
is displayed to this effect.
3-102
68P02900W22-R
GMR-02
Mar 2008
MCDF key equivalents
MCDF key equivalents

Table 3-24 describes the key equivalents that are available when working on MCDF tables.
Table 3-24 Hot keys for MCDF

Action
Hot keys
load
Ctrl-O
save
Ctrl-S
saveAs
Ctrl-A
print
Ctrl-P
restart
Ctrl-R
quit
Ctrl-E
cut
Ctrl-X
copy
Ctrl-C
paste
Ctrl-V
clear
Ctrl-B
ll
Ctrl-F
insert Before
Ctrl-J
insert After
Ctrl-I
delete
Ctrl-D
undo
Ctrl-U
68P02900W22-R
3-103
GMR-02
Mar 2008
Using the Topology Viewer
Introduction to the Topology Viewer
CAUTION
Selecting the Topology option causes the DataGen GUI to core if the GMS licence
(KEYS) is not purchased.
The Topology Viewer allows the user to display a graphical representation of a BSS Area
showing a BSC and its associated BTSs. Two topologies can be displayed at the same time
for comparison purposes.
The viewer has four data elds which show the Base Site System Description information and
a Menu bar with Cage, MMI, Path File and Increase/Decrease magnication options. The
File menu has an Exit option only.
3-104
68P02900W22-R
GMR-02
Mar 2008
Invoking the Topology Viewer
Invoking the Topology Viewer

To display the Topology Viewer (as in Figure 3-44), either select Topology from the Services
menu or click the Topology icon on the Services window.
Figure 3-44
Topology Viewer
68P02900W22-R
3-105
GMR-02
Mar 2008

Use the buttons on the menu bar shown in Figure 3-45 to access the topology viewer options.
Figure 3-45 Topology Viewer menu bar
The topology viewer options are described in greater detail below.
Cage hardware conguration button

The Cage selection on the menu bar and the Cage Number window allow the user to display
cage congurations for a BSC and BTSs displayed in the Topology Viewer window.
To display a cage conguration, perform the following procedure.
Procedure 3-39 Display a cage conguration
Click the Cage Hardware Conguration button on the Topology Viewer

window. Refer to Figure 3-45.
Click a BSC or BTS symbol (only green and yellow symbols are valid).
In the displayed Cage Number window, select the cage number. Refer
to Figure 3-46.
A Cage Description window is displayed as shown in Figure 3-47.
Figure 3-46 The Cage Number window
3-106
68P02900W22-R
GMR-02
Mar 2008
Cage hardware conguration button
The Cage Description window

The main section of the window contains a graphical representation of the layout of the
hardware within the selected cage. If required, this main section can be cut and printed,
enabling users to produce a hard copy showing cabinet congurations.
The Cage Description window has six data elds which show the Cage Description information.
The buttons on the left-hand side of the window are not enabled. The message window shown
at the bottom is currently unused.
Select the Exit option from the File menu to close the window.
Figure 3-47 The Cage Description window
68P02900W22-R
3-107
GMR-02
Mar 2008
The MMI button
The MMI button

The MMI button enables the user to regenerate an MMI script for the current site. This
button performs exactly the same function as the MMI button located on the Service window,
described in the section The Service window on page 3-56.
Path File button

This button uses a text editor to display the path or connectivity information. For example:
PATH 0 = Site: 0 [MSI 2,0] connected to Site: 7 [MSI 3,0].
A copy of the le is stored in the users home directory:
/home/<username>/PathFile
If the le exists, a backup of the original le is made.
Increase magnication button

This button increases the magnication factor applied to the Topology Viewer to allow greater
denition.
Decrease magnication button

This button decreases the magnication factor applied to the Topology Viewer.
3-108
68P02900W22-R
GMR-02
Mar 2008
Generating a hardware report
Generating a hardware report
Overview of hardware reports

Users can generate a hardware report containing a list of all the devices names, function
names, slot numbers, and Id devices within each cage per site. A default text editor is used
to open the report.
Procedure for generating a hardware report

To generate a hardware report, perform the following procedure.
Procedure 3-40
Generate a hardware report
Open the Service window (refer to Opening a BSS area on page 3-39 for
details).
From the Service window, select Generate Hardware Report from the
Services menu.
NOTE
The Generate Hardware Report option is available only if the
BSS area contains data.
The following message is displayed in a status window:

Generating Hardware Report for Base Station System
When complete, a Conrmation window is displayed.
3
Click OK to continue.
Continued
68P02900W22-R
3-109
GMR-02
Mar 2008
Procedure for generating a hardware report
Procedure 3-40 Generate a hardware report (Continued)

4
To view the report, select Hardware Report from the Edit menu. The default
text editor displays the report as in the example shown in Figure 3-48. Refer
to Administration tasks on page 3-11 for details on how to dene a default
editor.
Figure 3-48 Viewing a hardware report
Close the report by using the appropriate command for the text editor in use.
3-110
68P02900W22-R
GMR-02
Mar 2008
Converting a database script le to a CM database object le
Converting a database script le to a CM database

object le
Overview of conversion
Conversion of a database script le to a database object le can be performed either on the
DataGen platform or in the BSS.
Producing a CM database object using SYSGEN mode

This process is normally carried out on a Test BSS which is not connected to the live network.
The Test BSS must rst be entered into SYSGEN Mode. Once this is done, the Database Script
File can be downloaded to the BSS through a TTY interface connected to the Master GPROC.
The BSC then processes the information sent to it and produces a CM Database Object from this
information. The object le has the extension .002.
The CM database object must then be uploaded to the OMC so that it is available for
downloading to the live network when it is required.
Producing a CM database object using the DataGen binary

object compiler
The Binary Object Compiler is used by DataGen to convert a script le into a CM database object.
If the software version is 1.6.0.0, then the CM database object is automatically compressed. As
a secondary function of compiling the object, the compiler also validates the database.
NOTE
As a requirement for running the binary object compiler, install the Options Object
into DataGen, during the installation phase. The object compiler reads the Options
Object to ascertain what additional functionality the network supports. Refer to
Installing the options object in Software Release Notes: DataGen (68P02900W76)
for details.
The binary object compiler is executed either from the Services menu, or by clicking the
Compile icon shown in Figure 3-49.
68P02900W22-R
3-111
GMR-02
Mar 2008
Producing a CM database object using the DataGen binary object compiler
Figure 3-49 Binary Object Compiler window
The Compiler does a validation check on all parameters. If any errors are detected during the
Compile process, a message is generated in the main window. The errors should be corrected
using the Table Controller. Editing of the script using the MMI Script Generate command does
not update the Informix database, as it is in an output le directory.
The Binary Object Compiler window has two data elds which display the BSS Area information and the Status of the compiler. There are two action buttons: Run Compiler and Exit.
The File menu has three selections:
Run Compiler
Remove Lock File
Exit
3-112
68P02900W22-R
GMR-02
Mar 2008
Producing a CM database object using the DataGen binary object compiler
NOTE
All binary object les (.002) are compressed. Refer to Command Line tools,
Compress /uncompress binary object les for details on how to uncompress les.
To activate the compiler, click the Compile button or select the Compile option from the
File menu.
68P02900W22-R
3-113
GMR-02
Mar 2008
Exporting object les to the OMC
Exporting object les to the OMC
Overview of exporting object les

After a binary object is generated, it can be downloaded to the OMC. The three methods for
exporting object les are:
Export multiple binary object les to the OMC
Export a single binary object le to the OMC
Export binary object les from the OLM to the OMC
NOTE
For more information about the requirements for this type of operation,
refer to DataGen-OMC Integration in Software Release Notes: DataGen
(68P02900W76).
Exporting multiple binary object les

To export multiple binary object les to the OMC, perform the following procedure.
Procedure 3-41 Export multiple binary object les
Ensure that the export path is set to the desired directory. For example,
/usr/omc/DataGen/dg/<Country>/<BSS Area Name>/<export>
Refer to Administration tasks on page 3-11, customizing parameters for
details on how to dene a path to an export directory.
From the Service window (refer to Figure 3-23), select the Export option
from the File menu.
Click OK in the displayed message window.
At the OMC, ensure that a sub directory exists in the database

directory with the same name as the BSS Area being exported from
DataGen. If a sub directory does not exist, create one. For example:
/usr/omc/ne_data/dbroot/BSS/BSSspecic/<BSS Area Name>
Continued
3-114
68P02900W22-R
GMR-02
Mar 2008
Exporting a single binary object le
Procedure 3-41 Export multiple binary object les (Continued)

5
At the OMC, invoke Utilities OMC Database Utility,

then select the Load Database option.
A load_db utility is invoked which opens a new Xterm window and presents
four load source options.
Select option 4 (User denable source and location) and input the requested
information.
After the download, check that the database object is located in the database
directory under the specied BSS Area name. For example:
/usr/omc/ne_data/dbroot/databases/<BSS Area Name>/<db_load
name>
NOTE
The setenv COUNTRY and COUNTRY_CODE variables need
to be set at the OMC, and must match the values set in the
country administrator (Country) table, in order for the available
congurations to be displayed.
Exporting a single binary object le

To export one object le that has been created using the DataGen GUI to the OMC, perform the
following procedure.
Procedure 3-42 Export a single binary object le
Verify that the binary object le is in the correct directory. For example:
/usr/omc/DG/dg/<Country>/<BSS Area Name>/conf<n>/002
Where n is replaced by the conguration number.
At the OMC, ensure that a sub directory exists in the database directory with
the same name as the BSS Area which is being exported from DataGen.
If one does not exist, create one. For example:
/usr/omc/ne_data/dbroot/BSS/BSSspecic/<BSS Area Name>
At the OMC, invoke Utilities OMC Database Utility,

then select the Load Database option.
Select option 2 (DataGen), then input the requested information.

Continued
68P02900W22-R
3-115
GMR-02
Mar 2008
Exporting OLM binary object les to the OMC
Procedure 3-42
5
Export a single binary object le (Continued)
directory under the specied BSS Area name.
NOTE
The setenv COUNTRY and COUNTRY_CODE variables need
to be set at the OMC, and must match the values set in the
country administrator (Country) table, in order for the available
congurations to be displayed.
Exporting OLM binary object les to the OMC

To export multiple binary object les to the OMC from the Ofine MIB, perform the following
procedure.
Procedure 3-43 Export multiple binary object les
At the OMC, invoke Utilities OMC Database Utility.
Select the Load Database option.

Select option 3 (Off-Line MIB), then input the requested information.
directory under the specied BSS Area name. For example:
/usr/omc/ne_data/dbroot/databases/<BSS Area Name>/<db_load
name>
3-116
68P02900W22-R
GMR-02
Mar 2008
Difference Reporter
Difference Reporter
Introduction to the Difference Reporter

Difference reports between sites and site elements for BSS areas can be generated using the
DIFF option from the DataGen main menu (refer to Figure 3-1).
Two different BSS Areas are chosen and a comparison of both the areas is started. A viewable
report is generated in which the sites common to both the areas are listed. Differences between
the two BSS Areas for each site are also listed. In addition, the report indicates the areas where
no differences between the sites are found.
The Difference Reporter window

Select DIFF from the DataGen main menu to display a Difference Reporter window as shown
in Figure 3-50.
Figure 3-50 Difference Reporter window
The Difference Reporter window displays the details of two BSS areas which can be selected
for comparison using the BSS Area Details window.
68P02900W22-R
3-117
GMR-02
Mar 2008
Select BSS Area Details window
Using the Difference Reporter window

The Difference Reporter main window has two sets of four user input areas labelled as:
Country
BSS Name
Version
Cong
The action buttons on the Difference Reporter window are used as follows:
Use
Set
Compare
To
Display a BSS Area Details window for Area 1 or Area 2
comparison (left or right-hand option).
Begin the comparison between Area 1 and Area 2.
View
View the Report File.
Exit
Close and exit the DIFF function.

The Select BSS Area Details window allows the user to select two BSS areas for comparison.
To open the window, select the left-hand or right-hand Set button for the relevant BSS area in
the Difference Reporter window. The Select BSS Area Details window is then displayed.
Refer to Figure 3-51.
Figure 3-51 Select BSS Area Details window
When the window is displayed for the rst time, the BSS Name, Software Version, and Cong
Version list boxes are blank. Only the Country Name list box contains a list of countries.
3-118
68P02900W22-R
GMR-02
Mar 2008
Using the Select BSS Area Details window

The Select BSS Area Details window has four user selectable areas:
Country Name
When Country Name is selected, a list of BSS names in the BSS area list is displayed.
BSS Name
When a BSS Name is selected, the Software Versions in the next list box are displayed.
Software Version
When a Software Version is selected, the conguration numbers in the last list box are
displayed.
Cong Version
Select the conguration number. The scroll bar can be used to step through the list of
conguration versions for a specied BSS area.
The action buttons on the Select BSS Area Details window are used as follows:
Use
Cancel
Done
To
Cancel the operation and close the window.
Enter the selected details into the Difference
Reporter window for BSS Area 1 and Area 2.
68P02900W22-R
3-119
GMR-02
Mar 2008
Difference Reporter Information window
Difference Reporter Information window

The Information window is displayed after the user presses the Compare button in the
Difference Reporter main window to begin the comparison. The Information window displays
the progress of the Difference Reporter as in Figure 3-52.
Figure 3-52 Difference Reporter - Information window
Using the Information window

The Difference Reporter Information window has a text area which displays the progress of
the Difference Reporter and two action buttons which are used as follows:
Use
To
View Report
Display an Information window.
Close
Close the Information window.
3-120
68P02900W22-R
GMR-02
Mar 2008
Difference Reporter Report window
Difference Reporter Report window

The results of the Difference Reporter process are displayed in a Report window as shown
in Figure 3-53.
Figure 3-53 Difference Reporter - Report window
Using the Report window

The Report window has a text box which displays Difference Report output. As reports can
be large, a horizontal scroll bar and a vertical scroll bar can be used to view different parts of
a report.
68P02900W22-R
3-121
GMR-02
Mar 2008
Upgrader
Upgrader
Overview of the Upgrade function

The Upgrade function allows the user to upgrade an earlier version of DataGen to a more recent
software release. This option can be invoked from the DataGen main menu by selecting the
UPG option (refer to Figure 3-1).
The existing BSS area is copied to a new BSS area. The MMI script changes and modications
to parameter values are applied to this new area.
The following upgrade paths are supported:
1.7.4.0 to 1.7.6.0
1.7.4.0 to 1.8.0.0
1.7.6.0 to 1.8.0.0
Refer to Software Release Notes: DataGen (68P02900W76) for more information about the
upgrades supported.
Upgrade BSS Area window

When UPG is selected from the DataGen main menu, the Upgrade BSS Area window is
displayed as in Figure 3-54. This allows the user to select the BSS Area characteristics to be
upgraded. The Target Version is entered automatically by DataGen.
Figure 3-54 Upgrade BSS Area window
3-122
68P02900W22-R
GMR-02
Mar 2008
Upgrade BSS Area window
NOTE
To change parameters in the BSS area prior to the upgrade, modify the MCDF les.
Refer to Using the Generic Table Editor (GTE) on page 3-89 for details. Do not modify
the BSS area by editing and compiling the MMI script, as any changes made will be
lost after the upgrade.
The Upgrade BSS Area window has:
Six list boxes (refer to Table 3-25).
Two action buttons (refer to Table 3-26).
Table 3-25 Upgrader - list boxes

To
Select
Country Name
BSS Area
Software Version
Display a list of country names.

Display a list of available BSS Areas.
Display a list software versions.
Conguration
number
Display a list of Conguration numbers for the software versions.
Target Version
Display the available target versions automatically.
Target Cong.
Display a list of target Conguration numbers.
Table 3-26 Upgrader - action buttons

To
Select
Upgrade
Close
Start the upgrade process and display a Status window.

Cancels the operation and close the Upgrade BSS Area window.
Area Comment eld

By default, the area comment eld contains the following information:
Upgraded from <BSS Area><Configuration NO>
Where
Is
BSS area
Name of the original BSS area.
Conguration No
Conguration number of the original BSS area.
68P02900W22-R
3-123
GMR-02
Mar 2008
Upgrading a BSS Area

To upgrade a BSS Area, perform the following procedure.
Procedure 3-44 Upgrade a BSS Area
Select the UPG from the DataGen Main menu (refer to Figure 3-1). This
displays the Upgrade BSS Area window (refer to Figure 3-54).
Select a Country Name in the list box to display a list of BSS areas.
Select a BSS Area to display a list of Software Versions.
Select the required software version which is to be upgraded: a list of

associated conguration numbers is displayed.
Select a Conguration No.
Select a Target Version which is displayed in the list box automatically. To

obtain a target conguration number automatically, do not select a number
from the Target Cong. list. DataGen then assigns the next available
conguration number.
NOTE
To overwrite an existing conguration, select the number from
the Target Cong. list.
7
If the information displayed in the list box data elds is correct, click
Upgrade. If the BSS area is locked by another user, an information window
is displayed as shown in Figure 3-55. If this message is not displayed,
proceed to step 9.
Figure 3-55 Locked information window
Continued
3-124
68P02900W22-R
GMR-02
Mar 2008
Procedure 3-44 Upgrade a BSS Area (Continued)

8
Click OK to override the lock or Cancel to return to the Upgrade BSS

Area window.
NOTE
Information on the user holding the lock can be found in the
DataGen.log le. Refer to Administration tasks on page 3-11
for details.
A Status window is displayed as shown in Figure 3-56.
Figure 3-56 Successful upgrade Status window
Continued
68P02900W22-R
3-125
GMR-02
Mar 2008
Upgrade multiple BSS areas
Procedure 3-44 Upgrade a BSS Area (Continued)

The following message is displayed in the Status window if the upgrade was
successful:
REPORT:- Upgrade completed successfully.
REPORT:- Starting gcmd for <Country:BSS_Area:Configuration_No>.
REPORT:- Gcmd completed without error.
NOTE
Wait until Gcmd has completed before closing the window.
9
Click Close to return to the Upgrade BSS Area window when Gcmd is
completed. If the upgrade is unsuccessful, the Status window displays the
following information:
REPORT:- Upgrade completed.
REPORT:- Please modify the area as detailed in the warnings.
REPORT:- Starting gcmd for <Country:BSS_Area:Configuration_No>
Gcmd completed without error
Refer to the section Resolving upgrade problems on page 3-126 for details.
Upgrade multiple BSS areas

It is not necessary to wait for the upgrade to be completed before starting to upgrade another
BSS area.
To upgrade a second BSS Area, select the Upgrade BSS Area window. Refer to Procedure 3-44
and carry out step 3 to step 9.
Resolving upgrade problems

During the upgrade process, problems may occur in the BSS area that prevent the successful
upgrading. The Status window identies any problems occurred.
Depending on the nature of the problem(s), modications can be done in one of two ways:
Modify MCDF les
Modify MMI scripts
To resolve the upgrade problem(s), perform the following procedure.
3-126
68P02900W22-R
GMR-02
Mar 2008
Resolving upgrade problems
Procedure 3-45 Resolve upgrade problems
If the upgrade is unsuccessful, for example, if changes are required in a

script, the following messages are displayed in the status window:
REPORT:REPORT:REPORT:REPORT:-
Upgrade completed
Please modify the area as detailed in the warnings.
Starting gcmd for <Country:BSS_Area:Configuration_No>.
Gcmd completed without error.
Click Close in the Status window to return to the Upgrade BSS Area
window and Cancel to return to the DataGen main menu (refer to
Figure 3-1).
NOTE
Wait until Gcmd has completed before closing the window.
Modify MCDF les

Use the following procedure to modify the MCDF les.
Procedure 3-46
Modify MCDF les to resolve upgrade problems
Open the target BSS area from the DataGen main menu. Refer to Opening a
BSS area on page 3-39 for details.
From the Service window, use the Table Controller to modify the MCDF
les and insert them back into the Informix database. Refer to Using the
Table Controller on page 3-78 for details.
Generate an MMI script by clicking the MMI button or by selecting

Generate Script from the Services menu. Refer to Generating a database
script le on page 3-70 for details.
Compile the created script le by selecting the COMPILE button or

selecting Object Compiler from the Services menu. Refer to Converting a
database script le to a CM database object le on page 3-111 for details.
68P02900W22-R
3-127
GMR-02
Mar 2008
Overview of DARBC and Enhanced XBL
Modify MMI script

To modify the MMI script, perform the following procedure.
Procedure 3-47
Modify MMI script to resolve upgrade problems
Open the target BSS areawindow from the DataGen main menu. Refer to
Opening a BSS area on page 3-39 for more details.
View the MMI script le with a text editor and make the necessary changes.
Refer to Generating a database script le on page 3-70 for more details.
From the Services menu, compile the script le to generate a new BSS
binary object les. Refer to Converting a database script le to a CM
database object le on page 3-111 for more details.
Export the binary object le from the DataGen Directory structure. To

create an export directory, refer to Administration tasks on page 3-11 for
more details. From the Service window, select File Export Object.
From the Service window, select File Exit.
Create a BSS area and overwrite the existing conguration number. Refer to
Creating a BSS area on page 3-34 for more details.
Import the exported binary object le from the Service window. Refer to the
section Import object in The Service window on page 3-56 for more details.
Revgen the binary object from the Service window to update the BSS area
in DataGen. Refer to Activating Revgen in Converting a CM database
object le to a script le on page 3-65 for more details.
Overview of DARBC and Enhanced XBL

The Dynamic Allocation of RXCDR to BSC circuits (DARBC) alters the role of the terrestrial
circuit portion of the A-interface between a BSC and RXCDR (known as Ater channels), so
that the Ater channels between the Remote Transcoder (RXCDR) and BSC are allocated as
the channels are needed, rather than statically assigning the channels to a specic Circuit
Identier Code (CIC).
The term XBL, refers to a Base Site Controller (BSC) transcoder (RXCDR) link. The new
Enhanced XBL (EXBL) feature provides robust communication between the BSC and the
RXCDR. The basis of the EXBL feature is to provide a generic messaging system between the
BSC and the RXCDR. This generic messaging system is used to suit both current operator
needs and the needs of future BSS features.
Dynamic Allocation of RXCDR-BSC Circuits (DARBC) and Enhanced XBL (EXBL) have
interdependent functionality.
For further technical details, refer to Technical Description: BSS Implementation
(68P02901W36).
3-128
68P02900W22-R
GMR-02
Mar 2008
Batch processing of binary object les
Batch processing of binary object les
Overview of batch processing

Batch processing of binary object (.002) les is carried out by selecting Batch from the DataGen
main menu. The following functions can be carried out on one or more binary object les:
Revgen
Multiple binary object les can be selected and converted into a DataGen script le.
Upgrade
Multiple binary object les can be selected and upgraded to GSR8 version of DataGen.
Compile
Multiple scripts les can be selected and compiled to form binary object les.
Export MCDF Files and or Copy Area

When the Revgen or upgrade batch option is selected, it is also possible to automatically
copy and or export the new areas.
NOTE
A default BSS Area name is derived from the binary object name minus the .002
extension. For example, BSS12.002 will become BSS area BSS12. It is advisable
to use meaningful binary names.
68P02900W22-R
3-129
GMR-02
Mar 2008
Revgen multiple binary object les

To Revgen multiple binary object les, perform the following procedure.
Procedure 3-48 Revgen multiple binary object les
Start DataGen from an Xterm window and select BATCH from the DataGen
main menu (refer to Figure 3-1). The Batch Tool window is displayed.
Select the Revgen option (as shown in Figure 3-57).
Figure 3-57 Batch Tool window with Revgen selected
To export the Revgened areas automatically, click Export MCDF Files; else
proceed to step 4.
To copy the Revgened areas automatically, click Copy Area; else proceed
to step 5.
To locate the directory where the binary object les are located, enter the
path in the Filter eld and click the Filter button. All les are Revgened in
the directory. To Revgen only one le in the directory, select the required
le from the Files list box.
NOTE
If les other than binary object les exist in the directory, then a
warning message is generated in the Batch monitoring window. A
default import path can be dened. Refer to Dening environment
variables on page 3-4 for details.
Continued
3-130
68P02900W22-R
GMR-02
Mar 2008
Procedure 3-48 Revgen multiple binary object les (Continued)

6
Click OK.
On the Batch Tool window, select the following:
Country (from the Country Name list)
Software version (from the Software Version list)
Enter the starting conguration number in the Start Cong eld and click
Execute. If the number exists, DataGen assigns the next available number.
NOTE
To obtain a conguration number automatically, do not enter a
number. DataGen automatically assigns the lowest conguration
number available.
A Conrmation window is displayed as in Figure 3-58. Click OK to

continue.
Figure 3-58 Revgen batch conrmation window
NOTE
If all the essential elds are not completed, an error window is
displayed stating: All elds are not lled in. Click OK to return to
the Batch Tools window.
Continued
68P02900W22-R
3-131
GMR-02
Mar 2008
Procedure 3-48 Revgen multiple binary object les (Continued)

9
The Batch monitor window is displayed as Figure 3-59. The Batch

monitor can be left open to monitor the batch processing.
Figure 3-59 Revgen Batch monitor window
NOTE
If the Close button is selected, batch processing continues in the
background. The outcome can be found in the report le which is
located in the selected binary object le directory. The report has a
Date and Time stamp, for example:
batch_ddmmyyyyhhmmss.rpt.
3-132
68P02900W22-R
GMR-02
Mar 2008
Upgrade multiple binary object les

To upgrade multiple binary object les, perform the following procedure.
Procedure 3-49
Refer to the procedure Revgen multiple binary object les and repeat
step 1. This displays the Batch Tool window (refer to Figure 3-57).
Select the Upgrade option.
To export the upgraded areas automatically, click Export MCDF Files; else
proceed to step 4.
To copy the upgraded areas automatically, click Copy Area; else proceed
to step 5.
To locate the directory where the binary objects les are located, enter the
path in the Filter eld and select the Filter button. All les are upgraded
in the directory. To upgrade only one le, select the required le from the
Files list box.
NOTE
If les other than binary object les exist in the directory, then
an error message is generated in the Batch monitor window.
A default import path can be dened. Refer to Dening
environment variables on page 3-4 for details.
6
Click OK.
On the Batch tool window, select the following:
Country (from the Country Name list)
Software version (from the Software Version list)
NOTE
All the binary object les in the directory must be of the
same software version for the upgrade to be successful.
8
Select the target version to upgrade to from the Target Version list.
Continued
68P02900W22-R
3-133
GMR-02
Mar 2008
Compile multiple MMI scripts
Procedure 3-49
9
Upgrade multiple binary object les (Continued)
Enter the starting conguration number in the Start Cong: eld and click
Execute. If the number exists, DataGen assigns the next available number.
NOTE
To obtain a conguration number automatically, do not

enter a number as DataGen assigns the lowest conguration
number available.
From the Edit menu on the Service window it is possible to

view the upgrade log le. Refer to The Service window on
page 3-56, Edit menu for details.

To compile multiple MMI scripts, carry out the following procedure.
Procedure 3-50 Compile multiple MMI scripts
Refer to the procedure Revgen multiple binary object les and repeat
step 1. This displays the Batch Tool window (refer to Figure 3-57).
Select the Compile option.
To locate the directory where the script les are located, enter the path in the
Filter eld and select the Filter button. All les are compiled in the directory.
To compile only one le from the directory, select it from the Files list box.
NOTE
If les other than script les (ASCII text) exist in the directory, then
a warning message is generated in the Batch monitor window.
A default import path can be dened. Refer to Network
Expansion - Dening environment variables for details.
4
Click OK.

Continued
3-134
68P02900W22-R
GMR-02
Mar 2008
Procedure 3-50 Compile multiple MMI scripts (Continued)

6
NOTE
All script les must be the of same software version and the correct
compiler version must be selected, else errors are generated.
7
Click Execute.
A Conrmation window displays a message similar to the following:
Compiling ALL files from selection:
/fanned/user43/users/mcdermjo/dev/scripts/1800c/scripts/temp/
Select OK to proceed or CANCEL to return.
Click OK to continue. The Batch monitor window is displayed, refer to

Figure 3-60. This window can be left open to monitor the batch processing.
Figure 3-60 Compile Batch monitor window
Continued
68P02900W22-R
3-135
GMR-02
Mar 2008
Procedure 3-50
Compile multiple MMI scripts (Continued)
NOTE
If the Close button is selected, batch processing continues in the
background. To view the outcome, check the report le which is
located in the directory where the scripts reside.
Once the batch process is complete, the following les are generated for each script compiled:
Binary object le (.002)
Report le (.rpt)
The les are located in the directory where the scripts reside.
NOTE
If any of the scripts fail to compile, then only a report le is generated. This can
be used to identify the problem.
3-136
68P02900W22-R
GMR-02
Mar 2008
Chapter
4
Operating the Ofine MIB
68P02900W22-R
Mar 2008
4-1
GMR-02
Introduction to the Ofine MIB
Introduction to the Ofine MIB

A Conguration Management (CM) database object is a binary le. Until the development of
DataGen, it was possible to create a binary le only by downloading an ASCII format script le
to a BSS in SYSGEN mode.
Prior to GSR4 it was possible to modify a single BSS binary le through MCDF tables or to
modify MMI scripts, using DataGen. Currently, DataGen allows the user to modify and carry out
Radio Frequency (RF) planning on multiple BSS binary les through the Ofine MIB (OLM)
which has a graphical user interface (GUI).
Users can run only one Ofine MIB at a time. However, multiple GUIs for the same MIB may be
displayed and tasks may be carried out by several different users.
The task list orders the tasks in the sequence that they are routinely performed within the OLM.
Additional OLM features describe extra functions that are performed infrequently.
NOTE
Parameters such as circuits, channels, statistics (enabling/disabling/thresholds) and
time slot reservations can not be modied using the OLM GUI.
Task list prior to using OLM GUI

The following list describes the general procedures which should be carried out before using
the OLM GUI:
Import BSS binary les from the OMC into DataGen. Refer to the procedure DataGen
- OMC Integration in the DataGen/OLM Clean Install Guide included in the manual
Software Release Notes: DataGen (68P02900W76).
The upgrade function is carried out from the front panel DataGen window, not from the
OLM GUI. For details, refer to Upgrader in Chapter 3 Operating DataGen.
Circuits, channels, statistics (enabling/disabling/thresholds), time slot reservations must

be modied through MCDF tables or MMI scripts. The scripts are compiled to create BSS
binary object les. For details, refer to Chapter 3 Operating DataGen.
4-2
68P02900W22-R
GMR-02
Mar 2008
Task list for using the OLM GUI
Task list for using the OLM GUI

The following lists, in sequence, the procedures that are normally performed using the OLM GUI:
Start the OLM from the DataGen front panel.
Create a network conguration.
From the Navigation Tree of the OLM, import the BSS binary les from DataGen into the
network.
NOTE
RXCDRs binary les can be added but channels cannot be modied or equipped.
Only hardware changes can be made.
Audit the network. The OLM must reect the current conguration of the BSS binary les.
Modify the BSSs through the Navigation Tree and Detail Views.
Perform CellXchange and implementing changes for multiple BSSs.
Save and verify all NEs.
Export BSS binary les to the OMC. Refer to Exporting object les to the OMC in
Chapter 3 Operating DataGen.
Delete the network conguration in the OLM.
Further information
Further information on using the OLM can be found in Online Help.
Additional OLM tasks

To carry out additional tasks such as importing binary les from tape into the OLM directory
(Realign Network), refer to Additional OLM features on page 4-56.
NOTE
These tasks are not routine functions and should be carried out only by the
administrator or creator of the Ofine MIB network.
68P02900W22-R
4-3
GMR-02
Mar 2008
Levels of users
Levels of users
The four levels of users are:
Administrator group.
Owner and creator of the Ofine MIB network.
First user to launch the Ofine MIB network.
Subsequent GUI user of an Ofine MIB network that is currently in use.
Table 4-1 shows the administrative tasks that the various users can perform on the Ofine MIB.
Table 4-1 Administrative tasks and user types

User Type
Administrative tasks
Shut down OLM
on last GUI exit
Force shutdown
OLM
Reinitialize OLM
network
Delete OLM
network cong.
Admin Group
Owner of
OLM network
conguration
First to launch
network
conguration
GUI
Troubleshooting and other tasks

If problems are encountered when operating the Ofine MIB, refer to the section
Troubleshooting the OLM on page 4-81 to help resolve the problems.
Many administrative tasks are located from the Network Conguration selection window
under the menu option Admin (refer to Figure 4-1). For more information about these tasks,
refer to:
Reinitialize database procedure on page 4-86
Introduction to the force shutdown feature on page 4-84
Compress or uncompress an OLM network on page 4-79
OLM environment variables

The environment variable OLM_VERIFY_DB_LOGGING can be used to identify the relevant
sites and cells that errors apply to when verifying an NE database. Refer to Verify and save
network on page 4-46 for details on this procedure.
4-4
68P02900W22-R
GMR-02
Mar 2008
Using the cmutil.olm command
To enable the environment variable, perform the following procedure.
Procedure 4-1
Enable OLM_VERIFY_DB_LOGGING environment variable
Edit the le olmProcCong.csh by executing the following commands:

cd /usr/omc/current/configvi olmProcConfig.csh
Insert the following line:

setenv OLM_VERIFY_DB_LOGGING ON
Save the le, then exit the vi editor.
Exit and restart the OLM for the variable to be applied. Refer to
Starting/exiting the OLM GUI on page 4-9 for more information.
Using the cmutil.olm command

On the OLM, the command cmutil.olm is used, while on the OMC, the command cmutil is
used. When using cmutil.olm, the environment variable DBNAME must be set to the name of
the network on which the operation is to be performed, for example: set DBNAME = network1.
Other than that, cmutil.olm should perform similarly to cmutil.
For more information about using the cmutil command, refer to the manual Installation and
Conguration: GSM System Conguration (68P02901W17).
68P02900W22-R
4-5
GMR-02
Mar 2008
Starting/creating a network conguration in the OLM
Starting/creating a network conguration in the OLM
Introduction to network conguration

This section describes the procedures to:
Launch the Ofine MIB from the DataGen main menu.
Create a network conguration.
Starting the OLM

To start the OLM from the DataGen main menu, perform the following procedure:
Procedure 4-2 Starting the OLM
Click the OLM button, refer to DataGen - startup and shutdown in the
Chapter 3 Operating DataGen A status message is displayed.
Click OK to continue. The OLM Network Congurations window then opens

as shown in Figure 4-1.
Creating a network conguration

To create a network conguration, perform the following procedure.
Procedure 4-3 Create a new network conguration
Select the Create button or select Edit Create from the menu bar (refer
to Figure 4-1). The OLM Network conguration creation window is then
Continued
4-6
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-3 Create a new network conguration (Continued)

Figure 4-1 Ofine MIB Network Congurations window
Figure 4-2
OLM Network conguration creation window
Continued
68P02900W22-R
4-7
GMR-02
Mar 2008
Procedure 4-3 Create a new network conguration (Continued)

2
Enter the name of the new network conguration and press the Tab key.
NOTE
The name can not start with a number or include a hyphen.
3
Enter the Mobile Country Code (MCC) and press the Tab key.
Enter the Mobile Network Code (MNC). The RDN Class Network is
displayed.
Select Additional Information and enter a brief description of the network.

(But it is not mandatory to enter this information).
Select File Create from the menu bar to create the network conguration.
Select File Save from the menu bar to save the conguration.
Select File Close from the menu bar to close the window and return to the
OLM Network Congurations window. The list is updated and now contains
the new network conguration name.
NOTE
To edit the Additional Information eld, select Network
Detailed View from the Navigation Tree. Refer to Modifying the
network conguration from the Navigation Tree on page 4-37 for
more details.
4-8
68P02900W22-R
GMR-02
Mar 2008
Starting/exiting the OLM GUI
Starting/exiting the OLM GUI
Introduction
The following procedures are described in this section:
Starting the OLM GUI
Exiting the OLM GUI
Shutting down the OLM

To start the OLM GUI, perform the following procedure.
Procedure 4-4 Start the OLM GUI
From the DataGen main menu, select the OLM button, refer to DataGen startup and shutdown in Chapter 3 Operating DataGen. The Ofine MIB
(OLM) Network Congurations window is displayed as in Figure 4-1.
Select the required network conguration name from the OLM Network
Congurations list. The selection is highlighted in black.
NOTE
By default, the rst network conguration is selected.
3
Select Edit Open from the menu bar (alternatively, click the Open button
or double click with left mouse button) to open the OLM GUI.
Continued
68P02900W22-R
4-9
GMR-02
Mar 2008
Procedure 4-4
4
Start the OLM GUI (Continued)
A Conrmation window displays a warning as shown in Figure 4-3. Click

OK to continue or Cancel to exit without opening the OLM GUI.
Figure 4-3 Starting the OLM - conrmation window
While the OLM is starting, a status window displays the following message:
Initialising...Please wait...
Starting the MIB process...
Initialising the Network Elements...
Starting the GUI application...
NOTE
It is possible to open only one network conguration at a time.
However, the GUI for the opened network can be displayed on
several machines. The InUse column on the OLM Network
Congurations window identies the number of users that
currently have the network conguration GUI open (refer to
Figure 4-4).
Continued
4-10
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-4
Start the OLM GUI (Continued)
Figure 4-4 Opening a network conguration - status window
The OLM GUI opens and the front panel is displayed (refer to Figure 4-5).
Refer to the section Front panel icons on page 4-15 for more information
about the OLM front panel.
Figure 4-5 Ofine MIB front panel
68P02900W22-R
4-11
GMR-02
Mar 2008
Exiting the OLM GUI
Exiting the OLM GUI

To exit the OLM GUI, click Exit on the OLM front panel (refer to Figure 4-5).
A Conrmation window is displayed (Figure 4-6).
Click OK to exit the GUI and return to the OLM Network Congurations window.
Figure 4-6 GUI exit - conrmation window
NOTE
The message shown in Figure 4-6 is displayed if the network conguration GUI is
opened by more than one user.
NOTE
The last user to exit the GUI shuts down the Ofine MIB.
4-12
68P02900W22-R
GMR-02
Mar 2008
Perform the following steps to exit and shut down the OLM.
Procedure 4-5 Exit and shut down the OLM
Click Exit on the OLM front panel (refer to Figure 4-5). A Conrmation
window is displayed as shown in Figure 4-7.
Figure 4-7 OLM shutdown conrmation window
Click the Save Exit button. If no errors exist within the network, the
Conrmation window closes and the OLM shuts down. If errors are
detected, proceed to step 3.
For each Network Element where errors exist, a Warning window is

displayed, detailing the location and errors found. Refer to Figure 4-8.
Figure 4-8 Binary Database errors and warning window for a

Network Element
Continued
68P02900W22-R
4-13
GMR-02
Mar 2008
Procedure 4-5 Exit and shut down the OLM (Continued)

4
Click the View More Details button to view more details of the errors found.
Click the Save NE button to save the Network Element with the reported
errors or go to step 6. If no more Network element errors are present, the
OLM shuts down.
Click Don't Save NE. If no more errors are present, the OLM shuts down.
NOTE
This may result in inconsistencies between the Ofine MIB and the
specic NE database within the network conguration directory.
4-14
68P02900W22-R
GMR-02
Mar 2008
Front panel icons
Front panel icons
Ofine MIB front panel

The DataGen OLM front panel provides the top level controls (icons) for the Ofine MIB (OLM)
as in Figure 4-5. The name of the operator who has logged in is displayed at the top left of
the front panel.
About the Ofine MIB

To show the current version of the OLM, place the cursor over the front panel, then press and
hold the right mouse button and select the About Ofine MIB option.
Conguration management
Select the Cong Mgmt icon to display the Navigation Tree. The Navigation Tree provides a
means of importing multiple BSS DataGen binary les. It displays a family tree representation
of all congurable objects. RF planning and modications can be carried out on multiple BSSs.
Refer to Using the Navigation Tree: Overview on page 4-27 for details.
For more detailed information about using the Navigation Tree, refer to Operating Information:
GSM System Operation (68P02901W14).
Administration
Select the Admin icon to view the Admin Options window. Administration is related to
the audit functions. All BSSs and RXCDRs must be audited before altering their BSS Binary
database les.
68P02900W22-R
4-15
GMR-02
Mar 2008
Find
Find
Select the Find icon to invoke a search facility to locate a Network Entity, PCU, Site, or Cell
within a network. The Find function displays a Navigation Tree starting at the network object
dened in the Find criteria. The Find function can also be used to locate an attribute.
Once the required item is found it is possible to perform the following:
Open the Navigation Tree with the found node as its root.
Open a Detailed View for the node.
Help
Select this icon to invoke the contents page of the OLM online help. The Help option can also
be selected from many of the windows shown in the OLM section of the manual. The Help
option is described in the DataGen OLM Online Help facility.
Xterm
Select this icon to open an Xterm window.
Exit
The EXIT button is located beneath the icons in the OLM front panel. Click this button and then
conrm the action to exit from the OLM front panel.
4-16
68P02900W22-R
GMR-02
Mar 2008
Expert Ofine MIB front panel
Expert Ofine MIB front panel

The OLM front panel can be reduced in size to optimize screen coverage. To reduce the size,
place the cursor over the front panel, then press and hold the right mouse button. Select the
Expert Desktop option to re-size the front panel (Figure 4-9).
Figure 4-9 Expert desktop
To return to the standard desktop, place the cursor over the front panel then press and hold the
right mouse button. Select the Standard Desktop option to return to the standard desktop
display.
68P02900W22-R
4-17
GMR-02
Mar 2008
Finding devices and attributes
Finding devices and attributes
Overview of the Find function

The Find function is used to locate:
Devices such as NEs, Sites, PCUs, or Cells within the network.
Attributes such as attributes containing the string ho_margin.
From the Ofine MIB front panel, select the Find icon to display a Find window. The Find
Devices option is selected by default. Search for NEs, Sites, PCUs, or Cells by entering
completely or partially the following details:
NE Name
Site Name
Site Id
PCU Name
Cell Name
GSM Cell Id
Once the required device has been found, it is possible to:
Open the Navigation Tree with the found node as its root.
Open a Detailed View for the node.
For more information about nding devices, refer to Finding an NE, PCU, Site, or Cell on page
4-19.
Select the Find Attributes option to open a Find attribute window where details of the
required attribute are entered. For more information about nding attributes, refer to Finding
an attribute on page 4-24.
4-18
68P02900W22-R
GMR-02
Mar 2008
Finding a Network Element, PCU, Site, or Cell
Finding a Network Element, PCU, Site, or Cell
Finding an NE, PCU, Site, or Cell

To nd an NE, PCU, Site, or Cell, perform the following procedure.
Procedure 4-6 Find an NE, PCU, Site, or Cell
Select the Find button from the Ofine MIB front panel. This displays the
Find window as in Figure 4-10 with the Find Devices option selected by
default.
Figure 4-10 Find window
Continued
68P02900W22-R
4-19
GMR-02
Mar 2008
Procedure 4-6
2
Find an NE, PCU, Site, or Cell (Continued)
Enter the name of the NE, PCU, Site, or Cell in the relevant Name eld. An ID
can be entered for a Site or Cell in the relevant ID eld. Click the Clear
button to remove the text from all the elds.
NOTE
The search performs an exact match on Site id or Cell id and a
partial match in all other elds. For example, Site id:1 is matched
with site 1 but not site 10. The text string SS1 is matched with
BSS1 and BSS10. The search is not case sensitive.
3
{28239}
Click the Find NE(s), Find PCU(s), Find SITE(s) or Find CELL(s) button.
Find NE(s) displays the network elements that match the criteria in
all elds. If a cell name is entered, it nds the NE containing the cell.
Find PCU(s) displays the PCUs that match the criteria in all elds.
Find SITE(s) displays the sites that match the criteria in all elds.
Find CELL(s) displays the cells that match the criteria in all elds.
NOTE
If no text is entered, the search displays all NEs, PCUs,

Sites, or Cells in the network.
Alternatively, use Enter from the keyboard instead of the

Find buttons.
The result of the search is displayed in the Find Results area of the window.
The heading indicates the class of objects found, that is, Network Elements,
PCUs, Sites, or Cells.
NOTE
If no match is found, an information window is displayed stating:
No matching <object> was found.
5
Click the required object in the Find Results box. The selection is
highlighted in inverse text, where object is the Network Element, PCU,
Site, or Cell.
For a Site or Cell, to obtain the parent view, click the Find Parent button;
else, go to step 7.
Continued
4-20
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-6
7
Find an NE, PCU, Site, or Cell (Continued)
From the Open section of the Find window, select either the Navigation
Tree or Detailed View button (refer to Figure 4-11). The Navigation Tree
opens with the found node as its root or a Detailed View opens for the node.
Figure 4-11 Find window with a Cell and Navigation Tree selected
From the menu bar on the Navigation Tree or Detailed View window, select
File Close to return to the Find window.
Select Close to return to the Ofine MIB front panel.
68P02900W22-R
4-21
GMR-02
Mar 2008
Examples of using Find

Below are typical examples of when an operator might use the Find feature.
Finding a Site using BSS name and Site Id

To nd a Site at a BSS by specifying the BSS name and the Site id, perform the following
procedure.
Procedure 4-7
Find a Site at a BSS
Select the Find button from the Ofine MIB Front Panel to open the Find
window.
Enter the BSS name in the NE Name eld, then enter the Site ID in the
Site id eld.
Click Find Site(s). The result of the search is displayed in the Find Results
box.
Finding a BSS parent of a Cell

To nd the BSS parent of a Cell, perform the following procedure.
Procedure 4-8 Find the BSS parent of a Cell
window.
Enter the name of the Cell in the Cell Name eld, or its ID in the GSM
Cell id eld.
Click Find Cell(s). The results of the search are displayed in the Find
Results box.
Select the Cell in the Find Results box.
Click Find Parent. The parent site of the Cell is displayed in the Find
Results box.
Select the Site and then click Find Parent. The parent BSS of the Cell is
displayed in the Find Results box.
4-22
68P02900W22-R
GMR-02
Mar 2008
Finding a Cell with a LAC

To search for Cells with a particular Location Area Code (LAC), perform the following procedure.
Procedure 4-9 Find a Cell with a LAC
window.
Enter the LAC in the third eld of the GSM Cell Id.
Click Find Cell(s). All Cells with the specied LAC are displayed in the
Find Results box.
NOTE
Additional information about GSM Cell IDs can be found in
Technical Description: BSS Command Reference (68P02903W18)

and Installation and Conguration: GSM System Conguration
(68P02901W17).
68P02900W22-R
4-23
GMR-02
Mar 2008
Finding an attribute
Overview of nding attributes

The Find attributes window (as in Figure 4-12) can be used to identify the exact name of
an attribute when only part of the attribute name is known. For example, searching for con
would list all attribute names containing con.
Figure 4-12 Find Attributes
4-24
68P02900W22-R
GMR-02
Mar 2008
To nd an attribute, perform the following procedure.
Procedure 4-10
Find an attribute
Click the Find icon on the DataGen Front Panel. The Find window
Figure 4-10 is displayed with the Find Devices button selected, by default.
Click the Find Attributes button at the top of the window. The window is
ready to accept nd criteria for an attribute (refer to Figure 4-12).
Select either Begins With, Ends With, or Anywhere in the Attribute

Name eld to search for an attribute whose name either begins with, ends
with or contains with the contiguous characters entered in step 4.
Enter at least three of the contiguous characters in the attribute name in the
Attribute name eld.
For example, if searching for attribute names containing ho_margin in the
attribute name, entering mar would return many attribute names, but
entering ho_margin would return a more precise list of attribute names.
NOTE
The attribute name or search string cannot be less than three
characters.
5
Click either the OMC Naming or BSS Naming button to indicate the
naming convention of the attribute to be found.
Select the software version number associated with the attribute in the
Version eld. The default is the latest software version.
NOTE
Some attributes can have a slightly different name in the OMC-R
database and the BSS database.
Continued
68P02900W22-R
4-25
GMR-02
Mar 2008
Procedure 4-10 Find an attribute (Continued)

7
Click the Find Attribute button to start the search. Alternatively, press
RETURN. The results of the search are displayed in the Find Results
pane. Use the scroll bars to scroll through the results, if necessary. The
results are shown in the following format: classname::attributename
Where classname is the container name and attributename is the attribute
name.
For example, if the attribute Anywhere is selected and ho_margin
is entered as the search string in the Attribute Name eld, the
Find Results pane would display the following list of attributes:
CELL::ho_margin_def
neighbour::ho_margin_cell
neighbour::ho_margin_rxqual
neighbour::ho_margin_rxlev
neighbour::ho_margin_type5
neighbour::congest_ho_margin
If no results are found, the following message is displayed:
No matching attribute found for given search string.
Printing the Find results

To print the results shown in the Find Results pane, click the Print button.
Saving the Find results

To save the results shown in the Find Results pane to a le, perform the following procedure:
Click the Save button. The File Selection window is displayed.
Enter the name of the le and the directory to which the Find results are to be saved.
Closing the Find window

To close the Find window, click the Close button.
4-26
68P02900W22-R
GMR-02
Mar 2008
Using the Navigation Tree: Overview
Using the Navigation Tree: Overview
Procedure list
The following is a list of procedures available from a Navigation Tree window:
Opening and closing a Navigation Tree on page 4-28
Moving levels on a Navigation Tree on page 4-30
Creating a BSS/RXCDR from the Navigation Tree on page 4-32
Further information
Further information on using the Navigation Tree can be found in Online Help.
The Navigation Tree is similar to the OMC Navigation Tree except for the following details:
The menu bar has an Ofine MIB pull down menu bar.
Load Mgt, Fault Mgt are not present in the menu bar.
68P02900W22-R
4-27
GMR-02
Mar 2008
Opening and closing a Navigation Tree
Opening and closing a Navigation Tree
Opening the Navigation Tree

To open a Navigation Tree, on the Ofine MIB front panel (Figure 4-5), select the Cong Mgmt
icon to display a Navigation Tree window as shown in Figure 4-13.
Figure 4-13
Navigation Tree window
4-28
68P02900W22-R
GMR-02
Mar 2008
Warning window invalid NE
Warning window invalid NE

When the Navigation Tree is opened, a comparison between the NEs in the MIB and the
BSS binary les in the conguration directory is carried out. If NEs exist in the MIB with
no corresponding BSS binary les, a Warning window listing all invalid NEs is displayed as
in Figure 4-14.
Figure 4-14
Invalid NEs window
Click Close to exit from the Warning window.
Resolving inconsistencies
The inconsistencies can be resolved by:
Carrying out a realign from the Navigation Tree. Refer to Realign a network on page
4-77 and carry out step 5 to step 8.
OR
Selecting the NEs and deleting them from the Navigation Tree. Refer to Deleting a BSS
or RXCDR from the Navigation Tree on page 4-58 for details.
Closing the Navigation Tree

To close a Navigation Tree, select File Close from the menu bar.
68P02900W22-R
4-29
GMR-02
Mar 2008
Moving levels on a Navigation Tree
Moving levels on a Navigation Tree
Prerequisite to moving levels

A Navigation Tree must be open and displayed on the user terminal before attempting to move
levels on that tree. See the procedure for Opening and closing a Navigation Tree on page 4-28.
NOTE
In the event that the OLM has no BSS or RXCDR network object created, an empty
Navigation Tree window is displayed. Refer to Creating a BSS/RXCDR from the
Navigation Tree on page 4-32 for details on how to create BSSs or RXCDRs.
Procedure for moving levels

Assuming the Navigation Tree is in the form shown in Figure 4-15, perform the following
procedure to move the levels.
Procedure 4-11 Move levels on a Navigation Tree
To expand the Navigation Tree to the second level, click the folder icon next
to the Network object. The various class buttons are displayed.
To open the branch of a tree under a button, click the folder icon beside
the button.
To close the branch of a tree under a button, click again on the folder icon
beside the button.
4-30
68P02900W22-R
GMR-02
Mar 2008
Figure 4-15
Panner and porthole
Navigation Tree window - showing panner
Panner and porthole

When the Navigation Tree diagram becomes larger in size than the display area of the
Navigation Tree window (Figure 4-15), a panner and porthole arrangement is used to control
what is displayed. The tree is displayed in the porthole region on the right hand side of the
window, and the display is controlled by means of a panner on the left.
To display different portions of the tree, move the panner as follows:
Click and hold the left mouse button within the panner region.
Move the mouse until the required area is in view within the porthole.
Release the mouse button.
68P02900W22-R
4-31
GMR-02
Mar 2008
Creating a BSS/RXCDR from the Navigation Tree
Creating a BSS/RXCDR from the Navigation Tree
Introduction to creating an NE
Creating a BSS or RXCDR involves importing BSS binary les from DataGen into the OLM. The
original les remain in DataGen and a copy is imported into the OLM.
Procedure for creating a BSS or RXCDR

To create a BSS or RXCDR from the Navigation Tree window, perform the following procedure.
Procedure 4-12 Create a BSS or RXCDR
Click the BSS/RXCDR Node and select Edit Create from the menu bar.
The BSS Binary congurations creation window is displayed as in
Figure 4-16.
Figure 4-16 BSS Binary congurations creation window
Select a country from the Country list.
Select a BSS area from the Area list.
Select a software version from the Software version list.
Select the conguration from the Conguration list.

Continued
4-32
68P02900W22-R
GMR-02
Mar 2008
Procedure for creating a BSS or RXCDR
Procedure 4-12 Create a BSS or RXCDR (Continued)

6
Click the Import database button. The message ReAlign Operation

successful is displayed in the status bar at the bottom of the Navigation
Tree window when the import is complete.
An information window is displayed as shown in Figure 4-17. Click OK

to continue.
Repeat step 2 to step 6 to import the required number of BSS binary les
into the network conguration.
NOTE
The maximum number of BSS binary les that can be imported is
64. The BSS binary les must be from different areas containing
different cells.
9
Click Cancel to close the BSS Binary congurations creation window

and return to the Navigation Tree.
To audit the network, refer to the section Running an audit from the Navigation Tree on page
4-35.
68P02900W22-R
4-33
GMR-02
Mar 2008
Audit: overview
Audit: overview
Introduction to auditing
After creating a network element from the Navigation Tree, it is necessary to populate the
network elements (NEs) with device information. This is done by selecting the network and
carrying out an Audit and Apply to OMC.
Ways to audit
An audit can be carried out as follows:
From the Navigation Tree

Current audits for the entire network can be set in progress from the Navigation Tree.
Refer to Running an audit from the Navigation Tree on page 4-35 for more
information.
Using the Admin icon on the Ofine MIB front panel

Audit puts a signicant load on the OLM in terms of processing power and memory usage.
It takes a considerable amount of time and therefore it is better to schedule the audit.
Refer to Scheduling an audit on page 4-60 for more information.
NOTE
The preferred way of using audit is on a per NE basis. Network-wide audits
are not recommended as they may cause degradation of the DataGen
machine due to resource consumption. For more information about Auditing
recommendations, refer to the manual Installation and Conguration: GSM
System Conguration (68P02901W17).
4-34
68P02900W22-R
GMR-02
Mar 2008
Running an audit from the Navigation Tree
Running an audit from the Navigation Tree
Introduction to auditing from the Navigation Tree

An audit can be performed from the Navigation Tree. After the audit is complete, perform the
function, Apply to OMC.
Audit from the Navigation Tree

To carry out an audit from the Navigation Tree, perform the following procedure.
Procedure 4-13
Run audit from the Navigation Tree
From the Navigation Tree (refer to Figure 4-13), click the network node
for the whole network, then select either the individual BSS or multiple
BSSs to be audited.
NOTE
It is valid to select either the BSS, RXCDR, SITE, PCU, or the
entire network to be audited.
2
Select Cong Mgt Audit from the menu bar. The message Audit
operation successfully dispatched is displayed in the status bar at the
bottom of the Navigation Tree window.
To monitor the status of the audit, select Cong Mgt Audit Logs from
the menu bar.
From the Audit Logs window, monitor the audit until it shows a status of
having been nished.
Select the Audited Item (highlighted in inverse text).

Continued
68P02900W22-R
4-35
GMR-02
Mar 2008
Audit from the Navigation Tree
Procedure 4-13 Run audit from the Navigation Tree (Continued)

6
Select File Open from the menu bar or double-click the highlighted row.
An Audit Inconsistency List window is displayed as in Figure 4-18.
Figure 4-18 Audit Inconsistency List window
Select Options Apply to OLM from the menu bar.
A Conrmation window is then displayed. Click OK to continue or Cancel

to abort the procedure. The progress is documented in the status bar.
When complete, select File Close to close the window and to return to
the Navigation Tree. Inconsistencies that have been applied to the OLM
during the audit procedure are now visible on the Navigation Tree window:
that is, any devices deleted are removed from the Navigation Tree and any
new devices introduced are displayed.
4-36
68P02900W22-R
GMR-02
Mar 2008
Modifying the network conguration from the Navigation Tree
Modifying the network conguration from the

Navigation Tree
Device management
From the Navigation Tree, it is possible to create, modify, save NE devices and parameters.
The procedures to carry out these operations are documented in Installation and Conguration:
GSM System Conguration (68P02901W17).
Creating or editing circuits, channels, statistics (enabling or disabling or threshold), and time
slot reservations are not supported from the Navigation Tree.
When required, use the Ofine MIB pull-down menu to verify and save the new conguration.
NOTE
From the Navigation Tree, saving a detailed view of a device will not automatically
alter the BSS binary le. To update the BSS binary le, it is necessary to verify and
save the databases. For further information, refer to Verify and save NE database
Conguring cells
From the Navigation Tree, it is possible to add, modify, delete, and propagate certain cell
parameters. When certain cell parameters are changed the values are propagated to the
neighbor commands of the surrounding cells automatically.
The procedures for carrying out these tasks are documented in Installation and Conguration:
GSM System Conguration (68P02901W17).
When required, use the Ofine MIB pull-down menu to verify and save the new conguration.
NOTE
From the Navigation Tree, saving a detailed view of a device will not automatically
alter the BSS binary le. To update the BSS binary le, it is necessary to verify and
save the databases. For further information, refer to Verify and save NE database
68P02900W22-R
4-37
GMR-02
Mar 2008
CellXchange: overview
CellXchange: overview
Introduction to CellXchange
CellXchange enables operators to perform the following tasks:
Export parameters from the OLM network into a tab delimited format.
Import parameters from a tab delimited format into the OLM network.
CellXchange can be carried out either in a live environment using the OMC-R CM MIB or in
an ofine environment using the OLM. Refer to the manual Installation and Conguration:
GSM System Conguration (68P02901W17) for more information on performing CellXchange
from the OLM.
Running CellXImport on the OMC-R or OLM

On the Cell X Import Watcher window, Motorola recommends the following for the BSS
deployment setting:
On the OLM, select Sequential mode.

Each BSS binary on the OLM has its own process running, so running several in parallel on
the OLM results in a lot of commands being sent out at the same time. Since all of these
commands need to be run on the same machine, applying all the BSS changes results
in a heavy loading on the OLM machine.
On the OMC-R, select Parallel mode.

On the live OMC-R the commands are sent out to each individual BSS. Therefore, the
loading on the OMC-R is not as great since each BSS is doing its own work.
4-38
68P02900W22-R
GMR-02
Mar 2008
Overwrite a BSS/RXCDR binary object le
Overwrite a BSS/RXCDR binary object le
Overview of overwrite feature

It is possible to copy BSS binary object le and overwrite the existing BSS binary object le in
the OLM.
NOTE
This feature overwrites the existing NEs and any changes made through the OLM
are lost.
Procedure for overwriting a BSS Binary object le

To overwrite a BSS Binary object le, perform the following procedure.
Procedure 4-14 Overwrite a BSS Binary object le
Select the network from the network selection window. Refer to

Starting/exiting the OLM GUI on page 4-9 for details.
Select Cong Mgmt from the Front Panel to display the Navigation Tree.
Refer to Opening and closing a Navigation Tree on page 4-28 for details.
Select the BSS or RXCDR from the Navigation Tree.

Continued
68P02900W22-R
4-39
GMR-02
Mar 2008
Procedure 4-14 Overwrite a BSS Binary object le (Continued)

4
Select Ofine MIB Import NE Database from the menu bar. The BSS
Binary congurations window is displayed as in Figure 4-19.
Figure 4-19 BSS Binary congurations window
Select the database conguration as follows:
Select the same country from the Country list.
Select the same BSS or RXCDR area from the Area list.
Select a software version from the Software version list.
Select the conguration from the Conguration list.

Continued
4-40
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-14 Overwrite a BSS Binary object le (Continued)

6
Click Import database. The message Reload Operation successful is

displayed in the status bar at the bottom of the Navigation Tree window
when the import is complete. An Information window is displayed as shown
in Figure 4-20. Click OK to continue.
Click Cancel to close the window and return to the Navigation Tree.
An audit is initiated.
To view the status of the audit, select Cong Mgt Audit Logs from
the menu bar. When the audit and apply is complete, the Navigation Tree
reects the new BSS binary object le.
68P02900W22-R
4-41
GMR-02
Mar 2008
Verify and save: overview
Verify and save: overview
Introduction to applying changes

The Navigation Tree is used to modify the network, and the information is saved in the OLM.
To apply the changes to the BSS databases (binary les) on disk, the following actions must
be performed:
Verify - Ensures that all the parameters are correct in accordance with predened BSS
rules. Once a validation is carried out it highlights any discrepancies that need corrective
action. It is possible to select individual NEs or an entire network. This option is available
under the Ofine MIB pull-down menu.
Save - Saves the BSS database le to disk and should be carried out regularly. Exiting the
OLM without saving, results in the loss of the changes effected. This option is available
under the Ofine MIB pull-down menu.
NOTE
Do not deploy a saved BSS database without rst carrying out a verify procedure.
The Verify and the Save actions for the entire network can be performed in a single step by
selecting Database Operations from the Ofine MIB pull-down menu. This option provides a
complete list of all NEs in the network to which verify and save operations can be applied.
NOTE
By default all NEs are selected. It is possible to deselect NEs from the list before
performing the Verify or Save action.
4-42
68P02900W22-R
GMR-02
Mar 2008
Verify and save NE database
Verify and save NE database
Verify a network element
NOTE
If the environment variable OLM_VERIFY_DB_LOGGING is set to ON, then a

detailed error le will be found in the following location:
/usr/DataGen/olm/<Network_name>/<Network_name002>.verify
Upon successive Verify actions, the le is over written. Refer to Introduction to

the Ofine MIB on page 4-2 for details.
To verify a network element (NE), perform the following procedure.
Procedure 4-15

Select Cong Mgt from the Front Panel to display the Navigation Tree.
Select the NE from the Navigation Tree.

Continued
68P02900W22-R
4-43
GMR-02
Mar 2008
Procedure 4-15 Verify a network element (Continued)

4
Select Ofine MIB Verify NE Database from the menu bar on the
Navigation Tree window. If errors exist, a Warning window is displayed
detailing the location and errors found for each NE as in Figure 4-21. Click
the View More Details button to see detailed information for each site
and cell affected.
Figure 4-21 Binary Database error and warnings window
Click Close to continue. To resolve any errors found (for example, to add
NE devices and parameters), refer to Modifying the network conguration
from the Navigation Tree on page 4-37 for details.
Repeat step 3 to step 4. A message is displayed in the status bar at the

bottom of the Navigation Tree window when no errors are present:
Operation successful.
NOTE
Do not deploy a saved NE database without rst carrying out a
verify procedure.
4-44
68P02900W22-R
GMR-02
Mar 2008
Save a network element
Save a network element

To save a NE, rst refer to the previous procedure Verify a network element Procedure 4-15
and follow step 1 to step 4. The NE is then selected.
Select Ofine MIB Save NE Database from the menu bar on the Navigation Tree
window. The following message is displayed in the status bar at the bottom of the Navigation
Tree window:
Off-Line MIB operation in progress...
Operation successful.
NOTE
Carry out this procedure at regular intervals.
68P02900W22-R
4-45
GMR-02
Mar 2008
Verify and save network
Verify and save network
Verify network
NOTE
If the environment variable OLM_VERIFY_DB_LOGGING is set to ON, a detailed

error le can be found in the following location:
/usr/DataGen/olm/<Network_name>/<Network_name002>.verify
Upon successive Verify actions, the le will be over written. Refer to Introduction
to the Ofine MIB on page 4-2 for details.
To verify the entire network, perform the following procedure.
Procedure 4-16 Verify the entire network

Select Cong Mgmt from the Front Panel to display the Navigation Tree.
Select the Network node from the Navigation Tree.
Select Ofine MIB Database Operations from the menu bar on the
Navigation Tree window.
Continued
4-46
68P02900W22-R
GMR-02
Mar 2008
Verify network
Procedure 4-16 Verify the entire network (Continued)

5
Click the button Verify NE Database on the Ofine MIB Database

Operations window (Refer to Figure 4-22). The Ofine MIB Verify
Operation Monitor window is displayed as in Figure 4-23. This contains a
list of all NE names and the operation status. If the verication produces
errors or warnings, this is indicated in the Reason column.
Figure 4-22 Ofine MIB Database Operations window
NOTE
By default all NEs in the network are selected and highlighted in
the OLM Database Operations window. To deselect an NE, click
the NE in the list. The NE is then displayed in normal text.
Continued
68P02900W22-R
4-47
GMR-02
Mar 2008
Verify network

Figure 4-23 Ofine MIB Verify Operation Monitor window
If the status Operation successful is displayed for all NEs, click Close in
this window and in all the subsequent windows to return to the Navigation
Tree window. If the operation fails, select the Network Element. The
selected NE is then highlighted.
Click Show Errors/Warnings. This displays the Binary Database error

and warnings window, detailing the location, and errors found as in
Figure 4-24.
Continued
4-48
68P02900W22-R
GMR-02
Mar 2008
Verify network

8
Click the View More Details button to see detailed information for each
site and cell affected.
Figure 4-24 Binary Database error and warnings window
Click Close to return to the Ofine MIB Verify Operation Monitor

window.
Writing errors to a le
To write the errors to a le, perform the following procedure.
Procedure 4-17
Write errors to a le
Click Save Errors/Warnings from the Monitor window.

A Conrmation window is displayed stating:
Off-Line MIB Verify operation results successfully saved.
The error le can be found in the following location:
/usr/DataGen/olm/<Network_name>/<Network_name>.result
Click Close to exit the OLM Verify Operation Monitor window.
Click Close in all subsequent windows to return to the Navigation Tree

window.
68P02900W22-R
4-49
GMR-02
Mar 2008
Aborting a verify network in progress
Resolving errors
To resolve any errors found, for example, to add NE devices and parameters, refer to the section
Modifying the network conguration from the Navigation Tree on page 4-37.
Procedure 4-18 Resolve errors
After resolving the errors found, repeat step 3 to step 5 (from the Verify
Network procedure) to validate the modications. If successful, the
Operation Status eld in the OLM Verify Operation Monitor window
should display the status Operation successful for all NEs.
Click Close in this window and in all subsequent windows to return to the
Aborting a verify network in progress

As soon as a verify NE database operation commences, the details are displayed in the Ofine
MIB Verify Operation Monitor window.
To abort a verify operation that is in progress, perform the following procedure.
Procedure 4-19 Abort a verify network in progress
Refer to the Verify network procedure (Procedure 4-16) and follow step 1
to step 5. The Ofine MIB Verify Operation Monitor window is then
displayed (refer to Figure 4-23).
Click the Abort button. A Conrmation window is displayed.
Click OK to conrm the action and close the window. The Ofine MIB
Verify Operation Monitor window is updated. The details in the
Operation Status eld change to Operation aborted for NEs that are not
already veried.
4-50
68P02900W22-R
GMR-02
Mar 2008
Saving a network
Saving a network
To save the entire network, perform the following procedure.
Procedure 4-20 Save a network
Refer to the procedure Verify network (Procedure 4-16) and

repeat step 1 to step 4. If the save is successful, the Ofine MIB
Database Operations window is displayed (refer to Figure 4-22).
If the save is not successful, a Binary Database error and warnings
window, detailing the location and errors found, is displayed similar to
that seen in Figure 4-24. Click the View More Details button to see
detailed information for each site and cell affected. Click the Don't Save
NE button to display the Ofine MIB Save Operation Monitor window
without saving the NE.
Click the Save NE Database button to save the NE database. The Ofine
MIB Save Operation Monitor window is displayed as in Figure 4-25. This
contains a list of all the NE names and the status of the saved NE(s).
Figure 4-25 Ofine MIB Save Operation Monitor window
NOTE
Do not deploy a saved network without rst carrying out a verify
procedure.
68P02900W22-R
4-51
GMR-02
Mar 2008
Aborting a save network in progress
Aborting a save network in progress

As soon as a save NE database commences, the details are displayed in the Ofine MIB Save
Operation Monitor window.
To abort a save operation in progress, perform the following procedure.
Procedure 4-21 Abort a save operation
Refer to the procedure Saving a network, repeat step 1 to step 2. The

Ofine MIB Save Operation Monitor window is displayed. Refer to
Figure 4-25.
Click the Abort button. A Conrmation window is displayed.
Click OK to conrm and close the Conrmation window. The Ofine MIB
Save Operation Monitor window is then updated. The Operation Status
eld displays the status Operation aborted for NEs that are not already
saved.
NOTE
For NEs that are saved, aborting does not rollback the saves
already carried out.
4
4-52
68P02900W22-R
GMR-02
Mar 2008
Deleting a network conguration in the OLM
Deleting a network conguration in the OLM
Introduction to deleting a network

It is recommended that the network conguration is archived and deleted, once the binary les
are transferred to the OMC. For details, refer to Exporting object les to the OMC Chapter 3
Operating DataGen.
Delete network conguration

To delete a network conguration, perform the following procedure.
Procedure 4-22 Delete a network conguration
From the DataGen main menu, select the OLM option. The Ofine
MIB (OLM) Network Congurations window is displayed as shown in
Figure 4-1.
Select the Network Conguration Name to be deleted. The selection is

highlighted.
NOTE
A network conguration can be deleted only by the owner or the
system administrator.
Continued
68P02900W22-R
4-53
GMR-02
Mar 2008
Delete network conguration
Procedure 4-22 Delete a network conguration (Continued)

3
Click Delete. A Conrmation window is displayed as shown in Figure 4-26.
Figure 4-26 Delete network Conrmation window
Click OK. The Conrmation window closes.

The network conguration is then removed from the list and the following
information is displayed:
Database operation successfully completed
Click OK to close the window.
4-54
68P02900W22-R
GMR-02
Mar 2008
Network Expansion: overview
Network Expansion: overview
Overview of Network Expansion

The purpose of this feature is to support large scale network expansion in an ofine
environment. This is achieved from the Navigation Tree by:
Creating a new BTS SITE by copying and pasting an existing BTS into a BSS conguration.
Recreating a BTS within the same Intra-BSS or a different Inter-BSS.
Deleting a BTS with its associated hardware devices and software functions in a single
operation.
Batch and schedule Network Expansion operations to run at an appropriate time.
Reviewing the transaction logs and maintaining a historical record of operations. It allows
the operator to progress intervened batch mode operations.
Network Expansion can be carried out either in a live environment using the OMC-R CM MIB or
in an ofine environment using the OLM. Refer to the manual Installation and Conguration:
GSM System Conguration (68P02901W17) for more information on performing Network
Expansion from the OLM.
68P02900W22-R
4-55
GMR-02
Mar 2008
Additional OLM features
Additional OLM features
List of additional tasks

Additional tasks that are carried out from the Ofine MIB are:
Using the autoclose function on page 4-57.

The Navigation Tree supports an autoclose feature. This feature controls the expanding
and closing of branches on the Navigation Tree.
Deleting a BSS or RXCDR from the Navigation Tree on page 4-58.

It is possible to hierarchically delete a BSS or RXCDR from the Navigation Tree.
Scheduling an audit on page 4-60.

To carry out an audit takes a considerable amount of time and where possible it is better to
schedule an audit.
Auditing logs on page 4-68.

Audit logs provide a method of monitoring audits and also provide an audit history.
Audit log management on page 4-73.

Audit log management can be used to automatically delete logs after a predened period.
Reload NE database on page 4-75.

It is possible to roll back to the previous saved version of an NE database.
Realign a network on page 4-77.

BSS binary les can be copied to the appropriate directory in the OLM. The realign
function ensures that there is the same number of NEs in the Navigation Tree as there are
BSS binary les in the network directory.
Compress or uncompress an OLM network on page 4-79.

It is possible from the Network conguration window under the Admin options to compress
or uncompress an ofine MIB network.
4-56
68P02900W22-R
GMR-02
Mar 2008
Using the autoclose function
Using the autoclose function
Overview of autoclose feature

The Navigation Tree supports an autoclose feature. When this feature is turned on, expanding a
certain branch of a tree results in the automatic closing of any other branches that might be open
at that level. With the feature turned off, multiple branches of a tree at any given level is open.
Prerequisite
A Navigation Tree must be open and displayed on the user terminal before setting autoclose.
Procedure for using autoclose

To use the autoclose function, select View Auto Close On/Off from the menu bar to toggle
the function. The default setting is Off.
NOTE
The autoclose function is a menu option. When selected, the alternate state is shown
in the menu window, that is, with Autoclose On selected. Autoclose Off is displayed
in the View menu.
68P02900W22-R
4-57
GMR-02
Mar 2008
Deleting a BSS or RXCDR from the Navigation Tree
Deleting a BSS or RXCDR from the Navigation Tree
Introduction to deleting BSS or RXCDR network elements

This option is used to hierarchically delete all BSS or RXCDR network elements from the OLM.
The associated binary les are also deleted from the network conguration directory.
Deleting BSS or RXCDR network elements

To delete BSS or RXCDR network elements, perform the following procedure.
Procedure 4-23 Delete BSS or RXCDR network elements
Select the specied BSS or RXCDR element from the Navigation Tree.
Select Edit Delete from the menu bar on the Navigation Tree window
(refer to Figure 4-13). A Conrmation window as shown in Figure 4-27
is displayed.
Figure 4-27 Deleting a BSS or RXCDR - Conrmation window
Continued
4-58
68P02900W22-R
GMR-02
Mar 2008
Deleting BSS or RXCDR network elements
Procedure 4-23 Delete BSS or RXCDR network elements (Continued)
NOTE
Since the OLM is performing a hierarchical delete of the NE,

a considerable delay may occur.
A network can be selected and deleted from the Network

conguration selection window (Figure 4-1). Deleting
the network is faster than deleting individual NEs from the
Navigation Tree.
Click OK to continue. An Information window is displayed stating that the

operation was completed successfully.
Click OK to return to the Navigation Tree.
68P02900W22-R
4-59
GMR-02
Mar 2008
Scheduling an audit
Scheduling an audit
List of procedures
The procedures that can be performed using the Audit Scheduler Admin Option are:
Scheduling an audit.
Modifying a scheduled audit.
Deleting a scheduled audit list.
Creating a scheduled audit

To schedule an audit, perform the following procedure.
Procedure 4-24 Create a scheduled audit
Select the Admin icon from the Front Panel to display the Admin Options
window (Figure 4-28).
Continued
4-60
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-24 Create a scheduled audit (Continued)

Figure 4-28 Admin Options window
Select the Audit Scheduler option. The selection is highlighted in black.

Continued
68P02900W22-R
4-61
GMR-02
Mar 2008

3
Click OK. The Audit scheduler window, is shown in Figure 4-29. This
contains a list of all scheduled audits, detailing their Scheduled Item,
Status, Deferred Time, Start Time, End Time, Interval, Execute Mode,
Update Mode, and Operator.
Figure 4-29 Audit Scheduler window
Continued
4-62
68P02900W22-R
GMR-02
Mar 2008

4
To create an audit, select Edit Create from the Audit Scheduler

window. The auSchedule Detailed View <create> window is displayed
as in Figure 4-30.
{27761}
Figure 4-30 auSchedule Detailed View <Create> window
Continued
68P02900W22-R
4-63
GMR-02
Mar 2008

5
To insert the elements to be audited, click the Scheduled Element button.

The network Navigation Tree window is displayed.
Select the Network Element(s) to be audited in the usual way. For more
information about using the Navigation Tree, refer to Moving levels on a
Navigation Tree on page 4-30.
NOTE
It is valid to select either BSS, RXCDR, SITE, PCU, or the entire
network to be audited.
7
Select Cong Mgt Audit. The Navigation Tree window closes and the
selected element is displayed in the Scheduled Element Name eld.
Entering schedule information

Enter schedule information in the Detailed View window as described in the procedure.
Procedure 4-25
Enter information in the Detailed View window
Only the Start Time eld needs to be specied for One shot auditing. Click
the parameter that requires changing. The selected parameter is highlighted
in black. The parameters are ordered as follows: Month/Day/Year
Hour:Minute:Second
NOTE
Ensure that the Execute Mode is Oneshot.
Use the up/down arrow symbols to the right of the Start Time eld to change
the parameter to the required value.
2
Verify that the Update Mode eld is Apply to OMC.

If not, click the Execute Mode button. Hold the left mouse button down, and
scroll to Apply to OMC. Once this is highlighted, release the mouse button.
The selected option is then displayed on the Detailed View.
Continued
4-64
68P02900W22-R
GMR-02
Mar 2008
Modifying a scheduled audit
Procedure 4-25 Enter information in the Detailed View window (Continued)

3
{27761} Choose the Audit Type to be performed by selecting either the Full
Audit or Per Site Audit option.
If the Per Site Audit option is selected, the available options in the Per Site
Audit Logging eld are:
List All Sites
List Audited Sites
List Un-audited Sites
NOTE
When the selected Audit Type is Full Audit, the Per Site Audit
Logging eld is unavailable.
4
Verify that the Neighbor Propagation after Audit eld is No unless neighbor
propagation after audit is required.
Once all the above information is entered into the Detailed View, select File
Create from the menu bar. The new Scheduled Audit is created and can be
viewed in the Audit Scheduler window.
Close the Detailed View window by selecting File Close from the menu
bar.
Close the Audit Scheduler window by selecting File Close from the
menu bar.

All the limitations that apply to auditing also apply when modifying a scheduled audit. For more
information, refer to the earlier procedure for Creating a scheduled audit.
To modify a scheduled audit, perform the following procedure.
Procedure 4-26
Modify a scheduled audit
Open an Audit Scheduler window. The Audit Scheduler window is

Continued
68P02900W22-R
4-65
GMR-02
Mar 2008
Procedure 4-26 Modify a scheduled audit (Continued)

2
Select the audit to be modied. The selection is highlighted in black.
Figure 4-31 Audit Scheduler window
To open this audit for modication, select Edit Detailed View from the
Audit Scheduler window. The auSchedule Detailed View window is
Select Edit Edit from the menu bar. The Detailed View can now be edited.
The File Revert option can be used before saving an edited auSchedule
Detailed View to return all changed elds to their previous state.
NOTE
It is not possible to revert to a previous version after an edited
version has been saved.
5
When all the required elds are changed, select File Save from the menu
bar.
Close the Detailed View by selecting File Close from the menu bar. The
modied Scheduled Audit can be viewed in the Audit Scheduler window.
menu bar.
4-66
68P02900W22-R
GMR-02
Mar 2008
Deleting a scheduled audit
Deleting a scheduled audit

Expired Scheduled Audits must be deleted from time to time to avoid using excess memory.
To delete a scheduled audit, perform the following procedure.
Procedure 4-27 Delete a scheduled audit
Refer to the earlier procedure for Creating a scheduled audit and follow
step 1 to step 3. The Audit Scheduler window is displayed as in
Figure 4-31.
Select the audit to be deleted.
Select Edit Delete from the Audit Scheduler window. A Conrmation

window is displayed.
Click OK. The Scheduled Audit closes and the message Element Deleted is
displayed in the status bar.
menu bar.
68P02900W22-R
4-67
GMR-02
Mar 2008
Auditing logs
Auditing logs
List of procedures
The procedures that can be performed using the Audit Logs Admin Option are:
Viewing an audit log list.
Aborting an audit in progress.
Viewing an audit inconsistency report.
Deleting an audit log.
Viewing an audit log list

After an audit has taken place, information relating to this audit is placed in an audit log.
This information can be accessed and printed.
To view an audit log list, perform the following procedure.
Procedure 4-28 Viewing an audit log list
Select the Admin icon on the Front Panel to display the Admin Options
window (Figure 4-28).
NOTE
It is also possible to view the audit logs from the Navigation Tree
by selecting Cong Mgt Audit Logs from the menu bar.
Continued
4-68
68P02900W22-R
GMR-02
Mar 2008
Aborting an audit in progress
Procedure 4-28 Viewing an audit log list (Continued)

2
Select Audit Logs option, then click OK. The Audit Logs window is
displayed. Refer to Figure 4-32. This contains a list of all completed audits,
detailing the Audited Item, Status, Reason, Actual Start Time, Actual
End Time, Update Mode, Operator, and Warning for NE Apply.
Figure 4-32 Audit Logs window
Close the Audit Logs window by selecting File Close from the menu bar.
Aborting an audit in progress

As soon as a Scheduled Audit begins (see Scheduling an audit on page 4-60), progress details
are displayed in the Audit log list.
To abort an audit in progress, perform the following procedure.
Procedure 4-29
Abort an audit in progress
Refer to the Viewing an audit log procedure (Procedure 4-28) and follow
step 1 and step 2 to open the Audit Logs window.
From the Audit Log list, select the audit to be aborted.
NOTE
The Status of an audit in progress is displayed as Active in the
Audit Log list.
Continued
68P02900W22-R
4-69
GMR-02
Mar 2008
Inconsistency reports
Procedure 4-29 Abort an audit in progress (Continued)

3
Select Options Abort from the menu bar. A Conrmation window is

Figure 4-33 Audit Logs abort conrmation window
Click OK. The Conrmation window closes and the Audit Log list is
updated. The Status of the audit is now changed to Aborted.
Select File Close from the menu bar to close the Audit Log window.
Inconsistency reports
After an audit has taken place, information relating to this audit is placed in an Audit Log.
Any inconsistencies found between the NE and OLM conguration database are placed in an
Inconsistency List. This information can be accessed and printed.
There is a distinction between an Audit Log, which is a general information message generated
as the outcome of an audit, and an Audit Inconsistency Report, which is a further extension to
show any inconsistencies discovered during an audit in a more detailed form.
4-70
68P02900W22-R
GMR-02
Mar 2008
Viewing an audit inconsistency report
Viewing an audit inconsistency report

To view an Audit Inconsistency report for a particular Scheduled Audit, perform the following
procedure.
Procedure 4-30 View an Audit Inconsistency report
step 1 and step 2. The Audit Logs window is displayed as in Figure 4-32.
From the Audit Log list, select the audit from which any inconsistencies
should be viewed. The selected audit is highlighted.
NOTE
An Audit Inconsistency report is valid only for an audit with a
Status of either Finished or Applied.
3
Select File Open from the menu bar. An Audit Inconsistency List
window is then displayed (refer to Figure 4-18), detailing all elements where
inconsistencies were found during the audit. Information is displayed for
each reported inconsistency or error as in Table 4-2.
Select File Close from the menu bar to close the Audit Inconsistency
report.
Table 4-2 Reported inconsistencies or errors

Column
Identies
Object Name
The name of the congurable device.
Object Class
The class (or type) of the congurable device.
Record Type
Whether this record is reporting an inconsistency or an error,

and what type of inconsistency it is, if applicable.
The Record Type can be one of:
Object Not at OMC
Object Not at NE
Attribute Differs
Error Report
Continued
68P02900W22-R
4-71
GMR-02
Mar 2008
Deleting an audit log
Table 4-2 Reported inconsistencies or errors (Continued)

Column
Identies
Apply Status
The status of an attempted update to the system to remove an

inconsistency, or error indicates the error detected by the audit.
If an inconsistency is reported and an Apply to OMC or Apply
to NE operation is performed, this column indicates the result
of the operation. This can be Success or Failure. If an apply
operation is not attempted, this eld is blank.
If an error is reported, this column describes the error.
Warning for NE
Apply
The type of warning given when inconsistencies applied to a

network element fail.
Attribute Name
The name of the attribute that is inconsistent, if applicable.
OMC Attr Value
The value of the attribute at the OMC, if applicable.
NE Attr Value
Reason
The value of the attribute at the NE, if applicable.

The reason why an inconsistency fails to be applied, if
applicable.
Deleting an audit log

To delete an audit log, perform the following procedure.
Procedure 4-31 Delete an audit log
step 1 and step 2. The Audit Logs window opens on the screen as in
Figure 4-32.
Select the Audit Log to be deleted. The selection is highlighted.
Select Edit Delete from the menu bar. Select Edit Delete All to delete
all the logs. A conrmation of deletion window is displayed.
Click OK. The Conrmation window closes and the selected audit log is
removed from the list.
Close the Audit Logs window by selecting File Close from the menu bar.
4-72
68P02900W22-R
GMR-02
Mar 2008
Audit log management
Audit log management
Overview of audit log management

The Audit Log Management Admin option is used to delete audit logs after a predened
period. This period is congurable between zero and seven days.
Audit logs can also be deleted manually. Refer to the procedure Deleting an audit log for
more information.
Setting the delete period

The operator is required to set the number of days for retaining the audit log les, after
which the OMC automatically deletes the les. If set to zero all the audit logs, except the
current one, are deleted.
To set the delete period, perform the following procedure.
Procedure 4-32 Set the delete period
Select the Admin icon on the Front Panel to open the Admin Options
window as in Figure 4-28.
Continued
68P02900W22-R
4-73
GMR-02
Mar 2008
Setting the delete period
Procedure 4-32 Set the delete period (Continued)

2
Select the Audit Log Management option, then click OK.

The Audit Log Management window is displayed. Refer to Figure 4-34.
Figure 4-34 Audit Log Management window in Edit mode
Select Edit Edit from the menu bar.
Enter the number of days after which the log is to be deleted.
Select File Save from the menu bar to save the change. The following
message is displayed in the status bar at the foot of the window:
Save completed
NOTE
To quit without saving, select File Close. A Message window
displays the following:
There have been changes since you last saved. Pressing

OK will exit your current interface without saving.
6
Select File Close to close the window.
4-74
68P02900W22-R
GMR-02
Mar 2008
Reload NE database
Reload NE database
Introduction to reloading an NE database

If changes are made to the network and the user wishes to return to a previous saved version of
the NE database, then Reload from the Ofine MIB can be carried out.
Procedure for reloading an NE database
NOTE
If multiple NEs are changed, for example if an RF import, Cell or neighbor
propagation is carried out, then all the affected NEs must be included in the roll back.
To reload a previously saved version of an NE database, perform the following procedure.
Procedure 4-33 Reload an NE database
Refer to the procedure Verify and save NE database on page 4-43 and repeat
step 1 to step 4. The NE is selected.
Select Ofine MIB Reload NE Database from the menu bar on the
Navigation Tree. A Conrmation window is displayed as in Figure 4-35.
Continued
68P02900W22-R
4-75
GMR-02
Mar 2008
Procedure for reloading an NE database
Procedure 4-33
Reload an NE database (Continued)
Figure 4-35 Reload Conrmation window
Click OK to conrm the reload. The progress of the reload NE

Database is shown in the status bar at the bottom of the
Navigation Tree window. An Information window is displayed as:
Updating the OMC CM MIB - View Audit Log or inconsistency List's
Status Column for Completion: <NE_Name>
Click OK.
To monitor the status of the audit, select Cong Mgt Audit Logs from
the menu bar.
From the audit log list, monitor the audit until it shows a Finished status.
4-76
68P02900W22-R
GMR-02
Mar 2008
Realign a network
Realign a network
Introduction to realigning a network

The realign function is a shortest method of putting BSSs and RXCDRs into a network
conguration. Normally, this is done from the Navigation Tree. Refer to Creating a BSS/RXCDR
from the Navigation Tree on page 4-32 for details. However, it is possible to copy NE binary
les from a tar tape or through ftp into the appropriate conguration directory in the OLM.
The realign function ensures that there is the same number of NEs in the MIB, as there are
BSS binary les in the conguration directory.
The following cases apply (refer to Table 4-3).
Table 4-3
Realign a network - cases
BSS Binary les

(conguration directory)
Result
(MIB)
Action Required
Add
Shell NEs added
Audit network
Replace
NEs updated
Reload database
Remove
NEs deleted
NOTE
It is not possible to continue working on the network when a realign is in progress.
Procedure for realigning a network

To realign a network, perform the following procedure.
Procedure 4-34
Realign a network
Create a network conguration. Refer to Starting/creating a network

conguration in the OLM on page 4-6 for details.
Open the network conguration. Refer to Starting/exiting the OLM GUI on

page 4-9 for details.
Open a Navigation Tree using the Cong Mgmt icon. Refer to Opening and
closing a Navigation Tree on page 4-28 for details.
Continued
68P02900W22-R
4-77
GMR-02
Mar 2008
Procedure for realigning a network
Procedure 4-34 Realign a network (Continued)

4
Open an Xterm window and copy the BSS binary les to:
/usr/omc/DataGen/olm/<network configuration name>
NOTE
The network conguration name is that created in step 1 above.
5
Select the network node and select Ofine MIB ReAlign Network from
the menu bar.
The message ReAlign Operation successful is displayed in the status bar
at the bottom of the Navigation Tree window when no errors are present.
An Information window is displayed as shown in Figure 4-36.
Click OK to return to the Navigation Tree window.
If new NEs have been added, then carry out an audit on the network. Refer
to Running an audit from the Navigation Tree on page 4-35 for details.
If NE binary les have been replaced, carry out step 8.
Select the NE and do a reload from the Ofine MIB pull down menu. Refer
to Reload NE database on page 4-75. Reload NE database for details.
4-78
68P02900W22-R
GMR-02
Mar 2008
Compress or uncompress an OLM network
Compress or uncompress an OLM network
Overview of compress and uncompress

It is possible to compress or uncompress an Ofine MIB network from the OLM Network
Congurations window using the Admin options. All the binary les located in the selected
network conguration directory will be compressed or uncompressed.
When starting the OLM from the DataGen main menu, all compressed les are automatically
uncompressed. The compress function can be used when disk space is an issue.
NOTE
It is better to archive and delete old network congurations when the binary les are
transferred to the OMC.
Compress a network procedure

To compress a network, perform the following procedure.
Procedure 4-35 Compress a network
Open the OLM Network Congurations window (Figure 4-1) from the
DataGen main menu. Refer to Starting/creating a network conguration
in the OLM on page 4-6 for details.
Select the network conguration name from the list on the OLM Network
Congurations window. The selection is highlighted in black as in
Figure 4-37.
Continued
68P02900W22-R
4-79
GMR-02
Mar 2008
Uncompress a network procedure
Procedure 4-35 Compress a network (Continued)

3
Select Admin Compress from the menu bar. A Conrmation window

is displayed.
Figure 4-37
window
Compress from the OLM Network Congurations
Click OK to continue or Cancel to abort.
Uncompress a network procedure

To uncompress a network without restarting the OLM from the DataGen front panel, perform
the following procedure.
Procedure 4-36 Uncompress a network
Refer to the Compress procedure and follow step 1 to step 2.
Select Admin Uncompress from the menu bar. A Conrmation window

is displayed.
Click OK to continue or Cancel to abort.
4-80
68P02900W22-R
GMR-02
Mar 2008
Troubleshooting the OLM
Troubleshooting the OLM
Introduction to troubleshooting the OLM

If the OLM does not function normally, refer to the information in Table 4-4 to Table 4-8 which
details errors that can occur and how to resolve them.
To investigate potential problems, perform the following procedure.
Procedure 4-37 Troubleshooting the OLM
Check the omcaudit le which is located in

/usr/omc/logs/omcaudityyyymmdd. If a problem occurs, the messages
are stored in the omcaudit le.
Refer to Table 4-4 to Table 4-8 for information on error messages and the
appropriate actions to be taken.
Error OLM fails to start

If the OLM fails to start, Table 4-4 shows the possible error messages that may appear and the
appropriate action to take.
Table 4-4
OLM fails to start
Error/Warning
Explanation
Action
msgctl call failed

with main message
queuemsgget call failed
with main message queue
The maximum message size

and maximum bytes per
queue is specied during the
DataGen install. These kernel
parameters should not be
altered.
Check using sysdef -i to verify

value. Put in original values.
Reboot and open the network.
It is not known what

BSS software version
BSS Binary file
<BSS_Name is>.
The size of the BSS binary

le is not specied in:
/usr/omc/cong/OLM.CNFG
Check le size of BSS binary le

and contact your local support
ofce.
Continued
68P02900W22-R
4-81
GMR-02
Mar 2008
Database errors
Table 4-4 OLM fails to start (Continued)

Explanation
Error/Warning
Action
All copies of the

ported BSS software
have not started up in
the allotted time.
If there is a heavy load on the

system it may be necessary to
increase the start up time in
/usr/omc/cong/OLM.CNFG
or
BSS binary le is
corrupt.
Edit OLM.CNFG le and

increase the number for
NMASECM_WAIT_SECS
parameter. Exit and restart
the OLM. Refer to the
procedure Starting/exiting
the OLM GUI on page 4-9.
Recompile to create
a BSS binary le and
replace the existing one.
Open the network.
Failed fork to run

NmaseCm code.
The maximum number of

processes that can be run is
specied during the DataGen
install. This kernel parameter
should not be altered.
Check using sysdef -i to verify

value. Put in original value.
Reboot and open network.
Problem accessing
DataGen INFORMIX
database sql code -387:
no connect permission
The administrator must

grant the user the connect
permission.
Log in as omcadmin. From the

command line invoke DGAdmin
by typing DGAdmin and enter
tp -u <username>
Database errors
Table 4-5 shows the error messages that may appear and the appropriate actions to be taken.
Table 4-5
Database Errors
Action
Error/Warning
Invalid NE
failed to open database
<Network name> sql error
<Number>
Network name is <Name> it
should be <Network Name>
To correct the errors carry out the following:
Reinitialize the database. Refer to the procedure

Reinitialize database procedure on page 4-86.
Audit the network. Refer to the procedure Running

an audit from the Navigation Tree on page 4-35.
There is more than one

Network in this database
Rose message received from
an NE when only start up
messages expected
Continued
4-82
68P02900W22-R
GMR-02
Mar 2008
General errors
Table 4-5 Database Errors (Continued)

Action
Error/Warning
Rejecting message because
unable to route message to
NE
Unable to route message to

<BSS NAME>
Message from BSS with key
<number>rejected BSS unknown
NE %s in Binary directory
and in MIB do not have the
same software version and/or
type (BSS/RXCDR)
Revert to the previously saved version of the NE database.

Refer to Reload NE database on page 4-75 for details.
Unable to route message

because NE is unknown.
Check the version of BSS binary les as specied in

/usr/omc/cong/OLM.CNFG and contact your local
support ofce.
NE %s is in MIB, not in BSS

Binary directory
Contact your local support ofce.
NE %s is in BSS Binary
directory, not in MIB
Contact your local support ofce.
General errors
Table 4-6 shows the error messages that may appear and the appropriate actions to be taken.
Table 4-6
General operating errors

Action
Error/Warning
The number of Users in
the Network Configurations
list is set to non-zero
even though there
is no OLM GUI open.
The GUI hangs
SMASE channel has been

deleted.
OlmOmcInit channel has been

deleted
Unable to read from IPC
channels
Reset the number of users to zero. Refer to the

procedure Force shutdown OLM in this section.
Audit the network. Refer to the procedure Running

an audit from the Navigation Tree on page 4-35.
Force shutdown the OLM. Refer to the procedure

Force shutdown OLM in this section.
Open the network. Refer to the procedure

Starting/exiting the OLM GUI on page 4-9.
Specic operation fails

If a specic task fails, Table 4-7 shows the error messages that may appear and the appropriate
actions to be taken.
68P02900W22-R
4-83
GMR-02
Mar 2008
Import errors
Table 4-7
Specic operation error

Action
Error/Warning
To correct the error carry out the following:
Fatal Off-Line MIB Operation

Error
View the audit log. Refer to the procedure Auditing

logs on page 4-68.
Exit and restart the OLM. Refer to the procedure

Import errors
While importing NE binary les Table 4-8 shows the possible error that may occur and the
appropriate actions to be taken.
Table 4-8
Importing NE software errors

Action
Error/Warning
Transaction timeout
Link OOS
Ported BSS S/W for <BSS Name>

has not started
Revert to the previously saved version of

the NE database. Refer to the procedure
Reload NE database on page 4-75.
msgsnd call failed for NE <BSS

Name>.
or
msgrcv call failed for msg Q
msgget call failed with key

<number> for BSS <BSS Name>.
Exit and restart the OLM. Refer to the procedure

Unable to route message to <BSS

Name> because ported BSS SW is
not started.
Introduction to the force shutdown feature

Force shutdown OLM function should be carried out only when the OLM is behaving abnormally.
This function will shut down the Ofine MIB and reset the number of users to zero for the
network conguration.
NOTE
Any changes that are done since the last save was carried out are lost. The system
administrator, the person who created the network conguration or the rst user to
launch the OLM network can carry out this task.
4-84
68P02900W22-R
GMR-02
Mar 2008
Force shutdown OLM procedure
Force shutdown OLM procedure

To shut down the OLM and reset the number of users to zero for the network conguration,
perform the following procedure.
Procedure 4-38 Force a shutdown of the OLM
From the DataGen main menu, select the OLM option. The Ofine MIB (OLM)
Network Congurations selection window is displayed. Refer to Figure 4-1.
Select the required network conguration name from the OLM Network
Conguration list. The selection is highlighted in black.
Select Admin Force shutdown from the menu bar. A Conrmation

window is then displayed as in Figure 4-38.
Figure 4-38 Conrmation window
Click OK. The following message is displayed in an Information window:

Database operation successfully completed.
Click OK. The column Users in the Network conguration window is reset to
zero for the network.
NOTE
On opening the network, carry out an audit. Refer to Running an audit
from the Navigation Tree on page 4-35 for details.
68P02900W22-R
4-85
GMR-02
Mar 2008
Reinitialize database procedure

The reinitialize function should be carried out only when the database has become corrupt. This
function shuts down and deletes all audited information in the Ofine MIB.
NOTE
Only the person who created the network conguration, or the system administrator
can carry out this task.
To reinitialize the network database, perform the following procedure.
Procedure 4-39 Reinitialize the network database
Refer to the earlier procedure Force shutdown OLM and follow step 1 to
step 2. The OLM Network Congurations window opens and the network is
selected.
Select Admin Reinitialize Database from the menu bar. A Conrmation

window is displayed as in Figure 4-39.
Figure 4-39 Reinitialize DataBase - Conrmation window
Click OK. The message Database operation successfully completed is

displayed in an Information window.
Continued
4-86
68P02900W22-R
GMR-02
Mar 2008
Procedure 4-39 Reinitialize the network database (Continued)

4
Click OK to close the window.
NOTE
On opening the network, it is seen that all the information that was
audited is lost. It is necessary to carry out a complete audit on the
shell NEs. Refer to Running an audit from the Navigation Tree on
page 4-35 for details.
68P02900W22-R
Mar 2008
4-87
GMR-02
4-88
68P02900W22-R
GMR-02
Mar 2008
Chapter
5
Command line tools
68P02900W22-R
Mar 2008
5-1
GMR-02
Overview of command line tools
Overview of command line tools
Command line functions

There are several software tools available for use in association with DataGen which are not
part of the Graphical User Interface (GUI), which can be accessed either from the GUI or the
command line.
Table 5-1 shows the user tools available for command line operation.
Table 5-1
Command line tools

Command line tools
Command name
Invoked with
Use
Command line
or GUI
Auto-compile MMI scripts
auto_compile
Compile a number of MMI

scripts
Both
Auto-revgen binary les
auto_revgen
Revgen a number of binary

les
Both
Auto-upgrade binary les
auto_upgrade
Upgrade a number of
binary les
Both
Copy Area
ca
Copies a BSS area to a new

conguration
Both
MMI Combiner
combine
Combine GSM MMI

command les
Command line
Compile MMI script
compile
Compile MMI scripts
Both
Compress/ uncompress
.002 les
cpdb
Compress or uncompress
the binary object les
Both
Delete Database Object
del
Delete a DataGen BSS area
Both
MCDF lters
lter
Export or import or validate

MCDF les.
Both
MMI Command Generator
gcmd
Generates BSS command

le(s)
Both
Dbaccess command
dbaccess
Optimize DataGen database
Command line
Continued
5-2
68P02900W22-R
GMR-02
Mar 2008
Table 5-1
General information
Command line tools (Continued)

Command line tools
Command name
Invoked with
Use
Command line
or GUI
Lock/Unlock BSS area
lock_adm
Locks or unlocks a BSS

area
Command line
Revgen Command
revgen
Generate MMI les from

CM database objects
Both
Toggle Permissions
tp
Toggle database
permissions for a user
Command line
Version Upgrader
upg
Copies a BSS area to

a new conguration,
and upgrades the new
conguration
Both
Country Administration
(CADM)
xcadm
Create new Country

and Network les in the
DataGen database
Both
General information
Most command line tools require that DGAdmin be run before they can be invoked, using the
following command:
DGAdmin
This command sets the user environment for DataGen. DGAdmin sets system variables in the
current environment to allow DataGen tools to function correctly. It changes the current prompt
to indicate that the environment has been set up for use with DataGen.
User options
There is a user option to display values in either Hexadecimal or Decimal (default) format.
Prior to starting DataGen, two variables must be set to allow MMI scripts to display GSM
Cell IDs, OPCs and DPCs in Hex.
68P02900W22-R
5-3
GMR-02
Mar 2008
User options
Procedure
Open an Xterm window and, if using the Bourne Shell (sh) interpreter, execute the
following commands:
DG_HEX_CELL_IDS=yes ; export DG_HEX_CELL_IDS
DG_HEX_POINT_CODES=yes ; export DG_HEX_POINT_CODES
Open an Xterm window and, if using the C shell interpreter, execute the following
commands:
setenv DG_HEX_CELL_IDS yes
setenv DG_HEX_POINT_CODES yes
5-4
68P02900W22-R
GMR-02
Mar 2008
Copy Area (ca) command
Copy Area (ca) command
Name
ca - Copies area.
Synopsis
ca -source <country name>:<BSS area name>:<configuration number> [-area <new BSS
area name> [-id <new BSS area id>]] [-config <new configuration number>] [-title
<new/open Area comment>"]
See Table 5-2 for option descriptions.
Description
This utility allows a BSS area to be copied to a new conguration, or act as the basis with which
to generate a new BSS area at a given conguration. If no conguration number is specied for
the new conguration, the next available conguration number is used.
Command line options

An explanation of the command line options is given in Table 5-2.
Table 5-2 Command line options (ca command)

Description
Option
<country name>
<BSS area name>
<conguration number>
-area <new BSS area name>
-id <new BSS area id>
-cong <new conguration
number>
-title <new conguration title
string>
The country name containing the objects.

The BSS name for the original objects.
The conguration number of the BSS containing the
objects.
Dene a new BSS area.
Dene a BSS area id for the new area.
Dene a new conguration.
The comment entered when creating the BSS area.
68P02900W22-R
5-5
GMR-02
Mar 2008
Requirements
Requirements
Run DGAdmin before executing the copy command. Any parameters that contain spaces must
be entered between single quotes.
Output
Output from Copy Area utility is the insertion of a new BSS area conguration, or a new BSS
area in the DataGen database. The screen output informs the user of the Copy Area operation
and completion.
If the user opens the table controller screen for the new area created by the ca command,
all of the columns are blank. The File and Report columns are blank as the ca utility only
copies the database entry and not the input tables. The Validate and Insert columns are blank
because the records associated with the original database entry holding this information are
specically excluded from the copy.
Example Copy Area usage

The Copy Area utility ca works from the command line. The following command line can be
customized to perform the required copy:
ca -source UK:Area10:0
NOTE
This example does not have a title string. By default, a comment is created for the
target area:
Copied from BSS area:
<BSS Area> <Configuration No>
This copies conguration 0 of Area 10 to the next free conguration number within Area10.
To copy conguration 0 of area 10 to a new area and add the comment copy of Area 10, a
command of the following type must be used:
ca -source UK:Area10:0 -area Area11 -title copy of Area 10"
NOTE
The next free conguration number in Area 11 is used and, if Area 11 does not exist,
it is created.
5-6
68P02900W22-R
GMR-02
Mar 2008
MMI Combiner (combine) command
MMI Combiner (combine) command
Name
combine - Combines GSM MMI command les.
Synopsis
combine
Description
This utility generates a combined GSM MMI command le by combining the GSM MMI
command les under the command directory (generated by gcmd) when run under the BSS
area directory path.
Output
Output from the script is in the form of a combined GSM MMI command le, located under the
command directory and named COMBINED.
68P02900W22-R
5-7
GMR-02
Mar 2008
Example
Example
To create an MMI script le, run the following command:
cd \<country>\<bss area>\<config no>\command combine
This generates an MMI script le called COMBINED.
NOTE
Each time a combined script is generated the original script is backed up with a Date
and Time stamp. For example, COMBINED.BACKUP072498123425.
Requirements
Run DGAdmin before executing the compile command.
5-8
68P02900W22-R
GMR-02
Mar 2008
Compile MMI script (compile) command
Name
compile - Compiles MMI script.
Synopsis
compile -C <country> -v <Version> <filename>
Where
Is
country
name of the country where the options object is located.
Version
software version to compile with (1.7.4.0 or 1.7.6.0 or 1.8.0.0).
lename
name of script le to compile.
Description
This utility allows an MMI script to be converted into a CM database object (binary object)
le. It outputs a binary object le and a report le and places them in the directory where
the script was run.
Example
The following is an example of using the compile command:
compile -C Austria -v 1.8.0.0 BSS_scr
The following les are generated on successful compilation:
BSS_scr.002
BSS_scr.rep
If the compilation fails, only the report le (.rep) is generated and this can be used to determine
the error.
Requirements
Run DGAdmin before executing the compile command.
68P02900W22-R
5-9
GMR-02
Mar 2008
Auto-compile MMI script command
Auto-compile MMI script command
Name
auto_compile - Batch compiling of multiple MMI scripts.
Synopsis
auto_compile -C <Country> -v <Version> <filename or *>
Description
This utility allows a number of MMI scripts to be compiled sequentially. The software version
of the scripts must be the same and the correct compiler version must be selected. After
a successful compilation, the resultant binary and report les are created in the directory
where the scripts reside.

Table 5-3
Command line options (auto_compile command)

Description
Option
-C <Country>
The -C option identies the country in which to insert the BSS

record.
-v <Version>
The software version for compilation.
<lename or *>
Dene a directory where the scripts reside or a single MMI script.
5-10
68P02900W22-R
GMR-02
Mar 2008
Requirements
Requirements
Run DGAdmin before executing the auto_compile command.
Any parameters that contain spaces must be entered between single quotes.
Output
Output from the auto_compile utility is a batch logle. This shows each operation of the batch
process and any relevant report le created along with its path. The result of each compile,
successful or not, appears in the logle.
Once the batch process is complete the nal message in the log le states:
BATCH COMPLETED
The batch le resides in the directory of the original binaries.
Example auto_compile usage

The auto_compile utility works from the command line. The following command line can be
customized to perform the required batch compile:
auto_compile -C Austria -v 1.8.0.0 ~/scr_objs/1800x/*
This compiles all existing MMI scripts in the specied directory using the corresponding 1800
compiler. On successful completion, the report les and binaries reside in the chosen batch
directory.
Running cron jobs

A cronjob can be set up to schedule the running of auto_revgen or auto_compile or auto
_upgrade batch jobs. If cronjobs are set up, then the specic path for the DGAdmin executable
and the auto_revgen or auto_upgrade or auto_compile scripts must be entered along with
the les to be run through the batch process.
For example, when setting up a crontab le, 'cron', containing an auto_revgen cronjob to be
run at 10.20 a.m. every day, the cron le should contain the following:
20 10 * * * /usr/omc/DataGen/bin/DGAdmin
/usr/omc/DataGen/current/bin/auto_revgen -m -d -C
Austria -v 1.8.0.0 -c 0 /usr/omc/test/1800x/objects/*
NOTE
The complete path for DGAdmin, batch process, and the location of the binary les
must be entered.
To run the cronjob job, log on to the DataGen processor as omcadmin and enter the following
command:
68P02900W22-R
5-11
GMR-02
Mar 2008
Running cron jobs
crontab cron
To check the status of the cronjob, enter the following command:
crontab -l
5-12
68P02900W22-R
GMR-02
Mar 2008
Compress/uncompress binary object les
Name
cpdb -c - compress 1740, 1760 or 1800 binary object (.002) les.
cpdb -u - uncompress 1740, 1760 or 1800 binary object (.002) les.
Synopsis
Compress
cpdb -c <database object filename> <compressed object filename>
Where
Is
database object lename
name of the .002 le to compress
compressed object lename
the name of the compressed le
Uncompress
cpdb -u <database object filename> <uncompressed object filename>
Where
Is
database object lename
name of the compressed .002 le to

uncompress
uncompressed object lename
the name for the uncompressed le
Description
The above command allows binary object les to be compressed or uncompressed from the
command line. Revgen converts the binary object le into a DataGen script le. Revgen can
use both compressed and uncompressed binary object les.
68P02900W22-R
5-13
GMR-02
Mar 2008
Example
Example
The following are two examples of using the compress and uncompress commands:
cpdb -c BSS.002.uncompressed BSS.002.compressed

This compresses the le named BSS.002.uncompressed and names it
BSS.002.compressed.
cpdb -u BSS.002.compressed BSS.002.uncompressed

This uncompresses the le named BSS.002.compressed and names it
BSS.002.uncompressed.
Requirements
Run DGAdmin before executing the compress or uncompress command.
5-14
68P02900W22-R
GMR-02
Mar 2008
Delete database object (del) command
Name
del - Delete database object.
Synopsis
del <verification> <country> <BSS area> <configuration number>
Description
This utility deletes a DataGen BSS Conguration area.
NOTE
After the last Conguration area has been deleted, the BSS Area is also deleted.

Table 5-4
Command line options (del command)

Description
Option
<verication>
<country>
<BSS area>
<conguration number>
Off (0) performs action.
On (1) veries action without performing it (displays a

list with the number of rows that can be deleted from the
database).
The country name.

The BSS name.
The conguration number of the BSS area.
The deletion must be specied to the <verification> <country> <BSS area> <configuration
number> level.
68P02900W22-R
5-15
GMR-02
Mar 2008
Example
Example
The following is an example of how to use the delete command:
del 0 Austria Area10 0
where conguration number 0 is deleted from the Country (Austria) and BSS area (Area 10).
Requirements
Run DGAdmin before executing the delete command.
NOTE
If the BSS area is deleted, the related les in the DDS are also deleted.
5-16
68P02900W22-R
GMR-02
Mar 2008
MCDF lter command
MCDF lter command
Name
lter - allows the insertion or validation or exportation of MCDF les from and to the DataGen
database.
Synopsis
filter [-insert(default) | -validate | -export] -area <country:bss area:config
no> [-files[FileName...]|all (default) ]
Description
This utility allows MCDF les to be exported from the DataGen database or inserted into the
DataGen database. It is also used to validate les.

Table 5-5 Command line options (lter command)

Description
Option
insert
Insert the le or all les from the DataGen Directory Structure

(DDS) into the DataGen database.
validate
Validate the le or all les from the DDS. This checks the tables
for errors and does not affect the DataGen database.
export
Export the le or all les from the DataGen database into the DDS ~/dg/country/BSS_area_name/conguration_number/MCDF/.
country
The country name containing the BSS area.
bss area
The BSS area name.
cong no
The conguration number to lter.
les[FileName ...] | all]
If 'All' is selected, then all les will be either inserted, validated, or

exported. Otherwise only the specic le name or le names will
be used. Refer to Table 5-6 for valid le names.
Table 5-6 lists the valid le names to lter MCDF les.
68P02900W22-R
5-17
GMR-02
Mar 2008
Example
Table 5-6
Valid le names
FileName
Table
bss
BSS
site
Site
cab
Cabinet
hware
Hardware
gene
Generics
timer
Timer
modv
Modify Value
acct
Circuits
chan
Channels (The Channels table is

available in MCDF for RXCDR scripts
only).
link
Links
path
Paths
lapd
Lapd
cell
Cell
stat
Statistics
spec
Specic
rtf
RTF
dri
DRI
alg
Algorithm
ngbr
Neighbors
thro
Throttles
eas
EAS
dgtr
Daughters
pix
PIX
ksw
KSW
nsvc
Nsvc
hop
Hop
acs
ACS
Example
The following example demonstrates how to use the MCDF lter command:
filter -export -area Austria:Area10:0 -files all
5-18
68P02900W22-R
GMR-02
Mar 2008
Requirements
This example exports all the MCDF les for country Austria, BSS Area, Area10,
and conguration number 0 to the directory:
~/dg/Austria/Area10/conf0/MCDF/.
Requirements
Run DGAdmin before executing the lter command.
The MCDF le structure is interdependent. Therefore, in certain cases, a le can only be
validated if all its dependent les have been validated. For further details, refer to the MCDF
BSS and RXCDR tables in Chapter 6 MCDF tables.
68P02900W22-R
5-19
GMR-02
Mar 2008
MMI command generator (gcmd) command
MMI command generator (gcmd) command
Name
gcmd - generate BSS command le(s).
Synopsis
gcmd <Country>:<BSS area>:<Config No>[:Site name]
Description
This utility generates BSS command les from the DataGen database, for the objects specied
by the command line parameters.

Table 5-7 Command line options (gcmd command)

Option
<Country>
Description
The country name
<BSS area>
The BSS area
<Cong No>
The conguration number of the BSS
<Site name>
The site name (optional parameter)
5-20
68P02900W22-R
GMR-02
Mar 2008
Example
Example
The following are examples of how to use the gcmd command:
gcmd Austria:Area10:0
This example produces an MMI script for Austria BSS Area10, conguration number 0.
gcmd Austria:Area10:0:1
This example produces an MMI script for site 1 only in Austria BSS Area10, conguration
number 0.
Requirements
Run DGAdmin before executing the gcmd command.
Output
Output from the script is in the form of BSS command les which can be found in the directory
from where the command was run. A logle is also produced and the user is mailed the
command status on completion.
68P02900W22-R
5-21
GMR-02
Mar 2008
Name
dbaccess - optimize the DataGen database.
Synopsis
dbaccess db_dg clusters.sql
Description
In order to maximize free disk space, it is advisable to optimize the DataGen database. This
can be performed by running the script named clusters.sql.
NOTE
The DataGen GUI must be closed before running the command:
dbaccess db_dg clusters.sql
Example
The following is an example of how to use the dbaccess command:
cd /usr/informix/bin/dbaccess db_dg clusters.sql
Requirements
Run DGAdmin before executing the dbaccess command. Before starting the optimization,
execute the following command:
/usr/gsm/DataGen/bin/DGAdmin
5-22
68P02900W22-R
GMR-02
Mar 2008
Lock/unlock BSS area (lock_adm) command
Lock/unlock BSS area (lock_adm) command
Name
lock_adm - lock or unlock a BSS area conguration.
Synopsis
lock_adm -area <country name:BSS area name:config_no> [-who | -lock | -unlock]
Description
This utility allows a BSS area conguration to be:
Locked or Unlocked.
Queried about when and where a lock was applied.
A BSS area conguration is automatically locked while the user is working on it and is
automatically unlocked when the user is nished. However, due to occasional error conditions,
a BSS area conguration can remain locked. If this happens, it must then be unlocked using
the lock_adm command before further progress can be made.

Table 5-8 Command Line options (lock_adm command)

Option
Description
<country name>
The country name of the conguration
<BSS area
name>
<cong_no>
The BSS name of the conguration

The conguration number
who
Query about lock status
lock
Lock a conguration
unlock
Unlock a conguration
68P02900W22-R
5-23
GMR-02
Mar 2008
Example
Example
The following example shows how to use the lock_adm command:
This example is displayed if BSS Area10, conguration number 0 is locked or unlocked.

lock_adm -area Austria:Area10:0 -who
The following example shows how to unlock an area:

lock_adm -area Austria:Area10:0 -unlock
NOTE
This command should not be used when another user is genuinely accessing an area.
The following example shows how to lock an area:
lock_adm -area Austria:Area10:0 -lock
Requirements
Run DGAdmin before executing the lock_adm command.
Output
The lock option locks a BSS area. The unlock option unlocks a BSS area. The who option gives
the process id, the user name, the host name and the time when the area was locked as shown
in the following example:
omcadmin kiran>DGAdmin lock_adm -area Austria:182188:0 -lock
DATAGEN DATABASE LOCK ADMINISTRATION TOOL
BSS Area is already locked
Area: Austria, 182188, 0
5-24
68P02900W22-R
GMR-02
Mar 2008
Revgen command
Revgen command
Name
revgen - Generate MMI les from CM database objects.
Synopsis
revgen -d <CM Object Filename> -C <Country Name> -a <BSS Area Name> [-s <Sites
String>] [-i <area id>] [-c <config number>] [-r <reference config number>] [-B
<config file>] [-v <BSS Version Number>] [-n]
See Table 5-9 for options description.
Description
The CM Database Object does not contain all of the information needed to create a complete
DataGen record. The information missing is the name of the country, the BSS, and the names of
the sites. This information can be supplied in one of three ways:
The database where a previous conguration version of the BSS exists.
A conguration le.
The command line.
The command line options indicate the preferred method. If the CM Database Object contains
a site that is not named by any of these sources, it will be given a default name Site <N>,
where N is the site number.

Table 5-9 Command line options (revgen command)

Option
Description
-d <CM Object Filename>
The -d option takes a further parameter and identies the CM

Database Object's le name.
-C <Country Name>
The -C option identies the Country in which to insert the

BSS record.
Continued
68P02900W22-R
5-25
GMR-02
Mar 2008
Table 5-9
Command line options (revgen command) (Continued)

Description
Option
-a <BSS area name>
-s <Sites String>
-i <area id>
The BSS name for the original objects.

The -s option takes a further parameter and identies the
site names for the sites in the BSS. The names parameter is
a single option and must be placed in quotes. It consists of
the site number immediately followed by an equal sign (=)
and then the name of the site. The quotes prevent the names
parameter being split and information being lost. For example:
0=B06, 1=Hereford, 2=Upper Dunton
Dene a BSS area ID.
-c <cong number>
The -c option takes a further parameter and identies the

conguration version in which to insert the new DataGen
BSS record. If this option is not used, the revgen process
will pick out the next available conguration in the indicated
BSS records.
-r <reference cong
number>
The -r option takes a further parameter and identies the

reference conguration number. This number identies a
similar BSS which the revgen utility uses to look up in the
unscheduled site names.
-B <cong le>
The -B option takes a further parameter and identies a

conguration le to use to identify the BSS and the site
names. The structure of the conguration le is as follows.
Line
Line
Line
Line
1 - The Country name.

2 - The BSS name (and optionally BSS ID).
3 - The conguration number (may be blank).
4 onwards - Site numbers and names.
For example, a le with the contents:

UK
B06,6
0=B06
1=Hereford
2=Upper Dunton
would create a BSS record choosing the rst available
conguration number in country UK and BSS name B06
with ID of 6. Set site 0 up with name B06, site 1 as
Hereford and site 2 as Upper Dunton.
-v <BSS Version Number>
-n
The -v option takes a further parameter and identies the

conguration version number of the DataGen BSS record
for the reference conguration. This record will be used to
resolve any site numbers left unnamed by the -B or -s option.
If the reference contains the same site numbers with the
names that are required in the new record, then this is all that
needs to be supplied.
No SYSGEN generated.
5-26
68P02900W22-R
GMR-02
Mar 2008
Example
Example
The following is an example of how to use the revgen command:
revgen -d Area10.002 -C Austria -a Area10 -c 0 -v 1.7.4.0
This example creates a conguration number 0 for the CM Database Area10.002. The
conguration number (-c) is optional. If no conguration number is dened, the next available
number is used.
NOTE
If the DDS directory does not exist for the conguration, the command will fail.
Therefore before running the revgen command, type:
mkdir -p /home/<user_name>/dg/<country>/<BSS_area_name>/
<configuration_number>/002
Requirements
Run DGAdmin before executing the revgen command.
The DataGen database must be loaded with the GSM software versions, and any intermediate
software version requested by the upgrader to perform the Revgen.
Output
The output from this command is in the form of a set of GSM MMI command les, which
can be found in the relevant DDS command directory. The set of GSM MMI command les
are combined to produce one script (COMBINED) for the current DataGen BSS record. The
command status is mailed to the user upon completion.
68P02900W22-R
5-27
GMR-02
Mar 2008
Auto-Revgen command
Auto-Revgen command
Name
auto_revgen - batch Revgening of multiple binaries.
Synopsis
auto_revgen [-m] [-d] -C <Country> [-c <configuration number>] -v <Version>
<filename or *>
Refer to Table 5-10 for option descriptions.
Description
This utility allows a number of binaries of one software version to be Revgened sequentially,
creating the database areas under relevant BSS areas in the database. The binaries must all be
of the version specied. The BSS areas are named after the binary le names.
Extra options are available to export all the MCDF tables for each new area and to copy each
new area upon Revgen completion. An optional initial conguration number can be specied
for the rst new area, with subsequent new areas having the next available congurations
above the starting number.

Table 5-10 Command line options (auto_revgen command)

Description
Option
-m
Species that MCDF tables, should be exported after Revgen

(optional).
-d
Species that a copy of the new area should be made after Revgen is
complete (optional).
-C <Country>
The -C option identies the country in which to insert the BSS record.
-c <conguration>
-v <Version>
<lename or *>
The conguration number to Revgen the rst binary to (optional).

The software version to Revgen the binaries.
Denes a directory where the binary or binaries reside.
5-28
68P02900W22-R
GMR-02
Mar 2008
Requirements
Requirements
Run DGAdmin before executing the auto-revgen command.
Output
Output from the auto_revgen utility is a batch logle. This shows each operation of the batch
process and any relevant report le created along with its path. Any part of the batch process
which fails, will be reported along with an explanation. For example, when an attempted Revgen
is carried out on a non binary le.
Once the batch process is complete the nal message in the batch le states:
BATCH COMPLETED
Example
The auto_revgen utility works from the command line. The following command line can be
customized to perform the required batch Revgen:
auto_revgen -C Austria -v 1.8.0.0 ~/option_object/1800x/*
This Revgens all existing binaries in the specied directory to the corresponding 1760 areas
in the database. If the BSS areas already exist in the database, then the next available
conguration, for each new area is used.
auto_revgen -m -d -C Austria -c 25 -v 1.8.0.0 ~/option_object/1800x/*
This command Revgens all existing binaries. After each Revgen process, the MCDF tables
are exported for the new area. The area is copied to the next available conguration and the
MCDF tables for the copied area are exported. The process attempts to Revgen rst and then
assigns the conguration number 25. If the number is already in use, the next available number
greater than 25 will be selected.
68P02900W22-R
5-29
GMR-02
Mar 2008
Toggle permissions (tp) command
Toggle permissions (tp) command
Name
tp - Toggle Database Permissions.
Synopsis
tp -r | -u <user name> [<class>] [<mail address>]
Description
The DataGen user has a standard set of access permissions. This utility toggles between the
access permitted, and access denied states.

Table 5-11 Command line options (tp command)

Description
Option
<-r>
-u <user name>
[<class>] [<mail address>]
Reallocate grant permissions to all registered users.

Toggle permissions for the specied user.
Update class or mail address for the specied user.
Example
The following is an example of how to use the toggle command:
tp -u smithd
This example switches between access permitted and access denied or vice versa for user
smithd.
Requirements
Run DGAdmin before executing the tp command.
5-30
68P02900W22-R
GMR-02
Mar 2008
Version upgrader (upg) command
Version upgrader (upg) command
Name
upg - GSM BSS software version upgrader.
Synopsis
upg -C <country> -a <area> -c <config> -u <version> -t <target config>
Description
This utility copies the specied BSS area to a new conguration, and upgrades the new
conguration to the specied GSM BSS software version. If no parameters are specied, the
upgrader reports which upgrade paths are available. An upgrade path consists of a single
upgrade, or a series of upgrades to take the specied area from its current BSS/GSM software
version to an upgraded version.
Refer to Software Release Notes: DataGen (68P02900W76) for details of current upgrades
supported.

Table 5-12 Command line options (upg command)

Description
Option
-C <country>
-a <area>
-c <cong>
-u <version>
-t <target Cong >
BSS or RXCDR area country name.

BSS or RXCDR area name.
BSS or RXCDR area conguration to be upgraded.
GSM software version to which area is to be upgraded.
Target conguration number for upgrading.
68P02900W22-R
5-31
GMR-02
Mar 2008
Requirements
Requirements
Run DGAdmin before executing the upg command.
The DataGen database must be loaded with the GSM software versions and any intermediate
software version requested by the upgrader.
Output
Output from the upgrader consists of a screen report informing the user of the new conguration
number for the upgraded area and of the progress and status.
Example of upgrading
An example is shown below:
upg -C UK -a BSS_area -c 0 -u 1.8.0.0 -t 5
Where
Is
Country
UK
BSS area
BSS area
Conguration
Number
0 to version 1.8.0.0
Conguration
Number
NOTE
If the specied target conguration exists, the upgrade is aborted.
5-32
68P02900W22-R
GMR-02
Mar 2008
Auto-upgrader command
Auto-upgrader command
Name
auto_upgrade - batch upgrading of multiple binaries.
Synopsis
auto_upgrade [-m] [-d] -C <Country> [-c <start configuration number>] -v
<Version>-u <Upgrade Version> <filename or *>
Description
This utility allows a number of binaries of the same software version to be upgraded sequentially.
It creates new database areas under relevant BSS areas in the database. All the binary les
must be version specied. These new areas are then upgraded to the specied software version.
Extra options are available to export all the MCDF tables for each new area and to copy each
new area upon upgrade completion. An optional initial conguration number can be specied
for the rst new area with subsequent new areas having the next available congurations
greater than the initial number.

68P02900W22-R
5-33
GMR-02
Mar 2008
Requirements
Table 5-13 Command line options (auto_upgrade command)

Description
Option
m
Species that MCDF tables, should be exported after

revgen (optional).
Species that a copy of the new area should be made after

revgen (optional).
C <Country>
The -C option identies the Country in which to insert the

BSS record.
c <start conguration>
v <Version>
u <Upgrade Version>
<lename or *>
The conguration number to revgen the rst binary to

(optional).
The software version of the binary les.
The software version to which the resultant areas should
all be upgraded.
Dene a directory where the binaries reside or a single
binary.
Requirements
Run DGAdmin before executing the auto_upgrade command.
Output
Output from the auto_upgrade utility is a batch logle. This shows each operation of the batch
process and any relevant report les created and their location. Any part of the batch process
which fails is reported along with the reason for failure. For example, when an attempted
Revgen is performed on a non-binary le.
Once the batch process is complete the nal message in the batch le states:
BATCH COMPLETED
Example
The auto_upgrade utility works from the command line. The following command line can be
customized to perform the required batch upgrade:
auto_upgrade -C Austria -v 1.7.6.0 -u 1.8.0.0 ~/scr_objs/1760x/*
5-34
68P02900W22-R
GMR-02
Mar 2008
Example
This Revgens all existing binaries in the specied directory to corresponding 1760 areas in
the database. If the BSS areas corresponding to the binary le names already exist in the
database, then the next available conguration for each new area is used in each case. Each
newly created 1760 area is then upgraded to 1800.
auto_upgrade -m -d -C Austria -c 25 -v 1.7.6.0 -u 1.8.0.0 ~/scr_objs/1760x/*
This command Revgens all existing binaries as before. After each Revgen process, each area
is upgraded to 1800 and all MCDF tables are exported for the upgraded area. The upgraded
areas are then copied to the next available congurations and the MCDF tables for the copied
areas are exported. The process attempts to Revgen and assign conguration number 25. If the
number is already in use, the next available number greater than 25 is selected.
68P02900W22-R
5-35
GMR-02
Mar 2008
Country administration
Country administration
Introduction to country administration

The following describes how the DataGen user can create new Country and Network les in the
DataGen database using the Country Administration (CADM) feature. The various functions of
the CADM feature which enables the user to manipulate the les are:
Administration les are created and edited using the Generic Table Editor (GTE). The GTE
is also used to save the les to a specied name or to a supplied standard le name.
Default Country and Network administration les can be edited using the GTE. The GTE is
also used to save the les to a specied name or to a supplied standard le name.
Generate or update operations can be performed on the default Country and Network
administration les.
The CADM feature prompts the DataGen user to decide whether or not to notify the owners
and modiers of BSS area congurations about Countries and Networks that cannot be
deleted. Notication is by email.
Command Line Interface (CLI)

A Command Line Interface (CLI), enables the DataGen user to generate and update Country and
Network administration les in the DataGen database using CADM utilities.
Invoking xcadm
To invoke the Country Administration tool, execute the following procedure.
Procedure 5-1
Invoke the Country Administration tool
Start DataGen.
Open an Xterm window and execute the following commands:

DGAdmin
xcadm
If the Country Admin option is already in use, a warning message is
displayed. Refer to Figure 5-1.
Continued
5-36
68P02900W22-R
GMR-02
Mar 2008
Using the xcadm GUI
Procedure 5-1
Invoke the Country Administration tool (Continued)
Figure 5-1 Country Admin in use conrmation window
Click OK to continue.
Using the xcadm GUI

The xcadm GUI (Figure 5-2) is organized into three functional areas:
Menu bar
Data elds
Action buttons
Figure 5-2
The xcadm GUI
68P02900W22-R
5-37
GMR-02
Mar 2008
Menus
Menus
The menu bar enables the DataGen user to Create, Update and Edit Country, and Network
Administration les as follows.
File menu
The Exit option is the only option available, which is used to exit from the Country Administration
window.
Network menu
The following options are available:
Edit
Select to use GTE to edit the default Network Administration le.
Generate
Select to generate a Network Administration le from the DataGen database.
Update
Select to update the DataGen database with the default Network Administration le.
NOTE
Country and Network menu options are greyed out, depending on the operations
permitted at the corresponding time.
5-38
68P02900W22-R
GMR-02
Mar 2008
Data elds
Country menu
The following options are available:
Edit
Select to use GTE to edit the default Country.
Generate
Select to generate a Country Administration le from the DataGen database.
Update
Select to update the DataGen database with the default Country Administration le.
NOTE
For NEW users where no country.std le exists, select Generate from
the Country menu to automatically generate a country.std le in the
/omcadmin/dg/ADMIN/country directory. This also applies to the network.std
le.
Data elds
The following data elds are displayed on the xcadm GUI:
Country File
Displays the default Country Administration le name when the CADM GUI window
is opened.
Network File
Displays the default Network Administration le name when the CADM GUI window is
opened.
Action buttons
Table 5-14 shows the denitions for the action buttons on the xcadm GUI.
Table 5-14 Action buttons denitions

Button
Denition
Exit
The Exit button closes the CADM window.
Help
Not available in this version of DataGen.
68P02900W22-R
5-39
GMR-02
Mar 2008
CADM utilities
CADM utilities
The CADM utilities provide read and write access to the CADM administration les through the
File Format utilities (FFMT). FFMT utilities are part of the GTE functionality.
CADM administration les are held in the DataGen database in the following format:
The le contains country denitions, one denition per line.
Each eld is separated by a @ character.
The last eld of each line is terminated by a new line character.
Each eld is permitted to contain embedded spaces.
The le record is entered with the following syntax:

<country_name>@<MCC><new_line_character>
Where
Is
country_name
the name of the country.
MCC
the Mobile Country Code.
new_line_character
the character which designates the end

of the record.
5-40
68P02900W22-R
GMR-02
Mar 2008
Chapter
6
MCDF tables
68P02900W22-R
Mar 2008
6-1
GMR-02
Overview of MCDF tables
Overview of MCDF tables
Scope of MCDF tables

This specication gives in detail, the format of each of the les within the MCDF le set for use
in BSS versions 1.6.5.0 and beyond.
Its aim is to provide a clear, understandable description and format for the customer, the
developer, and any other audience which needs information about its scope.
This chapter denes the layout and format of each of the les within the MCDF le set.
NOTE
Refer to the appropriate DataGen manual Software Release Notes: DataGen
(68P02900W76) for Customer Committed Problem Resolutions to the software
release installed.
Ranges, default values, and dependencies

Due to MCDF supporting BSS versions 1.7.4.0, 1.7.6.0, and 1.8.0.0, it is important that
users adhere to all the ranges dened in the subsequent tables. Remember that ranges and
recommended values may change from one load to the next. Refer to the manual Technical
Description: BSS Command Reference (68P02901W23) for detailed information about the
parameters in the MCDF tables.
Viewing the MCDF tables

If accessing DataGen using Exceed and viewing the MCDF tables on a at screen monitor, users
should maximize Exceed to avoid possible DataGen GUI truncation.

The following diagrams show which tables are mandatory and which are optional (refer to
Figure 6-1 and Figure 6-2).
6-2
68P02900W22-R
GMR-02
Mar 2008
Figure 6-1 Non-collocated BSS hierarchy
ti-GS M-Non-colloca te d_BS S _hie ra rchy-00117-a i-s w
68P02900W22-R
6-3
GMR-02
Mar 2008
Figure 6-2 RXCDR Hierarchy

BSS Table
EAS Table
KSW Table
Cabinet Table
Hardware Table
MMS Table
Daughter Table
PIX Table
Generics Table
Timers Table
Circuits Table
Channel Table
LAPD Table
Links Table
Stats Table
Throttles Table
Specifics Table
Key
MCDF Table
Optional Table
File dependency ,
predecessor must exist
File dependency
if predecessor exists.
ti-GSM-RXCDR_Hierarchy-001 18-a i-sw
6-4
68P02900W22-R
GMR-02
Mar 2008
BSS table
BSS table
Description of BSS table

This table is at the top of the MCDF hierarchy and contains BSS specic information along with
a eld depicting the format of the MCDF le itself (refer to Table 6-1).
This table lists the elds as follows: Field name, Field width, range, and status.
Default lename: bss.mcd
Table 6-1 BSS specic table

Field Name
Field Width
Range
50
Text
Mandatory
50
Text
Mandatory
50
30 characters
Text
Mandatory
50
Text
50
0 to 16777215
50
Text
Country
Status
Used to verify the country name.

BSS Name
Used to verify the BSS name.
Software Version
Desired
Used to verify the GSM BSS software version.
BSS Serial
Optional
A complex code to refer to each BSS.

SPC BSC
Mandatory if
BSS area is
not an RXCDR
(refer Site
Type) otherwise
unused.
Used for element opc.

MSC Name
Optional
The name of the MSC the to which the BSS is connected.

SPC MSC
50
0 to 16777215
Mandatory if
the BSS area is
not an RXCDR
(refer Site
Type) otherwise
unused.
Used for element dpc.

Continued
68P02900W22-R
6-5
GMR-02
Mar 2008
Table 6-1
BSS specic table (Continued)
Field Name
Field Width
Range
50
Text
OMC Name
Status
Optional
Used to group BSSs together into OMC regions.

50
XCDR Location
0 to 1
Mandatory if
BSS area is
not an RXCDR
(refer Site
Type), otherwise
unused.
Used for element transcoder_location:

0
RXCDR
BSC/
Collocated
50
Site Type
0, 1 or 3
Mandatory
0 to 3
Mandatory
Used for element fm_site_type:

0
Collocated
BSC/BTS
BSC
BTS
Remote
transcoder
BSC Type
50
Used for element bsc_type:

0
Non-Abis,
only DHP
Non-Abis,
only BSP
and LCF
Non-Abis,
BSP, LCF
and OMF
Abis, only
BSP
Continued
6-6
68P02900W22-R
GMR-02
Mar 2008
Table 6-1 BSS specic table (Continued)

Field Name
Field Width
Range
Status
50
0 to 3
Mandatory for
a Non-remote
transcoder area.
Network Indicator
Used for element ni. Used for non-remote transcoder areas only.
50
A5 Encryption Order
0 to 7 for each
of the entered
elds, with a
maximum of 8
elds.
Optional
The order of the A5 encryption algorithms to be used by the BSS.

Digit
GSM Algorithm
No encryption
A5/1
A5/2
A5/3
A5/4
A5/5
A5/6
A5/7
5,3,1
1,2,3,4,5,6,7,0
The ciphering algorithms are

in the order A5/5, A5/3,A5/1
The order is A5/1 to A5/7
and no encryption.
50
Dynamic CSFP Recongure
1 character text
'Y', 'y' or 'N', 'n'
depicting [Y]es
or [N]o.
Mandatory
The BSS area (in SYSGEN mode) performs a dynamic recongure of

GPROCs to CSFPs.
50
Frequency Types Allowed
1-15
Mandatory
Used for the frequency_type parameter of the freq_types_allowed command. This denes
the valid frequency types for the current BSS area.
The valid frequency types are dened below:
Frequency Type
Numeric
Entry
PGSM
EGSM
PGSM EGSM
DCS1800
PGSM DCS1800
5
Continued
68P02900W22-R
6-7
GMR-02
Mar 2008
Table 6-1
BSS specic table (Continued)
Field Name
Field Width
EGSM DCS1800
PGSM, EGSM DCS1800
PCS1900
PGSM PCS1900
EGSM PCS1900
10
PGSM, EGSM PCS1900
11
DCS1800 PCS1900
12
PGSM, DCS1800 PCS1900
13
EGSM, DCS1800 PCS1900
14
PGSM, EGSM, DCS1800 PCS1900
15
PCS1900 Frequency Blocks
50
Range
A, B, C, D, E,
F, ALL
Status
Optional (Only
applicable from
1510).
The eld is used to dene the valid frequency blocks for PCS1900. Valid blocks are detailed in
Table 6-2.
NOTE
For a subset of blocks, a space character is required.
Table 6-2
Valid Frequency Blocks
Frequency
Block
Parameter
Channels
ALL
512-810
512-585
587-610
612-685
687-710
712-735
737-810
All entries into this eld must be separated with a space, for example, the blocks allowed are A,
B, D only, so the user must type:
A B D
Information must be entered this way when a subset of frequency blocks is required.
6-8
68P02900W22-R
GMR-02
Mar 2008
Site (BTS specic) table
Site (BTS specic) table
Description of Site (BTS specic) table

This table contains information regarding each site in the BSS area (refer to Table 6-3).
Default lename: bts.mcd
Table 6-3
BTS specic table
Field Name
Field Width
Range
Status
Site Name
50
Text
Mandatory
0 to 120,
251, 252
and 253 (up
to 1760).
0 to 100,
251, 252 and
253 (from
1800).
Mandatory
Text
Mandatory
The Unique Site Name.

Site Number
The Site Number within the BSS.

Site Conguration
The type of site: BSC, BSS, BTS, M_BTS (MCell family) or L_BTS (Horizonofce sites).
Frequency Type
0 to 3
Optional, defaults to 0 (only

applicable for pre-1510, refer
to Cabinet table frequency
type from 1510 onwards).
Denes the frequency range to use at this site.

Pre-BSSGSM 1510:
0 GSM 900 or EGSM 900
1 DCS 1800
2 PCS 1900
Continued
68P02900W22-R
6-9
GMR-02
Mar 2008
Table 6-3
BTS specic table (Continued)
Field Name
Field Width
Range
Status
BTS Type
0 to 2
Mandatory if site number is

not 0 and site conguration is
a BTS, otherwise unused.
Used for element bts_type:

0
only BTP
only BTP and DHP2
only BTP, DHP, and

RSLP
1
Device Type
Boolean

not 0, otherwise unused.
0 to 24

not 0, otherwise unused.
Used for element site_type:

0
Site type is BSP.
Site type is LCF.

2
Device ID
Used
0-16
0-16
0-24
for element Device ID of LCF or BSP:

BSP
LCF (Pre-1510)
LCF (1510 onwards)
Range
0-16
0-16
0-24
RSL Rate
Device
BSP
LCF (Pre-1510)
LCF (1510 onwards)
16 or 64
Mandatory
Used to determine the data rate of the RSL on BTSs.

Continued
6-10
68P02900W22-R
GMR-02
Mar 2008
Table 6-3
BTS specic table (Continued)
Field Name
Field Width
Range
Status
CSFP algorithm
10
See below
Optional
Used for determining the algorithm for dynamic conguration of CSFP and for the CSFP
download ow control percentage.
Entries are made in the following format:
Site 0:
ALG
Sites other than 0:
ALG_Pctg
Where ALG Is
NONE
ANY
STBY
POOL
And Pctg ranges from 10% to 100% in steps of 10.

For example:
(Site 0)
(Site other than 0)
(Site other than 0)
Dynamic Allocation
ANY
ANY_10
POOL_20
3
no/yes
Default is
no.
Optional. Applicable from

1600 for In Cell sites only.
Used to indicate whether the site uses dynamic allocation of terrestrial backing resources.
68P02900W22-R
6-11
GMR-02
Mar 2008
Cabinet table
Cabinet table
Description of Cabinet table

This mandatory table contains information about all of the non-default type cabinets throughout
the BSS area. Refer to Table 6-4. The default cabinet type is type 0 (BTS4).
Default lename: cab.mcd
NOTE
In GSR8, Horizon II micro shares the Horizon II mini cabinet identiers. Use the
Horizon II mini cabinet identiers when equipping Horizon II micro in the database.
Table 6-4 Cabinet table

Field Name
Field Width
Range
Site Number
0 to 120 (up
to 1760).
0 to 100 (from
1800).
Status
Mandatory
The site number at which the cabinet is located (refer to the description in Table 6-3).
2
Cabinet ID
0 to 15
Mandatory
Text or Numeric in
the range set out
below.
Mandatory
The CAB ID for the cabinet.

20
Cabinet Type
BTS_4D_48_VOLT
BTS_4D_27_VOLT
BSSC_48_VOLT
BSSC_27_VOLT
BTS_DAB
BSSC_DAB
EXCELL_4
EXCELL_6
TOPCELL
BTS_5
10
M_CELL_2
Continued
6-12
68P02900W22-R
GMR-02
Mar 2008
Table 6-4 Cabinet table (Continued)

Field Name
Field Width
Range
11
M_CELL_6
12
TCU_2
13
TCU_6
14
M_CELL_MICRO
15
M_CELLCITY
16
M_CELLARENA
17
LIBRA
18
HORIZONMACRO (THOR)
19
HORIZONMACRO_EXT (THOR_EXT)
20
M_CELLARENA_MACRO
21
PCU_CAB
22
HORIZONMICRO
23
HORIZONCOMPACT
24
HORIZONMACRO2
25
HORIZONMACRO2_EXT
26
{24281} HORIZON2MINI
27
{24281} HORIZON2MINI_EXT
Status
NOTE
Cabinet type LIBRA is not supported.
Frequency Type
1 to 15
Mandatory
The valid frequency types are dened in Table 6-5.

Option dependencies are dened in Table 6-6.
NOTE
The HORIZONMACRO/HORIZONMACRO_EXT cabinets can have PCS1900

as a valid frequency type. A PCS1900 cell with a HORIZONMACRO cabinet
must be a High Power cell. It can be set using the max_ts_bts prompt for
the add_cell command.
Multiple frequency types within a single cabinet are not supported by the
HORIZONMACRO2 and HORIZONMACRO2_EXT cabinet_types.
HDSL Modem
Used for the prompted parameter:

Integrated
Antenna
Used for the prompted parameter:
yes/no
Default is no.
Optional. Used only for

cabinet type 15/16/20.
Is HDSL Modem allowed?

yes/no
Default is no.
Optional. Used only for

cabinet type 15/16.
Is Integrated Antenna allowed?
68P02900W22-R
6-13
GMR-02
Mar 2008
Table 6-5 Frequency Types

Numeric
Entry
Frequency Type
PGSM
EGSM
PGSM EGSM
DCS1800
PGSM DCS1800
EGSM DCS1800
PGSM EGSM DCS1800
PCS1900
PGSM PCS1900
EGSM PCS1900
10
PGSM EGSM PCS1900
11
DCS1800 PCS1900
12
PGSM, DCS1800 PCS1900
13
EGSM, DCS1800 PCS1900
14
PGSM, EGSM, DCS1800 PCS1900
15
Table 6-6 Option dependencies

Then
If
Both Infrastructure Sharing Homogeneous
Cabinet and Infrastructure Sharing
Heterogeneous Cabinet options have been
purchased.
Each cabinet (within any given site)

supports multiple frequency types.
Valid Range: 1 to 15.
Both Infrastructure Sharing Homogeneous

Cabinet and Infrastructure Sharing
Heterogeneous Cabinet options have not
been purchased.
Only the rst cabinet for any given

site need have this eld set. Multiple
frequency types within a single cabinet,
or multiple frequencies within a number
of cabinets in a given site is not allowed.
Valid Range: 1, 2, 4 or 8.
Infrastructure Sharing Homogeneous

Cabinet has been purchased and
Infrastructure Sharing Heterogeneous
Cabinet options has not been purchased.
Each cabinet for any given site

can be congured to support
a different frequency type.
Valid Range: 1, 2, 4 or 8.
6-14
68P02900W22-R
GMR-02
Mar 2008
Hardware table
Hardware table
Description of Hardware table

This table contains information about all cages, default cabinets, and full height cards
throughout the BSS area. Each entry in the table contains details of one device noting the site,
cabinet, cage, and slot in which the device resides (refer to Table 6-7).
NOTE
The cabinets and cages are not explicitly noted in the table, more included within
the details of the cards.
Default lename: hw.mcd
Table 6-7
Hardware table
Field Name
Field Width
Site Number
Range
0 to 120, 251,
252 and 253
(up to 1760).
0 to 100, 251,
252 and 253
(from 1800).
Status
Mandatory
The Site number for this device/function.

Cabinet ID
0 to 15
Mandatory for non-M-Cell

sites and also at M-Cell
DRIs.
0 to 15
Mandatory for
non-M-Cell/Horizon sites,
otherwise unused.
0 to 28
Mandatory for
otherwise unused.
The CAB ID for this device/function.

Cage Number
The CAGE ID for this device/function.

Slot Number
The slot number for this device/function.

Not applicable for Horizon ofce DRIs. Refer to the DRI table (Table 6-25).
Continued
68P02900W22-R
6-15
GMR-02
Mar 2008
Table 6-7 Hardware table (Continued)

Field Name
Field Width
Range
Status
Device Name
Text
Optional
The name of this device at a BSS area:

BSS
AXCDR
The name of this device at an RXCDR area:
RXCDR
ABSS
The name of this device at a non-M-Cell site:
DRI
GPROC
LCF
GCLK
KSW
MSI
XCDR
The name of this device at an M-Cell site:
DRI
GPROC (This can only denote a BTP, and no other function)
MSI
The name of this device at a PCU:
PCU
PSP
DPROC
MSI (PICP MSIs for use at the PCU)
GBL
GDS
GSL
Device ID
0 to 255 (valid
range is device
dependent).
Mandatory if Device Name

is lled in.
0 to 255 (valid
range is device
dependent).
Optional
The rst device ID for this device.

Second Device ID
This eld is used only when a second device id is required. In the case of the DRI device, this
eld is actually the RCU number per sector and has a range of 0 to 24.
For MSI/XCDR devices, this is used to dene the MSI type (non-MCELL sites only).
Continued
6-16
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
MSI Type
255
MSI2 (non-MCell sites only)
21
MSI_NIU2 (Horizon II macro sites only)
12
RF Unit (Horizonofce sites only)
11
RESERVED
10
RESERVED
MSI_NIU_EXT_HDSL (MCell sites only)
MSI_NIU_HDSL (M-Cellcity/M-Cellarena only)
MSI_EXT_HDSL (Non MCell and non-RXCDR sites only)
RESERVED
RESERVED
RESERVED
MSI_NIU (MCell sites only)
GDP (is supported in 1.6.5.0 for non-MCell sites)
XCDR (non-MCell sites only)
MSI (non-MCell sites only)
NOTE
Manual equipage of MSI is not allowed on Horizon II
and Horizon II_ext cabinets.
MMS0 Protocol Type
TEXT (E1 or
HDSL)
Optional (Mandatory if
Integrated MCell HDSL
feature purchased and
msi_type is HDSL).
Used for the Enter MMS0 protocol type prompt in the equip MSI command.
MMS0 Timeslots
16 or 32
MMS0 Protocol Type is
HDSL).
Used for the Enter the number of time slots supported on MMS0 prompt in the equip MSI
command.
Continued
68P02900W22-R
6-17
GMR-02
Mar 2008

Field Name
Field Width
Range
MMS0 Modem Setting
TEXT (MASTER
or SLAVE)
Status
HDSL and msi_type is
NIU_HDSL).
Used for the Enter MMS0 modem setting prompt in the equip MSI command.
MMS1 Protocol Type
TEXT (E1 or
HDSL)
msi_type is HDSL).
Used for the Enter MMS1 protocol type prompt in the equip MSI command.
MMS1 Timeslots
16 or 32
HDSL).
Used for the Enter the number of time slots supported on MMS1 prompt in the equip MSI
command.
MMS1 Modem Setting
TEXT (MASTER
or SLAVE)
HDSL and msi_type is
NIU_HDSL).
Used for the Enter MMS1 modem setting prompt in the equip MSI command.
Continued
6-18
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Function Name
Range
Text
Status
Mandatory for GPROC
devices. Used for PCU
DPROC devices and PCU
PICP MSIs.
The name of this function at a non-M-Cell site. (This is only valid for a GPROC device entry).
NONE (This is a redundant GPROC)
BSP
CSFP
DHP
LCF
OMF
RCF
RSLF
The name of this function at an M-Cell site. (This is valid only for a GPROC device entry).
BTP
The name of this function at a PCU.
PICP (for a PCU DPROC)
PRP (for a PCU DPROC)
DPROC (mandatory for a PICP MSI at the PCU)
Function ID
See below
Optional
The rst ID of this function valid in GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows for non-M-Cell devices:
Continued
68P02900W22-R
6-19
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
DEVICE
FUNCTION
RANGE
USAGE
yes/no/<blank>
Represents whether or not

a gclk clkx0 is equipped
from 1.5.0.0.
GCLK
NONE
Not Used
GPROC
BSP
0-1
0 Controller, 1 Redundant
GPROC
BTP
0-1
0 Controller, 1 Redundant
GPROC
CSFP
0-1
CSFP ID
GPROC
DHP
0-7
Second ID (First ID is Cage

Number).
GPROC
LCF
0-24
First ID
NOTE
0 to 16 for
pre-1.5.1.0 and
0 to 24 from
1.5.1.0.
GPROC
OMF
Not Used
GPROC
RCF
0-7
First ID
GPROC
RSLF
0-7
First ID
KSW
yes/no/<blank>
Represents whether or
not DRIs are allowed on a
highway.
Used as follows for M-Cell devices:

DEVICE
FUNCTION
RANGE
GPROC
BTP
0 to 1
This is blank for a BTP in

an M-Cell Micro cabinet.
0 to 1
Used for MCU Card Frame

prompt.
MSI
USAGE
Used as follows for PCU devices:

Continued
6-20
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
DEVICE
FUNCTION
RANGE
USAGE
1 to 6, 11 to 16
MSI (PICP)
GBL
Used for the associated

DPROC ID.
Used for the FIRST MMS
ID.
GDS
N/A
Used for BSC MMS ID 1.
GSL
N/A
Associated GDS ID.
PCU
0 to 65535
Used for nsei. The

older binaries (1650,
1670) contain the NSEI
parameter in the Generics
table.
Used as follows for BSS area specic devices:

DEVICE
FUNCTION
AXCDR
Second Function ID
3
(Allow for
expansion)
RANGE
USAGE
yes/no
Used to specify use of CIC

validation.
0 to 1
Optional
NOTE
In the case of AXCDR, the Second Function ID represents eac_mode.
The second ID of this function is valid for GPROC and PCU entries, BSS, or RXCDR area
entries. Used as follows:
DEVICE
FUNCTION
GCLK
RANGE
USAGE
yes/no/<blank>
Represents whether a gclk

clkx1 is equipped from
1.5.0.0.
NONE
Not Used
BSP
0-2
Maximum number of MTLs
BTP
0-6
Maximum number of DRIs
CSFP
Not Used
DHP
1-6
Maximum number of DRIs
LCF
0-2
Maximum number of MTLs
OMF
Not Used
RCF
Not Used
RSLF
Not Used
Continued
68P02900W22-R
6-21
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
The applicable range for an LCF Maximum number of MTLs is 0-1 in pre-1.5.1.0 and 0-2 from
1.5.1.0 onwards (2 indicates a GPROC2 card is being used for this purpose). The applicable
range for an LCF Maximum number of LMTLs is 0-2 in 1.6.5.0 onwards.
Used for M-Cell devices as follows:
DEVICE
FUNCTION
MSI
RANGE
USAGE
0 to 1
Used for NUI Slot Number

prompt.

DEVICE
FUNCTION
RANGE
USAGE
MSI (PICP)
1 to 2
GBL
N/A
Used for the SECOND

MMS ID.
GDS
N/A
Used for BSC MMS ID 2.
GSL
0 to 24.
Used as the GSL_LCF_ID.
Used for DPROC SOCKET.

DEVICE
FUNCTION
BSS
RANGE
USAGE
yes/no
Used for transcoding type

(yes implies at a BSC, no at
an RXCDR).
RANGE
USAGE
Used as follows for RXCDR area specic devices:

DEVICE
FUNCTION
ABSS
Third Function ID
0 to 1
0 to 254
Species volume
control type
(0 off, 1 on).
Optional
The third ID of this function - valid in GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows:
Continued
6-22
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
DEVICE
FUNCTION
RANGE
USAGE
yes/no/<blank>
Represents whether or not

a gclk clkx2 is equipped
from 1.5.0.0.
GCLK
NONE
Not Used
BSP
Not Used
BTP
Not Used
CSFP
Not Used
DHP
Not Used
LCF
0 to 1
OMF
Not Used
RCF
Not Used
RSLF
Not Used
FUNCTION
RANGE
USAGE
1 to 31
N/A
Used for the start time slot.

Used for PCU MMS ID1.
RANGE
USAGE
yes/no
Used for dynamic

allocation.
RANGE
USAGE
Number supported CBLs.

DEVICE
GBL
GDS
DEVICE
FUNCTION
BSS
DEVICE
FUNCTION
ABSS
-15 to 15
3
Fourth Function ID
0 to 99
Species downlink audio

level offset.
Optional
The fourth ID of this function - valid for GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows for GPROC devices:
DEVICE
FUNCTION
RANGE
GPROC
LCF
0 to 6
USAGE
Used for the maximum
number of GSLs that the
LCF can manage.

Continued
68P02900W22-R
6-23
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
DEVICE
FUNCTION
RANGE
USAGE
GBL
1 to 31
Used for the end time slot.
GDS
N/A
Used for PCU MMS ID2.

DEVICE
FUNCTION
BSS
RANGE
USAGE
0 to 255
Used for darbc related CIC

blocking.
RANGE
USAGE
-15 to 15
Species uplink audio level

offset.

DEVICE
FUNCTION
ABSS
Fifth Function ID
0 to 1
Optional
The fth ID of this function - valid for PCU entries and BSS area specic entries.
Used as follows:
DEVICE
FUNCTION
RANGE
N/A
GDS
USAGE
Used for GDS TYPE.

DEVICE
FUNCTION
BSS
GBL T391 Timer
RANGE
USAGE
0 to 255
Used for darbc related

CIC unblocking.
5 to 29
Used only with the PCU

GBL device - optional.
Used to Enter the T391 timer prompt in the equip GBL command.
GBL T392 Timer
6 to 30

Used to Enter the T392 timer prompt in the equip GBL command.
GBL N391 Counter
1 to 255

Used to Enter the N391 counter prompt in the equip GBL command.
GBL N392 Counter
1 to 10

GBL N393 Counter
1 to 10

IP address
15
0 to 255 per byte

PSP device - optional.
Species the IP address of the PSP.

Continued
6-24
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Subnet mask
15
0 to 255 per byte

0 to 255 per byte

Status
Species the subnet mask of the PSP.

Router IP address
15
Species the router address of the PSP.

MSC MSI ID
0 to 123
Used only when MSI type

is GDP.
Species the id of a GDP whose MMS is available for routing the transcoding circuits of a
secondary GDP towards the MSC.
MSC MMS ID
0 only

is GDP.
Always set to zero, because MSIs cannot be used to provide MSC MMSs.
Transcoding
Capability
0 or 1

is GDP.
Species the transcoding functionality of the GDP board.
68P02900W22-R
6-25
GMR-02
Mar 2008
Generics table
Generics table
Description of Generics table

The Generics table contains a list of elements, including Motorola specic elements. For
convenience, the timer and statistics elements have been placed in separate les. Either the
value from the value eld (if present), or the Motorola recommended value, is set BSS-wide but
can be overridden for a site or cell by values in the Specics and Cell tables.
Table 6-8 outlines the parameters of the Generics table.
Default lename: gene.mcd
Table 6-8 Generics table

Field Name
Element Name
Field Width
50
Range
<element
name>[,<index>]
Status
Mandatory
Name of the element optionally followed by an index.

Recommended
Value
11
-2,147,483,647 to
+2,147,483,647
(Element dependent)
Mandatory
-2,147,483,647 to
+2,147,483,647
(Element dependent)
Optional
Recommended value of the element.

Value
11
Overrides the recommended value of the element.
6-26
68P02900W22-R
GMR-02
Mar 2008
Layout of elements in the MCDF Generics table
The elements in the Generics table are displayed in Table 6-9as follows:
Table 6-9
Generics table - elements

Element name
Recommended value
_bss_data,0
_bss_data,1
_bss_data,2
_bss_data,3
_bss_data,4
24
{32340}_bss_data,12
aci_error_clr_thresh
aci_error_gen_thresh
aci_error_inc
0 (if ECERM is restricted). 1

(if ECERM is not restricted).
10
adap_ho_alt_trigger_rxqual
11
adap_ho_pbgt
12
adap_ho_rxlev
13
adap_ho_rxqual
14
adap_trigger_pbgt
15
adap_trigger_rxlev_dl
16
adap_trigger_rxlev_ul
17
adap_trigger_rxqual_dl
18
adap_trigger_rxqual_ul
19
adap_trigger_hop_rxqual_dl
20
adap_trigger_hop_rxqual_ul
21
addr_ind_bit_8
22
alt_qual_proc
23
amr_fr_dl_la_enabled
24
amr_fr_ul_la_enabled
25
amr_hr_dl_la_enabled
26
amr_hr_ul_la_enabled
27
amr_hr_res_ts
2
Continued
68P02900W22-R
6-27
GMR-02
Mar 2008
Table 6-9 Generics table - elements (Continued)

Element name
Recommended value
28
amr_hr_intracell_ho_allowed
29
amr_hop_count
30
amr_inner_hr_usage_thres
101
31
amr_bss_half_rate_enabled
32
amr_half_rate_enabled
33
amr_bss_full_rate_enabled
34
amr_full_rate_enabled
35
amr_new_calls_hr
101
36
amr_recong_fr_to_hr
101
37
amr_ms_monitor_period
40
38
amr_ms_high_cmr
95
39
amr_ms_low_cmr
99
40
amr_ms_high_rxqual
41
amr_ms_low_rxqual
42
amr_dl_thresh_adjust
43
amr_dl_la_mode_chg_min
44
amr_force_hr_usage
45
{23956}arp_signal_sele
46
attach_detach
47
auto_dl_dur
48
auto_rf_loss_trace
49
ba_alloc_proc
50
band_preference
51
band_preference_mode
52
bep_period
53
bep_period2
54
ber_loss_daily
55
ber_loss_hourly
56
{22879}blind_search_preference
57
bounce_protect_margin
58
bs_ag_blks_res
59
bs_pa_mfrms
60
bs_pag_blks_res
61
bs_pbcch_blks
50
None
15
Continued
6-28
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
62
bs_pcc_chans
63
bs_prach_blks
64
{22586}bss_overload_control
65
bssap_ss
66
bssgp block retries
67
bssgp_cbl_bit
68
bssgp_fc_period_c
69
{23956}bssgp_pfc_bit
70
bssgp_racap_retries
71
bssgp_reset_retries
72
bssgp_unblock_retries
73
bss_egsm_alm_allowed
74
bss_msc_overload_allowed
75
bts_escalation
60
76
bts_p_con_ack
77
bts_p_con_interval
78
bts_power_control_allowed
79
bts_txpwr_max_inner
80
bvci
81
c31_hyst
82
c32_qual
83
call_trace_options
84
called_pci
85
calling_pci
86
carrier_disable_time
120
87
carriers_ins_pwr_fail
30
88
cbc_fast_select
89
cbc_intface_vers
90
cbc_vbind_cntr
91
cbs_outage_cntr
92
cbch_enabled
93
ccch_conf
94
ccch_load_period
95
cell_bar_access_class
12500
254
10
None
40
0
Continued
68P02900W22-R
6-29
GMR-02
Mar 2008

Element name
Recommended value
96
cell_bar_access_switch
97
cell_bar_qualify
98
cell_reselect_hysteresis
99
cell_reselect_offset
100
cell_reselect_param_ind
101
channel_reconguration_switch
102
cic_ccitt_order
103
cic_error_clr_threshold
104
cic_error_gen_threshold
105
cic_error_increment
106
ciph_mode_rej_allowed
107
clk_src_fail_reset_period
108
coincident_offset
109
confusion_msg_allowed
110
congest_at_source
111
congest_at_target
112
cp_option_reset_ckt
113
cp_option_rr_status
114
cr_calling
115
ct_ow_control_hi_level
60
116
ct_ow_control_lo_level
20
117
ct_ow_control_msc_trace
118
ddtr_ctrl_enabled
119
decision_1_dl_rxlev_av_h
120
decision_1_dl_rxlev_av_ih
121
decision_1_dl_rxlev_av_p
122
decision_1_dl_rxqual_av_h
123
decision_1_dl_rxqual_av_p
124
decision_1_n1
125
decision_1_n2
126
decision_1_n3
127
decision_1_n4
128
decision_1_n5
129
decision_1_n6
None
24
Continued
6-30
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
130
decision_1_n7
131
decision_1_n8
132
decision_1_ncell_rxlev_av_h_calc
133
decision_1_p1
134
decision_1_p2
135
decision_1_p3
136
decision_1_p4
137
decision_1_p5
138
decision_1_p6
139
decision_1_p7
140
decision_1_p8
141
decision_1_p_bgt_rxlev_av_h
142
decision_1_tim_adv_av_alg
143
decision_1_ul_rxlev_av_h
144
decision_1_ul_rxlev_av_ih
145
decision_1_ul_rxlev_av_p
146
decision_1_ul_rxqual_av_h
147
decision_1_ul_rxqual_av_p
148
decision_alg_type
149
delay_dl_rel_dur
50
150
delay_ul_rel_dur
18
151
direct_inner_zone_threshold
63
152
disuse_cnt_hreqave
153
dl_audio_lev_offset
154
dl_dtx_voice_data
155
dl_rxlev_ho_allowed
156
dl_rxqual_ho_allowed
157
dnlk_vad_dtx
158
dr_chan_mode_modify
159
dr_ho_during_assign
160
dr_preference
161
dr_standard_congest
162
dtx_required
163
dual_band_offset
0
Continued
68P02900W22-R
6-31
GMR-02
Mar 2008

Element name
Recommended value
164
dyn_step_adj
165
dyn_step_adj_fmpr
166
dynet_tchs_reserved
167
early_classmark_sending
168
efr_enabled
169
egprs_init_dl_cs
170
egprs_init_ul_cs
171
egsm_handover_threshold
172
emergency_class_switch
173
{24347}emergency_group_priority
174
en_incom_ho
175
enhanced_relief
176
{23956}eop_enabled
177
erc_ta_priority
178
extended_paging_active
179
fdd_gprs_qoffset
180
{22879}fdd_multirat_reporting
181
{22879}fdd_rep_quant
182
force_hr_usage
183
full_pwr_ross
184
gbl_thrput_period
185
gci_error_clr_thresh
186
gci_error_gen_thresh
187
gci_error_inc
188
gclk_qwarm_ag
189
global_reset_repetitions
190
gproc_slots
16
191
gprs_alarm_time
60
192
gprs_bs_cv_max
193
gprs_cell_reselect_hysteresis
194
gprs_com_ms_class
195
gprs_dl_pwr_mode
196
gprs_drx_timer_max
10
50
50

Continued
6-32
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
197
gprs_intraho_allwd
198
gprs_mac_mode
199
gprs_max_ul_ts
2 (not supported in 1800)
200
gprs_min_prr_blks
201
gprs_ms_pan_dec
202
gprs_ms_pan_inc
203
gprs_ms_pan_max
204
gprs_ms_txpwr_max_cch
205
gprs_network_operation_mode
206
{23956}gprs_par_wait_ind
207
gprs_pb
208
gprs_pc_alpha
209
gprs_pc_meas_chan
210
gprs_penalty_time
211
gprs_recong_thresh_idle_tch
212
gprs_reselect_offset
213
gprs_rxlev_access_min
214
{23956}gprs_sched_beta
None
3
150
16
NOTE
For DataGen 1740 and
1760, the gprs_sched_beta
parameter has the following
range: 0 to 2 with a default
value of 1.
215
gprs_sig_bvci
216
gprs_smg30_t3192
217
gprs_t3168
4000
218
gprs_t3192
500
219
gprs_temporary_offset
220
gprs_ts_cong_alg
221
{22708}gprs_type5_alg
222
gprs_ul_dl_bias
223
group_block_unblock_allowed
224
gsl_lcf_mapping
225
gsm_bss_half_rate_enabled
500
Continued
68P02900W22-R
6-33
GMR-02
Mar 2008

Element name
Recommended value
226
gsm_cell_id_format
227
gsm_half_rate_enabled
228
handover_power_level
229
handover_recognized_period
230
handover_required_curr_ch
231
handover_required_reject_switch
232
handover_required_sp_ver_used
233
hcs_thr
234
ho_exist_congest
235
ho_margin_def
236
ho_margin_usage_ag
237
ho_only_max_pwr
238
ho_pwr_level_inner
239
hop_count
240
hopping_support
241
hopping_systems_enabled,0
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
hopping_systems_hsn,0
258
259
255
Continued
6-34
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
260
261
262
263
264
265
266
267
268
269
270
271
272
273
hr_fr_hop_count
274
hr_intracell_ho_allowed
275
hr_res_ts
276
illegal_circuit_id
277
immediate_assign_mode
278
inact_cont_allow
279
{28075}improve_ts_enabled
280
{22404}imrm_dcs1800_weight
281
{22404}imrm_egsm_weight
282
{22404}imrm_force_recalc
283
{22404}imrm_pgsm_weight
284
{22404}imrm_umts_weight
285
inc_prp_cap_ena
286
intave
287
init_dl_cs
288
init_ul_cs
289
inner_hr_usage_thres
101
290
interband_ho_allowed
None
291
inter_cell_handover_allowed
292
interfer_bands,0
63
293
interfer_bands,1
63
Continued
68P02900W22-R
6-35
GMR-02
Mar 2008

Element name
Recommended value
294
interfer_bands,2
63
295
interfer_bands,3
63
296
interfer_bands,4
63
297
interfer_ho_allowed
298
intra_cell_handover_allowed
299
l_rxlev_dl_h
10
300
l_rxlev_dl_p
30
301
l_rxlev_ul_h
10
302
l_rxlev_ul_p
30
303
l_rxqual_dl_h
None
304
l_rxqual_dl_h_data
None
305
l_rxqual_dl_h_hopping
None
306
l_rxqual_dl_h_hopping_hr
None
307
l_rxqual_dl_h_hr
None
308
l_rxqual_dl_p
None
309
l_rxqual_dl_p_data
None
310
l_rxqual_dl_p_hopping
None
311
l_rxqual_dl_p_hopping_hr
None
312
l_rxqual_dl_p_hr
None
313
l_rxqual_ul_h
None
314
l_rxqual_ul_h_data
None
315
l_rxqual_ul_h_hopping
None
316
l_rxqual_ul_h_hopping_hr
None
317
l_rxqual_ul_h_hr
None
318
l_rxqual_ul_p
None
319
l_rxqual_ul_p_data
None
320
l_rxqual_ul_p_hopping
None
321
l_rxqual_ul_p_hopping_hr
None
322
l_rxqual_ul_p_hr
None
323
l_rxqual_ul_p_amr_fr
None
324
l_rxqual_ul_p_amr_hr
None
325
l_rxqual_ul_h_amr_fr
None
326
l_rxqual_ul_h_amr_hr
None
327
l_rxqual_ul_h_hopping_amr_fr
None
Continued
6-36
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
328
l_rxqual_ul_h_hopping_amr_hr
None
329
l_rxqual_dl_p_hopping_amr_fr
None
330
l_rxqual_dl_p_hopping_amr_hr
None
331
l_rxqual_dl_p_amr_fr
None
332
l_rxqual_dl_p_amr_hr
None
333
l_rxqual_dl_h_amr_fr
None
334
l_rxqual_dl_h_amr_hr
None
335
l_rxqual_dl_h_hopping_amr_fr
None
336
l_rxqual_dl_h_hopping_amr_hr
None
337
l_rxqual_ul_p_hopping_amr_fr
None
338
l_rxqual_ul_p_hopping_amr_hr
None
339
land_layer1_mode
340
layer_number
341
lcs_mode
342
link_about_to_fail
343
link_fail
344
local_maintenance
345
low_sig_thresh
346
lta_alarm_range
347
ltu_fw_auto_download
348
max_gprs_ts_per_carrier
349
max_ms_dl_buffer
350
max_ms_dl_rate
351
max_number_of_sdcchs
None
352
{22586}max_pagenum_per_sec
65535
353
max_paging_per_sec
354
max_q_length_full_rate_channel
355
max_q_length_sdcch
356
max_retran
357
max_rst_ckt_timer_exps
358
max_tx_bts
359
max_tx_ms
None
360
mb_preference
361
mb_tch_congest_thres
38400
900
120
0
100
Continued
68P02900W22-R
6-37
GMR-02
Mar 2008

Element name
Recommended value
362
missing_rpt
363
mmi_cell_id_format
364
mms_cat_enable
365
mms_cong_type
366
mms_cong_type_pcu
367
{22586}msc_bss_overload_allowed
368
msc_preference
369
msc_qt
370
msc_release
371
ms_distance_allowed
372
ms_max_range
63
373
ms_p_con_ack
374
ms_p_con_interval
375
ms_power_control_allowed
376
ms_power_offset
377
ms_txpwr_max_cch
378
ms_txpwr_max_inner
379
mspwr_alg
380
mtl_loadshare_granularity
381
multiband_reporting
382
{22708}nacc_enabled
383
n_avg_i
384
ncc_of_plmn_allowed
385
nccr_enabled
386
nc_non_drx_period
387
nc_reporting_period_i
388
nc_reporting_period_t
389
neighbor_journal
390
new_calls_hr
391
ns_alive_retries
392
ns_block_retries
393
ns_unblock_retries
394
nsei
395
num_audit_retries
84
None
255
101
None
1
Continued
6-38
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
396
num_gbl_dl_thrput_samples
10
397
num_gbl_ul_thrput_samples
10
398
number_of_preferred_cells
16
399
number_sdcchs_preferred
None
400
option_alg_a5_1
401
option_alg_a5_2
402
option_alg_a5_3
403
option_alg_a5_4
404
option_alg_a5_5
405
option_alg_a5_6
406
option_alg_a5_7
407
option_emergency_preempt
408
{24347}option_preempt
409
outer_zone_usage_level
410
override_intra_bss_pre_transfer
411
pbgt_mode
412
pccch_drx_timer_max
413
pccch_enabled
414
pcr_enable
415
pcr_n1
127
416
pcr_n2
3750
417
pcu_redundancy
418
pcu_red_map_01
-1
419
pcu_red_map_02
-1
420
pcu_red_map_11
-1
421
pcu_red_map_12
-1
422
pcu_red_map_21
-1
423
pcu_red_map_22
-1
424
penalty_time
425
percent_traf_cs
426
{23956}pfc_be_arp
427
phase2_classmark_allowed
428
phase2_resource_ind_allowed
429
phase_lock_gclk
55
Continued
68P02900W22-R
6-39
GMR-02
Mar 2008

Element name
Recommended value
430
phase_lock_retry
255
431
pic_error_clr_thresh
432
pic_error_gen_thresh
433
pic_error_inc
434
pool_gproc_preemption
435
poor_initial_assignment
436
pow_inc_step_size_dl
437
pow_inc_step_size_ul
438
pow_red_step_size_dl
439
pow_red_step_size_ul
440
prach_s
441
prach_tx_int
14
442
primary_pcu
-1
443
prioritize_microcell
444
priority_class
445
prm_gmsk_cap_x_changed
446
protect_last_ts
447
prr_aggr_factor
448
psi1_repeat_period
449
pwr_handover_allowed
450
pwrc
451
{23956}qos_mtbr_be_dl
452
{23956}qos_mtbr_be_ul
453
{23956}qos_mtbr_bg_dl
454
{23956}qos_mtbr_bg_ul
455
{23956}qos_mtbr_i1_dl
456
{23956}qos_mtbr_i1_ul
457
458
459
460
461
{22879}qsearch_c
462
qsearch_p

15
0
Continued
6-40
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
463
queue_management_information
50
464
rac
None
465
ra_colour
None
466
ra_reselect_hysteresis
467
rach_load_period
468
rach_load_threshold
469
rach_load_type
470
radio_link_timeout
471
rapid_pwr_down
472
rci_error_clr_threshold
473
rci_error_gen_threshold
474
rci_error_increment
475
recong_fr_to_hr
476
red_loss_daily
16
477
red_loss_hourly
20
478
red_loss_oos
511
479
red_loss_restore
600
480
red_psp_audit_tmr
24
481
red_time_oos
25
482
red_time_restore
483
reestablish_allowed
484
remote_loss_daily
16
485.
remote_loss_daily_pcu
16
486
remote_loss_hourly
20
487
remote_loss_hourly_pcu
20
488
remote_loss_oos
511
489
remote_loss_oos_pcu
511
490
remote_loss_restore
600
491
remote_loss_restore_pcu
600
492
remote_time_oos
25
493
remote_time_oos_pcu
25
494
remote_time_restore
600
495
remote_time_restore_pcu
600
496
report_resource_tch_f_high_water_mark
0
16
1000
101
600
0
2
Continued
68P02900W22-R
6-41
GMR-02
Mar 2008

#
Element name
Recommended value
497
report_resource_tch_f_low_water_mark
12
498
res_gprs_pdchs
499
res_ts_less_one_carrier
500
rf_res_ind_period
501
rpd_offset
502
rpd_period
503
rpd_trigger
45
504
rpt_bad_qual_no_mr
505
{22586}rsl_congestion_alarm_timer
506
{22586}rsl_lcf_congestion_thi
60
507
{22586}rsl_lcf_congestion_tlow
25
508
rtf_path_enable
509
rxlev_access_min
510
rxlev_dl_zone
63
511
rxlev_min_def
15
512
rxlev_ul_zone
63
513
sccp_bssap_mgt
514
scr_enabled
515
sdcch_ho
516
sdcch_need_high_water_mark
517
sdcch_need_low_water_mark
12
518
sdcch_timer_ho
519
sdcch_tch_band_reassign_delay
520
search_prio_3g
521
secondary_freq_type
522
second_asgnmnt
523
{22879}serving_band_reporting
524
sgsn_r
525
sgsn_release
526
sig_lnk_tst_allow
527
slip_loss_daily
528
slip_loss_hourly
529
slip_loss_oos
255
530
slip_loss_restore
600
0
None
10
0
60000
None
10
Continued
6-42
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
531
smg_gb_vers
31
532
sms_dl_allowed
533
sms_tch_chan
534
sms_ul_allowed
535
ssp_burst_delay
200
536
ssp_burst_limit
10
537
ss7_mode
538
ssm_critical_overload_threshold
80
539
ssm_normal_overload_threshold
70
540
static_sync_timer
541
stat_interval
542
{22076}stop_dri_tx_enable
543
{22076}stop_dri_tx_time
544
stp_pc
545
stp_pc_enabled
546
{24347}sw_pdtch_priority
547
sw_ts_less_one_carrier
548
swfm_enable
549
switch_gprs_pdchs
550
sync_loss_daily
16
551
sync_loss_daily_pcu
16
552
sync_loss_hourly
20
553
sync_loss_hourly_pcu
20
554
sync_loss_oos
511
555
sync_loss_oos_pcu
511
556
sync_loss_restore
600
557
sync_loss_restore_pcu
600
558
sync_time_oos
25
559
sync_time_oos_pcu
25
560
sync_time_restore
600
561.
sync_time_restore_pcu
600
562
t_avg_t
10
563
t_avg_w
10
564
tch_busy_critical_threshold
12000
30
0
300
None
0
14
None
100
Continued
68P02900W22-R
6-43
GMR-02
Mar 2008

Element name
Recommended value
565
tch_busy_norm_threshold
100
566
tch_congest_prevent_thres
100
567
tch_ow_control
568
tch_full_need_low_water_mark
569
{24620}tch_usage_threshold
570
temporary_offset
571
{23956}thp_be_weight
40
572
{23956}thp_bg_weight
40
573
{23956}thp_i2_weight
40
574
{23956}thp_i3_weight
40
575
threshold
576
timing_advance_period
577
tlli_blk_coding
578
trace_msgs_after_ho
579
trace_msgs_before_ho
580
trunk_critical_threshold
50
581
trunk_major_threshold
10
582
ts_alloc_ag
583
tsc_update_method
584
tx_integer
585
tx_power_cap
586
u_rxlev_dl_ih
45
587
u_rxlev_dl_p
40
588
u_rxlev_ul_ih
45
589
u_rxlev_ul_p
40
590
u_rxqual_dl_p
None
591
u_rxqual_dl_p_amr_hr
None
592
u_rxqual_dl_p_hr
None
593
u_rxqual_ul_p
None
594
u_rxqual_ul_p_hr
None
595
ul_audio_lev_offset
596
ul_rxlev_ho_allowed
597
ul_rxqual_ho_allowed
598
{22879}umts_band_preferred
0
255
Continued
6-44
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
599
{22879}umts_cpich_ec_no_min
-15
600
{22879}umts_cpich_rscp_min
-90
601
unequipped_circuit_allowed
602
use_bcch_for_gprs
603
use_derived_ho_power
604
use_neighbor_pbgt_hreqave
605
volume_control_type
606
wait_for_reselection
10
607
wait_indication_parameters
608
worse_neighbor_ho
609
zone_ho_hyst
610
zone_pingpong_enable_win
30
611
zone_pingpong_disable_win
30
612
zone_pingpong_preferred_zone
613
zone_pingpong_count
255
30
68P02900W22-R
6-45
GMR-02
Mar 2008
Timer table
Timer table
Description of Timer table

This table contains a list of timer elements, including Motorola specic elements. Either the
value from the value eld (if present) or the Motorola recommended value is set bss-wide, but
can be overridden for a site or cell by values in the Specics table.
Table 6-10 outlines the parameters of the Timer table.
Default lename time.mcd
Table 6-10 Timer table

Field Name
Field Width
Element Name
50
Range
Status
<element
name>[<index>]
Mandatory
Name of the timer element optionally followed by an index.

Recommended
Value
11
-2,147,483,648 to
+2,147,483,647
(Element dependent)
Mandatory
-2,147,483,648 to
+2,147,483,647
(Element dependent)
Optional
Recommended value of the timer element.

11
Value
Overrides the recommended value for the timer element.
Layout of timer elements in the MCDF Timer table

Table 6-11 shows the layout of the timer element parameters in the Timer table.
Table 6-11 Timer table - elements

#
Element name
Recommended value
add_access_class
60000
assign_successful
30000
bcch_info
bounce_protect_cong_tmr
bounce_protect_qual_tmr
2000
Continued
6-46
68P02900W22-R
GMR-02
Mar 2008
Table 6-11 Timer table - elements (Continued)

#
Element name
Recommended value
bsc_audit
bsc_audit_response
30000
{23956}
bssgp_dwnld_retry
bssgp_t1_timer
10
bssgp_t2_timer
60
11
{27717} bssgp_t4_timer
800
12
3000
13
3000
14
3000
15
bssmap_t1
30000
16
bssmap_t4
50000
17
bssmap_t7
30000
18
bssmap_t8
28000
19
bssmap_t10
28000
20
bssmap_t11
28000
21
bssmap_t13
40000
22
bssmap_t19
30000
23
bssmap_t20
30000
24
bssmap_tqho
30000
25
bts_audit
60000
26
bts_audit_response
30000
27
carrier_free_immediate
28
cbch_1
30000
29
cbch_2
30000
30
cbch_3
35000
31
channel_act
10000
32
channel_teardown
28000
33
cipher_comp_ms
28000
34
ciphering_successful
30000
35
circuit_reset_ack
70000
36
clear_cmd_ext_ho
30000
37
clear_command
30000
38
dealloc_inact
10000
120000
120000
Continued
68P02900W22-R
6-47
GMR-02
Mar 2008
Table 6-11
#
Timer table - elements (Continued)

Element name
Recommended value
39
downlink_sync_timer
1000
40
dynet_retry_time
1000
41
early_classmark_delay
42
emerg_reserved
43
ext_rtry_cand_prd
4000
44
ext_ho_allocation
30000
45
ow_control_t1
20000
46
ow_control_t2
30000
47
ho_ack
48
ho_allocation
30000
49
ho_complete
28000
50
ho_request
28000
51
ho_successful
30000
52
hop_count_timer
53
initial_sync_timer
4000
54
lb_int_bssmap_t4
50000
55
lb_int_bssmap_t13
40000
56
lb_int_called_pci
57
llb_int_calling_pci
58
lb_int_clear_command
59
lb_int_cr_calling
60
lb_int_dpc
61
lb_int_global_reset_repetitions
62
lb_int_sccp_released
30000
63
lb_int_sccp_tconn_est
30000
64
lb_int_sccp_tiar
30000
65
lb_int_sccp_tias
30000
66
lb_int_sccp_trel
10000
67
lb_int_spi
60000
68
lb_int_ss7_l2_t1
50000
69
lb_int_ss7_l2_t2
25000
70
lb_int_ss7_l2_t3
1400
71
lb_int_ss7_l2_t4
600
72
lb_int_ss7_l2_t5
100
0
120000
5000
30000
Continued
6-48
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
73
lb_int_ss7_l2_t6
5000
74
lb_int_ss7_l2_t7
1000
75
lb_int_ss7_l3_t1
850
76
lb_int_ss7_l3_t2
1400
77
lb_int_ss7_l3_t4
850
78
lb_int_ss7_l3_t5
850
79
lb_int_ss7_l3_t12
1150
80
lb_int_ss7_l3_t13
1150
81
lb_int_ss7_l3_t14
2500
82
lb_int_ss7_l3_t17
1150
83
lb_int_ss7_l3_t22
270000
84
lb_int_ss7_l3_t23
270000
85
lb_int_ss7_slt_t1
8000
86
lb_int_t_stat_info
90000
87
lcs_perf_location
300000
88
lcs_segmentation
10000
89
lcs_supervision
30000
90
lmtl_loadshare_granularity
91
mode_modify
10000
92
mode_rr_modify_ack
28000
93
ms_sapi3_est
28000
94
neighbor_report_timer
95
ns_alive_timer
96
ns_block_timer
97
ns_reset_period
125
98
ns_reset_timer
40
99
ns_test_timer
30
10
100
radio_chan_released
30000
101
register_exp
102
rf_chan_rel_ack
103
rr_ny1_rep
104
rr_T3101
5000
105
rr_T3103
30000
106
rr_T3105
60
120000
10000
20
Continued
68P02900W22-R
6-49
GMR-02
Mar 2008
Table 6-11
#
Timer table - elements (Continued)

Element name
Recommended value
107
rr_T3109
14400
108
rr_T3111_sd
1500
109
rr_T3111_tch
1500
110
rr_T3212
111
rtry_cand_prd
4000
112
sacch_info
2000
113
sccp_released
30000
114
sccp_tconn_est
30000
115
sccp_tiar
30000
116
sccp_tias
30000
117
sccp_trel
10000
118
sm_audit_response
30000
119
spi
60000
120
ss7_l2_t1
50000
121
ss7_l2_t2
25000
122
ss7_l2_t3
1400
123
ss7_l2_t4
600
124
ss7_l2_t5
100
125
ss7_l2_t6
5000
126
ss7_l2_t7
1000
127
ss7_l3_t1
850
128
ss7_l3_t2
1400
129
ss7_l3_t4
850
130
ss7_l3_t5
850
131
ss7_l3_t12
1150
132
ss7_l3_t13
1150
133
ss7_l3_t14
2500
134
ss7_l3_t17
1150
135
ss7_l3_t22
270000
136
ss7_l3_t23
270000
10
NOTE
ss7_l3_t23 has a value of 270000 if ss7_mode = 0 (ITU) but ss7_l3_t23
has a value of 90000 if ss7_mode = 1 (ANSI).
Continued
6-50
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
137
ss7_slt_t1
8000
138
start_ack
30000
139
t_stat_info
90000
140
ts_free_immediate
50000
141
uplink_sync_timer
1000
142
valid_candidate_period
4000
68P02900W22-R
6-51
GMR-02
Mar 2008
Modify Value table
Modify Value table
Description of Modify Value table

This table contains the modify_value commands. The table is applicable only for MMS and LCF
device functions currently as DataGen only supports these devices within the modify_value
command.
Default lename: modv.mcd
Table 6-12 shows the MMS element parameters:
Table 6-12
Modify Value table
Field Name
Field Width
Range
Status
Location
0 to 120
Mandatory
This eld identies the location (Site) at which the MMS for the MSI/XCDR card, DYNET, or
LCF device resides. Used for the location parameter of the modify_value command.
25
Value Name
Refer Applicable
Names below.
Mandatory
Applicable Names
MMS:
nbit
ber_oos_mon_period
ber_restore_mon_period
phase_lock_duration
mms_priority
hdsl_oos_mon_period
hdsl_restore_mon_period
LCF:
*max_opls
*max_opls is not currently supported,
except for Motorola internal use.
DYNET:
shared_timeslots
Used for the value_name parameter of the modify_value command.
New Value
Refer Range Table

below.
Mandatory
The applicable ranges are shown in the following table:

Continued
6-52
68P02900W22-R
GMR-02
Mar 2008
Table 6-12
Modify Value table (Continued)
Field Name
Value Name
Field Width
Minimum Value
Range
Status
Maximum Value
nbit
ber_oos_mon_period
60
ber_restore_mon_period
18000
phase_lock_duration
3600
mms_priority
255
max_opls
hdsl_oos_mon_period
3598
hdsl_restore_mon_period
65534
shared_timeslots
32
Used for the new_value parameter of the modify_value command.

Device Function
TEXT
Mandatory
MMS, LCF, and DYNET are the only applicable device functions for this table. Used for
dev_func parameter of the modify_value command.
Device Fn ID1
Based on site type

below:
Mandatory
Used for the dev_fun_id1 parameter of the modify_value command.

MMS - Site Types:
0 to 56/71 at a BSC/RXCDR
0 to 9 at a non-M-Cell BTS
0 to 1 at an M-Cell2 BTS
0 to 3 at an M-Cell6 BTS
0 at an M-Cellmicro BTS
This value denes the MSI identier for the
MMS device function.
LCF:
0 to 24
This value denes the LCF id to which
this modify_value command relates.
DYNET:
0 to 19
This value denes the DYNET rst id to which this modify_value
command relates.
Continued
68P02900W22-R
6-53
GMR-02
Mar 2008
Table 6-12
Modify Value table (Continued)
Field Name
Device Fn ID2
Field Width
Range
Status
0 or 1
Mandatory
Used for the dev_fun_id2 parameter of the modify_value command

MMS:
This value denes the MMS identier for the MMS device function.
LCF:
0 is the only applicable value.
DYNET:
0 to 2.
This value denes the DYNET second id to which this modify_value
command relates.
Device Fn ID3
Mandatory (Not
required for DYNET).
Used for the dev_fun_id3 parameter of the modify_value command.

This parameter must be entered as required by the modify_value command, but it serves no
purpose to the MMS/LCF/DYNET device functions. It is added to allow support of further
modify_value commands as and when required.
6-54
68P02900W22-R
GMR-02
Mar 2008
Circuit table
Circuit table
Description of Circuit table

Table 6-13 contains all MTL, LMTL, and OML signalling links. It also contains the terrestrial
circuits to timeslots at the BSC for radio trafc channels. (Typical commands supported are
chg_ts_usage and add_circuit/equip CIC).
NOTE
The MSIs and MMSs required are detailed in the hardware le.
Default lename: acct.mcd
Table 6-13 Circuit table

Field Name
Field Width
Range
Status
Site Number
Mandatory
Value must always be 0 unless Type = RES in which case the full range applies.
This eld identies the Site at which the MSI/XCDR card resides.
MSI
0 to 56
(0 to 71
for RXCDR)
(0 to 123 for LMTL
devices)
Mandatory
This eld refers to the MSI/XCDR ID of the entry.

MMS
0 to 1
Mandatory
This eld refers to the MMS of the MSI/XCDR card of the entry.
Continued
68P02900W22-R
6-55
GMR-02
Mar 2008
Table 6-13 Circuit table (Continued)

Field Name
Field Width
Range
Status
Type
String width 4
Mandatory
The type of entry being referred to as follows:

Abbreviation
TCH
OML
OPL
MTL
LMTL
XBL
CBL
RES
Description
Trafc channel
Operations and maintenance link device
Optimization Link
Message transfer link device
Location message transfer link device
Transcoder base station link
Cell Broadcast Link
Reserve specied timeslot(s)
2
Device ID
See below
Mandatory if Type is CBL,

OML, OPL, MTL, LMTL, or
XBL, otherwise unused.
This eld contains the device id for the CBL, OML, OPL, MTL, LMTL, and XBL devices.
The range for the IDs are as follows:
ID
CBL
OPL
OML
MTL
LMTL5
XBL
Associated Device
ID
Range
0
0
0 to 3
0 to 15
0 to 15
0 to 31 (Pre
1600), 0 to 9
(From 1600)
3
1 to 128
Mandatory if not used for

signalling links.
Provides the ID of the associated RXCDR and AXCDR when at the BSS and the associated
BSS and ABSS when at the RXCDR.
At the BSC this is the device ID, which corresponds to the RXCDR which provides the TRAU
resource for the CIC.
At the RXCDR this is the device ID, which corresponds to the BSS which is managing the CIC.
(This eld is not valid for local transcoding BSCs).
Start Timeslot
1 to 31
Mandatory
The Timeslot at which the dened block is to start.

End Timeslot
1 to 31
Mandatory if Type = TCH or

RES, otherwise unused.
The Timeslot at which the dened block is to end.

Continued
6-56
68P02900W22-R
GMR-02
Mar 2008
Table 6-13 Circuit table (Continued)

Field Name
Field Width
Range
Start CIC
0 to 65,535
Status
Mandatory if Type = TCH,
otherwise unused.
The CIC at which the dened block is to start.

End CIC
0 to 65,535

otherwise unused.
0 to 3

otherwise unused.
The CIC at which the dened block is to end.

Start Group
The starting group number for the start timeslot.

End Group
0 to 3

otherwise unused.
0 to 71

otherwise unused.
The ending group number for the end timeslot.

MSC MSI
MSI used to the MSC (valid only for local transcoding BSC and RXCDR sites).
MSC MMS
0 to 1

otherwise unused.
MSC used to the MSC (valid only for local transcoding BSC and RXCDR sites).
MSC Start Timeslot
1 to 31

otherwise unused.
The starting timeslot (valid only for local transcoding BSC and RXCDR sites).
MSC End Timeslot
1 to 31

otherwise unused.
The end timeslot (valid only for local transcoding BSC and RXCDR sites).
BSS Operator
20
20 character string
Mandatory if Type = CBL,

otherwise unused.
Used for the BSS Operator name of the equip CBL command.
CBC Operator
20
20 character string
Mandatory if Type = CBL,

otherwise unused.
Used for the CBC Operator name of the equip CBL command.
68P02900W22-R
6-57
GMR-02
Mar 2008
Channel table
Channel table
Description of Channel table

Table 6-14 is required only for Remote Transcoders. This table contains the OML and MTL
signalling links through the remote transcoder. It also contains details of the trafc channels
between the MSC and the BSC on the remote transcoder. The MSIs and MMSs required are
detailed in the hardware table Table 6-7.
Default lename: chan.mcd
Table 6-14 Channel table

Field Name
Type
Field Width
Range
Status
TEXT
Mandatory
The type of entry being referred to as follows:

TCH
LINK
MSI A
Trafc channel (add_channel)

OML/MTL/CBL link (add_rxcdr_link/add_link)
3
0 to 123
Mandatory
0 to 1
Mandatory
1 to 31
Mandatory
This eld refers to the MSI ID of the A side.

MMS A
This eld refers to the MMS ID of the A side.

Start Timeslot A
The A side Timeslot at which the dened block is to start.

End Timeslot A
1 to 31
Mandatory
The A side Timeslot at which the dened block is to end.

Start Group A
0 to 3
Mandatory if Type
is TCH, otherwise
unused.
0 to 3
Mandatory if Type
is TCH, otherwise
unused.
0 to 123
Mandatory
The A side group at which the dened block is to start.

End Group A
The A side group at which the dened block is to end.

MSI B
This eld refers to the MSI ID of the B side.

Continued
6-58
68P02900W22-R
GMR-02
Mar 2008
Description of Channel table
Table 6-14 Channel table (Continued)

Field Name
MMS B
Field Width
Range
Status
0 to 1
Mandatory
1 to 31
Mandatory
This eld refers to the MMS ID of the B side.

Start Timeslot B
The B side Timeslot at which the dened block is to start.

End Timeslot B
1 to 31
Mandatory
The B side Timeslot at which the dened block is to end.
68P02900W22-R
6-59
GMR-02
Mar 2008
Links table
Links table
Description of Links table

This table is used for two different tasks (refer to Table 6-15):
Non-RXCDR area
Contains details of the links between MMSs required by the paths. May also contain
details of the links between the RXCDR and its BSCs used by the XBL feature (add_conn
from 1620).
RXCDR area
Contains details of the links between the RXCDR and its BSCs used by the XBL feature
(add_conn from 1620, add_bss_conn from 1510 and add_xbl_conn for pre-1510).
In both cases, the MSIs and MMSs required are detailed in the Hardware table.
Default lename: link.mcd
Table 6-15 Links table

Field Name
Field Width
Range
Status
Link Type
TEXT
Mandatory
PATH - used for identifying links between MMSs required by the paths.
LINK - used for identifying add_conn commands within BSS or RXCDR congurations.
NOTE
Valid for 1620 onwards.
Link Number
0 to 999
Mandatory if
area is a BSC or
collocated, unused if
area is an RXCDR.
This eld is used as an internal ID to refer to this point-to-point link in the PATHS table. This
number is used as a unique identier for the LINK within the scope of the BSS.
Continued
6-60
68P02900W22-R
GMR-02
Mar 2008
Table 6-15 Links table (Continued)

Field Name
Field Width
Site Number A
Range
0 to 120, 251,
252, 253 and
254 (up to 1760)
0 to 100, 251, 252,
253 and 254 (from
1800)
Status
Mandatory
This eld is used as the A end site identier. Value must be 0 in the case of an RXCDR area.
TS_SWITCH/Marker Sites
From 1510, this eld may also indicate the TS_SWITCH (marker site) if the Aggregate Abis
option has been purchased.
254 is the value to insert if a TS_SWITCH is required.
NOTE
When the Link Type is LINK, Site Number A should always be 0 for the BSC. Site
Number B is the unique NE ID of the counterpart of the LINK (Transcoder).
MSI A
0 to 123,254
Mandatory
This eld is used as the A end MSI identier.

From 1510 if Site Number A is a TS_SWITCH (marker site), 254 must be entered as the MSI A
value.
MMS A
0 to 1,254
Mandatory
This eld is used as the A end MMS identier.

From 1510 if Site Number A is a TS_SWITCH (marker site), 254 must be entered as the MMS A
value.
Continued
68P02900W22-R
6-61
GMR-02
Mar 2008
Table 6-15 Links table (Continued)

Field Name
Field Width
Site Number B
Range
0 to 120, 251,
252, 253 and
254 (up to 1760)
0 to 100, 251, 252,
253 and 254 (from
1800)
Status
Mandatory
This eld is used as the B end site identier.

From 1510 this eld may also indicate the TS_SWITCH (marker site) if the Aggregate Abis
option is purchased.
254 is the value to insert if a TS_SWITCH is required.
MSI B
0 to 123,254
Mandatory
This eld is used as the B end MSI identier.

From 1510 if Site Number B is a TS_SWITCH (marker site), 254 must be entered as the MSI A
value.
MMS B
0 to 1,254 (for 1740

and 1800 Release)
0 to 5,254 (for 1760
Release)
Mandatory
This eld is used as the B end MMS identier.

From 1510 if Site Number B is a TS_SWITCH (marker site), 254 must be entered as the MMS A
value.
6-62
68P02900W22-R
GMR-02
Mar 2008
Paths table
Paths table
Description of Paths table

Table 6-16 contains details of all the paths or Dynets within the BSS area (providing signalling
and trafc communication between the BSC and the BTSs), using the links detailed in the links
table. Details of RSLs are also contained in this table.
Default lename: path.mcd
Table 6-16 Paths table

Field Name
Field Width
Range
Status
Terminating Site
Number
1 to 120
Mandatory
This eld is used as the SITE at which the PATH terminates.

For a DYNET device this site MUST be site 0 (BSC/BSS).
First ID
0 to 9 (PATH)
0 to 19 (DYNET)
Mandatory
Device Type:
PATH:
DYNET:
Second ID
This eld is used as the per SITE Unique PATH device ID.
This eld is used as the DYNET rst device ID.
1
0 to 2
Mandatory if DYNET
not applicable for
PATH.
This eld is used at the DYNET second device ID. If dened, then an equip DYNET is assumed
else if empty an equip PATH will be inserted.
RSL First ID
0 to 120
Optional, each Site

requires an RSL but
not each path to each
site.
This eld is used as the rst device ID for the RSL device.
RSL Second ID
0 to 7 (dependent on
type of equipment
- see below)
Mandatory if the rst

RSL ID is present,
refer RSL First ID.
This eld is used as the second device ID for the RSL device.
The range is as follows:
Continued
68P02900W22-R
6-63
GMR-02
Mar 2008
Description of Paths table
Table 6-16 Paths table (Continued)

Field Name
Field Width
Range
Field
Range
Non-M-Cell
0 to 7
M-Cell2/6 BTS
0 to 5
M-Cellmicro BTS
0 to 1
DYNET
Even numbers only (including 0).
LINKS 1 to 11
0 to 999
Status
Mandatory
PATH Device
This eld is used to identify the links in the chain (1 through 10) that composes the PATH.
Link 1 must terminate at site 0, and Link 10 must terminate at the value specied as the
Terminating Site Number. These links should be dened within the Links table.
It is an error to enter a link that does not terminate one end at the terminating site (refer
to rst eld above).
DYNET Device
This eld is used to identify the links in the chain (1 through 11) that composes the
DYNET. Link 11 may only terminate at the BSC (site 0). These links should be
dened within the Links table.
6-64
68P02900W22-R
GMR-02
Mar 2008
LAPD table
LAPD table
Description of LAPD table

Table 6-17 contains details of the LAPD values for the RSLs and XBLs in the area. The RSLs and
XBLs required are detailed in the circuits and paths tables.
Default lename: lapd.mcd
Table 6-17 LAPD table

Field Name
Field Width
Range
Status
Device Type
10
TEXT
Mandatory
First device ID
0 to 120
Mandatory
Type
Range
Usage
RSL
1-120
First Device ID
XBL
0-19
Device ID
Second device ID
Type
Range
Usage
RSL
0 to 7
First Device ID
XBL
1 to 254
Refer to the following Note
RSL, XBL
0 to 7
Mandatory (If Device Type

is RSL or XBL, for 1620
onwards).
NOTE
Identies at the BSC the device ID which corresponds to the RXCDR which
provides the TRAU resource for the CIC.
Identies at the RXCDR the device ID which corresponds to the BSS which is
managing the CIC. This eld is not valid for local transcoding BSCs.
XBL data rate
16 or 64
Mandatory if Device Type is

XBL AND 16Kbps LAPD XBL
option is purchased, otherwise
unused.
Used for the prompt Enter the data rate for the XBL of the equip XBL command.
Continued
68P02900W22-R
6-65
GMR-02
Mar 2008
Description of LAPD table
Table 6-17 LAPD table (Continued)

Field Name
Field Width
Range
Status
XBL timeslot group
0 to 3
Mandatory if Device Type is

XBL AND 16Kbps LAPD XBL
option is purchased AND XBL
data rate of 16 is chosen,
otherwise unused.
Used for the prompt Enter the group of the timeslot where this device appears of
the equip XBL command.
T200 timer value
See below.
Optional
Range
Minimum
Maximum
Step Size
Pre-1500
200
5000
50
1500 onwards
1400
5000
50
1 to 5
Optional
Optional
Used for the LAPD T200 timer value.

1
N200 value
Used for the LAPD N200 value.

K value
See below.
Range
Minimum
Maximum
Pre-1500
127
1500 onwards
10
Used for the LAPD K value.
6-66
68P02900W22-R
GMR-02
Mar 2008
Cell table
Cell table
Description of Cell table

Table 6-18 provides the details of all the cells across the OMC or network and also the external
neighbors used by the cells specied. The optional elds in this table contain information that
overrides the defaults, as specied in the Generics table on page 6-26.
Default lename: cell.mcd
Table 6-18
Cell table
Field Name
Field Width
Range
Status
BSS ID
0 to 255 or X
Mandatory
The bss_id of the BSS in which this cell is located.

X being a cell external to the BSS area, that is, a neighbor of a cell inside this BSS area.
Site Number
1 to 120 or X
(up to 1760)
1 to 100 or X
(from 1800)
Mandatory
The Site number, within the BSS, of the Site in which this cell is located.
X being a cell external to the BSS area, that is, a neighbor of a cell inside this BSS area.
{22239} MCC
3 digit numeric
Mandatory
3 digit numeric
Mandatory
The Mobile Country Code.

{22239} MNC
The Mobile Network Code.
The MNC can have optional third digit only for PCS1900 and GSM850 systems.
LAC
6 digit numeric
Mandatory
The Location Area Code.

Digits can be entered either in decimal or hex. Hex numbers are to be followed by h or
preceded by 0x, for example, 1234h or 0x1234.
CI
6 digit numeric
Mandatory
The Cell identier.

Digits can be entered either in decimal or hex form. Hex numbers are to be followed by h or
Continued
68P02900W22-R
6-67
GMR-02
Mar 2008
Table 6-18 Cell table (Continued)

Field Name
Field Width
Range
Status
Cell Name
31
31 character
string
Optional
0, 1, 2, 4, 6 or 8
(See below)
Mandatory
The cell name.

Frequency Type
External Neighbors:
Used for the Enter neighbor cell frequency type parameter of the add_neighbor command.
Internal Cells:
Used for the frequency_type parameter of the add_cell command.
The valid frequency types are:
Frequency Type
Numeric Entry
PGSM
EGSM
DCS1800
PGSM and DCS1800
EGSM and DCS1800
PCS1900
bsic
0 to 63 (hex)
Mandatory
Used for the bsic parameter of the add_neighbor command, when this cell is identied as a
neighbor to another cell.
1
egsm_bcch_sd
0 or 1
Optional
This parameter allows the BCCH ARFN to be within the GSM Extension band.
BCCH ARFN
Refer Frequency
Type Channel
Groupings below:
Mandatory
Used for the bcch_freq_num parameter of the add_neighbor command, when this
cell is identied as a neighbor to another cell.
It is veried by the RTF table while assigning the absolute radio
frequency channel to the RTF.
Frequency Type Channel Groupings:
Frequency
BCCH
PGSM
1 to 124
EGSM
1 to 124 (975 to 1023, 0 if egsm_bcch_sd is enabled)
DCS1800
512 to 885
PCS1900
512 to 810
ho_margin_cell
-63 to 63
Optional
This value is for display purposes. The value is extracted from any add_neighbor commands.
Continued
6-68
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
rxlev_min_cell
0 to 63
Optional
This value is purely for display purposes. The value is extracted from any add_neighbor
commands.
2
ms_txpwr_max_def
0 to 39
Optional
For GSM 900

and GSM 900
Extended 5 to 39, odd
values only.
For DCS 1800
and PCS1900 - 0
to 30, even values
only.
This value may also be extracted for use with the Neighbor table on page 6-168.
Used for element ms_txpwr_max_def:
rxlev_access_min
0 to 63
Optional
If a value is not entered here, a generic value is used (refer to the Generics table on page 6-26).
Used for element rxlev_access_min:
ccch_conf
0, 1, 2, 4, 6
Optional, only
used if not an
external cell.
0: 1 Timeslot using Timeslot 0
1: Combined ccch and sdcch on Timeslot 0
2: 2 Timeslots using Timeslots 0 and 2
4: 3 Timeslots using Timeslots 0, 2 and 4
6: 4 Timeslots using Timeslots 0, 2, 4 and 6
Used for element ccch_conf:
bs_ag_blks_res
See below for

range.
Optional, only
used if not an
external cell.
Range:
if ccch_conf = 1: range 0 to 2
if ccch_conf not 1: range 0 to 7.
If a value is not entered here, a generic value is used (refer to the
Generics table on page 6-26).
Used for element bs_ag_blks_res
Continued
68P02900W22-R
6-69
GMR-02
Mar 2008

Field Name
Field Width
number_sdcchs_
preferred
Range
See below for
range.
Status
Optional, only
used if not an
external cell.
Range:
{26987}
In 1760 and 1800, when the Increased SDCCH feature is unrestricted:
if ccch_conf = 1, the range is: 4, 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100, 108, 116, 124
if ccch_conf is not 1, the range is: 8 ,16, 24, 32, 40, 48, 56, 64, 72, 80,
88, 96, 104, 112, 120, 128
In 1760 and 1800, when the Increased SDCCH feature is restricted:
if ccch_conf = 1, the range is: 4, 12, 20, 28, 36, 44
if ccch_conf is not 1, the range is: 8, 16, 24, 32, 40, 48
number_sdcchs_preferred must be <= max_number_of_sdcchs.
Used for element number_sdcchs_preferred:
3
max_number_of_
sdcchs
16 to 48
12 to 48
(From 1600)
12 to 128 (From
1800)
Optional, only
used if not an
external cell.
In 1760 and 1800, when the Increased SDCCH feature is unrestricted:

if ccch_conf = 1, the range is: 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100, 108, 116, 124
if ccch_conf is not 1, the range is: 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128
{26987}
In 1760 and 1800, when the Increased SDCCH feature is restricted:
if ccch_conf = 1, the range is: 12, 20, 28, 36, 44
if ccch_conf is not 1, the range is: 16, 24, 32, 40, 48
The value should be greater than that of number_sdcchs_preferred.
If ext_range_cell is set, then the range is 16 to 20.
The max_number_of_sdcchs default in 1760 and 1800 is as follows:
If ccch_conf = 1 and Increased SDCCH feature is unrestricted:
60
If ccch_conf is not 1 and Increased SDCCH feature is unrestricted:
64
If ccch_conf = 1 and SDCCH is restricted:
44
If ccch_conf is not 1 and SDCCH is restricted:
48
Used for element max_number_of_sdcchs:

Continued
6-70
68P02900W22-R
GMR-02
Mar 2008

Field Name
sdcch_need_high_
water_mark
Field Width
3
Range
1 to 38
From 1800 see
allowed ranges
below:
Status
Optional, only
used if not an
external cell.
Allowed ranges from 1800:

1 to 119 when the Increased SDCCH feature is unrestricted but 1 to 115 if ccch_conf = 1.
1 to 39 when the Increase SDCCH feature is restricted.
sdcch_need_high_water_mark must be greater than or equal to 9
sdcch_need_low_water_mark. It is used for element sdcch_need_high_water_mark:
sdcch_need_low_
water_mark
11 to 48
From 1800 see
allowed ranges
below.
Optional, only
used if not an
external cell.
Allowed ranges from 1800:

10 to 128 when the Increased SDCCH feature is unrestricted.
10 to 48 when the Increase SDCCH feature is restricted.
sdcch_need_low_water_mark must be less than or equal to max_number_of_sdcchs.
Used for element sdcch_need_low_water_mark:
max_tx_ms
5 to 39 - PGSM
and EGSM (Odd
values only).
0 to 36 DCS1800 (Even
values only).
0 to 32, 33 PCS1900 (Even
values only and
value 33).
Optional, only
used if not an
external cell.
Used for element max_tx_ms:
ms_txpwr_max_cch
5 to 39 - PGSM
and EGSM (Odd
values only).
0 to 36 DCS1800 (Even
values only).
0 to 32, 33 PCS1900 (Even
values only and
value 33).
Optional, only
used if not an
external cell.
Used for element ms_txpwr_max_cch:
Continued
68P02900W22-R
6-71
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
ms_max_range
0 to 630 to 219 (if

ext_range_cell
is enabled*).
Optional, only
used if not an
external cell.
Used for element ms_max_range:
ho_margin_def
-63 to 63
Optional, only
used if not an
external cell.
Used for element ho_margin_def:
rxlev_min_def
0 to 63
Optional
Used for element rxlev_min_def:
handover_power_level
0 to 15
Optional, only
used if not an
external cell.
Used for element handover_power_level:
cell_reselect_hysteresis
0 to 7
Optional, only
used if not an
external cell.
Used for element cell_reselect_hysteresis:
max_tx_bts
0 to 21 (for
PCS1900 cells).
-1 to 21 (for
PGSM/EGSM and
DCS1800 cells).
Optional, only
used if not an
external cell.
Used for element max_tx_bts:
bcch_power_level
0 to 21
Optional, only
used if not an
external cell.
Used for element bcch_power_level:
Continued
6-72
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
inner_zone_alg
Range
0 to 3 (3 is
only valid when
the Dual Band
Cell Opt is
purchased).
Status
Optional
NOTE
Multi band must be enabled for inner_zone_alg to be modied. This attribute is
not valid at Horizonofce sites.
Five parameters are associated with inner_zone_alg as follows:
ms_txpwr_max_inner
zone_ho_hyst
rxlev_dl_zone
rxlev_ul_zone
These parameters may be set using the Generics table on page 6-26 or the Specics table
on page 6-109.
Used for chg_cell_element inner_zone_alg:
ext_range_cell
0 to 2
Optional
One parameter is associated with ext_range_cell as follows:

ms_max_range (if ext_range is set then ms_max_range may be set between 0 and 219).
This parameter may be set using the Cell table eld ms_max_range.
Used for chg_cell_element ext_range_cell:
hop_qual_enabled
0 to 1
Optional, only
applicable to
1601 loads or
later.
Four parameters are associated with hop_qual_enabled as follows:
on page 6-109.
Continued
68P02900W22-R
6-73
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
0 to 1
Optional, only
applicable to
1601 loads or
later.
Used for chg_cell_element hop_qual_enabled:

1
data_qual_enabled
Four parameters are associated with data_qual_enabled as follows:
l_rxqual_dl_h_data
l_rxqual_dl_p_data
l_rxqual_ul_h_data
l_rxqual_ul_p_data
on page 6-109.
Used for chg_cell_element data_qual_enabled:
1
gprs_enabled
0 to 1
Optional, only
applicable to
1610 loads or
later.
Two parameters are associated with gprs_enabled as follows:
rac
ra_colour
on page 6-109.
Used for chg_cell_element gprs_enabled:
network_control_order
0 to 4
Optional
ts_in_usf_active
0 to 3
Optional
inter_rat_enabled
0 to 3
Optional, only
applicable to
1650 loads
and later.
The default value is 0.

Continued
6-74
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
qsearch_i
0 to 15
Optional, only
applicable to
1650 loads
and later.
0 to 1
Optional, only
applicable to
1650 loads
and later.
0 to 15
Optional, only
applicable to
1650 loads
and later.
0 to 7
Optional, only
applicable to
1650 loads
and later.

qsearch_c_initial

fdd_qoffset

fdd_qmin
The default value is 7. For pre-1800 releases, the default value is 0.

gprs_cell_cgt_thr
1 to 4
Optional
1 to 10
Optional
5 to 40
Optional
0 to 15
Optional

gprs_num_pmrs
gprs_cr_margin
persistence
_level,0
Species the values of the access persistence level P(i) for each radio priority i (i = 1..4),
where radio priority 1 represents the highest radio priority. The default value is 4.
persistence_level,1
0 to 15
Optional
persistence_level,2
0 to 15
Optional
Continued
68P02900W22-R
6-75
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
persistence_level,3
0 to 15
Optional
prach_max_
retran,0
0 to 3
Optional
Maximum number of retransmissions allowed for each radio priority level on a per cell basis.
prach_max_
retran,1
0 to 3
Optional
prach_max_
retran,2
0 to 3
Optional
prach_max_
retran,3
0 to 3
Optional
vgcs_options_
enable
0, 1, or 3.
0 - Indicates
that VGCS and
the Uplink reply
mechanism
options are
disabled.
1 - Indicates
that the VGCS
option is enabled.
3 - Indicates that
VGCS and the
Uplink reply
mechanism are
enabled.
Optional
0 to 27
Optional

nch_position
Continued
6-76
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
{23311} GPRS ERC enabled

(_cell_data,1)
0 to 1
Optional
{23311} GPRS ERC RTF

First ID
0 to 23
Optional
{23311} GPRS ERC RTF

Second ID
0 to 11
Optional
{23311} ext_pdchs
(_cell_data,2)
0 to 4
Optional
NOTE
To avoid the need for two ms_max_range elements (add_cell and

chg_cell_element), the ms_max_range parameter for ext_range_cell may be
set in the ms_max_range eld within the Cell table.
A default value of 63 is inserted into the ms_max_range parameter of the

add_cell command as the chg_cell_element value overrides this. If this were
not so, the add_cell command would fail to compile with the new range.
68P02900W22-R
6-77
GMR-02
Mar 2008
Statistics table
Statistics table
Description of Statistics table

Table 6-19, the Statistics table, contains a list of statistical elements. Either the value from
the value eld (if present) or the Motorola recommended value is set bss-wide but may be
overridden for a site or cell by values in the Specics table.
Default lename: stat.mcd
Table 6-19 Statistics table

Field Name
Element Name
Field Width
50
Range
Text:
<element name>
[,<index>]
Status
Mandatory
Name of the statistics element, optionally followed by an index.

Recommended
Value
11
-2, 147, 483, 648

to
+2, 147, 483, 647
Mandatory
(Element dependent)
Default value of the statistics element.
Value
11
-2, 147, 483, 648

to
+2, 147, 483, 647
Optional
(Element dependent)
Specic value of the statistics element.
6-78
68P02900W22-R
GMR-02
Mar 2008
Layout of elements in the MCDF Statistics table
The elements in the Statistics table are displayed in Table 6-20 as follows:
Table 6-20
Statistics table - elements

Element name
Recommended value
access_per_agch,0
access_per_pch_cs,0
access_per_pch_cs_ps,0
access_per_pch_ps,0
access_per_ppch,0
access_per_rach,0
air_dl_control_blks,0
air_ul_control_blks,0
air_dl_tbf_failures,0
10
air_ul_tbf_failures,0
11
alloc_sdcch,0
12
alloc_sdcch_fail,0
13
alloc_sdcch_fail,2
2147483647
14
alloc_sdcch_carr,0
15
alloc_tch,0
16
alloc_tch_inner_zone,0
17
alloc_tch_fail_hr,0
18
alloc_tch_fail_inner_zone,0
19
2147483647
20
alloc_tch_hr,0
21
alloc_tch_fail,0
22
alloc_tch_fail,2
2147483647
23
alloc_tch_fail_hr_amr,0
24
alloc_tch_carr,0
25
alloc_tch_hr_amr,0
26
amr_fr_ul_codec_mode_usage,0
27
amr_fr_dl_codec_mode_usage,0
28
amr_hr_ul_codec_mode_usage,0
29
amr_hr_dl_codec_mode_usage,0
0
Continued
68P02900W22-R
6-79
GMR-02
Mar 2008
Table 6-20 Statistics table - elements (Continued)

#
Element name
Recommended value
30
amr_fr_ul_adaptation,0
31
amr_fr_dl_adaptation,0
32
amr_hr_ul_adaptation,0
33
amr_hr_dl_adaptation,0
34
amr_increase_thresh_adjust,0
35
amr_decrease_thresh_adjust,0
36
assignment_redirection,0
37
ater_channel_status,0
38
ater_emerg_preempt_status,0
39
{24347}ater_preempt_rqd,0
40
{24347}ater_preempt_atmpt,0
41
{24347}ater_preempt_atmpt_swover,0
42
{24347}ater_preempt_fail,0
43
2147483647
44
{24347}ater_preempt_fail_swover,0
45
available_sdcch,0
46
available_tch,0
47
available_tch,4,0
48
available_tch,4,1
49
available_tch,4,2
50
available_tch,4,3
51
available_tch,4,4
52
available_tch,4,5
53
available_tch,4,6
11
54
available_tch,4,7
13
55
available_tch,4,8
15
56
available_tch,4,9
17
57
available_tch,5,0
58
available_tch,5,1
59
available_tch,5,2
60
available_tch,5,3
61
available_tch,5,4
62
available_tch,5,5
10
63
available_tch,5,6
12
Continued
6-80
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
64
available_tch,5,7
14
65
available_tch,5,8
16
66
available_tch,5,9
400
67
available_tch_hr,0
68
available_tch_hr_amr,0
69
{22404}available_tch_dcs1800,0
70
{22404}available_tch_egsm,0
71
{22404}available_tch_pgsm,0
72
{28486}avg_simul_dl_tbfs,0
73
{28486}avg_simul_ul_tbfs,0
74
bad_ho_refnum_ms,0
75
bad_ho_refnum_ms,2
2147483647
76
ber,0
77
{28486}blocked_dl_tbfs,0
78
bss_availability
79
{22586}bss_ovld_msgs_tx,0
80
bsslap_abort_rcv,0
81
bsslap_abort_sent,0
82
bsslap_ms_pos_cmd,0
83
bsslap_ms_pos_resp,0
84
bsslap_rej,0
85
bsslap_reset,0
86
bsslap_ta_req,0
87
bsslap_ta_resp,0
88
bsslap_toa_req,0
89
bssmap_conless_info_rcv,0
90
bssmap_conless_info_sent,0
91
bssmap_perf_loc_abort_msgs,0
92
bssmap_perf_loc_req_msgs,0
93
bssmap_perf_loc_resp_msgs,0
94
bssmaple_conless_info_rcv,0
95
bssmaple_conless_info_sent,0
96
bssmaple_perf_loc_abort_msgs,0
97
bssmaple_perf_loc_req_msgs,0
0
Continued
68P02900W22-R
6-81
GMR-02
Mar 2008

Element name
Recommended value
98
bssmaple_perf_loc_resp_msgs,0
99
busy_cics,0
100
busy_cics,4,0
101
busy_cics,4,1
10
102
busy_cics,4,2
50
103
busy_cics,4,3
100
104
busy_cics,4,4
200
105
busy_cics,4,5
400
106
busy_cics,4,6
800
107
busy_cics,4,7
1200
108
busy_cics,4,8
1600
109
busy_cics,4,9
2200
110
busy_cics,5,0
111
busy_cics,5,1
49
112
busy_cics,5,2
99
113
busy_cics,5,3
199
114
busy_cics,5,4
399
115
busy_cics,5,5
799
116
busy_cics,5,6
1199
117
busy_cics,5,7
1599
118
busy_cics,5,8
2199
119
busy_cics,5,9
3200
120
busy_sdcch,0
121
busy_sdcch,4,0
122
busy_sdcch,4,1
123
busy_sdcch,4,2
124
busy_sdcch,4,3
125
busy_sdcch,4,4
126
busy_sdcch,4,5
127
busy_sdcch,4,6
11
128
busy_sdcch,4,7
13
129
busy_sdcch,4,8
15
130
busy_sdcch,4,9
17
131
busy_sdcch,5,0
0
Continued
6-82
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
132
busy_sdcch,5,1
133
busy_sdcch,5,2
134
busy_sdcch,5,3
135
busy_sdcch,5,4
136
busy_sdcch,5,5
10
137
busy_sdcch,5,6
12
138
busy_sdcch,5,7
14
139
busy_sdcch,5,8
16
140
busy_sdcch,5,9
400
141
busy_tch,0
142
busy_tch,4,0
143
busy_tch,4,1
144
busy_tch,4,2
145
busy_tch,4,3
146
busy_tch,4,4
147
busy_tch,4,5
148
busy_tch,4,6
11
149
busy_tch,4,7
13
150
busy_tch,4,8
15
151
busy_tch,4,9
17
152
busy_tch,5,0
153
busy_tch,5,1
154
busy_tch,5,2
155
busy_tch,5,3
156
busy_tch,5,4
157
busy_tch,5,5
10
158
busy_tch,5,6
12
159
busy_tch,5,7
14
160
busy_tch,5,8
16
161
busy_tch,5,9
400
162
busy_tch_carr,0
163
busy_tch_carr_hr,0
164
busy_tch_hr,0
165
busy_tch_hr,4,0
0
Continued
68P02900W22-R
6-83
GMR-02
Mar 2008

#
Element name
Recommended value
166
busy_tch_hr,4,1
167
busy_tch_hr,4,2
168
busy_tch_hr,4,3
169
busy_tch_hr,4,4
170
busy_tch_hr,4,5
171
busy_tch_hr,4,6
11
172
busy_tch_hr,4,7
13
173
busy_tch_hr,4,8
15
174
busy_tch_hr,4,9
17
175
busy_tch_hr,5,0
176
busy_tch_hr,5,1
177
busy_tch_hr,5,2
178
busy_tch_hr,5,3
179
busy_tch_hr,5,4
180
busy_tch_hr,5,5
10
181
busy_tch_hr,5,6
12
182
busy_tch_hr,5,7
14
183
busy_tch_hr,5,8
16
184
busy_tch_hr,5,9
400
185
busy_tch_hr_amr,0
186
busy_tch_hr_amr,4,0
187
busy_tch_hr_amr,4,1
188
busy_tch_hr_amr,4,2
189
busy_tch_hr_amr,4,3
190
busy_tch_hr_amr,4,4
191
busy_tch_hr_amr,4,5
192
busy_tch_hr_amr,4,6
11
193
busy_tch_hr_amr,4,7
13
194
busy_tch_hr_amr,4,8
15
195
busy_tch_hr_amr,4,9
17
196
busy_tch_hr_amr,5,0
197
busy_tch_hr_amr,5,1
198
busy_tch_hr_amr,5,2
199
busy_tch_hr_amr,5,3
6
Continued
6-84
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
200
busy_tch_hr_amr,5,4
201
busy_tch_hr_amr,5,5
10
202
busy_tch_hr_amr,5,6
12
203
busy_tch_hr_amr,5,7
14
204
busy_tch_hr_amr,5,8
16
205
busy_tch_hr_amr,5,9
400
206
busy_tch_carr_hr_amr,0
207
{22404}busy_tch_dcs1800,0
208
{22404}busy_tch_egsm,0
209
{22404}busy_tch_pgsm,0
210
call_sp_vers_downgrade_monitor,0
211
calls_queued,0
212
calls_queued,2
2147483647
213
calls_queued,2,0
65534
214
cell_ush_reqs,0
215
ch_req_unsvcd_pcu,0
216
chan_dl_tx_pwr_lvl,0
217
chan_dl_tx_pwr_lvl,4,0
218
219
220
14
221
18
222
23
223
27
224
32
225
36
226
41
227
228
229
13
230
17
231
22
232
26
233
31
Continued
68P02900W22-R
6-85
GMR-02
Mar 2008

#
Element name
Recommended value
234
35
235
40
236
44
237
chan_req_cause_atmpt,0
238
chan_ul_tx_pwr_lvl,0
239
chan_ul_tx_pwr_lvl,4,0
240
241
242
14
243
18
244
23
245
27
246
32
247
36
248
41
249
250
251
13
252
17
253
22
254
26
255
31
256
35
257
40
258
44
259
chan_req_ms_blk,0
260
chan_req_ms_blk,2
2147483647
261
chan_req_ms_fail,0
262
chan_req_ms_fail,2
2147483647
263
chan_req_ms_fail,2,0
65534
264
65534
265
65534
266
channel_reqs_rec,0
267
channel_reqs_reject,0
0
Continued
6-86
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
268
channel_reqs_success,0
269
cipher_mode_fail,0
270
cipher_mode_fail,2
2147483647
271
classmk_update_fail,0
272
2147483647
273
clr_cmd_from_msc,0
274
clr_req_to_msc,0
275
coding_scheme_change,0
276
congest_exist_ho_atmpt,0
277
congest_stand_ho_atmpt,0
278
congestion_lost_msu,0
279
2147483647
280
cong_rel_dl_scts,0
281
conn_refused,0
282
conn_req_to_msc,0
283
cpu_usage,0
284
cpu_usage,4,0
285
cpu_usage,4,1
11
286
cpu_usage,4,2
21
287
cpu_usage,4,3
31
288
cpu_usage,4,4
41
289
cpu_usage,4,5
51
290
cpu_usage,4,6
61
291
cpu_usage,4,7
71
292
cpu_usage,4,8
81
293
cpu_usage,4,9
91
294
cpu_usage,5,0
10
295
cpu_usage,5,1
20
296
cpu_usage,5,2
30
297
cpu_usage,5,3
40
298
cpu_usage,5,4
50
299
cpu_usage,5,5
60
300
cpu_usage,5,6
70
301
cpu_usage,5,7
80
Continued
68P02900W22-R
6-87
GMR-02
Mar 2008

Element name
Recommended value
302
cpu_usage,5,8
90
303
cpu_usage,5,9
100
304.
cs12_on_32k_chan,0
305
{22577}cs1234_on_64k_chan,0
306
{22577}cs_page_reqs,0
307
{22577}dl_bler_cs1,0
308
309
310
311
{22577}dl_bler_mcs1,0
312
313
314
315
316
317
318
319
320
dl_busy_pdtch,0
321
dl_busy_pdtch,4,0
322
dl_busy_pdtch,4,1
323
dl_busy_pdtch,4,2
324
dl_busy_pdtch,4,3
325
dl_busy_pdtch,4,4
326
dl_busy_pdtch,4,5
327
dl_busy_pdtch,4,6
11
328
dl_busy_pdtch,4,7
13
329
dl_busy_pdtch,4,8
15
330
dl_busy_pdtch,4,9
17
331
dl_busy_pdtch,5,0
332
dl_busy_pdtch,5,1
333
dl_busy_pdtch,5,2
334
dl_busy_pdtch,5,3
335
dl_busy_pdtch,5,4
8
Continued
6-88
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
336
dl_busy_pdtch,5,5
10
337
dl_busy_pdtch,5,6
12
338
dl_busy_pdtch,5,7
14
339
dl_busy_pdtch,5,8
16
340
dl_busy_pdtch,5,9
400
341
{23769}dl_egprs_backhaul_demand,0
342
{23769}dl_egprs_backhaul_used,0
343
{22577}dl_llc_frames_gb,0
344
{22577}dl_llc_frames_pcu,0
345
{23956}dl_llc_data_volume,0
346
{22577}dl_pdtch_congestion,0
347
dl_pdtch_q_length,0
348
dl_pdtch_seizure,0
349
dl_radio_blks_1_ts,0
350
351
352
353
dl_rlc_ack_new_blks,0
354
dl_rlc_ddtr_blks,0
355
dl_rlc_nack_blks,0
356
dl_rlc_retx_blks,0
357
dl_rlc_stalled_blks,0
358
dl_rlc_unack_new_blks,0
359
dl_tbf_time_1_ts,0
360
dl_tbf_time_2_ts,0
361
dl_tbf_time_3_ts,0
362
dl_tbf_time_4_ts,0
363
dynet_assign_fail,0
364
dynet_call_rejects,0
365
{23769}egprs_64k_channel_width,0
366
egprs_64k_channels_switched,0
367
egprs_64k_not_avail,0
368
egprs_avail_pdtch,0
369
egprs_dl_asgn_pccch,0
0
Continued
68P02900W22-R
6-89
GMR-02
Mar 2008

Element name
Recommended value
370
er_intra_cell_ho_atmpt,0
371
er_intra_cell_ho_suc,0
372
fer,0
373
fer_non_amr,0
374
fer_amr_fr,0
375
fer_amr_hr,0
376
fer_gsm_fr_efr,0
377
fer_gsm_hr,0
378
ow_control_barred,0
379
frmr,0
380
frmr,2
2147483647
381
g_rach_unsvcd_bts,0
382
gbl_link_ins,0
383
gbl_dl_data_thrput,0
384
gbl_ow_ctrl_sent,0
385
gbl_paging_reqs,0
386
gbl_dl_data_thrput_hist,0
387
gbl_dl_data_thrput_hist,4,0
388
31
389
71
390
111
391
141
392
171
393
231
394
301
395
401
396
501
397
30
398
70
399
110
400
140
401
170
402
230
403
300
Continued
6-90
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
404
400
405
500
406
600
407
gbl_ul_data_thrput_hist,0
408
gbl_ul_data_thrput_hist,4,0
409
31
410
71
411
111
412
141
413
171
414
231
415
301
416
401
417
501
418
30
419
70
420
110
421
140
422
170
423
230
424
300
425
400
426
500
427
600
428
gbl_ul_data_thrput,0
429
gbl_unavailable,0
430
{22100}gci_for_16kpd_demand,0
431
432
433
gprs_access_per_agch,0
434
gprs_access_per_rach,0
435
gprs_avail_pdtch,0
436
{22577}gprs_cell_congestion,0
437
gprs_cell_reselect_attmpt,0

Continued
68P02900W22-R
6-91
GMR-02
Mar 2008

#
Element name
Recommended value
438
gprs_cell_reselect_fail,0
439
gprs_channels_switched,0
440
gprs_32k_channels_switched,0
441
gprs_32k_dl_not_avail,0
442
gprs_32k_ul_not_avail,0
443
gprs_dl_asgn_pccch,0
444
gprs_dynet_failures,0
445
gprs_dynet_res_reqs,0
446
gprs_dynet_res_reqs,4,0
447
448
11
449
16
450
21
451
26
452
31
453
36
454
41
455
46
456
457
10
458
15
459
20
460
25
461
30
462
35
463
40
464
45
465
50
466
gprs_dynet_swi_reqs,0
467
gprs_dynet_swi_reqs,4,0
468
469
11
470
16
471
21
Continued
6-92
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
472
26
473
31
474
36
475
41
476
46
477
478
10
479
15
480
20
481
25
482
30
483
35
484
40
485
45
486
50
487
gprs_ms_neighbor_strong
488
gprs_pch_agch_q_length,0
489
gprs_ppch_pagch_q_length,0
490
gprs_prr_blk_usg,0
491
gprs_prr_blk_usg,4,0
492
493
494
11
495
21
496
41
497
61
498
81
499
101
500
126
501
502
503
10
504
20
505
40
Continued
68P02900W22-R
6-93
GMR-02
Mar 2008

Element name
Recommended value
506
60
507
80
508
100
509
125
510
160
511
gprs_rach_arrival,0
512
gprs_rach_arrival,4,0
513
514
515
11
516
21
517
41
518
61
519
81
520
101
521
126
522
523
524
10
525
20
526
40
527
60
528
80
529
100
530
125
531
160
532
ho_fail_no_resources,0
533
ho_req_ack_to_msc,0
534
ho_req_from_msc,0
535
ho_req_msc_fail,0
536
ho_req_msc_fail,2
2147483647
537
ho_req_msc_proto,0
538
ho_req_msc_proto,2
2147483647
539
i_frames_rx,0
0
Continued
6-94
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
540
i_frames_tx,0
541
idle_pdtch_intf_band0,0
542
543
544
545
546
idle_tch_intf_band0,0
547
548
549
550
551
imm_assgn_cause,0
552
in_inter_bss_ho,0
553
in_intra_bss_ho,0
554
in_intra_bss_nc_atmpt,0
555
in_intra_bss_nc_suc,0
556
interband_activity,0
557
intf_on_idle,0
558
intf_on_idle,4,0
559
intf_on_idle,4,1
560
intf_on_idle,4,2
11
561
intf_on_idle,4,3
16
562
intf_on_idle,4,4
21
563
intf_on_idle,4,5
26
564
intf_on_idle,4,6
31
565
intf_on_idle,4,7
36
566
intf_on_idle,4,8
41
567
intf_on_idle,4,9
46
568
intf_on_idle,5,0
569
intf_on_idle,5,1
10
570
intf_on_idle,5,2
15
571
intf_on_idle,5,3
20
572
intf_on_idle,5,4
25
573
intf_on_idle,5,5
30
Continued
68P02900W22-R
6-95
GMR-02
Mar 2008

Element name
Recommended value
574
intf_on_idle,5,6
35
575
intf_on_idle,5,7
40
576
intf_on_idle,5,8
45
577
intf_on_idle,5,9
65
578
intra_bss_ho_cause_suc,0
579
intra_cell_ho,0
580
inv_est_cause_on_rach,0
581
invalid_frames_rx,0
582
invalid_frames_rx,2
2147483647
583
l_routing_syntax,0
584
l_routing_syntax,2
2147483647
585
l_routing_unknown,0
586
l_routing_unknown,2
2147483647
587
l_sccp_msgs,0
588
l_sccp_msgs_rx,0
589
l_sccp_msgs_tx,0
590
l_sif_sio_rx_opc,0
591
l_sif_sio_tx_dpc,0
592
l_sif_sio_type,0
593
l_sl_stop_congestion,0
594
lapd_congestion,0
595
lmtp_changeback,0
596
lmtp_changeover,0
597
lmtp_congestion,0
598
lmtp_congestion_lost_msu,0
599
lmtp_congestion_lost_msu,2
2147483647
600
lmtp_link_ins,0
601
lmtp_linkfail,0
602
lmtp_local_busy,0
603
lmtp_local_mgt,0
604
lmtp_local_sl_congestion,0
605
lmtp_local_sl_congestion,2
2147483647
606
lmtp_mgt_inhibit,0
607
lmtp_mgt_uninhibit,0
Continued
6-96
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
608
lmtp_msu_discarded,0
609
lmtp_msu_discarded,2
2147483647
610
lmtp_msu_rx,0
611
lmtp_msu_tx,0
612
lmtp_neg_acks,0
613
lmtp_neg_acks,2
2147483647
614
lmtp_re_tx,0
615
lmtp_re_tx,2
2147483647
616
lmtp_remote_mgt,0
617
lmtp_remote_proc,0
618
lmtp_remote_sl_congestion,0
619
lmtp_remote_sl_congestion,2
2147483647
620
lmtp_restoration,0
621
lmtp_sib_rx,0
622
lmtp_sib_tx,0
623
lmtp_sif_sio_rx,0
624
lmtp_sif_sio_tx,0
625
lmtp_sl_ack,0
626
lmtp_sl_ack,2
2147483647
627
lmtp_sl_alignment,0
628
lmtp_sl_alignment,2
2147483647
629
lmtp_sl_error_rate,0
630
lmtp_sl_error_rate,2
2147483647
631
lmtp_sl_fail,0
632
lmtp_sl_fail,2
2147483647
633
lmtp_sl_br,0
634
lmtp_sl_br,2
2147483647
635
lmtp_start_rpo,0
636
lmtp_start_rpo,2
2147483647
637
lmtp_stop_rpo,0
638
lmtp_su_error,0
639
lmtp_su_error,2
2147483647
640
lmtp_unavailable,0
641
ma_cmd_to_ms,0
0
Continued
68P02900W22-R
6-97
GMR-02
Mar 2008

Element name
Recommended value
642
ma_cmd_to_ms_blkd,0
643
ma_cmd_to_ms_blkd,2
2147483647
644
ma_complete_from_ms,0
645
ma_complete_to_msc,0
646
ma_fail_from_ms,0
647
ma_fail_from_ms,2
2147483647
648
ma_req_from_msc,0
649
ma_req_from_msc_fail,0
650
2147483647
651
ma_req_sdcch_pg_rsp,0
652
ms_access_by_type,0
653
ms_tch_usage_by_type,0
654
msc_ovld_msgs_rx,0
655
{22586}msgs_discard_on_gproc,0
656
{22586}msgs_discard_on_rsl,0
657
msu_discarded,0
658
msu_discarded,2
2147483647
659
mt_lcs_on_sdcch,0
660
mtp_changeback,0
661
mtp_changeover,0
662
mtp_congestion,0
663
mtp_link_ins,0
664
mtp_linkfail,0
665
mtp_local_busy,0
666
mtp_local_mgt,0
667
mtp_mgt_inhibit,0
668
mtp_mgt_uninhibit,0
669
mtp_msu_rx,0
670
mtp_msu_tx,0
671
mtp_neg_acks,0
672
mtp_neg_acks,2
2147483647
673
mtp_re_tx,0
674
mtp_re_tx,2
2147483647
675
mtp_remote_mgt,0
0
Continued
6-98
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
676
mtp_remote_proc,0
677
mtp_restoration,0
678
mtp_sif_sio_rx,0
679
mtp_sif_sio_tx,0
680
mtp_sl_ack,0
681
mtp_sl_ack,2
2147483647
682
mtp_sl_alignment,0
683
mtp_sl_alignment,2
2147483647
684
mtp_sl_congestion,0
685
mtp_sl_congestion,2
2147483647
686
mtp_sl_error_rate,0
687
mtp_sl_error_rate,2
2147483647
688
mtp_sl_fail,0
689
mtp_sl_fail,2
2147483647
690
mtp_sl_br,0
691
mtp_sl_br,2
2147483647
692
mtp_start_rpo,0
693
mtp_start_rpo,2
2147483647
694
mtp_stop_rpo,0
695
mtp_su_error,0
696
mtp_su_error,2
2147483647
697
mtp_unavailable,0
698
n2_expiry,0
699
n2_expiry,2
2147483647
700
no_pdtch_avail,0
701
no_pdtch_avail_time,0
702
{22708}num_cell_resel_cell,0
703
{22708}num_cell_resel_cell_pccn,0
704
{22708}num_cell_resel_cell_succ,0
705
num_emerg_access,0
706
num_emerg_rejected,0
707
num_emerg_tch_kill,0
708
num_emerg_term_sdcch,0
709
{22879}num_ho_to_3g_attempts,0
0
Continued
68P02900W22-R
6-99
GMR-02
Mar 2008

Element name
Recommended value
710
{22100}num_ho_from_3g_attempts,0
711
{22100}num_ho_from_3g_success,0
712
{22100}num_ho_to_3g_res_alloc_succ,0
713
{22100}num_ho_to_3g_success,0
714
{22100}num_multirat_ms_orig_call,0
715
{27717}num_susp_resu_rcvd
716
{22100}num_t3121_expiry,0
717
ok_acc_proc,0
718
ok_acc_proc_suc_rach,0
719
out_ho_cause_atmpt,0
720
out_inter_bss_ho,0
721
out_inter_bss_ho,2
65534
722
out_intra_bss_ho,0
723
out_intra_bss_nc_atmpt,0
724
out_intra_bss_nc_suc,0
725
{22577}pacch_page_reqs,0
726
{24303}packet_sysinfo_req,0
727
{24303}packet_sysinfo_resp,0
728
page_req_from_msc,0
729
page_req_from_msc_fail,0
730
2147483647
731
page_req_from_smlc_fail,0
732
page_req_from_smlc_fail,2
2147483647
733
paging_requests_cs,0
734
paging_requests_ps,0
735
path_balance,0
736
path_balance,4,0
737
path_balance,4,1
30
738
path_balance,4,2
50
739
path_balance,4,3
70
740
path_balance,4,4
90
741
path_balance,4,5
110
742
path_balance,4,6
130
Continued
6-100
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
743
path_balance,4,7
150
744
path_balance,4,8
170
745
path_balance,4,9
190
746
path_balance,5,0
29
747
path_balance,5,1
49
748
path_balance,5,2
69
749
path_balance,5,3
89
750
path_balance,5,4
109
751
path_balance,5,5
129
752
path_balance,5,6
149
753
path_balance,5,7
169
754
path_balance,5,8
189
755
path_balance,5,9
220
756
pch_agch_q_length,0
757
pch_q_page_discard,0
758
pch_q_page_discard,2,0
65534
759
65534
760
{22577}pdu_discard_fr,0
761
{22577}pdu_discard_llc,0
762
{23956}pfc_admission,0
763
{23956}pfc_admission_other,0
764
{23956}pfc_downgrade_success,0
765
{23956}pfc_downgrade_failure,0
766
{23956}pfc_preemptions,0
767
{23956}pfc_rejection,0
768
{23956}pfc_rejection_other,0
769
{23956}pfc_reject_causes,0
770
{23956}pfc_rej_dgrd_prmpt_prp,0
771
{23956}pfc_rej_dgrd_prmpt_cell,0
772
{23956}pfc_upgrade,0
773
ppch_q_page_discard,0
774
{24347}preempt_cap
775
prp_load,0
776
prp_load,4,0
0
Continued
68P02900W22-R
6-101
GMR-02
Mar 2008

Element name
Recommended value
777
prp_load,4,1
778
prp_load,4,2
779
prp_load,4,3
11
780
prp_load,4,4
21
781
prp_load,4,5
41
782
prp_load,4,6
61
783
prp_load,4,7
101
784
prp_load,4,8
161
785
prp_load,4,9
261
786
prp_load,5,0
787
prp_load,5,1
788
prp_load,5,2
10
789
prp_load,5,3
20
790
prp_load,5,4
40
791
prp_load,5,5
60
792
prp_load,5,6
100
793
prp_load,5,7
160
794
prp_load,5,8
260
795
prp_load,5,9
400
796
{22100}prp_pd_demand,0
797
{22577}ps_page_reqs,0
798
{24347}queue_preempt_atmpt
799
rber,0
800
rf_losses_sd,0
801
rf_losses_sd,2
2147483647
802
rf_losses_tch,0
803
rf_losses_tch,2
2147483647
804
rf_losses_tch_hr,0
805
rf_losses_tch_hr,2
2147483647
806
rf_losses_tch_hr_amr,0
807
2147483647
808
roc,0
809
roc,4,0
810
roc,4,1
14
Continued
6-102
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
811
roc,4,2
21
812
roc,4,3
28
813
roc,4,4
35
814
roc,4,5
42
815
roc,4,6
49
816
roc,4,7
55
817
roc,4,8
64
818
roc,4,9
819
roc,5,0
13
820
roc,5,1
20
821
roc,5,2
27
822
roc,5,3
34
823
roc,5,4
41
824
roc,5,5
48
825
roc,5,6
54
826
roc,5,7
63
827
roc,5,8
219
828
roc,5,9
829
routing_syntax,0
830
routing_syntax,2
2147483647
831
routing_unknown,0
832
routing_unknown,2
2147483647
833
{22586}rsl_lcf_congestion,0
834
{22586}rsl_lcf_congestion,2
2147483647
835
sabm_tx,0
836
sccp_msgs,0
837
sccp_msgs_rx,0
838
sccp_msgs_tx,0
839
sdcch_congestion,0
840
sdcch_handover,0
841
second_assign_atmpt,0
842
second_assign_suc,0
843
sib_rx,0
844
sib_tx,0
1
Continued
68P02900W22-R
6-103
GMR-02
Mar 2008

Element name
Recommended value
845
sif_sio_rx_opc,0
846
sif_sio_tx_dpc,0
847
sif_sio_type,0
848
sl_congestion,0
849
sl_congestion,2
2147483647
850
sl_stop_congestion,0
851
sms_init_on_sdcch,0
852
sms_init_on_sdcch_ho_in,0
853
sms_init_on_sdcch_ho_out,0
854
sms_init_on_tch,0
855
sms_no_bcast_msg,0
856
{22577}tbf_dl_asgn_pacch,0
857
{22577}tbf_rel_pacch_lost,0
858
{22577}tbf_sessions,0
859
tch_cong_inner_zone,0
860
tch_congestion,0
861
tch_congestion_hr,0
862
tch_congestion_hr_amr,0
863
tch_cong_inner_zone_hr,0
864
tch_cong_inner_zone_hr_amr,0
865
tch_delay,0
866
tch_delay,4,0
867
tch_delay,4,1
10001
868
tch_delay,4,2
20001
869
tch_delay,4,3
30001
870
tch_delay,4,4
40001
871
tch_delay,4,5
50001
872
tch_delay,4,6
60001
873
tch_delay,4,7
70001
874
tch_delay,4,8
80001
875
tch_delay,4,9
90001
876
tch_delay,5,0
10000
877
tch_delay,5,1
20000
878
tch_delay,5,2
30000
Continued
6-104
68P02900W22-R
GMR-02
Mar 2008

Element name
Recommended value
879
tch_delay,5,3
40000
880
tch_delay,5,4
50000
881
tch_delay,5,5
60000
882
tch_delay,5,6
70000
883
tch_delay,5,7
80000
884
tch_delay,5,8
90000
885
tch_delay,5,9
100000
886
{24347}tch_preempt_atmpt,0
887
{24347}tch_preempt_fail_no_cand,0
888
2147483647
889.
{24347}tch_preempt_fail_timeout,0
890
{24347}tch_preempt_no_q_alloc
891
{24347}tch_preempt_rqd,0
892
tch_q_length,0
893
tch_q_length,4,0
894
tch_q_length,4,1
895
tch_q_length,4,2
896
tch_q_length,4,3
897
tch_q_length,4,4
898
tch_q_length,4,5
899
tch_q_length,4,6
900
tch_q_length,4,7
901
tch_q_length,4,8
902
tch_q_length,4,9
903
tch_q_length,5,0
904
tch_q_length,5,1
905
tch_q_length,5,2
906
tch_q_length,5,3
907
tch_q_length,5,4
908
tch_q_length,5,5
909
tch_q_length,5,6
910
tch_q_length,5,7
911
tch_q_length,5,8
912
tch_q_length,5,9
255
Continued
68P02900W22-R
6-105
GMR-02
Mar 2008

Element name
Recommended value
913
tch_q_removed,0
914
tch_usage,0
915
tch_usage_ext_range,0
916
tch_usage_inner_zone,0
917
{23956}timer_exp_pap_conv,0
918
total_calls,0
919
{22100}total_gci_for_pd_demand,0
920
u_ber,0
921
u_ber,4,0
922
u_ber,4,1
923
u_ber,4,2
924
u_ber,4,3
925
u_ber,4,4
926
u_ber,4,5
927
u_ber,4,6
928
u_ber,4,7
929
u_ber,4,8
930
u_ber,4,9
931
u_ber,5,0
932
u_ber,5,1
933
u_ber,5,2
934
u_ber,5,3
935
u_ber,5,4
936
u_ber,5,5
937
u_ber,5,6
938
u_ber,5,7
939
u_ber,5,8
940
u_ber,5,9
941
{22577}ul_bler_cs1,0
942
943
944
945
{22577}ul_bler_mcs1,0
946
0
Continued
6-106
68P02900W22-R
GMR-02
Mar 2008

#
Element name
Recommended value
947
948
949
950
951
952
953
954
ul_busy_pdtch,0
955
ul_busy_pdtch,4,0
956
ul_busy_pdtch,4,1
957
ul_busy_pdtch,4,2
958
ul_busy_pdtch,4,3
959
ul_busy_pdtch,4,4
960
ul_busy_pdtch,4,5
961
ul_busy_pdtch,4,6
11
962
ul_busy_pdtch,4,7
13
963
ul_busy_pdtch,4,8
15
964
ul_busy_pdtch,4,9
17
965
ul_busy_pdtch,5,0
966
ul_busy_pdtch,5,1
967
ul_busy_pdtch,5,2
968
ul_busy_pdtch,5,3
969
ul_busy_pdtch,5,4
970
ul_busy_pdtch,5,5
10
971
ul_busy_pdtch,5,6
12
972
ul_busy_pdtch,5,7
14
973
ul_busy_pdtch,5,8
16
974
ul_busy_pdtch,5,9
400
975
{23769}ul_egprs_backhaul_demand,0
976
{23769}ul_egprs_backhaul_used,0
977
{22577}ul_llc_frames,0
978
{23956}ul_llc_data_volume,0
979
ul_pdtch_congestion,0
980
ul_pdtch_q_length,0
0
Continued
68P02900W22-R
6-107
GMR-02
Mar 2008

#
Element name
Recommended value
981
ul_pdtch_seizure,0
982
ul_radio_blks_8psk_1_ts,0
983
984
ul_radio_blks_gmsk_1_ts,0
985
986
ul_rlc_ack_new_blks,0
987
ul_rlc_retx_blks,0
988
ul_rlc_unack_new_blks,0
989
ul_tbf_time_8psk_1_ts,0
990
991
ul_tbf_time_gmsk_1_ts,0
992
993
uplink_path_loss,0
994
uplink_path_loss,4,0
47
995
58
996
69
997
80
998
90
999
101
1000
112
1001
122
1002
132
1003
143
1004
57
1005
68
1006
79
1007
89
1008
100
1009
111
1010
121
1011
131
1012
142
1013
153
1014
zone_change_atmpt,0
1015
zone_change_suc,0
6-108
68P02900W22-R
GMR-02
Mar 2008
Specics table
Specics table
Description of Specics table

The Specics table (Table 6-21) allows the user to specify specic values for chg_element
and add_cell elements for a particular site or cell overriding the parameters specied in the
Generics, Timers, and Statistics tables.
NOTE
Elements that can exist in the Cell table are not shown in the Specics table.
Some elements exist here but do not exist in the Generics, Timers, or Statistics
table because of restrictions such as the following elements that have no specic
default value, or elements that are specic to particular site/cell congurations,
for example, elements only supported at Horizonofce.
Some elements that exist within the Generics, Timers, or Statistics tables do not
exist here because they are only required for site 0 (BSC). Therefore, there may
only be one instance of the element.
Default lename: spec.mcd
Table 6-21 Specics table

Field Name
Element Name
Field Width
Range
Status
50
Text:
<element name>
[,<index>]
Mandatory
This eld identies the element for which a specic value is required. The specic element
name is optionally followed by an index.
Continued
68P02900W22-R
6-109
GMR-02
Mar 2008
Description of Specics table
Table 6-21
Specics table (Continued)
Field Name
Site Number
Field Width
Range
Status
0 to 120, 251, 252

and 253 (up to 1760).
0 to 100, 251, 252
and 253 (from 1800).
Mandatory
This eld is used to identify the site at which the specic value is required.
* From 1515 and prior to 1620 RXCDR areas:
For the following elements this eld is used for the BSS_ID (range 0 to 31 ) parameter of
the chg_element command, not the site number. In RXCDRs the Site Number for these
elements is xed as site 0.
efr_enabled
dl_audio_lev_offset
ul_audio_lev_offset
volume_control_type
enh_ter_cic_mgt_ena
MCC
3 digit numeric
Mandatory
3 digit numeric
Mandatory
6 digit numeric
Optional

MNC
LAC
The Location Area Code. This eld can be entered in decimal or hex form.
Hex numbers must be followed by h or preceded by 0x, for example, 1234h or 0x1234.
This eld is used as the LAC of the Cell for which the specic value is required.
CI
6 digit numeric
Optional (mandatory
if the LAC eld
contains a cell's LAC).
The Cell identier can be entered in decimal or hex form.

Hex numbers must be followed by h or preceded by 0x, for example, 1234h or 0x1234.
This eld is used as the CI of the Cell for which the specic value is required.
Value
11
-2, 147, 483, 647

to
+2, 147, 483, 647
(Element dependent)
Mandatory
This eld is used as the specic value.
6-110
68P02900W22-R
GMR-02
Mar 2008
Layout of elements in the MCDF Specics table
The elements in the Specics table are displayed in Table 6-22as follows:
Table 6-22 Specics table - elements

Element name
#
1
access_per_agch,0
access_per_pch_cs,0
access_per_pch_cs_ps,0
access_per_pch_ps,0
access_per_ppch,0
access_per_rach,0
adap_ho_alt_trigger_rxqual
adap_ho_pbgt
adap_ho_rxlev
10
adap_ho_rxqual
11
adap_trigger_hop_rxqual_dl
12
adap_trigger_hop_rxqual_ul
13
adap_trigger_pbgt
14
adap_trigger_rxlev_dl
15
adap_trigger_rxlev_ul
16
adap_trigger_rxqual_dl
17
adap_trigger_rxqual_ul
18
air_dl_control_blks,0
19
air_dl_tbf_failures,0
20
air_ul_control_blks,0
21
air_ul_tbf_failures,0
22
alloc_sdcch,0
23
alloc_sdcch_carr,0
24
alloc_sdcch_fail,0
25
alloc_sdcch_fail,2
26
alloc_tch,0
27
alloc_tch_carr,0
28
alloc_tch_fail,0
Continued
68P02900W22-R
6-111
GMR-02
Mar 2008
Table 6-22 Specics table - elements (Continued)

Element name
#
29
alloc_tch_fail,2
30
alloc_tch_fail_hr,0 (from 1760)
31
alloc_tch_fail_hr_amr,0 (in 1740)
32
33
alloc_tch_hr,0 (from 1760)
34
alloc_tch_hr_amr,0 (in 1740)
35
alloc_tch_inner_zone,0
36
alt_qual_proc
37
amr_decrease_thresh_adjust,0
38
amr_fr_dl_adaptation,0
39
amr_fr_dl_codec_mode_usage,0
40
amr_fr_dl_la_enabled
41
amr_fr_ul_adaptation,0
42
amr_fr_ul_codec_mode_usage,0
43
amr_fr_ul_la_enabled
44
amr_full_rate_enabled
45
46
amr_hop_count (in 1740)
47
amr_hr_dl_adaptation,0
48
amr_hr_dl_codec_mode_usage,0
49
amr_hr_dl_la_enabled
50
amr_hr_intracell_ho_allowed (in 1740)
51
amr_hr_res_ts (in 1740)
52
amr_hr_ul_adaptation,0
53
amr_hr_ul_codec_mode_usage,0
54
amr_hr_ul_la_enabled
55
amr_increase_thresh_adjust,0
56
amr_inner_hr_usage_thres (in 1740)
57
amr_new_calls_hr
58
amr_recong_fr_to_hr
59
assignment_redirection,0
60
ater_channel_status,0
61
ater_emerg_preempt_status,0
62
{24347}ater_preempt_atmpt,0
(in 1740)
Continued
6-112
68P02900W22-R
GMR-02
Mar 2008

Element name
#
63
{24347}ater_preempt_atmpt_swover,0
64
65
66
{24347}ater_preempt_fail_swover,0
67
{24347}ater_preempt_rqd,0
68
attach_detach
69
auto_rf_loss_trace
70
available_sdcch,0
71
available_tch,0
72
available_tch,4,0
73
available_tch,4,1
74
available_tch,4,2
75
available_tch,4,3
76
available_tch,4,4
77
available_tch,4,5
78
available_tch,4,6
79
available_tch,4,7
80
available_tch,4,8
81
available_tch,4,9
82
available_tch,5,0
83
available_tch,5,1
84
available_tch,5,2
85
available_tch,5,3
86
available_tch,5,4
87
available_tch,5,5
88
available_tch,5,6
89
available_tch,5,7
90
available_tch,5,8
91
available_tch,5,9
92
{22404}available_tch_dcs1800,0
93
{22404}available_tch_egsm,0
94
available_tch_hr (from 1760)
95
available_tch_hr_amr,0 (in 1740)
96
{22404}available_tch_pgsm,0
Continued
68P02900W22-R
6-113
GMR-02
Mar 2008

Element name
#
97
{28486}avg_simul_dl_tbfs,0
98
{28486}avg_simul_ul_tbfs,0
99
bad_ho_refnum_ms,0
100
bad_ho_refnum_ms,2
101
band_preference
102
band_preference_mode
103
bep_period
104
bep_period2
105
ber,0
106
ber_loss_daily
107
ber_loss_hourly
108
{22879}blind_search_preference
109
{28486}blocked_dl_tbfs,0
110
bounce_protect_cong_tmr
111
bounce_protect_margin
112
bounce_protect_qual_tmr
113
bs_pa_mfrms
114
bs_pag_blks_res
115
bs_pbcch_blks
116
bs_pcc_chans
117
bs_prach_blks
118
bss_availability
119
bss_msc_overload_allowed
120
{22586}bss_ovld_msgs_tx,0
121
bssgp_block_retries
122
{23956}bssgp_dwnld_retry
123
bssgp_fc_period_c
124
bssgp_racap_retries
125
bssgp_reset_retries
126
bssgp_t1_timer
127
bssgp_t2_timer
128
{23956}bssgp_t5_timer
129
130
Continued
6-114
68P02900W22-R
GMR-02
Mar 2008

Element name
#
131
bssgp_unblock_retries
132
bts_escalation
133
bts_p_con_ack
134
bts_p_con_interval
135
bts_power_control_allowed
136
bts_txpwr_max_inner
137
busy_cics,0
138
busy_cics,4,0
139
busy_cics,4,1
140
busy_cics,4,2
141
busy_cics,4,3
142
busy_cics,4,4
143
busy_cics,4,5
144
busy_cics,4,6
145
busy_cics,4,7
146
busy_cics,4,8
147
busy_cics,4,9
148
busy_cics,5,0
149
busy_cics,5,1
150
busy_cics,5,2
151
busy_cics,5,3
152
busy_cics,5,4
153
busy_cics,5,5
154
busy_cics,5,6
155
busy_cics,5,7
156
busy_cics,5,8
157
busy_cics,5,9
158
busy_sdcch,0
159
busy_sdcch,4,0
160
busy_sdcch,4,1
161
busy_sdcch,4,2
162
busy_sdcch,4,3
163
busy_sdcch,4,4
164
busy_sdcch,4,5
Continued
68P02900W22-R
6-115
GMR-02
Mar 2008

Element name
#
165
busy_sdcch,4,6
166
busy_sdcch,4,7
167
busy_sdcch,4,8
168
busy_sdcch,4,9
169
busy_sdcch,5,0
170
busy_sdcch,5,1
171
busy_sdcch,5,2
172
busy_sdcch,5,3
173
busy_sdcch,5,4
174
busy_sdcch,5,5
175
busy_sdcch,5,6
176
busy_sdcch,5,7
177
busy_sdcch,5,8
178
busy_sdcch,5,9
179
busy_tch,0
180
busy_tch,4,0
181
busy_tch,4,1
182
busy_tch,4,2
183
busy_tch,4,3
184
busy_tch,4,4
185
busy_tch,4,5
186
busy_tch,4,6
187
busy_tch,4,7
188
busy_tch,4,8
189
busy_tch,4,9
190
busy_tch,5,0
191
busy_tch,5,1
192
busy_tch,5,2
193
busy_tch,5,3
194
busy_tch,5,4
195
busy_tch,5,5
196
busy_tch,5,6
197
busy_tch,5,7
198
busy_tch,5,8
Continued
6-116
68P02900W22-R
GMR-02
Mar 2008

Element name
#
199
busy_tch,5,9
200
busy_tch_carr,0
201
busy_tch_carr_hr,0 (from 1760)
202
busy_tch_carr_hr_amr,0 (in 1740)
203
{22404}busy_tch_dcs1800,0
204
{22404}busy_tch_egsm,0
205
busy_tch_hr,0
206
busy_tch_hr,4,0
207
busy_tch_hr,4,1
208
busy_tch_hr,4,2
209
busy_tch_hr,4,3
210
busy_tch_hr,4,4
211
busy_tch_hr,4,5
212
busy_tch_hr,4,6
213
busy_tch_hr,4,7
214
busy_tch_hr,4,8
215
busy_tch_hr,4,9
216
busy_tch_hr,5,0
217
busy_tch_hr,5,1
218
busy_tch_hr,5,2
219
busy_tch_hr,5,3
220
busy_tch_hr,5,4
221
busy_tch_hr,5,5
222
busy_tch_hr,5,6
223
busy_tch_hr,5,7
224
busy_tch_hr,5,8
225
busy_tch_hr,5,9
226
busy_tch_hr_amr,0
227
busy_tch_hr_amr,4,0
228
busy_tch_hr_amr,4,1
229
busy_tch_hr_amr,4,2
230
busy_tch_hr_amr,4,3
231
busy_tch_hr_amr,4,4
232
busy_tch_hr_amr,4,5
Continued
68P02900W22-R
6-117
GMR-02
Mar 2008

Element name
#
233
busy_tch_hr_amr,4,6
234
busy_tch_hr_amr,4,7
235
busy_tch_hr_amr,4,8
236
busy_tch_hr_amr,4,9
237
busy_tch_hr_amr,5,0
238
busy_tch_hr_amr,5,1
239
busy_tch_hr_amr,5,2
240
busy_tch_hr_amr,5,3
241
busy_tch_hr_amr,5,4
242
busy_tch_hr_amr,5,5
243
busy_tch_hr_amr,5,6
244
busy_tch_hr_amr,5,7
245
busy_tch_hr_amr,5,8
246
busy_tch_hr_amr,5,9
247
{22404}busy_tch_pgsm,0
248
bvci
249
c31_hyst
250
c32_qual
251
call_trace_options
252
called_pci
253
calling_pci
254
calls_queued,0
255
calls_queued,2
256
carrier_disable_time
257
carriers_ins_pwr_fail
258
cbc_fast_select
259
cbc_intface_vers
260
cbc_vbind_cntr
261
cbch_enabled
262
cbs_outage_cntr
263
ccch_conf
264
ccch_load_period
265
cell_bar_access_class
266
cell_bar_access_switch
Continued
6-118
68P02900W22-R
GMR-02
Mar 2008

Element name
#
267
cell_bar_qualify
268
cell_ush_reqs,0
269
cell_reselect_offset
270
cell_reselect_param_ind
271
ch_req_unsvcd_pcu,0
272
chan_dl_tx_pwr_lvl,0
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
chan_req_cause_atmpt,0
294
chan_req_ms_blk,0
295
chan_req_ms_blk_2
296
chan_req_ms_fail,0
297
chan_req_ms_fail_2
298
chan_req_ms_fail_2,0
299
300
Continued
68P02900W22-R
6-119
GMR-02
Mar 2008

Element name
#
301
chan_ul_tx_pwr_lvl,0
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
channel_reconguration_switch
323
channel_reqs_rec,0
324
channel_reqs_reject,0
325
channel_reqs_success,0
326
ciph_mode_rej_allowed
327
cipher_mode_fail,0
328
cipher_mode_fail,2
329
330
331
clk_src_fail_reset_period
332
clr_cmd_from_msc,0
333
clr_req_to_msc,0
334
coding_scheme_change,0
Continued
6-120
68P02900W22-R
GMR-02
Mar 2008

Element name
#
335
coincident_offset
336
confusion_msg_allowed
337
cong_rel_dl_scts,0
338
congest_at_source
339
congest_at_target
340
congest_exist_ho_atmpt,0
341
congest_stand_ho_atmpt,0
342
343
congestion_lost_msu_2
344
conn_refused,0
345
connection_code
346
conn_req_to_msc,0
347
cp_option_reset_ckt
348
cp_option_rr_status
349
cpu_usage,0
350
cpu_usage,4,0
351
cpu_usage,4,1
352
cpu_usage,4,2
353
cpu_usage,4,3
354
cpu_usage,4,4
355
cpu_usage,4,5
356
cpu_usage,4,6
357
cpu_usage,4,7
358
cpu_usage,4,8
359
cpu_usage,4,9
360
cpu_usage,5,0
361
cpu_usage,5,1
362
cpu_usage,5,2
363
cpu_usage,5,3
364
cpu_usage,5,4
365
cpu_usage,5,5
366
cpu_usage,5,6
367
cpu_usage,5,7
368
cpu_usage,5,8
Continued
68P02900W22-R
6-121
GMR-02
Mar 2008

Element name
#
369
cpu_usage,5,9
370
cr_calling
371
crm_timer_value,0
372
crm_timer_value,1
373
crm_timer_value,2
374
crm_timer_value,3
375
crm_timer_value,4
376
crm_timer_value,5
377
crm_timer_value,6
378
crm_timer_value,7
379
crm_timer_value,8
380
crm_timer_value,9
381
crm_timer_value,10
382
crm_timer_value,11
383
crm_timer_value,12
384
crmpc_timer_value,0
385
crmpc_timer_value,1
386
crmpc_timer_value,2
387
crmpc_timer_value,3
388
crmpc_timer_value,4
389
crmpc_timer_value,5
390
crmpc_timer_value,6
391
crmpc_timer_value,7
392
crmpc_timer_value,8
393
{22577}cs_page_reqs,0
394
cs12_on_32k_chan,0
395
cs1234_on_64k_chan,0
396
d1_ba_alloc_proc
397
d1_missing_rpt
398
d1_ncell_proc
399
d1_sdcch_ho
400
d1_sdcch_timer_ho
401
decision_1_dl_rxlev_av_h
402
decision_1_dl_rxlev_av_ih
Continued
6-122
68P02900W22-R
GMR-02
Mar 2008

Element name
#
403
decision_1_dl_rxlev_av_p
404
decision_1_dl_rxqual_av_h
405
decision_1_dl_rxqual_av_p
406
decision_1_n1
407
decision_1_n2
408
decision_1_n3
409
decision_1_n4
410
decision_1_n5
411
decision_1_n6
412
decision_1_n7
413
decision_1_n8
414
decision_1_ncell_rxlev_av_h_calc
415
decision_1_p_bgt_rxlev_av_h
416
decision_1_p1
417
decision_1_p2
418
decision_1_p3
419
decision_1_p4
420
decision_1_p5
421
decision_1_p6
422
decision_1_p7
423
decision_1_p8
424
decision_1_tim_adv_av_alg
425
decision_1_ul_rxlev_av_h
426
decision_1_ul_rxlev_av_ih
427
decision_1_ul_rxlev_av_p
428
decision_1_ul_rxqual_av_h
429
decision_1_ul_rxqual_av_p
430
decision_alg_type
431
direct_inner_zone_threshold
432
disuse_cnt_hreqave
433
dl_audio_lev_offset
434
435
436
Continued
68P02900W22-R
6-123
GMR-02
Mar 2008

Element name
#
437
438
439
440
441
442
443
444
445
446
447
dl_busy_pdtch,0
448
dl_busy_pdtch,4,0
449
dl_busy_pdtch,4,1
450
dl_busy_pdtch,4,2
451
dl_busy_pdtch,4,3
452
dl_busy_pdtch,4,4
453
dl_busy_pdtch,4,5
454
dl_busy_pdtch,4,6
455
dl_busy_pdtch,4,7
456
dl_busy_pdtch,4,8
457
dl_busy_pdtch,4,9
458
dl_busy_pdtch,5,0
459
dl_busy_pdtch,5,1
460
dl_busy_pdtch,5,2
461
dl_busy_pdtch,5,3
462
dl_busy_pdtch,5,4
463
dl_busy_pdtch,5,5
464
dl_busy_pdtch,5,6
465
dl_busy_pdtch,5,7
466
dl_busy_pdtch,5,8
467
dl_busy_pdtch,5,9
468
dl_dtx_voice_data
469
{23769}dl_egprs_backhaul_demand,0
470
{23769}dl_egprs_backhaul_used,0
Continued
6-124
68P02900W22-R
GMR-02
Mar 2008

Element name
#
471
{23956}dl_llc_data_volume,0
472
{22577}dl_llc_frames_gb,0
473
{22577}dl_llc_frames_pcu,0
474
dl_pdtch_q_length,0
475
dl_pdtch_seizure,0
476
477
478
479
dl_radio_blks,4_ts,0
480
dl_rlc_ack_new_blks,0
481
dl_rlc_ddtr_blks,0
482
dl_rlc_nack_blks,0
483
dl_rlc_retx_blks,0
484
dl_rlc_stalled_blks,0
485
dl_rlc_unack_new_blks,0
486
dl_rxlev_ho_allowed
487
dl_rxqual_ho_allowed
488
dl_tbf_time_1_ts,0
489
dl_tbf_time_2_ts,0
490
dl_tbf_time_3_ts,0
491
dl_tbf_time,4_ts,0
492
downlink_sync_timer
493
dr_chan_mode_modify
494
dr_ho_during_assign
495
dr_msc_preference
496
dr_preference
497
dr_standard_congest
498
dtx_required
499
dual_band_offset
500
dyn_step_adj
501
dyn_step_adj_fmpr
502
dynet_assign_fail,0
503
dynet_call_rejects,0
504
dynet_retry_time
Continued
68P02900W22-R
6-125
GMR-02
Mar 2008

Element name
#
505
dynet_tchs_reserved
506
efr_enabled
507
{23769}egprs_64k_channel_width,0
508
egprs_64k_channels_switched,0
509
egprs_64k_not_avail,0
510
egprs_avail_pdtch,0
511
egprs_dl_asgn_pccch,0
512
egprs_init_dl_cs
513
egprs_init_ul_cs
514
egsm_handover_threshold
515
emergency_class_switch
516
en_incom_ho
517
enh_ter_cic_mgt_ena_val
518
enhanced_relief
519
er_intra_cell_ho_atmpt,0
520
er_intra_cell_ho_suc,0
521
erc_ta_priority
522
extended_paging_active
523
fdd_gprs_qoffset
524
{22879}fdd_multirat_reporting
525
{22879}fdd_rep_quant
526
fer,0
527
fer_amr_fr,0
528
fer_amr_hr,0
529
fer_gsm_fr_efr,0
530
fer_gsm_hr,0
531
fer_non_amr,0
532
ow_control_barred,0
533
frmr,0
534
frmr,2
535
full_pwr_ross
536
g_rach_unsvcd_bts,0
537
gbl_dl_data_thrput,0
538
gbl_dl_data_thrput_hist,0
Continued
6-126
68P02900W22-R
GMR-02
Mar 2008

Element name
#
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
gbl_ow_ctrl_sent,0
560
gbl_paging_reqs,0
561
gbl_thrput_period
562
gbl_ul_data_thrput,0
563
gbl_ul_data_thrput_hist,0
564
565
566
567
568
569
570
571
572
Continued
68P02900W22-R
6-127
GMR-02
Mar 2008

Element name
#
573
574
575
576
577
578
579
580
581
582
583
584
gbl_unavailable,0
585
gclk_qwarm_ag
586
global_reset_repetitions
587
gproc_slots
588
gprs_32k_channels_switched,0
589
gprs_32k_dl_not_avail,0
590
gprs_32k_ul_not_avail,0
591
gprs_access_per_agch,0
592
gprs_access_per_rach,0
593
gprs_avail_pdtch,0
594
gprs_bs_cv_max
595
gprs_cell_congestion,0
596
gprs_cell_reselect_attmpt,0
597
gprs_cell_reselect_fail,0
598
gprs_cell_reselect_hysteresis
599
gprs_channels_switched,0
600
gprs_dl_asgn_pccch,0
601
gprs_drx_timer_max
602
gprs_dynet_failures,0
603
gprs_dynet_res_reqs,0
604
605
606
Continued
6-128
68P02900W22-R
GMR-02
Mar 2008

#
Element name
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
gprs_dynet_swi_reqs,0
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
Continued
68P02900W22-R
6-129
GMR-02
Mar 2008

Element name
#
641
642
643
644
645
gprs_intraho_allwd
646
gprs_min_prr_blks
647
gprs_ms_pan_dec
648
gprs_ms_pan_inc
649
gprs_ms_pan_max
650
gprs_ms_txpwr_max_cch
651
{23956}gprs_par_wait_ind
652
gprs_pb
653
gprs_pc_alpha
654
gprs_pc_meas_chan
655
gprs_pch_agch_q_length,0
656
gprs_penalty_time
657
gprs_ppch_pagch_q_length,0
658
gprs_prr_blk_usg,0
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
Continued
6-130
68P02900W22-R
GMR-02
Mar 2008

Element name
#
675
676
677
678
679
gprs_rach_arrival,0
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
gprs_recong_thresh_idle_tch
701
gprs_reselect_offset
702
gprs_rxlev_access_min
703
gprs_sig_bvci
704
gprs_smg30_t3192
705
gprs_t3168
706
gprs_t3192
707
gprs_temporary_offset
708
gprs_ts_cong_alg
Continued
68P02900W22-R
6-131
GMR-02
Mar 2008

Element name
#
709
group_block_unblock_allowed
710
gsm_cell_id_format
711
gsm_half_rate_enabled
712
handover_recognized_period
713
handover_required_curr_ch
714
handover_required_reject_switch
715
hcs_thr
716
hdsl_losw_oos
717
hdsl_losw_restore
718
hdsl_snr_daily
719
hdsl_snr_daily_mon_period
720
hdsl_snr_hourly
721
hdsl_snr_hourly_mon_period
722
hdsl_snr_oos
723
hdsl_snr_restore
724
ho_exist_congest
725
ho_fail_no_resources,0
726
ho_margin_usage_ag
727
ho_only_max_pwr
728
ho_pwr_level_inner
729
ho_req_ack_to_msc,0
730
ho_req_msc_fail,0
731
ho_req_msc_fail,2
732
ho_req_msc_proto,0
733
ho_req_msc_proto,2
734
hop_count
735
hop_count_timer
736
hopping_support
737
738
739
740
741
742
Continued
6-132
68P02900W22-R
GMR-02
Mar 2008

Element name
#
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
hr_fr_hop_count (from 1760)
770
hr_intracell_ho_allowed (from 1760)
771
hr_res_ts (from 1760)
772
i_frames_rx,0
773
i_frames_tx,0
774
775
776
Continued
68P02900W22-R
6-133
GMR-02
Mar 2008

Element name
#
777
778
779
780
781
782
783
784
illegal_circuit_id
785
imm_assgn_cause,0
786
immediate_assign_mode
787
{22404}imrm_dcs1800_weight
788
{22404}imrm_egsm_weight
789
{22404}imrm_force_recalc
790
{22404}imrm_pgsm_weight
791
{22404}imrm_umts_weight
792
in_inter_bss_ho,0
793
in_intra_bss_ho,0
794
in_intra_bss_nc_atmpt,0
795
in_intra_bss_nc_suc,0
796
init_dl_cs
797
init_ul_cs
798
initial_sync_timer
799
inner_hr_usage_thres (from 1760)
800
intave
801
inter_cell_handover_allowed
802
interband_activity,0
803
interband_ho_allowed
804
interfer_bands,0
805
interfer_bands,1
806
interfer_bands,2
807
interfer_bands,3
808
interfer_bands,4
809
interfer_ho_allowed
810
intf_on_idle,0
Continued
6-134
68P02900W22-R
GMR-02
Mar 2008

Element name
#
811
intf_on_idle,4,0
812
intf_on_idle,4,1
813
intf_on_idle,4,2
814
intf_on_idle,4,3
815
intf_on_idle,4,4
816
intf_on_idle,4,5
817
intf_on_idle,4,6
818
intf_on_idle,4,7
819
intf_on_idle,4,8
820
intf_on_idle,4,9
821
intf_on_idle,5,0
822
intf_on_idle,5,1
823
intf_on_idle,5,2
824
intf_on_idle,5,3
825
intf_on_idle,5,4
826
intf_on_idle,5,5
827
intf_on_idle,5,6
828
intf_on_idle,5,7
829
intf_on_idle,5,8
830
intf_on_idle,5,9
831
intra_bss_ho_cause_suc,0
832
intra_cell_handover_allowed
833
intra_cell_ho,0
834
inv_est_cause_on_rach,0
835
invalid_frames_rx,0
836
invalid_frames_rx,2
837
l_rxlev_dl_h
838
l_rxlev_dl_p
839
l_rxlev_ul_h
840
l_rxlev_ul_p
841
l_rxqual_dl_h
842
l_rxqual_dl_h_amr_fr
843
l_rxqual_dl_h_amr_hr (in 1740)
844
l_rxqual_dl_h_hr (from 1760)

Continued
68P02900W22-R
6-135
GMR-02
Mar 2008

Element name
#
845
l_rxqual_dl_h_data
846
847
l_rxqual_dl_h_hopping_amr_fr
848
l_rxqual_dl_h_hopping_amr_hr (in 1740)
849
l_rxqual_dl_h_hopping_hr (from 1760)
850
l_rxqual_dl_p
851
l_rxqual_dl_p_amr_fr
852
l_rxqual_dl_p_amr_hr
853
l_rxqual_dl_p_data
854
855
l_rxqual_dl_p_hopping_amr_fr
856
l_rxqual_dl_p_hopping_amr_hr (in 1740)
857
l_rxqual_dl_p_hopping_hr (from 1760)
858
l_rxqual_ul_h
859
l_rxqual_ul_h_amr_fr
860
l_rxqual_ul_h_amr_hr (in 1740)
861
l_rxqual_ul_h_hr (from 1760)
862
l_rxqual_ul_h_data
863
864
l_rxqual_ul_h_hopping_amr_fr
865
l_rxqual_ul_h_hopping_amr_hr (in 1740)
866
l_rxqual_ul_h_hopping_hr (from 1760)
867
l_rxqual_ul_p
868
l_rxqual_ul_p_amr_fr
869
l_rxqual_ul_p_amr_hr
870
l_rxqual_ul_p_data
871
872
l_rxqual_ul_p_hopping_amr_fr
873
l_rxqual_ul_p_hopping_amr_hr (in 1740)
874
l_rxqual_ul_p_hopping_hr (from 1760)
875
layer_number
876
link_about_to_fail
877
link_fail
878
local_maintenance
Continued
6-136
68P02900W22-R
GMR-02
Mar 2008

Element name
#
879
low_sig_thresh
880
lta_alarm_range
881
ltu_fw_auto_download
882
ma_cmd_to_ms,0
883
ma_cmd_to_ms_blkd,0
884
ma_cmd_to_ms_blkd,2
885
ma_complete_from_ms,0
886
ma_complete_to_msc,0
887
ma_fail_from_ms,0
888
ma_fail_from_ms,2
889
ma_req_from_msc,0
890
891
892
ma_req_sdcch_pg_rsp,0
893
max_gprs_ts_per_carrier
894
max_ms_dl_buffer
895
max_ms_dl_rate
896
max_q_length_full_rate_channel
897
max_q_length_sdcch
898
max_retran
899
max_rst_ckt_timer_exps
900
mb_tch_congest_thres
901
mms_cat_enable
902
mms_cong_type
903
mms_cong_type_pcu
904
ms_access_by_type,0
905
ms_distance_allowed
906
ms_p_con_ack
907
ms_power_control_allowed
908
ms_power_level_period
909
ms_power_offset
910
ms_tch_usage_by_type,0
911
ms_txpwr_max_inner
912
{22586} msgs_discard_on_gproc,0
Continued
68P02900W22-R
6-137
GMR-02
Mar 2008

Element name
#
913
{22586} msgs_discard_on_rsl,0
914
mspwr_alg
915
msu_discarded,0
916
msu_discarded,2
917
mt_lcs_on_sdcch,0
918
mtl_loadshare_granularity
919
mtp_changeback,0
920
mtp_changeover,0
921
mtp_congestion,0
922
mtp_link_ins,0
923
mtp_linkfail,0
924
mtp_local_busy,0
925
mtp_local_mgt,0
926
mtp_mgt_inhibit,0
927
mtp_mgt_uninhibit,0
928
mtp_msu_rx,0
929
mtp_msu_tx,0
930
mtp_neg_acks,0
931
mtp_neg_acks,2
932
mtp_re_tx,0
933
mtp_re_tx,2
934
mtp_remote_mgt,0
935
mtp_remote_proc,0
936
mtp_restoration,0
937
mtp_sif_sio_rx,0
938
mtp_sif_sio_tx,0
939
mtp_sl_ack,0
940
mtp_sl_ack,2
941
mtp_sl_alignment,0
942
mtp_sl_alignment,2
943
mtp_sl_congestion,0
944
mtp_sl_congestion,2
945
mtp_sl_error_rate,0
946
mtp_sl_error_rate,2
Continued
6-138
68P02900W22-R
GMR-02
Mar 2008

Element name
#
947
mtp_sl_fail,0
948
mtp_sl_fail,2
949
mtp_sl_br,0
950
mtp_sl_br,2
951
mtp_start_rpo,0
952
mtp_start_rpo,2
953
mtp_stop_rpo,0
954
mtp_su_error,0
955
mtp_su_error,2
956
mtp_unavailable,0
957
multiband_reporting
958
n_avg_i
959
n2_expiry,0
960
n2_expiry,2
961
ncc_of_plmn_allowed
962
neighbor_journal
963
964
new_calls_hr (from 1760)
965
no_pdtch_avail,0
966
no_pdtch_avail_time,0
967
ns_alive_retries
968
ns_alive_timer
969
ns_block_retries
970
ns_block_timer
971
ns_reset_period
972
ns_reset_timer
973
ns_test_timer
974
ns_unblock_retries
975
num_audit_retries
976
{22708}num_cell_resel_cell,0
977
{22708}num_cell_resel_cell_pccn,0
978
{22708}num_cell_resel_cell_succ,0
979
{22708}num_cell_resel_nei,0
980
{22708}num_cell_resel_nei_pccn,0
Continued
68P02900W22-R
6-139
GMR-02
Mar 2008

Element name
#
981
{22708}num_cell_resel_nei_succ,0
982
num_emerg_access,0
983
num_emerg_rejected,0
984
num_emerg_tch_kill,0
985
num_emerg_term_sdcch,0
986
num_gbl_dl_thrput_samples
987
num_gbl_ul_thrput_samples
988
{22879}num_ho_to_3g_attempts,0
989
{22879}num_ho_from_3g_attempts,0
990
{22879}num_ho_from_3g_success,0
991
{22879}num_ho_to_3g_res_alloc_succ,0
992
{22879}num_ho_to_3g_success,0
993
{22879}num_multirat_ms_orig_call,0
994
{22879}num_t3121_expiry,0
995
number_of_preferred_cells
996
ok_acc_proc,0
997
ok_acc_proc_suc_rach,0
998
option_alg_a5_1
999
option_alg_a5_2
1000
option_alg_a5_3
1001
option_alg_a5_4
1002
option_alg_a5_5
1003
option_alg_a5_6
1004
option_alg_a5_7
1005
{24347}option_preempt
1006
out_ho_cause_atmpt,0
1007
out_inter_bss_ho,0
1008
out_inter_bss_ho,2
1009
out_intra_bss_ho,0
1010
out_intra_bss_nc_atmpt,0
1011
out_intra_bss_nc_suc,0
1012
outer_zone_usage_level
1013
override_intra_bss_pre_transfer
1014
{22577}pacch_page_reqs,0
Continued
6-140
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1015
{24303}packet_sysinfo_req,0
1016
{24303}packet_sysinfo_resp,0
1017
page_req_from_msc,0
1018
1019
1020
paging_requests_cs,0
1021
paging_requests_ps,0
1022
path_balance,0
1023
path_balance,4,0
1024
path_balance,4,1
1025
path_balance,4,2
1026
path_balance,4,3
1027
path_balance,4,4
1028
path_balance,4,5
1029
path_balance,4,6
1030
path_balance,4,7
1031
path_balance,4,8
1032
path_balance,4,9
1033
path_balance,5,0
1034
path_balance,5,1
1035
path_balance,5,2
1036
path_balance,5,3
1037
path_balance,5,4
1038
path_balance,5,5
1039
path_balance,5,6
1040
path_balance,5,7
1041
path_balance,5,8
1042
path_balance,5,9
1043
pbgt_mode
1044
pccch_drx_timer_max
1045
pccch_enabled
1046
pch_agch_q_length,0
1047
pch_q_page_discard,0
1048
Continued
68P02900W22-R
6-141
GMR-02
Mar 2008

Element name
#
1049
1050
pcr_enable
1051
pcr_n1
1052
pcr_n2
1053
{22577}pdu_discard_fr,0
1054
{22577}pdu_discard_llc,0
1055
penalty_time
1056
percent_traf_cs
1057
{23956}pfc_admission,0
1058
{23956}pfc_admission_other,0
1059
{23956}pfc_downgrade_failure,0
1060
{23956}pfc_downgrade_success,0
1061
{23956}pfc_preemptions,0
1062
{23956}pfc_rej_dgrd_prmpt_cell,0
1063
{23956}pfc_rej_dgrd_prmpt_prp,0
1064
{23956}pfc_reject_causes,0
1065
{23956}pfc_rejection,0
1066
{23956}pfc_rejection_other,0
1067
{23956}pfc_upgrade,0
1068
phase_lock_gclk
1069
phase_lock_retry
1070
phase2_resource_ind_allowed
1071
pool_gproc_preemption
1072
poor_initial_assignment
1073
pow_inc_step_size_dl
1074
pow_inc_step_size_ul
1075
pow_red_step_size_dl
1076
pow_red_step_size_ul
1077
ppch_q_page_discard,0
1078
prach_s
1079
prach_tx_int
1080
{24347}preempt_cap,0
1081
primary_pcu
1082
prioritize_microcell
Continued
6-142
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1083
priority_class
1084
protect_last_ts
1085
prp_load,0
1086
prp_load,4,0
1087
prp_load,4,1
1088
prp_load,4,2
1089
prp_load,4,3
1090
prp_load,4,4
1091
prp_load,4,5
1092
prp_load,4,6
1093
prp_load,4,7
1094
prp_load,4,8
1095
prp_load,4,9
1096
prp_load,5,0
1097
prp_load,5,1
1098
prp_load,5,2
1099
prp_load,5,3
1100
prp_load,5,4
1101
prp_load,5,5
1102
prp_load,5,6
1103
prp_load,5,7
1104
prp_load,5,8
1105
prp_load,5,9
1106
{22577}ps_page_reqs,0
1107
psi1_repeat_period
1108
pwr_handover_allowed
1109
pwrc
1110
{23956}qos_mtbr_be_dl
1111
{23956}qos_mtbr_be_ul
1112
{23956}qos_mtbr_bg_dl
1113
{23956}qos_mtbr_bg_ul
1114
1115
1116
Continued
68P02900W22-R
6-143
GMR-02
Mar 2008

Element name
#
1117
1118
1119
1120
{22879}qsearch_c
1121
qsearch_p
1122
queue_management_information
1123
{24347}queue_preempt_atmpt,0
1124
ra_colour
1125
ra_reselect_hysteresis
1126
rac
1127
rach_load_period
1128
rach_load_threshold
1129
rach_load_type
1130
radio_link_timeout
1131
rapid_pwr_down
1132
rber,0
1133
recong_fr_to_hr (from 1760)
1134
red_loss_daily
1135
red_loss_hourly
1136
red_loss_oos
1137
red_loss_restore
1138
red_time_oos
1139
red_time_restore
1140
reestablish_allowed
1141
remote_loss_daily
1142
remote_loss_daily_pcu
1143
remote_loss_hourly
1144
remote_loss_hourly_pcu
1145
remote_loss_oos
1146
remote_loss_oos_pcu
1147
remote_loss_restore
1148
remote_loss_restore_pcu
1149
remote_time_oos
1150
remote_time_oos_pcu
Continued
6-144
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1151
remote_time_restore
1152
remote_time_restore_pcu
1153
report_resource_tch_f_high_water_mark
1154
report_resource_tch_f_low_water_mark
1155
res_gprs_pdchs
1156
res_ts_less_one_carrier
1157
rf_losses_sd,0
1158
rf_losses_sd,2
1159
rf_losses_tch,0
1160
rf_losses_tch,2
1161
rf_losses_tch_hr,0
1162
rf_losses_tch_hr,2
1163
1164
1165
rf_res_ind_period
1166
roc,0
1167
roc,4,0
1168
roc,4,1
1169
roc,4,2
1170
roc,4,3
1171
roc,4,4
1172
roc,4,5
1173
roc,4,6
1174
roc,4,7
1175
roc,4,8
1176
roc,4,9
1177
roc,5,0
1178
roc,5,1
1179
roc,5,2
1180
roc,5,3
1181
roc,5,4
1182
roc,5,5
1183
roc,5,6
1184
roc,5,7
Continued
68P02900W22-R
6-145
GMR-02
Mar 2008

Element name
#
1185
roc,5,8
1186
roc,5,9
1187
routing_syntax,0
1188
routing_syntax,2
1189
routing_unknown,0
1190
routing_unknown,2
1191
rpd_offset
1192
rpd_period
1193
rpd_trigger
1194
rpt_bad_qual_no_mr
1195
rrs_timer_values,0
1196
rrs_timer_values,1
1197
rrs_timer_values,2
1198
rrs_timer_values,3
1199
rrsm_timer_value,0
1200
rrsm_timer_value,3
1201
rrsm_timer_value,5
1202
rrsm_timer_value,8
1203
rrsm_timer_value,9
1204
rrsm_timer_value,10
1205
rrsm_timer_value,11
1206
rrsm_timer_value,12
1207
rrsm_timer_value,14
1208
rrsm_timer_value,15
1209
rrsm_timer_value,16
1210
rrsm_timer_value,18
1211
rrsmpc_timer_value,0
1212
rrsmpc_timer_value,1
1213
{22586} rsl_lcf_congestion,0
1214
{22586} rsl_lcf_congestion,2
1215
rsspc_timer_values,0
1216
rsspc_timer_values,1
1217
rxlev_dl_zone
1218
rxlev_ul_zone
Continued
6-146
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1219
sabm_tx,0
1220
sccp_bssap_mgt
1221
sccp_msgs,0
1222
sccp_msgs_rx,0
1223
sccp_msgs_tx,0
1224
sdcch_congestion,0
1225
sdcch_tch_band_reassign_delay
1226
search_prio_3g
1227
second_assign_atmpt,0
1228
second_assign_suc,0
1229
secondary_freq_type
1230
{22879}serving_band_reporting
1231
sif_sio_rx_opc,0
1232
sif_sio_tx_dpc,0
1233
sif_sio_type,0
1234
sl_congestion,0
1235
sl_congestion,2
1236
sl_stop_congestion,0
1237
slip_loss_daily
1238
slip_loss_hourly
1239
slip_loss_oos
1240
slip_loss_restore
1241
smg_gb_vers
1242
sms_dl_allowed
1243
sms_init_on_sdcch,0
1244
sms_init_on_sdcch_ho_in,0
1245
sms_init_on_tch,0
1246
sms_no_bcast_msg,0
1247
sms_tch_chan
1248
sms_ul_allowed
1249
ss7_mode
1250
ssm_critical_overload_threshold
1251
ssm_normal_overload_threshold
1252
ssmpc_timer_value,0
Continued
68P02900W22-R
6-147
GMR-02
Mar 2008

Element name
#
1253
ssmpc_timer_value,1
1254
ssmpc_timer_value,2
1255
ssp_burst_delay
1256
ssp_burst_limit
1257
stat_interval
1258
static_sync_timer
1259
sw_ts_less_one_carrier
1260
switch_gprs_pdchs
1261
sync_loss_daily
1262
sync_loss_daily_pcu
1263
sync_loss_hourly
1264
sync_loss_hourly_pcu
1265
sync_loss_oos
1266
sync_loss_oos_pcu
1267
sync_loss_restore
1268
sync_loss_restore_pcu
1269
sync_time_oos
1270
sync_time_oos_pcu
1271
sync_time_restore
1272
sync_time_restore_pcu
1273
t_avg_t
1274
t_avg_w
1275
{22577}tbf_dl_asgn_pacch,0
1276
{22577}tbf_rel_pacch_lost,0
1277
tbf_sessions,0
1278
tch_busy_critical_threshold
1279
tch_busy_norm_threshold
1280
tch_cong_inner_zone,0
1281
1282
1283
tch_congest_prevent_thres
1284
tch_congestion,0
1285
tch_congestion_hr,0 (from 1760)
1286
tch_congestion_hr_amr,0 (in 1740)

Continued
6-148
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1287
tch_delay,0
1288
tch_delay,4,0
1289
tch_delay,4,1
1290
tch_delay,4,2
1291
tch_delay,4,3
1292
tch_delay,4,4
1293
tch_delay,4,5
1294
tch_delay,4,6
1295
tch_delay,4,7
1296
tch_delay,4,8
1297
tch_delay,4,9
1298
tch_delay,5,0
1299
tch_delay,5,1
1300
tch_delay,5,2
1301
tch_delay,5,3
1302
tch_delay,5,4
1303
tch_delay,5,5
1304
tch_delay,5,6
1305
tch_delay,5,7
1306
tch_delay,5,8
1307
tch_delay,5,9
1308
tch_ow_control
1309
tch_full_need_low_water_mark
1310
{24347}tch_preempt_atmpt,0
1311
1312
1313
{24347}tch_preempt_fail_timeout,0
1314
{24347}tch_preempt_no_q_alloc
1315
{24347}tch_preempt_rqd,0
1316
tch_q_length,0
1317
tch_q_length,4,0
1318
tch_q_length,4,1
1319
tch_q_length,4,2
1320
tch_q_length,4,3
Continued
68P02900W22-R
6-149
GMR-02
Mar 2008

Element name
#
1321
tch_q_length,4,4
1322
tch_q_length,4,5
1323
tch_q_length,4,6
1324
tch_q_length,4,7
1325
tch_q_length,4,8
1326
tch_q_length,4,9
1327
tch_q_length,5,0
1328
tch_q_length,5,1
1329
tch_q_length,5,2
1330
tch_q_length,5,3
1331
tch_q_length,5,4
1332
tch_q_length,5,5
1333
tch_q_length,5,6
1334
tch_q_length,5,7
1335
tch_q_length,5,8
1336
tch_q_length,5,9
1337
tch_q_removed,0
1338
tch_usage,0
1339
tch_usage_ext_range,0
1340
tch_usage_inner_zone,0
1341
{24620}tch_usage_threshold
1342
temporary_offset
1343
threshold
1344
{23956}timer_exp_pap_conv,0
1345
timing_advance_period
1346
tlli_blk_coding
1347
total_calls,0
1348
ts_alloc_ag
1349
tsc_update_method
1350
tx_integer
1351
tx_power_cap
1352
u_ber,0
1353
u_ber,4,0
1354
u_ber,4,1
Continued
6-150
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1355
u_ber,4,2
1356
u_ber,4,3
1357
u_ber,4,4
1358
u_ber,4,5
1359
u_ber,4,6
1360
u_ber,4,7
1361
u_ber,4,8
1362
u_ber,4,9
1363
u_ber,5,0
1364
u_ber,5,1
1365
u_ber,5,2
1366
u_ber,5,3
1367
u_ber,5,4
1368
u_ber,5,5
1369
u_ber,5,6
1370
u_ber,5,7
1371
u_ber,5,8
1372
u_ber,5,9
1373
u_rxlev_dl_ih
1374
u_rxlev_dl_p
1375
u_rxlev_ul_ih
1376
u_rxlev_ul_p
1377
u_rxqual_dl_p
1378
u_rxqual_dl_p_amr_hr
1379
u_rxqual_ul_p
1380
u_rxqual_ul_p_amr_hr
1381
ul_audio_lev_offset
1382
1383
1384
1385
1386
1387
1388
Continued
68P02900W22-R
6-151
GMR-02
Mar 2008

Element name
#
1389
1390
1391
1392
1393
1394
1395
ul_busy_pdtch,0
1396
ul_busy_pdtch,4,0
1397
ul_busy_pdtch,4,1
1398
ul_busy_pdtch,4,2
1399
ul_busy_pdtch,4,3
1400
ul_busy_pdtch,4,4
1401
ul_busy_pdtch,4,5
1402
ul_busy_pdtch,4,6
1403
ul_busy_pdtch,4,7
1404
ul_busy_pdtch,4,8
1405
ul_busy_pdtch,4,9
1406
ul_busy_pdtch,5,0
1407
ul_busy_pdtch,5,1
1408
ul_busy_pdtch,5,2
1409
ul_busy_pdtch,5,3
1410
ul_busy_pdtch,5,4
1411
ul_busy_pdtch,5,5
1412
ul_busy_pdtch,5,6
1413
ul_busy_pdtch,5,7
1414
ul_busy_pdtch,5,8
1415
ul_busy_pdtch,5,9
1416
{23769}ul_egprs_backhaul_demand,0
1417
{23769}ul_egprs_backhaul_used,0
1418
{23956}ul_llc_data_volume,0
1419
{22577}ul_llc_frames,0
1420
ul_pdtch_q_length,0
1421
ul_pdtch_seizure,0
1422
Continued
6-152
68P02900W22-R
GMR-02
Mar 2008

Element name
#
1423
1424
1425
1426
ul_rlc_ack_new_blks,0
1427
ul_rlc_retx_blks,0
1428
ul_rlc_unack_new_blks,0
1429
ul_rxlev_ho_allowed
1430
ul_rxqual_ho_allowed
1431
1432
1433
1434
1435
{22879}umts_band_preferred
1436
{22879}umts_cpich_ec_no_min
1437
{22879}umts_cpich_rscp_min
1438
unequipped_circuit_allowed
1439
uplink_path_loss,0
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
Continued
68P02900W22-R
6-153
GMR-02
Mar 2008

Element name
#
1457
1458
1459
1460
uplink_sync_timer
1461
use_bcch_for_gprs
1462
use_derived_ho_power
1463
use_neighbor_pbgt_hreqave
1464
wait_for_reselection
1465
wait_indication_parameters
1466
worse_neighbor_ho
1467
zone_change_atmpt,0
1468
zone_change_suc,0
1469
zone_ho_hyst
6-154
68P02900W22-R
GMR-02
Mar 2008
RTF table
RTF table
Description of RTF table

This table contains details of the RTFs contained within the BSS area (refer to Table 6-23).
Default lename: rtf.mcd
Table 6-23 RTF table

Field Name
{22239} MCC
Field Width
Range
3 digit numeric
Mandatory
3 digit numeric
Mandatory
Status

{22239} MNC
The MNC can have an optional third digit only for PCS1900 and GSM850 systems.
LAC
6 digit numeric
Mandatory

This eld can be entered in decimal or hex.
Hex numbers are to be followed by h or preceded by 0x, for example, 1234h or 0x1234.
CI
6 digit numeric
Mandatory
The Cell identier.

This eld can be entered in decimal or hex. Hex numbers are to be followed by h or
Site Number
1 to 120
(up to 1760)
1 to 100 (from 1800)
Mandatory
The Site number, within the BSS, of the Site where this RTF is located.
First ID
0 to 23
Mandatory
0 to 11
Mandatory
First device ID of the RTF.

Second ID
Second device ID of the RTF.
Continued
68P02900W22-R
6-155
GMR-02
Mar 2008
Table 6-23 RTF table (Continued)

Field Name
Primary Path ID
Field Width
Range
Status
0 to 9
Mandatory (If site

number is not 0 and
DRI is not redundant,
else unused. Not
required for RTFs
using Dynamic
Allocation).
The Primary Path ID used in the associated RTF function.

Redundant Path
ID
0 to 9
Optional
The Redundant Path ID used in the associated RTF function.

BCCH Carrier
Boolean
Mandatory
Used for the carrier type prompt within the RTF equipage command.
0 NON_BCCH carrier
1 BCCH carrier
Frequency
Refer Frequency
Type Table below.
Mandatory if not
a BCCH carrier.
Optional if a BCCH
carrier, leave blank
to pick up value from
Cell table.
The Frequency Types are as follows:

Frequency Type
BCCH
NON-BCCH
PGSM
1 to 124
1 to 124
EGSM
1 to 124 (975 to 1023,0*)
1 to 124 or 975
to 1023,0
DCS1800
512 to 885
512 to 885
PCS1900
512 to 810
512 to 810
Used for the absolute radio freq. channel prompt within the RTF equipage command.
If the RTF is a BCCH carrier, this frequency is checked against the BCCH ARFN in the Cell
Table. If the two frequencies are different, the BCCH frequency from the Cell Table will be
used.
The channel selected for a PCS1900 cell must be within the allowed frequency blocks.
(Refer to the BSS table, PCS1900 Frequency Blocks eld).
* From 1600, BCCH Frequency may be in extension band if egsm_bcch_sd is enabled in
the Cell table.
Continued
6-156
68P02900W22-R
GMR-02
Mar 2008
Table 6-23
RTF table (Continued)
Field Name
KSW pair
Field Width
Range
Status
0 to 3
Optional (Mandatory
at non-M-Cell or
non-Horizonofce
sites, otherwise
unused).
Used for the Managing KSW Pair prompt within the RTF equipage command.
Carrier Capacity
TEXT
Mandatory.
Not required for
RTFs using Dynamic
Allocation.
Valid Range: FULL or SUB.

Used for Capacity of the Carrier prompt within the RTF equipage command.
Cell Zone
0 to 1
Optional (Required if
non-BCCH carrier).
Used for the Enter Cell Zone prompt within the RTF equipage command.
TRX Power
Reduction
(trx_pwr_red)
-1 to 21
Optional (Mandatory
if Cell Zone = 1).
Used for the Enter TRX transmit power reduction prompt within the RTF equipage command.
Extended Range
Timeslots
0 to 4
Optional
(ext_range_cell
enabled).
Used for the Enter the number of extended range timeslots allowed prompt within the RTF
equipage command.
RSL Second ID
0 to 7
Optional (Applicable
only for 16 kbps
RSL).
Used for the Enter the optional second identier for the associated RSL prompt within the
RTF equipage command.
Redundant RSL
Second ID
0 to 7
Optional (Mandatory
if both RSL Second
ID and Redundant
PATH ID elds are
dened).
Used for the Enter the second identier for the associated RSL prompt within the RTF
equipage command. This parameter is only applicable for redundant RTFs.
Continued
68P02900W22-R
6-157
GMR-02
Mar 2008
Table 6-23 RTF table (Continued)

Field Name
{26803} SDCCH
Load
Field Width
Range
0 to 8 (see below)
Status
Optional (Only valid
if Cell Zone = 0).
If the Increased SDCCH feature is unrestricted, the range is as follows:

ccch_conf
BCCH RTF
Non-BCCH RTF
0 - 7
0 - 8
0 - 7
0 - 8
0 - 6
0 - 8
0 - 5
0 - 8
0 - 4
0 - 8
Used for the Enter SDCCH load prompt within the RTF equipage command.
SDCCH
Placement
Priority
0 to 250
Optional (Only valid

if SDCCH load is non
zero).
Used for the Enter SDCCH placement priority prompt within the RTF equipage command.
Channel
Allocation
Priority
0 to 250
Mandatory
parameter in 1600.
Used for the Enter channel allocation priority prompt within the RTF equipage command.
FHI 1 to FHI 8
0 to 15, 255
Optional
Used for the Frequency Hopping Indicator prompt within the RTF equipage command.
TSC 1 to TSC 8
0 to 7
Optional if left
blank and RTF is a
BCCH carrier, value
calculated from bsic
in Cell table.
Used for the Carrier training sequence code prompt within the RTF equipage command.
pkt_radio_type
0 to 3
Optional. This
parameter is only
applicable for
EGPRS.
Used to specify the terrestrial resource capacity of an RTF.

Continued
6-158
68P02900W22-R
GMR-02
Mar 2008
Table 6-23
RTF table (Continued)
Field Name
{23769}
rtf_ds0_count
Field Width
Range
Refer Table 6-24 for

range and values.
Status
Optional. This
parameter is
prompted only when
VersaTrau feature
is purchased and
pkt_radio_type is 3.
The number of terrestrial timeslots congured for an RTF.
NOTE
While upgrading from 1740/1760 to 1800, the parameter rtf_ds0_count is set to
7 (BCCH) and 8 (NON-BCCH) RTFs, as DataGen cannot handle the change in the
number of timeslot allocations. Users are provided with a WARNING message
through Upgrader as follows:
GSR8 VersaTrau Feature can be used to reduce the number of backhaul
timeslots required to support EDGE carriers. During Upgrades to GSR8,
rtf_ds0_count will be set to 7 (BCCH) or 8 (NON_BCCH ) for a VersaTrau
RTF and the user can change this to any value between 3 to 7/8.
amr_half_rate_
enabled
0 to 1
Optional
Used to enable or disable AMR Half Rate at an RTF:

0 = disabled
1 = enabled
Allow 8k Trau
0 to 1, No or Yes
Optional (Only
valid if the
parameter is
enabled).
Used to enable or disable 8k backhaul:

0 = disabled
1 = enabled
Not prompted for if the BTS is not AMR capable or the RTF is sub-equipped.
half_rate_enabled
0 to 1
Optional
Used to enable or disable GSM Half Rate at an RTF:

0 = disabled
1 = enabled
68P02900W22-R
6-159
GMR-02
Mar 2008
Table 6-24 Range and values for rtf_ds0_count

TRAU
format
Edge
purchased
VT
purchased
BCCH
Sub
equipped
HR
enabled
8K
allowed
Range
Default
16
N/A
N/A
N/A
No
No
N/A
16
N/A
N/A
N/A
Yes
No
N/A
16
N/A
N/A
N/A
No
Yes
No
16
N/A
N/A
N/A
Yes
Yes
No
16
N/A
N/A
N/A
No
Yes
Yes
16
N/A
N/A
N/A
Yes
Yes
Yes
32
N/A
N/A
N/A
No
N/A
N/A
32
N/A
N/A
N/A
Yes
N/A
N/A
64
Yes
Yes
N/A
N/A
No
N/A
3 to 7
64
Yes
Yes
N/A
N/A
Yes
Yes
3 to 8
64
Yes
No
No
N/A
No
N/A
64
Yes
No
Yes
N/A
Yes
Yes
6-160
68P02900W22-R
GMR-02
Mar 2008
DRI table
DRI table
Description of DRI table

This table contains details of the DRIs specied in the Hardware table for the BSS area (refer
to Table 6-25).
NOTE
The DRI must have its Cage and Slot number detailed in the Hardware table Table 6-7.
Default lename: dri.mcd
Table 6-25 DRI table

Field Name
{22239} MCC
Field Width
Range
Status
3 digit numeric
Mandatory
3 digit numeric
Mandatory

{22239} MNC
LAC
6 digit numeric
Mandatory

This eld can be entered in decimal or hex. Hex numbers are to be followed by h or preceded
by 0x, for example, 1234h or 0x1234.
CI
6 digit numeric
Mandatory
The Cell identier.

This eld can be entered in decimal or hex. Hex numbers are to be followed by h or preceded
by 0x, for example, 1234h or 0x1234.
Site Number
1 to 120 (up to 1760)

1 to 100 (from 1800)
Mandatory
The Site number, within the BSS, of the Site where this DRI is located.
Continued
68P02900W22-R
6-161
GMR-02
Mar 2008
Table 6-25
DRI table (Continued)
Field Name
First ID
Field Width
Range
Status
0 to 23
Mandatory
0 to 24
Mandatory
0 to 4
Optional
First device ID of the DRI.

Second ID
Second device ID of the DRI.
Board Type
Type of DRI at non-M-CELL site:

0 Digital Radio Modied (DRIM)FOX/FMUX board at an MCELL/Horizonmacro site:
0 FOX
1 FMUX0
2 FMUX1
3 FMUX2
4 DIRECT
NOTE
Must be DIRECT for an M-Cellmicro site.
The value of Board Type is not veried in the DRI table against the
cabinet_type.
TRU Identier
0 to 6
Optional, only used

for non-M-Cell sites.
0 to 5 (MCell)
1 to 24
(Horizonofce)
Optional,
only used for
M-Cell/Horizonofce
sites.
Topcell Radio Unit identier.

TCU Port Identier
M-Cell: Transceiver Control Unit Port identier.

Horizonofce: LTU Connector number (range 1 to 24)
fm_cell_type
0 to 4 (depends on
diversity_ag)
Mandatory (Not
required at
Horizonofce sites).
Used for the fm_cell_type prompt within the DRI equipage command as follows:
Continued
6-162
68P02900W22-R
GMR-02
Mar 2008
Table 6-25
Field Name
Field Width
Range
Status
diversity_ag
fm_cell_type
Result
Non-diversity (RCUs only)
Use branch 1 of a DRCU in a

non-diversity mode
Use branch 2 of a DRCU in a

non-diversity mode
Shared diversity
Full diversity
Diversity
Boolean
Mandatory (Not
required at
Horizonofce sites).
Used for the diversity ag prompt within the DRI equipage command.
0
No diversity
Diversity (requires
a DRCU)
Antenna number
1 to 6
Mandatory (Not
required at
Horizonofce sites).
Used for the antenna select number prompt within the RTF equipage command.
NOTE
Antenna number has no cabinet dependencies before the 1740 release. From 1740,
this parameter is valid for the following cabinets only:
MCell6 (cab type 11)
TCU6 (cab type 13)
HORIZONMACRO (cab type 18)
HORIZONMACRO EXT (cab type 19)
HORIZONMACRO2 (cab type 24)
HORIZONMACRO2 EXT (cab type 25)
HORIZON2 MINI (cab type 26)
HORIZON2 MINI EXT (cab type 27)
Assigned RTF rst

ID
0 to 5
Optional
First device ID of the RTF to assign to this DRI.

Continued
68P02900W22-R
6-163
GMR-02
Mar 2008
Table 6-25
Field Name
Assigned RTF
second ID
Field Width
Range
Status
0 to 24
Optional
0 to 1
Mandatory at
Horizonofce sites.
0 to 1
Optional.
Only valid at
Horizonofce sites.
Second device ID of the RTF to assign to this DRI.

Opto Alarm State
Species the number alarm state for the Optocoupler:

Number
Alarm status
Normally closed
Normally open
Opto Alarm
Reporting
Indicates whether or not the alarm is reported when the Optocoupler enters the alarm state.
Opto Alarm Index
0 to 33
Mandatory at
Horizonofce sites.
Species the alarm string displayed when an alarm is reported for the Optocoupler.
Combining Type
0 to 2
Optional
Used to describe the role of this DRI in system combining:

0
1
2
Combiner Identier
None or Hybrid
Non-Controlling
Controlling
2
0 to 13
Optional
Valid for 1620 onwards and used to reference the associated combiner for this DRI.
Cavity Number
0 to 5
Optional
Valid for 1620 onwards and used to reference the associated combiner for this DRI.
dri_density
1 to 2
Optional
DRI density 2 is allowed only for HORIZON, HORIZONMACRO, HORIZONMACRO2,

HORIZONMACRO2_EXT cabinets.
Assoc_dri_id
0 to 11
Mandatory when
dri_density is 2.
DRI density 2 is allowed only for HORIZON, HORIZONMACRO, HORIZONMACRO2,

HORIZONMACRO2_EXT cabinets.
6-164
68P02900W22-R
GMR-02
Mar 2008
Algorithm data table
Algorithm data table
Description of Algorithm data table

Table 6-26 species the algorithm data to be used across the BSS area. These entries do not
use the lac and ci elds.
It also allows the user to specify specic algorithm data for specic cells identied by their lac
and ci. These entries specify the lac and ci for the cell to which the specic algorithm data
applies and do not stop the cell picking up all the other standard algorithm entries for the
remaining algorithms or indexes into algorithms.
Default lename: alg.mcd
Table 6-26 Algorithm data table

Field Name
Algorithm Name
Field Width
Range
Status
30
Text
Mandatory
This eld identies the Algorithm Data set to update the following:
surround_cell
rel_tim_adv
rxlev_dl_ho
rxlev_dl_pc
rxlev_ul_ho
rxlev_ul_pc
rxqual_dl_ho
rxqual_dl_pc
rxqual_ul_ho
rxqual_ul_pc
interfer_alg
Continued
68P02900W22-R
6-165
GMR-02
Mar 2008
Table 6-26 Algorithm data table (Continued)

Field Name
Algorithm ID
Field Width
Range
Status
0 to 3
Mandatory if
Algorithm Name is
not interfer_alg,
otherwise unused.
This eld gives the value for the algorithm ID/bin number eld.
1
Algorithm Number
0 to 1
Mandatory
This eld gives the value for the algorithm number eld.
3
Algorithm Data
0 to 255
Mandatory
This eld gives the value for the algorithm data eld (for 1.6.1.3 and 1.6.2.0).
2
Index
0 to 32
Mandatory
This eld gives the value for the algorithm index eld (for 1.6.1.3 and 1.6.2.0).
0
index for Hreqave.
index for Hreqt.
index for qual_weight.
index for
qual_power_ag.
index for
qual_margin_ag.
index for
neigh_protect_ag.
index for
adj_qual_margin.
7 - 31
reserved for future

use.
hreqave
1 to 31
Optional
1 to 31
Optional
0 to 255
Optional
3 digit numeric
Mandatory
3 digit numeric
Mandatory
Only valid for 1.6.5.0.

hreqt
w_qual
{22239} MCC
{22239} MNC
Continued
6-166
68P02900W22-R
GMR-02
Mar 2008
Table 6-26 Algorithm data table (Continued)

Field Name
LAC
Field Width
Range
Status
6 digit numeric
Optional
The Location Area Code. This eld can be entered in decimal or hex. Hex numbers will be
followed by h or preceded by 0x, for example, 1234h or 0x1234.
Location area code of cell to which this algorithm data is to be specically applied.
CI
6 digit numeric
Optional (mandatory
if the LAC eld is
specied).
The Cell identier. This eld can be entered in decimal or hex form. Hex numbers will be
Cell Identity of cell to which this algorithm data is to be specically applied.
To display only generic algorithm details for cells with no MCC, MNC, LAC, and CI details
specied, refer to Table 6-27.
68P02900W22-R
6-167
GMR-02
Mar 2008
Neighbor table
Neighbor table
Description of Neighbor table

This table identies the cell pairs network-wide, using the bss_id to identify the BSS area
containing the cell marked as the source. Refer to Table 6-27. The bsic and bcch frequency are
detailed in the cell table. The elds classed as optional may contain values overriding those
specied in the cell table.
Default lename: ngbr.mcd
Table 6-27 Neighbor table

Field Name
BSS ID
Field Width
Range
0 to 255
Mandatory
3 digit numeric
Mandatory
3 digit numeric
Mandatory
Status
The bss_id of the BSS the source cell is in.

{22239} Source
MCC
The Mobile Country Code of the source.

{22239} Source
MNC
The Mobile Network Code of the source.

Source LAC
6 digit numeric
Mandatory
The location Area Code of the source. This eld can be entered in decimal or hex form. Hex
numbers will be followed by h or preceded by 0x, for example, 1234h or 0x1234.
Source CI
6 digit numeric
Mandatory
The cell identier of the source. This eld can be entered in decimal or hex form. Hex
{22239} Neighbor
MCC
3 digit numeric
Not required for blind search

neighbors, mandatory for non
blind search neighbors.
The Mobile Country Code of the Neighbor.

Continued
6-168
68P02900W22-R
GMR-02
Mar 2008
Table 6-27 Neighbor table (Continued)

Field Name
{22239} Neighbor
MNC
Field Width
Range
3 digit numeric
Status
Not required for blind search
neighbors, mandatory for non
blind search neighbors.
The Mobile Network Code of the neighbor.

The location area code of the neighbor. This eld can be entered in decimal or hex form. Hex
Neighbor LAC
6 digit numeric
Mandatory
Neighbor RNC Id
4 digit numeric
Mandatory, if a UMTS neighbor.
Neighbor CI
6 digit numeric
Mandatory
The location area code of the neighbor. This eld can be entered in decimal or hex form. Hex
Sync
Boolean
Used to determine if the handovers between the cells are synchronized or not.
Pre 1.5.0.0
From BSS 1.5.0.0
Coincident Cell
Not synchronized
Synchronized
no
Not synchronized
yes
Synchronized
0 to 2
Optional. Only applies to

internal neighbors.
Used for element: coincident_mb parameter of the chg_cell_element command as follows:

0
Coincident Multiband is disabled at the cell.
Coincident Multiband utilizes better cell detection.
Coincident Multiband utilizes coincident cell redirection.
This will enable coincident Multiband at the source cell, not the neighboring cell.
Both neighbors must be within the same site if set to 2. If not within the same site, the value
must be set to 1, must be synchronized and must be neighbors of one another.
ho_margin_cell
-24 to 31
Optional for both external and

internal neighbors.
Used for element: ho_margin_cell

If this no value is entered here the ho_margin_def value for the source will be used.
rxlev_min_cell
0 to 63
Optional for both external and

internal neighbors.
Used for element: rxlev_min_cell

If no value is entered here the rxlev_min_def value will be used.
Continued
68P02900W22-R
6-169
GMR-02
Mar 2008

Field Name
Field Width
Range
ms_txpwr_max_cell
0 to 43
Status
Mandatory if the neighbor cell
is external to BSS ID, not used
if neighbor is internal.
Range for GSM 900 and GSM 900 Extended = 5-43. Odd values only.
Range for DCS 1800 and PCS1900 = 0-30. Even values only.
Used for element: ms_txpwr_max_cell
If this element is entered, it overrides the value extracted from the cell table.
BA List Type
10
Text (valid strings

listed below).
Optional
Used for the add_neighbor parameter: ba_list_type

Valid text strings:
ba_bcch
Place the neighbor in the ba_bcch list.
ba_sacch
Place the neighbor in the ba_sacch list.
both
Place the neighbor in both the ba_bcch and ba_sacch lists.
empty eld
Place the neighbor in both the ba_bcch and ba_sacch lists.
Valid for 1.6.1.3 and 1.6.2.0 only.

BA BCCH List Type
Yes or No
Optional
The BA BCCH List Type should be set to Yes if the BA SACCH and BA GPRS List Types
are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA BCCH List (yes/no)?
BA SACCH List Type
Yes or No
Optional
The BA SACCH List Type must be set to Yes if the BA BCCH and BA GPRS List Types
are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA SACCH List (yes/no)?
BA GPRS List Type
Yes or No
Optional
The BA GPRS List Type must be set to Yes if the BA BCCH and
BA SACCH List Types are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA GPRS List (yes/no)?
Power Budget
hreqave
1 to 31
Optional. BSS Microcellular

option purchased.
Used for the add_neighbor prompted parameter: Power budget surround cell hreqave.
Power Budget
Algorithm Type
1 to 7

option purchased.
Used for the add_neighbor prompted parameter: Power budget algorithm type.
Continued
6-170
68P02900W22-R
GMR-02
Mar 2008

Field Name
Interfering
Frequency
Field Width
Range
Boolean
Status
Optional. Only applicable
where Concentric
Cells option purchased
AND inner_zone_alg is set
to interference for source cell
AND the neighbor is being
added to the SACCH list.
Used for the add_neighbor prompt: Does this neighbor have a carrier with an
interfering frequency?
Inner Zone
Handover
Threshold
0 to 63
Optional. Only applicable if

Interfering Frequency is yes.
Used for the add_neighbor prompt: Enter the threshold for inner zone handover.
Inner Zone
Handover Margin
0 to 63
Optional. Only applicable if

Interfering Frequency is yes.
Used for the add_neighbor prompt: Enter the margin for inner zone handover.
Uplink rxlev
(serving cell)
Range:
See below

option purchased AND power
budget algorithm type is 3.
Pre 1600:
0-63
From 1600:
0-255
Used for the add_neighbor prompted parameter: Uplink rxlev of serving cell.
Downlink rxlev
(serving cell)
Range:
See below

Pre 1600:
0-63
From 1600:
0-255
Used for the add_neighbor prompted parameter: Downlink rxlev of serving cell.
Qualifying Time
0 to 255

Used for the add_neighbor prompted parameter: Qualifying time.

Qualifying Delay
Time
0 to 255

Used for the add_neighbor prompted parameter: Qualifying delay time.

Continued
68P02900W22-R
6-171
GMR-02
Mar 2008

Field Name
Field Width
Range
Neighbor Cell rxlev

Threshold
0 to 63
Status
Used for the add_neighbor prompted parameter: Neighbor cell rxlev threshold.
Delay Time
0 to 255

Used for the add_neighbor prompted parameter: Delay time.

Handover Static
Offset
0 to 127

Used for the add_neighbor prompted parameter: Handover static offset.

Handover Dynamic
Offset
0 to 127

Used for the add_neighbor prompted parameter: Handover dynamic offset.

Congestion
Handover Margin
-63 to 63
Optional. BSS Directed Retry

option OR Alternate Congestion
Relief option purchased AND
neighbor is placed on a SACCH
list.
Used for the add_neighbor prompted parameter: Neighbor congestion handover margin.
Directed Retry
Allowed
yes or no
Optional. BSS Directed

Retry option purchased AND
neighbor is placed on a SACCH
list AND neighbor is external.
Used for the add_neighbor prompt: Is directed retry allowed at this external
neighbor cell.
Adj Chan Intf Test
yes or no
Optional. From 1500 AND

BSS Directed Retry option
purchased.
Used for the add_neighbor prompt: Enable channel interference avoidance test.
Rxlev Diff Adj Chan
Intf Avoid
-63 to 63
Optional. From 1500

AND Micro-Cellular option
purchased AND Channel
Interference Avoidance has a
value of 1.
Used for the add_neighbor prompt: Rxlev difference for channel interference
avoidance test.
Continued
6-172
68P02900W22-R
GMR-02
Mar 2008

Field Name
Adj Channel Intf
HO Det Margin
Field Width
Range
-63 to 63
Status
Optional. From 1500
AND Micro-Cellular option
purchased AND Power Budget
Algorithm Type has a value of
7).
Used for the add_neighbor prompted parameter: Adjacent channel interference

handover detection margin.
Neighbor Range
Text EXTENDED
or NORMAL
Optional. Only applicable when

extended range cell option
purchased AND ext_range_cell
is enabled.
Used for the neighbor_range element of the add_neighbor command to allow the range to
be extended or normal range per neighbor.
Handover Margin
rxqual
-63 to 63
Optional
Used for the ho_margin_rxqual element of the modify_neighbor command.

Handover Margin
rxlev
-63 to 63
Optional
Used for the ho_margin_rxlev element of the modify_neighbor command.

Handover Margin
Type5
-63 to 63
Optional
Used for the ho_margin_type5 element of the modify_neighbor command.

Neighbor PBGT
0 to 255
Optional
The recommended value is 40. This parameter (adap_trigger_pbgt_nbr) species the

cumulative trigger level for the adaptive hand over power budget algorithm. When the
threshold is exceeded, the system triggers a hand over to a better cell.
fdd_arfcn
10562 to 10838
Mandatory, if a UMTS
Neighbor.
Scrambling Code
0 to 511
Neighbor.
Diversity Enabled
0 to 1
Neighbor.

Continued
68P02900W22-R
6-173
GMR-02
Mar 2008

Field Name
{22879} Umts
Measurement
Margin
Field Width
Range
0 to 20.
Default: 3
Status
Optional. This is a prompt for
the add_neighbor command.
If a value is not specied
for this parameter, then the
default value is used. It
can be modied using the
modify_neighbor command
only when the 2G/3G hand over
feature is unrestricted.
Measurement parameter used by hand over algorithm.

{22879} Umts NCell
Avg Period
1 to 12
Default: 6
Optional. This is a prompt

for add_neighbor command.
If a value is not specied
for this parameter, then
the default value is used.
It can be modied using
modify_neighbor command
only when 2G/3G hand over
feature is unrestricted.
Neighbor averaging period measured in SACCH multiframes.

{22879} UMTS
BCCH List Type
Yes or No.
Default: Yes
Optional. This is an
add_neighbor command
prompt which is not prompted
when the Enhanced 2G/3G
feature is restricted.
Yes or No.
Default: Yes
Optional. This is an
add_neighbor command
prompt which is not prompted
when the Enhanced 2G/3G
feature is restricted.
10562 to 10838
Default: N/A
Mandatory for creating blind

search neighbor using the
add_neighbor command with
a placement type of umts_fdd.
Used for add_neighbor.

{22879} UMTS
SACCH List Type
Used for add_neighbor.

{22879} Blind
Search FDD Arfcn
Used for specifying fdd_arfcn value for blind search neighbor.
6-174
68P02900W22-R
GMR-02
Mar 2008
Throttles table
Throttles table
Description of Throttles table

The Throttles table species throttles to be applied to device types for the whole BSS area and
links them to alarm numbers. Refer to Table 6-28.
Default lename: thro.mcd
Table 6-28
Throttles table
Field Name
Field Width
Range
Status
Text
Mandatory
0 to 254
Mandatory
0 to 1440
Mandatory
Device Name
The name of one of the following devices:

DRI
GCLK
KSW
MMS
LMTL
MTL
RSL
XBL
GSL
Alarm Index
Species the alarm number for the throttle.

Throttle Value
Species the throttle value.
68P02900W22-R
6-175
GMR-02
Mar 2008
EAS table
EAS table
Description of EAS table

The EAS table is used to specify alarm strings for alarm numbers used with the BSS area.
Refer to Table 6-29.
Default lename: eas.mcd
Table 6-29 EAS table

Field Name
Alarm Index
Field Width
Range
Status
0 to 33
Mandatory
This eld is used to identify the alarm number to give the string.
EAS Severity
0 to 4
Mandatory
This eld is used as the severity number of this EAS alarm.

Alarm String
Text
24
Mandatory
This eld is used as the string equipped against this EAS alarm number.
6-176
68P02900W22-R
GMR-02
Mar 2008
Daughter table
Daughter table
Description of Daughter table

This table is used to specify the half height cards at a site in the same way as the hardware table
(Table 6-7) species the full height cards at a site, as described in Table 6-30.
Default lename: dgtr.mcd
Table 6-30 Daughter table

Field Name
Field Width
Range
Status
0 to 120
(up to 1760)
0 to 100 (from
1800)
Mandatory
0 to 15
Mandatory
0 to 15
Optional (Mandatory at
otherwise unused).
0 to 28
Optional (Mandatory at
otherwise unused).
Text
Mandatory
0 to 255 (Valid
range depends
on device).
Mandatory
Site Number
The Site number of the device.

Cabinet ID
The CAB ID of the device.
Cage Number
The CAGE ID of the device.

Slot Number
The slot number of the device.

Device Name
The name of this device.
Device ID
The ID of this device. At present only one device can be put here.
NAME
Non-M-CELL EAS
M-CELL EAS
RANGE
0-7
0-15 (must be the same as the Cabinet ID)
68P02900W22-R
6-177
GMR-02
Mar 2008
PIX table
PIX table
Description of PIX table

The PIX table species the hardware circuits which activate specic alarms in an EAS device
as in Table 6-31.
Default lename: pix.mcd
Table 6-31 PIX table

Field Name
Site Number
Field Width
Range
Status
0 to 120
(up to 1760)
0 to 100 (from
1800)
Mandatory
The Site number for this EAS device. This is set in the Daughter table.
Device ID
0 to 15
Mandatory
Device ID of the EAS device. This is set in the Daughter table.

Opto Number
1 to 16
Mandatory
This eld is used to select the Opto Number to congure.

The range is as follows:
M-cell site
Non-M-cell site
Off State
1 to 16
1 to 8
1
Boolean
Mandatory
This eld determines the default off state for the Opto (Optocoupler).
Initial Setting
Boolean
Mandatory
This eld is used to congure the initial settings of the relays. There are only four relays for
the number of Optos (8 Optos for a non-M-Cell EAS, 16 Optos for an M-Cell EAS).
Alarm Index
0 to 33 or MPF
Mandatory
MPF represents the main power failure alarm. This eld indicates which alarm string to use
from the EAS table.
Report Changes
Y or N ([Y]es or
[N]o)
Mandatory
This eld is used to decide whether to report the state changes (send alarm) for the specied
Opto Number.
6-178
68P02900W22-R
GMR-02
Mar 2008
KSW table
KSW table
Description of KSW table

The KSW table species the data for the KSW conguration commands (chg_ksw_cong)
as in Table 6-32. This table has entries only for sites that implement expanded KSW cards.
Also, this table contains the entries that differ from the default values (generated within the
BSS and BTS tables) only.
NOTE
This command is invalid at M-Cell sites and will not be generated for these sites.
Default lename: ksw.mcd
Table 6-32
Field Name
Site Number
KSW table
Field Width
Range
Status
0 to 120
(up to 1760)
0 to 100 (from
1800)
Mandatory
0 to 3
Mandatory
The Site number within the BSS.

KSW pair
The KSW pair within a cage (corresponds to the Highway number that the KSW pair manages).
Highway 0
0 to 3
Mandatory
The KSWX card that handles TDM Highway 0.

This can be any of the following values:
0
Highway is managed by the current

KSW pair
EXP KSWX A0
EXP KSWX A1
EXP KSWX A2
Highway 1
0 to 3
Optional (Value must be

entered for Highway 0).

Continued
68P02900W22-R
6-179
GMR-02
Mar 2008
Description of KSW table
Table 6-32 KSW table (Continued)

Field Name
Field Width
Range
Status
Highway 2
0 to 3

0 to 3


Highway 3
6-180
68P02900W22-R
GMR-02
Mar 2008
NSVC table
NSVC table
Description of NSVC table

The NSVC table is used to specify the parameters for any add_nsvc commands as in Table 6-33.
Default lename: nsvc.mcd
Table 6-33
NSVC table
Field Name
Field Width
Range
Status
Location
251 to 253
Mandatory
This eld species the location of the PCU at which mapping between the Network
Service-Virtual Connection Identier (NSVCI) and Data Link Connection Identier (DLCI) to
a specic GBL is enabled.
NSVCI
0 to 65535
Mandatory
This eld is used to identify the Network Service Virtual Connection ID on a GBL.
{22461} GBL Id
0 to 3
Mandatory
This eld is used to specify the ID of the associated GBL.

DLCI
16 to 991
Mandatory
This eld is used to specify the Data Link Connection Identier.

FR Committed Info
Rate
0 to 1984
Mandatory
This eld is used to specify the Frame Relay committed information rate.
FR Burst Size
0 to 1984
Mandatory
This eld is used to specify the Frame Relay burst size.

FR Burst Excess
0 to 1984
Mandatory
This eld is used to specify the Frame Relay burst excess.
68P02900W22-R
6-181
GMR-02
Mar 2008
Hop table
Hop table
Description of Hop table

The Hop table is used to specify the parameters of the chhg_hop_params command as in
Table 6-34.
Default lename: hop.mcd
Table 6-34
Hop table
Field Name
Field Width
Range
Status
1 to 120
(up to
1760)
1 to 100
(from
1800)
Mandatory
Site Number
Used to identify the site at which the specic value is required.

{22239} MCC
3 digit
numeric
Mandatory
3 digit
numeric
Mandatory

{22239} MNC
LAC
6 digit
number
Mandatory

This eld can be entered in decimal or hex. Hex numbers are to be followed by h
or preceded by 0x, for example, 1234h or 0x1234.
CI
6 digit
number
Mandatory.
The Cell Identier can be entered in decimal or hex form. Hex numbers are to be
Hopping FHI
0 to 3
Mandatory
Hopping system (FHI) for a cell.

Continued
6-182
68P02900W22-R
GMR-02
Mar 2008
Table 6-34 Hop table (Continued)

Field Name
Field Width
Range
Status
0 to 1023
Mandatory
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
Hopping Frequency 0
Mobile allocation ARFCN for FHI.
Hopping Frequency 1
Hopping Frequency 2
Hopping Frequency 3
Hopping Frequency 4
Hopping Frequency 5
Hopping Frequency 6
Hopping Frequency 7
Hopping Frequency 8
Hopping Frequency 9
Hopping Frequency 10
Continued
68P02900W22-R
6-183
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
Continued
6-184
68P02900W22-R
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
Continued
68P02900W22-R
6-185
GMR-02
Mar 2008

Field Name
Field Width
Range
Status
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
0 to 1023
Optional
6-186
68P02900W22-R
GMR-02
Mar 2008
ACS table
ACS table
Description of ACS table

The Active Codec Set (ACS) table is used to specify the parameters for any chg_acs_params
commands as in Table 6-35.
Default lename: acs.mcd
Table 6-35 ACS table

Field Name
Site Number
Field Width
Range
Status
1 to 120
(up to 1760)
1 to 100 (from
1800)
Mandatory
This eld is used to identify the site at which the specic value is required.
{22239} MCC
3 digit numeric
Mandatory
3 digit numeric
Mandatory

{22239} MNC
LAC
6 digit numeric
value
Mandatory

This eld can be entered in decimal or hex. Hex numbers are to be followed by h or
CI
6 digit numeric
value
Mandatory
The Cell identier can be entered in decimal or hex form. Hex numbers are to be followed by
h or preceded by 0x, for example, 1234h or 0x1234.
3
Acs Mode
0 to 2
Mandatory
This parameter species the rate:

0
Full Rate
Half Rate
Both Rates
Continued
68P02900W22-R
6-187
GMR-02
Mar 2008
Table 6-35 ACS table (Continued)

Field Name
AMR FR ACS,1
Field Width
Range
Status
0 to 6
Mandatory. Prompted for if

the AMR feature has been
purchased, the BTS type is AMR
capable, and the mode specied
on the command line is 0 or 2.
AMR codec mode that can be used for any given voice call in the uplink or downlink direction.
AMR FR ACS,2
0 to 6

AMR FR ACS,3
0 to 6

AMR FR ACS,4
0 to 6

AMR FR Init Codec
Mode
0 to 6
Mandatory. Prompted for if the

Active Codec Set contains more
than one codec mode.
The Codec Mode used at the beginning of a call. If one mode is entered for the FR ACS, then
the FR Initial Codec Mode defaults this mode (if valid).
AMR FR Uplink
Threshold,1
0 to 63

ACS contains more than one
codec mode.
Lower Full-Rate uplink decision threshold for switching from one mode to another.
AMR FR Uplink
Threshold,2
0 to 63

codec mode.
AMR FR Uplink
Threshold,3
0 to 63

codec mode.
Continued
6-188
68P02900W22-R
GMR-02
Mar 2008

Field Name
AMR FR Uplink
Hystersis,1
Field Width
Range
Status
0 to 15

codec mode.
The sum of the associated threshold and hysteresis used as the upper decision threshold for
switching the codec mode.
AMR FR Uplink
Hystersis,2
0 to 15

codec mode.
AMR FR Uplink
Hystersis,3
0 to 15

codec mode.
AMR FR Downlink
Threshold,1
0 to 63

codec mode.
Lower Full-Rate downlink decision threshold for switching from one mode to another.
AMR FR Downlink
Threshold,2
0 to 63

codec mode.
AMR FR Downlink
Threshold,3
0 to 63

codec mode.
AMR FR Downlink
Hystersis,1
0 to 15

codec mode.
AMR FR Downlink
Hystersis,2
0 to 15

codec mode.
Continued
68P02900W22-R
6-189
GMR-02
Mar 2008

Field Name
AMR FR Downlink
Hystersis,3
Field Width
Range
Status
0 to 15

codec mode.
AMR FR Uplink Thresh
Hop,1
0 to 63

codec mode.
Uplink switching threshold applied to frequency hopping channels.

Hop2
0 to 63

codec mode.

Hop,3
0 to 63

codec mode.

AMR FR Uplink Hyst
Hop,1
0 to 15

codec mode.
Uplink hysteresis applied to frequency hopping channels.

AMR FR Uplink Hyst
Hop,2
0 to 15

codec mode.

AMR FR Uplink Hyst
Hop,3
0 to 15

codec mode.

AMR FR Downlink
Thresh Hop,1
0 to 63

codec mode.
Downlink switching threshold applied to frequency hopping channels.

AMR FR Downlink
Thresh Hop,2
0 to 63

codec mode.

Continued
6-190
68P02900W22-R
GMR-02
Mar 2008

Field Name
AMR FR Downlink
Thresh Hop,3
Field Width
Range
Status
0 to 63

codec mode.

AMR FR Downlink Hyst
Hop,1
0 to 15

codec mode.
Downlink hysteresis applied to frequency hopping channels.

Hop,2
0 to 15

codec mode.

Hop,3
0 to 15

codec mode.

AMR HR ACS,1
2 to 6

AMR HR ACS,2
2 to 6

AMR HR ACS,3
2 to 6

AMR HR ACS,4
2 to 6

Continued
68P02900W22-R
6-191
GMR-02
Mar 2008

Field Name
AMR HR Init Codec
Mode
Field Width
Range
Status
2 to 6

codec mode.
This is the Codec Mode used at the beginning of a call. If one mode is entered for the HR ACS,
then the HR Initial Codec Mode defaults to this mode (if valid).
AMR HR Uplink
Threshold,1
0 to 63

codec mode.
Lower half rate decision threshold for switching from one mode to another.
AMR HR Uplink
Threshold,2
0 to 63

codec mode.
AMR HR Uplink
Threshold,3
0 to 63

codec mode.
AMR HR Uplink
Hystersis,1
0 to 15

codec mode.
AMR HR Uplink
Hystersis,2
0 to 15

codec mode.
AMR HR Uplink
Hystersis,3
0 to 15

codec mode.
AMR HR Downlink
Threshold,1
0 to 63

codec mode.
AMR HR Downlink
Threshold,2
0 to 63

codec mode.
Continued
6-192
68P02900W22-R
GMR-02
Mar 2008

Field Name
AMR HR Downlink
Threshold,3
Field Width
Range
Status
0 to 63

codec mode.
AMR HR Downlink
Hystersis,1
0 to 15

codec mode.
AMR HR Downlink
Hystersis,2
0 to 15

codec mode.
AMR HR Downlink
Hystersis,3
0 to 15

codec mode.
AMR HR Uplink Thresh
Hop,1
0 to 63

codec mode.

Hop,2
0 to 63

codec mode.

Hop,3
0 to 63

codec mode.

AMR HR Uplink Hyst
Hop,1
0 to 15

codec mode.

AMR HR Uplink Hyst
Hop,2
0 to 15

codec mode.

Continued
68P02900W22-R
6-193
GMR-02
Mar 2008

Field Name
AMR HR Uplink Hyst
Hop,3
Field Width
Range
Status
0 to 15

codec mode.

AMR HR Downlink
Thresh Hop,1
0 to 63

codec mode.

AMR HR Downlink
Thresh Hop,2
0 to 63

codec mode.

AMR HR Downlink
Thresh Hop,3
0 to 63

codec mode.

AMR HR Downlink
Hyst Hop,1
0 to 15

codec mode.

AMR HR Downlink
Hyst Hop,2
0 to 15

codec mode.

AMR HR Downlink
Hyst Hop,3
0 to 15

codec mode.
6-194
68P02900W22-R
GMR-02
Mar 2008
Test Neighbor table
Test Neighbor table
{27127}
Description of the Test Neighbor table

Table 6-36 contains test neighbor details. Test neighbors are used by operators to optimize their
cellular network. The test neighbor allows the cell to add frequencies to the bcch allocation
list without having that frequency considered for a hand over.
Default lename: testngbr.mcd
Table 6-36 Test Neighbor table

Field Name
Source MCC
Field Width
Range
Status
3 digit numeric
value
Mandatory
3 digit numeric
value
Mandatory
The Source Mobile Country Code.

Source MNC
The Source Mobile Network Code.

The Source MNC can have an optional third digit only for PCS1900 and GSM850
systems.
Source LAC
6 digit numeric
value
Mandatory
The Source Location Area Code.

This eld can be entered in decimal or hex. Hex numbers are to be followed by
h or preceded by 0x, for example, 1234h or 0x1234.
Source CI
6 digit numeric
value
Mandatory
The Source Cell Identier can be entered in decimal or hex form. Hex numbers
are to be followed by h or preceded by 0x, for example, 1234h or 0x1234.
Neighbor Test Id
1 to 64
Mandatory
Unique ID used to distinguish one Test Neighbor from another Test Neighbor.
BA BCCH List Type
3
Text
Yes or No
Mandatory
The BA BCCH List Type must be set to Yes if the BA SACCH and
BA GPRS List Types are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbour to the BA BCCH List
(yes/no)?
Continued
68P02900W22-R
6-195
GMR-02
Mar 2008
Description of the Test Neighbor table
Table 6-36 Test Neighbor table (Continued)

Field Name
BA SACCH List
Type
Field Width
Range
Status
3
Text
Yes or No
Mandatory
The BA SACCH List Type must be set to Yes if the BA BCCH and
BA GPRS List Types are set to No, otherwise MCDF Insert fails.
(yes/no)?
BA GPRS List Type
Yes or No
3
Text
Mandatory. Prompted
if NCCR purchased.
The BA GPRS List Type must be set to Yes if the BA BCCH and
BA SACCH List Types are set to No, otherwise MCDF Insert fails.
(yes/no)?
Neighbor Cell
Frequency Type
1 to 8
Mandatory
0 to 1023
Mandatory
Test Neighbor Cell Frequency type.

Neighbor BCCH
Frequency Number
Test Neighbor Mobile Allocation ARFCN for FHI.
6-196
68P02900W22-R
GMR-02
Mar 2008
Index
Index
A
Administration . . . . . . . . . .
changing permissions . . . . . .
country admin. . . . . . . . . .
customising parameters. . . . .
database administration tasks .
importing CM database objects .
installing the Options Object . .
optimising the database. . . . .
viewing the log le . . . . . . .
Administration - CADM . . . . . .
Administration icon
use of . . . . . . . . . . . . . .
Audit . . . . . . . . . . . . . . .
aborting while in progress . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-11
3-12
3-26
3-15
3-19
3-25
3-16
3-13
3-14
5-36
. . . .
. . . .
. . . .
4-15
4-34
4-69
Audit (contd.)
audit logs . . . . . . . . . . . . .
from Navigation Tree . . . . . . .
inconsistency report . . . . . . .
scheduling . . . . . . . . . . . .
Audit inconsistency report . . . . .
viewing . . . . . . . . . . . . . .
Audit log management . . . . . . .
Audit logs
deleting . . . . . . . . . . . . . .
viewing . . . . . . . . . . . . . .
Auto-compile MMI script command .
Auto-Revgen command . . . . . . .
Auto-upgrader command . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-68
4-35
4-70
4-60
4-71
4-71
4-73
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-72
4-68
5-10
5-28
5-33
.
.
.
.
.
.
.
.
.
.
.
.
3-34
3-43
3-34
3-39
B
Batch processing
compile . . . . . . . . . . . . . . . . . 3-129
BSS area
conguring . . . . . . . . . . . . . . .
3-45
copying . . . . . . . . . . . . . . . . .
3-41
BSS area (contd.)

creating .
deleting .
deleting a
opening .
. . . . . . . . .
. . . . . . . . .
country/network
. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
C
Cell
nd . . . . . . . . . . . . . . . . . .
CellXchange
introduction . . . . . . . . . . . . . .
Radio Frequency planning . . . . . .
CM database objects . . . . . . . . . .
converting to a database script le . .
cmutil.olm command . . . . . . . . . .
Command line tools . . . . . . . . . . .
auto compile MMI Script (auto_com
pile) . . . . . . . . . . . . . . . . . .
auto_revgen . . . . . . . . . . . . . .
auto_upgrade . . . . . . . . . . . . .
compile MMI script (compile) . . . . .
compress binary object les (cpdb -c) .
copy area (ca) . . . . . . . . . . . . .
delete database object (del) . . . . . .
Command line tools (contd.)

.
4-23
.
.
.
.
. .
. .
4-38
4-38
3-25
3-65
4-5
5-2
.
5-10
.
5-28
.
5-33
. . 5-9
.
5-13
. . 5-5
.
5-15
general information . . . . . . . . . .
lock/unlock BSS area (lock_adm) . . .
MCDF lter (lter) . . . . . . . . . .
MMI combiner (combine) . . . . . . .
MMI command generator (gcmd) . . .
optimise DataGen database (dbac
cess) . . . . . . . . . . . . . . . . .
revgen . . . . . . . . . . . . . . . .
toggle permissions (tp) . . . . . . . .
uncompress binary object les (cpdb
-u). . . . . . . . . . . . . . . . . . .
user options . . . . . . . . . . . . . .
version upgrader (upg) . . . . . . . .
Compile multiple binary object les . . .
Compress OLM network . . . . . . . .
68P02900W22-R
Mar 2008
. . 5-3
.
5-23
.
5-17
. . 5-7
.
5-20
.
.
.
5-22
5-25
5-30
.
5-13
. . 5-3
.
5-31
. . 5-9
. 3-129
.
4-79
IX-1
GMR-02
Index

command . . . . . . . . . . . . . . . . .
Conguration management icon . . . . .
Conguring BSS area(s) . . . . . . . . .
basic BSS with TS switch - expansion . .
daisy chain conguration with TS
switch . . . . . . . . . . . . . . . . . .
functions and MCDF table relation
ships . . . . . . . . . . . . . . . . . .
Converting a script le . . . . . . . . . .
binary object compiler . . . . . . . . .
Sysgen mode . . . . . . . . . . . . . .
Copy area (ca) command . . . . . . . . .
Copy BSS binary les into OLM . . . .

Copying a BSS area from the GUI . . .
Country administration (CADM) . . .
administration les . . . . . . . . .
menus. . . . . . . . . . . . . . . .
using the xcadm GUI . . . . . . . .
Creating a BSS area . . . . . . . . .
Creating a BSS from Navigation Tree .
Creating a network
Saving a network . . . . . . . . . .
Creating a RXCDR from Navigation
Tree . . . . . . . . . . . . . . . . . .
5-13
4-15
3-45
3-47
3-52
3-45
3-111
3-111
3-111
. 5-5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-77
3-41
5-36
5-40
5-38
5-37
3-34
4-32
. . .
. .
4-6
4-32
D
Daisy chain conguration with TS
switch . . . . . . . . . . . . . . . . . . .
Database
dropping/recreating the db_dg Informix
database . . . . . . . . . . . . . . . .
reloading the Informix database . . . .
save . . . . . . . . . . . . . . . . . . .
system performance . . . . . . . . . .
usage scripts . . . . . . . . . . . . . .
verify . . . . . . . . . . . . . . . . . .
warning messages . . . . . . . . . . .
Database script les . . . . . . . . . . .
alternative text editor . . . . . . . . . .
producing . . . . . . . . . . . . . . . .
viewing . . . . . . . . . . . . . . . . .
xedit window . . . . . . . . . . . . . .
DataGen and OLM platform . . . . . . . .
DataGen database structure . . . . . . .
BSS database . . . . . . . . . . . . . .
CM database object . . . . . . . . . .
database script le . . . . . . . . . .
DataGen database structure (contd.)

3-52
.
.
.
.
.
DataGen - OMC integration . . . . .

DataGen directory structure . . . . .
sub-structure . . . . . . . . . . . .
DataGen les . . . . . . . . . . . . .
tools for editing . . . . . . . . . . .
DataGen functions . . . . . . . . . .
Defragmenting the database . . . . .
Deleting a BSS area . . . . . . . . . .
Deleting a network . . . . . . . . . .
Deleting a network/country . . . . . .
Device management
from navigation tree . . . . . . . .
Difference reporter . . . . . . . . . .
menu option. . . . . . . . . . . . .
selecting BSS area details. . . . . .
using the information window. . . .
using the report window . . . . . .
3-21
3-20
4-42
3-19
3-19
4-42
3-20
3-70
3-73
3-70
3-71
3-72
1-5
1-7
1-7
1-7
1-7
.
.
.
.
.
.
.
.
.
.
.
. . 1-7
.
1-11
.
1-13
.
3-76
.
3-76
. . 1-2
.
3-13
.
5-15
.
3-43
.
4-53
.
3-32
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-37
3-117
3-10
3-118
3-120
3-121
E
Environment variables
automate RevGen . . . . . . . . . . .
dening . . . . . . . . . . . . . . . .
display generic details in alg.mcd table
export path . . . . . . . . . . . . . .
import path . . . . . . . . . . . . . .
output to script . . . . . . . . . . . .
override lock . . . . . . . . . . . . .
setenv command . . . . . . . . . . .
setting from the GUI . . . . . . . . .
Environment variables (contd.)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-5
3-4
3-8
3-6
3-6
3-8
3-7
3-4
3-11
text editor. . . . . .
time slot order . . .
version order . . . .
Exiting the OLM GUI .
Expanded BSS with TS
Expanding the network
Expert desktop option.
Exporting object les .
IX-2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-7
3-5
3-5
4-12
3-47
4-55
4-17
3-114
68P02900W22-R
GMR-02
Mar 2008
Index
F
feature
22076 . . . . . . . . . . . . . . . . . .
6-43
22100 . . . . . . . . 6-91, 6-100, 6-102, 6-106
22239 . . . . . . . . . . . 6-67, 6-155, 6-161,
6-166, 6-168 to 6-169, 6-182, 6-187
22404 . . . . . . . . . . . . . . . 6-35, 6-81,
6-85, 6-113, 6-117 to 6-118, 6-134
22461 . . . . . . . . . . . . . . . . . . 6-181
22577 . . . . . . . . 6-88 to 6-89, 6-91, 6-100
to 6-102, 6-104, 6-106 to 6-107, 6-122 to 6-125,
6-140, 6-142 to 6-143, 6-148, 6-151 to 6-152
22586 . .
6-29, 6-37 to 6-38, 6-42, 6-81, 6-98,
6-103, 6-114, 6-137 to 6-138, 6-146
22708 . . . .
6-33, 6-38, 6-99, 6-139 to 6-140
22879 . . . . . . . . . . . . 6-28, 6-32, 6-40,
6-42, 6-44 to 6-45, 6-99, 6-114, 6-126, 6-140,
6-144, 6-147, 6-153, 6-174
23769 . . . . . . . . . . . . . . . . . . 6-89,
6-107, 6-124, 6-126, 6-152, 6-159
23956 . . . . . . . . . . . . 6-28 to 6-29, 6-32
to 6-33, 6-39 to 6-40, 6-44, 6-47, 6-89, 6-101,
6-106 to 6-107, 6-114, 6-125, 6-130, 6-142 to
6-144, 6-150, 6-152
24281 . . . . . . . . . . . . . . . . . .
6-13
24303 . . . . . . . . . . . . . . 6-100, 6-141
24347 . . . . . . . . . . . . . . . . . . 6-32,
6-39, 6-43, 6-80, 6-101 to 6-102, 6-105, 6-112 to
6-113, 6-140, 6-142, 6-144, 6-149
feature (contd.)
24380 . . . . . . . . . . . . . 2-2 to 2-3, 2-13
24620 . . . . . . . . . . . . . . . 6-44, 6-150
26803 . . . . . . . . . . . . . . . . . . 6-158
26987 . . . . . . . . . . . . . . . . . .
6-70
27127 . . . . . . . . . . . . . . . . . . 6-195
27761 . . . . . . . . . . . . . . . . 4-63, 4-65
28075 . . . . . . . . . . . . . . . . . .
6-35
28239 . . . . . . . . . . . . . . . . . .
4-20
28486 . . . . . . . . . . . . . . . 6-81, 6-114
Feature
23311 . . . . . . . . . . . . . . . . . .
6-77
27717 . . . . . . . . . . . . . . . 6-47, 6-100
Find icon
use of . . . . . . . . . . . . . . . . . .
4-16
Find, using . . . . . . . . . . . . . . . .
4-18
examples
BSS parent of a Cell. . . . . . . . . .
4-22
cell with LAC . . . . . . . . . . . . .
4-23
site with BSS name and Site Id . . . .
4-22
nding attributes . . . . . . . . . . . .
4-24
nding devices . . . . . . . . . . . . .
4-19
overview . . . . . . . . . . . . . . . .
4-18
printing results . . . . . . . . . . . . .
4-26
saving results . . . . . . . . . . . . . .
4-26
Functions - command line . . . . . . . . . . 5-2
G
Generic Table Editor (GTE)
edit menu . . . . . . . .
le menu . . . . . . . .
ll cells . . . . . . . . .
format menu . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-89
3-95
3-89
3-96
3-98
Generic Table Editor (GTE) (contd.)

hot keys for MCDF . . . . . . . . . . . 3-103
Group management . . . . . . . . . . . .
2-13
group parameters . . . . . . . . . . . .
2-13
H
Hardware congurations supported. . . .
1-15
Hardware reports, generating . . . . . . 3-109
Help button, DataGen . . . . . . . . . . .
3-10
Help icon
OLM GUI . . . . . . . . . . . . . . . .
4-16
Invalid NE. . . . . . . . . . . . . . . . .
4-29
I
Importing/exporting objects. . . . . . . .
Installing the Options Object . . . . . . .
3-58
3-16
68P02900W22-R
Mar 2008
IX-3
GMR-02
Index
L
Loading network information . . . . . . . . 1-9
gathering network information . . . . .
1-10
Locate NE, PCU, site or cell . . . . . . . .
4-19
Lock/Unlock BSS area (lock_adm) com

mand . . . . . . . . . . . . . . . . . . .
Log les
viewing audit logs. . . . . . . . . . . .
5-23
4-68
M
MCDF les
creating . . . . . . . . . .
editing tables . . . . . . .
inserting . . . . . . . . .
invalid data entry . . . . .
validating . . . . . . . . .
MCDF lter (lter) command
MCDF table hierarchy . . .
MCDF tables
ACS table . . . . . . . . .
Algorithm data table . . .
BSS table . . . . . . . . .
Cabinet table . . . . . . .
Cell table . . . . . . . . .
Channel table . . . . . . .
Circuit table. . . . . . . .
Daughter table . . . . . .
DRI table . . . . . . . . .
EAS table . . . . . . . . .
Generics table . . . . . .
Hardware table . . . . . .
Hop table . . . . . . . . .
MCDF tables (contd.)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-83
3-85
3-85
3-87
3-84
5-17
6-2
KSW table. . . . . . . . . . . . . . .
Lapd table . . . . . . . . . . . . . .
Links table . . . . . . . . . . . . . .
Modify Value table . . . . . . . . . .
Neighbour table. . . . . . . . . . . .
NSVC table . . . . . . . . . . . . . .
Paths table . . . . . . . . . . . . . .
PIX table . . . . . . . . . . . . . . .
ranges, default values, dependencies .
RTF table . . . . . . . . . . . . . . .
Site table . . . . . . . . . . . . . . .
Specics table . . . . . . . . . . . .
Statistics table . . . . . . . . . . . .
Test Neighbour table . . . . . . . . .
Throttles table . . . . . . . . . . . .
Timer table . . . . . . . . . . . . . .
viewing . . . . . . . . . . . . . . . .
MMI combiner (combine) command. . .
MMI command generator (gcmd) com
mand . . . . . . . . . . . . . . . . . .
6-187
6-165
. 6-5
6-12
6-67
6-58
6-55
6-177
6-161
6-176
6-26
6-15
6-182
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-179
6-65
6-60
6-52
6-168
6-181
6-63
6-178
. 6-2
6-155
. 6-9
6-109
6-78
6-195
6-175
6-46
. 6-2
. 5-7
5-20
4-28
.
.
.
4-39
4-31
4-31
N
Navigation tree
autoclose . . . . . . .
Navigation Tree
audit . . . . . . . . .
closing . . . . . . . .
create BSS or RXCDR .
deleting a BSS/RXCDR
device management . .
introduction . . . . . .
moving levels . . . . .
Navigation Tree (contd.)

. . . . . . . . .
4-57
.
.
.
.
.
.
.
4-35
4-29
4-32
4-58
4-37
4-27
4-30
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
opening . . . . . . . . .
overwrite a BSS/RXCDR
le . . . . . . . . . . .
panner . . . . . . . . .
porthole . . . . . . . . .
Network
create . . . . . . . . . .
delete . . . . . . . . . .
Network Expansion . . . .
. . . . . . .
binary object
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . . . . 4-6
. . . . . . . .
4-53
. . . . . . . .
4-55
O
Ofine MIB (OLM)
integration with DataGen . . . . . . . . . 1-4
overview . . . . . . . . . . . . . . . . . 1-3
Ofine MIB directory structure . . . . . .
1-13
Ofine MIB directory structure (contd.)

main structure . . . . . . . . . . . . .
1-14
OLM le structure . . . . . . . . . . .
1-13
OLM GUI, using . . . . . . . . . . . . . . . 4-2
IX-4
68P02900W22-R
GMR-02
Mar 2008
Index
OLM GUI, using (contd.)

additional features . . . . . . . .
auditing logs . . . . . . . . . .
autoclose . . . . . . . . . . . .
compress/uncompress an OLM
network . . . . . . . . . . . . .
deleting a NE database . . . . .
deleting a scheduled audit . . .
managing audit logs . . . . . .
modifying a scheduled audit . .
realigning a network . . . . . .
scheduling an audit . . . . . . .
cmutil.olm command . . . . . . .
deleting a network conguration .
environment variables . . . . . .
exiting the OLM GUI . . . . . . .
expert desktop . . . . . . . . . .
front panel icons . . . . . . . . .
levels of users . . . . . . . . . . .
shutting down the OLM . . . . . .
standard desktop . . . . . . . . .
starting the OLM GUI . . . . . . .
task list . . . . . . . . . . . . . .
troubleshooting . . . . . . . . . .
database errors . . . . . . . . .
fails to start . . . . . . . . . . .
. . .
. . .
. . .
4-56
4-68
4-57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-79
4-58
4-67
4-73
4-65
4-77
4-60
4-5
4-53
4-4
4-12
4-17
4-15
4-4
4-12
4-17
4-9
4-3
4-4
4-82
4-81
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
OLM GUI, using (contd.)

troubleshooting (contd.)
force shutdown . . . . . . . . . . . .
general operating errors . . . . . . .
import errors . . . . . . . . . . . . .
reinitialise database . . . . . . . . .
specic operation fails . . . . . . . .
verify and save network . . . . . . . . .
OLM online Help . . . . . . . . . . . . .
OMC
exporting object les to the OMC . . . .
importing binary object les from the
OMC . . . . . . . . . . . . . . . . . .
Opening a BSS area . . . . . . . . . . . .
Operating DataGen . . . . . . . . . . . .
overview . . . . . . . . . . . . . . . .
procedures . . . . . . . . . . . . . . .
shutdown . . . . . . . . . . . . . . . .
startup . . . . . . . . . . . . . . . . .
Optimise DataGen database (dbaccess)
command . . . . . . . . . . . . . . . . .
Optimising the database . . . . . . . . .
Overview - DataGen . . . . . . . . . . . .
Overwriting a BSS/RXCDR binary object
le . . . . . . . . . . . . . . . . . . . .
4-84
4-83
4-84
4-86
4-83
4-42
4-16
3-114
.
.
.
.
3-58
3-39
3-2
3-2
3-2
3-10
3-9
5-22
3-13
. 1-2
4-39
P
Panner . . . . . . . . . . . . . . . . . .
4-31
Porthole . . . . . . . . . . . . . . . . . .
4-31
R
Radio Frequency planning
overview . . . . . . . .
Realign a network. . . . .
Reload an NE database . .
Revert to saved network .
Revgen . . . . . . . . . .
activating . . . . . . . .
Revgen (contd.)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-38
4-77
4-75
4-46
3-65
3-67
auto-Revgen. . . . . . . . . . .
converting object les. . . . . .
menu options . . . . . . . . . .
toolbar . . . . . . . . . . . . .
Revgen command . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-68
.
3-65
.
3-65
.
3-66
.
5-25
. 3-129
Service window
BSS area . . . . . . .
Edit menu . . . . . . .
File menu . . . . . . .
menu bar . . . . . . .
Services menu . . . .
toolbar . . . . . . . .
Shutting down DataGen .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
S
Save NE database
Save NE. . . . . . . . . .
Save network . . . . . . . .
aborting a save operation .
Scheduling an audit . . . . .
deleting . . . . . . . . . .
modifying . . . . . . . . .
Script le generator. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-43
4-46
4-52
4-60
4-67
4-65
3-70
68P02900W22-R
Mar 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-56
3-62
3-58
3-58
3-63
3-56
3-10
IX-5
GMR-02
Index
Shutting down the OLM. . . . . . . . . .

4-12
Starting DataGen . . . . . . . . . . . . . . 3-9
Starting the OLM GUI. . . . . . . . . . . . 4-9

Supported platforms . . . . . . . . . . .
1-15
T
Table Controller . . . .
command buttons . .
controls . . . . . . .
creating MCDF les.
le select buttons . .
le status display . .
les status icons . .
functions . . . . . .
menu bar . . . . . .
Toggle permissions (tp)
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
command.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-78
3-79
3-79
3-83
3-80
3-80
3-87
3-79
3-79
5-30
Tools - overview . . . . .
Troubleshooting OLM
database errors . . . .
fails to start . . . . . .
force shutdown . . . .
general errors. . . . .
import errors . . . . .
reinitialise database. .
specic operation fails
. . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-82
4-81
4-84
4-83
4-84
4-86
4-83
rename user account . . . . .

user administration utilities . .
user management . . . . . . .
user management parameters
Using the CADM tool
country administration . . . .
creating a new country . . . .
creating a new network . . . .
deleting a country/network . .
Using the Generic Table Editor
Generic Table Editor (GTE) . .
editing MCDF tables . . . . .
MCDF les . . . . . . . . . .
MCDF tables . . . . . . . . .
Using the Topology Viewer . . .
hardware conguration . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-10
. . 2-4
. . 2-3
. . 2-3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-26
3-29
3-31
3-32
. . . . .
3-89
U
Uncompress OLM network . . . . .
Upgrader . . . . . . . . . . . . . .
Upgrading a BSS area . . . . . . .
DARBC and EXBL . . . . . . . . .
multiple BSS areas . . . . . . . .
resolving problems . . . . . . . .
upgrade procedure . . . . . . . .
Usage scripts . . . . . . . . . . . .
User and group management . . . .
Usertool, using . . . . . . . . . . .
add group . . . . . . . . . . . . .
add new user account . . . . . . .
delete group . . . . . . . . . . .
delete user account . . . . . . . .
group management parameters . .
modify group . . . . . . . . . . .
modify user account . . . . . . .
rename group . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-79
3-129
3-122
3-122
3-128
3-126
3-126
3-124
3-19
. 2-2
. 2-2
2-13
. 2-7
2-17
2-11
2-13
2-15
. 2-9
2-16
Usertool, using (contd.)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-85
.
3-83
.
3-80
. 3-104
. 3-106
V
Verify NE database . . . . . . . . . . . .
Verify network . . . . . . . . . . . . . .
aborting a verify operation . . . . . . .
4-43
4-46
4-50
Version upgrader (upg) command . . . . .
5-31
X
Xterm icon . . . . . . . . . . . . . . . .
4-16
IX-6
68P02900W22-R
GMR-02
Mar 2008
Standard Printing Instructions

Part Number
68P02900W22-R
Manual Title
A4 Ring Bound - GSD (UK)

Binder
Printing
Finishing
4 D-ring binder - A4 size (210mm x 297mm) white PVC.
40mm or 65mm capacity depending on the size of the manual.
Clear pockets on front and spine.
Cover / spine text printed in colour.
Body- printed double sided onto white A4 (210mm x 297mm) 80g

4 hole paper.
A4 size (210mm x 297mm) clear PVC sheet front page for

protection.
Bag wrapped with clear polythene.
If this is to be used by manufacturing as an Inbox document, then refer to appropriate

Materials or Methods Specification.
Datagen
System Information
Datagen
System Information
GSR8
68P02900W22-R
GSR8
68P02900W22-R
Cutting
datum point
Spine
Front cover

68P02900W22

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

68P02900W22

Hochgeladen von

Copyright:

Verfügbare Formate

System Information: DataGen

All Rights Reserved

System Information: DataGen

Chapter 1: Overview of DataGen

DataGen and the OMC . . . . . . . . . . . . . . . .

Chapter 2: User and Group management using the usertool

Chapter 3: Operating DataGen

System Information: DataGen

Converting a CM database object le to a script le

System Information: DataGen

Converting a database script le to a CM database object le .

Chapter 4: Operating the Ofine MIB

Expert Ofine MIB front panel . . . . . . . . . . . . . . .

System Information: DataGen

Deleting a BSS or RXCDR from the Navigation Tree . . . . . .

Chapter 5: Command line tools

System Information: DataGen

Chapter 6: MCDF tables

Description of Site (BTS specic) table . . .

1-1: DataGen GUI . . . . . . . . . . . . . . . . . . . . . . .

3-32: Viewing an MMI script with vi . . . . . . . . . . . . . . . . . . .

4-30: auSchedule Detailed View <Create> window . .

1-1: Supported platforms in GSR8 . . . . . . . . . . . .

5-11: Command line options (tp command) . . . . . . .

System Information: DataGen

What is covered in this manual?

DataGen/OLM Clean Install Guide provides information about installation procedures.

The following sections show the revision status of this document.

Table 1 Manual version history

GSM Software Release 7

GSM Software Release 7 Half-Rate

GSM Software Release 8 GMR-02

GSM Software Release 8 FP

Resolution of service requests

Service requests resolved in this manual

Updated the default values of remote_loss_daily

The download information for the option

Incorporation of Change Notices

CDCNs incorporated in this manual

Special key sequences

Press the Ctrl and C keys at the same time.

Press the Ctrl, Shift, and C keys at the same time.

Press the Alt and F keys at the same time.

Press the pipe symbol key.

Press the Return or Enter key.

Motorola appreciates feedback from the users of our documents.

Questions and comments

The document type

The document title, part number, and revision character

The page number with the error

A detailed description of the error and if possible the proposed solution

Warnings, cautions, and notes

Warnings, cautions, and notes

Power down or unplug the equipment before servicing.

Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Council recommendation of 12 July 1999 on the limitation of exposure of the general

Caring for the environment

Caring for the environment

Disposal of Motorola equipment

Disposal of surplus packaging

CMM labeling and disclosure table

CMM labeling and disclosure table

Motorola document set

Motorola document set