Software Release Notes Cell Optimization Product (COP) GSR10v1.0.10

Cell Optimization Product (COP)
Software Release Notes

COP GSR10v1.0.10
GSR10
68P02900W69-L
2011 Motorola, Inc. All Rights Reserved.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola Solutions, Inc. assumes
no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola Solutions, 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 Solutions, 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 modified 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.
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 Solutions, 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 Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark on Motorola products confirms the Motorola Solutions, 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
athttp://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 office.
GSR10v1.0.10
Apr 2011
Table
of
Contents
Contents
Software Release Notes: Cell Optimization Product (COP)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
3
4
5
5
5
5
5
General information about the release notes . . .

Introduction to the COP release . . . . . . .
Chapter descriptions . . . . . . . . . . . . .
General information about this software release .
Overview of software . . . . . . . . . . . .
Nomenclature, release load identification . .
Deliverables: CD-ROM . . . . . . . . . . . . . .
Media . . . . . . . . . . . . . . . . . . . .
Verifying integrity . . . . . . . . . . . . . .
New features. . . . . . . . . . . . . . . . . . .
Introduction to new features . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-2
1-3
1-3
1-3
1-4
1-4
1-4
1-6
1-6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-2
2-2
2-3
2-4
2-5
2-6
2-7
Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Document banner definitions . . .
Text conventions . . . . . . . . . .
Contacting Motorola Solutions . . . . .
24-hour support . . . . . . . . . .
Ordering documents and CD-ROMs
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: About this release
Chapter 2: Open issues

Issues: overview . . . . . . . .
Service affecting (P1) . . .
Serious (P2) . . . . . . . .
Low Priority (P3) . . . . . .
Information provided . . .
Open issues summary . . . . .
Open P1 (service affecting) SRs
Open P2 (serious) SRs . . . . .
Open P3 (annoying) SRs . . . .
68P02900W69-L
Apr 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
GSR10v1.0.10
Contents
Chapter 3: Resolved issues

SRs resolved in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2
Chapter 4: Compatibility
OMC and BSS Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC and BSS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC and BSS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4-2
4-2
Chapter 5: Hardware and firmware requirements

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-2
5-3
5-4
Introduction to COP software management . . . . . . .

Open problems affecting software management . . .
Pre-installation checks . . . . . . . . . . . . . . . .
Managing users and access . . . . . . . . . . . . . . .
Creating the asaadmin user on the OMCs . . . . . .
Accessing usertool . . . . . . . . . . . . . . . . . .
Creating the asaadmin user . . . . . . . . . . . . .
Checking the asaadmin user . . . . . . . . . . . . .
Checking the asaadmin crontab access . . . . . . .
Checking asaadmin account trusted on each OMC-R
Installing COP . . . . . . . . . . . . . . . . . . . . . .
General installation information . . . . . . . . . . .
Installation procedure . . . . . . . . . . . . . . . .
COP License . . . . . . . . . . . . . . . . . . . . .
OTG installation . . . . . . . . . . . . . . . . . . .
Utility/tools selection . . . . . . . . . . . . . . . .
GLU installation . . . . . . . . . . . . . . . . . . .
CAT installation . . . . . . . . . . . . . . . . . . .
CTP installation . . . . . . . . . . . . . . . . . . .
ECT installation . . . . . . . . . . . . . . . . . . .
Installation complete. . . . . . . . . . . . . . . . .
Post-installation procedures . . . . . . . . . . . . . . .
Introduction to post-installation procedures . . . . .
Adjust COP cronjob timings . . . . . . . . . . . . .
Auto Tune feature . . . . . . . . . . . . . . . . . .
Configure the mouse menu for COP Tools GUI . . . .
GUI Client setup . . . . . . . . . . . . . . . . . . .
Backout . . . . . . . . . . . . . . . . . . . . . . . . .
Removal of GLU . . . . . . . . . . . . . . . . . . .
Removal of CAT . . . . . . . . . . . . . . . . . . .
Removal of CTP . . . . . . . . . . . . . . . . . . .
Removal of ECT . . . . . . . . . . . . . . . . . . .
Removal of OTG . . . . . . . . . . . . . . . . . . .
Backing up COP . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . .
Prerequisites for tape backup . . . . . . . . . . . .
Local Machine Disk Backup on the GUI Server . . .
Remote Machine Disk Backup to the OMC-R Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-2
6-2
6-3
6-3
6-3
6-5
6-7
6-8
6-8
6-10
6-10
6-10
6-15
6-19
6-20
6-21
6-21
6-25
6-26
6-33
6-34
6-34
6-34
6-35
6-36
6-38
6-40
6-40
6-40
6-41
6-42
6-43
6-44
6-44
6-47
6-47
6-50
COP requirements . . . . . . .
Target platforms . . . . . .
System specifications . . .
Requirements for executing
OMC-R version upgrades .
. . .
. . .
. . .
COP
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 6: Software management
ii
GSR10v1.0.10
68P02900W69-L
Apr 2011
Contents
Local Machine Tape Backup on the GUI Server . . .

Remote Machine Tape Backup to the OMC-R Server
Post Backup Procedures . . . . . . . . . . . . . . .
Upgrading . . . . . . . . . . . . . . . . . . . . . . . .
Starting the upgrade process . . . . . . . . . . . .
Selecting a tool for upgrade . . . . . . . . . . . . .
Upgrading COP license . . . . . . . . . . . . . . .
Upgrading GLU procedure . . . . . . . . . . . . .
Upgrading CAT procedure . . . . . . . . . . . . . .
Upgrading CTP procedure . . . . . . . . . . . . .
Upgrading ECT procedure . . . . . . . . . . . . .
Restoring COP . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . .
Restore COP from disk backup on the GUI Server . .
Restore COP from tape backup on the GUI Server . .
Post Restore Procedures . . . . . . . . . . . . . . .
Setting up CAT . . . . . . . . . . . . . . . . . . . . . .
System Administration . . . . . . . . . . . . . . . .
Auto Tune Thresholds . . . . . . . . . . . . . . . .
Manually adjust thresholds and throttles . . . . . .
Comments . . . . . . . . . . . . . . . . . . . . . .
Blacklist . . . . . . . . . . . . . . . . . . . . . . .
Critical cells . . . . . . . . . . . . . . . . . . . . .
Parameters. . . . . . . . . . . . . . . . . . . . . .
Rule sets . . . . . . . . . . . . . . . . . . . . . . .
Changing the ECT configuration . . . . . . . . . . . . .
Effecting changes . . . . . . . . . . . . . . . . . .
Window location . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-52
6-55
6-59
6-60
6-60
6-61
6-62
6-63
6-64
6-67
6-68
6-70
6-70
6-70
6-73
6-73
6-74
6-75
6-75
6-75
6-76
6-77
6-77
6-78
6-79
6-79
6-80
6-80
6-80
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
asaadmin .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-2
7-3
7-3
7-3
7-3
7-4
7-4
7-6
7-7
7-7
7-8
7-9
7-9
7-9
7-10
7-10
7-10
7-11
7-11
7-13
7-13
7-13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 7: Troubleshooting
Problems and questions . . . . . . . . . . . . . . . . . . .
Motorola contacts . . . . . . . . . . . . . . . . . . . .
Solving COP Installer problems . . . . . . . . . . . . . . .
Possible problems . . . . . . . . . . . . . . . . . . . .
g_1MmiNames is not set . . . . . . . . . . . . . . . . .
The COOKIE variable . . . . . . . . . . . . . . . . . .
Solving CAT problems . . . . . . . . . . . . . . . . . . . .
Reporting CAT problems . . . . . . . . . . . . . . . . .
Solving CTP problems . . . . . . . . . . . . . . . . . . . .
Reporting CTP problems . . . . . . . . . . . . . . . . .
Solving ECT problems . . . . . . . . . . . . . . . . . . . .
No data to display . . . . . . . . . . . . . . . . . . . .
License expiry message still appears after renewal . . .
Run PdpNow button is disabled . . . . . . . . . . . . .
ECT help does not work . . . . . . . . . . . . . . . . .
ECT application reports server or database issue . . . .
ECT application starts but contains no data . . . . . . .
Solving licensing problems. . . . . . . . . . . . . . . . . .
When OMC reboots, the license server cannot be started
68P02900W69-L
Apr 2011
GSR10v1.0.10
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
by user
iii
Contents
iv
GSR10v1.0.10
68P02900W69-L
Apr 2011
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
6-1: Usertool main window . . . . . . . . . . . . . . .

6-2: User Administration utility. . . . . . . . . . . . .
6-3: Xterm prompt . . . . . . . . . . . . . . . . . . .
6-4: OMC Validation message . . . . . . . . . . . . .
6-5: OMC Validation Complete message . . . . . . . .
6-6: Motorola CD-ROM Installer window . . . . . . . .
6-7: Machines List window . . . . . . . . . . . . . . .
6-8: COP Licence window . . . . . . . . . . . . . . .
6-9: COP Licence installation complete window . . . .
6-10: COP license screen - 1 . . . . . . . . . . . . . .
6-11: COP license screen - 2 . . . . . . . . . . . . . .
6-12: COP license screen 3 . . . . . . . . . . . . . .
6-13: OTG Main Window . . . . . . . . . . . . . . . .
6-14: An example of the Status window . . . . . . . .
6-15: CAT Configuration window . . . . . . . . . . . .
6-16: cron job setup window . . . . . . . . . . . . . .
6-17: COP Security Warning . . . . . . . . . . . . . .
6-18: ECT Installer window. . . . . . . . . . . . . . .
6-19: ECT Configuration window . . . . . . . . . . . .
6-20: ECT Configuration window: OMC-R details . . .
6-21: ECT Configuration window: Database Settings. .
6-22: Motorola CD-ROM Installer window . . . . . . .
6-23: GLU Upgrading window . . . . . . . . . . . . .
6-24: CAT upgrading message . . . . . . . . . . . . .
6-25: CAT Threshold Upgrader window . . . . . . . .
6-26: CAT Threshold Upgrader - Detail Screen window
6-27: COP Security Warning . . . . . . . . . . . . . .
6-28: ECT Upgrade window . . . . . . . . . . . . . .
68P02900W69-L
Apr 2011
GSR10v1.0.10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-4
6-5
6-7
6-12
6-12
6-14
6-15
6-16
6-16
6-17
6-18
6-18
6-20
6-21
6-23
6-25
6-26
6-27
6-29
6-30
6-31
6-61
6-63
6-64
6-66
6-67
6-68
6-69
List of Figures
vi
GSR10v1.0.10
68P02900W69-L
Apr 2011
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
2-1:
2-2:
3-1:
5-1:
6-1:
6-2:
7-1:
7-2:
Information provided on the open service requests

Open issues reported in GSR10v1.0.10 . . . . . .
SRs resolved in this version of COP . . . . . . . .
Target platforms for COP applications . . . . . .
Field entries of usertool. . . . . . . . . . . . . .
Forcing ECT to use new OMC-R configuration . .
CAT problems . . . . . . . . . . . . . . . . . . .
CTP problems . . . . . . . . . . . . . . . . . . .
68P02900W69-L
Apr 2011
GSR10v1.0.10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-3
2-4
3-2
5-2
6-6
6-80
7-4
7-7
vii
List of Tables
viii
GSR10v1.0.10
68P02900W69-L
Apr 2011
About
This
Document
Software Release Notes: Cell Optimization

Product (COP)
This manual contains release notes for the Cell Optimization Product (COP) at GSR10v1.0.10. It
is a general description of the product package, which contains a reference to the installation
instructions, and the system requirements. It details the features in the product for this release,
and a summary of the open problem reports up to the date of the document.
For COP functionality, refer to System Information: Cell Optimization Product (68P02900W90).
For software release information, refer to this manual.
68P02900W69-L
Apr 2011
GSR10v1.0.10
Revision history
About this Document
Revision history
Version information
The following table shows the issue status of this document since it was first released.
Issue
Date of issue
Remarks
Jun 2010
Issue L - COP GSR 10v1.0.0
Jan 2011
Jan 2011
Jan 2011
Mar 2011
Apr 2011
Resolution of Service Requests

The following Service Requests are resolved in this document:
Service
Request
CMBP Number
N/A
N/A
Remarks
Incorporation of Change Notices
CN Date
CN Number
N/A
N/A
GSR10v1.0.10
Title
68P02900W69-L
Apr 2011

Product (COP)
General information
General information
Purpose
Motorola Solutions documents provide the information to operate, install, and maintain
Motorola Solutions equipment. It is recommended that all personnel engaged in such activities
be properly trained by Motorola Solutions.
Motorola Solutions 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 Solutions. They can be used to supplement and enhance the knowledge gained
through such training.
NOTE
If this document was obtained when attending a Motorola Solutions training course,
it is not updated or amended by Motorola Solutions. It is intended for TRAINING
PURPOSES ONLY. If it was supplied under normal operational circumstances, to
support a major software release, then Motorola Solutions automatically supplies
corrections and posts on the Motorola Solutions 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.
Document banner definitions

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
68P02900W69-L
Apr 2011
GSR10v1.0.10
General information
About this Document
Text conventions
The following conventions are used in Motorola Solutions 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.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Contacting Motorola Solutions
Contacting Motorola Solutions
Motorola Solutions appreciates feedback from the users of our documents.
24-hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. 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 Solutions Office.
Ordering documents and CD-ROMs

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

Send questions and comments regarding user documentation to the email address:
mydocs@motorolasolutions.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
68P02900W69-L
Apr 2011
GSR10v1.0.10
About this Document
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
1
About this release
68P02900W69-L
Apr 2011
GSR10v1.0.10
1-1
General information about the release notes
General information about the release notes
Introduction to the COP release

These release notes provide an introduction to the Cell Optimization Product new features in
COP GSR10v1.0.10.
For COP functionality, refer to System Information: Cell Optimization Product (COP)
(68P02900W90).
For software release information, refer to this manual.
Chapter descriptions
Chapter 1 provides general information about this release of COP, including lists of new and
amended features.
Chapter 2 provides information on open problems in this release.
Chapter 3 provides information on resolved problems in this release.
Chapter 4 provides information on OMC and BSS compatibility.
Chapter 5 provides information on target platforms and requirements for operating COP.
Chapter 6 describes how to install, upgrade, and configure COP.
Chapter 7 provides Motorola contact details, and describes some common problems that may
be experienced with COP, and their solutions.
1-2
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
General information about this software

release
General information about this software release
Overview of software
This section covers general information about this version of COP. It is provided to make the
user aware of any special operating notes and/or procedures before installing this software
release in their network.
NOTE
To confirm the compatibility of this COP version with OMC and BSS software releases,
refer to Chapter 4 Compatibility.
Nomenclature, release load identification

The release load identifier for COP GSR10v1.0.10 is:
COP GSR10v1.0.10
Where:
is:
v1.0
the version number.
10
the revision number.
This load identifier is reproduced at the foot of each page of the documentation and on the
CD-ROM (refer to the section Deliverables: CD-ROM on page 1-4 in this chapter).
NOTE
When reporting difficulties to Motorola, quote this load identifier.
68P02900W69-L
GSR10v1.0.10
1-3
Apr 2011
Deliverables: CD-ROM
Media
CD-ROM: COP software
All the COP software and customer documentation is supplied on one CD-ROM. The CD-ROM
also contains third-party product software for TCL/TK, EasyCharts, and Postgres.
The following information is contained on the CD-ROM label:
Release load identifier.
Checksum number.
Verifying integrity
COP Software Verification (CD-ROM)
The COP software to be installed on each processor should be verified first.
1.
Ensure that the CD-ROM is mounted on each processor.
2.
Enter the following commands:

cd /cdrom/cdrom0
./CHECK_CD
The CHECK_CD utility displays checksums, which verify the files contained in the CD-ROM. A
checksum is given for each of the files in the CD-ROM. If all the files pass the check successfully,
a message is displayed to this effect. An example for the screen output of a successful check is
as follows:
1-4
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
26932
17142
1885
2782
23787
1264
58134
40206
20294
16251
12
4
13
64
94
6
1037
21
1
1
9991
7814
26409
43834
9294
40799
26482
55191
55115
54498
54041
1
2
1
2
1
47
47
2
2
81
5
./CHECK_CD
./CD_Installer.cfg
./Install
./make_tools_dir
./CD_Installer.tcl
./instListMachines.sh
./omctools/licence/MOT_SIG
./omctools/licence/cop_install_licence.tcl
./omctools/licence/install.fid
./omctools/licence/license_template
.
.
.
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
ok.....
./omctools/cat/GetDRIOMC.arc
./omctools/cat/GetDRISITE.arc
./omctools/cat/GetGetBlList.arc
./omctools/cat/GetSites.arc
./omctools/cat/GetDRICnt.arc
./cmd_cron
./cmd_prtvtoc
./isql_mib.sh
./isql_pm.sh
./tools_web_built_1600.tar
./install_CTP
All file checksums verify ok !

If the output from the check indicates an error, contact Motorola.
68P02900W69-L
GSR10v1.0.10
1-5
Apr 2011
New features
New features
Introduction to new features

GLU new features and enhancements
GLU has been enhanced to support and to be compatible with GSR10 environment and its
embedded third-party products.
GLU has been enhanced with the following new security features:
COP GSR10 Compatibility
Proper exception handling
COP ECT DB audit trail review
GLU has been enhanced to support the following features:

Gb Over IP
New CTU8m hardware
E-EDGE Phase 1: - Dual Carrier (this feature is not available for order yet)
CTU8m and RCTU8m 8 carrier support
Alarm when TS goes INTRANS
CTU8m Low Loss Coherently Combined Solution for High Power 8/8/8
Separate Radio Link Timers for AMR FR/HR
CTU8m license
EDGE KPIs for CMCC
Supporting large site 12/12/12 for GSR program
1-6
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
New features
CAT new features and enhancements

CAT has been enhanced with the following new security features:
Proper exception handling
Strong admin password
CAT has been enhanced to support the following features:
Split BER to SDCCH BER and TCH BER on both DL and UL
Separation of temporary block flow (TBF) time depending on GPRS and EDGE activity
ECT new features and enhancements

ECT has been enhanced with the following new security features:
Strong admin password
CTP new features and enhancements

This is a CTP compatibility release only, which means CTP is able to decode only GSR9 and
GSR10 GSM Call Trace and RF Loss files. There are no new GSR10 features or enhancements
included for this release. All new GSR10 features and enhancements are integrated into the
CTP-GSM (Windows) product.
68P02900W69-L
Apr 2011
GSR10v1.0.10
1-7
1-8
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
2
Open issues
68P02900W69-L
Apr 2011
GSR10v1.0.10
2-1
Issues: overview
Issues: overview
This chapter details the Service Affecting (P1), Serious (P2) and Low Priority (P3) service
requests logged against the COP software, and which remain outstanding at the time of the
release.
Service affecting (P1)

A service affecting problem report is one that affects a primary functional requirement of
the system. Examples of primary functional requirements are: processing calls, signaling,
and other interworking functions.
Serious (P2)
A serious problem report is one that affects a major functional requirement of the system.
Examples of these major functional requirements are operational and system performance
information, the ability to reconfigure the network and errors in procedures where service risks
are involved. Serious problem reports do not prevent the system from meeting its primary
functional requirements.
Low Priority (P3)

A low priority problem report is one that affects a minor functional requirement of the system.
P3 problem reports do not prevent the system from meeting its primary functional requirements.
2-2
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Issues: overview
Information provided
The information provided on each open issue is explained in the Table 2-1.
Table 2-1 Information provided on the open service requests

Section
Type of information
SR #
The Service Request number.
Description
A detailed description of the problem.
Customer Impact
Provides information on service-related difficulties that the

customer may experience.
Cause
Describes the steps/operation which cause the problem to

occur.
Workaround
Describes the steps to perform the required operation without

causing the problem, as described, to occur.
Prevention
Describes any preventative action which could be implemented

to minimize occurrence.
Recovery
Describes the steps necessary to return the system to normal

operation.
68P02900W69-L
GSR10v1.0.10
2-3
Apr 2011
Open issues summary
Open issues summary
Table 2-2 lists the SRs which are reported in the Cell Optimization Product (COP) GSR10v1.0.10
release.
Table 2-2 Open issues reported in GSR10v1.0.10
2-4
SR
Severity
Description
N/A
N/A
N/A
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
There are no open P1 (service affecting) SRs in this release.
68P02900W69-L
GSR10v1.0.10
2-5
Apr 2011
Open P2 (serious) SRs
Open P2 (serious) SRs
There are no open P2 (serious) SRs in this release.
2-6
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Open P3 (annoying) SRs
Open P3 (annoying) SRs
There are no open P3 (annoying) SRs in this release.
68P02900W69-L
Apr 2011
GSR10v1.0.10
2-7
2-8
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
3
Resolved issues
68P02900W69-L
Apr 2011
GSR10v1.0.10
3-1
SRs resolved in this release
Table 3-1 lists all the service requests resolved in this version of COP.
Table 3-1
SRs resolved in this version of COP
SR Number
SR1189542
Release Introduced
Description
COP_R7.2.0
COP_CTP looses parts of the Trace Request

messages while decoding the GSM Call Trace file.
This SR resolves the data loss issue by retrieving
some of the missing Trace Request messages in
the CTP decode output.
The ECT cannot upgrade from GSR10v1 IR2 to
GSR10v1 IR3.
This SR resolves the upgrade issue between
different IRs in the same release of the ECT.
SR1194053
COP_R10.1.0
SR1205632
COP_R7.2.0
The CTP Decoding has no response.

This SR resolves the CTP decode issue by fixing the
NULL pointer exception in the code.
GSR9v1.0 build.16
CAT Daily Summary Data missing if RTF OOS.

This SR resolves the deficiency in the SQL query to
generate CAT Carrier Daily Report when the RTF
is OOS.
SR2298692
SR2299436
GSR9v2.0 build.5
SR2302709
COP_R7.2.0
SR2333749
GSR9v1.0
SR2334190
COP_R8.1.0
SR2349800
GSR8v2.0 build.8
Error in the CTP command line

CTP_copy_to_bsc_dirs.
This SR resolves the error by modifying the
CTP_copy_to_bsc_dir script to support years
beyond 2005.
CTP generates core file daily when running cron
job to collect call trace logs. This SR resolves the
issue by enlarging the size of message array.
ECT failure to get *sps license code from
/usr/omc/tools. This SR added applix license
path to tcl8env file to fix the issue.
In the GLU output, the parameter option_preempt
is not reflecting properly. The CM database is
showing the values as 2, where as the GLU output
is showing the value as 0.
This SR resolves the issue by deleting the
related impact from another parameter
option_empreempt.
GLU cannot export inter-RAT neighbor. This SR
resolves this issue by updating SQL language.
Continued
3-2
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Table 3-1
SRs resolved in this version of COP (Continued)
SR Number
SR2362966
68P02900W69-L
Apr 2011
Release Introduced
COP_R9.1.0
Description
In the GLU output, parameter
gprs_network_operation_mode appears twice,
first on a per BSC basis and the second time on
a per PCU basis. The value on the PCU basis is
incorrect.
This SR resolves the issue by deleting the
parameter gprs_network_operation_mode on
the PCU window.
GSR10v1.0.10
3-3
3-4
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
4
Compatibility
68P02900W69-L
Apr 2011
GSR10v1.0.10
4-1
OMC and BSS Compatibility
Chapter 4: Compatibility
OMC and BSS Compatibility
OMC and BSS hardware

COP works with any GSM OMC-R hardware that is supported by Motorola, and with any BSS
equipment managed by the OMC-R.
OMC and BSS software

This version of COP is fully compatible with the following GSM OMC-R software release:
GSR10 (OMC release 1.a.0.0)
This version of COP is fully compatible with the following GSM BSS software releases:
4-2
GSR10 (BSS release 1.a.0.x)
GSR9 (BSS release 1.9.0.x)
GSR8 (BSS release 1.8.0.x) (this feature is now not available for order)
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
5
Hardware and firmware requirements
68P02900W69-L
Apr 2011
GSR10v1.0.10
5-1
COP requirements
Chapter 5: Hardware and firmware

requirements
COP requirements
Target platforms
Ensure that the COP applications are installed on the appropriate target platforms (refer to
Table 5-1).
Table 5-1 Target platforms for COP applications

Application
Target platforms
GLU
GUI Server only
CAT
GUI Server only
CTP
GUI Server or remote Sun Solaris 10 based machine
ECT
GUI Server only
The performance of COP is affected by the specification of the GUI Server. Choose a high
specification server, if available. The minimum specification is a SPARC ULTRA5 or whatever is
recommended as part of the OMC-R specifications for GUI Servers.
A GUI Server where COP is installed needs to allocate some resources periodically to the
maintenance of COP. This allocation resource may impact the performance of the GUI Server
user interface as seen by the user while the maintenance activity completes. For example, while
the hourly CAT cronjob completes, the GUI performance may slow down.
It is recommended that COP tools are not executed on a GUI Server where there are one or
more GUI Clients attached, as the GUI Clients may experience performance degradation while
the COP processes execute in the GUI Server.
COP tools cannot be directly executed from a GUI Client, the display must be transported from
a GUI Server to the GUI Client. This is because the Informix client software and disk shares
required by COP are not available to the GUI Client.
System specifications
The system specifications for COP release GSR10 are as follows:
NETRA 20 (GSM OMC-R small)
5-2
2 X 900 MHz US-III+ processors
4 GB memory
2 X 73 GB internal drives
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
COP requirements
NETRA 440 (GSM OMC-R small)
2 X 1280 MHz US-IIIi processors (N42-XCB2-4GUBD)
4 GB memory
SUNFIRE 4800 (GSM OMC-R large)
8 GB memory
SUNFIRE 4900 (GSM OMC-R large)
8 GB memory
M5000 (GSM OMC-R large)
4 X 2.15 Ghz Sparc64 VI processors
24 GB Memory
12 x 146 GB external drives
Requirements for executing COP

GLU, CAT, and ECT can be executed by any user (other than omcadmin) on a GUI Server.
CTP can be executed by any user (other than omcadmin) on a GUI Server or a remote Sun
Solaris 10 based machine.
NOTE
COP multi OMC-R functionality requires that both CAT and GLU are installed on
all OMC-Rs, and that both have been configured with the list of OMC-R system
processor names.
For all the login procedure in this document, use ssh command.
68P02900W69-L
GSR10v1.0.10
5-3
Apr 2011
COP requirements
Chapter 5: Hardware and firmware

requirements
Motorola recommends that the maximum number of concurrent CAT, CTP UNIX, ECT, or GLU
sessions started on a GUI Server platform is 5. By exceeding this limit, performance issues
are experienced in the GUI Server platform.
OMC-R version upgrades

After an OMC-R version upgrade, it is possible that COP tools do not function properly, for
example, they may not start. This is because the OMC-R upgrade process may change the
ownership of the COP directories and files in /usr/omc/ne_data. To restore the ownership,
the procedure is as follows:
Procedure 5-1 Restoring ownership
5-4
Log in as root on the OMC-R.
Change directory to /usr/omc/ne_data/tools.
Execute the COP_chown.sh script.
Verify the ownership of the following COP directories and files:
GLU
ECTv2
OTG
cell_analysis
CTP
tools
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
6
Software management
68P02900W69-L
Apr 2011
GSR10v1.0.10
6-1
Introduction to COP software management
Introduction to COP software management
This chapter comprises the following sections:
Introduction to COP software management.
Managing users and access.
Installing the appropriate utility/tool.
Backout.
Upgrading.
Setting up CAT.
Changing the ECT configuration.
CAUTION
Users must not edit or alter any of the scripts in the installation program supplied. If
problems occur, contact the Motorola local office or the Customer Network Resolution
Center at Swindon.
Open problems affecting software management

There are no SRs affecting the installation, upgrade, or backout of this release.
Pre-installation checks
Ensure that you have the following:
The correct COP CD-ROM.
Hardcopy documentation (68P02900W90 System Information: Cell Optimization Product ).
License (shipped with the product).
NOTE
Before installing the COP software, ensure that it is the same version as the
OMC-R. The OMC-R version number is given on the OMC-R GUI, and the
appropriate utility/tool version number is printed on the COP CD-ROM.
COP must be installed using a pre-configured asaadmin account. Refer to the section Managing
users and access on page 6-3 to configure this account.
6-2
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Managing users and access
Creating the asaadmin user on the OMCs

To allow COP to be installed on the OMC-R, a user asaadmin must exist on each OMC that
connects to COP.
To check whether the user asaadmin exists, enter the following command at the OMC
command line:
ypcat passwd | grep asaadmin
If the user exists, the response should be:
asaadmin:<encrypted password>::uuu:110::/home/asaadmin:/bin/csh
Where:
is:
uuu
the allocated user ID.
If there is no response then perform the procedures described here to create and check the
asaadmin user.
Accessing usertool
The procedure to access usertool through the command-line interface is as follows:
Procedure 6-1 Accessing usertool through the command line interface
If logged in as user root execute the following command:

DISPLAY=omc_splat:0.0
where omc_splat is the TCP/IP address setting of the system processor.
This can be found in the /etc/hosts file.
If logged in to the Server remotely, execute the following command:
DISPLAY=TerminalDisplay:0.0
where TerminalDisplay is the TCP/IP address setting of the terminal being
used for the remote login.
68P02900W69-L
Execute the following command:

export DISPLAY
/usr/omc/current/sbin/OMC_Sync
GSR10v1.0.10
6-3
Apr 2011
The usertool main window is displayed as shown in Figure 6-1:
Figure 6-1 Usertool main window
Once an option has been selected, a screen is displayed (refer to the Figure 6-2) with all the
relevant fields which can be modified. In this screen, a field is highlighted which can be moved
with the cursor keys. The highlighted field can be modified by typing or deleting as required.
Once all the fields have been correctly filled in, select Done to save the changes, or select
Cancel to quit.
6-4
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Figure 6-2
User Administration utility
The relevant user or group operation is performed. After adding, deleting, or modifying users,
the CDE settings and MIB profiles are also updated automatically, if the user is a member of
the omc group.
Creating the asaadmin user

Add asaadmin
Follow Procedure 6-2 to add a user asaadmin.
68P02900W69-L
GSR10v1.0.10
6-5
Apr 2011
Procedure 6-2 Adding an asaadmin user
Access usertool as given in the Procedure 6-1.
From the usertool main window, type 1 to Add user. The User administration
utility is displayed as in Figure 6-2.
Enter a unique user name (asaadmin) and modify the default user creation
parameters as required.
It is highly recommended that a value is entered in the Full name field, as it
is required by specific command-line Operation and Maintenance utilities
such as cmdLineAudit.
Highlight Done and press Enter.
Enter the user account password twice. This completes the user creation.
The user privileges and profile are updated in the MIB database.
Field entries of usertool are listed in Table 6-1.
Table 6-1
Field entries of usertool
Field
Value
User Name
asaadmin
User Id
112 or 113 (or any unused user id).
Primary Group
110
Example of creating asaadmin using usertool

Username : asaadmin
Full Name : asaadmin Operator
Home directory : /home/asaadmin
UID : 112 or 113 (or any unused user id)
Group : omc / 110
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
After creating the user asaadmin successfully, the message will be displayed as:
Creating user asaadmin
64 blocks
Setting password for user asaadmin...
New Password:
Re-enter new Password:
6-6
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
passwd: password successfully changed for asaadmin

Updating privileges on the mib database for asaadmin
Sun Microsystems Inc.
SunOS 5.9
Generic May 2002
You have new mail.

Creating MIB profile for asaadmin...
Done.
Checking the asaadmin user

Check the new user by the following procedure:
Procedure 6-3 Checking the asaadmin user
Log into the console as user asaadmin with the password asar00t.
If the response is incorrect then use the usertool to correct the error.
Verify the prompt that is displayed as in Figure 6-3.
Figure 6-3 Xterm prompt
68P02900W69-L
GSR10v1.0.10
6-7
Apr 2011
Checking the asaadmin crontab access

Check the crontab access permission of the user asaadmin by the following procedure:
Procedure 6-4 Checking the crontab access
Log in as user root.
Display the content of the file cron.allow present under the directory
/etc/cron.d:
cd /etc/cron.d
cat cron.allow
If asaadmin is displayed in the output, it means that the user asaadmin
has access to the crontab.
If asaadmin is not displayed, the user has to edit the file. Before opening
the file, the user has to check the access right of the file. If it is read-only,
then the user has to change the access right as follows:
ls la
chmod 644 cron.allow
Then, open the file cron.allow and insert asaadmin into the file as follows:
vi cron.allow
Type:
asaadmin
If the file permission is changed, revert back to the original read permission
as follows:
chmod 444 cron.allow
Display the crontab file which belongs to each user:

cd /var/spool/cron/crontabs
ls la
If asaadmin file is not displayed in the output, it means that there is no
crontab file belonging to asaadmin user.
Create the asaadmin crontab file as follows:
cd /var/spool/cron/crontabs
touch asaadmin
Change the access permission of the asaadmin crontab file as follows:
chmod 600 asaadmin
Checking asaadmin account trusted on each OMC-R

To enable COP to share configuration settings between OMC-Rs, the asaadmin account must
be trusted on each OMC-R.
6-8
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Perform this procedure for each OMC-R where a trust relationship is required:
Procedure 6-5 Checking asaadmin account trusted on each OMC-R
68P02900W69-L
Log in as user asaadmin.
Execute the command :ssh <omc name or IP address>

Ensure that the target OMC-R allows the user to log in without requiring a
password. If there is any problem, contact the system administrator.
Execute the command: ssh < target GUI server or IP address>

Ensure that the target GUI Server allows the user to log in without requiring
a password. If there is any problem, contact the system administrator.
GSR10v1.0.10
6-9
Apr 2011
Installing COP
Installing COP
General installation information

This chapter covers basic installation and the changes needed to make it possible to run the
appropriate utility/tool from the Motif or Common Desktop Environment (CDE) Window
Manager.
NOTE
Before installing the COP software, ensure that it is the same release version
as the OMC-R. The OMC-R version number is given on the OMC-R GUI and the
appropriate utility/tool version number is printed on the CD-ROM.
CAT must not be installed before a PM Resync has been run on the OMC-R, as
described in the Administration Procedures chapter of the manual Operating
Information: GSM System Operation (68P02901W14).
The COP installation and upgrade should be done on a GUI Server.
If this is a re-installation, the existing utility/tool must be removed before installing the new
version. For detailed information, refer to the section Backout on page 6-40 in this chapter.
If this is an upgrade, refer to the section Upgrading on page 6-60 in this chapter.
If any problems are encountered during installation, refer to the section Solving COP Installer
problems on page 7-3 in Chapter 7 Troubleshooting.
Installation procedure
NOTE
If this is an upgrade of an existing COP installation, refer to the section Upgrading on
page 6-60 in this chapter.
6-10
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
The procedure for a new installation of the appropriate utility/tool is as follows:
Procedure 6-6 Installing the appropriate utility/tool
On the GUI Server with a CD-ROM drive, log in as asaadmin. Check that the
DISPLAY environment variable is correctly set to the operators display:
echo $DISPLAY
If there is an error:
DISPLAY: Undefined variable
set DISPLAY to the IP address for the terminal being used.
Change to user root.

su
(When prompted, enter the root password).
Insert the Cell Optimization Product CD-ROM into the drive.
Execute the following commands:

cd /cdrom/cdrom0
./Install
The following prompt is displayed:

Are you sure you want to continue (Y/N) [N] ?
Enter Y.
NOTE
If the TCL processes are currently used by other users, the
following prompt will be displayed:
TCL active processes detected. It currently
been used by others.
Are you sure you want to kill all the
TCL processes (Y/N) [N] ?
Enter Y to terminate all the TCL processes and continue

installation. Otherwise, installation will be aborted.
Continued
68P02900W69-L
GSR10v1.0.10
6-11
Apr 2011
Installing COP
Procedure 6-6 Installing the appropriate utility/tool (Continued)

6
The OMC validation message (Figure 6-4) is displayed.
Figure 6-4 OMC Validation message
ti-gsm-OMC Validation-0002a-ai-sw
Select OK.
7
The OMC Validation Complete message (Figure 6-5) is displayed.
Figure 6-5 OMC Validation Complete message
Click OK.
6-12
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
CD Installer GUI
A message is displayed while the CD Installer GUI is started. Then the CD-ROM Installer
window and the Security Warning window, as in Figure 6-6, are displayed. Upon acknowledging
the security warning message by clicking the OK button, the Security Warning window is closed.
The CD Installer window contains a list of items that can be installed. If an item is already
installed, the list shows the date of installation.
NOTE
A series of status windows, superimposed on the CD-ROM Installer window (some
of which require operator response), are displayed to show the progress through a
series of pre-install checks. These checks are read-only and are designed to indicate
where the OMC-R configuration has to be adjusted.
68P02900W69-L
GSR10v1.0.10
6-13
Apr 2011
Installing COP
Figure 6-6 Motorola CD-ROM Installer window
ti-gsm-COP GSR10v1.0-00003a-ai-sw
6-14
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
COP License
To install the COP license from the CD-ROM Installer window (Figure 6-22), follow this
procedure:
Procedure 6-7 Installing the COP license
Select COP license and click Install. The Machines List window, as in
Figure 6-7, is displayed with a list of processors.
Figure 6-7
Machines List window
Select the appropriate processor and click OK.
The COP Licence window and the Security Warning window, as in

Figure 6-8, are displayed. Upon acknowledging the security warning
message by clicking the OK button, the Security Warning window is closed.
The COP Licence window allows entry of Licence Expiry Date and Licence
Key. These values must be available before continuing. Contact the GSM
Software Distribution and Licensing Center at Motorola, Swindon if there
are any problems.
NOTE
The COP license must be installed correctly. Otherwise, the

COP tools/utility will not function.
Ensure that the Licence Key Alpha/Numeric string is correct,

in every detail, before selecting OK.
Click OK and the license information is confirmed if the license details are
correct.
Continued
68P02900W69-L
GSR10v1.0.10
6-15
Apr 2011
Installing COP
Procedure 6-7 Installing the COP license (Continued)

Figure 6-8 COP Licence window
The following window (Figure 6-9) is displayed on completion of the COP

Licence installation.
Figure 6-9
COP Licence installation complete window
When the installation of the COP Licence is complete, the following message
is displayed:
Press RETURN to return to the CD installer ...
6-16
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
Renewing or upgrading a license using the GUI

To renew the current license or upgrade a temporary license using the GUI, the procedure is
as follows:
Procedure 6-8
Renewing or upgrading a license using the GUI
Log in as user asaadmin and execute the script:

/usr/omc/ne_data/tools/licensing/cop_install_licence.tcl
The COP Licence window is displayed as in Figure 6-8.
Complete the remaining steps of the COP license installation procedure

as described in the section COP License on page 6-15. The upgraded
license applies to any client connected to this OMC-R sharing the
/usr/omc/ne_data partition.
Renewing or upgrading a license using the command line

To renew the current license or upgrade a temporary license using the command line, the
procedure is as follows:
Procedure 6-9 Renewing or upgrading a license using the command line
Log in as user asaadmin and execute the script:

/usr/omc/ne_data/tools/licensing/cop_install_licence.tcl nogui
The COP license screen is displayed as in Figure 6-10.
Figure 6-10 COP license screen - 1
Enter 1.
Continued
68P02900W69-L
GSR10v1.0.10
6-17
Apr 2011
Installing COP
Procedure 6-9 Renewing or upgrading a license using the command line (Continued)
2
Follow the steps shown in Figure 6-11 to complete the renewing or upgrading
of the COP license.
Figure 6-11 COP license screen - 2
After renewing or upgrading of the COP license is completed, Figure 6-12 is

displayed. Enter 2 to exit.
Figure 6-12 COP license screen 3
6-18
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
OTG installation
To install the OMC Tools GUI from the CD-ROM Installer window (Figure 6-22), follow the steps
given in Procedure 6-10:
Procedure 6-10 OTG installation
Select OMC Tools GUI and click Install.

The Machines List window (Figure 6-7) is displayed with a list of processors.
OMC Tools GUI (OTG) will install automatically, without any prompts.
However, it needs to be added to the mouse menu. There are two possible
ways:
If there is a .dt directory in the home directory of the users login name.
If logged in as asaadmin, edit the /home/asaadmin/.dt/dtwmrc or
/home/asaadmin/.dt/C/dtwmrc file and add the lines shown in bold, in
step 4, at the correct place in the right mouse button menu.
If there is no .dt directory in the home directory of the users login

name.
Open a separate xterm window, log in as user root, edit the file
/etc/dt/config/C/sys.dtwmrc to add the lines shown in bold, in
step 4, at the correct place in the right mouse button menu.
Add the lines shown in bold at the correct place in the right mouse button
menu:
Menu DtRightMenu
{
"Utilities" f.title
.
no-label f.separator
"OTG" f.exec "/usr/omc/ne_data/OTG/start_gui.tcl"
Restart the CDE Window Manager to make the OTG addition visible.
Invoking OTG
To invoke the OMC Tools GUI Main Window (Figure 6-13), click the right mouse button to
display the menu and select OTG. Upon acknowledging the security warning message by
clicking the OK button, the Security Warning window is closed.
68P02900W69-L
GSR10v1.0.10
6-19
Apr 2011
Installing COP
Figure 6-13 OTG Main Window
Utility/tools selection
Having installed the OTG, the COP tools (GLU, CAT, CTP, or ECT) must be installed from the
CD-ROM Installer window (Figure 6-22). GLU must be installed next as both CAT and CTP
use GLU for some functionalities.
Select required tool and processor

To select one of the tools and a target processor, execute the following the procedure:
Procedure 6-11 Selecting required tool and processor
Select the required tool (GLU, CAT, CTP, or ECT) and click Install.
Go to tool installation procedures

Go to the appropriate procedures for each tool:
Then...
If...
Generic Lookup Utility (GLU)
Go to GLU installation, and then to Installation

complete.
Continued
6-20
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
Then...
If...
Cell Analysis Tool (CAT)
Go to CAT installation, and then to Installation

complete.
Call Trace Product (CTP)

(Non-OMC)
If installing CTP on a non-OMC machine, enter:

cd /cdrom/cdrom0
./install_CTP
The non-OMC CTP installation is complete.
Call Trace Product (CTP)
Go to CTP installation, and then to Installation

complete.
Event Counting Tool (ECT)
Go to ECT installation, and then to Installation

complete.
GLU installation
If Generic Lookup Utility and a target machine are selected in the Utility/tools selection
procedure, then GLU installs automatically, without any prompts.
A Status window (Figure 6-14) is displayed to show progress.
Figure 6-14 An example of the Status window
When installation is complete, press RETURN. In response, the CD Installer window is

displayed again.
CAT installation
If Cell Analysis Tool and a target machine are selected in the Utility/tools selection
procedure, then the CAT installation starts.
68P02900W69-L
GSR10v1.0.10
6-21
Apr 2011
Installing COP
To complete CAT installation, follow this procedure:
Procedure 6-12 CAT installation
Reply to any prompts until the CAT Configuration window (Figure 6-15) is
displayed. The temporary directory is automatically set to the recommended
location. If the recommended location cannot be used, specify a new path
name. Then click Ok.
Continued
6-22
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
Procedure 6-12 CAT installation (Continued)

Figure 6-15 CAT Configuration window
Continued
68P02900W69-L
GSR10v1.0.10
6-23
Apr 2011
Installing COP
Procedure 6-12 CAT installation (Continued)

2
The installation script checks whether statistics are turned on in the PM

database. If any required statistics are off, the following prompts are
displayed:
Some statistics were found that need turning on.
Leaving these statistics turned off will reduce the accuracy of
CAT's reports.
Select an option from below
1. Investigate stats using a CAT GUI
2. Turn all required CAT stats on (this may take a while)
3. Leave all of the CAT required stats off
Select the appropriate option.

If option 1 is selected, the CAT Missing Statistics Viewer window is
displayed. For further information on this window, see the Display section
in the CAT chapter in System Information: Cell Optimization Product
(68P02900W90).
If option 2 is selected, CAT attempts to turn on all the required statistics at
all the BSCs.
If option 3 is selected, all statistics are left as they are.
NOTE
For best results from CAT, turn on all the statistics required.
The set required will be a small subset of the statistics that are
available. Remember, if all the required statistical options are not
selected, then do not expect a meaningful output.
4
6-24
Go to the Setting up CAT section, in this chapter, to set up the required

statistics.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
CTP installation
If Call Trace Product and a target machine are selected in the Utility/tools selection procedure,
CTP installation starts.
To complete CTP installation, follow this procedure:
Procedure 6-13 CTP installation
The CTP Cron Setup window (Figure 6-16) is displayed for the optional setting
up of the Collect cron job.
Figure 6-16 cron job setup window
If no cron job is required, select Cancel. To set up the cron job, select
Everyday; select a suitable time; select Done.
The CTP Information window is displayed with this message:

Cron entry has been saved.
Click OK.
The CTP Installation window is displayed with this message:

CTP Installation has deleted an automatic generation
of single BCCH list Cron entry from hostname.
Click OK.
The CTP Cron Setup window (Figure 6-16) is displayed again but with the
message:
Select the day and time to update BCCH list
68P02900W69-L
If no cron job is required, select Cancel. To set up the cron job, select
Everyday; select a suitable time; select Done.
When the Call Trace Product window is displayed, press RETURN to return
to the CD installer.
GSR10v1.0.10
6-25
Apr 2011
Installing COP
NOTE
CTP installation may take a long time for a large MIB database (that is, one with more
than 70 K of carriers).
ECT installation
NOTE
Before trying to install ECT, make sure that the GUI Server has been configured as
described in GUI Server configuration for ECT. The GUI Server shared memory
should be set up correctly before launching ECT installation.
If the Event Counting Tool and a target machine are selected in the Utility/tools selection
procedure, then a warning dialog box is displayed.
Figure 6-17 COP Security Warning
ti-gsm-COP Security Warning-0 001a-ai-sw
6-26
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Installing COP
After user clicks OK button in the dialog box, the ECT Installer window (Figure 6-18) is
displayed.
Figure 6-18 ECT Installer window
68P02900W69-L
GSR10v1.0.10
6-27
Apr 2011
Installing COP
ECT full installation

To complete full ECT installation, follow this procedure:
Procedure 6-14 ECT full installation
From the ECT Installer (Figure 6-18), select ECT Full Installation and
then Continue.
A window is displayed with this message:

Ready to install...
The ECT Full Installation...
do you wish to proceed?
Select OK.
The ECT Information window is displayed with this message:

Cron Entry for ectRunCel has been removed successfully in
machine <hostname>
Select OK.

Java binaries are already installed, do you want to overwrite?
Select Yes.
The ECT Install Status window is displayed with this message:
Installing Java binary files
Please wait...
When the Java binary files have been installed, a window may be displayed
with this message:
The pgsql source directory /gen/tools already exists
do you wish to reinstall?
Select Yes.
The following message is displayed:
Installing postgreSQL package.
Please wait...
Creating ECT database...

Running ECT Configuration GUI.
Please wait...
Please insert the Ev_logs location
Select OK.
Continued
6-28
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-14
7
Installing COP
ECT full installation (Continued)
The ECT Configuration window (Figure 6-20) is displayed.
Figure 6-19 ECT Configuration window
Click Add OMC.

Insert the name of the OMC-R from which data will be collected and press
Enter or Tab; the IP Address should be updated automatically.
Continued
68P02900W69-L
GSR10v1.0.10
6-29
Apr 2011
Installing COP
Procedure 6-14
Figure 6-20 ECT Configuration window: OMC-R details
Insert a user who is enabled to sftp files from the OMC-R (usually it is
asaadmin).
Click Test to check that the fields have been entered correctly.
Click Save to apply the changes.
NOTE
Consult the ECT Configuration window section in System
Information: Cell Optimization Product (68P02900W90) to learn
how to configure other ECT parameters. You can postpone ECT
tuning until later.
Continued
6-30
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-14
Installing COP
If you are installing on SPARC ULTRA5 GUI Server, select Database

Settings tab and the window is displayed as in Figure 6-21.
Figure 6-21 ECT Configuration window: Database Settings
Use the slide bar to set the maximum acceptable level of disk usage to 50%
and click Save to apply the changes.
8
Click Cancel to close the window.

The system asks for a confirmation:
Are you sure?
Select Yes.

Do you wish to populate the ECT db with existing event data?
Select Yes to populate the database with the current data. This procedure
could take a little longer (up to 2 hours for an OMC-R with many events).
Select No to populate the database automatically the first time the periodic
data parser runs.
10
The ECT Information window is displayed with the following message:

Adding automatic ECT server startup (every hour) to cronjob.
Please wait...
Cron Entry to automatic server start has been added successfully
Select OK.
Continued
68P02900W69-L
GSR10v1.0.10
6-31
Apr 2011
Installing COP
Procedure 6-14
11

Adding automatic /gen size check partition (every hour) to
cronjob.
Please wait...
Cron Entry to check gen partition has been added successfully
Select OK.
12

Do you want to start ECT Server now?
Select YES or NO.
NOTE
If you select NO, you will have to start the server later, as
explained in the Starting ECT server section in System
Information: Cell Optimization Product (68P02900W90).

13

ECT server installation completed
Select OK.
14
The ECT Installer window (Figure 6-18) is redisplayed.

Select Cancel.
ECT client installation

To complete ECT client installation, follow this procedure:
Procedure 6-15
ECT client installation
From the ECT Installer (Figure 6-18), select ECT Client GUI and then
Continue.

Ready to install...
The ECT User Interface
...
do you wish to proceed?
Select OK.

Java binaries are already installed, do you want to overwrite?
Select Yes.
The ECT Install Status window is displayed with this message:
Installing Java binary files
Please wait...
Continued
6-32
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-15
4
Installing COP
ECT client installation (Continued)

ECT GUI client installation completed
Select OK.
Installation complete
When the installation of a tool/utility is complete, the following message is displayed:
### installation complete

(Where ### is either OTG/GLU/CAT/CTP/ECT)
Follow this procedure:
Procedure 6-16 Installation complete
If the installation completed message is not displayed, uninstall the

appropriate utility/tool as described in the Backout section of this chapter,
and repeat the installation.
NOTE
If further utility/tools are required then repeat from Utility/tools
selection.
2
When all required tools/utility have been installed, click Exit, and enter the
following commands:
cd
eject cd
Remove the CD-ROM and store in a secure place.
To return to asaadmin, enter exit and press RETURN.

Ensure that the window is active, and press RETURN.
Invoking COP
Invoke the utility/tool by clicking the appropriate icon in the OMC Tools GUI Main Window,
Figure 6-13.
68P02900W69-L
GSR10v1.0.10
6-33
Apr 2011
Post-installation procedures
Introduction to post-installation procedures

The following checks and configuration procedures must be performed when COP installation is
complete:
Adjust cronjob timings: Check and configure cronjobs.
Auto Tune feature: Update CAT using Auto Tune.
Configure the mouse menu for COP Tools GUI: Customize the mouse pop-up menu.
Adjust COP cronjob timings

The system administrator is advised to check and configure (where necessary) the COP cronjobs
post installation to avoid the omc_db_maint process.
To check and configure COP cronjobs, follow this procedure:
Procedure 6-17 Checking and configuring COP cronjobs
Log in as asaadmin on the GUI Server upon which COP is installed.
Type:
crontab -l
Make a note of the times of the cronjobs.
Log in as omcadmin on the system processor.
Type:
crontab -l | grep omc_db_maint
Make a note of the start time of the omc_db_maint cronjob.
Check the latest execution time of omc_db_maint by entering:

cd /usr/omc/logs
ls -ltr
cat omc_db_maint.<latest date>
Make a note of the end time of the cronjob.
Continued
6-34
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-17 Checking and configuring COP cronjobs (Continued)

6
Adjust the timing of COP cronjobs so that they do not run while
omc_db_maint is executing.
NOTE
Motorola recommends a minimum of 60 minutes between
completion of omc_db_maint and the first execution of any COP
cron.
Auto Tune feature

When the installation is complete, it is recommended that the system administrator should
update CAT using the Auto Tune feature. The following steps are recommended for a simple
Auto Tune implementation:
Procedure 6-18 Auto Tune implementation
Ensure that the Configuration Files option is checked for Only One.
This option is visible from the menu option System Admin CAT
Configuration.
Let the CAT operate for one day so that a meaningful sample of results
data is generated.
Execute the Auto Tune feature to tighten thresholds. This should reduce the
number of rule failures to an acceptable number. The auto tune assesses
network performance from the last 24 hours and adjusts the thresholds
appropriately to reduce the rule failures to show the worst cell faults in
the network.
If the number of rule failures has not reduced sufficiently for optimization
purposes (network operators have differing views on the extent of data
that should be displayed) then adjust throttling to restrict the reporting of
each rule. One recommendation is to report a repetitive rule failure only
once every two hours. To adjust throttling for each rule, select the menu
option System Admin Threshold Management Manually Adjust
Throttles, check the All cell types and Whole of current rule set options
and apply a throttle count of 3 (for 3 intervals).
Continued
68P02900W69-L
GSR10v1.0.10
6-35
Apr 2011
Procedure 6-18 Auto Tune implementation (Continued)

5
After 24 hours repeat the execution of the Auto Tune feature.
NOTE
For advanced network operators, there is an option to have one
configuration file per day. In this case it is recommended that CAT
is executed for 7 days and then the Auto Tune executed once each
day for 7 days thereafter to tune each individual configuration
files.
For CAT System Admin password and other information, see System Admin in the CAT chapter
in System Information: Cell Optimization Product (68P02900W90).
Configure the mouse menu for COP Tools GUI

To customize the mouse pop-up menu to run the COP Tools GUI, follow these steps:
Procedure 6-19
Customizing the mouse pop-up menu
Log in to the GUI Server where COP has been installed, as the user you
want to customize.
Type the command:

cd $HOME/.dt
Verify that the file called dtwmrc exists. If it exists, make a backup copy:
cp dtwmrc dtwmrc.orig
Copy the file /etc/dt/config/C/sys.dtwmrc into the user home directory

(in the .dt folder):
cp /etc/dt/config/C/sys.dtwmrc $HOME/.dt/dtwmrc
Continued
6-36
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-19 Customizing the mouse pop-up menu (Continued)

5
Modify the file by adding the following lines to the section Menu
DtRightMenu:
"COP Tools GUI"
f.exec
"/usr/omc/ne_data/OTG/start_gui.tcl"
no-label
f.separator
The resulting file is as follows (for the section Menu DtRightMenu):
Menu DtRightMenu
{
"Utilities" f.title
"OMC Database Utilities"f.menu OMC_DB_utils
"Calculator" f.action Dtcalc
"Filemanager" f.action DtfileHome
"Texteditor" f.action
Dtpad
"COP Tools GUI"
f.exec "/usr/omc/ne_data/OTG/start_gui.tcl"
"Answerbook" f.exec "/usr/dt/bin/answerbook2 &"
"Sun Tools
Manual"f.exec "helpopen handbooks/top.toc.handbook"
no-label
f.separator
"X Editor" f.exec "/usr/openwin/bin/xedit &"
"VI Editor"f.exec "/usr/dt/bin/dtterm -title vi -e vi&"
"X Load" f.exec "/usr/openwin/bin/xload"
"Unix Manual" f.exec "/usr/openwin/bin/xman"
"Lock Screen" f.exec "/usr/openwin/bin/xlock"
}
68P02900W69-L
Save the file and restart the Window Manager by clicking the left mouse
button on the desktop, and select Restart
GSR10v1.0.10
6-37
Apr 2011
GUI Client setup

The following procedure explains how to set up a GUI Client to run the COP application from
a GUI Server.
It is assumed that:
COP has already been installed on the GUI Server.
The GUI Client machine belongs to the same domain as the GUI Server and is running NIS.
This is to ensure that hostnames and usernames are known to both Server and Client.
The username used to run COP on the GUI Server is the same username which will be
used on the GUI Client system.
The following procedures can be repeated for each GUI Client required.
GUI Server
On the GUI Server, follow this procedure:
Procedure 6-20
6-38
GUI Server
Log in as root.
Create a file in /usr/omc/ne_data/tools called:

start_COP_on_GUI_Client
Add the following lines:

setenv DISPLAY GUI_Client:0.0
/usr/omc/ne_data/OTG/start_gui.tcl
Save the file.
Log out.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
GUI Client
On the GUI Client, follow this procedure:
Procedure 6-21 GUI Client
If the home directory for username has not been mounted from the
omc_splat then create one.
Log in as user root and enter the following commands:

mkdir /home/username
chown username /home/username
Edit the /etc/dt/config/C/sys.dtwmrc file.
NOTE
If the file /home/username/.dt/dtwmrc or /home/username/.
dt/C/dtwmrc exists, then that the file should be edited instead
(logged in as that username).
4
Add the following lines at the end of the Menu DtRightMenu section, above
the line with }:
no-label
f.separator
"COP OTG"
f.exec "xhost +; ssh GUI_Server source
/usr/omc/ne_data/tools/start_COP_from_GUI_Client "
Example:
Menu DtRightMenu
{
"Utilities"
f.title
.
.
.
"Lock Screen" f.exec
"/usr/openwin/bin/xlock"
"COP OTG" f.exec "xhost +; ssh GUI_Server source
/usr/omc/ne_data/tools/start_COP_from_GUI_Client "
}
68P02900W69-L
Save the file.
Log out.
Log in as username.
Select the COP OTG option from the right mouse menu to test.
GSR10v1.0.10
6-39
Apr 2011
Backout
Backout
Removal of GLU
NOTE
Before removing GLU consider the effect this may have on other tools in the set
that access GLU files for information.
To remove GLU, the procedure is as follows:
Procedure 6-22 Removing GLU
Log in to the System Processor or GUI Server as asaadmin.
Remove any crontab entry referring to GLU using the standard UNIX
commands.
Remove the GLU directories:

rm -rf /usr/omc/ne_data/GLU
Log out.
Removal of CAT
NOTE
Once CAT has been removed it cannot be upgraded; as all settings are lost.
6-40
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backout
Locate the machine that has the CAT cron job on it by looking at the screen produced by User
Admin Support Details. Then proceed as follows:
Procedure 6-23 Removing CAT
Log in to this machine as asaadmin.
Enter:
crontab -e
This opens the crontab file in edit mode.
Comment out the following line (which is too long to show on one line in this
manual):
20,0,2-23***/usr/omc/ne_data/cell_analysis/bin/catCronjob.sh
>/usr/omc/ne_data/cell_analysis/log/error.log 2>&1
Save the file and exit.
Remove the CAT program:

rm -rf /usr/omc/ne_data/cell_analysis
rm -rf /gen/tools/CAT
Log out.
Removal of CTP
NOTE
Once CTP has been removed it cannot be upgraded, as all settings are lost.
If the long-term distribution data are still required, copy the contents of the da_files directory
(pointed to by the environment variable CTP_DA_DIR) to a separate directory not connected
with the CTP source directory.
To remove CTP, the procedure is as follows:
Procedure 6-24 Removing CTP
Log in on the System Processor or GUI Server as asaadmin.
From the CTP Welcome menu, select Cell Details Single BCCH.
Select Crontab Remove entry in crontab.

Continued
68P02900W69-L
GSR10v1.0.10
6-41
Apr 2011
Backout
Procedure 6-24 Removing CTP (Continued)

4
Click OK.
Click Quit.
From the CTP Welcome menu, select Call Trace.
From the CTP main menu select Distribution Analysis Configure Long
Term Data Collection.
Select Cron Remove.
Click OK.
10
Select File Exit.
11
Remove the CTP directories:

rm -rf /usr/omc/ne_data/CTP
rm -rf /gen/tools/CTP
12
Log out.
Removal of ECT
To remove ECT, the procedure is as follows:
Procedure 6-25 Removing ECT
6-42
Log in to the appropriate System Processor or GUI Server as asaadminn.
Remove any entries in crontab that relate to ECT using:

crontab -e
Stop the server:

/usr/omc/ne_data/ECTv2/ectSer stop
Stop the postgreSQL daemon:

/gen/tools/pgsql/install/pg_wrap stop
Remove the ECT directories:

rm -rf /usr/omc/ne_data/ECTv2
rm -rf /gen/tools/pgsql
Log out.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backout
Removal of OTG
To remove OTG, proceed as follows:
Procedure 6-26 Removing OTG
68P02900W69-L
Log in on the System Processor or GUI Server as asaadmin.
Remove the OTG directories:

rm -rf /usr/omc/ne_data/OTG
Log out.
GSR10v1.0.10
6-43
Apr 2011
Backing up COP
Backing up COP
This section describes the procedure to perform a COP backup on the GUI Server using the
backup_COP utility. The utility is able to perform Local Machine Disk Backup (LMDB), Remote
Machine Disk Backup (RMDB), Local Machine Tape Backup (LMTB) and Remote Machine Tape
Backup (RMTB). All the procedures are outlined in the following sections.
Prerequisites
The following procedure shows the guidelines to disable COP cronjobs. The following commands
have to be executed by asaadmin:
Procedure 6-27 Disabling COP cronjobs
Log on to the GUI Server as asaadmin.

./disableCopCronjobs.sh
cd /usr/omc/ne_data/tools/
Disabling asaadmin COP cronjobs:

Do you want to be prompted for GUI Servers' crontab modification
(Y/N) [N] ? y
Getting list of connected hosts...
...found host [mmis28], do you want to search for COP cronjob
and remove it? (Y/N) [Y] ? y
COP cronjob removal DONE on mmis28
NOTE
Make a note of the host name where the cronjob has been disabled.
The host name from the previous example is mmis28.
6-44
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP
Follow Procedure 6-28 to kill all COP processes.
Procedure 6-28
Killing COP processes

./stopCopProcess.sh

Stopping CAT processes:
==========================================================
asaadmin
8392
8391
0 15:41:21 ?
0:00 csh -c
/usr/omc/ne_data/cell_analysis/bin/catGUI.sh
-display 10.228.114.73:0.0
asaadmin
8410
8392
0 15:41:21 ?
0:00 /bin/sh
/usr/omc/ne_data/cell_analysis/bin/catGUI.sh
-display 10.228.114.73:0.0
asaadmin
8493
8410
1 15:41:27 ?
0:01 /usr/omc/ne_data/tools/cop_tcl/bin/wish8.4
/usr/omc/ne_data/cell_analysis/bin/c
asaadmin
8252
7156
0 15:41:14 pts/19
0:00 /bin/sh
/usr/omc/ne_data/cell_analysis/bin/sshCatGUI.sh
==========================================================
Do you want to kill above CAT process [Y/N]?y
Stopping CTP processes:
==========================================================
asaadmin
8293
7156
1 15:41:14 pts/19
/usr/omc/ne_data/CTP/CTP_gui
==========================================================
Do you want to kill above CTP process [Y/N]?y
Stopping ECT processes:
==========================================================
asaadmin
8334
7156
0 15:41:16 pts/19
0:00 /bin/sh /usr/omc/ne_data/ECTv2/ectUi

==========================================================
Do you want to kill above ECT process [Y/N]?y
Continued
68P02900W69-L
GSR10v1.0.10
6-45
Apr 2011
Backing up COP
Procedure 6-28 Killing COP processes (Continued)

==========================================================
asaadmin
8066
0 15:37:16 ?
0:00 /gen/tools/pgsql/bin/postmaster D/gen/tools/pgsql/data -p5432 -i -c silent_mod

asaadmin
8069
8066
0 15:37:16 ?

asaadmin
8174
8066
0 15:38:22 ?

asaadmin
8068
8066
0 15:37:16 ?

asaadmin
8071
8066
0 15:37:16 ?

asaadmin
8070
8066
0 15:37:16 ?

asaadmin
8171
8066
0 15:38:22 ?
0:00 /gen/tools/pgsql/bin/postmaster D/gen/tsools/pgsql/data -p5432 -i -c silent_mod

==========================================================
Stopping GLU processes:
==========================================================
asaadmin
8326
8306
0 15:41:16 pts/19
gluGui.tcl setenv LRUAGE 1 # Address
==========================================================
Do you want to kill above GLU process [Y/N]?y
2
6-46
Ensure that all the COP processes are killed.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP
Prerequisites for tape backup

Before performing a tape backup either locally or remotely from the GUI server, label the
tape and insert into the DAT tape drive. If there is no internal tape drive in a machine, follow
Procedure 6-29 to attach an external tape drive:
Procedure 6-29 Attaching an external tape drive to a machine
As user root on the machine where the external tape drive is attached,
execute the following command and ensure that it is completed without
errors:
devfsadm
Insert a tape into the external tape drive and ensure the functionality of the
tape drive by executing the following command:
mt f /dev/rmt/0 status
NOTE
If there is more than one backup drive attached to the machine, the
tape device name might not be /dev/rmt/0. Check with the system
administrator for the correct tape device name.
Use the following procedure to verify that the archived files in the tape can be read.
Procedure 6-30 Tape drive archive verification
Insert a tape into the DAT drive
Verify that the tape can be read as follows:

tar tvf /dev/rmt/0
Local Machine Disk Backup on the GUI Server

A complete disk backup can be performed automatically using the backup_COP utility. This
utility can be used to perform a local disk backup at the GUI Server as outlined in the following
procedure.
Procedure 6-31 Local Machine Disk Backup
Log on to the GUI Server as root.

Continued
68P02900W69-L
GSR10v1.0.10
6-47
Apr 2011
Backing up COP
Procedure 6-31 Local Machine Disk Backup (Continued)

2

./backup_COP
The following menu is displayed:
cd /usr/omc/ne_data/tools
----------------------------------------------Please select which COP Tools to be backed up

----------------------------------------------CAT) Cell_Analysis_Tool
CTP) Call_Trace_Product
ECT) Event_Counting_Tool
GLU) Generic_Lookup_Utility
A|ALL) ALL Tools Listed Above
----------------------------------------------Q|QUIT) Quit Utility
----------------------------------------------Any combination can be selected by separating them with comma
(eg: cat,glu)
----------------------------------------------Enter Choice :
Enter A to back up all the COP tools. The following message is displayed:
GLU,ECT,CTP,CAT tool(s) selected.

----------------------------------------------Please select the detected backup type
----------------------------------------------LMDB) Local Machine Disk Backup
(Local disk backup is valid)
RMDB) Remote Machine Disk Backup
(Remote omc_splat machine backup is valid)
LMTB) Local Machine Tape Backup
(Local tape device /dev/rmt/0 may not be valid)
RMTB) Remote Machine Tape Backup
(Remote tape device /dev/rmt/0 on omc_splat is valid)
----------------------------------------------B|BACK) Back
Q|QUIT) Quit Utility
----------------------------------------------Enter Choice :
Continued
6-48
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP
Procedure 6-31 Local Machine Disk Backup (Continued)

Enter LMDB to back up to the local machine. The following message is
displayed:
----------------------------------------------Local Disk Path (Default is /tmp,press Enter for default.)

----------------------------------------------B|BACK) Back
----------------------------------------------Enter Local Disk Path :
Press Enter to back up to the default directory (/tmp). The following message
is displayed:

Local Machine Disk Backup is selected
The backup disk path is /tmp
Note that you are not allowed to interrupt the backup process
once it is launched.
Do you want to start the backup now? [Y/B] (B to Back):
Enter Y to start backup. The following message is displayed:
Performing data backup... Ok!

Checking data integrity between the source and target... Ok!
Number of file(s) in /tmp/COP_BACKUP_091908112703.tar.gz is 4434
Number of file(s) in /usr/omc/ne_data/cell_analysis /usr/omc
/ne_data/CTP
/gen/tools/pgsql /usr/omc/ne_data/ECTv2 /usr/omc/ne_data/GLU
is 4434
COP Backup is successful!
Backup File Location: /tmp/COP_BACKUP_091908112703.tar.gz
Press Enter to continue...
Press Enter to return to the main menu.
68P02900W69-L
GSR10v1.0.10
6-49
Apr 2011
Backing up COP
Remote Machine Disk Backup to the OMC-R Server

A complete disk backup can be performed automatically using the backup_COP utility. This
utility can be used to perform a remote disk backup to the OMC-R Server as outlined in the
following procedure.
Procedure 6-32
Remote Machine Disk Backup

./backup_COP

(eg: cat, glu)
----------------------------------------------Enter Choice :
(Local tape device /dev/rmt/0 may not valid)
Continued
6-50
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP
Procedure 6-32 Remote Machine Disk Backup (Continued)

----------------------------------------------B|BACK) Back
----------------------------------------------Enter Choice :
Enter RMDB to back up to the remote machine. The following message is
displayed:
----------------------------------------------Remote Machine Hostname (Default is omc_splat, press Enter

for default.)
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Remote Machine Hostname :
Press Enter to back up to default remote host (omc_splat). The following
message is displayed:
Remote machine omc_splat verified.
----------------------------------------------Remote Disk Path (Default is /tmp,press Enter for default.)
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Remote Disk Path:
Press Enter to back up to the default directory (/tmp). The following message
is displayed:
Remote Machine Disk Backup is selected
The backup disk path is /tmp in omc_splat
Continued
68P02900W69-L
GSR10v1.0.10
6-51
Apr 2011
Backing up COP
Procedure 6-32 Remote Machine Disk Backup (Continued)

Enter Y to start backup. The following message is displayed:

Checking data integrity between the source and target... Ok!
Number of file(s) in /tmp/COP_BACKUP_091908113609.tar.gz is 4434
Number of file(s) in /usr/omc/ne_data/cell_analysis /usr/omc
/ne_data/CTP
/gen/tools/pgsql /usr/omc/ne_data/ECTv2 /usr/omc/ne_data/GLU
is 4434
Backup File Location: omc_splat:/tmp/COP_BACKUP_091908113609.tar.gz
Local Machine Tape Backup on the GUI Server

A complete tape backup can be performed automatically using the backup_COP utility. This
utility can be used to perform a local machine tape backup on the GUI Server as outlined
in the following procedure.
Procedure 6-33
Local Machine Tape Backup

./backup_COP

Continued
6-52
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-33
Backing up COP
Local Machine Tape Backup (Continued)

(eg: cat, glu)
----------------------------------------------Enter Choice :
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Choice :
Enter LMTB to back up to a tape on the local machine. The following message
is displayed:
----------------------------------------------Valid Backup Tape Types(Default is DAT,press Enter for default.)

----------------------------------------------Continued
68P02900W69-L
GSR10v1.0.10
6-53
Apr 2011
Backing up COP
Procedure 6-33
D|DAT) DAT
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Backup Tape Type (D) :
Press Enter to back up to the default tape type (DAT). The following message
is displayed:
----------------------------------------------Is there a writable DAT tape loaded in the Tape Drive ??

(Default is YES, press ENTER for default.)
----------------------------------------------Y|YES) Continue
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Choice (Y):
Press Enter to proceed to back up. The following message is displayed:
----------------------------------------------Local Tape Device (Default is /dev/rmt/0,press Enter for default.)

----------------------------------------------B|BACK) Back
----------------------------------------------Enter Local Tape Device :
Press Enter to select the default tape drive. The following message is
displayed:
Local Machine Tape Backup is selected
The backup tape path is /dev/rmt/0
Create a new tape archive, existing tape content will be overwritten
Continued
6-54
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Procedure 6-33
Backing up COP
Enter Y to start the backup. The following message is displayed:
REWINDING TAPE....
Checking data integrity between the source and target.
Please wait... (This may take several minutes) Ok!
Size of the source is 10057863
Size of the target is 10057863
Backup File Location: /dev/rmt/0:COP_BACKUP_092108233200.tar.gz
REWINDING TAPE....
Remote Machine Tape Backup to the OMC-R Server

A complete tape backup can be performed automatically using the backup_COP utility. This
utility can be used to perform a remote machine tape backup to the OMC-R Server as outlined
in the following procedure:
Procedure 6-34 Remote Machine Tape Backup

./backup_COP

Continued
68P02900W69-L
GSR10v1.0.10
6-55
Apr 2011
Backing up COP
Procedure 6-34 Remote Machine Tape Backup (Continued)

(eg: cat,glu)
----------------------------------------------Enter Choice :


----------------------------------------------B|BACK) Back
----------------------------------------------Enter Choice :
Enter RMTB to back up to a tape on the remote machine. The following
----------------------------------------------Remote Machine Hostname(Default is omc_splat, press

Enter for default.)
----------------------------------------------B|BACK) Back
----------------------------------------------Continued
6-56
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP

Enter Remote Machine Hostname :
Press Enter to select the default remote machine (omc_splat). The following
----------------------------------------------Valid Backup Tape Types(Default is DAT, press Enter for default.)
----------------------------------------------D|DAT) DAT
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Backup Tape Type (D) :
Press Enter to back up to the default tape type (DAT). The following message
is displayed:
----------------------------------------------Is there a writable DAT tape loaded in the Tape Drive ??
(Default is YES, press ENTER for default.)

----------------------------------------------Y|YES) Continue
----------------------------------------------B|BACK) Back
----------------------------------------------Enter Choice (Y):
Press Enter to proceed to back up. The following message is displayed:
Remote machine omc_splat verified.

----------------------------------------------Remote Tape Device (Default is /dev/rmt/0, press Enter for default.)
----------------------------------------------B|BACK) Back
----------------------------------------------Continued
68P02900W69-L
GSR10v1.0.10
6-57
Apr 2011
Backing up COP

Enter Remote Tape Device :
Press Enter to select the default tape drive. The following message is
displayed:

Remote Machine Tape Backup is selected
The backup tape path is /dev/rmt/0 in omc_splat
Create a new tape archive, existing tape content will be overwritten
Note that you are not allowed to interrupt the backup
process once it is launched.
Enter Y to start the backup. The following message is displayed:
REWINDING TAPE....
Checking data integrity between the source and target.
Please wait... (This may take several minutes) Ok!
Size of the source is 52357409
Size of the target is 52357409
Backup File Location:
omc_splat:/dev/rmt/0:COP_BACKUP_091908115708.tar.gz
REWINDING TAPE....
6-58
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Backing up COP
Post Backup Procedures

The following commands need to be executed to enable the cronjob which has been disabled:
Procedure 6-35 Enabling Cronjob

./enableCopCronjobs.sh
Enabling asaadmin COP cronjobs:

(Y/N) [N] ? Y
and restore it? (Y/N) [Y] ? Y
COP cronjob restore DONE on mmis28
NOTE
Take note of the host name where the cronjob has been enabled.
The host name from the previous example is mmis28.
3
Ensure that the ECT server is started by executing the following commands:
cd /usr/omc/ne_data/ECTv2
ectSer start
68P02900W69-L
GSR10v1.0.10
6-59
Apr 2011
Upgrading
Upgrading
Starting the upgrade process

The procedure for starting the upgrade process is as follows:
Procedure 6-36 Starting the Upgrade
On the GUI Server with a CD-ROM drive, log in as asaadmin. Check that the
DISPLAY environment variable is correctly set to the operators display:
echo $DISPLAY
If there is an error:
DISPLAY: Undefined variable
set DISPLAY to the IP address for the terminal being used.
Change to root.
su
When prompted, enter the root password.
Insert the Cell Optimization Product CD-ROM into the drive.
Enter:
cd /cdrom/cdrom0
./Install
The following prompt is displayed:

Are you sure you want to continue (Y/N) [N] ?
Enter Y.
NOTE
If the TCL processes are currently used by other users, the
following prompt will be displayed:
TCL active processes detected. It currently
been used by others.
Are you sure you want to kill all the
TCL processes (Y/N) [N] ?
Enter Y to terminate all the TCL processes and continue

installation. Otherwise, installation will be aborted.
Continued
6-60
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Upgrading
Procedure 6-36 Starting the Upgrade (Continued)

6
The OMC Validation message (Figure 6-4) is displayed.

Select OK.
The OMC Validation Complete message (Figure 6-5) is displayed.

Select OK.
In response, the CD-ROM Installer window, (Figure 6-22) is displayed.
NOTE
The COP license must be upgraded if the existing COP Licence is installed with
GSR7v2.0 or earlier versions. Otherwise, the COP tools/utility do not function.
Selecting a tool for upgrade

The CD-ROM Installer window, (Figure 6-22) contains a list of items that have been installed
(documentation and tools).
Figure 6-22 Motorola CD-ROM Installer window
ti-gsm-Select a tool to install-00004a-ai-sw
68P02900W69-L
GSR10v1.0.10
6-61
Apr 2011
Upgrading
To upgrade a tool from the CD-ROM Installer window, highlight the application you wish to
upgrade and select Upgrade.
Upgrading COP license

To upgrade the COP license from the CD-ROM Installer window (Figure 6-22), follow this
procedure:
Procedure 6-37
Upgrading COP license
Select COP license and click Upgrade. The Machines List window, as in
Figure 6-7, is displayed with a list of processors.
The COP Licence window, as in Figure 6-8 is displayed, which allows the
entry of license Expiry Date and Licence Key. These values must be
available before starting the license upgrade procedure. Contact the GSM
Software Distribution and Licensing Center at Motorola, Swindon if there
are any problems.
NOTE
The COP license must be upgraded correctly. Otherwise, the

COP tools/utility will not function.
Ensure that the Licence Key Alpha/Numeric string is correct.
Click OK if the license details are correct. A window, as in Figure 6-9, is

displayed on completion of the COP license upgrade.
When the installation of COP Licence is complete, the following message
is displayed:
Press RETURN to return to the CD installer ..
6-62
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Upgrading
Upgrading GLU procedure

If the Generic Lookup Utility is highlighted and Upgrade is selected from the CD-ROM
Installer window, follow this procedure:
Procedure 6-38 Upgrading GLU
The GLU Upgrading window, Figure 6-23, is displayed.
Figure 6-23 GLU Upgrading window
Click OK.
2
From this point, the upgrade procedure is the same as the installation procedure described in
the GLU installation section of this chapter.
CAUTION
If GLU is upgraded from a pre-GSR6 version, all files will be overwritten. This means
that the Remote OMCs list will be lost.
68P02900W69-L
GSR10v1.0.10
6-63
Apr 2011
Upgrading
Upgrading CAT procedure

If the Cell Analysis Tool is highlighted and Upgrade is selected from the CD-ROM Installer
window, follow this procedure:
Procedure 6-39 Upgrading CAT
NOTE
If the CAT cronjob process is currently used by other users, a
message prompt is displayed as in Figure 6-24.
Figure 6-24 CAT upgrading message
Users are not allowed to proceed with the upgrade when CAT is being used.
To proceed with the upgrade, ensure that all the CAT GUI windows are
closed.
To ensure that CAT cronjob is not running, execute the command kill -9
<process id> to kill the following processes:
/usr/omc/ne_data/cell_analysis/bin/catCronjob.sh
/usr/omc/ne_data/cell_analysis/bin/catRunJava.sh
CatEngine.jar
Continued
6-64
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Upgrading
Procedure 6-39 Upgrading CAT (Continued)

2
If the thresholds on the upgrade CD-ROM are the same as the currently
installed version of CAT, then the process requires no user intervention and
the following message is displayed:
CAT upgrade complete
Select RETURN.
If the thresholds on the upgrade CD-ROM are different from the currently
installed version of CAT, then see Modified thresholds.
Modified thresholds
If any thresholds have been modified by the user then the CAT Threshold Upgrader window
(Figure 6-25) is displayed. By default the current thresholds are retained. Click OK.
If the user wishes to use the CAT defaults on the upgrade CD-ROM, highlight the rule in the left
column and move it to the right column using the >> direction arrow button.
68P02900W69-L
GSR10v1.0.10
6-65
Apr 2011
Upgrading
Figure 6-25 CAT Threshold Upgrader window
6-66
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Upgrading
Detail window
To investigate the differences between the existing thresholds and the CAT defaults on the
upgrade CD-ROM, double click the appropriate rule in the CAT Threshold Upgrader window and
the window will be replaced by the CAT Threshold Upgrader - Detail Screen window, Figure 6-26.
Figure 6-26 CAT Threshold Upgrader - Detail Screen window
Upgrading CTP procedure

If the Call Trace Product is highlighted and Upgrade is selected from the CD-ROM Installer
window, the upgrade procedure is the same as the installation procedure described in the CTP
installation section of this chapter.
68P02900W69-L
GSR10v1.0.10
6-67
Apr 2011
Upgrading
Upgrading ECT procedure

If the Event Counting Tool is highlighted and Upgrade is selected from the CD-ROM Installer
window, a warning dialog box is displayed (see Figure 6-27).
Figure 6-27 COP Security Warning
ti-gsm-COP Security Warning-0 001a-ai-sw
After the user clicks OK button in the dialog box, the ECT upgrade process starts. A window
(see Figure 6-28) is displayed to show the progress of the upgrade.
NOTE
Ensure that the PostgreSQL server is running before the upgrade. Execute the
following command to check the existence of the PostgreSQL:
ps -ef | grep postmaster
6-68
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Figure 6-28
Upgrading
ECT Upgrade window
If you are using SPARC ULTRA5 GUI Server, /gen directory may actually use / (root) file system
as it was not set up as a separate file system in the machine. It is recommended to perform the
precaution steps as in Procedure 6-40 to make sure that the ECT database does not affect the
root directory.
Procedure 6-40 SPARC ULTRA5 GUI Server precaution steps
Log in to the GUI Server as user asaadmin.
Execute the following command:

Launch ectUi using the following command:

./ectUi
Select Administration Login and enter the asaadmin password. Click

OK.
Select Administration ECT Config and select Database Settings tab.
Use the slide bar to set the maximum acceptable level of disk usage to 50%
and click Save to apply the changes.
For the ECT Configuration password and configuration information, refer to the ECT
Configuration window in the ECT chapter in System Information: Cell Optimization Product
(68P02900W90).
68P02900W69-L
GSR10v1.0.10
6-69
Apr 2011
Restoring COP
Restoring COP
Introduction
This section describes how to perform a COP restoration on the GUI Server from the backup
archives created by backup_COP utility. The backup archives are either stored in disk or tape
media.
Prerequisites
The following procedure shows the guidelines to disable COP cronjobs. The following commands
have to be executed by asaadmin:
Procedure 6-41 Disabling COP cronjobs

./disableCopCronjobs.sh
Disabling asaadmin COP cronjobs:

(Y/N) [N] ? y
and remove it? (Y/N) [Y] ? y
COP cronjob removal DONE on mmis28
NOTE
Take note of the host name where the cronjob has been disabled.
The host name from the example previous is mmis28.
6-70
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Restoring COP
The following procedure shows the guidelines to kill all COP processes:
Procedure 6-42
Killing COP processes

./stopCopProcess.sh
Stopping CAT processes:

===================================================================
asaadmin
8392
8391
0 15:41:21 ?
0:00 csh -c /usr/omc
/ne_data/cell_analysis/bin/catGUI.sh -display 10.228.114.73:0.0

asaadmin
8410
8392
0 15:41:21 ?
0:00 /bin/sh /usr/omc
/ne_data/cell_analysis/bin/catGUI.sh -display 10.228.114.73:0.0

asaadmin
8493
8410
1 15:41:27 ?
0:01 /usr/omc
/ne_data/tools/cop_tcl/bin/wish8.4 /usr/omc/ne_data/cell_analysis/bin/c
asaadmin
8252
7156
0 15:41:14 pts/19
/ne_data/cell_analysis/bin/sshCatGUI.sh
===================================================================
Do you want to kill above CAT process [Y/N]?y
Stopping CTP processes:
===================================================================
asaadmin
8293
7156
1 15:41:14 pts/19
0:00 /usr/omc/ne_data
/tools/cop_tcl/bin/wish8.4
/usr/omc/ne_data/CTP/CTP_gui
===================================================================
Do you want to kill above CTP process [Y/N]?y
===================================================================
asaadmin
8334
7156
0 15:41:16 pts/19
/ne_data/ECTv2/ectUi
===================================================================
===================================================================
asaadmin
8066
0 15:37:16 ?
0:00 /gen/tools/pgsql/bin
/postmaster -D/gen/tools/pgsql
/data -p5432 -i -c silent_mod
Continued
68P02900W69-L
GSR10v1.0.10
6-71
Apr 2011
Restoring COP
Procedure 6-42 Killing COP processes (Continued)

asaadmin
8069
8066
0 15:37:16 ?
0:00 /gen/tools/pgsql
/bin/postmaster -D/gen/tools/pgsql
asaadmin
8174
8066
0 15:38:22 ?
asaadmin
8068
8066
0 15:37:16 ?
asaadmin
8071
8066
0 15:37:16 ?
asaadmin
8070
8066
0 15:37:16 ?
asaadmin
8171
8066
0 15:38:22 ?
===================================================================
Stopping GLU processes:
===================================================================
asaadmin
8326
8306
0 15:41:16 pts/19
0:00 /usr/omc/ne_data
/tools/cop_tcl/bin/wish8.4 gluGui.tcl setenv LRUAGE 1 # Address

===================================================================
Do you want to kill above GLU process [Y/N]?y
2
Ensure that all the COP processes are killed.
The following procedure outlines the steps to remove COP:
Procedure 6-43 Remove COP
Remove the GLU directories by executing the following command:

rm -rf /usr/omc/ne_data/GLU
Remove the CAT directories by executing the following commands:

rm -rf /usr/omc/ne_data/cell_analysis
rm rf /gen/tools/CAT
Continued
6-72
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Restoring COP
Procedure 6-43 Remove COP (Continued)

3
Remove the CTP directories by executing the following commands:

rm -rf /usr/omc/ne_data/CTP
rm rf /gen/tools/CTP
Remove the ECT directories by executing the following commands:

rm -rf /usr/omc/ne_data/ECTv2
rm rf /gen/tools/pgsql
Restore COP from disk backup on the GUI Server

After removing the COP directories, the backed up COP can be restored as outlined in the
following procedure:
Procedure 6-44 Restoring COP from disk backup
As asaadmin user, transfer the disk backup archive to GUI Server if the
archive is in the OMC server.
Restore the disk backup archive:

For example, gzip cd COP_BACKUP_092208131012.tar.gz | tar xvf -
Restore COP from tape backup on the GUI Server

After removing the COP directories, the backed up COP can be restored as outlined in the
following procedure:
Procedure 6-45 Restore COP from tape backup on the GUI Server
68P02900W69-L
As asaadmin user, retrieve the backup archive from the machine where the
tape device is attached.
For example, tar -xvf /dev/rmt/0 COP_BACKUP_092208145525.tar.gz
Transfer the backup archive to GUI Server if the archive is in the OMC server.
Restore the disk backup archive.

For example, gzip cd COP_BACKUP_092208145525.tar.gz | tar xvf -
GSR10v1.0.10
6-73
Apr 2011
Restoring COP
Post Restore Procedures

The following commands need to be executed to enable the cronjob which has been disabled:
Procedure 6-46 Enabling Cronjob

./enableCopCronjobs.sh
Enabling asaadmin COP cronjobs:

(Y/N) [N] ? Y
and restore it? (Y/N) [Y] ? Y
COP cronjob restore DONE on mmis28
NOTE
Take note of the host name where the cronjob has been enabled.
The host name from the example previous is mmis28.
3
Ensure that the ECT server is started by executing the following commands:
ectSer start
6-74
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Setting up CAT
Setting up CAT
System Administration
A user can adjust some configuration parameters through the Options, Customize and User
Admin menus. Other configuration parameters can only be set by a CAT system administrator
using the System Admin menu. For more information, see the CAT chapter in System
This section contains procedures for the CAT system administrator.
Auto Tune Thresholds

To use the auto-tune function to change thresholds for rules, proceed as follows:
Procedure 6-47
Changing thresholds for rules using the auto tune function
Select System Admin Threshold Management Auto Tune

Thresholds.
Select all required Rule Sets.
Select, if required, Loosen. (Tighten is the default.)

Loosening results in CAT generating more rule failures.
Tightening results in CAT generating less rule failures.
Click Auto Tune.

When all the thresholds have been recalculated (tuning could take between
2 and 10 minutes) a results window confirms the results of the Auto Tune.
Click Ok.
For the CAT System Admin password and other information, refer to the System Admin in the
CAT chapter in System Information: Cell Optimization Product (68P02900W90).
NOTE
Refer to Post-installation procedures for recommendations on when to run the
auto-tune function.
68P02900W69-L
GSR10v1.0.10
6-75
Apr 2011
Setting up CAT
Manually adjust thresholds and throttles

The following two procedures describe how to manually adjust CAT thresholds and throttles.
These procedures are intended for use by the experienced CAT user who wishes to configure a
bespoke network monitoring environment for a specific monitoring of system performance. For
new CAT users, it is recommended that the auto-tune recommended thresholds combined with
the Motorola default throttle settings be used.
Manually Adjust Thresholds

To manually adjust thresholds, proceed as follows:
Procedure 6-48 Manually adjusting thresholds
Select System Admin Threshold Management Manually Adjust

Thresholds.
Select a rule.
Edit the thresholds as required.
Click Save This Entry.
Repeat steps 2 to 4.
When all the thresholds are correct, click Ok to save any unsaved entries
and close the window.
For further information, see the System Admin (Threshold Management, Manually
Adjust Thresholds) in the CAT chapter in System Information: Cell Optimization Product
(68P02900W90).
Manually Adjust Throttles

To manually adjust throttles, proceed as follows:
Procedure 6-49 Manually adjusting throttles
Select System Admin Threshold Management Manually Adjust

Throttles.
Select a rule.
Edit the throttle as required.

Continued
6-76
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Setting up CAT
Procedure 6-49 Manually adjusting throttles (Continued)

4
Click Save.
Repeat steps 2 to 4.
When all the throttles are correct, click Ok to save any unsaved entries
and close the window.
For further information, see System Admin (Threshold Management, Manually Adjust
Throttles) in the CAT chapter in System Information: Cell Optimization Product (68P02900W90).
Comments
To change the comments that describe rules, proceed as follows:
Procedure 6-50 Changing the comments
Select System Admin Rule Explanation Maintenance.
Select a rule set and rule.
Enter the comments required.
Click Save This Entry.
When all comments are complete, click Ok.
For further information, see System Admin (Threshold Management, Rule Explanation
Maintenance) in the CAT chapter in System Information: Cell Optimization Product
(68P02900W90).
Blacklist
The blacklist feature enables the user to exclude BSSs and cells from the CAT monitor process
so that irrelevant rule failures are not continually reported. For example, the user may choose
to exclude a lab BSS.
68P02900W69-L
GSR10v1.0.10
6-77
Apr 2011
Setting up CAT
To change the system blacklist, proceed as follows:
Cell option
Procedure 6-51 Cell option
Select System Admin System Blacklist Cells.
Select a BSC.
Select any of the cells in it that are to be blacklisted.
Click Save BSC.
Repeat steps 2 to 4 for any other BSCs.
BSC option
Procedure 6-52
BSC option
Select System Admin System Blacklist BSC.
Select the BSC(s) to be ignored.
Click Ok.
For further information, see System Admin (System Blacklist) in the CAT chapter in System
Critical cells
Critical cells must be selected for display on the CAT Scoreboard window.
To select critical cells, proceed as follows:
Procedure 6-53
6-78
Selecting critical cells
Select System Admin Critical Cells.
Select the critical cells.
Click Ok.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Setting up CAT
For further information, see System Admin (Critical Cells) and Display (Scoreboard) in the
Parameters
To change configuration parameters, proceed as follows:
Procedure 6-54 Changing configuration parameters
Select System Admin CAT Configuration.
Select the value required for a parameter.
Click Save
Repeat steps 2 and 3 until all parameters have been set.
Click Ok.
For further information, see System Admin (CAT Configuration) in the CAT chapter in System
Rule sets
To change the rule sets that are visible to the user, proceed as follows:
Procedure 6-55
Changing the rule sets
Select System Admin Valid Rule Sets.
Select the rule sets that are to be available to the user.
Click Save to save the configuration.
For further information, see System Admin (Valid Rule Sets) in the CAT chapter in System
68P02900W69-L
GSR10v1.0.10
6-79
Apr 2011
Changing the ECT configuration
Changing the ECT configuration
Effecting changes
If the OMC-R configuration or blacklist changes, ECT automatically uses the changed data, after
the overnight cron job has been run. The OMC-R system administrator can force ECT to use
the new data immediately by running the appropriate script.
Table 6-2 Forcing ECT to use new OMC-R configuration

Change
Script in /usr/omc/ne_data/ECTv2
Blacklist
ECTGetBlacklist.sh
Alarm text changes
ECTConvertMIT.sh
Window location
It is possible to drag the window using the middle mouse button while holding down the ALT key.
6-80
GSR10v1.0.10
68P02900W69-L
Apr 2011
Chapter
7
Troubleshooting
68P02900W69-L
Apr 2011
GSR10v1.0.10
7-1
Problems and questions
Problems and questions
If a problem occurs during the installation, upgrade, backout, or operation of COP, refer to the
following troubleshooting sections:
Solving COP installer problems.
Solving CAT problems.
Solving CTP problems.
Solving ECT problems.
Motorola contacts
If a resolution to the problem is not found, contact Motorola. The following contact list should
be used, in the following order:
During office hours

Contact the on-site Motorola field support personnel, if available, or the in-country Motorola
office.
Out-of-office hours
Contact the Customer Network Resolution Center:
7-2
EMEA region: +44 1793 565444.
APAC region: +86 10 88417733
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Solving COP Installer problems
Solving COP Installer problems
Possible problems
This section describes some common problems that may be experienced with the COP Installer,
and their solutions.
g_1MmiNames is not set

Installation may terminate with an error message as follows:
g_lMmiNames is not set

There are two probable causes of this error:
There are no GUI Servers attached to the OMC-R.
There are attached GUI Servers, but ssh does not work for all them.
If GUI Servers are attached, then check that the ssh command works for each server by
entering this command:
ssh <GUI Server Name>
If one of the GUI Servers cannot be accessed using ssh, this can cause the install script to fail
when it encounters this GUI Server. If this might be a problem, try temporarily editing the
/etc/dfs/dfstab file to remove this GUI Server; using the # to comment it out.
The COOKIE variable

In certain instances of COP installation on an OMC-R system, the installer may advise the
system administrator that the COOKIE variable is undefined. This occurs when the COP
installation is initiated on a machine accessed using the telnet process. To solve this problem,
set the COOKIE variable to:
COOKIE=cookie_tmp; export COOKIE;
68P02900W69-L
GSR10v1.0.10
7-3
Apr 2011
Solving CAT problems
Possible problems
The following problems may occur:
Table 7-1 CAT problems

Then ...
If ...
After typingcd /cdrom Wait a few seconds to give the CD-ROM time to respond. If the problem
ls
persists, the system was started without a CD-ROM drive connected.
no files are
Reboot the processor with the CD-ROM drive connected. It can then
displayed.
read the CD-ROM.
CAT displays the
wrist watch symbol
every minute,
indicating that it
is doing something.
The UNIX time may be different on the system processor and the
processor on which CAT is installed. UNIX time should be GMT on
both computers. To check it select User Admin Support Details.
The window lists the CAT processors and their UNIX times.
CAT finds no cells or

a reduced number of
cells.
Select Display Redundant Cells. To eliminate redundant cells,

perform a PM Resync from the OMC-R GUI. This command causes the
PM database data to be synchronized with the CM database. CAT will
notice the cells the next time the cron job is executed.
There is no rule fail

count for yesterday
(displayed by
selectingDisplay
Daily Rule Fail
Counts).
Get the CAT system administrator to check which rule sets, if any, are
being monitored. By default, CAT does not perform any rule fail counts.
The daily summary

files do not exist.
Get the CAT system administrator to check which rule sets are being
monitored. By default, CAT does not monitor any rule sets.
The daily average

files do not exist.
Get the CAT system administrator to check which rule sets are being
monitored. By default, CAT does not monitor any rule sets.
Certain users
cannot generate
CAT reports in a
multiple OMC-R
environment.
Create those users on all OMC-Rs. The name of each GUI Server
(where CAT is installed) on each OMC-R, should be set in the
/etc/hosts.equiv or /home/<user>/.rhosts file.
Continued
7-4
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Table 7-1 CAT problems (Continued)

Then ...
If ...
The message CAT
Data missing
or incorrect is
displayed
Perform the following steps:

1.
Log in as the user asaadmin, on each GUI Server execute the

following command:
crontab -l | grep -i cat
Check that a cronjob exists for CAT on one of the OMC-R GUI
Servers and that the cronjob is active (refer to standard Unix
manuals for format of cronjobs).
The CAT hourly

cronjob is too slow
(that is, it takes more
than 15 minutes to
finish).
2.
Change to the directory usr/omc/ne_data/cell_analysis/logs

and view the file named cronjob.log for an indication as to when
the last cronjob was executed.
3.
Change to the directory /usr/omc/ne_data/cell_analysis/logs

and view the file named error.log for an indication as to where
the error occurred.
4.
Contact CNRC with the issue and attach the cronjob.log and
error.log files to the support request ticket.
The reason could be that the throttle calculation requires too much
system resource. Modify the CAT entry in the asaadmin user crontab
such that the option -no_throttle is passed to the catCronjob script.
The entry should read as follows:
20 0,5-23 * * * /usr/omc/ne_data/cell_analysis/
bin/catCronjob.sh -no_throttle>/usr/omc/ne_data/
cell_analysis/log/error.log 2>&1
Use the standard UNIX commands to modify the crontab. This option
will exclude the throttle calculation so all the rule failures will now
be reported the first time.
68P02900W69-L
GSR10v1.0.10
7-5
Apr 2011
Reporting CAT problems

If a problem is detected that cannot be resolved, do as follows:
Procedure 7-1 Reporting CAT problems
In the main window, select User Admin Support Details. This opens the
CAT Telephone Support Details window.
Select File Save to save the contents of the window.
Send the following information to the Customer Network Resolution Center:
The file from the saved window.
A description of the problem.
Version number of the OMC-R software being used.
For the CAT System Admin password and other information, refer to the System Admin in the
7-6
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Solving CTP problems
Possible problems
The following problems may occur with CTP:
Table 7-2 CTP problems

Then ...
If ...
Output does not
match the filters
that have been set.
Recheck the filters. Look at the title of the window to check whether it
mentions anything you do not wish to be included. Check the start and
end dates to check whether they are set accidentally from a previous
action.
BSSAP/ABIS/RR
decode output
does not appear
in the middle of
the timeline display
following a drawing
command.
It is possible that there are no messages associated with that particular

call or part of call. Alternatively, the disk consumed limit may have
been reached. Check on the command line how much disk space is left
using the command:
CTP does not run

because the disk
space limit has been
reached.
Delete unnecessary files from the current disk partition. If this is not
possible edit the CTP_setup_env file and increase the default value
used for CTP_PERCENT_DC if allowed by the Administrator.
CTP complains that

the WORKING or
OUTPUT directories
do not exist.
If CTP is running on an OMC, check that the /gen/tools/CTP/OUTPUT

and /gen/tools/CTP/WORKING directories exist with the appropriate
permissions. If not create them.
If CTP has been installed on another UNIX processor, check that there
are OUTPUT and WORKING directories with full permissions below
the directory where CTP is installed.
Selecting the Collect

function from the
GUI or running
CTP_collect on
the command line
appears to have no
effect.
The CTP Collect function keeps a record of the last Call Trace file it
processed in the files CTP_LAST_DA_BIN and CTP_LAST_DA_TEXT.
It does not process any data before the last file. If older files are copied
in to the Call Trace log directories, they are ignored. To get round
this, delete the files CTP_LAST_DA_BIN and CTP_LAST_DA_TEXT
in the CTP directory. The next collect will process all data in the Call
Trace file directory.
Unable to Save As
output files from
GUI.
CTP output files are always written to the output directory specified by
the environment variable CTP_OUTPUT_DIR. Check this directory for
the output file recently created and copy or rename it as required.
df -k
Continued
68P02900W69-L
GSR10v1.0.10
7-7
Apr 2011
Table 7-2 CTP problems (Continued)

If ...
Then ...
Although Call Trace

files appear to be
present, CTP insists
it cannot read any.
CTP only decodes BSSMAP/RR, DTAP/ABIS and Measurement Reports.

Any files that do not contain such messages are ignored. Also, by
default, Location Updates are ignored.
If files have arrived while the GUI has been running, they may not
have been pre-indexed. To do this, click Update. Check CTP call trace
statistics.
On the commandline CTP keeps

preindexing even
though no new files
are present.
Use the command-line option -nopreindex to stop preindexing

occurring.
The BSSMAP/
ABIS/RR or RSS
template has been
edited, yet the
decode output
ignores it.
The template file that has been created must be selected using
the Templates menu, or added to the command line using the
-templater or -templatea or -templateb option.
The Path Balance

values for a
particular cell
appear wrong.
Is the cell micro or pico? If it is either, the correct BTS nominal value
must be set through the Cell Details menu in the Welcome window.
CTP states there are

too many files.
Reduce the number of Call Trace files in the specified directory to

below 11,000. For example, use CTP_tidy_Ct_logs.
Strange values are

displayed for BTS
and MS Power.
Has the cell configuration been changed recently? If so delete

CTP_cell_details file in the CTP directory. Also run the updata MIB
data option.
Reporting CTP problems

If a problem is detected that cannot be resolved, send the following information to the Customer
Network Resolution Center:
7-8
Version number of the CTP software (from the Help About menu in any window).
A description of the problem.
Version numbers of the OMC and BSS software being used.
The Call Trace files that caused the problem, if possible.
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Solving ECT problems
Possible problems
This section describes some common problems that may be experienced with ECT, and their
solutions.
No data to display
The following message may be seen in the GUI after running the parser:
There is no data to display

There are three possible reasons for this message:
The parsed event data may be older than the data retention period specified in the ECT
Database Settings tab. Thus, the data has been loaded and then the housekeeping process
has summarized the data and discarded the detail. This can be checked by changing to
the historical tab: if events have been excluded during the data parsing then there will be
neither events nor historical events.
The parser may have skipped the file because an invalid COP license was used
to sign' the event log files. Check the first line of the ASCII event log stored in
/usr/omc/ne_data/CEL_files on the OMC and verify that it appears in the form:
<COP_licence_expiry_date, integer value>
(for example, 1-jan-2004,1256)
If the line is missing, check that the COP license daemon is running by starting another
COP Tool and verifying that it starts correctly.
The parser may not have parsed any file because the directory /usr/omc/ne_data/CEL_files
is empty.
Check the asaadmin cronjob on the GUI Server where ECT has been installed by entering
this command:
crontab -l | grep -i ectRunCel
This should retrieve at least one line.
Check that ectRunCel.tcl exists in /usr/omc/ne_data/ECTv2.
68P02900W69-L
GSR10v1.0.10
7-9
Apr 2011
License expiry message still appears after renewal

If the license expiry message is still displayed on the GUI after the license has been removed,
then take the following corrective action:
1.
Log in as asaadmin user on the GUI Server where ECT has been installed.
2.

/usr/omc/ne_data/ECTv2/ectRunCel.tcl
/usr/omc/ne_data/ECTv2/ectPdp -sftp -int
This updates the local license in ECT to the most recent and resolves the problem.
NOTE
This problem is automatically resolved when the daily ectRunCel process executes
followed by a scheduled parser execution.
Run PdpNow button is disabled

If the Run PdpNow button is disabled on the GUI, then the ECT GUI has been started on a
system different from the GUI Server where ECT has been installed. The parser can be executed
only from a platform where ECT Server resides.
NOTE
In normal operation it is not possible to execute the ECT GUI on the system processor.
ECT help does not work

If ECT Help does not work, then it is possible that the current Mozilla files have been corrupted
in the user home directory. To solve the problem, log in as asaadmin and execute the following
commands:
cd /home/asaadmin
rm -rf .mozilla
This corrective action deletes the Mozilla cache and also the settings and bookmarks of the
user. Take care to make a copy of any important information. For example, the problem could
be solved by saving a copy of the settings with the following commands:
cd /home/asaadmin
mv .mozilla .mozilla.copy
7-10
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
ECT application reports server or database issue

If ECT reports a server or database issue, proceed as follows:
Procedure 7-2 Troubleshooting when ECT reports a server or database issue
Locate the GUI Server upon which ECT was originally installed. To do this,
log in as asaadmin and then log into each GUI Server and execute the
following command:
ls -l /gen/tools | grep pgsql
On the machine that returns a directory presence of pgsql, check that the
postmaster daemon is running by typing:
ps -ef | grep post
If no postmaster processes are returned, then the ECT server application is

not running and should be manually started with the command:
/usr/omc/ne_data/ECTv2/ectSer start
ECT application starts but contains no data

If ECT starts but contains no data, proceed as follows:
Procedure 7-3 Troubleshooting if ECT starts but contains no data
Locate the GUI Server where the ECT maintenance cronjobs is installed and
check that it is active. To do this log in as asaadmin into each GUI Server
and type the command:
crontab -l | grep -i ect
On the machine where the postgres database is installed (see the previous
issue for details on how to locate), there should be two cronjobs activated,
namely:
/usr/omc/ne_data/ECTv2/ectRunCel.tcl
/usr/omc/ne_data/ECTv2/ectSer start
The ectRunCel cronjob is responsible for decoding data. The other cronjob
maintains the ECT server application to ensure that it is always running.
3
Check that the PDP is not aborting prematurely due to an incorrectly

resident log file. To do this, enter the following commands:
cd /usr/omc/ne_data/ECTv2/logs
ls -ltr
View the most recent log and look for a message reading:
Pdp exiting: found a lock file.
Continued
68P02900W69-L
GSR10v1.0.10
7-11
Apr 2011
Procedure 7-3 Troubleshooting if ECT starts but contains no data (Continued)

4
If this message is in the log, it means that the PDP is trying to start but
finding an instance of the PDP already running. This may be because the PDP
is already running, a possibility that can be checked using the command:
ps -ef | grep -I pdp
However, it is also possible that the lock file was not removed after the PDP
was aborted prematurely (for example, due to an unexpected system restart).
In this case, locate and clear the log file so that the PDP can now execute.
7-12
GSR10v1.0.10
68P02900W69-L
Apr 2011

Product (COP)
Solving licensing problems
Solving licensing problems
Possible problems
This section describes some common problems that may be experienced with licensing, and
their solution.
When OMC reboots, the license server cannot be started by

user asaadmin
To solve this problem, perform the following steps:
Procedure 7-4 Troubleshooting when OMC reboots and the license server cannot be
started by user asaadmin
68P02900W69-L
Log in to OMC as root.

rm -rf /usr/tmp/lockMOT_CIG
su asaadmin
/usr/omc/ne_data/tools/licensing/start_license_server
GSR10v1.0.10
7-13
Apr 2011
7-14
GSR10v1.0.10
68P02900W69-L
Apr 2011

Software Release Notes Cell Optimization Product (COP) GSR10v1.0.10

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Software Release Notes Cell Optimization Product (COP) GSR10v1.0.10

Загружено:

Авторское право:

Доступные форматы

Cell Optimization Product (COP)

Software Release Notes

2011 Motorola, Inc. All Rights Reserved.

Software Release Notes: Cell Optimization Product (COP)

General information about the release notes . . .

Chapter 1: About this release

Chapter 2: Open issues

Chapter 3: Resolved issues

Chapter 5: Hardware and firmware requirements

Introduction to COP software management . . . . . . .

Chapter 6: Software management

Local Machine Tape Backup on the GUI Server . . .

6-1: Usertool main window . . . . . . . . . . . . . . .

Information provided on the open service requests

Software Release Notes: Cell Optimization

About this Document

Issue L - COP GSR 10v1.0.0

Issue L - COP GSR 10v1.0.6

Issue L - COP GSR 10v1.0.7

Issue L - COP GSR 10v1.0.8

Issue L - COP GSR 10v1.0.9

Issue L - COP GSR 10v1.0.10

Resolution of Service Requests

Incorporation of Change Notices

Software Release Notes: Cell Optimization

Document banner definitions

About this Document

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.

Software Release Notes: Cell Optimization

Contacting Motorola Solutions

Contacting Motorola Solutions

Motorola Solutions appreciates feedback from the users of our documents.

Ordering documents and CD-ROMs

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

About this Document

General information about the release notes

Chapter 1: About this release

General information about the release notes

Introduction to the COP release

Software Release Notes: Cell Optimization

General information about this software

General information about this software release

Nomenclature, release load identification

the version number.

the revision number.

Chapter 1: About this release

Release load identifier.

Ensure that the CD-ROM is mounted on each processor.

Enter the following commands:

Software Release Notes: Cell Optimization

All file checksums verify ok !

Chapter 1: About this release

Introduction to new features

GLU has been enhanced to support the following features: